GNOME Bugzilla – Bug 269886
Starting to use webcalendars work, but crash when evo restarts
Last modified: 2005-08-11 21:27:02 UTC
Distribution: Debian 3.1 Package: Evolution Priority: Normal Version: GNOME2.6.1 2.0.2 Gnome-Distributor: Debian Synopsis: Starting to use webcalendars work, but crash when evo restarts Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.0.2 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: I Put in a webcal (backend is apache, ics creator is mozcal), it imported it fine. But the n i stoped and then started evo and now it crashes every single time i start it, no matter what i do with evolution -c Remeber, this is debianppc latest sid packages Steps to reproduce the crash: 1. Create a webcal 2. Verify it 3. Delete your webcal 4. Close evo or reboot machine 5. Evo doesnt come back Expected Results: Evo should come back fine How often does this happen? Every time as far as ive seen Additional Information: Buuu... i cant use teh evo...:( Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.0' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 2951)] [New Thread 32769 (LWP 2955)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 2951)] [New Thread 32769 (LWP 2955)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 2951)] [New Thread 32769 (LWP 2955)] [New Thread 16386 (LWP 2956)] [New Thread 32771 (LWP 2957)] (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)...(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)...0x0ead9110 in waitpid () from /lib/libpthread.so.0
+ Trace 52604
Thread 1 (Thread 16384 (LWP 2951))
Unknown reporter: alex@co.com.mx, 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 bug has been marked as a duplicate of 269566 ***
This is not a 69566 duplicate
Does this still happen with evolution 2.2.x? If so, can you provide us with the information about the webcal that you subscribed to and deleted it later?
closing this bug as the reporter has not responded. Please reopen the bug if you find this happening in the latest version with the needed information.