[kmail2] [Bug 449891] kmail crashes on startup
https://bugs.kde.org/show_bug.cgi?id=449891 tjbp changed: What|Removed |Added CC||kde@tjbp.net --- Comment #2 from tjbp --- Am also experiencing this and the subsequent corruption of data detailed in #449898 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever
https://bugs.kde.org/show_bug.cgi?id=406917 tjbp changed: What|Removed |Added CC||kde@tjbp.net --- Comment #17 from tjbp --- Possibly now fixed - see comment: https://bugs.kde.org/show_bug.cgi?id=418910#c1 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 379300] New: Gmail IMAP token/code not saved
https://bugs.kde.org/show_bug.cgi?id=379300 Bug ID: 379300 Summary: Gmail IMAP token/code not saved Product: Akonadi Version: GIT (master) Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Gmail resource Assignee: dvra...@kde.org Reporter: kde@tjbp.net CC: kdepim-bugs@kde.org Target Milestone: --- Created attachment 105231 --> https://bugs.kde.org/attachment.cgi?id=105231&action=edit First pane When adding a Gmail account as an IMAP resource with KMail, it now loads a small browser window to authenticate with Google. After successfully allowing the app permissions, the final pane includes a code that can't be pasted anywhere into KMail. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 379300] Gmail IMAP token/code not saved
https://bugs.kde.org/show_bug.cgi?id=379300 --- Comment #1 from tjbp --- Created attachment 105232 --> https://bugs.kde.org/attachment.cgi?id=105232&action=edit Second pane -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 379300] Gmail IMAP token/code not saved
https://bugs.kde.org/show_bug.cgi?id=379300 --- Comment #2 from tjbp --- Created attachment 105233 --> https://bugs.kde.org/attachment.cgi?id=105233&action=edit Third pane -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 318949] XML in message body causes KMail to hang after every action
https://bugs.kde.org/show_bug.cgi?id=318949 tjbp changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #3 from tjbp --- Apologies for the delay - after failing to replicate this more recently I'm wondering if the problem was actually caused by a vast number of line breaks in a long email correspondence. It seems the email clients of my other contacts are duplicating line breaks from my emails exponentially and eating memory. -- 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 318949] New: XML in message body causes KMail to hang after every action
https://bugs.kde.org/show_bug.cgi?id=318949 Bug ID: 318949 Summary: XML in message body causes KMail to hang after every action Classification: Unclassified Product: kmail2 Version: 4.10.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: kde@tjbp.net I am often sent large quantities of XML pasted in an email, and when composing my reply message I am faced with frequent hangs. KMail becomes completely unresponsive, and starts to consume about 20% of my CPU time. The more XML, the longer the hangs will last. The hang seems to be triggered when I first open the composer to reply, and then again after 8 or so words I write. I suspect this might have a connection to the greater-than signs used to indent quoted text, and something attempting to parse them is getting confused by all the greater-than signs in the XML. Apologies if this is a duplicate or even already fixed (though I did search), since I'm aware I'm not using the latest revision. Reproducible: Always Steps to Reproduce: 1. Send an email with a significant amount of XML (say ~100 elements) to yourself. 2. Open a reply to that email. x86_64 -- 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