[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 --- Comment #40 from Rodney Baker --- It is working for me (plain text emails around 41MB - log files from an automated backup script), but it is very slow to load the email. The CPU fan does ramp up slightly when doing so, but at least it loads, and once it loads, scrolling is usable. By comparison, "View Message Source" uses almost no CPU or RAM, and displays the message pretty much instantly. Thunderbird displays the message absolutely fine, too, with no noticeable hit on system resources or CPU load. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 --- Comment #33 from Rodney Baker --- Sorry, it's taken a while for me to be able to verify on my system due to other issues, but I can confirm it is now working as expected. Thanks for your work - much appreciated! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 --- Comment #29 from Rodney Baker --- So, is it possible to make it conditional i.e. below a certain size threshold, use the preferred method, but if a message is above that threshold, use the alternative (working but reverted) method from this patch? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 Rodney Baker changed: What|Removed |Added Version|5.6.0 |5.14.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 Rodney Baker changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #26 from Rodney Baker --- REGRESSION - this was fixed but the issue has recurred in version 5.14.1 (20.04.0). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 Rodney Baker changed: What|Removed |Added Summary|Large messages don't|REGRESSION: Large messages |display in the viewer pane |don't display in the viewer |(eg. New Tumbleweed |pane (eg. New Tumbleweed |snapshot 20171117 |snapshot 20171117 |released!) |released!) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 --- Comment #24 from Rodney Baker --- Tested locally and now works as expected. Many thanks, Laurent! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 --- Comment #14 from Rodney Baker --- On Monday, 13 May 2019 7:55:39 ACST Sandro Knauß wrote: > https://bugs.kde.org/show_bug.cgi?id=387061 > > --- Comment #13 from Sandro Knauß --- > (In reply to Rodney Baker from comment #12) > > > I have no idea where or how to do that. I tried cloning the kmail source > > but I can find neither messagelib nor any instance (using grep -r) of a > > call to QWebEngineView::setHtml within kmail. My programming experience > > is limited to Visual Basic and Ruby, so this might be a step too far at > > the moment. > kdepim is about 50 repos. The repo you search is > https://cgit.kde.org/messagelib.git. > And the file: > messageviewer/src/htmlwriter/webengineparthtmlwriter.cpp:l66 > To build up a development environment look at: > https://community.kde.org/KDE_PIM/Docker Thanks for the pointer. I'm a complete newbie when it comes to c++, so this may be beyond me, but I'll see how I go. So far what I see doesn't make a lot of sense, but I guess I'll have to compare the docs for the two methods and see what needs to change, first. Hopefully this doesn't turn out to be like peeling an onion (layer upon layer upon layer...). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 --- Comment #12 from Rodney Baker --- I have no idea where or how to do that. I tried cloning the kmail source but I can find neither messagelib nor any instance (using grep -r) of a call to QWebEngineView::setHtml within kmail. My programming experience is limited to Visual Basic and Ruby, so this might be a step too far at the moment. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 --- Comment #10 from Rodney Baker --- Still a problem in version 5.10.3, Qt5.12.2, KDE Frameworks 5.57.0. Any target version for the fix? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 --- Comment #14 from Rodney Baker --- Updated version on bug. Still no developer activity by the looks of it. Care factor for kmail2 bugs seems very low. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Rodney Baker changed: What|Removed |Added Version|5.7.0 |5.10.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Rodney Baker <rodney.ba...@iinet.net.au> changed: What|Removed |Added Component|general |commands and actions --- Comment #9 from Rodney Baker <rodney.ba...@iinet.net.au> --- The silence is deafening... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388871] New: KMail reports message send failure, but sends multiple copies of same message
https://bugs.kde.org/show_bug.cgi?id=388871 Bug ID: 388871 Summary: KMail reports message send failure, but sends multiple copies of same message Product: kmail2 Version: 5.7.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: rodney.ba...@iinet.net.au Target Milestone: --- When sending a 6.2MB message with attachments, KMail2 reported "Failed to transport message; connection to server lost." The email was sent to 4 recipients (1 "To:" address, 1 CC and 2 BCC). The message remained in the outbox folder until moved to Drafts. Despite the claimed failure, each recipient received 6 complete copies of the same 6.2MB email. Verified the failure by sending the same message from the drafts folder to myself - I received 2 copies. The same happened with other large emails >2MB (not sure exactly what the threshold is). All emails were successfully and correctly sent from Thunderbird. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Rodney Baker <rodney.ba...@iinet.net.au> changed: What|Removed |Added Version|5.6.3 |5.7.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Rodney Baker <rodney.ba...@iinet.net.au> changed: What|Removed |Added Version|5.5.3 |5.6.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 --- Comment #8 from Rodney Baker <rodney.ba...@iinet.net.au> --- Likewise - is anyone actually working on this bug? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Rodney Baker <rodney.ba...@iinet.net.au> changed: What|Removed |Added Version|5.4.1 |5.5.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 --- Comment #6 from Rodney Baker <rodney.ba...@iinet.net.au> --- Version 5.5.3, I now cannot even use View Source to display large messages. The log file messages I'm speaking of are ~22MB. They are plain text messages and show the "No HMTL Message" side bar but the messages are never displayed, even with View Source. I concur - this is getting worse, not better. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Rodney Baker <rodney.ba...@iinet.net.au> changed: What|Removed |Added Version|5.4.0 |5.4.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 --- Comment #2 from Rodney Baker <rodney.ba...@iinet.net.au> --- In version 5.4.2 this behaviour has now changed. The message is still never displayed, but at least KMail does not hang, and if I open the message and select "View Source" I can view the entire message (and it loads very quickly). Nothing I can do, however, makes it display in the preview window or by opening the message, except when viewing the message source. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Rodney Baker <rodney.ba...@iinet.net.au> changed: What|Removed |Added CC||rodney.ba...@iinet.net.au -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 375445] New: KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Bug ID: 375445 Summary: KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server Product: kmail2 Version: 5.4.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rodney.ba...@iinet.net.au Target Milestone: --- KMail2 hangs when trying to read large text-based emails (~22MB Log files) from a Dovecot IMAP server. The emails are never shown in the preview window and KMail2 becomes unresponsive. CPU Usage for the KMail2 process goes to 100% and stays there. Memory usage gradually increases as the email is presumably parsed but the preview is never displayed, even after CPU usage eventually returns to normal and KMail again becomes responsive (takes >5 minutes). At the same time, none of the akonadi processes show unusual CPU or memory usage (if anything, perhaps unusually low, as if it is not actually doing a whole lot). By comparison, Mozilla Thunderbird can read the same emails from the same IMAP server and account without issues. The initial preview is shown immediately as the rest of the message is parsed (which does take some time, but Thunderbird remains responsive). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 --- Comment #6 from Rodney Baker <rodney.ba...@iinet.net.au> --- (In reply to Frits Spieker from comment #5) > Not to be blunt, but deleting all imap accounts, dropping and recreating the > akonadi database and recreating of all imap accounts is not what I would > call resolved. It is a messy workaround and a very messy one at that. What > about users that also still have pop3 email boxes? What about the less > technical inclined? > It's a messy workaround which hides a messy bug which is in need of a proper > fix. In my case it is a resolution because it was most likely caused by an upgrade from 4.14.x to 5.23.x. There are documented incompatibilities between KDE4 and KF5 versions of KDE PIM that I was not aware of when I upgraded. This was the likely cause of the instability. There is a recommended upgrade procedure which I'd not followed because I was not aware of it. Deleting/recreating the akonadi database has solved the problem in my case. YMMV. I'm happy to leave this open for the devs to review - the cause of your issue may be different. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 --- Comment #4 from Rodney Baker <rodney.ba...@iinet.net.au> --- This now seems to be resolved for me after deleting all imap accounts in KMail, then dropping and recreating the akonadi database, then recreating the imap accounts. Since doing that I've not seen KMail2 lose connection to the akonadi server. I will continue to monitor and if it remains stable I will mark this as resolved. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 367846] KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 Rodney Baker <rodney.ba...@iinet.net.au> changed: What|Removed |Added CC||rodney.ba...@iinet.net.au Version|unspecified |16.04 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 367846] New: KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes.
https://bugs.kde.org/show_bug.cgi?id=367846 Bug ID: 367846 Summary: KMail2 and akonadiconsole continuously lose connection to akonadi server - happens every 30 secs to 2 minutes. Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: rodney.ba...@iinet.net.au After updating to kmail2 v5.2.3 and the latest version of akonadi in openSuSE Tumbleweed, kmail and akonadiconsold continuously lose connection to the akonadi server for 10-45 seconds at a time. This appears to happen at intervals of anywhere from 10-60 seconds. Running akonadiconsole from the command line reveals the following output; 0:35:15 bakerr@mako:~> akonadiconsole org.kde.akonadi.ETM: GEN true true true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Subtree: 254 QSet(254) org.kde.akonadi.ETM: Subtree: 114 QSet(114) org.kde.akonadi.ETM: Subtree: 263 QSet(263) org.kde.akonadi.ETM: Fetch job took 5752 msec org.kde.akonadi.ETM: was collection fetch job: collections: 3 org.kde.akonadi.ETM: first fetched collection: "Google Calendar" org.kde.akonadi.ETM: Subtree: 103 QSet(103) org.kde.akonadi.ETM: Subtree: 142 QSet(142) org.kde.akonadi.ETM: Subtree: 262 QSet(262) org.kde.akonadi.ETM: Subtree: 254 QSet(254) org.kde.akonadi.ETM: Subtree: 87 QSet(145, 87, 102, 89, 88, 90, 93, 92, 95, 94, 97, 96, 99, 98, 101, 100) org.kde.akonadi.ETM: Subtree: 105 QSet(105) org.kde.akonadi.ETM: Subtree: 104 QSet(104, 149, 151, 150) org.kde.akonadi.ETM: Subtree: 148 QSet(148) org.kde.akonadi.ETM: Subtree: 106 QSet(107, 106, 109, 108, 113, 110, 112) org.kde.akonadi.ETM: Subtree: 1 QSet(1, 139) org.kde.akonadi.ETM: Subtree: 168 QSet(236, 239, 238, 225, 224, 227, 226, 229, 228, 231, 230, 249, 248, 241, 240, 243, 242, 245, 244, 247, 246, 169, 168, 171, 170, 173, 172, 175, 174, 185, 184, 187, 186, 189, 188, 191, 190, 177, 176, 179, 178, 181, 180, 183, 182, 201, 200, 203, 202, 205, 204, 207, 206, 193, 192, 195, 194, 197, 196, 199, 198, 217, 216, 219, 218, 221, 220, 223, 222, 209, 208, 211, 210, 213, 212, 215, 214, 233, 235, 234, 237) org.kde.akonadi.ETM: Subtree: 114 QSet(114) org.kde.akonadi.ETM: Subtree: 250 QSet(251, 250, 253, 252) org.kde.akonadi.ETM: Subtree: 263 QSet(263) org.kde.akonadi.ETM: Fetch job took 5759 msec org.kde.akonadi.ETM: was collection fetch job: collections: 122 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: Subtree: 254 QSet(254) org.kde.akonadi.ETM: Subtree: 114 QSet(114) org.kde.akonadi.ETM: Fetch job took 5758 msec org.kde.akonadi.ETM: was collection fetch job: collections: 2 org.kde.akonadi.ETM: first fetched collection: "Google Calendar" org.kde.akonadi.ETM: Subtree: 103 QSet(103) org.kde.akonadi.ETM: Subtree: 142 QSet(142) org.kde.akonadi.ETM: Subtree: 262 QSet(262) org.kde.akonadi.ETM: Subtree: 105 QSet(105) org.kde.akonadi.ETM: Fetch job took 5759 msec org.kde.akonadi.ETM: was collection fetch job: collections: 4 org.kde.akonadi.ETM: first fetched collection: "Notes" akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" org.kde.akonadi.ETM: GEN true true true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Subtree: 254 QSet(254) org.kde.akonadi.ETM: Subtree: 114 QSet(114) org.kde.akonadi.ETM: Subtree: 263 QSet(263) org.kde.akonadi.ETM: Fetch job took 1861 msec org.kde.akonadi.ETM: was collection fetch job: collections: 3 org.kde.akonadi.ETM: first fetched collection: "Google Calendar" org.kde.akonadi.ETM: Subtree: 103 QSet(103) org.kde.akonadi.ETM: Subtree: 142
[kmail2] [Bug 357150] New: KMail crash on opening
https://bugs.kde.org/show_bug.cgi?id=357150 Bug ID: 357150 Summary: KMail crash on opening Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rodney.ba...@iinet.net.au Application: kmail (4.14.9) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 4.3.3-2.gdb72752-default x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: KMail had hung while emptying the Trash folders on 2 IMAP accounts. It appeared to close normally via File-Quit but crashed with the attached segfault/backtrace when I next attempted to start it (about 30 mins later). The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f77ab517840 (LWP 12666))] Thread 5 (Thread 0x7f7784b4b700 (LWP 12671)): #0 0x7f77a669705f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f779bd94686 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f779bd946b9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f77a66930a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f77a889208d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f777f998700 (LWP 12672)): #0 0x7f77a669705f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f779bb06e7d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f779bdbc1e6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f77a66930a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f77a889208d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f777eb87700 (LWP 12673)): #0 0x7f77a06028e9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f77a05c0299 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f77a05c0b03 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f77a05c0cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f77a9ee40de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f77a9eb5e6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f77a9eb6165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7f77a9db30bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #8 0x7f77a9db579f in () at /usr/lib64/libQtCore.so.4 #9 0x7f77a66930a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f77a889208d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f777d0fc700 (LWP 12676)): #0 0x7f77a669985a in __lll_unlock_wake () at /lib64/libpthread.so.0 #1 0x7f77a66965d9 in _L_unlock_554 () at /lib64/libpthread.so.0 #2 0x7f77a6696516 in __pthread_mutex_unlock_usercnt () at /lib64/libpthread.so.0 #3 0x7f7793f3af45 in () at /usr/lib64/libGL.so.1 #4 0x7f7793f40608 in () at /usr/lib64/libGL.so.1 #5 0x7f779147a102 in () at /usr/lib64/tls/libnvidia-tls.so.358.16 #6 0x7f77a0601750 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f77a05c0714 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #8 0x7f77a05c0b7b in () at /usr/lib64/libglib-2.0.so.0 #9 0x7f77a05c0cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #10 0x7f77a9ee40de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #11 0x7f77a9eb5e6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #12 0x7f77a9eb6165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #13 0x7f77a9db30bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #14 0x7f77a9e97783 in () at /usr/lib64/libQtCore.so.4 #15 0x7f77a9db579f in () at /usr/lib64/libQtCore.so.4 #16 0x7f77a66930a4 in start_thread () at /lib64/libpthread.so.0 #17 0x7f77a889208d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f77ab517840 (LWP 12666)): [KCrash Handler] #6 0x7f77a9df8c88 in QString::operator==(QString const&) const () at /usr/lib64/libQtCore.so.4 #7 0x7f77ab0cee5c in KStatusNotifierItem::setToolTipSubTitle(QString const&) (this=0x1fbbb00, subTitle=...) at /usr/src/debug/kdelibs-4.14.9/kdeui/notifications/kstatusnotifieritem.cpp:419 #8 0x7f77aa2d703e in () at /usr/lib64/libkmailprivate.so.4 #9 0x7f77aa2d6f1d in () at /usr/lib64/libkmailprivate.so.4 #10 0x7f77aa2d71f6 in () at /usr/lib64/libkmailprivate.so.4 #11 0x7f77aa2dfea5 in KMKernel::toggleSystemTray() () at /usr/lib64/libkmailprivate.so.4 #12 0x7f77aa30cd8f in KMMainWidget::readConfig() () at /usr/lib64/libkmailprivate.so.4 #13 0x7f77aa31cab1 in
[kmail2] [Bug 276856] message goes back to unread after new mail check
https://bugs.kde.org/show_bug.cgi?id=276856 --- Comment #11 from Rodney Baker rodney.ba...@iinet.net.au --- After watching the log file for quite some time (using tail -f) for the relevant akonadi process, the IMAP STORE command (with \SEEN flag) is not being sent to the server the first time a mail is fetched. It is only sent on the second fetch. When sent, the STORE command is being actioned and the response OK Store completed is returned. No errors from the server that I can see. An example transaction: C: A000548 UID FETCH 25270 (BODY.PEEK[] UID) S: * 65 FETCH ( UID 25270 BODY[] Return-Path: opensuse+bounces-143179-rodney.baker=iinet.net...@opensuse.org [...message body removed...] S: A000548 OK Fetch completed. The next time the folder is refreshed, note the lack of SEEN flag on UID 25270: S: * 64 FETCH ( FLAGS () UID 25269 ) S: * 65 FETCH ( FLAGS () UID 25270 ) S: * 66 FETCH ( FLAGS () UID 25271 ) S: * 67 FETCH ( FLAGS () UID 25272 ) S: * 68 FETCH ( FLAGS (\Seen) UID 25273 ) S: * 69 FETCH ( FLAGS () UID 25274 ) S: * 70 FETCH ( FLAGS () UID 25275 ) The next time the message is selected (after another folder refresh): S: * 63 FETCH ( FLAGS (\Seen) UID 25268 ) S: * 64 FETCH ( FLAGS () UID 25269 ) S: * 65 FETCH ( FLAGS () UID 25270 ) S: * 66 FETCH ( FLAGS () UID 25271 ) S: * 67 FETCH ( FLAGS (\Seen) UID 25272 ) S: * 68 FETCH ( FLAGS (\Seen) UID 25273 ) S: * 69 FETCH ( FLAGS () UID 25274 ) S: * 70 FETCH ( FLAGS () UID 25275 ) S: A000565 OK Fetch completed. C: A000566 UID STORE 25270 FLAGS (\Seen) S: * 65 FETCH ( UID 25270 FLAGS (\Seen) ) S: A000566 OK Store completed. This pattern is consistently repeatable. I have the full log as a tgz archive - I'm happy to email it to someone but I'd rather not attach it here. Rodney. -- 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 276856] message goes back to unread after new mail check
https://bugs.kde.org/show_bug.cgi?id=276856 Rodney Baker rodney.ba...@iinet.net.au changed: What|Removed |Added CC||rodney.ba...@iinet.net.au --- Comment #8 from Rodney Baker rodney.ba...@iinet.net.au --- Further information re this bug: it appears that the read status is not being pushed back to the IMAP server correctly. Running KMail2 with a dovecot IMAP server running on another box, using Maildir mail storage which made it easy to spot the problem. With dovecot, when the mail is marked as read the filename is suffixed with an S. Mails marked for deletion are marked with a T. The flags are cumulative i.e. a read mail marked for deletion will have ST. I connected via an ssh console session to the mailserver and went to Maildir/.Mailbox/cur an did ls -l. Here is the directory contents: -rw--- 1 bakerr bakerr 5013 Feb 6 18:09 1360136366.10220_3.mailpi.vk5ztv.ampr.org:2, -rw--- 1 bakerr bakerr 6797 Feb 6 19:30 1360141187.10935_2.mailpi.vk5ztv.ampr.org:2, -rw--- 1 bakerr bakerr 5134 Feb 6 19:35 1360141553.10983_0.mailpi.vk5ztv.ampr.org:2, -rw--- 1 bakerr bakerr 5497 Feb 6 20:20 1360144218.11362_1.mailpi.vk5ztv.ampr.org:2, -rw--- 1 bakerr bakerr 7073 Feb 7 02:14 1360165472.14541_2.mailpi.vk5ztv.ampr.org:2, -rw--- 1 bakerr bakerr 7654 Feb 7 02:19 1360165775.14586_1.mailpi.vk5ztv.ampr.org:2, -rw--- 1 bakerr bakerr 5844 Feb 7 02:20 1360165775.14590_3.mailpi.vk5ztv.ampr.org:2, -rw--- 1 bakerr bakerr 9800 Feb 7 02:50 1360167604.14959_2.mailpi.vk5ztv.ampr.org:2, Now, I read all the mails and again do ls -l: -rw--- 1 bakerr bakerr 5013 Feb 6 18:09 1360136366.10220_3.mailpi.vk5ztv.ampr.org:2,S -rw--- 1 bakerr bakerr 6797 Feb 6 19:30 1360141187.10935_2.mailpi.vk5ztv.ampr.org:2,S -rw--- 1 bakerr bakerr 5134 Feb 6 19:35 1360141553.10983_0.mailpi.vk5ztv.ampr.org:2,S -rw--- 1 bakerr bakerr 5497 Feb 6 20:20 1360144218.11362_1.mailpi.vk5ztv.ampr.org:2,S -rw--- 1 bakerr bakerr 7073 Feb 7 02:14 1360165472.14541_2.mailpi.vk5ztv.ampr.org:2, -rw--- 1 bakerr bakerr 7654 Feb 7 02:19 1360165775.14586_1.mailpi.vk5ztv.ampr.org:2,S -rw--- 1 bakerr bakerr 5844 Feb 7 02:20 1360165775.14590_3.mailpi.vk5ztv.ampr.org:2, -rw--- 1 bakerr bakerr 9800 Feb 7 02:50 1360167604.14959_2.mailpi.vk5ztv.ampr.org:2, At this stage ALL the mails are marked as read in KMail2, but not all the mails have read status flags on the mailserver. The next time KMail2 syncs with the IMAP server, those mails go back to unread status in KMail2. If I issue a Mark all mails as Read, all mails are marked as unread but the status are NOT updated on the dovecot mail server until the next scheduled mail check. I have seen the same thing happen with IMAP on gmail (I don't know what they run in the back end). Read status updates should either be pushed back to the mailserver as soon as they are changed in KMail2, or remembered locally and changed correctly on the mailserver at each scheduled mail check. There should also be a means of verifying that the change of status has been accepted and actioned by the mailserver and an error message should be displayed after a reasonable number of retries if the operation fails. -- 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 276856] message goes back to unread after new mail check
https://bugs.kde.org/show_bug.cgi?id=276856 --- Comment #9 from Rodney Baker rodney.ba...@iinet.net.au --- Further to that, the number of messages that do not get their status updated correctly on the mailserver when marked locally as read (by reading them in the preview pane) varies from a few (2 or 3) to all messages in the mailbox (esp. if is 20-30 messages). It does not seem to be consistent or necessarily predictable (yet). -- 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 294074] read IMAP mails are marked unread upon next folder sync
https://bugs.kde.org/show_bug.cgi?id=294074 Rodney Baker rodney.ba...@iinet.net.au changed: What|Removed |Added CC||rodney.ba...@iinet.net.au --- Comment #7 from Rodney Baker rodney.ba...@iinet.net.au --- Still happening consistently on KMail2 4.9.5 Release 3. Has any work been done on this yet? -- 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 293963] Akonadi config reports Invalid Password whenever trying to add Google Calendar or Contacts resource
https://bugs.kde.org/show_bug.cgi?id=293963 Rodney Baker rodney.ba...@iinet.net.au changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Rodney Baker rodney.ba...@iinet.net.au --- I have just tested this with Korganiser 4.9.5 Release 3 under openSuSE 12.2 and it now works correctly. I was able to add a google calendar resource (using an application-specific password created online) and correctly sync, add appointments etc. -- 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
[Bug 172388] Attachments saved as filenames enclosed in quotes
https://bugs.kde.org/show_bug.cgi?id=172388 --- Comment #9 from Rodney Baker rodney.ba...@iinet.net.au --- (In reply to comment #8) No news :) Sorry - haven't had a chance to try it out, yet, like I promised I would. Give me until Monday (since it is now Friday night and I need to be at work to test it). -- 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 172388] Attachments saved as filenames enclosed in quotes
https://bugs.kde.org/show_bug.cgi?id=172388 --- Comment #6 from Rodney Baker rodney.ba...@iinet.net.au --- Don't know - still running 4.6.5. I haven't updated to KMail2 for various reasons - I'm running 1.13.7 - so I can't say whether or not it is still in 4.9 or not, but if nothing has been done about it since 4.6.5 then I'm guessing it will be. I will try sending an email with attachment from Outlook when I get to work next week so you can check how 4.9 handles it. -- 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 293963] New: Akonadi config reports Invalid Password whenever trying to add Google Calendar or Contacts resource
https://bugs.kde.org/show_bug.cgi?id=293963 Summary: Akonadi config reports Invalid Password whenever trying to add Google Calendar or Contacts resource Product: Akonadi Version: 1.2.0 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Google Resource AssignedTo: savag...@yahoo.com ReportedBy: rodney.ba...@iinet.net.au CC: vkra...@kde.org, kdepim-bugs@kde.org Version: 1.2.0 (using KDE 4.6.5) OS:Linux When attempting to create a new Google Calendar (or Contacts) Akonadi resource, Akonadi always reports invalid password despite the password and username being entered correctly. Tracing the connection with Wireshark shows that Akonadi is returning a TLSv1 Record Layer Alert 48 - Unknown CA error immediately after the server certificate exchange. This only occurs when attempting to add Google gcal resources - KMail IMAP using SSL/TLS works fine with GMail on the same account. I have tried with both the openSuSE rpms and building libgcal and akonadi-googledata from source. No difference. Reproducible: Always Steps to Reproduce: Install libgcal and akonadi-googledata. Make sure akonadi server is running and start Akonadi Configuration Click Add, select Google Calendar Resource Enter Username/Password Actual Results: Akonadi returns Invalid Password error dialog. Expected Results: Akonadi should connect to the gcal resource and allow two-way synchronisation. OS: Linux (i686) release 3.1.0-3-desktop-vk5ztv Compiler: gcc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
[Bug 172388] Attachments saved as filenames enclosed in quotes
https://bugs.kde.org/show_bug.cgi?id=172388 --- Comment #4 from Rodney Baker rodney baker iinet net au 2012-02-13 04:57:27 --- This is still an issue with KMail 1.13.7 on KDE 4.6.5 -- 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 154454] Incorrect IMAP folder size shown
https://bugs.kde.org/show_bug.cgi?id=154454 --- Comment #10 from Rodney Baker rodney baker iinet net au 2009-06-04 14:36:29 --- Any further work on this? Still broken on 1.11.90 (Using KDE 4.2.88 (KDE 4.2.88 (KDE 4.3 = 20090527)) release 127) -- 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 184147] When previewing a signed message with Enterprise Headers the Show Details link for the signature details is disabled.
https://bugs.kde.org/show_bug.cgi?id=184147 --- Comment #2 from Rodney Baker rodney baker iinet net au 2009-05-12 13:15:35 --- Appears to be fixed in version 1.11.3 (KDE 4.2.3 release 116). -- 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 62253] Display size summary for IMAP-Folders/IMAP-Mailbox
https://bugs.kde.org/show_bug.cgi?id=62253 Rodney Baker rodney.ba...@iinet.net.au changed: What|Removed |Added CC||rodney.ba...@iinet.net.au --- Comment #4 from Rodney Baker rodney baker iinet net au 2009-05-12 13:23:27 --- As of version 1.11.3 (KDE 4.2.3) this appears to be working for IMAP folders but it only updates the folder size if unread messages are in the folder. I have approximately 50 folders - almost all have messages in them. All show 0B folder size *until* new unread messages appear in the folder. As soon as 1 of the unread messages is marked as read, the folder size updates and appears to be correct. Deleting messages (i.e. moving them to Trash) causes the folder size to decrease according to the size of the message, as expected. The only mild annoyance is that folder sizes only update the first time when new messages are read. I think this can probably be closed and a new issue opened for the folder size updating. Any other comments? -- 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 180945] Wrong message size in message list
https://bugs.kde.org/show_bug.cgi?id=180945 --- Comment #9 from Rodney Baker rodney baker iinet net au 2009-05-12 16:28:06 --- I can confirm this is now working as expected in version 1.11.3 (version 4.2.3 release 116). Thanks. -- 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 154454] Incorrect IMAP folder size shown
https://bugs.kde.org/show_bug.cgi?id=154454 Rodney Baker rodney.ba...@iinet.net.au changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Comment #7 from Rodney Baker rodney baker iinet net au 2009-05-12 16:35:49 --- This is only partly working on version 1.11.3 (version 4.2.3 release 116). I am seeing the following behaviour now: - 50 (or so) IMAP folders, most non-empty. All showed 0B folder size. - Once a new, unread message was delivered to an IMAP folder, when the first unread message was read, the folder size was calculated and displayed correctly. All other folders that have not had a new, unread message delivered and read still show 0B. - Deleting messages from folders that are showing the correct size sees the size decremented according to the size of the deleted messages (appears correct). - The Trash folder size (also an IMAP folder) initially increments according to the size of the messages being moved into it, but then reverts to 0B once moving the messages has completed. I have tried rebuilding the local IMAP caches with no effect (probably expected). Running 1.11.3 (KDE 4.2.3) on openSuse 11.0 with Dovecot 1.0.15-4.1. Looks like progress but not quite there yet... -- 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 154454] Incorrect IMAP folder size shown
https://bugs.kde.org/show_bug.cgi?id=154454 --- Comment #8 from Rodney Baker rodney baker iinet net au 2009-05-12 16:58:53 --- Actually I've just realised that what I'm seeing is a little more subtle than what I described above. The folder size is calculated and shown when the number of messages shown for a particular folder (in the Total column) changes. - I have some non-empty folders with no value shown in the Total messages column. If I click on those folders, the folder size is calculated and displayed. - I have some non-empty folders showing a number of messages in the Total column; if I click on those folders the size remains at zero bytes, regardless of what I do, until a new message is delivered to that folder (via procmail). - I have an empty folder showing zero bytes. I drag a read message from another folder (which is showing the correct folder size) to that empty folder. The Total message count is incremented by 1 but the size remains at zero. I drag another message into the folder; total count is now 2 but size remains at zero bytes. The size of the folder that I dragged the messages from is decremented by the size of the messages. - I drag the messages back to their original folder. The Total count in the previously empty folder is back to zero. The Total count in the folder from where the messages originally came (which, remember, was showing the correct folder size) is incremented by 2 (as expected) but the folder size is now shown as 0 bytes (it was correct before I dragged the messages back). I hope that description is clear. As I said, progress has definitely been made but something appears still to be not quite right. Let me know if I can do anything further to assist in tracking it down. -- 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 154454] Incorrect IMAP folder size shown
https://bugs.kde.org/show_bug.cgi?id=154454 --- Comment #9 from Rodney Baker rodney baker iinet net au 2009-05-12 17:12:55 --- Sorry to bug you again, but further refining my previous comments, if I drag messages between folders one at a time, the folder I am dragging the message *From* has the folder size calculated and displayed correctly as the message leaves the folder; the folder I drag the message *To* has its size set to and displayed as zero bytes. This is consistently repeatable across all IMAP folders. So, to summarise: Clicking on a folder that has newly delivered, unread messages will result in the folder size being calculated and displayed correctly. Dragging a message between folders (or moving a message to Trash, where Trash is an IMAP folder) will result in the source folder having its size calculated and displayed correctly but the destination folder having its size reset to and displayed as zero bytes. That is about as succinct as I can make it. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 172123] Kmail Crash when deleting multiple read and unread IMAP messages from folder (backtrace included)
http://bugs.kde.org/show_bug.cgi?id=172123 --- Comment #3 from Rodney Baker rodney baker iinet net au 2009-01-28 12:44:57 --- This appeared fixed in 4.2RC1 but now appears to have regressed after today updating to 4.2.00. Backtrace from most recent crash is as follows: Application: KMail (kmail), signal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] Thread 1 (Thread 0xb41786d0 (LWP 26877)): [KCrash Handler] #6 KMail::MessageListView::Widget::getSelectionStats (this=0x82c4b70, selectedsernu...@0xbfcc1938, selectedvisiblesernu...@0xbfcc1934, allSelectedBelongToSameThread=0xbfcc193f, includeCollapsedChildren=value optimized out) at /usr/src/debug/kdepim-4.2.0/kmail/messagelistview/widget.cpp:579 #7 0xb78760c6 in KMail::MessageListView::Pane::getSelectionStats (this=0x8236f30, selectedsernu...@0xbfcc1938, selectedvisiblesernu...@0xbfcc1934, allSelectedBelongToSameThread=0xbfcc193f, includeCollapsedChildren=value optimized out) at /usr/src/debug/kdepim-4.2.0/kmail/messagelistview/pane.cpp:579 #8 0xb7749357 in KMMainWidget::updateMessageActions (this=0x8236c28) at /usr/src/debug/kdepim-4.2.0/kmail/kmmainwidget.cpp:4288 #9 0xb77639b8 in KMMainWidget::qt_metacall (this=0x8236c28, _c=QMetaObject::InvokeMetaMethod, _id=20, _a=0xbfcc1a08) at /usr/src/debug/kdepim-4.2.0/build/kmail/kmmainwidget.moc:363 #10 0xb6cd8740 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb6cd94c2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb6d13bc7 in QTimer::timeout () from /usr/lib/libQtCore.so.4 #13 0xb6cdf1de in QTimer::timerEvent () from /usr/lib/libQtCore.so.4 #14 0xb6cd31ff in QObject::event () from /usr/lib/libQtCore.so.4 #15 0xb626882c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #16 0xb62706ce in QApplication::notify () from /usr/lib/libQtGui.so.4 #17 0xb7ed068d in KApplication::notify () from /usr/lib/libkdeui.so.5 #18 0xb6cc3a71 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #19 0xb6cf1de6 in ?? () from /usr/lib/libQtCore.so.4 #20 0xb6cee2b0 in ?? () from /usr/lib/libQtCore.so.4 #21 0xb48992d9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #22 0xb489c85b in ?? () from /usr/lib/libglib-2.0.so.0 #23 0xb489c9d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #24 0xb6cee208 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #25 0xb63018c5 in ?? () from /usr/lib/libQtGui.so.4 #26 0xb6cc214a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #27 0xb6cc230a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #28 0xb6cc49a5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #29 0xb62686a7 in QApplication::exec () from /usr/lib/libQtGui.so.4 #30 0x0804a5c0 in main (argc=) at /usr/src/debug/kdepim-4.2.0/kmail/main.cpp:146 Will try running it under valgrind to see what it says... -- Configure bugmail: http://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 172123] Kmail Crash when deleting multiple read and unread IMAP messages from folder (backtrace included)
http://bugs.kde.org/show_bug.cgi?id=172123 --- Comment #1 from Rodney Baker rodney baker iinet net au 2008-11-02 13:55:47 --- This is still occuring in version 1.10.1 KDE 4.1.2 release 49.1. It is consistently reproducable when selecting and deleting a non-contiguous group of messages from an IMAP (Dovecot) folder for deletion e.g. Shift-select a range of messages, then Ctrl-deselect on message in the middle of the range, then click on the trash can icon. Kmail will crash every time. Here is the latest backtrace... Application: KMail (kmail), signal SIGSEGV [?1034hUsing host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb4229a00 (LWP 20880)] [KCrash handler] #6 0xb4b06610 in clearerr () from /lib/libc.so.6 #7 0xb751c01c in KMFolderMbox::addMsg () from /usr/lib/libkmailprivate.so.4 #8 0xb752c666 in KMFolderImap::slotGetMessagesData () from /usr/lib/libkmailprivate.so.4 #9 0xb753467b in KMFolderImap::qt_metacall () from /usr/lib/libkmailprivate.so.4 #10 0xb7ecfc19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb7ed02e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb5ee7109 in KIO::TransferJob::data () from /usr/lib/libkio.so.5 #13 0xb5ee78de in KIO::TransferJob::slotData () from /usr/lib/libkio.so.5 #14 0xb5eed6fd in KIO::TransferJob::qt_metacall () from /usr/lib/libkio.so.5 #15 0xb7ecfc19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb7ed02e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #17 0xb5f9b613 in KIO::SlaveInterface::data () from /usr/lib/libkio.so.5 #18 0xb5f9e06e in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #19 0xb5f9bde7 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #20 0xb5f8d7c0 in KIO::Slave::gotInput () from /usr/lib/libkio.so.5 #21 0xb5f8db2d in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5 #22 0xb7ecfc19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #23 0xb7ed02e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #24 0xb5eb9c17 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5 #25 0xb5ebbc0b in KIO::ConnectionPrivate::dequeue () from /usr/lib/libkio.so.5 #26 0xb5ebbcce in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5 #27 0xb7ec956b in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4 #28 0xb7eca971 in QObject::event () from /usr/lib/libQtCore.so.4 #29 0xb50771cc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #30 0xb507bc79 in QApplication::notify () from /usr/lib/libQtGui.so.4 #31 0xb5b862bd in KApplication::notify () from /usr/lib/libkdeui.so.5 #32 0xb7ebacb9 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #33 0xb7ebbe89 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #34 0xb7ebc0ad in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #35 0xb7ee633f in ?? () from /usr/lib/libQtCore.so.4 #36 0xb4a275d6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #37 0xb4a2a972 in ?? () from /usr/lib/libglib-2.0.so.0 #38 0x0806a490 in ?? () #39 0x in ?? () #0 0xe410 in __kernel_vsyscall () -- Configure bugmail: http://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 172388] Attachments saved as filenames enclosed in quotes
http://bugs.kde.org/show_bug.cgi?id=172388 --- Comment #1 from Rodney Baker rodney baker iinet net au 2008-10-08 12:21:55 --- Created an attachment (id=27747) -- (http://bugs.kde.org/attachment.cgi?id=27747) Partial screenshot showing how attachment is displayed in kmail -- Configure bugmail: http://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 172388] Attachments saved as filenames enclosed in quotes
http://bugs.kde.org/show_bug.cgi?id=172388 --- Comment #2 from Rodney Baker rodney baker iinet net au 2008-10-08 12:22:56 --- Created an attachment (id=27748) -- (http://bugs.kde.org/attachment.cgi?id=27748) Screen shot of Save As dialog showing filename in quotes. -- Configure bugmail: http://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 172388] New: Attachments saved as filenames enclosed in quotes
http://bugs.kde.org/show_bug.cgi?id=172388 Summary: Attachments saved as filenames enclosed in quotes Product: kmail Version: unspecified Platform: SuSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version:(using KDE 4.1.2) OS:Linux Installed from:SuSE RPMs When saving attachments from emails sent from Outlook, KMail includes the quotes from the attachment description in the filename. Outlook adds the attachment as per the attached screenshot, with the attachment filename in quotes, then the description as the filename with no quotes. Here is an example of the relevant headers from the Outlook email: Content-Type: application/msword; name=#2782339-v1-Southern_Expressway_RS485_Wiring_Audit_-_July_2008.DOC Content-Transfer-Encoding: base64 Content-Description: #2782339-v1-Southern_Expressway_RS485_Wiring_Audit_-_July_2008.DOC Content-Disposition: attachment; filename= #2782339-v1-Southern_Expressway_RS485_Wiring_Audit_-_July_2008.DOC When saving the attachment from KMail, it encloses the destination filename in quotes by default. This breaks kde's filetype associations due to the fact that the filename extension now includes a double quote e.g. KMail saves test.doc as test.doc - KDE then sees the document extension as .doc and does not recognise the file type. This may well be due to Outlook's handling of attachment filenames (I haven't read the relevant RFC to see if it is compliant). The workaround is to delete the quotes from KMail's Save As... dialog before saving the file, however it would be better if KMail stripped the quotes from the beginning and end of the filename automatically. Could this be added please, at least as a configurable option? We already have Outlook compatibility options for sending emails and invitations, so it shouldn't be too hard to add an option for receiving attachments also. -- Configure bugmail: http://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 172123] New: Kmail Crash when deleting multiple read and unread IMAP messages from folder (backtrace included)
http://bugs.kde.org/show_bug.cgi?id=172123 Summary: Kmail Crash when deleting multiple read and unread IMAP messages from folder (backtrace included) Product: kmail Version: unspecified Platform: SuSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version:(using KDE 4.1.2) OS:Linux Installed from:SuSE RPMs When deleting multiple messages from an IMAP folder (some read, some unread) Kmail (KDE 4.1.2) crashes. Reproducible about 1 time in 3. Backtrace as follows: Application: KMail (kmail), signal SIGSEGV [?1034hUsing host libthread_db library /lib/libthread_db.so.1. [Thread debugging using libthread_db enabled] [New Thread 0xb416ca00 (LWP 2919)] [KCrash handler] #6 0xb4a49610 in clearerr () from /lib/libc.so.6 #7 0xb745cd4c in KMFolderMbox::addMsg () from /usr/lib/libkmailprivate.so.4 #8 0xb746d396 in KMFolderImap::slotGetMessagesData () from /usr/lib/libkmailprivate.so.4 #9 0xb74753ab in KMFolderImap::qt_metacall () from /usr/lib/libkmailprivate.so.4 #10 0xb7e0ec19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb7e0f2e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb5e29549 in KIO::TransferJob::data () from /usr/lib/libkio.so.5 #13 0xb5e29d1e in KIO::TransferJob::slotData () from /usr/lib/libkio.so.5 #14 0xb5e2fb3d in KIO::TransferJob::qt_metacall () from /usr/lib/libkio.so.5 #15 0xb7e0ec19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb7e0f2e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #17 0xb5edc933 in KIO::SlaveInterface::data () from /usr/lib/libkio.so.5 #18 0xb5edf38e in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #19 0xb5edd107 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #20 0xb5ece9e0 in KIO::Slave::gotInput () from /usr/lib/libkio.so.5 #21 0xb5eced4d in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5 #22 0xb7e0ec19 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #23 0xb7e0f2e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #24 0xb5dfba17 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5 #25 0xb5dfda0b in KIO::ConnectionPrivate::dequeue () from /usr/lib/libkio.so.5 #26 0xb5dfdace in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5 #27 0xb7e0856b in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4 #28 0xb7e09971 in QObject::event () from /usr/lib/libQtCore.so.4 #29 0xb4fba1cc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #30 0xb4fbec79 in QApplication::notify () from /usr/lib/libQtGui.so.4 #31 0xb5ac8d6d in KApplication::notify () from /usr/lib/libkdeui.so.5 #32 0xb7df9cb9 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #33 0xb7dfae89 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #34 0xb7dfb0ad in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #35 0xb7e2533f in ?? () from /usr/lib/libQtCore.so.4 #36 0xb496a5d6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #37 0xb496d972 in ?? () from /usr/lib/libglib-2.0.so.0 #38 0x0806a840 in ?? () #39 0x in ?? () #0 0xe410 in __kernel_vsyscall () -- Configure bugmail: http://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 158535] Corrupted names in message list where accented characters (e.g. umlauts) are used.
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=158535 --- Additional Comments From rodney.baker iinet net au 2008-02-28 14:59 --- Created an attachment (id=23739) -- (http://bugs.kde.org/attachment.cgi?id=23739action=view) Screenshot with name displayed correctly. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 115593] Move mail form imap to local folder crashes kmail
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=115593 --- Additional Comments From rodney.baker optusnet com au 2007-12-22 00:10 --- I have experienced a similar crash when moving mail in the opposite direction (i.e. from local to IMAP folder). Unfortunately I didn't save the stack dump but I will next time it happens. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
