Bug 348365 - imap ressource crashes on start
Summary: imap ressource crashes on start
Status: RESOLVED DUPLICATE of bug 351850
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
Depends on:
Blocks:
 
Reported: 2015-05-28 12:20 UTC by Mathias Homann
Modified: 2016-03-21 23:54 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (4.62 KB, text/plain)
2015-05-28 13:20 UTC, Mathias Homann
Details
New crash information added by DrKonqi (4.74 KB, text/plain)
2015-06-19 17:25 UTC, Matt Scheirer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mathias Homann 2015-05-28 12:20:54 UTC
Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.6
Qt Version: 4.8.6
Operating System: Linux 3.16.7-21-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Doing nothing in particular, I had just logged into KDE and was getting ready to do things. Akonadi was starting up, strangely enough only this one instance crashed, the other imap ressources are working fine.

- Unusual behavior I noticed:
nothing unusual.

The crash can be reproduced every time.

-- Backtrace:
Application: lemmy@megatokyo.de vom Typ 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 0x7fe4740867c0 (LWP 7098))]

Thread 3 (Thread 0x7fe460ba4700 (LWP 7100)):
#0  0x00007fff2b911d18 in  ()
#1  0x0000000000000000 in  ()

Thread 2 (Thread 0x7fe45bfff700 (LWP 7689)):
#0  0x00007fe46f9fac5d in poll () at /lib64/libc.so.6
#1  0x00007fe46e982be4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fe46e982cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007fe4736dc0de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#4  0x00007fe4736ade6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#5  0x00007fe4736ae165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#6  0x00007fe4735ab0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x00007fe4735ad79f in  () at /usr/lib64/libQtCore.so.4
#8  0x00007fe46f0670a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007fe46fa0308d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fe4740867c0 (LWP 7098)):
[KCrash Handler]
#5  0x00007fe47131764d in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () at /usr/lib64/libkimap.so.4
#6  0x00007fe471307ddc in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () at /usr/lib64/libkimap.so.4
#7  0x00007fe4736c759e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4
#8  0x00007fe472a4876c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#9  0x00007fe472a4ecad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#10 0x00007fe470b5ecea in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5
#11 0x00007fe4736af2ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4
#12 0x00007fe4736b257d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#13 0x00007fe4736dc8fe in  () at /usr/lib64/libQtCore.so.4
#14 0x00007fe46e982a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#15 0x00007fe46e982c48 in  () at /usr/lib64/libglib-2.0.so.0
#16 0x00007fe46e982cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#17 0x00007fe4736dc0be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#18 0x00007fe472ae5676 in  () at /usr/lib64/libQtGui.so.4
#19 0x00007fe4736ade6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#20 0x00007fe4736ae165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#21 0x00007fe4736b35b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4
#22 0x00007fe473b99283 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () at /usr/lib64/libakonadi-kde.so.4
#23 0x0000000000419f53 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 348319.

Possible duplicates by query: bug 348319, bug 345748, bug 345229, bug 344828, bug 344805.

Reported using DrKonqi
Comment 1 Mathias Homann 2015-05-28 13:20:45 UTC
Created attachment 92888 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.14) on KDE Platform 4.14.6 using Qt 4.8.6

the imap ressource keeps crashing, but it is the only one that does that. I have several other imap accounts in akonadi all on the same server that work fine. I have already run a reconstruct on the imap server, didn't help.

-- Backtrace (Reduced):
#5  0x00007f276f1c564d in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () at /usr/lib64/libkimap.so.4
#6  0x00007f276f1b5ddc in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () at /usr/lib64/libkimap.so.4
#7  0x00007f277157559e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4
#8  0x00007f27708f676c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#9  0x00007f27708fccad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
Comment 2 Matt Scheirer 2015-06-19 17:25:29 UTC
Created attachment 93238 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.14) on KDE Platform 4.14.9 using Qt 4.8.7

- What I was doing when the application crashed:

Whenever kmail tries to refresh the inbox, it segfaults on the response. Its only on imap responses - I can send smtp messages from the account fine. It was working fine yesterday, and I would not be surprised if it worked again after a reboot or after readding the imap info.

- Custom settings of the application:

Disabling interval checking stops the constant crashing, but opening the inbox still auto-updates it and crashes the resource.

-- Backtrace (Reduced):
#6  0x00007f7dc19038e5 in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () from /usr/lib/libkimap.so.4
#7  0x00007f7dc18f2a6e in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () from /usr/lib/libkimap.so.4
#8  0x00007f7dc2bd4bc1 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#9  0x00007f7dc1f0513c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#10 0x00007f7dc1f0bf96 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
Comment 3 Daniel Vrátil 2016-03-21 23:54:05 UTC

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