GNOME Bugzilla – Bug 626393
crash in Evolution: Sending a message. This ...
Last modified: 2010-08-09 03:57:47 UTC
What were you doing when the application crashed? Sending a message. This message was a reply to a previously received message. Distribution: Debian squeeze/sid Gnome Release: 2.30.2 2010-07-17 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-5-686 #1 SMP Sat Jul 24 02:27:10 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, gail:atk-bridge, canberra-gtk-module Memory status: size: 202018816 vsize: 202018816 resident: 52924416 share: 25612288 rss: 52924416 rss_rlim: 18446744073709551615 CPU usage: start_time: 1281287824 rtime: 1479 utime: 1364 stime: 115 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 0xa9e29b70 (LWP 5513)] [New Thread 0xac62eb70 (LWP 5509)] [New Thread 0xaeaa9b70 (LWP 3351)] [New Thread 0xaf2aab70 (LWP 3350)] [New Thread 0xb17d8b70 (LWP 3345)] [New Thread 0xb56aeb70 (LWP 3344)] 0xb7861424 in __kernel_vsyscall ()
+ Trace 223166
Thread 1 (Thread 0xb5ea7770 (LWP 3342))
Inferior 1 [process 3342] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (11268 sec old) --------------------- (firefox-bin:3545): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3545): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3545): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3545): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3545): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3545): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:3545): Gdk-WARNING **: XID collision, trouble ahead ...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 bug 626371 ***