[kontact] [Bug 288141] Kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=288141 --- Comment #37 from Stephan Menzel <stephan.men...@gmx.eu> --- (In reply to Denis Kurz from comment #36) > This bug has only been reported for versions before 4.14, which have been > unsupported for at least two years now. Can anyone tell if this bug still > present? > > If noone confirms this bug for a Framework-based version of kontact (version > 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in > about three months. I remember this bug from back then. It used to hit me hard for many months and then it somehow disappeared. I guess you can safely consider it fixed. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 288141] Kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=288141 Stephan Menzel stephan.men...@gmx.eu changed: What|Removed |Added CC||stephan.men...@gmx.eu --- Comment #35 from Stephan Menzel stephan.men...@gmx.eu --- I also have this problem. At least I think its the same as it fits the symptoms. Here is two stack traces: -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f67878f17c0 (LWP 4509))] Thread 3 (Thread 0x7f676b402700 (LWP 4513)): #0 0x7f677f09482f in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f6782c8a1fe in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f6782c8a239 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7f677f08f2c4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f6784bcdfcd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f676aaf1700 (LWP 4514)): #0 0x7f6784bc51dd in poll () from /lib64/libc.so.6 #1 0x7f677e0204e4 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7f677e0205fc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f678618553e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f678614c421 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x7f678614c785 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7f678601bcb9 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7f678601eb6b in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7f677f08f2c4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f6784bcdfcd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f67878f17c0 (LWP 4509)): [KCrash Handler] #5 0x7f671afc5173 in Akregator::Part::slotSaveFeedList() () from /usr/lib64/kde4/akregatorpart.so #6 0x7f671afcaea7 in Akregator::Part::slotAutoSave() () from /usr/lib64/kde4/akregatorpart.so #7 0x7f671aff13c5 in Akregator::Part::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/kde4/akregatorpart.so #8 0x7f678616ccc3 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #9 0x7f6785358fac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #10 0x7f6785362038 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #11 0x7f6786c783ba in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #12 0x7f678614e6fb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #13 0x7f6786152e51 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4 #14 0x7f678618512e in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/qt4/libQtCore.so.4 #15 0x7f677e02023d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #16 0x7f677e020548 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #17 0x7f677e0205fc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #18 0x7f678618553e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #19 0x7f6785412eb6 in QGuiEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtGui.so.4 #20 0x7f678614c421 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #21 0x7f678614c785 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #22 0x7f678661d7f3 in KJob::exec() () from /usr/lib64/libkdecore.so.5 #23 0x7f6720a5b9e6 in KMKernel::cleanup() () from /usr/lib64/libkmailprivate.so.4 #24 0x7f6720e48e8a in KMailPart::~KMailPart() () from /usr/lib64/kde4/kmailpart.so #25 0x7f678711755e in KontactInterface::Plugin::~Plugin (this=0x1b83830, __vtt_parm=optimized out, __in_chrg=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.14.6/work/kdepimlibs-4.14.6/kontactinterface/plugin.cpp:92 #26 0x7f67237b57d6 in KMailPlugin::~KMailPlugin() () from /usr/lib64/kde4/kontact_kmailplugin.so #27 0x7f678733f046 in Kontact::MainWindow::~MainWindow (this=this@entry=0x1a6d1e0, __in_chrg=optimized out, __vtt_parm=optimized out) at /var/tmp/portage/kde-base/kontact-4.14.6/work/kontact-4.14.6/kontact/src/mainwindow.cpp:296 #28 0x7f678733f1e9 in Kontact::MainWindow::~MainWindow (this=0x1a6d1e0, __in_chrg=optimized out, __vtt_parm=optimized out
[Akonadi] [Bug 332781] Akonadi server fails to start right after upgrading to 1.12.0
https://bugs.kde.org/show_bug.cgi?id=332781 Stephan Menzel stephan.men...@gmx.eu changed: What|Removed |Added CC||stephan.men...@gmx.eu --- Comment #4 from Stephan Menzel stephan.men...@gmx.eu --- I'm having the exact same problem here with both akonadi 1.12 and 1.12.1. The only thing that helps is a downgrade to 1.11. My problem description and stacktrace are the same. Also, I can connect to the MySQL server with other tools with no problems. -- 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 273612] Local Folders: Unknown error. (There is no transaction in progress.)
https://bugs.kde.org/show_bug.cgi?id=273612 Stephan Menzel stephan.men...@gmx.eu changed: What|Removed |Added CC||stephan.men...@gmx.eu -- 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 289207] KMail sometimes fails to send messages with cyrus-sasl-2.1.25
https://bugs.kde.org/show_bug.cgi?id=289207 --- Comment #25 from Stephan Menzel stephan menzel gmx eu 2012-01-29 14:08:13 --- Thanks, downgrading cyrus-sasl to 2.1.23 solved the problem. Until now I was under the impression that = 2.2 causes this but apparently it's 2.1.25 already. -- 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 289207] KMail sometimes fails to send messages with cyrus-sasl-2.1.25
https://bugs.kde.org/show_bug.cgi?id=289207 --- Comment #23 from Stephan Menzel stephan menzel gmx eu 2012-01-28 22:35:45 --- I have just upgraded to 4.8.0 and cyrus-sasl 2.1.25 and the problem actually came back, after it went away when I commented on 1/1/2012. So the bug is not resolved. Furthermore, the upgrade (gentoo ~x86) involved only kde itself and nothing else. Especially not cyrus-sals which remained untouched 2.2. So I suppose this means the bug is indeed in kmail and not in cyrus. Once again, kmail is dysfunctional because of this. Should I try to downgrade to 4.7.x? This is quite a big deal on gentoo, so I would only do this if there's reasonable hope. Cheers, Stephan -- 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 289207] KMail sometimes fails to send message via IMAP with error SASL(0): successful result:
https://bugs.kde.org/show_bug.cgi?id=289207 --- Comment #5 from Stephan Menzel stephan menzel gmx eu 2012-01-01 19:53:46 --- A little update here: This appears to be fixed with what gentoo calls 4.7.4-r1. Just came with upstream and I can't reproduce the issue anymore. Don't know how / if this affects the original poster. Thanks, Stephan -- 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 289207] KMail sometimes fails to send message via IMAP with error SASL(0): successful result:
https://bugs.kde.org/show_bug.cgi?id=289207 Stephan Menzel stephan.men...@gmx.eu changed: What|Removed |Added CC||stephan.men...@gmx.eu --- Comment #3 from Stephan Menzel stephan menzel gmx eu 2011-12-25 21:30:59 --- Same problem here with 4.7.4 and GMX imap but always reproducable. I think it didn't occur with 4.7.3 but since this is gentoo it might be some underlying package change as well. Sadly, this bug renders my kmail useless at the moment. Merry Xmas everyone! Stephan -- 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 289207] KMail sometimes fails to send message via IMAP with error SASL(0): successful result:
https://bugs.kde.org/show_bug.cgi?id=289207 --- Comment #4 from Stephan Menzel stephan menzel gmx eu 2011-12-25 21:32:57 --- Ooops, sorry. I misread. In fact, it happens here when accessing the IMAP for reading mail. The bug is about sending. But the error message is the same. -- 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 267372] Crash on deleting message from imap folder
https://bugs.kde.org/show_bug.cgi?id=267372 Stephan Menzel stephan.men...@gmx.eu changed: What|Removed |Added CC||stephan.men...@gmx.eu -- 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 267372] Crash on deleting message from imap folder
https://bugs.kde.org/show_bug.cgi?id=267372 --- Comment #1 from Stephan Menzel stephan menzel gmx eu 2011-04-11 15:33:57 --- Created an attachment (id=58800) -- (http://bugs.kde.org/attachment.cgi?id=58800) New crash information added by DrKonqi kontact (4.4.10) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2 - What I was doing when the application crashed: I am under the impression this bug happens when I delete more than one message by repeatedly pressing the delete button. This time at the 4th mail. -- Backtrace (Reduced): #6 QList (this=0xffe4e3e2ffe4e3e2) at /usr/include/qt4/QtCore/qlist.h:118 #7 KMail::FolderJob::msgList (this=0xffe4e3e2ffe4e3e2) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10/kmail/folderjob.cpp:120 #8 0x7fd1a181ca7b in KMAcctImap::ignoreJobsForMessage (this=0x24947f0, msg=0x3f912c0) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10/kmail/kmacctimap.cpp:217 #9 0x7fd1a1921eb7 in KMMoveCommand::execute (this=0x3f565e0) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10/kmail/kmcommands.cpp:2208 #10 0x7fd1a191682a in KMCommand::slotPostTransfer (this=0x3f565e0, result=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.4.10-r1/work/kmail-4.4.10/kmail/kmcommands.cpp:295 -- 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
