[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case
https://bugs.kde.org/show_bug.cgi?id=222878 --- Comment #33 from Alexander Stein alexander...@web.de --- Unfortunately this hasn't gone yet :( Here I have the backtraces of all this existing threads of kontact after closing it: (gdb) info threads Id Target Id Frame 4Thread 0x7f4f92048700 (LWP 12365) kontact 0x7f4fa1583fdc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 3Thread 0x7f4f91747700 (LWP 12370) QThread 0x7f4fa6d6213d in poll () from /lib64/libc.so.6 2Thread 0x7f4f42601700 (LWP 22120) QInotifyFileSys 0x7f4fa6d6213d in poll () from /lib64/libc.so.6 * 1Thread 0x7f4fa99db780 (LWP 11840) kontact 0x7f4fa6d6213d in poll () from /lib64/libc.so.6 (gdb) bt #0 0x7f4fa6d6213d in poll () from /lib64/libc.so.6 #1 0x7f4fa05366bc in g_main_context_poll (n_fds=11, fds=0x56d72d0, timeout=15012, context=0x22430b0, priority=optimized out) at /var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:4007 #2 g_main_context_iterate (context=context@entry=0x22430b0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3708 #3 0x7f4fa05367ec in g_main_context_iteration (context=0x22430b0, may_block=1) at /var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3774 #4 0x7f4fa828e10e in QEventDispatcherGlib::processEvents (this=0x223e680, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #5 0x7f4fa75c5126 in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #6 0x7f4fa825ba2f in QEventLoop::processEvents (this=this@entry=0x7fff27fd22c0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f4fa825bd0d in QEventLoop::exec (this=this@entry=0x7fff27fd22c0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f4fa8261d2b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221 #9 0x7f4fa75158bc in QApplication::exec () at kernel/qapplication.cpp:3823 #10 0x004039d9 in main (argc=3, argv=0x7fff27fd25a8) at /var/tmp/portage/kde-base/kontact-4.13.0/work/kontact-4.13.0/kontact/src/main.cpp:219 (gdb) thread 2 [Switching to thread 2 (Thread 0x7f4f42601700 (LWP 22120))] #0 0x7f4fa6d6213d in poll () from /lib64/libc.so.6 (gdb) bt #0 0x7f4fa6d6213d in poll () from /lib64/libc.so.6 #1 0x7f4fa05366bc in g_main_context_poll (n_fds=2, fds=0x7f4f3c0029b0, timeout=-1, context=0x7f4f3c0009a0, priority=optimized out) at /var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:4007 #2 g_main_context_iterate (context=context@entry=0x7f4f3c0009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3708 #3 0x7f4fa05367ec in g_main_context_iteration (context=0x7f4f3c0009a0, may_block=1) at /var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3774 #4 0x7f4fa828e10e in QEventDispatcherGlib::processEvents (this=0x7f4f3c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #5 0x7f4fa825ba2f in QEventLoop::processEvents (this=this@entry=0x7f4f42600e20, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f4fa825bd0d in QEventLoop::exec (this=this@entry=0x7f4f42600e20, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f4fa8149f96 in QThread::exec (this=this@entry=0x2d8d280) at thread/qthread.cpp:536 #8 0x7f4fa823b1f8 in QInotifyFileSystemWatcherEngine::run (this=0x2d8d280) at io/qfilesystemwatcher_inotify.cpp:256 #9 0x7f4fa814c4dc in QThreadPrivate::start (arg=0x2d8d280) at thread/qthread_unix.cpp:338 #10 0x7f4fa1580033 in start_thread () from /lib64/libpthread.so.0 #11 0x7f4fa6d6bf0d in clone () from /lib64/libc.so.6 (gdb) thread 3 [Switching to thread 3 (Thread 0x7f4f91747700 (LWP 12370))] #0 0x7f4fa6d6213d in poll () from /lib64/libc.so.6 (gdb) bt #0 0x7f4fa6d6213d in poll () from /lib64/libc.so.6 #1 0x7f4fa05366bc in g_main_context_poll (n_fds=1, fds=0x7f4f8c0029c0, timeout=-1, context=0x7f4f8c0009a0, priority=optimized out) at /var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:4007 #2 g_main_context_iterate (context=context@entry=0x7f4f8c0009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3708 #3 0x7f4fa05367ec in g_main_context_iteration (context=0x7f4f8c0009a0, may_block=1) at /var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3774 #4 0x7f4fa828e0e3 in QEventDispatcherGlib::processEvents (this=0x7f4f8c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f4fa825ba2f in QEventLoop::processEvents (this=this@entry=0x7f4f91746e60, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f4fa825bd0d in QEventLoop::exec (this=this@entry=0x7f4f91746e60, flags=...) at kernel/qeventloop.cpp:204 #7
[kmail2] [Bug 322958] KMail: duplicate special folder causes endless loop Emitting defaultFoldersChanged
https://bugs.kde.org/show_bug.cgi?id=322958 Alexander Stein alexander.st...@informatik.tu-chemnitz.de changed: What|Removed |Added CC|alexander.stein@informatik. | |tu-chemnitz.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
[kmail2] [Bug 322958] KMail: duplicate special folder causes endless loop Emitting defaultFoldersChanged
https://bugs.kde.org/show_bug.cgi?id=322958 Alexander Stein alexander.st...@informatik.tu-chemnitz.de changed: What|Removed |Added CC||alexander.stein@informatik. ||tu-chemnitz.de --- Comment #9 from Alexander Stein alexander.st...@informatik.tu-chemnitz.de --- I've been hit by the same problem. I got 3 duplicates: inbox, outbox, sent-mail each in pure german language. When I started LANG=C kmail I could distinguish them without problem. But it would be nice to know how to delete those directories without waiting for ages in kmail for processing of each deletion job. Something in command line maybe? -- 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
[kmail2] [Bug 317795] New: Mail selection when using a quick search opens all threads in group
https://bugs.kde.org/show_bug.cgi?id=317795 Bug ID: 317795 Summary: Mail selection when using a quick search opens all threads in group Classification: Unclassified Product: kmail2 Version: 4.10.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: alexander.st...@informatik.tu-chemnitz.de This is a bit tricky to describe and to reproduce. Actually it seems this does only happen exactly once per mail. To be hold: I use the Fance with Clickable Status theme. Reproducible: Sometimes Steps to Reproduce: 1. Open all groups and close all threads. 2. Use quick search to filter for a specific word (e.g. about) 3. Now all groups _and_ threads are opened 4. Close all threads (e.g. Ctrl+,) 5. Click on an arbitrary mail Actual Results: All threads in the group of the selected mail (even if this mail doesn't have athread itself) are opened again which makes it very difficult to search in the mail for a specific one if the message list changes on every click, especially when browsing mailng lists with lots of traffic. Expected Results: The threads stay collapsed or in the previous state. -- 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
[kmail2] [Bug 316367] New: kmail2: Selecting INBOX again there is no message listed again
https://bugs.kde.org/show_bug.cgi?id=316367 Bug ID: 316367 Summary: kmail2: Selecting INBOX again there is no message listed again Classification: Unclassified Product: kmail2 Version: 4.10.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: alexander.st...@informatik.tu-chemnitz.de Ok, it's a bit hard to explain. After kmail starts I see all my mails in my INBOX. When i afterwards switch to a different folder in my IMAP ressource and then switch back to my INBOX no message at all is listed. Reproducible: Always Steps to Reproduce: 1. Restart Akonadi (once the problem occurs it doesn't not vanish until akonadi is restarted) 2. Launch kmail and see Mails in INBOX 3. Select a different folder 4. Select INBOX again Actual Results: I don't see my mails as in step 2. It seems this does only occur with a specific or at least with one of my mailboxes. Watching .xsession-errors meanwhile gives the following messages: This is from step 3: akonadi_imap_resource_5(30830)/kdepimlibs (kimap) RetrieveItemsTask::triggerExpunge: INBOX.Junk kmail2(30914) MessageList::StorageModel::StorageModel: Using model: Akonadi::EntityTreeModel [/usr/bin/nepomukservicestub] nepomukstorage(8143)/nepomuk (storage service) Nepomuk2::ResourceWatcherManager::watch: () (http://www.semanticdesktop.org/ontologies/2007/08/15/nao#hasTag;, http://www.semanticdesktop.org/ontologies/2007/08/15/nao#description;) () [/usr/bin/nepomukservicestub] nepomukstorage(8143)/nepomuk (storage service) Nepomuk2::ResourceWatcherManager::createConnection: () (QUrl(http://www.semanticdesktop.org/ontologies/2007/08/15/nao#hasTag;) , QUrl( http://www.semanticdesktop.org/ontologies/2007/08/15/nao#description; ) ) () akonadi_imap_resource_5(30830)/kdepimlibs (kimap) RetrieveItemsTask::onFinalSelectDone: No messages present so we are done akonadi_imap_resource_5(30830)/kdepimlibs (kimap) RetrieveCollectionMetadataTask::doStart: .Junk akonadi_imap_resource_5(30830)/kdepimlibs (kimap) RetrieveCollectionMetadataTask::doStart: Not refreshing because of timestamp kmail2(30914) KMKernel::instanceStatusChanged: A Resource started to synchronize, starting a mail check. kmail2(30914) KMKernel::slotProgressItemCompletedOrCanceled: Last resource finished syncing, mail check done Those are the messages from step 4: kmail2(30914) MessageList::StorageModel::StorageModel: Using model: Akonadi::EntityTreeModel [/usr/bin/nepomukservicestub] nepomukstorage(8143)/nepomuk (storage service) Nepomuk2::ResourceWatcherManager::watch: () (http://www.semanticdesktop.org/ontologies/2007/08/15/nao#hasTag;, http://www.semanticdesktop.org/ontologies/2007/08/15/nao#description;) () [/usr/bin/nepomukservicestub] nepomukstorage(8143)/nepomuk (storage service) Nepomuk2::ResourceWatcherManager::createConnection: () (QUrl(http://www.semanticdesktop.org/ontologies/2007/08/15/nao#hasTag;) , QUrl( http://www.semanticdesktop.org/ontologies/2007/08/15/nao#description; ) ) () kmail2(30914) KMKernel::instanceStatusChanged: A Resource started to synchronize, starting a mail check. akonadi_imap_resource_5(30830)/kdepimlibs (kimap) RetrieveItemsTask::triggerExpunge: INBOX akonadi_imap_resource_5(30830)/kdepimlibs (kimap) RetrieveItemsTask::onFinalSelectDone: UIDVALIDITY check failed ( -666705594 | 3628261702 ) refetching INBOX Object::connect: No such signal KIMAP::FetchJob::headersReceived( QString, QMapqint64, qint64, QMapqint64, qint64 QMapqint64, KIMAP::MessageFlags, QMapqint64, KIMAP::MessagePtr ) akonadi_imap_resource_5(30830)/kdepimlibs (kimap) RetrieveCollectionMetadataTask::doStart: .INBOX akonadi_imap_resource_5(30830)/kdepimlibs (kimap) RetrieveCollectionMetadataTask::doStart: Not refreshing because of timestamp kmail2(30914) KMKernel::slotProgressItemCompletedOrCanceled: Last resource finished syncing, mail check done To my view UIDVALIDITY check failed seems oddly. -- 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
[kmail2] [Bug 316367] kmail2: Selecting INBOX again there is no message listed again
https://bugs.kde.org/show_bug.cgi?id=316367 --- Comment #1 from Alexander Stein alexander.st...@informatik.tu-chemnitz.de --- Oh, an additional note. First occured in KDE 4.10.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 297115] New: kontact crashed when closed
https://bugs.kde.org/show_bug.cgi?id=297115 Bug ID: 297115 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact crashed when closed Classification: Unclassified OS: Linux Reporter: alexander.st...@informatik.tu-chemnitz.de Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) (Compiled from sources) Qt Version: 4.8.1 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: I closed kontact and after some minutes it simply crashed. I have used the parts from kmail akregator and knode. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f1959633760 (LWP 11421))] Thread 3 (Thread 0x7f194361a700 (LWP 11422)): #0 0x7f19511a964c in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f1955bd640c in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f1955bd6449 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7f19511a4dbc in start_thread () from /lib64/libpthread.so.0 #4 0x7f195693eded in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f1942d19700 (LWP 11423)): #0 0x7f1956935fb3 in poll () from /lib64/libc.so.6 #1 0x7f194ffda614 in g_main_context_iterate.clone.6 () from /usr/lib64/libglib-2.0.so.0 #2 0x7f194ffdaa7f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1957e766d6 in QEventDispatcherGlib::processEvents (this=0x1f466b0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f1957e431f2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f1957e434c5 in QEventLoop::exec (this=0x7f1942d18e20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f1957d32458 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f1957d349ed in QThreadPrivate::start (arg=0x1f45f90) at thread/qthread_unix.cpp:298 #8 0x7f19511a4dbc in start_thread () from /lib64/libpthread.so.0 #9 0x7f195693eded in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f1959633760 (LWP 11421)): [KCrash Handler] #6 parent (this=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:273 #7 parentWidget (this=0x288d920) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:1033 #8 QWidget::window (this=0x288d930) at kernel/qwidget.cpp:4337 #9 0x7f18f48cc51b in KNAccountManager::loadPasswordsAsync (this=0x2ad0d70) at /tmp/portage/kde-base/knode-4.8.1/work/knode-4.8.1/knode/knaccountmanager.cpp:213 #10 0x7f18f48c3a9b in KNode::Scheduler::addJob (this=optimized out, job=0x52d4720) at /tmp/portage/kde-base/knode-4.8.1/work/knode-4.8.1/knode/scheduler.cpp:63 #11 0x7f18f48c5bda in KNJobConsumer::emitJob (this=optimized out, j=0x52d4720) at /tmp/portage/kde-base/knode-4.8.1/work/knode-4.8.1/knode/knjobdata.cpp:46 #12 0x7f18f48d367e in KNGroupManager::checkAll (this=0x2e955d0, a=..., silent=true) at /tmp/portage/kde-base/knode-4.8.1/work/knode-4.8.1/knode/kngroupmanager.cpp:580 #13 0x7f18f48d376b in KNGroupManager::checkAll (this=0x2e955d0, id=1, silent=true) at /tmp/portage/kde-base/knode-4.8.1/work/knode-4.8.1/knode/kngroupmanager.cpp:588 #14 0x7f1957e5d1a1 in QMetaObject::activate (sender=0x2a0f4a0, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547 #15 0x7f1957e5b0f9 in QObject::event (this=0x2a0f4a0, e=optimized out) at kernel/qobject.cpp:1157 #16 0x7f19570dbc60 in QApplicationPrivate::notify_helper (this=0x1f3d030, receiver=0x2a0f4a0, e=0x7fffbaeb3350) at kernel/qapplication.cpp:4554 #17 0x7f19570e0f8d in QApplication::notify (this=optimized out, receiver=0x2a0f4a0, e=0x7fffbaeb3350) at kernel/qapplication.cpp:4415 #18 0x7f1958927251 in KApplication::notify (this=0x7fffbaeb36a0, receiver=0x2a0f4a0, event=0x7fffbaeb3350) at /tmp/portage/kde-base/kdelibs-4.8.1-r3/work/kdelibs-4.8.1/kdeui/kernel/kapplication.cpp:311 #19 0x7f1957e44aeb in QCoreApplication::notifyInternal (this=0x7fffbaeb36a0, receiver=0x2a0f4a0, event=0x7fffbaeb3350) at kernel/qcoreapplication.cpp:876 #20 0x7f1957e7966e in sendEvent (event=0x7fffbaeb3350, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #21 QTimerInfoList::activateTimers (this=0x1f49930) at kernel/qeventdispatcher_unix.cpp:611 #22 0x7f1957e75f3d in timerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:186 #23 0x7f1957e75f71 in idleTimerSourceDispatch
[Bug 297115] kontact crashed when closed
https://bugs.kde.org/show_bug.cgi?id=297115 --- Comment #3 from Alexander Stein alexander.st...@informatik.tu-chemnitz.de --- No, if I run KNode alone all works as expected. It seems it just occurs when using KNode-Kpart 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 296436] New: kontact crashed after closing
https://bugs.kde.org/show_bug.cgi?id=296436 Bug ID: 296436 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact crashed after closing Classification: Unclassified OS: Linux Reporter: alexander.st...@informatik.tu-chemnitz.de Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.7.4) KDE Platform Version: 4.7.4 (4.7.4) (Compiled from sources) Qt Version: 4.7.4 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: I just closed kontact. From backtrace you can see I had used the knode kpart, but the last open kpart was either kmail or akregator, I don't remember exactly. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7ff2d487a760 (LWP 27139))] Thread 3 (Thread 0x7ff2bf140700 (LWP 27140)): #0 0x7ff2ccbe832c in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7ff2d12b6ed4 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7ff2ccbe3c2c in start_thread () from /lib64/libpthread.so.0 #3 0x7ff2d1e2c7bd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7ff2be83f700 (LWP 27141)): #0 0x7ff2d1e394ff in __libc_enable_asynccancel () from /lib64/libc.so.6 #1 0x7ff2d1e23c68 in poll () from /lib64/libc.so.6 #2 0x7ff2cba21d50 in g_main_context_iterate.clone.6 () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff2cba22201 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7ff2d31e5b46 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x7ff2d31ba842 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7ff2d31baa84 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7ff2d30d333c in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7ff2d30d5b15 in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #9 0x7ff2ccbe3c2c in start_thread () from /lib64/libpthread.so.0 #10 0x7ff2d1e2c7bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff2d487a760 (LWP 27139)): [KCrash Handler] #6 0x7ff2d25ee58c in QWidget::window() const () from /usr/lib64/qt4/libQtGui.so.4 #7 0x7ff2a7ae93ab in KNAccountManager::loadPasswordsAsync() () from /usr/lib64/libknodecommon.so.4 #8 0x7ff2a7ae10a0 in KNode::Scheduler::addJob(KNJobData*) () from /usr/lib64/libknodecommon.so.4 #9 0x7ff2a7ae2bda in KNJobConsumer::emitJob(KNJobData*) () from /usr/lib64/libknodecommon.so.4 #10 0x7ff2a7af35bd in KNGroupManager::checkAll(boost::shared_ptrKNNntpAccount, bool) () from /usr/lib64/libknodecommon.so.4 #11 0x7ff2a7af378d in KNGroupManager::checkAll(int, bool) () from /usr/lib64/libknodecommon.so.4 #12 0x7ff2a7aee1a0 in KNNntpAccountIntervalChecking::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libknodecommon.so.4 #13 0x7ff2d31cf917 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #14 0x7ff2d31cf151 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #15 0x7ff2d25ade44 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #16 0x7ff2d25b292a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #17 0x7ff2d3c237d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #18 0x7ff2d31bb433 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #19 0x7ff2d31e82be in QTimerInfoList::activateTimers() () from /usr/lib64/qt4/libQtCore.so.4 #20 0x7ff2d31e5438 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/qt4/libQtCore.so.4 #21 0x7ff2cba21842 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #22 0x7ff2cba22020 in g_main_context_iterate.clone.6 () from /usr/lib64/libglib-2.0.so.0 #23 0x7ff2cba22201 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #24 0x7ff2d31e5b46 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #25 0x7ff2d26519be in QGuiEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtGui.so.4 #26 0x7ff2d31ba842 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #27 0x7ff2d31baa84 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
[Bug 295534] kmail2 randomly crashes upon browsing mail
https://bugs.kde.org/show_bug.cgi?id=295534 Alexander Stein alexander.st...@informatik.tu-chemnitz.de changed: What|Removed |Added CC||alexander.stein@informatik. ||tu-chemnitz.de --- Comment #6 from Alexander Stein alexander.st...@informatik.tu-chemnitz.de --- I have the same behavior with the current version 4.8.1 though my backtrace looks a bit different. Attaching it. I just browsed, deleted (moveing to trash) one mail and browsed again afterwards and it crashed then. -- 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 295534] kmail2 randomly crashes upon browsing mail
https://bugs.kde.org/show_bug.cgi?id=295534 --- Comment #7 from Alexander Stein alexander.st...@informatik.tu-chemnitz.de --- Created attachment 69660 -- https://bugs.kde.org/attachment.cgi?id=69660action=edit kontact/kmail crash while browsing -- 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 255388] Kmail filters dont work in incoming mail
https://bugs.kde.org/show_bug.cgi?id=255388 Alexander Stein alexander.st...@informatik.tu-chemnitz.de changed: What|Removed |Added CC||alexander.stein@informatik. ||tu-chemnitz.de --- Comment #43 from Alexander Stein alexander stein informatik tu-chemnitz de 2011-12-12 13:26:55 --- I upgraded to 4.7.3 (Gnetoo stable) from 4.4.11 and also noticed the Mail filter problem. Filter on POP3 accounts works, but on IMAP it doesn't. Appllying filters manually works, but only on already fetched mails. So Ctrl+A and Ctrl+J does only work on mais previosly fetched (same for click and shift+click to get a list). But i noticed something interesting: Filter _do_ work on IMAP accounts, if I filter on To, rather than List-ID for mailing lists. This obviously only works for initial mails and not replies. So I launched the Filter Log Viewer and noticed the following filter output on a mail i wrote to myself in To and CC: -- [14:24:26] Evaluating filter rules: (match any of the following) To contains linux-arm-kernel.lists.infradead.org CC contains linux-arm-kernel.lists.infradead.org [14:24:26] 0 = To contains linux-arm-kernel.lists.infradead.org (alexander.st...@informatik.tu-chemnitz.de) [14:24:26] 0 = CC contains linux-arm-kernel.lists.infradead.org () [14:24:26] Evaluating filter rules: (match all of the following) List-Id contains linux-arm-kernel.lists.infradead.org [14:24:26] 0 = List-Id contains linux-arm-kernel.lists.infradead.org () [14:24:26] Evaluating filter rules: (match all of the following) CC contains linux-ker...@vger.kernel.org [14:24:26] 0 = CC contains linux-ker...@vger.kernel.org () [14:24:26] Evaluating filter rules: (match any of the following) To contains linux-ker...@vger.kernel.org CC contains linux-ker...@vger.kernel.org [14:24:26] 0 = To contains linux-ker...@vger.kernel.org (alexander.st...@informatik.tu-chemnitz.de) [14:24:26] 0 = CC contains linux-ker...@vger.kernel.org () [14:24:26] Evaluating filter rules: (match all of the following) List-Id contains u-boot.lists.denx.de [14:24:26] 0 = List-Id contains u-boot.lists.denx.de () --- If I manually apply the filter, I get the following output: -- [14:25:42] Evaluating filter rules: (match all of the following) List-Id contains wireshark-dev.wireshark.org [14:25:42] 0 = List-Id contains wireshark-dev.wireshark.org () [14:25:42] Evaluating filter rules: (match any of the following) To contains linux-arm-kernel.lists.infradead.org CC contains linux-arm-kernel.lists.infradead.org [14:25:42] 0 = To contains linux-arm-kernel.lists.infradead.org (alexander.st...@informatik.tu-chemnitz.de) [14:25:42] 0 = CC contains linux-arm-kernel.lists.infradead.org (alexander.st...@informatik.tu-chemnitz.de) [14:25:42] Evaluating filter rules: (match all of the following) List-Id contains linux-arm-kernel.lists.infradead.org [14:25:42] 0 = List-Id contains linux-arm-kernel.lists.infradead.org () [14:25:42] Evaluating filter rules: (match all of the following) List-Id contains linux-can.vger.kernel.org [14:25:42] 0 = List-Id contains linux-can.vger.kernel.org () [14:25:42] Evaluating filter rules: (match all of the following) CC contains linux-ker...@vger.kernel.org [14:25:42] 0 = CC contains linux-ker...@vger.kernel.org (alexander.st...@informatik.tu-chemnitz.de) [14:25:42] Evaluating filter rules: (match any of the following) To contains linux-ker...@vger.kernel.org CC contains linux-ker...@vger.kernel.org [14:25:42] 0 = To contains linux-ker...@vger.kernel.org (alexander.st...@informatik.tu-chemnitz.de) [14:25:42] 0 = CC contains linux-ker...@vger.kernel.org (alexander.st...@informatik.tu-chemnitz.de) [14:25:42] Evaluating filter rules: (match all of the following) List-Id contains u-boot.lists.denx.de [14:25:42] 0 = List-Id contains u-boot.lists.denx.de () --- It seems not all E-Mail headers are passed to the filter upon initial mail reception. -- 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 222878] kontact process does not exit after closing kontact window in every case
https://bugs.kde.org/show_bug.cgi?id=222878 --- Comment #15 from Alexander Stein alexander stein informatik tu-chemnitz de 2011-07-14 16:42:33 --- I still observed this running Kontact 4.6.1 now. But eventually I get a crash report. Seems to be related to KNode somehow. Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f3dd9684760 (LWP 3862))] Thread 2 (Thread 0x7f3dc3412700 (LWP 3863)): #0 0x7f3dd191c85c in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f3dd5fa4eac in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f3dd5fa4ee9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7f3dd1917dba in start_thread () from /lib64/libpthread.so.0 #4 0x7f3dd6a9e02d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f3dd9684760 (LWP 3862)): [KCrash Handler] #6 parent (this=0x177c220) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:250 #7 parentWidget (this=0x177c220) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:1022 #8 QWidget::window (this=0x177c220) at kernel/qwidget.cpp:4255 #9 0x7f3dba9a0fd4 in KNAccountManager::wallet () at /tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knaccountmanager.cpp:250 #10 0x7f3dba9a4d89 in KNServerInfo::readPassword (this=0x25f5a40) at /tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knserverinfo.cpp:167 #11 0x7f3dba9a58c8 in KNServerInfo::readConf (this=0x25f5a40, conf=...) at /tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knserverinfo.cpp:66 #12 0x7f3dba9a66f6 in KNNntpAccount::readInfo (this=0x25f5a10, confPath=...) at /tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knnntpaccount.cpp:110 #13 0x7f3dba9a2657 in KNAccountManager::loadAccounts (this=value optimized out) at /tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knaccountmanager.cpp:73 #14 0x7f3dba9a2a68 in KNAccountManager::KNAccountManager (this=0x203b440, gm=value optimized out, parent=value optimized out) at /tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knaccountmanager.cpp:40 #15 0x7f3dbaa24b8d in KNGlobals::accountManager (this=0x175c0b0) at /tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knglobals.cpp:113 #16 0x7f3dba9a7e44 in KNGroupManager::checkAll (this=0x133b4f0, id=1, silent=true) at /tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/kngroupmanager.cpp:587 #17 0x7f3dba9a6448 in KNNntpAccountIntervalChecking::qt_metacall (this=0x1a83b20, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=value optimized out) at /tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1_build/knode/knnntpaccount.moc:73 #18 0x7f3dd71e45ea in QMetaObject::activate (sender=0x14f1770, m=value optimized out, local_signal_index=value optimized out, argv=0x6) at kernel/qobject.cpp:3278 #19 0x7f3dd71dc999 in QObject::event (this=0x14f1770, e=0x0) at kernel/qobject.cpp:1181 #20 0x7f3dd7bcd2fc in QApplicationPrivate::notify_helper (this=0xead4d0, receiver=0x14f1770, e=0x7fffed2a36a0) at kernel/qapplication.cpp:4462 #21 0x7f3dd7bd5627 in QApplication::notify (this=0x7fffed2a39f0, receiver=0x14f1770, e=0x7fffed2a36a0) at kernel/qapplication.cpp:4341 #22 0x7f3dd89dc730 in KApplication::notify (this=0x7fffed2a39f0, receiver=0x14f1770, event=0x7fffed2a36a0) at /tmp/portage/kde-base/kdelibs-4.6.5/work/kdelibs-4.6.5/kdeui/kernel/kapplication.cpp:311 #23 0x7f3dd71c9deb in QCoreApplication::notifyInternal (this=0x7fffed2a39f0, receiver=0x14f1770, event=0x7fffed2a36a0) at kernel/qcoreapplication.cpp:731 #24 0x7f3dd71fcd1a in sendEvent (this=0xebb380) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #25 QTimerInfoList::activateTimers (this=0xebb380) at kernel/qeventdispatcher_unix.cpp:604 #26 0x7f3dd71f9a34 in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:184 #27 0x7f3dd13bdcf9 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x7f3dd13c2238 in g_main_context_iterate () from /usr/lib64/libglib-2.0.so.0 #29 0x7f3dd13c23de in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x7f3dd71f971e in QEventDispatcherGlib::processEvents (this=0xeabcf0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:422 #31 0x7f3dd7c8bd46 in QGuiEventDispatcherGlib::processEvents (this=0x177c220, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #32 0x7f3dd71c89f2 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #33 0x7f3dd71c8dbd in QEventLoop::exec (this=0x7fffed2a3960, flags=) at kernel/qeventloop.cpp:201 #34 0x7f3dd71cb65b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008 #35 0x00403e6a in main (argc=value optimized out, argv=value optimized out) at /tmp/portage/kde-base/kontact-4.6.1/work/kontact-4.6.1/kontact/src
[Bug 222878] kontact process does not exit after closing kontact window in every case
https://bugs.kde.org/show_bug.cgi?id=222878 --- Comment #2 from Alexander Stein alexander stein informatik tu-chemnitz de 2010-01-27 19:56:25 --- (In reply to comment #1) Do you have IMAP accounts in kmail? I have the same behavior on debian unstable with kde 4.3.4. I guess, it may be related to bug https://bugs.kde.org/show_bug.cgi?id=186936, because kontact on my system leaves processes after exit only after connection loss. Yes, I'm using (2) IMAP accounts. But I can't stay whether I got connection losses or not. -- 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 222878] New: kontact process does not exit after closing kontact window in every case
https://bugs.kde.org/show_bug.cgi?id=222878 Summary: kontact process does not exit after closing kontact window in every case Product: kontact Version: 4.3 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: alexander.st...@informatik.tu-chemnitz.de Version:(using KDE 4.3.4) Compiler: gcc-Version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) OS:Linux Installed from:Gentoo Packages Sometimes when I use kontact and want to close it. The kontact process doesn't exit but the window isn't shown anymore. Thus i cannot restart kontact again before killing the process left. Upon using kontact I usually use kmail, knode and akregator. Nothing special. I attached via gdb to the left over process and this is it's backtrace: #0 0x7fe5d7992896 in poll () from /lib/libc.so.6 #1 0x7fe5d38c43b9 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #2 0x7fe5d38c468c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fe5d8745c5f in QEventDispatcherGlib::processEvents (this=0x14e6b60, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:327 #4 0x7fe5d955355f in QGuiEventDispatcherGlib::processEvents (this=0x3ac7be0, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202 #5 0x7fe5d871d882 in QEventLoop::processEvents (this=value optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7fe5d871da1c in QEventLoop::exec (this=0x7fff65eadb50, flags=...) at kernel/qeventloop.cpp:197 #7 0x7fe5d8722396 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #8 0x0040405a in main (argc=1, argv=0x7fff65eae0f8) at /var/tmp/portage/kde-base/kontact-4.3.4/work/kontact-4.3.4/kontact/src/main.cpp:218 -- 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
