GNOME Bugzilla – Bug 593708
crash in Evolution Mail and Calendar: Switching from a pine fo...
Last modified: 2009-12-21 04:40:43 UTC
What were you doing when the application crashed? Switching from a pine folder to Inbox folder Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.30-1-amd64 #1 SMP Sat Aug 15 21:08:31 UTC 2009 x86_64 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: 150470656 vsize: 150470656 resident: 35823616 share: 20779008 rss: 35823616 rss_rlim: 18446744073709551615 CPU usage: start_time: 1251744950 rtime: 1042 utime: 846 stime: 196 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xf16a8b90 (LWP 26116)] [New Thread 0xf1ea9b90 (LWP 26115)] [New Thread 0xf2eabb90 (LWP 26113)] [New Thread 0xf36acb90 (LWP 26112)] [New Thread 0xf3eadb90 (LWP 26111)] [New Thread 0xf59a5b90 (LWP 26109)] 0xf7fb4425 in __kernel_vsyscall ()
+ Trace 217252
Thread 1 (Thread 0xf61df760 (LWP 26103))
----------- .xsession-errors (255127 sec old) --------------------- (epiphany-browser:9271): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:9271): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:9271): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:9271): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:9271): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:9271): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:9271): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
possible dupe of bug 582226
*** Bug 599288 has been marked as a duplicate of this bug. ***
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 bug 473887 ***