Epiphany crashes when restoring it from an old session

Bug #31670 reported by Ernst Persson
10
Affects Status Importance Assigned to Milestone
epiphany (Ubuntu)
Dapper
Invalid
Medium
Unassigned
epiphany-browser (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

I have auto-save session enabled in gnome.
When epiphany is saved in the session,
it crashes when I log in again.

Allways happens. I'm not sure how to get a backtrace or even printout of that.

Changed in epiphany:
status: Unconfirmed → Rejected
Revision history for this message
Ernst Persson (ernstp) wrote :

This was probably the error reporter extension. Works much better without it.

Revision history for this message
jhellen (jukka-hellen) wrote :
Download full text (9.4 KiB)

Could this be the same thing? I had some crashes with epiphany also.

Distribution: Ubuntu 6.04 (dapper)
Package: epiphany
Severity: Normal
Version: GNOME2.13.92 1.9.8
Gnome-Distributor: Ubuntu
Synopsis: Epiphany crashes at start
Bugzilla-Product: epiphany
Bugzilla-Component: General
Bugzilla-Version: 1.9.8
BugBuddy-GnomeVersion: 2.0 (2.13.90)
Description:
Description of the crash:
Epiphany crashes at start

Steps to reproduce the crash:
1. Just try to start Epiphany
2.
3.

Expected Results:
It should start Epiphany

How often does this happen?
First time now after yesterdays ubuntu dapper f4 update

Additional Information:
I think it has to do with my gtk theme:

/home/jhellen/.themes/T-ish-Brushed-bright/gtk-2.0/gtkrc:2: Unable to
find include file: "iconrc"

** (epiphany:7012): WARNING **: An error occured while calling remote
method: No reply within specified time

Debugging Information:

Backtrace was generated from '/usr/bin/epiphany'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1993316032 (LWP 6922)]
[New Thread 1974508464 (LWP 6925)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x7714a48b in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0x77e5e672 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0x76a2baed in js_fgets () from /usr/lib/firefox/libmozjs.so
#5 0x76a2e2a0 in js_fgets () from /usr/lib/firefox/libmozjs.so
#6 0x76a1bc3e in js_FindProperty () from /usr/lib/firefox/libmozjs.so
#7 0x76a21df9 in js_CompileTokenStream () from
/usr/lib/firefox/libmozjs.so
#8 0x769cd664 in JS_DefineUCFunction () from
/usr/lib/firefox/libmozjs.so
#9 0x769cd9cb in JS_CompileFileHandleForPrincipals ()
   from /usr/lib/firefox/libmozjs.so
#10 0x76a939be in NSGetModule ()
   from /usr/lib/firefox/components/libxpconnect.so
#11 0x76a93b19 in NSGetModule ()
   from /usr/lib/firefox/components/libxpconnect.so
#12 0x76a93eed in NSGetModule ()
   from /usr/lib/firefox/components/libxpconnect.so
#13 0x76a94360 in NSGetModule ()
   from /usr/lib/firefox/components/libxpconnect.so
#14 0x76a92e9a in NSGetModule ()
   from /usr/lib/firefox/components/libxpconnect.so
#15 0x76a92f05 in NSGetModule ()
   from /usr/lib/firefox/components/libxpconnect.so
#16 0x76f05eb8 in NS_GetComponentRegistrar_P ()
   from /usr/lib/firefox/libxpcom_core.so
#17 0x76f0688c in NS_GetComponentRegistrar_P ()
   from /usr/lib/firefox/libxpcom_core.so
#18 0x76f069fb in NS_GetComponentRegistrar_P ()
   from /usr/lib/firefox/libxpcom_core.so
#19 0x76ed1886 in NS_InitXPCOM3_P () from
/usr/lib/firefox/libxpcom_core.so
#20 0x77f57759 in NS_InitXPCOM3 () from /usr/lib/firefox/libxpcom.so
#21 0x77f67086 in gtk_moz_embed_get_title ()
   from /usr/lib/firefox/libgtkembedmoz.so
#22 0x77f6188b in gtk_moz_embed_get_ti...

Read more...

Revision history for this message
Barry deFreese (bddebian) wrote :

Why was this rejected for Dapper? Is this bug still an issue? I can't reproduce it? Thank you.

Changed in epiphany-browser:
status: Unconfirmed → Needs Info
Revision history for this message
Dennis Kaarsemaker (dennis) wrote : Re: [Bug 31670] Re: Epiphany crashes when restoring it from an old session

On ma, 2006-05-08 at 01:44 +0000, Barry deFreese wrote:
> Why was this rejected for Dapper?

Policy decision: no bugs need to be open on both ubuntu and ubuntu
dapper.
--
Dennis K.

Time is an illusion, lunchtime doubly so.

Revision history for this message
Dean Sas (dsas) wrote :

Hi, Are you still experiencing these crashes?

If so could you get a backtrace following the instructions at https://help.ubuntu.com/community/DebuggingProgramCrash

Revision history for this message
Sebastien Bacher (seb128) wrote :

no reply, bug closed. Feel free to reopen if you still get the issue

Changed in epiphany-browser:
assignee: nobody → desktop-bugs
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.