GNOME Bugzilla – Bug 270856
Crash: evolution launch on Suse 9.2 hangs in migrating folders from v1.x
Last modified: 2004-12-28 22:46:50 UTC
Distribution: SuSE Linux 9.2 (i586) Package: Evolution Priority: Critical Version: GNOME2.6. 2.0.1 Gnome-Distributor: SUSE Synopsis: evolution launch on Suse 9.2 hangs in migrating folders from v1.x Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.0.1 BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: /opt/gnome/bin/evolution ... Steps to reproduce the crash: 1. /opt/gnome/bin/evolution ... 2. 3. Expected Results: completed migration and client start How often does this happen? Additional Information: Dissapointed that Suse 9.2 removed the Evolution app from the provided gui selections in .../internet/brownsers. This is a major reason I liked Suse 9.1, redhat and fedora, ... 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 1093141376 (LWP 6457)] [New Thread 1116703664 (LWP 6482)] [Thread debugging using libthread_db enabled] [New Thread 1093141376 (LWP 6457)] [New Thread 1116703664 (LWP 6482)] [Thread debugging using libthread_db enabled] [New Thread 1093141376 (LWP 6457)] [New Thread 1116703664 (LWP 6482)] [New Thread 1114602416 (LWP 6481)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(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 53932
Thread 1 (Thread 1093141376 (LWP 6457))
Unknown reporter: joesch@woodtennis.com, 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 ***