[Akonadi] [Bug 344863] New: KMail Migration Tool immediately segfaults
Tristan Miller
psychonaut at nothingisreal.com
Thu Mar 5 11:55:24 GMT 2015
https://bugs.kde.org/show_bug.cgi?id=344863
Bug ID: 344863
Summary: KMail Migration Tool immediately segfaults
Product: Akonadi
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: grave
Priority: NOR
Component: Migration
Assignee: kdepim-bugs at kde.org
Reporter: psychonaut at nothingisreal.com
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
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Kdepim-bugs
mailing list