GNOME Bugzilla – Bug 492616
crash in Epiphany Web Browser: Launching Epiphany.
Last modified: 2007-11-02 11:35:24 UTC
Version: 2.20.1 What were you doing when the application crashed? Launching Epiphany. Distribution: Debian lenny/sid Gnome Release: 2.20.1 2007-10-26 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23 #1 Wed Oct 10 12:22:48 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 124133376 vsize: 124133376 resident: 38768640 share: 21987328 rss: 38768640 rss_rlim: 4294967295 CPU usage: start_time: 1193992418 rtime: 131 utime: 120 stime: 11 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 -1242409280 (LWP 17758)] [New Thread -1293976688 (LWP 17770)] [New Thread -1267881072 (LWP 17766)] [New Thread -1254605936 (LWP 17761)] 0xb7f51410 in __kernel_vsyscall ()
+ Trace 174548
Thread 1 (Thread -1242409280 (LWP 17758))
----------- .xsession-errors (573 sec old) --------------------- JACK tmpdir identified as [/dev/shm] No accelerated IMDCT transform found No accelerated IMDCT transform found JACK tmpdir identified as [/dev/shm] ERROR: No output during decompression No accelerated IMDCT transform found No accelerated IMDCT transform found JACK tmpdir identified as [/dev/shm] ERROR: No output during decompression ERROR: No output during decompression ERROR: No output during decompression ERROR: No output during decompression ERROR: No output during decompression (liferea:13301): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed --------------------------------------------------
Looks like a genuine bug.
I think this report made more sense in Debian's BTS... for what is worth, downgrading to 2.20.0 works around the crash. I'm using libxul and companions at version 1.8.1.9.
(In reply to comment #1) > Looks like a genuine bug. I noticed that the NSPR are missing. I can install the debugging symbols and regenerate the crash if you think the problem might lie in there.
In general including debug symbols for mozilla is a good idea. However in this case it's probably unnecessary. Could be that this bug is already fixed by the patch for #488718.
This is definitely a dupe of bug#488718.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 488718 ***