GNOME Bugzilla – Bug 353398
crash in Epiphany Web Bookmarks: Clicking on a link.
Last modified: 2007-03-25 14:17:46 UTC
Version: 2.15.91 What were you doing when the application crashed? Clicking on a link. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.92 2006-08-22 (Ubuntu) BugBuddy Version: 2.15.92 Memory status: size: 203169792 vsize: 0 resident: 203169792 share: 0 rss: 78999552 rss_rlim: 0 CPU usage: start_time: 1156771367 rtime: 0 utime: 17024 stime: 0 cutime:16280 cstime: 0 timeout: 744 it_real_value: 0 frequency: 51 Backtrace was generated from '/usr/bin/epiphany' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1228101968 (LWP 19338)] [New Thread -1298211936 (LWP 1242)] [New Thread -1342178400 (LWP 647)] [New Thread -1386222688 (LWP 646)] [New Thread -1306604640 (LWP 1570)] [New Thread -1323865184 (LWP 1569)] [New Thread -1272796256 (LWP 19348)] [New Thread -1252238432 (LWP 19342)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 71190
Thread 1 (Thread -1228101968 (LWP 19338))
Unfortunately the trace is missing the info on where gtk_style_attach is really called from... can you install the -dbg packages for the gnome stack and firefox-dbg, and see if you can reproduce the crash?
*** Bug 354673 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 353503 ***
*** Bug 355331 has been marked as a duplicate of this bug. ***
*** Bug 356558 has been marked as a duplicate of this bug. ***
*** Bug 409870 has been marked as a duplicate of this bug. ***
*** Bug 410219 has been marked as a duplicate of this bug. ***
*** Bug 410712 has been marked as a duplicate of this bug. ***
*** Bug 412481 has been marked as a duplicate of this bug. ***
*** Bug 414137 has been marked as a duplicate of this bug. ***
*** Bug 414529 has been marked as a duplicate of this bug. ***
*** Bug 422084 has been marked as a duplicate of this bug. ***
*** Bug 422494 has been marked as a duplicate of this bug. ***