Bug 368417 - adding IMAP account causing akonadi_imap_resource segmentation faults
Summary: adding IMAP account causing akonadi_imap_resource segmentation faults
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2016-09-07 19:02 UTC by Ian Borg
Modified: 2018-10-27 04:10 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Borg 2016-09-07 19:02:58 UTC
Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-35-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
just finished adding an imap account. 
The exact same account config info is working fine on my mobile phone, also just set up.
This is not a new install of kontact/kmail, it's been running for a couple of years. I just changed web hosting services and had to reconfigure the email account to match the new server. I had the same setup on the old servers, only the server address has changed.
The imap gmail account has not changed and is working fine with no errors.
When I go into Configure Kmail, the account is stuck on "Syncing folder 'inbox' (100%)"

The crash can be reproduced every time.

-- Backtrace:
Application: icb@wavefront of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbd32c3e780 (LWP 2672))]

Thread 3 (Thread 0x7fbd1f724700 (LWP 2728)):
#0  0x00007fbd2e58988d in poll () at /lib64/libc.so.6
#1  0x00007fbd2d511be4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fbd2d511cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007fbd3226b0de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#4  0x00007fbd3223ce6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#5  0x00007fbd3223d165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#6  0x00007fbd3213a0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x00007fbd3213c79f in  () at /usr/lib64/libQtCore.so.4
#8  0x00007fbd2dbf60a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007fbd2e591cbd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fbd17fff700 (LWP 2763)):
#0  0x00007fbd2d5538e9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x00007fbd2d51152e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fbd2d511b7b in  () at /usr/lib64/libglib-2.0.so.0
#3  0x00007fbd2d511cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#4  0x00007fbd3226b0de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#5  0x00007fbd3223ce6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#6  0x00007fbd3223d165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#7  0x00007fbd3213a0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x00007fbd3213c79f in  () at /usr/lib64/libQtCore.so.4
#9  0x00007fbd2dbf60a4 in start_thread () at /lib64/libpthread.so.0
#10 0x00007fbd2e591cbd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fbd32c3e780 (LWP 2672)):
[KCrash Handler]
#5  0x000000000045cd3b in  ()
#6  0x00007fbd3271a0cf in  () at /usr/lib64/libakonadi-kde.so.4
#7  0x00007fbd3268706c in Akonadi::CollectionModifyJob::doStart() () at /usr/lib64/libakonadi-kde.so.4
#8  0x00007fbd32700367 in  () at /usr/lib64/libakonadi-kde.so.4
#9  0x00007fbd3274cf39 in  () at /usr/lib64/libakonadi-kde.so.4
#10 0x00007fbd3274d6d5 in  () at /usr/lib64/libakonadi-kde.so.4
#11 0x00007fbd3225659e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4
#12 0x00007fbd315d776c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#13 0x00007fbd315ddcad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#14 0x00007fbd2f6ede0a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5
#15 0x00007fbd3223e2ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4
#16 0x00007fbd3224157d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#17 0x00007fbd3226b8fe in  () at /usr/lib64/libQtCore.so.4
#18 0x00007fbd2d511a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#19 0x00007fbd2d511c48 in  () at /usr/lib64/libglib-2.0.so.0
#20 0x00007fbd2d511cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#21 0x00007fbd3226b0be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#22 0x00007fbd31674676 in  () at /usr/lib64/libQtGui.so.4
#23 0x00007fbd3223ce6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#24 0x00007fbd3223d165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#25 0x00007fbd322425b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4
#26 0x00007fbd32727f83 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () at /usr/lib64/libakonadi-kde.so.4
#27 0x0000000000419f53 in _start ()

Reported using DrKonqi
Comment 1 Daniel Vrátil 2016-09-15 12:10:51 UTC
Thanks for the bug report. Could you please install debug info packages for libakonadi-kde and provide a more complete backtrace? Also if you could test with latest release (KDE Applications 16.08), it would be great. There's actually quite a big chance we've fixed the crash.
Comment 2 Andrew Crouthamel 2018-09-26 22:27:36 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 04:10:38 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!