GNOME Bugzilla – Bug 604291
crash in Evolution: Replied to a message, af...
Last modified: 2010-05-07 04:18:02 UTC
What were you doing when the application crashed? Replied to a message, after the exchange cache became corrupted. I don't know why, but occassionally evolution will "forget" about all messages. They are still on the server, and they can be accessed by: evolution --force-shutdown cd ~/.evolution rm -rf exchange cd mail rm -ef exchange cd ~ evolution And then wait for the database to rebuild. Distribution: Mandriva Linux release 2010.0 (Official) for i586 Gnome Release: 2.28.0 2009-10-22 (Mandriva) BugBuddy Version: 2.28.0 System: Linux 2.6.31.5-desktop-1mnb #1 SMP Fri Oct 23 01:46:54 EDT 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Steel Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 551931904 vsize: 551931904 resident: 358854656 share: 14307328 rss: 358854656 rss_rlim: 18446744073709551615 CPU usage: start_time: 1260446563 rtime: 228213 utime: 208852 stime: 19361 cutime:3 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb5bc68f0 (LWP 16170)] [New Thread 0xa87ffb70 (LWP 18739)] [New Thread 0xab7fcb70 (LWP 18725)] [New Thread 0xaf290b70 (LWP 24968)] [New Thread 0xaaffbb70 (LWP 24967)] [New Thread 0xafc10b70 (LWP 16325)] [New Thread 0xad7ffb70 (LWP 16324)] [New Thread 0xb0411b70 (LWP 16190)] [New Thread 0xb0c12b70 (LWP 16189)] [New Thread 0xb22fdb70 (LWP 16188)] [New Thread 0xb2afeb70 (LWP 16186)] [New Thread 0xb32ffb70 (LWP 16184)] [New Thread 0xb4684b70 (LWP 16177)] [New Thread 0xb4e85b70 (LWP 16176)] 0xffffe424 in __kernel_vsyscall ()
+ Trace 219548
Thread 2 (Thread 0xa87ffb70 (LWP 18739))
----------- .xsession-errors (941 sec old) --------------------- (gnome-panel:4980): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `GDK_IS_PIXBUF (pixbuf)' failed (gnome-panel:4980): GdkPixbuf-CRITICAL **: gdk_pixbuf_copy: assertion `GDK_IS_PIXBUF (pixbuf)' failed (gnome-panel:4980): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `GDK_IS_PIXBUF (src)' failed retrieved basic.i586.list?product=Powerpack&version=2010.0 getting exclusive lock on urpmi unlocking urpmi database medium "Main Updates" is up-to-date medium "Contrib Updates" is up-to-date medium "Non-free Updates" is up-to-date medium "Main Backports" is up-to-date medium "Contrib Backports" is up-to-date medium "Non-free Backports" is up-to-date --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
I have loaded the following debug packages: libgnomeui2-debug-2.24.2-1mdv2010.0 Wed 09 Dec 2009 06:03:27 AM CST ORBit2-debug-2.14.17-1mdv2010.0 Wed 09 Dec 2009 06:02:43 AM CST libsoup-debug-2.28.1-1mdv2010.0 Wed 09 Dec 2009 06:02:42 AM CST gvfs-debug-1.4.1-1mdv2010.0 Tue 08 Dec 2009 08:04:30 AM CST gtk+-debug-1.2.10-50mdv2009.1 Tue 08 Dec 2009 08:03:35 AM CST glib-debug-1.2.10-24mdv2010.0 Tue 08 Dec 2009 08:03:05 AM CST evolution-exchange-debug-2.28.1-1mdv2010.0 Mon 23 Nov 2009 06:52:54 PM CST evolution-data-server-debug-2.28.1-1mdv2010.0 Mon 23 Nov 2009 06:52:43 PM CST evolution-debug-2.28.1-1mdv2010.0 Mon 23 Nov 2009 06:52:13 PM CST Which other debug packages are needed to provide the traces that you desire?
Here is another crash with three more debug packages loaded.. Distribution: Mandriva Linux release 2010.0 (Official) for i586 Gnome Release: 2.28.0 2009-10-22 (Mandriva) BugBuddy Version: 2.28.0 System: Linux 2.6.31.6-desktop-1mnb #1 SMP Tue Dec 8 16:20:45 EST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Steel Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 264597504 vsize: 264597504 resident: 99495936 share: 24428544 rss: 99495936 rss_rlim: 18446744073709551615 CPU usage: start_time: 1260793433 rtime: 30826 utime: 28999 stime: 1827 cutime:25 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb5b9b8f0 (LWP 11339)] [New Thread 0xa7ffbb70 (LWP 23958)] [New Thread 0xa97feb70 (LWP 23929)] [New Thread 0xa87fcb70 (LWP 23826)] [New Thread 0xaf08bb70 (LWP 11442)] [New Thread 0xb3c93b70 (LWP 11441)] [New Thread 0xaead6b70 (LWP 11404)] [New Thread 0xad1a9b70 (LWP 11403)] [New Thread 0xb0411b70 (LWP 11363)] [New Thread 0xb0c12b70 (LWP 11362)] [New Thread 0xb22fdb70 (LWP 11361)] [New Thread 0xb2afeb70 (LWP 11356)] [New Thread 0xb32ffb70 (LWP 11354)] [New Thread 0xb4659b70 (LWP 11351)] [New Thread 0xb4e5ab70 (LWP 11349)] 0xffffe424 in __kernel_vsyscall ()
+ Trace 219598
Thread 1 (Thread 0xb5b9b8f0 (LWP 11339))
----------- .xsession-errors (88 sec old) --------------------- (npviewer.bin:11603): Gdk-WARNING **: XID collision, trouble ahead getting exclusive lock on urpmi unlocking urpmi database medium "Main Updates" is up-to-date $MIRRORLIST: media/contrib/updates/media_info/20091211-222730-synthesis.hdlist.cz updated medium "Contrib Updates" medium "Non-free Updates" is up-to-date medium "Main Backports" is up-to-date $MIRRORLIST: media/contrib/backports/media_info/20091213-162533-synthesis.hdlist.cz retrieval of [http://ftp.ndlug.nd.edu/pub/Mandrake/official/2010.0/i586/media/contrib/backports/media_info/synthesis.hdl problem reading synthesis file of medium "Contrib Backports" medium "Non-free Backports" is up-to-date Window manager warning: Invalid WM_TRANSIENT_FOR window 0x440000d specified for 0x440000b (pinentry). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x440000d specified for 0x440000b (pinentry). --------------------------------------------------
I feel both the traces are different.
NEEDINFO: Waiting on a good stack trace of the original crash. Stack trace in comment #3 is something completely different.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!