GNOME Bugzilla – Bug 585945
crash in Evolution Mail and Calendar: switching to another IMA...
Last modified: 2009-06-16 18:02:07 UTC
What were you doing when the application crashed? switching to another IMAP folder Distribution: Fedora release 11 (Leonidas) Gnome Release: 2.26.2 2009-06-01 (Red Hat, Inc) BugBuddy Version: 2.26.0 System: Linux 2.6.29.4-167.fc11.x86_64 #1 SMP Wed May 27 17:27:08 EDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10601901 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad Memory status: size: 1928081408 vsize: 1928081408 resident: 305025024 share: 26099712 rss: 305025024 rss_rlim: 18446744073709551615 CPU usage: start_time: 1245133610 rtime: 8623 utime: 7078 stime: 1545 cutime:80 cstime: 120 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f85eba4c910 (LWP 14886)] [New Thread 0x7f8617fff910 (LWP 14875)] [New Thread 0x7f85ff3f8910 (LWP 13568)] [New Thread 0x7f85ffdf9910 (LWP 13567)] [New Thread 0x7f862ddfd910 (LWP 13564)] [New Thread 0x7f86175fe910 (LWP 13563)] [New Thread 0x7f86157fb910 (LWP 13562)] [New Thread 0x7f86161fc910 (LWP 13561)] [New Thread 0x7f8616bfd910 (LWP 13560)] [New Thread 0x7f862d3fc910 (LWP 13556)] [New Thread 0x7f862f427910 (LWP 13553)] [New Thread 0x7f862fe28910 (LWP 13552)] 0x0000003ea880e9dd in __libc_waitpid (pid=14890, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL); Current language: auto; currently minimal
+ Trace 216019
Thread 1 (Thread 0x7f863b5c27f0 (LWP 13547))
---- Critical and fatal warnings logged during execution ---- ** Gdk **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed ** Gdk **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed ** Gdk **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed ** Gdk **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed ** Gdk **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed ** Gdk **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed ** Gdk **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed ----------- .xsession-errors (26 sec old) --------------------- (evolution:13547): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed (evolution:13547): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed Greasemonkey getFirebugConsole() error: (new TypeError("context is undefined", "chrome://firebug/content/consoleInjector.js", 95)) Greasemonkey getFirebugConsole() error: (new TypeError("context is undefined", "chrome://firebug/content/consoleInjector.js", 95)) Greasemonkey getFirebugConsole() error: (new TypeError("context is undefined", "chrome://firebug/content/consoleInjector.js", 95)) (evolution:13547): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() camel-Message: -- Greasemonkey getFirebugConsole() error: (new TypeError("context is undefined", "chrome://firebug/content/consoleInjector.js", 95)) --------------------------------------------------
Created attachment 136693 [details] screenshot in the moment of crash Interesting thing (in my opinion, which might be wrong) is that when switching to the new folder, right before the crash happened, only part of the headers were painted (see the screenshot). Also might be related to bug 585225 ... I was switching FROM that folder and its multi-megabyte messages.
could be dup of #537275? http://bugzilla.gnome.org/show_bug.cgi?id=537275
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 537275 ***