Bug 328101 - kmail crash during no desktop interaction
Summary: kmail crash during no desktop interaction
Status: RESOLVED DUPLICATE of bug 314123
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.11.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-11-26 09:55 UTC by Bruno Friedmann
Modified: 2013-12-22 03:34 UTC (History)
1 user (show)

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


Attachments
New crash information added by DrKonqi (4.84 KB, text/plain)
2013-11-27 09:20 UTC, Bruno Friedmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Friedmann 2013-11-26 09:55:19 UTC
Application: kmail (4.11.3)
KDE Platform Version: 4.11.3
Qt Version: 4.8.5
Operating System: Linux 3.12.0-1.ge8fa6b4-desktop x86_64
Distribution: "openSUSE 12.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I was afk during 18 minutes, the display has been dim down (but not locked)

During that time, knotify show 5 new messages, and a warning about one of the 11 imap connection lost ( 10 of the imap account are on the same server (dovecot 2.0) so 1/10 connection was considered faulty)

My connection at that time was with Wifi (long time not use it), but no connection was interupted, or dhcp release etc ...

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f375a80e780 (LWP 10800))]

Thread 4 (Thread 0x7f3737595700 (LWP 11014)):
#0  0x00007f37559b5964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f374b6c1770 in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f374b6c17a9 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x00007f37559b1e0f in start_thread () from /lib64/libpthread.so.0
#4  0x00007f3757b7d44d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f3736404700 (LWP 11015)):
#0  0x00007f37559b5964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f374b43df47 in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f374b6e8c9e in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x00007f37559b1e0f in start_thread () from /lib64/libpthread.so.0
#4  0x00007f3757b7d44d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f3734da4700 (LWP 11017)):
[KCrash Handler]
#6  0x00007f3757ac93d5 in raise () from /lib64/libc.so.6
#7  0x00007f3757aca858 in abort () from /lib64/libc.so.6
#8  0x00007f3757b0944b in __libc_message () from /lib64/libc.so.6
#9  0x00007f3757b0efc6 in malloc_printerr () from /lib64/libc.so.6
#10 0x00007f3757b0fd43 in _int_free () from /lib64/libc.so.6
#11 0x00007f37590e17f8 in QString::free (d=0x11b5630) at tools/qstring.cpp:1235
#12 0x00007f3755bf6e49 in ~QString (this=0x13e9400, __in_chrg=<optimized out>) at ../../src/corelib/tools/qstring.h:880
#13 QDBusMessagePrivate::~QDBusMessagePrivate (this=0x13e93e0, __in_chrg=<optimized out>) at qdbusmessage.cpp:72
#14 0x00007f3755bf6f5f in QDBusMessage::~QDBusMessage (this=0x2a30, __in_chrg=<optimized out>) at qdbusmessage.cpp:537
#15 0x00007f3755bf2a0d in ~QDBusCallDeliveryEvent (this=0x11a6ff0, __in_chrg=<optimized out>) at qdbusintegrator_p.h:93
#16 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0x11a6ff0, __in_chrg=<optimized out>) at qdbusintegrator_p.h:93
#17 0x00007f37591978aa in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x12f1590) at kernel/qcoreapplication.cpp:1589
#18 0x00007f37591c2423 in sendPostedEvents () at kernel/qcoreapplication.h:236
#19 postEventSourceDispatch (s=0x7f36e40012d0) at kernel/qeventdispatcher_glib.cpp:280
#20 0x00007f374f8847d5 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f374f884b08 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f374f884bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f37591c25b6 in QEventDispatcherGlib::processEvents (this=0x7f36e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#24 0x00007f3759192bef in QEventLoop::processEvents (this=this@entry=0x7f3734da3e00, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f3759192e78 in QEventLoop::exec (this=0x7f3734da3e00, flags=...) at kernel/qeventloop.cpp:204
#26 0x00007f3759095110 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:536
#27 0x00007f37590980ec in QThreadPrivate::start (arg=0xff64a0) at thread/qthread_unix.cpp:338
#28 0x00007f37559b1e0f in start_thread () from /lib64/libpthread.so.0
#29 0x00007f3757b7d44d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f375a80e780 (LWP 10800)):
#0  0x00007f3757b705ed in read () from /lib64/libc.so.6
#1  0x00007f374f8c0e0f in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f374f884634 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f374f884a42 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x00007f374f884bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#5  0x00007f37591c25d6 in QEventDispatcherGlib::processEvents (this=0xc74a70, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#6  0x00007f37585dce0e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#7  0x00007f3759192bef in QEventLoop::processEvents (this=this@entry=0x7fffd7066d70, flags=...) at kernel/qeventloop.cpp:149
#8  0x00007f3759192e78 in QEventLoop::exec (this=0x7fffd7066d70, flags=...) at kernel/qeventloop.cpp:204
#9  0x00007f3759197bb8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#10 0x0000000000402f1e in ?? ()
#11 0x00007f3757ab5a15 in __libc_start_main () from /lib64/libc.so.6
#12 0x0000000000403415 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 327724, bug 314123.

Possible duplicates by query: bug 327724, bug 324776, bug 316768, bug 315381, bug 314123.

Reported using DrKonqi
Comment 1 Bruno Friedmann 2013-11-27 09:20:07 UTC
Created attachment 83787 [details]
New crash information added by DrKonqi

kmail (4.11.3) on KDE Platform 4.11.3 using Qt 4.8.5

- What I was doing when the application crashed: This time I was working with the desktop but not in kmail.
No notifications, but still connected by wifi. 
During the whole night connected to wired network, there's was not crash
????

-- Backtrace (Reduced):
#11 0x00007f11c1d5f7f8 in QString::free (d=0x1ca21d0) at tools/qstring.cpp:1235
#12 0x00007f11be874e49 in ~QString (this=0xecff5a0, __in_chrg=<optimized out>) at ../../src/corelib/tools/qstring.h:880
#13 QDBusMessagePrivate::~QDBusMessagePrivate (this=0xecff580, __in_chrg=<optimized out>) at qdbusmessage.cpp:72
#14 0x00007f11be874f5f in QDBusMessage::~QDBusMessage (this=0x52cd, __in_chrg=<optimized out>) at qdbusmessage.cpp:537
#15 0x00007f11be870a0d in ~QDBusCallDeliveryEvent (this=0xdd55590, __in_chrg=<optimized out>) at qdbusintegrator_p.h:93
Comment 2 Jekyll Wu 2013-12-22 03:34:57 UTC

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