Bug 344863 - KMail Migration Tool immediately segfaults
Summary: KMail Migration Tool immediately segfaults
Status: RESOLVED INTENTIONAL
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Migration (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-05 11:55 UTC by Tristan Miller
Modified: 2016-08-13 22:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tristan Miller 2015-03-05 11:55:24 UTC 
I have a KMail configuration that I want to migrate to KMail2 on KDE 4.14.4.  When I launch kontact from the command line, it pops up a dialog informing me that I can migrate now, so I press the "Migrate Now" button.  But then the migration tool immediately segfaults and the crash handler shows the following backtrace.  The problem is always reproducible.

Application: KMail Migration Tool (kmail-migrator), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc7fe5c07c0 (LWP 10426))]

Thread 2 (Thread 0x7fc7ea37b700 (LWP 10428)):
#0  0x00007fc7fa425c3d in poll () at /lib64/libc.so.6
#1  0x00007fc7f67b6be4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fc7f67b6cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007fc7fadbf0de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#4  0x00007fc7fad90e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#5  0x00007fc7fad91165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#6  0x00007fc7fac8e0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x00007fc7fad72783 in  () at /usr/lib64/libQtCore.so.4
#8  0x00007fc7fac9079f in  () at /usr/lib64/libQtCore.so.4
#9  0x00007fc7f78fb0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x00007fc7fa42e06d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fc7fe5c07c0 (LWP 10426)):
[KCrash Handler]
#5  0x0000000000417129 in _start ()


The crash handler claims that the backtrace is not useful.  I have the following debugging packages installed, so if there are any additional ones I need let me know.

akonadi-debuginfo-4.14.5-12.5.x86_64
akonadi-runtime-debuginfo-1.13.0-2.2.3.x86_64
kdepim4-debuginfo-4.14.5-12.5.x86_64
kmail-debuginfo-4.14.5-12.5.x86_64
kontact-debuginfo-4.14.5-12.5.x86_64
kwin-debuginfo-4.11.14-3.8.x86_64
libakonadi4-debuginfo-4.14.5-12.1.x86_64
libkde4-debuginfo-4.14.3-3.1.x86_64
libkdepim4-debuginfo-4.14.5-12.5.x86_64


Reproducible: Always
Comment 1 Laurent Montel 2016-05-12 04:59:46 UTC 
In kf5 it doesn't exist now
Comment 2 Tristan Miller 2016-05-12 09:37:47 UTC 
So there is no way of migrating from KMail to KMail2?  Or is there some other upgrade path other than the KMail Migration Tool?
Comment 3 Laurent Montel 2016-05-12 10:17:18 UTC 
Nope, kmail 4.6 (before akonadi) has 8 years... so for sure we don't support it.

but you can migrate to kmail 4.14.11 and after move to kf5
but no support for kmail 4.6-> kmail 5.2
Comment 4 Tristan Miller 2016-05-12 11:14:29 UTC 
How am I supposed to migrate to KMail 4.14.11 when its migration tool is broken (as per this bug)?
Comment 5 Laurent Montel 2016-05-12 11:45:19 UTC 
did you test to 4.14.11 ?
Comment 6 Tristan Miller 2016-05-17 10:28:21 UTC 
No, but I will do that and get back to you here.
Comment 7 Tristan Miller 2016-08-13 22:54:36 UTC 
I tested just now with KMail 4.14.10 and was not able to reproduce the problem.  So I guess whatever issue was fixed between 4.14.4 and 4.14.10.