[Bug 302381] Kmail consistent crash on first launch of day or after reboot
https://bugs.kde.org/show_bug.cgi?id=302381 Thorsteinn A. Malmjursson changed: What|Removed |Added Summary|Kmail consistent crash on |Kmail consistent crash on |first launch of day |first launch of day or ||after reboot -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 302381] New: Kmail consistent crash on first launch of day
https://bugs.kde.org/show_bug.cgi?id=302381 Bug ID: 302381 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail consistent crash on first launch of day Classification: Unclassified OS: Linux Reporter: lightningstrik...@live.nl Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.1 Operating System: Linux 3.2.0-26-generic i686 Distribution: Ubuntu 12.04 LTS -- Information about the crash: I have seen many bugs on here which look similar and may (or may not) be the same as this one, but there is one added little trigger which I have a feeling might help. This only happens to me when kmail is opened for the *first* time each day, or after I have rebooted during the day. Other sessions once the machine is switched on and kmail is accessed for the first time, function perfectly well. It is not just deleting objects either, it can be triggered by ANY function within kmail, from reading an email to clicking on a subfolder of your inbox to view its contents, emptying your wastebin, clicking on the top menu bar, whatever. However, this is now getting serious as there are an increasingly large number of reports since 4.8.2 coming out of these types of crashes. Attention would be welcomed :) The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb5dbf740 (LWP 3615))] Thread 4 (Thread 0xb3cc1b40 (LWP 3619)): #0 0x00e12416 in __kernel_vsyscall () #1 0x01a3c96b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x041a73dc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb6ff2263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb6ff237f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0x01a38d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0x04199ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xb3398b40 (LWP 3620)): #0 0x01efb3d0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0x01ebb6b6 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0x01ebbfaf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x01ebc201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x00c008e7 in QEventDispatcherGlib::processEvents (this=0xb2a00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x00bcc50d in QEventLoop::processEvents (this=0xb3398270, flags=...) at kernel/qeventloop.cpp:149 #6 0x00bcc7a9 in QEventLoop::exec (this=0xb3398270, flags=...) at kernel/qeventloop.cpp:204 #7 0x00ab594c in QThread::exec (this=0x918a940) at thread/qthread.cpp:501 #8 0x00ab5a3b in QThread::run (this=0x918a940) at thread/qthread.cpp:568 #9 0x00ab8de0 in QThreadPrivate::start (arg=0x918a940) at thread/qthread_unix.cpp:298 #10 0x01a38d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #11 0x04199ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xb18ffb40 (LWP 3623)): #0 0x00a98287 in __i686.get_pc_thunk.bx () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #1 0x00c0004c in postEventSourcePrepare (s=0x9431ae0, timeout=0xb18ff0bc) at kernel/qeventdispatcher_glib.cpp:255 #2 0x01ebb872 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x01ebbfaf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x01ebc201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x00c008e7 in QEventDispatcherGlib::processEvents (this=0x9433be0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x00bcc50d in QEventLoop::processEvents (this=0xb18ff240, flags=...) at kernel/qeventloop.cpp:149 #7 0x00bcc7a9 in QEventLoop::exec (this=0xb18ff240, flags=...) at kernel/qeventloop.cpp:204 #8 0x00ab594c in QThread::exec (this=0x94ed5b8) at thread/qthread.cpp:501 #9 0x00ba9b5d in QInotifyFileSystemWatcherEngine::run (this=0x94ed5b8) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x00ab8de0 in QThreadPrivate::start (arg=0x94ed5b8) at thread/qthread_unix.cpp:298 #11 0x01a38d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0x04199ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb5dbf740 (LWP 3615)): [KCrash Handler] #7 0x07af121d in QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x998ee58, hm=, sc=0, rp=, pu=240, db=..., contentLength=-4165406276) at access/qnetworkaccesshttpbackend.cpp:827 #8 0x07b8837d in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x998ee58, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xb2a26f40) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #9 0x00bdfc01 in QMetaCallEvent::placeMeta
[Bug 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 --- Comment #135 from Thorsteinn A. Malmjursson --- Created attachment 70541 --> https://bugs.kde.org/attachment.cgi?id=70541&action=edit New crash information added by DrKonqi kmail (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1 - What I was doing when the application crashed: I was deleting a large number of mails from kmail installation, as I clicked the move to wastebin button, the application died. -- Backtrace (Reduced): #7 QNetworkAccessHttpBackend::replyDownloadMetaData (this=0xa2e37c0, hm=, sc=49, rp=, pu=116, db=, contentLength=-4198956612) at access/qnetworkaccesshttpbackend.cpp:827 #8 0x05b8937d in QNetworkAccessHttpBackend::qt_static_metacall (_o=0xa2e37c0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xb2b30c28) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 [...] #10 0x00bcfc7b in QObject::event (this=0xa2e37c0, e=0xb2b1a928) at kernel/qobject.cpp:1195 #11 0x00ed2ed4 in notify_helper (e=0xb2b1a928, receiver=0xa2e37c0, this=0x9c66cb0) at kernel/qapplication.cpp:4559 #12 QApplicationPrivate::notify_helper (this=0x9c66cb0, receiver=0xa2e37c0, e=0xb2b1a928) at kernel/qapplication.cpp:4531 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 Thorsteinn A. Malmjursson changed: What|Removed |Added CC||lightningstrik...@live.nl -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 297606] New: Kmail crashed on startup
https://bugs.kde.org/show_bug.cgi?id=297606 Bug ID: 297606 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crashed on startup Classification: Unclassified OS: Linux Reporter: lightningstrik...@live.nl Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.0.0-18-generic i686 Distribution: Ubuntu precise (development branch) -- Information about the crash: - What I was doing when the application crashed: I clicked on Kmail from the launch menu, and had literally just managed to get it to open, and without displaying any email whatsoever, it dropped out with Signal 11. I have tried more than once to open to get my mail, the same event doesn't always occur, but it has repeated on 3 more occasions. - Unusual behavior I noticed: Kmail froze during opening, and I was unable to click any buttons on the interface. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb5db6740 (LWP 11605))] Thread 6 (Thread 0xb3ce0b40 (LWP 11609)): #0 0x00d8f416 in __kernel_vsyscall () #1 0x00d6296b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x08b863dc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb6fe9263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb6fe937f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0x00d5ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0x08b78ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 5 (Thread 0xb33b7b40 (LWP 11610)): #0 0x02c36056 in postEventSourcePrepare (s=0xb2a00da8, timeout=0xb33b70ec) at kernel/qeventdispatcher_glib.cpp:255 #1 0x01d3d762 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0x01d3df6f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x01d3e1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x02c368e7 in QEventDispatcherGlib::processEvents (this=0xb2a00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x02c0250d in QEventLoop::processEvents (this=0xb33b7270, flags=...) at kernel/qeventloop.cpp:149 #6 0x02c027a9 in QEventLoop::exec (this=0xb33b7270, flags=...) at kernel/qeventloop.cpp:204 #7 0x02aeb94c in QThread::exec (this=0x97119b8) at thread/qthread.cpp:501 #8 0x02aeba3b in QThread::run (this=0x97119b8) at thread/qthread.cpp:568 #9 0x02aeede0 in QThreadPrivate::start (arg=0x97119b8) at thread/qthread_unix.cpp:298 #10 0x00d5ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #11 0x08b78ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 4 (Thread 0xb10feb40 (LWP 11615)): #0 0x08b86619 in pthread_mutex_unlock () from /lib/i386-linux-gnu/libc.so.6 #1 0x01d7d420 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0x01d3df10 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x01d3e1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x02c368e7 in QEventDispatcherGlib::processEvents (this=0xb1c059c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x02c0250d in QEventLoop::processEvents (this=0xb10fe240, flags=...) at kernel/qeventloop.cpp:149 #6 0x02c027a9 in QEventLoop::exec (this=0xb10fe240, flags=...) at kernel/qeventloop.cpp:204 #7 0x02aeb94c in QThread::exec (this=0x9abfed0) at thread/qthread.cpp:501 #8 0x02bdfb5d in QInotifyFileSystemWatcherEngine::run (this=0x9abfed0) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x02aeede0 in QThreadPrivate::start (arg=0x9abfed0) at thread/qthread_unix.cpp:298 #10 0x00d5ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #11 0x08b78ace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xb08fdb40 (LWP 11616)): #0 0x00d8f416 in __kernel_vsyscall () #1 0x08b6817b in read () from /lib/i386-linux-gnu/libc.so.6 #2 0x01d7c6be in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x01d3daf0 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x01d3e002 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x01d3e1c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0x02c368e7 in QEventDispatcherGlib::processEvents (this=0xb2a0f840, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x02c0250d in QEventLoop::processEvents (this=0xb08fd270, flags=...) at kernel/qeventloop.cpp:149 #8 0x02c027a9 in QEventLoop::exec (this=0xb08fd270, flags=...) at kernel/qeventloop.cpp:204 #9 0x02aeb94c in QThread::exec (this=0x9bec518) at thread/qthread.cpp:501 #10 0x02aeba3b in QThread::run (this=0x9bec518) at thread/qthread.c
[Bug 292284] Kmail closed while trying to receive mail from pop server
https://bugs.kde.org/show_bug.cgi?id=292284 --- Comment #2 from Thorsteinn A. Malmjursson 2012-01-23 21:09:32 --- Occasionally, Laurent, one out of every 7 or 8 opens results in this happening. It's not all of the time, but happens some of it. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 292284] New: Kmail closed while trying to receive mail from pop server
https://bugs.kde.org/show_bug.cgi?id=292284 Summary: Kmail closed while trying to receive mail from pop server Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: lightningstrik...@live.nl Application: kmail (4.7.3) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-15-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: I had just completed a mail check, and clicked on the first of the emails I'd received to open it - 2 or 3 windows opened concurrently, kmail hung and died. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0xb6144730 (LWP 12301))] Thread 4 (Thread 0xb5003b70 (LWP 12307)): #0 0x005e2416 in __kernel_vsyscall () #1 0x08875a5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x00cddcfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb7182883 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb718299f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0x08871d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0x00cd00ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 3 (Thread 0xb46dab70 (LWP 12308)): #0 0x08873dbd in pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0 #1 0x00cddf14 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6 #2 0x01ffd933 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x01ffdc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x0358cb37 in QEventDispatcherGlib::processEvents (this=0x9e56708, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x0355d1dd in QEventLoop::processEvents (this=0xb46da2c0, flags=...) at kernel/qeventloop.cpp:149 #6 0x0355d421 in QEventLoop::exec (this=0xb46da2c0, flags=...) at kernel/qeventloop.cpp:201 #7 0x0346090b in QThread::exec (this=0x9e55d90) at thread/qthread.cpp:498 #8 0x034609fb in QThread::run (this=0x9e55d90) at thread/qthread.cpp:565 #9 0x034637b3 in QThreadPrivate::start (arg=0x9e55d90) at thread/qthread_unix.cpp:331 #10 0x08871d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #11 0x00cd00ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 2 (Thread 0xb2c14b70 (LWP 12309)): #0 0x005e2416 in __kernel_vsyscall () #1 0x00cc140e in poll () from /lib/i386-linux-gnu/libc.so.6 #2 0x0200c34b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x01ffd896 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x01ffdc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x0358cb37 in QEventDispatcherGlib::processEvents (this=0x9ec8188, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x0355d1dd in QEventLoop::processEvents (this=0xb2c14290, flags=...) at kernel/qeventloop.cpp:149 #7 0x0355d421 in QEventLoop::exec (this=0xb2c14290, flags=...) at kernel/qeventloop.cpp:201 #8 0x0346090b in QThread::exec (this=0x9e6b0f8) at thread/qthread.cpp:498 #9 0x0353de2d in QInotifyFileSystemWatcherEngine::run (this=0x9e6b0f8) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x034637b3 in QThreadPrivate::start (arg=0x9e6b0f8) at thread/qthread_unix.cpp:331 #11 0x08871d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0x00cd00ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb6144730 (LWP 12301)): [KCrash Handler] #7 0x0355d2f7 in data (this=0x4) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135 #8 qGetPtrHelper > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2343 #9 d_func (this=0x0) at ../../include/QtCore/../../src/corelib/kernel/qeventloop.h:58 #10 QEventLoop::exit (this=0x0, returnCode=0) at kernel/qeventloop.cpp:279 #11 0x00fbb5fc in QDragManager::eventFilter (this=0xa299360, o=0xa28ff00, e=0xbf9ad80c) at kernel/qdnd_x11.cpp:1333 #12 0x0355e26b in QCoreApplicationPrivate::sendThroughApplicationEventFilters (this=0x9a68b40, receiver=0xa28ff00, event=0xbf9ad80c) at kernel/qcoreapplication.cpp:883 #13 0x00f1ecfa in QApplicationPrivate::notify_helper (this=0x9a68b40, receiver=0xa28ff00, e=0xbf9ad80c) at kernel/qapplication.cpp:4461 #14 0x00f24deb in QApplication::notify (this=0x9a68b40, receiver=0xa28ff00, e=0xbf9ad80c) at kernel/qapplication.cpp:4047 #15 0x002f7971 in KApplication::notify (this=0xbf9af19c, receiver=0xa28ff00, event=0xbf9ad80c) at ../../kdeui/kernel/kapplication.cpp:311 #16 0x0355e19e in QCoreApp
[Bug 284132] New: kmail-migrator did not migrate from the command line, and refuses to migrate kmailrc if repeated
https://bugs.kde.org/show_bug.cgi?id=284132 Summary: kmail-migrator did not migrate from the command line, and refuses to migrate kmailrc if repeated Product: kmail2 Version: 4.7 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: lightningstrik...@live.nl Version: 4.7 (using KDE 4.7.2) OS:Linux First time out using kmail2, i followed the instructions for the migration of kmailrc to the new version. Upon getting kmail2 open after some technical issues involving nepomuk, i discovered that absolutely nothing from the kmailrc had migrated. I had empty folders, no mails, no account settings, nothing. I tried to repeat the process only to be told that: kmail-migrator(4345) main: Migration of kmailrc has already run, not running it again The result of this being that I had to completely setup kmail2 from scratch, and I've had to remember all my passwords, account settings, etc in order to do this. Reproducible: Always Steps to Reproduce: migrate to kmail2 using kmail-migrator --interactive if it fails to migrate, try again. error message shown in the bug above is received Actual Results: nothing, migration did not work Expected Results: migration to kmail2 should have been completed automatically following the initial step. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
