GNOME Bugzilla – Bug 552355
crash in Epiphany Web Bookmarks: increasing text size
Last modified: 2008-09-15 14:56:31 UTC
Version: 2.22.3 What were you doing when the application crashed? increasing text size Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Thu Aug 28 12:00:54 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: EasyListening Icon Theme: Gorilla Memory status: size: 149078016 vsize: 149078016 resident: 42811392 share: 25673728 rss: 42811392 rss_rlim: 4294967295 CPU usage: start_time: 1221488762 rtime: 203 utime: 187 stime: 16 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 0xb6bd5700 (LWP 5680)] [New Thread 0xb22b2b90 (LWP 5690)] [New Thread 0xb2ab3b90 (LWP 5689)] [New Thread 0xb32b4b90 (LWP 5688)] [New Thread 0xb3d05b90 (LWP 5686)] [New Thread 0xb4d07b90 (LWP 5685)] [New Thread 0xb4506b90 (LWP 5684)] [New Thread 0xb5b0db90 (LWP 5681)] (no debugging symbols found) 0xb7fd7424 in __kernel_vsyscall ()
+ Trace 206794
----------- .xsession-errors (139995 sec old) --------------------- [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0]header damaged [mpeg4 @ 0xb5f425b0] ...Too much output, ignoring rest... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 525357 ***