After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 271007 - Upgrade from FC2 to FC3 causes Evolution to crash while migrating data
Upgrade from FC2 to FC3 causes Evolution to crash while migrating data
Status: RESOLVED DUPLICATE of bug 269566
Product: evolution
Classification: Applications
Component: Mailer
2.0.x (obsolete)
Other All
: Normal major
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-01-05 00:13 UTC by bugzilla
Modified: 2005-01-05 02:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description bugzilla 2005-01-05 00:13:21 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Package: Evolution
Priority: Major
Version: GNOME2.8.0 2.0.2
Gnome-Distributor: Red Hat, Inc
Synopsis: Upgrade from FC2 to FC3 causes Evolution to crash while migrating data
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: 2.0.2
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
Was using Evolution under Fedora Core 2.
Upgraded machine to Fedora Core 3.
When I started Evolution it said something about the folder locations
have been changed in this new version and it started automatically
migrating them.  It made it almost all the way through and then
crashed.

I will not be able to reproduce the crash  since I have to upgrade from
FC2 to FC3 to do it.

I will investigate further.


Debugging Information:

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...`shared object read from target memory'
has disappeared; keeping its symbols.
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(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 -1227327264 (LWP 7517)]
[New Thread -1246757968 (LWP 7547)]
[Thread debugging using libthread_db enabled]
[New Thread -1227327264 (LWP 7517)]
[New Thread -1246757968 (LWP 7547)]
[Thread debugging using libthread_db enabled]
[New Thread -1227327264 (LWP 7517)]
[New Thread -1246757968 (LWP 7547)]
[New Thread -1236608080 (LWP 7546)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(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 __kernel_vsyscall
()



Unknown reporter: bugzilla@darkpixel.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.

Comment 1 Gerardo Marin 2005-01-05 02:30:28 UTC

*** This bug has been marked as a duplicate of 269566 ***