GNOME Bugzilla – Bug 252195
evolution crashes on exit
Last modified: 2003-12-16 19:30:48 UTC
Distribution: Debian testing/unstable Package: Evolution Priority: Normal Version: unspecified Synopsis: evolution crashes on exit Bugzilla-Product: Evolution Bugzilla-Component: Shell Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Evolution crashes when either clicking the close button, picking close from the menu, or initiating quitting some other way. It usually occurs when I've done a lot of moving around of mail (from my inbox in /var/spool/mail to that inbox's trash), but I'm not sure that this is related to the crash. I'll do some more investigation. How often does this happen? A few times a day, every fourth quit or so. Additional Information: I'm compiling Evolution 1.5 right now, so hopefully the problem is fixed there. If you have any questions, feel free to email me. Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 24914)] [New Thread 32769 (LWP 24917)] [New Thread 16386 (LWP 24918)] [New Thread 32771 (LWP 24919)] [New Thread 49156 (LWP 25290)] [New Thread 65541 (LWP 1710)] [New Thread 98310 (LWP 1741)] 0x4112cbdb in waitpid () from /lib/libpthread.so.0
+ Trace 42659
Unknown reporter: jrockway@imsa.edu, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
This is fixed in latest 1.4.5 snapshots as well as 1.5 *** This bug has been marked as a duplicate of 247253 ***