GNOME Bugzilla – Bug 542368
crash in Epiphany Web Bookmarks: starting epiphany
Last modified: 2008-07-12 15:54:36 UTC
Version: 2.22.2 What were you doing when the application crashed? starting epiphany Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-custom #1 Wed May 21 22:50:36 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: UbuntuStudio Icon Theme: black-white_2-Style Memory status: size: 99012608 vsize: 99012608 resident: 41603072 share: 22667264 rss: 41603072 rss_rlim: 4294967295 CPU usage: start_time: 1215695045 rtime: 935 utime: 850 stime: 85 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6aab720 (LWP 11973)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 202480
Thread 1 (Thread 0xb6aab720 (LWP 11973))
----------- .xsession-errors --------------------- Launched application : 11739 *** Calendar schema version is: 7 CLIENT: Task: Task::done() CLIENT: Task: emitting finished Transfer ACCEPTED by: MailNotifierTask CLIENT: Task: Task::done() CLIENT: Task: emitting finished Launched application : 11928 CLIENT: Task: Task::done() CLIENT: Task: emitting finished Transfer ACCEPTED by: MailNotifierTask (epiphany-browser:11973): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `EphyNetMonitor' CLIENT: Task: Task::done() CLIENT: Task: emitting finished --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for epiphany, gtk, glib, libgnome, libgnomeui, and the backend (for example webkit, firefox, or xulrunner) (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
i don't know if the reason for this crash is the same. the only debug-package missing last time was from xulrunner-1.9 Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-custom #1 Wed May 21 22:50:36 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Moomex Icon Theme: black-white_2-Gloss Memory status: size: 134234112 vsize: 134234112 resident: 49905664 share: 24268800 rss: 49905664 rss_rlim: 4294967295 CPU usage: start_time: 1215797835 rtime: 1986 utime: 1840 stime: 146 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6a68720 (LWP 2903)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 202582
Thread 1 (Thread 0xb6a68720 (LWP 2903))
----------- .xsession-errors (16 sec old) --------------------- 'panel-menu=24,24 panel=20,20 gtk-button=18,18 gtk-large-toolbar=24,24' Network timeout occured. Cancel active operations. CLIENT: Task: Task::done() CLIENT: Task: emitting finished CLIENT: Task: Task::done() CLIENT: Task: emitting finished OggS-SEEK: at 0 want 164344 got 160064 (diff-requested 164344) OggS-SEEK: at 164160 want 520 got 0 (diff-requested -163640) CLIENT: Task: Task::done() CLIENT: Task: emitting finished CLIENT: Task: Task::done() CLIENT: Task: emitting finished --------------------------------------------------
Thanks for the info. This is actually a dupe of bug 509083.
*** This bug has been marked as a duplicate of 509083 ***