[Bug 295656] New: Kmail crashes when deleting (moving to trash) e-mails
https://bugs.kde.org/show_bug.cgi?id=295656 Bug ID: 295656 Severity: grave Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crashes when deleting (moving to trash) e-mails Classification: Unclassified OS: Linux Reporter: sti...@att.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: commands and actions Product: kmail2 Created attachment 69444 -- https://bugs.kde.org/attachment.cgi?id=69444action=edit Backtrace KMail crashes when I delete emails. Although I didn't find a reliable scenario which leads to a crash, I noted that changing the order in which emails are deleted sometime makes KMail succeed in deleting. E.g., if deleting emai A crashes KMail, then deleting email B and then email A sometimes would succeed. The backtrace is attached. It is probably different issue from the bug 295589 - different signal (SIGSEGV vs SIGABRT), and backtraces look different. -- 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 295656] Kmail crashes when deleting (moving to trash) e-mails
https://bugs.kde.org/show_bug.cgi?id=295656 --- Comment #1 from Alexey Neyman sti...@att.net --- I wish DrKonqi would be able to submit all the information automatically, but it currently cannot log in to bugs.kde.org. -- 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 293883] GroupDav addressbook from egroupware cancels with Unbekannter Fehler. (Unable to fetch item from backend)
https://bugs.kde.org/show_bug.cgi?id=293883 --- Comment #3 from Marcello Ceschia marce...@ceschia.de --- The problem is not solved on my side, but there are some curiosities. The installed packages have version number 4.8.1-327.1 but about kontact lists version 4.8.0, is I'm not realy sure what version this is -- 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 293883] GroupDav addressbook from egroupware cancels with Unbekannter Fehler. (Unable to fetch item from backend)
https://bugs.kde.org/show_bug.cgi?id=293883 --- Comment #4 from Grégory Oestreicher g...@kamago.net --- Hi Marcelo, Can you check the version of the kdepim-runtime package? I've just check in Kontact sources and the version apparently was not bumped when 4.8.1 was released. Cheers, Grégory -- 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 295657] New: Random crashes independent from specific action
https://bugs.kde.org/show_bug.cgi?id=295657 Bug ID: 295657 Severity: crash Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Random crashes independent from specific action Classification: Unclassified OS: Linux Reporter: f...@christian-reiner.info Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kmail2 Created attachment 69445 -- https://bugs.kde.org/attachment.cgi?id=69445action=edit kcrash backtrace I experience random crashes in Kmail2. The crashes started after upgrading to KDE-4.8 and still happen under KDE-4.8.1. There is no specific action I can relate to the crashes, they seem to be triggered by something in background, independent of user interaction. I would say KMail2 roughly crashes in average after about 5 minutes after being launched. Not exactly reproducable, but randomly again and again. -- 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 295474] kmail 4.8.1 crashes all the time
https://bugs.kde.org/show_bug.cgi?id=295474 --- Comment #12 from Peter peteros...@gmx.net --- Created attachment 69447 -- https://bugs.kde.org/attachment.cgi?id=69447action=edit crash report -- 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 295474] kmail 4.8.1 crashes all the time
https://bugs.kde.org/show_bug.cgi?id=295474 Peter peteros...@gmx.net changed: What|Removed |Added CC||peteros...@gmx.net -- 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 295659] New: kmail stalls from time to time since update to 4.8.1
https://bugs.kde.org/show_bug.cgi?id=295659 Bug ID: 295659 Severity: normal Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail stalls from time to time since update to 4.8.1 Classification: Unclassified OS: Linux Reporter: sven.burmeis...@gmx.net Hardware: Other Status: UNCONFIRMED Component: general Product: kmail2 Since 4.8.1 kmail from time to time just stalls. None of the UI buttons accept any clicks. It does not use any CPU, it does not crash, it is just dead forever. I attached gdb to that process and got: (gdb) bt #0 0x7fd0ecc73209 in syscall () from /lib64/libc.so.6 #1 0x7fd0ee1a602b in _q_futex (val2=0, addr2=0x0, timeout=0x0, val=2, op=0, addr=0x7fd07c028d40) at thread/qmutex_unix.cpp:99 #2 QMutexPrivate::wait (this=0x7fd07c028d40, timeout=optimized out) at thread/qmutex_unix.cpp:113 #3 0x7fd0ee1a1ded in QMutex::lockInternal (this=optimized out) at thread/qmutex.cpp:450 #4 0x7fd0eacb5558 in lockInline (this=0x7fd07c0254a0) at ../../src/corelib/thread/qmutex.h:190 #5 QMutexLocker (m=0x7fd07c0254a0, this=synthetic pointer) at ../../src/corelib/thread/qmutex.h:109 #6 QDBusConnectionPrivate::processFinishedCall (call=0x7fd07c025470) at qdbusintegrator.cpp:1789 #7 0x7fd0e3649e5a in complete_pending_call_and_unlock (connection=0x64d860, pending=0x7fd07c028930, message=optimized out) at dbus-connection.c:2304 #8 0x7fd0e364cfd3 in dbus_connection_dispatch (connection=0x64d860) at dbus-connection.c:4552 #9 0x7fd0eacb3379 in q_dbus_connection_dispatch (connection=optimized out) at qdbus_symbols_p.h:115 #10 QDBusConnectionPrivate::doDispatch (this=0x64cae0) at qdbusintegrator.cpp:1129 #11 0x7fd0eacb7345 in QDBusConnectionPrivate::socketRead (this=0x64cae0, fd=optimized out) at qdbusintegrator.cpp:1149 #12 0x7fd0ee2b8761 in QMetaObject::activate (sender=0xad8420, m=optimized out, local_signal_index=optimized out, argv=0x7fff84791ae0) at kernel/qobject.cpp:3556 #13 0x7fd0ee305c6e in QSocketNotifier::activated (this=optimized out, _t1=5) at .moc/release-shared/moc_qsocketnotifier.cpp:103 #14 0x7fd0ee2c1aeb in QSocketNotifier::event (this=0xad8420, e=0x7fff84792150) at kernel/qsocketnotifier.cpp:317 #15 0x7fd0ed629e84 in notify_helper (e=0x7fff84792150, receiver=0xad8420, this=0x662510) at kernel/qapplication.cpp:4550 #16 QApplicationPrivate::notify_helper (this=0x662510, receiver=0xad8420, e=0x7fff84792150) at kernel/qapplication.cpp:4522 #17 0x7fd0ed62ed03 in QApplication::notify (this=0x7fff847924b0, receiver=0xad8420, e=0x7fff84792150) at kernel/qapplication.cpp:4411 #18 0x7fd0ef353656 in KApplication::notify (this=0x7fff847924b0, receiver=0xad8420, event=0x7fff84792150) at /usr/src/debug/kdelibs-4.8.1/kdeui/kernel/kapplication.cpp:311 #19 0x7fd0ee2a489c in QCoreApplication::notifyInternal (this=0x7fff847924b0, receiver=0xad8420, event=0x7fff84792150) at kernel/qcoreapplication.cpp:876 #20 0x7fd0ee2d2f47 in sendEvent (event=0x7fff84792150, receiver=optimized out) at kernel/qcoreapplication.h:231 #21 socketNotifierSourceDispatch (source=0x664d90) at kernel/qeventdispatcher_glib.cpp:110 #22 0x7fd0e4e5658d in g_main_dispatch (context=0x664c20) at gmain.c:2425 #23 g_main_context_dispatch (context=0x664c20) at gmain.c:2995 #24 0x7fd0e4e56d88 in g_main_context_iterate (context=0x664c20, block=optimized out, dispatch=1, self=optimized out) at gmain.c:3073 #25 0x7fd0e4e56f59 in g_main_context_iteration (context=0x664c20, may_block=1) at gmain.c:3136 #26 0x7fd0ee2d38ef in QEventDispatcherGlib::processEvents (this=0x60b000, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #27 0x7fd0ed6cd2de in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #28 0x7fd0ee2a3682 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #29 0x7fd0ee2a38d7 in QEventLoop::exec (this=0x7fff84792390, flags=...) at kernel/qeventloop.cpp:204 #30 0x7fd0ee2a8435 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #31 0x00402df3 in main (argc=optimized out, argv=optimized out) at /usr/src/debug/kdepim-4.8.1/kmail/main.cpp:145 -- 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 273667] KMail crashes
https://bugs.kde.org/show_bug.cgi?id=273667 Peter peteros...@gmx.net changed: What|Removed |Added CC||peteros...@gmx.net -- 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 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 Thomas Beinicke merlin...@web.de changed: What|Removed |Added CC||merlin...@web.de -- 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 294441] kmail stays in offline mode, unable to send emails
https://bugs.kde.org/show_bug.cgi?id=294441 Robert Stetka robert.ste...@gmail.com changed: What|Removed |Added CC||robert.ste...@gmail.com -- 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 293883] GroupDav addressbook from egroupware cancels with Unbekannter Fehler. (Unable to fetch item from backend)
https://bugs.kde.org/show_bug.cgi?id=293883 --- Comment #5 from Marcello Ceschia marce...@ceschia.de --- Hello Grégory, thank you for you quick response. I reinstalled all kde packages from kde 4.8 repository to make sure that there ar no old version installed. The kdepim4-runtime package has version 4.8.1-128.2. Just need to mention that calendar entries from egroupware works as expected, only addressbook is the problem -- 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 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=193514 Markus S. kamika...@web.de changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #197 from Markus S. kamika...@web.de --- Not fixed. Here the backtrace of 4.8.1: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb2689710 (LWP 2381))] Thread 4 (Thread 0xb1479b70 (LWP 2382)): #0 0xb3d04782 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0xb61503ac in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6 #2 0xb5904189 in ?? () from /usr/lib/libQtWebKit.so.4 #3 0xb59041cf in ?? () from /usr/lib/libQtWebKit.so.4 #4 0xb3d00a7d in start_thread () from /lib/libpthread.so.0 #5 0xb614289e in clone () from /lib/libc.so.6 Thread 3 (Thread 0xb0b51b70 (LWP 2383)): #0 0xb3d03a74 in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0 #1 0xb6150604 in pthread_mutex_unlock () from /lib/libc.so.6 #2 0xb3c1943f in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #3 0xb3c1a207 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb3c1a7fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb647c5a7 in QEventDispatcherGlib::processEvents (this=0xb0200468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0xb644840d in QEventLoop::processEvents (this=0xb0b512d0, flags=...) at kernel/qeventloop.cpp:149 #7 0xb64486a9 in QEventLoop::exec (this=0xb0b512d0, flags=...) at kernel/qeventloop.cpp:204 #8 0xb6332d0c in QThread::exec (this=0x8163268) at thread/qthread.cpp:501 #9 0xb6332dfb in QThread::run (this=0x8163268) at thread/qthread.cpp:568 #10 0xb63361f0 in QThreadPrivate::start (arg=0x8163268) at thread/qthread_unix.cpp:298 #11 0xb3d00a7d in start_thread () from /lib/libpthread.so.0 #12 0xb614289e in clone () from /lib/libc.so.6 Thread 2 (Thread 0xaea61b70 (LWP 3672)): #0 0xb3d02ae6 in pthread_mutex_lock () from /lib/libpthread.so.0 #1 0xb61505c4 in pthread_mutex_lock () from /lib/libc.so.6 #2 0xb3c18cd7 in g_main_context_release () from /usr/lib/libglib-2.0.so.0 #3 0xb3c1a4d6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb3c1a7fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb647c5a7 in QEventDispatcherGlib::processEvents (this=0xae100468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0xb644840d in QEventLoop::processEvents (this=0xaea612a0, flags=...) at kernel/qeventloop.cpp:149 #7 0xb64486a9 in QEventLoop::exec (this=0xaea612a0, flags=...) at kernel/qeventloop.cpp:204 #8 0xb6332d0c in QThread::exec (this=0x9c5b6e8) at thread/qthread.cpp:501 #9 0xb642597d in QInotifyFileSystemWatcherEngine::run (this=0x9c5b6e8) at io/qfilesystemwatcher_inotify.cpp:248 #10 0xb63361f0 in QThreadPrivate::start (arg=0x9c5b6e8) at thread/qthread_unix.cpp:298 #11 0xb3d00a7d in start_thread () from /lib/libpthread.so.0 #12 0xb614289e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb2689710 (LWP 2381)): [KCrash Handler] #6 QString (other=) at /usr/include/QtCore/qstring.h:725 #7 KontactInterface::Plugin::identifier (this=0x7468002f) at /usr/src/debug/kdepimlibs-4.8.1/kontactinterface/plugin.cpp:101 #8 0xb77fa050 in activateInitialPluginModule (this=0x81970e8) at /usr/src/debug/kdepim-4.8.1/kontact/src/mainwindow.cpp:320 #9 Kontact::MainWindow::activateInitialPluginModule (this=0x81970e8) at /usr/src/debug/kdepim-4.8.1/kontact/src/mainwindow.cpp:315 #10 0xb77fa145 in Kontact::MainWindow::setInitialActivePluginModule (this=0x81970e8, module=...) at /usr/src/debug/kdepim-4.8.1/kontact/src/mainwindow.cpp:297 #11 0x0804ba78 in KontactApp::newInstance (this=0xbfa41034) at /usr/src/debug/kdepim-4.8.1/kontact/src/main.cpp:147 #12 0xb756aa07 in KUniqueApplicationAdaptor::newInstance (this=0x81640d0, asn_id=..., args=...) at /usr/src/debug/kdelibs-4.8.1/kdeui/kernel/kuniqueapplication.cpp:442 #13 0xb756aab8 in qt_static_metacall (_a=0xbfa4060c, _id=0, _o=0x81640d0, _c=optimized out) at /usr/src/debug/kdelibs-4.8.1/build/kdeui/kuniqueapplication_p.moc:58 #14 KUniqueApplicationAdaptor::qt_static_metacall (_o=0x81640d0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfa4060c) at /usr/src/debug/kdelibs-4.8.1/build/kdeui/kuniqueapplication_p.moc:52 #15 0xb756ac2c in KUniqueApplicationAdaptor::qt_metacall (this=0x81640d0, _c=QMetaObject::InvokeMetaMethod, _id=optimized out, _a=0xbfa4060c) at /usr/src/debug/kdelibs-4.8.1/build/kdeui/kuniqueapplication_p.moc:102 #16 0xb449f610 in QDBusConnectionPrivate::deliverCall (this=0x806c248, object=0x81640d0, msg=..., metaTypes=..., slotIdx=-1079770252) at qdbusintegrator.cpp:947 #17 0xb44a08e0 in QDBusConnectionPrivate::activateCall (this=0x806c248, object=0x81640d0, flags=337, msg=...) at qdbusintegrator.cpp:857 #18 0xb44a10ab in QDBusConnectionPrivate::activateObject (this=0x806c248, node=..., msg=..., pathStartPos=-1079769248)
[Bug 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=193514 Markus S. kamika...@web.de changed: What|Removed |Added Version Fixed In|4.8.0 | -- 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 293883] GroupDav addressbook from egroupware cancels with Unbekannter Fehler. (Unable to fetch item from backend)
https://bugs.kde.org/show_bug.cgi?id=293883 --- Comment #6 from Grégory Oestreicher g...@kamago.net --- OK, I've checked the source of the OpenSUSE package and the fix I thought would address this issue is present. I'll try to reproduce this issue. Cheers, Grégory -- 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 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=193514 --- Comment #198 from Christophe Giboudeaux cgiboude...@gmx.com --- which(pim) applications are installed on your machine and which are enabled in kontact ? -- 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 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=193514 --- Comment #199 from Markus S. kamika...@web.de --- (In reply to comment #198) which(pim) applications are installed on your machine and which are enabled in kontact ? KMail, KOrganizer (rarely used), and Akregaror which seems to cause this -- as it has done before. That particular crash happened after I subscribed to a RSS feed by clicking on it in Firefox which first launched Akregator stand alone. Then after quitting Akregator, I launched Kontact to get this bug. Another bug report tied this crash to a fault in Metakit. It was closed as dupe of this bug. -- 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 295542] the local folders list is greyed out, but functional
https://bugs.kde.org/show_bug.cgi?id=295542 --- Comment #5 from m.eik michalke m...@reaktanz.de --- the problem is permanent. but actually, i don't even have to press ok when editing the resource to solve this (temporarily, until next login): - log in, then i have to wait about three minutes until akonadi (supposedly) finished starting all resources (feels a little like the XP desktop...) - start kmail, my local folders are greyed out as seen in the screenshot - start akonadi resource configuration - select the maildir resource: it still has a plug symbol, but says ready - click on edit - don't change a thing, click cancel the resource symbol changes to the green light immediately and folders are normally visible in kmail. -- 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 294320] kmail complains about the semantic destkop not running, when it is
https://bugs.kde.org/show_bug.cgi?id=294320 --- Comment #7 from Hugo Costelha hugo.coste...@gmail.com --- I checked with akonadiconsole and had a problem with the connection to google contacts. I reconfigured it and the problems was solved. -- 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 294320] kmail complains about the semantic destkop not running, when it is
https://bugs.kde.org/show_bug.cgi?id=294320 Hugo Costelha hugo.coste...@gmail.com changed: What|Removed |Added CC|hugo.coste...@gmail.com | -- 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 295675] New: Kmail2 crashes
https://bugs.kde.org/show_bug.cgi?id=295675 Bug ID: 295675 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail2 crashes Classification: Unclassified OS: Linux Reporter: peteros...@gmx.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 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-12-generic x86_64 Distribution: Linux Mint 12 KDE -- Information about the crash: kmail crashes when i try to start istagain and again The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7f17aa3507a0 (LWP 5730))] Thread 4 (Thread 0x7f178ab53700 (LWP 5735)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f179c610c2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f179c610d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f17a5268efc in start_thread (arg=0x7f178ab53700) at pthread_create.c:304 #4 0x7f17a76c459d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7f178a252700 (LWP 5736)): #0 0x7f17a526b034 in __pthread_mutex_lock (mutex=0x2bdae48) at pthread_mutex_lock.c:61 #1 0x7f17a0100f2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f17a0101429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f17a8036f3e in QEventDispatcherGlib::processEvents (this=0x2bda9a0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f17a800acf2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f17a800aef7 in QEventLoop::exec (this=0x7f178a251de0, flags=...) at kernel/qeventloop.cpp:201 #6 0x7f17a7f2227f in QThread::exec (this=optimized out) at thread/qthread.cpp:498 #7 0x7f17a7f24d05 in QThreadPrivate::start (arg=0x2bd99f0) at thread/qthread_unix.cpp:331 #8 0x7f17a5268efc in start_thread (arg=0x7f178a252700) at pthread_create.c:304 #9 0x7f17a76c459d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 2 (Thread 0x7f17423d5700 (LWP 5737)): #0 0x7f17a76b8473 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f17a0100f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f17a0101429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f17a8036f3e in QEventDispatcherGlib::processEvents (this=0x30217e0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f17a800acf2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f17a800aef7 in QEventLoop::exec (this=0x7f17423d4db0, flags=...) at kernel/qeventloop.cpp:201 #6 0x7f17a7f2227f in QThread::exec (this=optimized out) at thread/qthread.cpp:498 #7 0x7f17a7fedcbf in QInotifyFileSystemWatcherEngine::run (this=0x3020a60) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f17a7f24d05 in QThreadPrivate::start (arg=0x3020a60) at thread/qthread_unix.cpp:331 #9 0x7f17a5268efc in start_thread (arg=0x7f17423d5700) at pthread_create.c:304 #10 0x7f17a76c459d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f17aa3507a0 (LWP 5730)): [KCrash Handler] #6 isNull (this=0x7f17001c) at image/qpixmapdata_p.h:130 #7 QPixmap::isNull (this=0x2b5bbe8) at image/qpixmap.cpp:545 #8 0x7f17a8613439 in QPixmap::copy (this=0x2b5bbe8, rect=...) at image/qpixmap.cpp:356 #9 0x7f17a86146d0 in QPixmap::QPixmap (this=0x7fff95797210, pixmap=...) at image/qpixmap.cpp:277 #10 0x7f17a9dddb97 in KPixmapSequence::frameAt (this=0x2b548c0, index=1) at ../../kdeui/util/kpixmapsequence.cpp:143 #11 0x7f17a43ec7d0 in Akonadi::DelegateAnimator::sequenceFrame (this=0x2b548a0, index=...) at ../../akonadi/progressspinnerdelegate.cpp:60 #12 0x7f17a436f0d0 in Akonadi::CollectionStatisticsDelegate::initStyleOption (this=optimized out, option=0x7fff95797330, index=...) at ../../akonadi/collectionstatisticsdelegate.cpp:174 #13 0x7f17a8aed185 in QStyledItemDelegate::paint (this=0x2566d10, painter=0x7fff95797ef0, option=..., index=...) at itemviews/qstyleditemdelegate.cpp:425 #14 0x7f17a436cf34 in Akonadi::CollectionStatisticsDelegate::paint (this=0x2566d10, painter=0x7fff95797ef0, option=..., index=...) at ../../akonadi/collectionstatisticsdelegate.cpp:207 #15 0x7f17a8a85f7d in QTreeView::drawRow (this=0x2b2c460, painter=0x7fff95797ef0, option=..., index=...) at itemviews/qtreeview.cpp:1678 #16
[Bug 295676] New: kmail crash on compose new email
https://bugs.kde.org/show_bug.cgi?id=295676 Bug ID: 295676 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail crash on compose new email Classification: Unclassified OS: Linux Reporter: malte.ge...@googlemail.com Hardware: Ubuntu Packages Status: NEW Component: general Product: kmail2 Application: kmail (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-16-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: i started kmail instead of kontact, as kontact behaves extremly slow after upgrade to 4.8.1 with kubuntu backports 11.10 reading and moving mails worked, but when i clicked on New Mail button the application crashed - Unusual behavior I noticed: mysqld and virtuose-t process takes very much cpu. KDE at all seems very unstable after the upgrade to 4.8.1 The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7f89ff8c87c0 (LWP 16185))] Thread 5 (Thread 0x7f89f5f73700 (LWP 16213)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f8a096d4c2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f8a096d4d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f8a1434defc in start_thread (arg=0x7f89f5f73700) at pthread_create.c:304 #4 0x7f8a1464659d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f89f5672700 (LWP 16214)): #0 0x7f8a1463a473 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f8a17156240 in ?? () from /opt/lib/libmediaclient.so #2 0x7f8a17156a1d in poll () from /opt/lib/libmediaclient.so #3 0x7f8a0cdbdf68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8a0cdbe429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8a14fcbc06 in QEventDispatcherGlib::processEvents (this=0x15223a0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f8a14f9b3e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f8a14f9b637 in QEventLoop::exec (this=0x7f89f5671dc0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f8a14e9b067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7f8a14e9e08b in QThreadPrivate::start (arg=0x15218c0) at thread/qthread_unix.cpp:298 #10 0x7f8a1434defc in start_thread (arg=0x7f89f5672700) at pthread_create.c:304 #11 0x7f8a1464659d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 3 (Thread 0x7f89ae229700 (LWP 16252)): #0 0x7f8a1463a473 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f8a17156240 in ?? () from /opt/lib/libmediaclient.so #2 0x7f8a17156a1d in poll () from /opt/lib/libmediaclient.so #3 0x7f8a0cdbdf68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8a0cdbe429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8a14fcbc06 in QEventDispatcherGlib::processEvents (this=0x10af960, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f8a14f9b3e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f8a14f9b637 in QEventLoop::exec (this=0x7f89ae228d90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f8a14e9b067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7f8a14f7b17f in QInotifyFileSystemWatcherEngine::run (this=0x182a440) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7f8a14e9e08b in QThreadPrivate::start (arg=0x182a440) at thread/qthread_unix.cpp:298 #11 0x7f8a1434defc in start_thread (arg=0x7f89ae229700) at pthread_create.c:304 #12 0x7f8a1464659d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 2 (Thread 0x7f89a61fe700 (LWP 17514)): #0 0x7f8a1463a473 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f8a17156240 in ?? () from /opt/lib/libmediaclient.so #2 0x7f8a17156a1d in poll () from /opt/lib/libmediaclient.so #3 0x7f8a0cdbdf68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8a0cdbe429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8a14fcbc06 in QEventDispatcherGlib::processEvents (this=0x4c72220, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f8a14f9b3e2 in
[Bug 295638] Kmail crash just beginning to compose an email
https://bugs.kde.org/show_bug.cgi?id=295638 Galeffi Christian c...@gallochri.com changed: What|Removed |Added CC||c...@gallochri.com -- 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 295638] Kmail crash just beginning to compose an email
https://bugs.kde.org/show_bug.cgi?id=295638 --- Comment #1 from Galeffi Christian c...@gallochri.com --- Created attachment 69455 -- https://bugs.kde.org/attachment.cgi?id=69455action=edit New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) release 481 using Qt 4.8.0 - What I was doing when the application crashed: I Start to typing a mail, I happen on two different system with openSUSE 12.1 and KDE4.8.1 -- Backtrace (Reduced): #6 0x7f533d500553 in Sonnet::Highlighter::eventFilter(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #7 0x7f533bd4ea28 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #8 0x7f533c761e4f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #9 0x7f533c7673ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #10 0x7f533d4a6656 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 -- 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 295615] kmail crashed after hitting reply
https://bugs.kde.org/show_bug.cgi?id=295615 Markus m4rkus...@web.de changed: What|Removed |Added CC||m4rkus...@web.de --- Comment #1 from Markus m4rkus...@web.de --- I have the same(?) issue. When I hit reply, the composer opens and when I try to type it will crash with a segfault. backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7f8fefbac760 (LWP 5326))] Thread 5 (Thread 0x7f8fd4f8e700 (LWP 5402)): #0 0x7f8feacb264c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8fe19c41ac in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f8feacaddbc in start_thread () from /lib64/libpthread.so.0 #3 0x7f8fece59ded in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f8fd468d700 (LWP 5503)): #0 0x7f8fece50fb3 in poll () from /lib64/libc.so.6 #1 0x7f8fe573c554 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8fe573c9bf in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8fed7e4f96 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f8fed7b4cf2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x7f8fed7b4fe5 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7f8fed6b2888 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7f8fed6b4f67 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7f8feacaddbc in start_thread () from /lib64/libpthread.so.0 #9 0x7f8fece59ded in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f8fd2fdb700 (LWP 11764)): #0 0x7f8fece50fb3 in poll () from /lib64/libc.so.6 #1 0x7f8fe573c554 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8fe573c9bf in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8fed7e4f96 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f8fed7b4cf2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x7f8fed7b4fe5 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7f8fed6b2888 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7f8fed793b20 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7f8fed6b4f67 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #9 0x7f8feacaddbc in start_thread () from /lib64/libpthread.so.0 #10 0x7f8fece59ded in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f8f8ad47700 (LWP 1736)): #0 0x7f8feacb29cb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8fed6b5d7e in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4 #2 0x7f8fed6a93ff in ?? () from /usr/lib64/qt4/libQtCore.so.4 #3 0x7f8fed6b4f67 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f8feacaddbc in start_thread () from /lib64/libpthread.so.0 #5 0x7f8fece59ded in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8fefbac760 (LWP 5326)): [KCrash Handler] #6 0x7f8fef6083cb in Sonnet::Highlighter::eventFilter(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #7 0x7f8fed7b5ee6 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7f8fedcf2d13 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #9 0x7f8fedcf7ffa in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #10 0x7f8fef5ac0e8 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #11 0x7f8fed7b5d4b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #12 0x7f8fedd94e53 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #13 0x7f8fedd95256 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #14 0x7f8fedd716a2 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #15 0x7f8fedd99322 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #16 0x7f8fe573c01a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #17 0x7f8fe573c828 in ?? () from /usr/lib64/libglib-2.0.so.0 #18 0x7f8fe573c9bf in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #19 0x7f8fed7e4f5a in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #20 0x7f8fedd98fe6 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #21 0x7f8fed7b4cf2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #22 0x7f8fed7b4fe5 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
[Bug 295638] Kmail crash just beginning to compose an email
https://bugs.kde.org/show_bug.cgi?id=295638 Galeffi Christian c...@gallochri.com changed: What|Removed |Added Version|unspecified |4.8 -- 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 295676] kmail crash on compose new email
https://bugs.kde.org/show_bug.cgi?id=295676 Jan malte.ge...@googlemail.com changed: What|Removed |Added Keywords||regression Version|unspecified |4.8 -- 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 295611] kmail crash after updating to 4.8.1
https://bugs.kde.org/show_bug.cgi?id=295611 Stefan Vater st.va...@web.de changed: What|Removed |Added CC||st.va...@web.de --- Comment #1 from Stefan Vater st.va...@web.de --- Do not know if this is related... I had kmail immediately crashing after start after update to 4.8.1 as well. What helped to me was removing ~/.kde/share/config/kmail2rc. This is not nice since I lost a lot of settings with that, but after that I got a kmail that works at least. Although there are occational crashes as they have been reported elsewhere (see e.g. http://lists.kde.org/?l=kde-pimm=133138130411584w=2). -- 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 295681] New: kmail crashes when opening IMAP emails
https://bugs.kde.org/show_bug.cgi?id=295681 Bug ID: 295681 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail crashes when opening IMAP emails Classification: Unclassified OS: Linux Reporter: spearhead...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-16-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I wanted to read my emails but kmail only displays an empty mail - no matter what mail I select, but when I try my pop3 account - everythign works it has something to do with IMAP or googlemail - Custom settings of the application: IMAP features enabled The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Aborted [Current thread is 1 (Thread 0x7f8ad84007c0 (LWP 14929))] Thread 5 (Thread 0x7f8ab7226700 (LWP 14933)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x7f8ad5fd24ff in wait (time=3, this=0x21e1e10) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x21e1d88, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f8ad5fc567f in QThreadPoolThread::run (this=0x21f6530) at concurrent/qthreadpool.cpp:141 #4 0x7f8ad5fd208b in QThreadPrivate::start (arg=0x21f6530) at thread/qthread_unix.cpp:298 #5 0x7f8ad3310efc in start_thread (arg=0x7f8ab7226700) at pthread_create.c:304 #6 0x7f8ad577b59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 4 (Thread 0x7f8ab5bca700 (LWP 14935)): #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 #1 0x7f8ad571862f in _L_lock_10501 () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f8ad57169c1 in __GI___libc_free (mem=0x7f8ad5a341c0) at malloc.c:3736 #3 0x7f8ad47d4feb in QAbstractSocket::disconnectFromHostImplementation (this=0x2112108) at socket/qabstractsocket.cpp:2510 #4 0x7f8ad47d567d in qt_static_metacall (_a=optimized out, _id=optimized out, _o=optimized out, _c=optimized out) at .moc/release-shared/moc_qabstractsocket.cpp:168 #5 QAbstractSocket::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at .moc/release-shared/moc_qabstractsocket.cpp:152 #6 0x7f8ad60d8661 in QMetaMethod::invoke (this=0x7f8ab5bc9300, object=0x2112108, connectionType=Qt::DirectConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1641 #7 0x7f8ad60da970 in QMetaObject::invokeMethod (obj=0x2112108, member=optimized out, type=Qt::DirectConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1179 #8 0x7f8ad47d08b4 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., type=Qt::DirectConnection, member=0x7f8ad480b820 disconnectFromHostImplementation, obj=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:418 #9 QAbstractSocket::disconnectFromHost (this=optimized out) at socket/qabstractsocket.cpp:2474 #10 0x7f8ad47d09e7 in QAbstractSocket::close (this=0x2112108) at socket/qabstractsocket.cpp:2452 #11 0x7f8ad47d6761 in QAbstractSocket::waitForReadyRead (this=0x2112108, msecs=60) at socket/qabstractsocket.cpp:1897 #12 0x7f8ac7d57019 in ?? () from /usr/lib/libsopranoclient.so.1 #13 0x7f8ac7d5b296 in ?? () from /usr/lib/libsopranoclient.so.1 #14 0x7f8ac7d5ac95 in ?? () from /usr/lib/libsopranoclient.so.1 #15 0x7f8acee0bd37 in Soprano::QueryResultIterator::binding(QString const) const () from /usr/lib/libsoprano.so.4 #16 0x7f8acee0bec9 in Soprano::QueryResultIterator::operator[](QString) const () from /usr/lib/libsoprano.so.4 #17 0x7f8aceb3c17c in Nepomuk::ResourceData::load (this=0x7f8ab0400640) at ../../nepomuk/core/resourcedata.cpp:419 #18 0x7f8aceb3c95c in Nepomuk::ResourceData::property (this=0x7f8ab0400640, uri=...) at ../../nepomuk/core/resourcedata.cpp:265 #19 0x7f8aceb50893 in Nepomuk::Resource::property (this=0x7f8ab5bc9cc0, uri=...) at ../../nepomuk/core/resource.cpp:301 #20 0x7f8ad1eaf7da in MessageCore::NepomukResourceRetrieverRunnable::run (this=0x7f8ab03fe5e0) at ../../messagecore/asyncnepomukresourceretriever.cpp:47 #21 0x7f8ad5fc55b2 in QThreadPoolThread::run (this=0x35da930) at concurrent/qthreadpool.cpp:107 #22 0x7f8ad5fd208b in QThreadPrivate::start (arg=0x35da930) at thread/qthread_unix.cpp:298 #23
[Bug 295681] kmail crashes when opening IMAP emails
https://bugs.kde.org/show_bug.cgi?id=295681 --- Comment #1 from David spearhead...@gmail.com --- Created attachment 69456 -- https://bugs.kde.org/attachment.cgi?id=69456action=edit debug output of the crash -- 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 295684] New: Total loss of e-mail content withspam-filters
https://bugs.kde.org/show_bug.cgi?id=295684 Bug ID: 295684 Severity: grave Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Total loss of e-mail content withspam-filters Classification: Unclassified OS: Linux Reporter: pi...@arcor.de Hardware: Ubuntu Packages Status: UNCONFIRMED Component: filtering Product: kmail2 Total loss of e-mail content of incoming messages after upgrading to kde 4.8.1. This behaviour stops after removing the spam-filter in the filter-menu. I tested it serveral times with different configurations and spamfilter like pop3 and imap-accounts, bogofilter and spamassin. The filters are all generated by the build-in option in the extra-menu. It's annoying, because I lost some important information and I had to ask for resending the mails. -- 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 295576] 4.8.1: gmail emails are blank in Inbox, two of each email shows up in All Mail, one is blank the other has correct content
https://bugs.kde.org/show_bug.cgi?id=295576 --- Comment #2 from Alexander Jones happy5...@gmail.com --- I can also confirm that this bug occurs with a locally installed IMAP server. (dovecot/postfix) -- 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 295686] New: open new mail, close it, discard it
https://bugs.kde.org/show_bug.cgi?id=295686 Bug ID: 295686 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: open new mail, close it, discard it Classification: Unclassified OS: Linux Reporter: ultra...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-16-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: when? more like before the crash happened. anyway: i wanted to send a new mail, but closed and discarded the new mail. then it crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 in ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S [Current thread is 1 (Thread 0x7f16190b57c0 (LWP 2941))] Thread 7 (Thread 0x7f15fd924700 (LWP 2942)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f16158eec2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f16158eed59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f16110bbefc in start_thread (arg=0x7f15fd924700) at pthread_create.c:304 #4 0x7f16165fe59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 6 (Thread 0x7f15fd013700 (LWP 2943)): #0 0x7f1610c10370 in g_thread_self () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1610bea419 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1616d6cc06 in QEventDispatcherGlib::processEvents (this=0x15f4230, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #3 0x7f1616d3c3e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #4 0x7f1616d3c637 in QEventLoop::exec (this=0x7f15fd012dc0, flags=...) at kernel/qeventloop.cpp:204 #5 0x7f1616c3c067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #6 0x7f1616c3f08b in QThreadPrivate::start (arg=0x15f3b00) at thread/qthread_unix.cpp:298 #7 0x7f16110bbefc in start_thread (arg=0x7f15fd013700) at pthread_create.c:304 #8 0x7f16165fe59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x in ?? () Thread 5 (Thread 0x7f15b0d5e700 (LWP 2945)): #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 #1 0x7f161659b62f in _L_lock_10501 () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f16165999c1 in __GI___libc_free (mem=0x7f16168b71c0) at malloc.c:3736 #3 0x7f1610be54e1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1616d6c937 in QEventDispatcherGlib::~QEventDispatcherGlib (this=0x1975bd0, __in_chrg=optimized out) at kernel/qeventdispatcher_glib.cpp:375 #5 0x7f1616d6cb19 in QEventDispatcherGlib::~QEventDispatcherGlib (this=0x1975bd0, __in_chrg=optimized out) at kernel/qeventdispatcher_glib.cpp:403 #6 0x7f1616c3df35 in QThreadPrivate::finish (arg=optimized out) at thread/qthread_unix.cpp:330 #7 0x7f1616c3f093 in ~__pthread_cleanup_class (this=synthetic pointer, __in_chrg=optimized out) at /usr/include/pthread.h:545 #8 ~__pthread_cleanup_class (this=synthetic pointer, __in_chrg=optimized out) at thread/qthread_unix.cpp:716 #9 QThreadPrivate::start (arg=0x7f16170944e0) at thread/qthread_unix.cpp:273 #10 0x7f16110bbefc in start_thread (arg=0x7f15b0d5e700) at pthread_create.c:304 #11 0x7f16165fe59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 4 (Thread 0x7f15ad00f700 (LWP 3101)): #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 #1 0x7f161659b62f in _L_lock_10501 () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f16165999c1 in __GI___libc_free (mem=0x7f16168b71c0) at malloc.c:3736 #3 0x7f1616d6c2a5 in socketNotifierSourceCheck (source=0x2242f60) at kernel/qeventdispatcher_glib.cpp:92 #4 0x7f1610be9734 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1610be9f82 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f1610bea429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f1616d6cb9f in QEventDispatcherGlib::processEvents (this=0x1d30140, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #8 0x7f1616d3c3e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #9 0x7f1616d3c637 in QEventLoop::exec (this=0x7f15ad00ed90, flags=...) at kernel/qeventloop.cpp:204 #10 0x7f1616c3c067 in QThread::exec (this=optimized
[Bug 295582] kontact crashed showing emails
https://bugs.kde.org/show_bug.cgi?id=295582 Serge Ratke wuseldu...@yahoo.de changed: What|Removed |Added CC||wuseldu...@yahoo.de -- 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 295582] kontact crashed showing emails
https://bugs.kde.org/show_bug.cgi?id=295582 --- Comment #1 from Serge Ratke wuseldu...@yahoo.de --- Created attachment 69457 -- https://bugs.kde.org/attachment.cgi?id=69457action=edit New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0 - What I was doing when the application crashed: jumpted to next unread e-mail which was in a different folder. -- Backtrace (Reduced): #6 0x7f9f7a70148b in malloc_consolidate (av=0x7f9f6020) at malloc.c:5161 #7 0x7f9f7a703175 in _int_malloc (av=0x7f9f6020, bytes=65536) at malloc.c:4373 [...] #9 0x7f9f7ba540c8 in QByteArray::realloc (this=0x7f9f61a5e828, alloc=65504) at tools/qbytearray.cpp:1452 #10 0x7f9f7ba541e9 in QByteArray::resize (this=0x7f9f61a5e828, size=32768) at tools/qbytearray.cpp:1420 #11 0x7f9f75fbf581 in reserve (bytes=2, this=0x7f9f602d0150) at ../../include/QtCore/private/../../../src/corelib/tools/qringbuffer_p.h:158 -- 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 295615] kmail crashed after hitting reply
https://bugs.kde.org/show_bug.cgi?id=295615 --- Comment #2 from Markus m4rkus...@web.de --- Sometimes selecting a different identity in the composer prevents the crash. Btw, I use kde-4.8.1 and have not experienced such behaviour before in 4.8.0. -- 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 295618] dav groupware resource always asks about logging in on startup
https://bugs.kde.org/show_bug.cgi?id=295618 Sergio Martins iamser...@gmail.com changed: What|Removed |Added CC||iamser...@gmail.com Component|groupware |DAV Resource Assignee|korganizer-de...@kde.org|kdepim-bugs@kde.org Product|korganizer |Akonadi -- 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 283020] Store Kmail Tags in IMAP flags, like Thunderbird
https://bugs.kde.org/show_bug.cgi?id=283020 Erik Quaeghebeur kdeb...@equaeghe.nospammail.net changed: What|Removed |Added CC||kdebugs@equaeghe.nospammail ||.net -- 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 295618] dav groupware resource always asks about logging in on startup
https://bugs.kde.org/show_bug.cgi?id=295618 Grégory Oestreicher g...@kamago.net changed: What|Removed |Added CC||g...@kamago.net --- Comment #1 from Grégory Oestreicher g...@kamago.net --- Hi, Which KDE / KDE PIM versions are you using? Cheers, Grégory -- 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 96968] Flat thread view in message list
https://bugs.kde.org/show_bug.cgi?id=96968 Erik Quaeghebeur kdeb...@equaeghe.nospammail.net changed: What|Removed |Added CC||kdebugs@equaeghe.nospammail ||.net -- 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 295618] dav groupware resource always asks about logging in on startup
https://bugs.kde.org/show_bug.cgi?id=295618 --- Comment #2 from Silver Salonen silver.salo...@gmail.com --- Started using DAV resource in KDE 4.8.0, currently using 4.8.1. -- 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 295700] New: After upgrade to 4.8.1: QMYSQL3 is Unable to execute statement
https://bugs.kde.org/show_bug.cgi?id=295700 Bug ID: 295700 Severity: normal Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: After upgrade to 4.8.1: QMYSQL3 is Unable to execute statement Classification: Unclassified OS: Linux Reporter: luk...@gmx.at Hardware: openSUSE RPMs Status: UNCONFIRMED Component: server Product: Akonadi -- 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 295700] After upgrade to 4.8.1: QMYSQL3 is unable to execute statement due to BINLOG_FORMAT = STATEMENT
https://bugs.kde.org/show_bug.cgi?id=295700 Franz Häuslschmid luk...@gmx.at changed: What|Removed |Added Summary|After upgrade to 4.8.1: |After upgrade to 4.8.1: |QMYSQL3 is Unable to|QMYSQL3 is unable to |execute statement |execute statement due to ||BINLOG_FORMAT = STATEMENT -- 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 295700] After upgrade to 4.8.1: QMYSQL3 is unable to execute statement due to BINLOG_FORMAT = STATEMENT
https://bugs.kde.org/show_bug.cgi?id=295700 --- Comment #1 from Franz Häuslschmid luk...@gmx.at --- After having updated to 4.8.1 I added an IMAP resource for a dovecot2 mail server. After that process I was trying to load messages (read and unread) from that server. I assume I was hit by the bug of https://bugs.kde.org/show_bug.cgi?id=295484 as the only unread message in the inbox lost its body. At some point Kmail2 crashed and I rebooted my computer. Kmail2 then listed my mail hierarchy, but didn't show the mail contents. I looked into .xsession-errors and observed many occurrences like found 1 item parts to expire in collection INBOX Error during updating record with id 11438 in table PartTable Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED. QMYSQL3: Unable to execute statement failed to update item part 11438 Decided to recreate Akonadi's database, deleted ~/.local/share/akonadi and started the command akonadictl start. There still was a problem regarding the setting for locking database objects: Database akonadi opened using driver QMYSQL DbInitializer::run() checking table SchemaVersionTable INSERT INTO SchemaVersionTable (version) VALUES (20) Unable to add initial data to table 'SchemaVersionTable'. Query error: 'Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED. QMYSQL: Unable to execute query' Query was: INSERT INTO SchemaVersionTable (version) VALUES (20) Unable to initialize database. [ 0: akonadiserver(_Z11akBacktracev+0x35) [0x453ba5] 1: akonadiserver() [0x453e6c] 2: /lib64/libc.so.6(+0x34e10) [0x7f91cd1b2e10] 3: /lib64/libc.so.6(gsignal+0x35) [0x7f91cd1b2d95] 4: /lib64/libc.so.6(abort+0x17b) [0x7f91cd1b42ab] 5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f91cec79c84] 6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x92) [0x456142] 7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xaf) [0x7f91ced1482f] 8: /usr/lib64/libQtCore.so.4(+0x11de02) [0x7f91ced1fe02] 9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x39) [0x7f91ced28c99] 10: akonadiserver() [0x45abd8] 11: akonadiserver(_ZN7Akonadi13AkonadiServer8instanceEv+0x35) [0x45bd45] 12: akonadiserver(main+0x1ea) [0x44c0da] 13: /lib64/libc.so.6(__libc_start_main+0xed) [0x7f91cd19f23d] 14: akonadiserver() [0x44c871] ] ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error) After that I explicitly added binlog_format=mixed to ~/.config/akonadi/mysql-local.conf. Akonadi and Kmail2 now work as expected. -- 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 295703] New: Cycling keyboard input focus into the composer window's body field crashes KMail
https://bugs.kde.org/show_bug.cgi?id=295703 Bug ID: 295703 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Cycling keyboard input focus into the composer window's body field crashes KMail Classification: Unclassified OS: Linux Reporter: k...@mattwhitlock.name Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) (Compiled from sources) Qt Version: 4.8.0 Operating System: Linux 3.2.1-gentoo-r2 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: 1. Open a new message composer window. 2. Fill in a recipient's address. 3. Press the Tab key (repeatedly) to move the input focus into the body field. 4. KMail crashes. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f26bee347a0 (LWP 5299))] Thread 3 (Thread 0x7f26a1f00700 (LWP 5312)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f26b0d60034 in scavengerThread (this=0x7f26b1747100) at wtf/FastMalloc.cpp:2495 #2 WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f26b1747100) at wtf/FastMalloc.cpp:1618 #3 0x7f26b9e82d0c in start_thread (arg=0x7f26a1f00700) at pthread_create.c:301 #4 0x7f26bc08fdbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f26a15e7700 (LWP 5313)): #0 0x7f26bc086ee3 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f26b44dfb4d in g_main_context_poll (n_fds=1, fds=0x7f269c002030, timeout=-1, context=0x2d25ef0, priority=optimized out) at gmain.c:3402 #2 g_main_context_iterate (context=0x2d25ef0, block=1, dispatch=1, self=optimized out) at gmain.c:3084 #3 0x7f26b44e0021 in g_main_context_iteration (context=0x2d25ef0, may_block=1) at gmain.c:3152 #4 0x7f26bca07956 in QEventDispatcherGlib::processEvents (this=0x2d25a80, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f26bc9d77e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f26bc9d7a95 in QEventLoop::exec (this=0x7f26a15e6de0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f26bc8d50d8 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7f26bc8d774b in QThreadPrivate::start (arg=0x2d25700) at thread/qthread_unix.cpp:298 #9 0x7f26b9e82d0c in start_thread (arg=0x7f26a15e7700) at pthread_create.c:301 #10 0x7f26bc08fdbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f26bee347a0 (LWP 5299)): [KCrash Handler] #6 0x7f26be86da53 in Sonnet::Highlighter::eventFilter (this=0x2c7f3b0, o=0x2741120, e=0x7fff0dde0550) at /var/tmp/portage/kde-base/kdelibs-4.8.1/work/kdelibs-4.8.1/kdeui/sonnet/highlighter.cpp:355 #7 0x7f26bc9d8936 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=optimized out, receiver=0x2741120, event=0x7fff0dde0550) at kernel/qcoreapplication.cpp:986 #8 0x7f26bcf091f1 in QApplicationPrivate::notify_helper (this=0x23275b0, receiver=0x2741120, e=0x7fff0dde0550) at kernel/qapplication.cpp:4546 #9 0x7f26bcf0e697 in QApplication::notify (this=optimized out, receiver=optimized out, e=0x7fff0dde0550) at kernel/qapplication.cpp:3991 #10 0x7f26be7ff716 in KApplication::notify (this=0x7fff0dde1550, receiver=0x2741120, event=0x7fff0dde0550) at /var/tmp/portage/kde-base/kdelibs-4.8.1/work/kdelibs-4.8.1/kdeui/kernel/kapplication.cpp:311 #11 0x7f26bc9d87bb in QCoreApplication::notifyInternal (this=0x7fff0dde1550, receiver=0x2741120, event=0x7fff0dde0550) at kernel/qcoreapplication.cpp:876 #12 0x7f26bcfaa4ca in QKeyMapper::sendKeyEvent (keyWidget=0x2741120, grab=optimized out, type=QEvent::KeyPress, code=16777217, modifiers=..., text=..., autorepeat=false, count=1, nativeScanCode=23, nativeVirtualKey=65289, nativeModifiers=16) at kernel/qkeymapper_x11.cpp:1866 #13 0x7f26bcfaa91f in QKeyMapperPrivate::translateKeyEvent (this=optimized out, keyWidget=0x2741120, event=optimized out, grab=false) at kernel/qkeymapper_x11.cpp:1836 #14 0x7f26bcf86e43 in QApplication::x11ProcessEvent (this=0x7fff0dde1550, event=0x7fff0dde1100) at kernel/qapplication_x11.cpp:3513 #15 0x7f26bcfae972 in x11EventSourceDispatch (s=0x232ae80, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #16 0x7f26b44df4f5 in g_main_dispatch (context=0x2329c00) at gmain.c:2441 #17 g_main_context_dispatch (context=0x2329c00) at gmain.c:3011 #18 0x7f26b44dfe38 in g_main_context_iterate (context=0x2329c00, block=1, dispatch=1,
[Bug 295703] Keyboard events in composer window's body text field crash KMail
https://bugs.kde.org/show_bug.cgi?id=295703 Matt Whitlock k...@mattwhitlock.name changed: What|Removed |Added Component|general |composer Summary|Cycling keyboard input |Keyboard events in composer |focus into the composer |window's body text field |window's body field crashes |crash KMail |KMail | --- Comment #1 from Matt Whitlock k...@mattwhitlock.name --- This bug actually prevents any text from being entered into the body of a composer. Even these steps are enough to crash KMail: 1. Open a new composer window. 2. Click in the body field to set the focus. 3. Press the Shift key. 4. KMail crashes. Oddly, my package manager (Gentoo Portage) says KMail 4.8.1 is installed, but the About dialog in KMail itself says Version 4.8.0, Using KDE Development Platform 4.8.1 (4.8.1). -- 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 290036] The Remove Duplicate Mails-Function deletes both the duplicate and the original (pop3)
https://bugs.kde.org/show_bug.cgi?id=290036 --- Comment #2 from Guido Schmidt pande...@gmx.net --- It gets worse: Today it deleted a new message that did not even have a duplicate. -- 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 295618] dav groupware resource always asks about logging in on startup
https://bugs.kde.org/show_bug.cgi?id=295618 --- Comment #3 from Grégory Oestreicher g...@kamago.net --- This means that the remote end answers with something else than a 401 (maybe a 3XX response code) that triggers this alert. If you try to connect to the address you configured with a web browser are you redirected to another page? If so, try to configured the URL at which you are. Cheers, Grégory -- 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 295709] New: Kontac crash when I open e-mail in Inbox
https://bugs.kde.org/show_bug.cgi?id=295709 Bug ID: 295709 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontac crash when I open e-mail in Inbox Classification: Unclassified OS: Linux Reporter: runetmem...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.2.0-18-generic x86_64 Distribution: Ubuntu precise (development branch) -- Information about the crash: - What I was doing when the application crashed: Kontac crash when I open e-mail in Inbox. Content of this e-mail is simple - new message forum notification (plain text) with two links. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f19b83477c0 (LWP 2583))] Thread 5 (Thread 0x7f199b61c700 (LWP 2602)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f19b4b44ddc in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f19b4b44f09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f19b000be9a in start_thread (arg=0x7f199b61c700) at pthread_create.c:308 #4 0x7f19b587474d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f199ad03700 (LWP 2609)): #0 QTimerInfoList::timerWait (this=0x7f1994002860, tm=...) at kernel/qeventdispatcher_unix.cpp:449 #1 0x7f19b5fe7fcc in timerSourcePrepareHelper (src=optimized out, timeout=0x7f199ad02c5c) at kernel/qeventdispatcher_glib.cpp:136 #2 0x7f19afb3e85e in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f19afb3f05b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f19afb3f264 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f19b5fe8a76 in QEventDispatcherGlib::processEvents (this=0x7f19940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f19b5fb82d2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f19b5fb8527 in QEventLoop::exec (this=0x7f199ad02dc0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f19b5eb7f97 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7f19b5ebafbb in QThreadPrivate::start (arg=0xb6e7f0) at thread/qthread_unix.cpp:298 #10 0x7f19b000be9a in start_thread (arg=0x7f199ad03700) at pthread_create.c:308 #11 0x7f19b587474d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 3 (Thread 0x7f1942d9d700 (LWP 2957)): #0 0x7f19afb3e1eb in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f19afb3f004 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f19afb3f264 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f19b5fe8a76 in QEventDispatcherGlib::processEvents (this=0x7f193c002df0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f19b5fb82d2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f19b5fb8527 in QEventLoop::exec (this=0x7f1942d9cd90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f19b5eb7f97 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f19b5f9806f in QInotifyFileSystemWatcherEngine::run (this=0x15b7180) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f19b5ebafbb in QThreadPrivate::start (arg=0x15b7180) at thread/qthread_unix.cpp:298 #9 0x7f19b000be9a in start_thread (arg=0x7f1942d9d700) at pthread_create.c:308 #10 0x7f19b587474d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7f193aa79700 (LWP 7641)): [KCrash Handler] #10 malloc_consolidate (av=0x7f193020) at malloc.c:4246 #11 0x7f19b5802156 in malloc_consolidate (av=0x7f193020) at malloc.c:4215 #12 _int_malloc (av=0x7f193020, bytes=65536) at malloc.c:3532 #13 0x7f19b5804cd5 in __GI___libc_malloc (bytes=65536) at malloc.c:2924 #14 0x7f19b5ebcfb8 in QByteArray::realloc (this=0x7f19300058f8, alloc=65504) at tools/qbytearray.cpp:1452 #15 0x7f19b5ebd0d9 in QByteArray::resize (this=0x7f19300058f8, size=32768) at tools/qbytearray.cpp:1420 #16 0x7f19b0eb58c6 in reserve (bytes=2, this=0x7f19300014d0) at ../../include/QtCore/private/../../../src/corelib/tools/qringbuffer_p.h:158 #17 QAbstractSocket::writeData (this=optimized out, data=0x7f193aa785ec \021, size=2) at socket/qabstractsocket.cpp:2315 #18 0x7f19b5f4c3cf in QIODevice::write (this=0x7f1930006c00, data=0x7f193aa785ec \021, maxSize=optimized out) at
[Bug 295709] Kontac crash when I open e-mail in Inbox
https://bugs.kde.org/show_bug.cgi?id=295709 RunetMember runetmem...@gmail.com changed: What|Removed |Added CC||runetmem...@gmail.com -- 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 295709] Kontac crash when I open e-mail in Inbox
https://bugs.kde.org/show_bug.cgi?id=295709 --- Comment #1 from RunetMember runetmem...@gmail.com --- Created attachment 69467 -- https://bugs.kde.org/attachment.cgi?id=69467action=edit New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0 - What I was doing when the application crashed: Probably same crash. This crash reproduced in few minutes after first crash. So this crash in indeed reproducable (at least at this moment). -- Backtrace (Reduced): #10 0x7f87e22ceb40 in malloc_consolidate (av=0x7f876820) at malloc.c:4246 #11 0x7f87e22d0156 in malloc_consolidate (av=0x7f876820) at malloc.c:4215 #12 _int_malloc (av=0x7f876820, bytes=65536) at malloc.c:3532 #13 0x7f87e22d2cd5 in __GI___libc_malloc (bytes=65536) at malloc.c:2924 #14 0x7f87e298afb8 in QByteArray::realloc (this=0x7f8768001368, alloc=65504) at tools/qbytearray.cpp:1452 -- 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 295638] Kmail crash just beginning to compose an email
https://bugs.kde.org/show_bug.cgi?id=295638 Galeffi Christian c...@gallochri.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Galeffi Christian c...@gallochri.com --- *** This bug has been marked as a duplicate of bug 295611 *** -- 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 295611] kmail crash after updating to 4.8.1
https://bugs.kde.org/show_bug.cgi?id=295611 Galeffi Christian c...@gallochri.com changed: What|Removed |Added CC||c...@gallochri.com --- Comment #2 from Galeffi Christian c...@gallochri.com --- *** Bug 295638 has been marked as a duplicate of this bug. *** -- 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 295582] kontact crashed showing emails
https://bugs.kde.org/show_bug.cgi?id=295582 George L. Emigh ab...@georgelemigh.com changed: What|Removed |Added CC||ab...@georgelemigh.com -- 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 295709] Kontac crash when I open e-mail in Inbox
https://bugs.kde.org/show_bug.cgi?id=295709 George L. Emigh ab...@georgelemigh.com changed: What|Removed |Added CC||ab...@georgelemigh.com -- 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 295722] New: messages aren't showing; webmail messages disappear, too
https://bugs.kde.org/show_bug.cgi?id=295722 Bug ID: 295722 Severity: major Version: 4.8 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: messages aren't showing; webmail messages disappear, too Classification: Unclassified OS: Linux Reporter: k...@ninthfloor.org Hardware: Other Status: UNCONFIRMED Component: general Product: kmail2 Since I upgraded to KDE 4.8.1, e-mail messages haven't been showing up. Their subjects will show up, but their messages will be blank. I've had e-mails from a few different organizations. I've checked the e-mails for two different accounts on the servers, and their messages are blank, too. I'm using IMAP. I checked one account through a browser and the other account through SSH. I think KMail is somehow downloading the e-mail and deleting the messages both locally and on the remote servers while leaving the subjects and other headers in tact. It's similar to https://bugs.kde.org/show_bug.cgi?id=287097 but I can't see the messages even on the server. When I check the e-mail on the server, before downloading with KMail, I can see the messages, and when I download those messages with KMail, I can still see the messages. Otherwise, I can't see them, and clicking Edit this Message doesn't show anything like in the bug report above. Also, this is for all e-mail, not just HTML with JavaScript, etc. -- 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 295676] kmail crash on compose new email
https://bugs.kde.org/show_bug.cgi?id=295676 --- Comment #1 from Jan malte.ge...@googlemail.com --- this crash is caused due to usage of nepomuk. with disabled nepomuk this does not happen. -- 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 295676] kmail crash on compose new email
https://bugs.kde.org/show_bug.cgi?id=295676 --- Comment #2 from Jan malte.ge...@googlemail.com --- seems like it is only the nepomuk mail indexer. With enabled basic nepomuk this crash does not happen. Having file indexer enabled works fine. Using nepomuk mail indexer causes this crash every time i try to compose a new 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 295725] New: Crash while switching between mails
https://bugs.kde.org/show_bug.cgi?id=295725 Bug ID: 295725 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Crash while switching between mails Classification: Unclassified OS: Linux Reporter: blaueshawaiih...@gmx.de Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-16-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I was browsing different mails by klicking on list entries. This kind of crash happens very regularly, especially when I switch quickly beween mails. - Custom settings of the application: IMAP account. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 in ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S [Current thread is 1 (Thread 0x7fe57f5f67c0 (LWP 7868))] Thread 5 (Thread 0x7fe55ecae700 (LWP 7872)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fe571a26c2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fe571a26d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fe57a514efc in start_thread (arg=0x7fe55ecae700) at pthread_create.c:304 #4 0x7fe57c97f59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7fe55e3ad700 (LWP 7873)): #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 #1 0x7fe57c91c62f in _L_lock_10501 () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7fe57c91a9c1 in __GI___libc_free (mem=0x7fe55820) at malloc.c:3736 #3 0x7fe57d3048d4 in QTimerInfoList::unregisterTimer (this=0x1ef3190, timerId=1879048206) at kernel/qeventdispatcher_unix.cpp:507 #4 0x7fe57d2f1f51 in stop (this=0x7fe558011430) at kernel/qtimer.cpp:266 #5 QTimer::stop (this=0x7fe558011430) at kernel/qtimer.cpp:263 #6 0x7fe57d2f2055 in QTimer::timerEvent (this=0x7fe558011430, e=optimized out) at kernel/qtimer.cpp:279 #7 0x7fe57d2ed8d9 in QObject::event (this=0x7fe558011430, e=optimized out) at kernel/qobject.cpp:1157 #8 0x7fe57d7f7104 in notify_helper (e=0x7fe55e3acb50, receiver=0x7fe558011430, this=0x16bf600) at kernel/qapplication.cpp:4555 #9 QApplicationPrivate::notify_helper (this=0x16bf600, receiver=0x7fe558011430, e=0x7fe55e3acb50) at kernel/qapplication.cpp:4527 #10 0x7fe57d7fbf83 in QApplication::notify (this=0x7fff10157830, receiver=0x7fe558011430, e=0x7fe55e3acb50) at kernel/qapplication.cpp:4416 #11 0x7fe57f0259a6 in KApplication::notify (this=0x7fff10157830, receiver=0x7fe558011430, event=0x7fe55e3acb50) at ../../kdeui/kernel/kapplication.cpp:311 #12 0x7fe57d2d45fc in QCoreApplication::notifyInternal (this=0x7fff10157830, receiver=0x7fe558011430, event=0x7fe55e3acb50) at kernel/qcoreapplication.cpp:876 #13 0x7fe57d3059a2 in sendEvent (event=0x7fe55e3acb50, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #14 QTimerInfoList::activateTimers (this=0x1ef3190) at kernel/qeventdispatcher_unix.cpp:611 #15 0x7fe57d30336d in timerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:186 #16 timerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:180 #17 0x7fe57d303391 in idleTimerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:233 #18 0x7fe57530ea5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fe57530f258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fe57530f429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fe57d303c06 in QEventDispatcherGlib::processEvents (this=0x1c73ad0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #22 0x7fe57d2d33e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #23 0x7fe57d2d3637 in QEventLoop::exec (this=0x7fe55e3acdc0, flags=...) at kernel/qeventloop.cpp:204 #24 0x7fe57d1d3067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #25 0x7fe57d1d608b in QThreadPrivate::start (arg=0x1c737d0) at thread/qthread_unix.cpp:298 #26 0x7fe57a514efc in start_thread (arg=0x7fe55e3ad700) at pthread_create.c:304 #27 0x7fe57c97f59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #28 0x in ?? () Thread 3 (Thread 0x7fe5172bc700 (LWP 7912)): #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 #1 0x7fe57c91c62f in
[Bug 295726] New: kmail crashes every now and then during checking mails
https://bugs.kde.org/show_bug.cgi?id=295726 Bug ID: 295726 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail crashes every now and then during checking mails Classification: Unclassified OS: Linux Reporter: rydb...@o2.pl Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-16-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: I was checking and sorting my mail. Every couple e-mails kmail crashes without any apparent reason: no matter if an email was in a plain text or html, had an attachement or not The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 in ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S [Current thread is 1 (Thread 0x7f2ab9fe67c0 (LWP 1874))] Thread 6 (Thread 0x7f2a9e8b5700 (LWP 1875)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f2ab681cc2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f2ab681cd59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f2ab1fe9efc in start_thread (arg=0x7f2a9e8b5700) at pthread_create.c:304 #4 0x7f2ab752c59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 5 (Thread 0x7f2a9df94700 (LWP 1876)): #0 0x7f2ab7520473 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f2ab1b17f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2ab1b18429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2ab7c9ac06 in QEventDispatcherGlib::processEvents (this=0x1f4fd00, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f2ab7c6a3e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f2ab7c6a637 in QEventLoop::exec (this=0x7f2a9df93dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f2ab7b6a067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f2ab7b6d08b in QThreadPrivate::start (arg=0x1f4f3d0) at thread/qthread_unix.cpp:298 #8 0x7f2ab1fe9efc in start_thread (arg=0x7f2a9df94700) at pthread_create.c:304 #9 0x7f2ab752c59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 4 (Thread 0x7f2a4ceaa700 (LWP 1894)): #0 0x7f2ab1fec034 in __pthread_mutex_lock (mutex=0x3331478) at pthread_mutex_lock.c:61 #1 0x7f2ab1b17023 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2ab1b17dfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2ab1b18429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2ab7c9ac06 in QEventDispatcherGlib::processEvents (this=0x33308f0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f2ab7c6a3e2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f2ab7c6a637 in QEventLoop::exec (this=0x7f2a4cea9d90, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f2ab7b6a067 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7f2ab7c4a17f in QInotifyFileSystemWatcherEngine::run (this=0x33271b0) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x7f2ab7b6d08b in QThreadPrivate::start (arg=0x33271b0) at thread/qthread_unix.cpp:298 #10 0x7f2ab1fe9efc in start_thread (arg=0x7f2a4ceaa700) at pthread_create.c:304 #11 0x7f2ab752c59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 3 (Thread 0x7f2a4dd35700 (LWP 1896)): [KCrash Handler] #6 malloc_consolidate (av=0x7f2a4820) at malloc.c:5153 #7 0x7f2ab74c4a4f in malloc_consolidate (av=0x7f2a4820) at malloc.c:5115 #8 _int_malloc (av=0x7f2a4820, bytes=65536) at malloc.c:4373 #9 0x7f2ab74c73cd in __GI___libc_malloc (bytes=65536) at malloc.c:3660 #10 0x7f2ab7b6f088 in QByteArray::realloc (this=0x7f2a98033118, alloc=65504) at tools/qbytearray.cpp:1452 #11 0x7f2ab7b6f1a9 in QByteArray::resize (this=0x7f2a98033118, size=32768) at tools/qbytearray.cpp:1420 #12 0x7f2ab2e1ea06 in reserve (bytes=2, this=0x7f2a980cea00) at ../../include/QtCore/private/../../../src/corelib/tools/qringbuffer_p.h:158 #13 QAbstractSocket::writeData (this=optimized out, data=0x7f2a4dd345ec \021, size=2) at socket/qabstractsocket.cpp:2315 #14 0x7f2ab7bfe4af in QIODevice::write (this=0x7f2a98033130, data=0x7f2a4dd345ec \021, maxSize=optimized out)
[Bug 295726] kmail crashes every now and then during checking mails
https://bugs.kde.org/show_bug.cgi?id=295726 JaromirD rydb...@o2.pl changed: What|Removed |Added CC||rydb...@o2.pl -- 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 295726] kmail crashes every now and then during checking mails
https://bugs.kde.org/show_bug.cgi?id=295726 --- Comment #1 from JaromirD rydb...@o2.pl --- Created attachment 69477 -- https://bugs.kde.org/attachment.cgi?id=69477action=edit New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0 And now again kmail crashed. This time it was enough to scroll the e-mail list. This program's became simply useless if it's even not possible to check one's mail. -- Backtrace (Reduced): #6 0x7f1122790a14 in malloc_consolidate (av=0x7f110420) at malloc.c:5161 #7 0x7f1122791a4f in malloc_consolidate (av=0x7f110420) at malloc.c:5115 #8 _int_malloc (av=0x7f110420, bytes=65536) at malloc.c:4373 #9 0x7f11227943cd in __GI___libc_malloc (bytes=65536) at malloc.c:3660 #10 0x7f1122e3c088 in QByteArray::realloc (this=0x7f1104009928, alloc=65504) at tools/qbytearray.cpp:1452 -- 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 295730] New: KMail suddenly crashes
https://bugs.kde.org/show_bug.cgi?id=295730 Bug ID: 295730 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail suddenly crashes Classification: Unclassified OS: Linux Reporter: zua...@riseup.net Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) (Compiled from sources) Qt Version: 4.8.0 Operating System: Linux 3.2.5-1-pae i686 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Hello This is not the first time I have a similar crash. Just I keep KMail running and, by surprise, it crashes. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library /lib/libthread_db.so.1. [Current thread is 1 (Thread 0xae6dd780 (LWP 2936))] Thread 4 (Thread 0xacf0db40 (LWP 2941)): #0 0xb7729424 in __kernel_vsyscall () #1 0xb5d51860 in poll () from /lib/libc.so.6 #2 0xb428423b in g_poll () from /usr/lib/libglib-2.0.so.0 #3 0xb4275746 in g_main_context_iterate.isra.19 () from /usr/lib/libglib-2.0.so.0 #4 0xb4275ada in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb60db377 in QEventDispatcherGlib::processEvents (this=0xac600480, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0xb60a2ffd in QEventLoop::processEvents (this=0xacf0d180, flags=...) at kernel/qeventloop.cpp:149 #7 0xb60a3299 in QEventLoop::exec (this=0xacf0d180, flags=...) at kernel/qeventloop.cpp:204 #8 0xb5f7fcad in QThread::exec (this=0x9b6c2e8) at thread/qthread.cpp:501 #9 0xb5f7fd7b in QThread::run (this=0x9b6c2e8) at thread/qthread.cpp:568 #10 0xb5f82ffa in QThreadPrivate::start (arg=0x9b6c2e8) at thread/qthread_unix.cpp:298 #11 0xb0841f51 in ?? () from /usr/lib/libGL.so.1 #12 0x5c8b0824 in ?? () #13 0xbab80424 in ?? () #14 0x6500 in ?? () #15 0x001015ff in ?? () #16 0xd389 in ?? () #17 0xfff0013d in ?? () #18 0xc30173ff in ?? () #19 0x0f6402e8 in ?? () #20 0x0fc18100 in ?? () #21 0x8b0016f6 in ?? () #22 0x1089 in ?? () #23 0x29d231ff in ?? () #24 0x0d0365c2 in ?? () #25 0x in ?? () Thread 3 (Thread 0xab11bb40 (LWP 12495)): #0 0xb7729424 in __kernel_vsyscall () #1 0xb572dc53 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb5d68fa4 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libc.so.6 #3 0xb5f83522 in wait (time=3, this=0x9bec898) at thread/qwaitcondition_unix.cpp:84 #4 QWaitCondition::wait (this=0x9bec840, mutex=0x9bec83c, time=3) at thread/qwaitcondition_unix.cpp:158 #5 0xb5f75744 in QThreadPoolThread::run (this=0x9c49e78) at concurrent/qthreadpool.cpp:141 #6 0xb5f82ffa in QThreadPrivate::start (arg=0x9c49e78) at thread/qthread_unix.cpp:298 #7 0xb0841f51 in ?? () from /usr/lib/libGL.so.1 #8 0x5c8b0824 in ?? () #9 0xbab80424 in ?? () #10 0x6500 in ?? () #11 0x001015ff in ?? () #12 0xd389 in ?? () #13 0xfff0013d in ?? () #14 0xc30173ff in ?? () #15 0x0f6402e8 in ?? () #16 0x0fc18100 in ?? () #17 0x8b0016f6 in ?? () #18 0x1089 in ?? () #19 0x29d231ff in ?? () #20 0x0d0365c2 in ?? () #21 0x in ?? () Thread 2 (Thread 0xac0e3b40 (LWP 12497)): #0 0xb7729424 in __kernel_vsyscall () #1 0xb5d692b1 in __lll_lock_wait_private () from /lib/libc.so.6 #2 0xb5ceb37e in _L_lock_6933 () from /lib/libc.so.6 #3 0xb5ce9753 in malloc () from /lib/libc.so.6 #4 0xb77376c1 in _dl_map_object_deps () from /lib/ld-linux.so.2 #5 0xb773cdda in dl_open_worker () from /lib/ld-linux.so.2 #6 0xb7738cef in _dl_catch_error () from /lib/ld-linux.so.2 #7 0xb773c816 in _dl_open () from /lib/ld-linux.so.2 #8 0xb5d93eb1 in do_dlopen () from /lib/libc.so.6 #9 0xb7738cef in _dl_catch_error () from /lib/ld-linux.so.2 #10 0xb5d93fa7 in dlerror_run () from /lib/libc.so.6 #11 0xb5d94037 in __libc_dlopen_mode () from /lib/libc.so.6 #12 0xb5d6e6e8 in init () from /lib/libc.so.6 #13 0xb572edbe in pthread_once () from /lib/libpthread.so.0 #14 0xb5d6e955 in backtrace () from /lib/libc.so.6 #15 0xb5cdf080 in __libc_message () from /lib/libc.so.6 #16 0xb5ce5842 in malloc_printerr () from /lib/libc.so.6 #17 0xb5ce7ab8 in _int_malloc () from /lib/libc.so.6 #18 0xb5ce975c in malloc () from /lib/libc.so.6 #19 0xb08403c0 in ?? () from /usr/lib/libGL.so.1 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 1 (Thread 0xae6dd780 (LWP 2936)): [KCrash Handler] #7 0xb7729424 in __kernel_vsyscall () #8 0xb5ca007f in raise () from /lib/libc.so.6 #9 0xb5ca1a05 in abort () from /lib/libc.so.6 #10 0xb3e6e385 in _dbus_abort () from /usr/lib/libdbus-1.so.3 #11 0xb3e63d7b in _dbus_warn_check_failed () from /usr/lib/libdbus-1.so.3 #12 0xb3e53780 in dbus_message_new_method_call () from /usr/lib/libdbus-1.so.3 #13 0xb576aba4 in
[Bug 249798] Kmail its always outputting error messages
https://bugs.kde.org/show_bug.cgi?id=249798 tbohan...@gmail.com changed: What|Removed |Added CC||tbohan...@gmail.com --- Comment #2 from tbohan...@gmail.com --- I'm seeing this in the 4.8.1 Kubuntu update. Everything was working prior to the update. Since then my Kmail Folders resource is displaying the error message (NO[LRCONFLICT} Resource tries to modify item with dirty payload, aborting STORE.) Only is failing with this specific resource. Others are working as expected.. -- 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
