GNOME Bugzilla – Bug 621224
crash in Epiphany Web Bookmarks:
Last modified: 2010-06-25 10:50:51 UTC
Version: 2.30.2 What were you doing when the application crashed? Distribution: "paldo" "1.22" ("stable") Gnome Release: 2.30.0 2010-04-30 (paldo.org) BugBuddy Version: 2.30.0 System: Linux 2.6.33.5-paldo1-x86 #1 SMP Thu May 27 11:28:52 CEST 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10800000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 235585536 vsize: 235585536 resident: 54050816 share: 29016064 rss: 54050816 rss_rlim: 18446744073709551615 CPU usage: start_time: 1276188833 rtime: 504 utime: 440 stime: 64 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany' 0xb7743424 in __kernel_vsyscall ()
+ Trace 222344
Thread 1 (process 1961)
Inferior 1 [process 1961] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. --------------------------------------------------
*** Bug 621225 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 622225 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 618355 ***