GNOME Bugzilla – Bug 543654
crash in Epiphany Web Browser:
Last modified: 2008-07-20 16:22:58 UTC
Version: 2.22.2 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-amd64 #1 SMP Fri Jun 27 00:16:12 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: OxygenRefit2-black-version Memory status: size: 649773056 vsize: 649773056 resident: 56131584 share: 28745728 rss: 56131584 rss_rlim: 18446744073709551615 CPU usage: start_time: 1216414374 rtime: 122 utime: 110 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7ff809c38780 (LWP 30682)] [New Thread 0x40f4b950 (LWP 30693)] [New Thread 0x43f5e950 (LWP 30692)] [New Thread 0x4375d950 (LWP 30691)] [New Thread 0x42f5c950 (LWP 30690)] [New Thread 0x4275b950 (LWP 30689)] [New Thread 0x41f5a950 (LWP 30686)] [New Thread 0x41759950 (LWP 30683)] 0x00007ff8025f9edf in waitpid () from /lib/libpthread.so.0
+ Trace 203214
Thread 1 (Thread 0x7ff809c38780 (LWP 30682))
----------- .xsession-errors (42873 sec old) --------------------- /dev/dsp: Device or resource busy /dev/dsp: Device or resource busy /dev/dsp: Device or resource busy /dev/dsp: Device or resource busy A: 0.0 (00.0) of 0.5 (00.4) ??,?% /dev/dsp: Device or resource busy /dev/dsp: Device or resource busy /dev/dsp: Device or resource busy /dev/dsp: Device or resource busy /dev/dsp: Device or resource busy /dev/dsp: Device or resource busy /dev/dsp: Device or resource busy A: 0.0 (00.0) of 0.5 (00.4) ??,?% A: 0.0 (00.0) of 0.5 (00.4) ??,?% A: 0.0 (00.0) of 0.5 (00.4) ??,?% Exiting... (End of file) A: 0.1 (00.0) of 0.5 (00.4) ??,?% A: 0.1 (00.0) of 0.5 (00.4) ??,?% A: 0.1 (00.0) of 0.5 (00.4) ??,?% ...Too much output, ignoring rest... --------------------------------------------------
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 installed some packages and here are more details. I just started Epiphany. It said "Transferring data from debian.org" and then crashed. I supposed it might be connected to the crashes of Iceweasel 3 rc2 which doesn't even show its window and that's why I have downgraded the package so I have some usable browser. Here is the new info from bug-buddy: Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-amd64 #1 SMP Fri Jun 27 00:16:12 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: OxygenRefit2-black-version Memory status: size: 666521600 vsize: 666521600 resident: 56098816 share: 28762112 rss: 56098816 rss_rlim: 18446744073709551615 CPU usage: start_time: 1216569493 rtime: 106 utime: 88 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f7935969780 (LWP 14486)] [New Thread 0x45488950 (LWP 14514)] [New Thread 0x44c87950 (LWP 14513)] [New Thread 0x44486950 (LWP 14512)] [New Thread 0x43c85950 (LWP 14510)] [New Thread 0x43484950 (LWP 14509)] [New Thread 0x42482950 (LWP 14508)] [New Thread 0x40e57950 (LWP 14507)] [New Thread 0x42c83950 (LWP 14505)] [New Thread 0x41c81950 (LWP 14487)] 0x00007f792e32aedf in waitpid () from /lib/libpthread.so.0
+ Trace 203338
Thread 1 (Thread 0x7f7935969780 (LWP 14486))
----------- .xsession-errors (126 sec old) --------------------- Gtk-Message: Failed to load module "gnomebreakpad": /usr/lib/gtk-2.0/modules/libgnomebreakpad.so: wrong ELF class: ELFCLASS64 Gtk-Message: Failed to load module "gnomebreakpad": /usr/lib/gtk-2.0/modules/libgnomebreakpad.so: wrong ELF class: ELFCLASS64 Gtk-Message: Failed to load module "gnomebreakpad": /usr/lib/gtk-2.0/modules/libgnomebreakpad.so: wrong ELF class: ELFCLASS64 Gtk-Message: Failed to load module "gnomebreakpad": /usr/lib/gtk-2.0/modules/libgnomebreakpad.so: wrong ELF class: ELFCLASS64 Gtk-Message: Failed to load module "gnomebreakpad": /usr/lib/gtk-2.0/modules/libgnomebreakpad.so: wrong ELF class: ELFCLASS64 /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) current dist not found in meta-release file /usr/lib/bug-buddy/firefox-bin: No such file or directory. Gtk-Message: Failed to load module "gnomebreakpad": /usr/lib/gtk-2.0/modules/libgnomebreakpad.so: wrong ELF class: ELFCLASS64 Window manager warning: last_user_time (1985603200) is greater than comparison timestamp (20982964). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ Window manager warning: 0x3a00095 (Synaptic) appears to be one of the offending windows with a timestamp of 1985603200. Working around... warning: could not initiate dbus current dist not found in meta-release file *** This build of Glib was compiled with glib 2.16.4, but is currently running with 2.16.3, which is too old. We'll continue, but expect problems! --------------------------------------------------
Thanks for the information! It turns out that this crash is already filed in bug 538569. Could you check if the bug is already filed with Mozilla, and file one if not? Thanks again. *** This bug has been marked as a duplicate of 538569 ***