GNOME Bugzilla – Bug 562279
crash in Evolution Mail and Calendar: I opened my evolution, t...
Last modified: 2008-11-27 11:19:18 UTC
What were you doing when the application crashed? I opened my evolution, then it started to download emails (I have 2 imaps accounts + 28 virtual folders). When finished to download, it started to filter emails (a very slow operation that take about 1 hour). While it filtered emails, I clicked on a mail in INBOX phisical directory of an account, this operation occured a lot of time, so I clicked on "cancel" icon to stop filtering and evolution crashes. Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.1 2008-11-06 (Red Hat, Inc) BugBuddy Version: 2.24.1 System: Linux 2.6.27.5-117.fc10.x86_64 #1 SMP Tue Nov 18 11:58:53 EST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 691875840 vsize: 691875840 resident: 57896960 share: 20922368 rss: 57896960 rss_rlim: 18446744073709551615 CPU usage: start_time: 1227658692 rtime: 649 utime: 520 stime: 129 cutime:2 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0x7fcd370fd7e0 (LWP 5628)] [New Thread 0x7fcd23fff950 (LWP 5686)] [New Thread 0x7fcd2a71d950 (LWP 5656)] [New Thread 0x7fcd2b329950 (LWP 5654)] 0x0000003dd54dc846 in poll () from /lib64/libc.so.6
+ Trace 210228
Thread 4 (Thread 0x7fcd2b329950 (LWP 5654))
----------- .xsession-errors (35 sec old) --------------------- (evolution:4974): camel-WARNING **: uid 44298 vanished from folder: imap://luca%40foppiano.org@imap.foppiano.org/INBOX (evolution:4974): camel-WARNING **: uid 44299 vanished from folder: imap://luca%40foppiano.org@imap.foppiano.org/INBOX (evolution:4974): e-data-server-WARNING **: Error in execution: Failed to retrieve message (evolution:4974): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:4974): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:4974): camel-WARNING **: camel_exception_get_id called with NULL parameter. evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:5628): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:5628): DEBUG: mailto URL program: evolution --------------------------------------------------
No signal_handler / segv call :/ 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. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, evolution-exchange, gtkhtml, gtk, glib, libsoup, gnome-vfs, libgnome, orbit2 and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
I tried to reproduce crash, but I have problem to reproduce with sequence I provided. I think this is a duplicate of http://bugzilla.gnome.org/show_bug.cgi?id=558337 because I'm not sure I managed folders before crash. I tried to perform this sequence. - open evolution - manage folder (add trash, remove trash, add junk, remove junk) - click on certain virtual and phisical folders, - evolution crashes... If you need I'll provide stacktrace.
thanks, then i will mark bug as dupe but please install debug info rpms so you can get better traces in future. 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 558337 ***
I installed all the debuginfo packages you told, I'll try to simulate crash, I'll register stacktrace, nd I'll post on this ticket as soon as possible.