[Akonadi] [Bug 322741] adding a large maildir to fresh akonadi setup never results in visible mail
https://bugs.kde.org/show_bug.cgi?id=322741 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- you use a very old kontact package/akonadi package. we will release in some days 4.11/1.10.1 so try with new packages. -- 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
[kontact] [Bug 322760] New: Kontact crashes upon shutdown when knode was enabled
https://bugs.kde.org/show_bug.cgi?id=322760 Bug ID: 322760 Summary: Kontact crashes upon shutdown when knode was enabled Classification: Unclassified Product: kontact Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: f...@christian-reiner.info Application: kontact (4.10.5) KDE Platform Version: 4.10.5 release 4 Qt Version: 4.8.4 Operating System: Linux 3.7.10-1.16-desktop x86_64 Distribution: openSUSE 12.3 (x86_64) -- Information about the crash: - What I was doing when the application crashed: Every time I shutdown the kontact shell I get a KCrash handler after a while (often 1-2 minutes after the shutdown). - Custom settings of the application: I have the impression that this crash only happens, when knode had been enabled (used) inside that kontact session. This issue has been around for a few years now (if I remember correctly). Here I am referring to the dependency that knode has to be enabled to produce a crash. I failed to find prior reports for this although I remember I made one myself. Maybe they got removed because of being older? The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f14fa1d07c0 (LWP 9321))] Thread 5 (Thread 0x7f14ddabc700 (LWP 9322)): #0 0x7f14f193a964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f14f69522f0 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f14f6952329 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f14f1936e0f in start_thread () from /lib64/libpthread.so.0 #4 0x7f14f77327dd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f14dd1bb700 (LWP 9323)): #0 0x7f14f193a964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f14f66d0157 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7f14f697981e in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7f14f1936e0f in start_thread () from /lib64/libpthread.so.0 #4 0x7f14f77327dd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f148b209700 (LWP 9334)): #0 0x7fff7f7ff847 in clock_gettime () #1 0x7f14f774453d in clock_gettime () from /lib64/libc.so.6 #2 0x7f14f8a8bd94 in ?? () from /usr/lib64/libQtCore.so.4 #3 0x7f14f8b60bed in ?? () from /usr/lib64/libQtCore.so.4 #4 0x7f14f8b60f33 in ?? () from /usr/lib64/libQtCore.so.4 #5 0x7f14f8b5f99c in ?? () from /usr/lib64/libQtCore.so.4 #6 0x7f14f8b5fa45 in ?? () from /usr/lib64/libQtCore.so.4 #7 0x7f14f092a338 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #8 0x7f14f092a9cb in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7f14f092abc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7f14f8b602e6 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #11 0x7f14f8b30adf in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #12 0x7f14f8b30d68 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #13 0x7f14f8a330f0 in QThread::exec() () from /usr/lib64/libQtCore.so.4 #14 0x7f14f8a360cc in ?? () from /usr/lib64/libQtCore.so.4 #15 0x7f14f1936e0f in start_thread () from /lib64/libpthread.so.0 #16 0x7f14f77327dd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f148ba0a700 (LWP 17576)): #0 0x7fff7f7ff847 in clock_gettime () #1 0x7f14f774453d in clock_gettime () from /lib64/libc.so.6 #2 0x7f14f8a8bd94 in ?? () from /usr/lib64/libQtCore.so.4 #3 0x7f14f8b60bed in ?? () from /usr/lib64/libQtCore.so.4 #4 0x7f14f8b60f33 in ?? () from /usr/lib64/libQtCore.so.4 #5 0x7f14f8b5f99c in ?? () from /usr/lib64/libQtCore.so.4 #6 0x7f14f8b5fa45 in ?? () from /usr/lib64/libQtCore.so.4 #7 0x7f14f092a338 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #8 0x7f14f092a9cb in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7f14f092abc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7f14f8b602e6 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #11 0x7f14f8b30adf in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #12 0x7f14f8b30d68 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #13 0x7f14f8a330f0 in QThread::exec() () from /usr/lib64/libQtCore.so.4 #14 0x7f14f44caa4e in KIO::NameLookUpThread::run (this=0x46bdb20) at /usr/src/debug/kdelibs-4.10.5/kio/kio/hostinfo.cpp:226 #15 0x7f14f8a360cc in ?? () from
[akregator] [Bug 322761] New: Akregator crashed when web page was refreshed
https://bugs.kde.org/show_bug.cgi?id=322761 Bug ID: 322761 Summary: Akregator crashed when web page was refreshed Classification: Unclassified Product: akregator Version: 4.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: b...@pcwhite.com Application: akregator (4.10.5) KDE Platform Version: 4.10.5 Qt Version: 4.8.4 Operating System: Linux 3.8.0-26-generic x86_64 Distribution: Ubuntu 13.04 -- Information about the crash: - What I was doing when the application crashed: I clicked on a link in the preview frame to open up a full web page in a new tab. That page included an embedded video which didn't play. I refreshed the page hoping that I could view the video without having to open up a web browser. Akregator immediately crashed. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f2469a907c0 (LWP 25341))] Thread 2 (Thread 0x7f2445599700 (LWP 25344)): #0 0x7f246148d075 in __GI___pthread_mutex_lock (mutex=0x7f244a60) at pthread_mutex_lock.c:95 #1 0x7f2460ff75c1 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2460fb790b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2460fb80fe in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2460fb8304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2467253036 in QEventDispatcherGlib::processEvents (this=0x7f2448c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f246722338f in QEventLoop::processEvents (this=this@entry=0x7f2445598d90, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f2467223618 in QEventLoop::exec (this=this@entry=0x7f2445598d90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f2467125410 in QThread::exec (this=this@entry=0x2134790) at thread/qthread.cpp:542 #9 0x7f2467204edf in QInotifyFileSystemWatcherEngine::run (this=0x2134790) at io/qfilesystemwatcher_inotify.cpp:256 #10 0x7f2467127bec in QThreadPrivate::start (arg=0x2134790) at thread/qthread_unix.cpp:338 #11 0x7f246148af8e in start_thread (arg=0x7f2445599700) at pthread_create.c:311 #12 0x7f2466649e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7f2469a907c0 (LWP 25341)): [KCrash Handler] #6 0x7f246365eb14 in KHTMLPart::onlyLocalReferences (this=this@entry=0x8708910) at ../../khtml/khtml_part.cpp:2794 #7 0x7f246365ebc9 in KHTMLPart::jScriptEnabled (this=0x8708910) at ../../khtml/khtml_part.cpp:1101 #8 0x7f246366000b in KHTMLPart::jScript (this=0x8708910) at ../../khtml/khtml_part.cpp:1133 #9 0x7f24636eeac7 in DOM::NodeImpl::dispatchEvent (this=this@entry=0x21cf040, evt=evt@entry=0x8461e50, exceptioncode=@0x71bbade4: 0, tempEvent=tempEvent@entry=true) at ../../khtml/xml/dom_nodeimpl.cpp:406 #10 0x7f2463651fd6 in KHTMLView::dispatchMouseEvent (this=this@entry=0x8c95f30, eventId=eventId@entry=4, targetNode=0x21cf040, targetNodeNonShared=optimized out, cancelable=cancelable@entry=true, detail=1, _mouse=_mouse@entry=0x71d0, setUnder=setUnder@entry=true, mouseEventType=mouseEventType@entry=0, orient=orient@entry=0) at ../../khtml/khtmlview.cpp:3607 #11 0x7f2463658007 in KHTMLView::mousePressEvent (this=0x8c95f30, _mouse=0x71d0) at ../../khtml/khtmlview.cpp:1233 #12 0x7f2467c5ba70 in QWidget::event (this=this@entry=0x8c95f30, event=event@entry=0x71d0) at kernel/qwidget.cpp:8371 #13 0x7f246800e316 in QFrame::event (this=0x8c95f30, e=0x71d0) at widgets/qframe.cpp:557 #14 0x7f2463649cb5 in KHTMLView::widgetEvent (this=0x8c95f30, e=optimized out) at ../../khtml/khtmlview.cpp:2213 #15 0x7f2463655fa0 in KHTMLView::eventFilter (this=0x8c95f30, o=0xd0bb420, e=0x71d0) at ../../khtml/khtmlview.cpp:2058 #16 0x7f24672247a6 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=this@entry=0x19d8b00, receiver=receiver@entry=0xd0bb420, event=event@entry=0x71d0) at kernel/qcoreapplication.cpp:1056 #17 0x7f2467c0e8bc in QApplicationPrivate::notify_helper (this=this@entry=0x19d8b00, receiver=receiver@entry=0xd0bb420, e=e@entry=0x71d0) at kernel/qapplication.cpp:4563 #18 0x7f2467c11a33 in QApplication::notify (this=this@entry=0x71bbc900, receiver=receiver@entry=0xd0bb420, e=e@entry=0x71d0) at kernel/qapplication.cpp:4110 #19 0x7f246891a1a6 in KApplication::notify (this=0x71bbc900, receiver=0xd0bb420, event=0x71d0) at ../../kdeui/kernel/kapplication.cpp:311 #20 0x7f246722463e in QCoreApplication::notifyInternal (this=0x71bbc900, receiver=receiver@entry=0xd0bb420,
[Akonadi] [Bug 288605] Mail Dispatcher Agent went offline for unknown reason
https://bugs.kde.org/show_bug.cgi?id=288605 --- Comment #3 from piedro piedro.kul...@googlemail.com --- Plz, can someone confirm this? I run KDE on Arch, it's version 4.10.5. This bug is not random: Anytime I leave my box running for more than a day (this is an estimate) the akonadi agent has to be restarted. And, by the way, this is true for: - mail dipatcher agent - mail filter agent (filtering always stops at a certain runtime) - local notes (for kjots: it stops showing the notes altogether and has to be restarted to work again) - ... there may be more but these are the agents I use mostly use Years ago I had a similar problem. That had to do with the missing entry wait_timeout=31536000 in the mysql.conf. But now I checked in the folder ~/.local/share/akonadi - the file mysql.conf is present and has the above entry. thx for reading, piedro -- 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
[Akonadi] [Bug 301182] Mail dispatcher agent stops working
https://bugs.kde.org/show_bug.cgi?id=301182 --- Comment #7 from piedro piedro.kul...@googlemail.com --- I run KDE on Arch, it's version 4.10.5. This bug is not random: Anytime I leave my box running for more than a day (this is an estimate) the akonadi agent has to be restarted. And, by the way, this is true for: - mail dipatcher agent - mail filter agent (filtering always stops at a certain runtime) - local notes (for kjots: it stops showing the notes altogether and has to be restarted to work again) - ... there may be more but these are the agents I use mostly use Years ago I had a similar problem. That had to do with the missing entry wait_timeout=31536000 in the mysql.conf. But now I checked in the folder ~/.local/share/akonadi - the file mysql.conf is present and has the above entry. thx for reading, piedro -- 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
[kdelibs] [Bug 272413] Akonadi crash
https://bugs.kde.org/show_bug.cgi?id=272413 Christoph Feck christ...@maxiom.de changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #3 from Christoph Feck christ...@maxiom.de --- No response, changing status. Please reopen, if you have more information. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 305987] Could not create collection when adding new top-level mailbox for IMAP account:
https://bugs.kde.org/show_bug.cgi?id=305987 Chao Feng rainofch...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #11 from Chao Feng rainofch...@gmail.com --- Same issue here. But it show up after I restart Kmail. Is this happen to you too? -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 322772] New: kmail should treat attached text/plain files named *.asc in signed and/or encrypted mails as mime type application/pgp-keys
https://bugs.kde.org/show_bug.cgi?id=322772 Bug ID: 322772 Summary: kmail should treat attached text/plain files named *.asc in signed and/or encrypted mails as mime type application/pgp-keys Classification: Unclassified Product: kmail2 Version: 4.11 rc2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: msch...@gentoo.org I assume that this is not a bug in kmail at all, as attached plaintext keys should be marked as application/pgp-keys instead of text/plain. But in reality there are Encryption gateways out there which attach peoples pgp-keys as text/plain However, to increase interoperability and usability it might be good to some more intelligence: Would it be complicated to implement if kmail checked the file-extension of an attachement and if the message is signed and/or encryped, and if a text/plain part is detected with a filename like *.asc, then handle that part if it was application/pgp-keys? That way one could just import the key by klicking on it... Ideas? Reproducible: Always -- 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 322772] kmail should treat attached text/plain files named *.asc in signed and/or encrypted mails as mime type application/pgp-keys
https://bugs.kde.org/show_bug.cgi?id=322772 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- could you send me in private a email with it ? I will look at what I can do. thanks -- 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 322772] kmail should treat attached text/plain files named *.asc in signed and/or encrypted mails as mime type application/pgp-keys
https://bugs.kde.org/show_bug.cgi?id=322772 --- Comment #2 from Marc Schiffbauer msch...@gentoo.org --- Hi Laurent, done! Thx. -- 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
[Akonadi] [Bug 308008] Filtering from checked accounts only not working for POP3 accounts
https://bugs.kde.org/show_bug.cgi?id=308008 Christian Trippe christiande...@web.de changed: What|Removed |Added CC||christiande...@web.de --- Comment #8 from Christian Trippe christiande...@web.de --- This bug is only partially fixed for me with KDE 4.11 RC1. It works if the destination folder of the pop3 resource is the inbox, but not if it is another folder. Should I open a new report for this or should this one get reopened? -- 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 317529] CPU hog when hovering over some items in the Tools menu
https://bugs.kde.org/show_bug.cgi?id=317529 Josh Liberty j...@vegansite.net changed: What|Removed |Added CC||j...@vegansite.net --- Comment #2 from Josh Liberty j...@vegansite.net --- Confirmed, something is very wrong in that menu. Note this also causes a noticeable UI delay when hovering over items and when opening the menu. -- 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
[akregator] [Bug 322749] akgregator crashes when trying to import OPML file
https://bugs.kde.org/show_bug.cgi?id=322749 --- Comment #2 from Kurt V. Hindenburg kurt.hindenb...@gmail.com --- 'Version 4.11 pre' imported the .opml file OK here. -- 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
