GNOME Bugzilla – Bug 595483
crash in Epiphany Web Bookmarks: Закрывал его... Просто з...
Last modified: 2009-09-17 20:53:36 UTC
Version: 2.26.3 What were you doing when the application crashed? Закрывал его... Просто закрывал... Предварительно дав задание на печать нескольких страниц текста... Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.30.4 #1 SMP PREEMPT Tue Aug 4 19:36:36 EEST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 170745856 vsize: 170745856 resident: 55971840 share: 30576640 rss: 55971840 rss_rlim: 18446744073709551615 CPU usage: start_time: 1253203857 rtime: 1058 utime: 996 stime: 62 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-gecko' [Thread debugging using libthread_db enabled] 0xffffe424 in __kernel_vsyscall ()
+ Trace 217646
Thread 1 (Thread 0xb6b2a760 (LWP 27045))
----------- .xsession-errors (460 sec old) --------------------- (gecko:10849): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed (gecko:10849): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed (gecko:10849): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed (gecko:10849): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed (gecko:10849): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed (gecko:10849): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed (gecko:10849): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed (gecko:10849): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed --------------------------------------------------
Thanks for taking the time to file this bug report. This issue is already filed in our bug tracker as bug 509083. Please feel free to report any other problem you find. *** This bug has been marked as a duplicate of bug 509083 ***