GNOME Bugzilla – Bug 267950
Crash when importing Evo1.4 calendar
Last modified: 2004-10-12 00:08:47 UTC
Distribution: SuSE Linux 9.2 (i586) Package: Evolution Priority: Normal Version: GNOME2.6. 2.0.1 Gnome-Distributor: SUSE Synopsis: Crash when importing Evo1.4 calendar Bugzilla-Product: Evolution Bugzilla-Component: Importers Bugzilla-Version: 2.0.1 BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: After installing new version Evo 2 crashed when trying to import my old calendar Steps to reproduce the crash: 1. Install new computer with Evo2 2. Copy old (1.4) ~/evolution directory to new computer 3. run evo Expected Results: How often does this happen? It happened once, now I have to try to reset configuration Additional Information: Debugging Information: Backtrace was generated from '/opt/gnome/bin/evolution' (no debugging symbols found)...Using host libthread_db library "/lib/tls/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)...[Thread debugging using libthread_db enabled] [New Thread 1093088128 (LWP 9526)] [New Thread 1116375984 (LWP 9596)] [Thread debugging using libthread_db enabled] [New Thread 1093088128 (LWP 9526)] [New Thread 1116375984 (LWP 9596)] [Thread debugging using libthread_db enabled] [New Thread 1093088128 (LWP 9526)] [New Thread 1116375984 (LWP 9596)] [New Thread 1114274736 (LWP 9595)] (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)...0xffffe410 in ?? ()
+ Trace 50951
Thread 1 (Thread 1093088128 (LWP 9526))
Unknown reporter: lsafar@novell.cz, 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 267675 ***