GNOME Bugzilla – Bug 253680
Evolution crash on restart
Last modified: 2004-02-02 03:48:23 UTC
Package: Evolution Priority: Normal Version: GNOME2.2.2 1.4.4 os_details: GNOME.Org Synopsis: Evolution crash on restart Bugzilla-Product: Evolution Bugzilla-Component: Mailer BugBuddy-GnomeVersion: 2.0 (2.2.2) Description: Description of Problem: Working over VPN using POP3. VPN connection was lost and user tried to answer the message. Evolution started to retrieve, but hangs forever. Evolutin was killed (all tasks that was possible to see using ps aux | grep -i evolution). Now tried to start evolution again. Evolution crashed. Steps to reproduce the problem: 1. Connect to POP3 over VPN and receive new message 2. Disconnect VPN and try to answer the mesage. Evolution hangs now. Kill evolution 3. Start evolution again Actual Results: Evolution crash Expected Results: Evolution does not hang, and allows to abort the operation using "Cancel" button Evolution does not crash after restart How often does this happen? This is first time I can see this behaviour, but I think that this is reproducible Additional Information: Debugging Information: Backtrace was generated from '/opt/gnome/bin/evolution-1.4' (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)... (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)... (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 6204)] [New Thread 32769 (LWP 6213)] [New Thread 16386 (LWP 6214)] [New Thread 32771 (LWP 6215)] (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)...0x4108dab6 in waitpid () from /lib/i686/libpthread.so.0
+ Trace 43695
Thread 4 (Thread 32771 (LWP 6215))
Unknown reporter: koroid.alla@arcor.de, 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 a glibc error recently fixed. *** This bug has been marked as a duplicate of 243160 ***