GNOME Bugzilla – Bug 578316
crash in Epiphany Web Browser:
Last modified: 2009-04-08 10:51:52 UTC
Version: 2.22.1.1 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 558837760 vsize: 558837760 resident: 78344192 share: 30228480 rss: 78344192 rss_rlim: 18446744073709551615 CPU usage: start_time: 1239153925 rtime: 1357 utime: 1121 stime: 236 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2aec077a0de0 (LWP 8148)] [New Thread 0x44808950 (LWP 8162)] [New Thread 0x44007950 (LWP 8161)] [New Thread 0x43005950 (LWP 8158)] [New Thread 0x41001950 (LWP 8151)] (no debugging symbols found) 0x00002aec01839edf in waitpid () from /lib/libpthread.so.0
+ Trace 214270
Thread 1 (Thread 0x2aec077a0de0 (LWP 8148))
----------- .xsession-errors (274 sec old) --------------------- Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** (gnome-app-install:8447): WARNING **: return value of custom widget handler was not a GtkWidget /usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1254: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed item.applications.set_default_sort_func(None) --------------------------------------------------
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 536768 ***