GNOME Bugzilla – Bug 518354
crash in Epiphany Web Browser:
Last modified: 2008-02-24 18:15:42 UTC
Version: 2.20.2 What were you doing when the application crashed? Distribution: PCLinuxOS release 2007 (PCLinuxOS) for i586 Gnome Release: 2.21.2 2007-11-30 (%vendor) BugBuddy Version: 2.20.1 System: Linux 2.6.18.8.tex5 #1 SMP Thu May 10 11:36:58 WST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Enabled GTK+ Theme: Crux Icon Theme: default.kde Memory status: size: 275415040 vsize: 275415040 resident: 103096320 share: 34504704 rss: 103096320 rss_rlim: 4294967295 CPU usage: start_time: 1203818545 rtime: 73051 utime: 69972 stime: 3079 cutime:52 cstime: 17 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany' (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231993136 (LWP 5223)] [New Thread -1456280672 (LWP 5445)] [New Thread -1337291872 (LWP 5329)] [New Thread -1328608352 (LWP 5328)] [New Thread -1394148448 (LWP 5304)] [New Thread -1383810144 (LWP 5303)] [New Thread -1305597024 (LWP 5234)] [New Thread -1287767136 (LWP 5233)] (no debugging symbols found) 0xb7f54410 in __kernel_vsyscall ()
+ Trace 190252
Thread 8 (Thread -1287767136 (LWP 5233)): #-1 0xb7f54410 in __kernel_vsyscall () No symbol table info available. Thread 7 (Thread -1305597024 (LWP 5234)): #-1 0xb7f54410 in __kernel_vsyscall () No symbol table info available. Thread 6 (Thread -1383810144 (LWP 5303)): #-1 0xb7f54410 in __kernel_vsyscall () No symbol table info available. Thread 5 (Thread -1394148448 (LWP 5304)): #-1 0xb7f54410 in __kernel_vsyscall () No symbol table info available. Thread 4 (Thread -1328608352 (LWP 5328)): #-1 0xb7f54410 in __kernel_vsyscall () No symbol table info available. Thread 3 (Thread -1337291872 (LWP 5329)): #-1 0xb7f54410 in __kernel_vsyscall () No symbol table info available. Thread 2 (Thread -1456280672 (LWP 5445)): #-1 0xb7f54410 in __kernel_vsyscall () No symbol table info available. Thread 1 (Thread -1231993136 (LWP 5223)): #-1 0xb7f54410 in __kernel_vsyscall () No symbol table info available. ----------- .xsession-errors --------------------- Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded --------------------------------------------------
Looks like a GTK+ problem. 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 mozilla backend (for example mozilla, firefox, or xulrunner) (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
*** This bug has been marked as a duplicate of 513230 ***