GNOME Bugzilla – Bug 270819
Evolution crashes on trying to migrate/import old setup
Last modified: 2004-12-27 20:26:21 UTC
Distribution: SuSE Linux 9.2 (i586) Package: Evolution Priority: Normal Version: GNOME2.6. 2.0.1 Gnome-Distributor: SUSE Synopsis: Evolution crashes on trying to migrate/import old setup Bugzilla-Product: Evolution Bugzilla-Component: Importers Bugzilla-Version: 2.0.1 BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: On launch, Evolution 2.0.1 detects an old evolution 1.x installation, and pops up a "Migrating..." message box. It gets through a number of folders (including personally created ones) until it gets to "Sent", at which point another message box pops up to the effect that Evolution has ended unexpectedly. Steps to reproduce the crash: 1. Place all files for Evolution 1.x (from ./evolution) in user home directory 2. Launch Evolution 2.0.1 from Task bar. 3. Expected Results: Presumably, Evolution 2.0 should migrate old files normally and launch. How often does this happen? Invariably Additional Information: Suse 9.2 standard installation Debugging Information: Backtrace was generated from '/opt/gnome/bin/evolution-2.0' (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 1093092224 (LWP 7100)] (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 53891
Thread 1 (Thread 1093092224 (LWP 7100))
Unknown reporter: arjun.ray@verizon.net, 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 268787 ***