GNOME Bugzilla – Bug 436751
crash in Tasks: sending an attached mail
Last modified: 2007-07-12 12:06:03 UTC
What were you doing when the application crashed? sending an attached mail Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3116.fc7 #1 SMP Thu Apr 26 10:36:44 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Fedora Memory status: size: 163401728 vsize: 163401728 resident: 52277248 share: 21405696 rss: 52277248 rss_rlim: 4294967295 CPU usage: start_time: 1178572248 rtime: 2052 utime: 1531 stime: 521 cutime:0 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208752416 (LWP 3463)] [New Thread -1250952304 (LWP 5077)] [New Thread -1298138224 (LWP 3577)] [New Thread -1239381104 (LWP 3488)] [New Thread -1228498032 (LWP 3487)] (no debugging symbols found) 0x00fc4402 in __kernel_vsyscall ()
+ Trace 132993
Thread 1 (Thread -1208752416 (LWP 3463))
----------- .xsession-errors (508 sec old) --------------------- DCOP: unregister 'anonymous-4785' DCOP: unregister 'kbuildsycoca' kdeinit: PID 4785 terminated. kdeinit: Got EXEC_NEW 'kconf_update' from launcher. Could not load library! Trying exec.... kdeinit: PID 4786 terminated. DCOP: new daemon kded DCOP: unregister 'anonymous-4783' kdeinit: PID 4783 terminated. DCOP: register 'kdevelop-4774' -> number of clients is now 1 QLayout "unnamed" added to IndexView "unnamed", which already has a layout kdeinit: Got EXEC_NEW 'kio_file' from launcher. BBDB spinning up... (evolution:3463): e-data-server-DEBUG: Loading categories from "/home/madc/.evolution/categories.xml" (evolution:3463): e-data-server-DEBUG: Loaded 29 categories --------------------------------------------------
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] 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! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
*** Bug 441831 has been marked as a duplicate of this bug. ***
*** Bug 443014 has been marked as a duplicate of this bug. ***
*** Bug 443406 has been marked as a duplicate of this bug. ***
*** Bug 444762 has been marked as a duplicate of this bug. ***
*** Bug 444839 has been marked as a duplicate of this bug. ***
*** Bug 444769 has been marked as a duplicate of this bug. ***
I had a crash when retrieving mail from my imap server. The application said it was an exception in the Task module - but it doesn't seem so. After that crash I wasn't even able to start Evolution up - it repeated the same book. I fixed the problem by deleting the files where the settings of the last session are stored - particularly somewhere under ~/.evolution/mail/ - unfortunately I don't remember more. I realize that several minutes before the first crash I rearranged the columns in sent mail - add recipient column and changed the order. Hope this will help a little...
*** Bug 443626 has been marked as a duplicate of this bug. ***
*** Bug 445414 has been marked as a duplicate of this bug. ***
*** Bug 446635 has been marked as a duplicate of this bug. ***
*** Bug 446756 has been marked as a duplicate of this bug. ***
*** Bug 446801 has been marked as a duplicate of this bug. ***
*** Bug 447227 has been marked as a duplicate of this bug. ***
*** Bug 447231 has been marked as a duplicate of this bug. ***
*** Bug 447421 has been marked as a duplicate of this bug. ***
*** Bug 447406 has been marked as a duplicate of this bug. ***
well, the exception repeated regularly (I do not realize, whether always - sorry) when closing Evolution. So I installed the gtk2-debuginfo package on my Fedora 7 and since then I'm not able to re-invoke the exception ( doing my best :-) ) Perhaps I should mention, that I just have been upgrading Fedora version by version (starting with FC3 to this Fedora 7), keeping the same configuration data.
*** Bug 447606 has been marked as a duplicate of this bug. ***
*** Bug 447554 has been marked as a duplicate of this bug. ***
This is a Fedora-specific bug and has since been fixed. See: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238497 Also, if using Fedora and Bug Buddy tells you that "Tasks" crashed, it's lying. Fedora lists each individual Evolution component in the Applications panel menu and that confuses the hell out of Bug Buddy. It just picks the first menu item it finds that invokes Evolution and then claims that's what's crashing. Current Bug Buddy versions pick "Tasks". In the past it was always "Calendar". *** This bug has been marked as a duplicate of 431342 ***
*** Bug 455931 has been marked as a duplicate of this bug. ***
My situation was similar to that of k15@mail.klfree.net . I switched to the sent folder. One of the default columns is 'from' which does not seem very useful as all the mails in this folder are from me so I tried to change the columns by removing 'from' and adding 'to' instead. The application crashed saying there was a problem with tasks. At the time I was connected to an MS exchange server using OWA. After restarting and logging in to Exchange again the application crashed again, and again. To restore some stability I restarted the application and then switched to a different folder before entering my exchange passowrd. Now it works OK as long as I do not select the sent folder. To gain access to the sent folder again I expect I need to delete something from my home folder but I have not had the time to experiment with this yet.