[kmail2] [Bug 461050] Bogus scam warning with trailing space
https://bugs.kde.org/show_bug.cgi?id=461050 --- Comment #3 from Volker Kuhlmann --- Created attachment 158471 --> https://bugs.kde.org/attachment.cgi?id=158471&action=edit Email with bogus scam warning Show this email, in kmail - default HTML off. kmail shows "This message may be a scam. (Details...)" and offers to move it to wastebin. Details: "This email contains a link which reads as 'https://status.voyager.nz/ ' in the text, but actually points to 'https://status.voyager.nz/'. This is often the case in scam emails to mislead the recipient" A trailing space in the path part of the link text is not a scam. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461050] Bogus scam warning with trailing space
https://bugs.kde.org/show_bug.cgi?id=461050 Volker Kuhlmann changed: What|Removed |Added CC||bug...@top.geek.nz --- Comment #2 from Volker Kuhlmann --- You mean an actual email where someone has put a link into the body where the link text in the HTML is the same as the link except with an added space at the end? It wouldn't take more than 5 seconds for anyone to make such an email. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461527] Save legible headers for Fcc
https://bugs.kde.org/show_bug.cgi?id=461527 --- Comment #3 from Volker Kuhlmann --- I sent an email but was unsure where kmail saved it. Because of another bug (not removing sent mails from outbox) I thought I could look up where kmail stored the sent copy, but unfortunately it only said X-KMail-Fcc: 380 thus telling me nothing. An actual folder name (without path is better) would have been useful. Instead I need to concoct with find and grep. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461653] kmail doesn't send when running over ssh
https://bugs.kde.org/show_bug.cgi?id=461653 --- Comment #7 from Volker Kuhlmann --- I don't understand why testing this from a text console has any merit. A Linux text console (e.g. ctrl-alt-f3) can only render characters, not graphics. The DISPLAY variable is undefined. No X-application is going to start. If you must, the kmail error is: > kmail qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. This was predictable (and it's a pretty bad error message after doing something stupid). E.g. trying to start an xterm: > xterm xterm: Xt error: Can't open display: xterm: DISPLAY is not set The error message is spot on. This will work when the earth stops spinning. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461653] kmail doesn't send when running over ssh
https://bugs.kde.org/show_bug.cgi?id=461653 --- Comment #5 from Volker Kuhlmann --- Thank you, I will get you the details when starting kmail from a terminal on B asap. Yes, on A it's an interactive KDE desktop session, with kmail started from the launcher (button in lower left corner of the screen). When I quit kmail, stop akonadi, pkill -e kwallet, and then start kmail from the konsole shell, it behaves as expected and as if started from the launcher, asking for the wallet password and sending emails without problems. If this is not what you meant me to try on A (I won't try the text console ctrl-alt-f3 or so... ;-) ), could you please clarify? Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461527] Save legible headers for Fcc
https://bugs.kde.org/show_bug.cgi?id=461527 Volker Kuhlmann changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||bug...@top.geek.nz --- Comment #2 from Volker Kuhlmann --- *I* am using this information when looking at the headers of mails, the numbers are completely useless to me for reading. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 461883] New: kontact hangs searching for todo
https://bugs.kde.org/show_bug.cgi?id=461883 Bug ID: 461883 Summary: kontact hangs searching for todo Classification: Applications Product: kontact Version: 5.19.3 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: todo Assignee: kdepim-bugs@kde.org Reporter: bug...@top.geek.nz Target Milestone: --- SUMMARY Kontact hangs with 100% CPU load when searching for a todo in the calendar view, the search result is empty and the date range from and to are both empty. STEPS TO REPRODUCE 1. Start kontact, switch to calendar view. 2. Open search popup with ctrl-F. 3. Enter something in search (I don't know whether there have to be no results for it). 4. Clear the date range from and to fields. 5. Untick "Include todos within date range". 6. Press enter. OBSERVED RESULT Kontact hangs with 100% CPU load. EXPECTED RESULT Either empty search results list, or list of matching todos. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.14.21-150400.24.28-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461653] kmail doesn't send when running over ssh
https://bugs.kde.org/show_bug.cgi?id=461653 --- Comment #3 from Volker Kuhlmann --- > 1. Do you, or did you previously have Gnome keyring installed on this system? No, I never install anything gnome explicitly. openSUSE 15.4 KDE desktop. This is also a clean new install with an empty user account, without any old ~/.config/, ~/.local/. > 2. What version is your KDE Frameworks? See versions, kded rpm. kmail help -> about doesn't say. systemsettings -> about says Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.14.21-150400.24.28-default (64-bit) Graphics Platform: X11 > 3. If it's 5.97 or later, do you have Secret Service enabled in the KWallet > settings? It's 5.90. There is nothing about secret service in systemsettings -> KDE wallet that I can see. > 4. Are you using a blowfish or GPG wallet? (Might be related to Bug 458085 if > it's a GPG wallet.) How do I find out which it is? There is a ~/.local/share/kwalletd/kdewallet.kwl It's likely not gpg, gpg --list-keys is empty. > 5. What happens if you try to send a mail locally (not via ssh)? "Locally" is ambiguous here. I am logged into A from B via ssh when the problem occurs, kmail running on A via ssh. When I quit the kmail started via ssh, stop akonadi, pkill kwallet, then go back to host A and start kmail on the KDE desktop session, kmail must be starting the wallet because something asks for the *wallet* password for "mailtransports", and everything works as expected. When I quit kmail, stop akonadi and kill the wallet on A, then log into A from B via ssh and start kmail, kmail does NOT ask for the wallet password, but then asks for the password for the SMTP server that's configured for the mail being sent, when clicking on "send". Note the interactive desktop session remains running on host A, but kmail and akonadi are stopped. Leaving the wallet running on A or not makes no difference, kmail doesn't open the wallet maybe? > > This used to work fine on openSUSE 12.3, kmail 4.10.5; > Those are pretty ancient. Agreed! But they provide the Unix mantra of things still working as expected when $DISPLAY is different! Currently, kmail is only capable of single-user machine stuff :-(. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461653] kmail doesn't send when running over ssh
https://bugs.kde.org/show_bug.cgi?id=461653 Volker Kuhlmann changed: What|Removed |Added CC||bug...@top.geek.nz --- Comment #1 from Volker Kuhlmann --- If I don't redirect stdout/err of the kmail started over ssh, there is a bunch of these on the screen when clicking "send": We have an error during reading password "The name org.freedesktop.secrets was not provided by any .service files" It looks to me like somehow kmail isn't finding the wallet, although the wallet is running and can be opened, showing expected content. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461653] New: kmail doesn't send when running over ssh
https://bugs.kde.org/show_bug.cgi?id=461653 Bug ID: 461653 Summary: kmail doesn't send when running over ssh Classification: Applications Product: kmail2 Version: 5.19.3 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bug...@top.geek.nz Target Milestone: --- SUMMARY When starting kmail over ssh on a remote host, kmail doesn't send any mail, it asks for the transport password instead. This is at least when there still is a local KDE desktop session running on the remote host, even when kmail and akonadi are not running. STEPS TO REPRODUCE 1. Log into host A, KDE desktop session. 2. Start kmail. 3. Quit kmail, stop akonadi. 4. Log into host B, KDE desktop session. 5. ssh from B to A. 6. Start kmail on A, compose mail, send. 6b. pkill kwallet; Start kmail on A, compose mail, send (no difference; kmail may or may not ask for the wallet password, but even if it does, it still asks for the transport password when sending). OBSERVED RESULT kmail asks for the password for the mailtransport. EXPECTED RESULT Mail is sent without more pop-ups, the mailtransport password is already saved in the wallet. SOFTWARE/OS VERSIONS kmail Version 5.19.3 (21.12.3) openSUSE Leap 15.4 kded-5.90.0-150400.1.4.x86_64 Qt Version: Name: libQt5Core5 Version : 5.15.2+kde294 Release : 150400.6.3.1 ADDITIONAL INFORMATION This used to work fine on openSUSE 12.3, kmail 4.10.5; kmail didn't even have to be quit, only akonadi had to be stopped. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461526] Message stays in outbox
https://bugs.kde.org/show_bug.cgi?id=461526 Volker Kuhlmann changed: What|Removed |Added CC||bug...@top.geek.nz --- Comment #1 from Volker Kuhlmann --- The number saved in X-KMail-Fcc: of the headers of the mail stored in sent-mail and outbox is the same as the one shown in folder-properties -> Internals -> Identifier of the sent-mail folder, when looking in akonadiconsole. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461527] New: Save legible headers for Fcc
https://bugs.kde.org/show_bug.cgi?id=461527 Bug ID: 461527 Summary: Save legible headers for Fcc Classification: Applications Product: kmail2 Version: 5.19.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bug...@top.geek.nz Target Milestone: --- SUMMARY When sending mail, kmail saves headers X-KMail-Identity: 123456 X-KMail-Identity-Name: abcedghi X-KMail-Transport: 9876543 X-KMail-Transport-Name: xx X-KMail-Fcc: 99 There is no human-readable name saved for Fcc, numbers of internal data structures are not so useful. This is local information that isn't sent to the recipient but is useful to the user. STEPS TO REPRODUCE 1. Send any email. 2. Look at the headers of the email stored in sent-mail. OBSERVED RESULT X-KMail-Fcc: is stored, but no X-KMail-Fcc-Name:. EXPECTED RESULT Store X-KMail-Fcc-Name: as well (corresponding to X-KMail-Fcc:). SOFTWARE/OS VERSIONS KMail Version 5.19.3 (21.12.3) plasma5-workspace-5.24.4-bp154.2.3.1.x86_64 openSUSE Leap 15.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461526] New: Message stays in outbox
https://bugs.kde.org/show_bug.cgi?id=461526 Bug ID: 461526 Summary: Message stays in outbox Classification: Applications Product: kmail2 Version: 5.19.3 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bug...@top.geek.nz Target Milestone: --- SUMMARY When I send an email, often a copy of it stays in outbox, even if is correctly saved into whatever was specified as sent-mail for that email. The email arrives at the recipient, so it is actually sent. Of course it is much better to have two copies than none... but checking and deleting is getting tedious. STEPS TO REPRODUCE 1. I haven't yet found the conditions under which it occurs. My suspicion is that it has something to do with whether the sending transport password is available, however it also occurs after a new login with sending though local sendmail. Does anyone have suggestions for what to check for? OBSERVED RESULT Sent mail is stored in the sent-mail folder as well as being left in the outbox folder. EXPECTED RESULT Sent mail is stored in the sent-mail folder only. SOFTWARE/OS VERSIONS KMail Version 5.19.3 (21.12.3) plasma5-workspace-5.24.4-bp154.2.3.1.x86_64 openSUSE Leap 15.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461050] New: Bogus scam warning with trailing space
https://bugs.kde.org/show_bug.cgi?id=461050 Bug ID: 461050 Summary: Bogus scam warning with trailing space Classification: Applications Product: kmail2 Version: 5.19.3 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bug...@top.geek.nz Target Milestone: --- SUMMARY Bogus scam warning with trailing space in link text. STEPS TO REPRODUCE 1. Read an email like this in kmail. OBSERVED RESULT Big warning in red reading "This email contains a link which reads as 'https://1stdomains.nz/renew ' in the text, but actually points to 'https://1stdomains.nz/renew'. This is often the case in scam emails to mislead the recipient" EXPECTED RESULT No warning. I'm not too worried about a trailing space in the link text. SOFTWARE/OS VERSIONS 5.19.3 (21.12.3) Linux (x86_64) release 5.14.21-150400.24.21-default openSUSE Leap 15.4 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461049] New: Folder properties moans about lacking network for local-disk folders
https://bugs.kde.org/show_bug.cgi?id=461049 Bug ID: 461049 Summary: Folder properties moans about lacking network for local-disk folders Classification: Applications Product: kmail2 Version: 5.19.3 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: bug...@top.geek.nz Target Milestone: --- SUMMARY Right-click on a folder -> folder properties gives an error "Network is unconnected. Folder information cannot be updated." even when the folder is located on local disk, and kmail is set to "Work offline". Those folders are using akonadi_mixedmaildir_resource_N. While I'm working locally only I'm seriously uninterested in whether the imap mailboxes are online or not. This error is annoying and serves no purpose. STEPS TO REPRODUCE 1. Add a mixedmaildir resource with any suitable directory on local disk. 2. Add an imap resource. 3. Set kmail offline File -> Work offline 4. Right-click on any folder inside the mixedmaildir and select "folder properties". OBSERVED RESULT Error about a missing network. EXPECTED RESULT No error about unrelated network folders. SOFTWARE/OS VERSIONS kmail Version 5.19.3 (21.12.3) openSUSE Leap 15.4 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 461043] New: Close message window with ESC when viewing message with double-click
https://bugs.kde.org/show_bug.cgi?id=461043 Bug ID: 461043 Summary: Close message window with ESC when viewing message with double-click Classification: Applications Product: kmail2 Version: unspecified Platform: OpenSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: bug...@top.geek.nz Target Milestone: --- When viewing a message by double-clicking on its line in the message list, close the message window with escape as well as ctrl-W. STEPS TO REPRODUCE 1. Navigate to any folder. 2. Double-click on a message in the folder; a window opens to display the message (read-only). OBSERVED RESULT The window can only be closed with ctrl-W (or clicking close in the title bar). EXPECTED RESULT The window can also be closed with ESC, like the view-source window when pressing V in the message list instead of double-clicking. SOFTWARE/OS VERSIONS Kmail Version 5.19.3 (21.12.3) openSUSE Leap 15.4 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 --- Comment #36 from Volker Kuhlmann --- > kwallet is not available ? but your password from imap/pop3 is stored in > kwallet. Yes. Crazy. Receiving mail always works as expected. And I'm sure it used to work for sending too, the only changes I can remember making is verifying the encryption settings and adding the odd mailbox and (less often) SMTP server. -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 --- Comment #34 from Volker Kuhlmann --- Created attachment 89467 --> https://bugs.kde.org/attachment.cgi?id=89467&action=edit kmail notification that kwallet is not available. -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 --- Comment #33 from Volker Kuhlmann --- I had two SMTP servers with passwords in the mailtransports file. I deleted both from kwallet, quit kmail, and stopped KDE PIM akonadictl stop qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit mysqladmin --socket=$USER/.local/share/akonadi/socket-$HOST/mysql.socket shutdown Starting kmail and composing an email with a sender ID belonging to one of the SMTP servers under test causes kmail to prompt for the password. Good. However, when attempting to store it kmail says "KWallet is not available". kwalletd is running afterwrads with no other app started that could have caused kwallet to be started. -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 --- Comment #31 from Volker Kuhlmann --- > But why you still have same identifier + password in kwallet ? One of two reasons: * It's still in there from before, when kmail was reading the password from kwallet correctly. * kmail migrated it into kwallet, but on next complete restart complained about a missing password, asks for it, stores it into mailtransports, then asks whether to migrate it, and round we go. -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 --- Comment #29 from Volker Kuhlmann --- Thanks Laurent! I can confirm that kmail reads some passwords from kwallet for sending, but not others. This one is NOT read from kwallet, although it is stored in the wallet (searching for the transport number): [Transport 113691] auth=true authtype=1 encryption=TLS host=mail.gmx.net id=113691 name=GMX ... password=... (!!) storepass=true user= Migrating it will cause kmail to start prompting for a missing password. (Does the migration fail if a password is already stored, same password or not same?) The password for this one is loaded correctly from kwallet: [Transport 12163] auth=true authtype=1 encryption=TLS host=net.nz id=12163 name=... port=587 storepass=true user=... Other than the port number I don't see a difference for the two entries. -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 --- Comment #25 from Volker Kuhlmann --- Created attachment 89408 --> https://bugs.kde.org/attachment.cgi?id=89408&action=edit Kmail pop-up migrating passwords. I have two SMTP servers now whos pw kmail won't read from the wallet. I think it still reads some from the wallet though. It's affecting GMX and Posteo - both might have turned off sslv3 recently and I think I edited the transport settings accordingly. -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 --- Comment #23 from Volker Kuhlmann --- Reboot. Click send. Popup message is: "You need to supply a username and password for this SMTP server". It offers to save it, I say yes, it gets stored in ~/.kde4/share/config/mailtransports Log out, make sure all user processes exit (console shell to check). Log in, start kmail, it asks "password stored insecurely, migrate to wallet" (or to that effect). Click yes. Compose email, click send. Popup "you need to supply a username...". I got the impression that kmail does not read the password from mailtransports either - but to be confirmed. I have 10 SMTP accounts and about 12 IMAP accounts configured. The problem has become seriously annoying more recently, about when I replaced mobo and CPU with faster ones. Hmm, at least 2 SMTP servers are affected. If it was only a config problem that'd be cool, but I can't think of one. I do frequently run kmail over ssh on the LAN, but that has always worked earlier. I take care of stopping akonadi appropriately (akonadictl stop) and running a dbus daemon per display. On startup kmail causes a popup asking for the wallet password; it still does, but it is no longer sufficient. kdeinit4: kwalletd is running, kwalletmanager is started by kmail when asking for a pasword. Every linux distro and KDE version is very old all the time :-) The problem is that you don't have the resources to deal with more than leading edge, and I don't have the resources to keep up and deal with the problems after each upgrade/reinstallation of $DISTRO. Thanks for looking over it thoguh. -- 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 261559] KMail stopped recognizing KWallet for password for specific SMTP server
https://bugs.kde.org/show_bug.cgi?id=261559 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #21 from Volker Kuhlmann --- Not fixed kmail-4.10.5-1.100.2.x86_64 openSUSE 12.3 kmail uses passwords from kwallet for IMAP retrieval, and by the looks of it for other SMTP servers, but there's always one for which it doesn't. It's been driving me nuts... -- 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 338672] Can't create folder on IMAP server
https://bugs.kde.org/show_bug.cgi?id=338672 --- Comment #2 from Volker Kuhlmann --- All of these operations, creating/deleting a top-level folder with non-ASCII characters in the name, work flawlessly in kmail with gmx.de. Even in case posteo.de's IMAP server is not as it should be, being able to recover from the problem only by deleting the akonadi IMAP resource looks like a bug in kmail (akonadi?). -- 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 338672] Can't create folder on IMAP server
https://bugs.kde.org/show_bug.cgi?id=338672 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #1 from Volker Kuhlmann --- When starting kmail from the console while akonadi is stopped, this shows up in between screefuls of stuff: Error during executing query "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6)" : "Duplicate entry '540-Test' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement" Is kmail trying to create an entry twice, and also not noticing on restarts/refreshes that it already exists? -- 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 338672] New: Can't create folder on IMAP server
https://bugs.kde.org/show_bug.cgi?id=338672 Bug ID: 338672 Summary: Can't create folder on IMAP server Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs URL: imap://posteo.de OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz Creating a new folder on the IMAP server using the posteo.de web interface works fine and the new folder shows up in kmail (receiving account) after a refresh (ctrl-F5). Creating a folder for this IMAP account at the top level in kmail produces error: "Posteo: Could not create collection Test resourceId: 34". This message is repeated frequently, on each kmail startup, and flooded through the panel's notifications facility (very irritating). The top-level folder is actually created on the IMAP server. From then on kmail will not show any new folders or sub-folders created on the server, e.g. with the server's webmail interface. Subfolders can still be created with kmail, and show up in kmail and are created on the server. kmail is then permanently stuck, stopping akonadi and quitting kmail does NOT change this. The only way to fix this is to delete the receive account in kmail (or system settings, personal information), and to re-create it. I haven't found similar bug reports in bugzilla. Workaround: Only perform creation of folders in posteo's webmail interface!! Reproducible: Always Steps to Reproduce: 1. Create a receive account in kmail for posteo.de 2. Add a new folder in the IMAP account on posteo.de at the top level - RMB on the IMAP service name in kmail's folder list (the server icon), with the name containing only ASCII characters. 3. Actual Results: * kmail produces an error: Posteo: Could not create collection Test resourceId: 34 * The folder is not shown in kmail (although it is created on the server). * No further folder or sub-folders created on the server will show in kmail. * Frequent notification drivel occurs. * Restarting akonadi and kmail does not fix it. * Sub-folders can still be created in kmail, and are shown as expected. Expected Results: Folder is created. Folder shows in kmail. Further folder or sub-folder creation, either with kmail or otherwise, is possible and all folders created on the server show in kmail after refresh. System is running on US or UK English locale. IMAP server is probably running on German locale. IMAP server's web interface shows folders Posteingang, Entwürfe, Gesendet, Gelöscht (which can't be deleted etc). kmail translates this into English, and does not associate Gelöscht with what it calls Trash. The problem does not occur with gmx.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
[kdepim] [Bug 323476] Sort akonadi resources by type
https://bugs.kde.org/show_bug.cgi?id=323476 --- Comment #7 from Volker Kuhlmann --- Sorry, no. Searching for imap or email gives nothing. Searching is useless if I don't know what I am searching for. It is essential to have a complete list at a glance of what's configured, especially for something as haphazzard as akonadi, e.g. for troubleshooting. The current display is a mess and not user-friendly. But if it's too difficult I rest my case. 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
[kdepim] [Bug 323476] Sort akonadi resources by type
https://bugs.kde.org/show_bug.cgi?id=323476 --- Comment #5 from Volker Kuhlmann --- Thanks! But did you mean search or sort? Both would be very useful, but are not the same. -- 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 327629] New: Default spell checker is not persistent
https://bugs.kde.org/show_bug.cgi?id=327629 Bug ID: 327629 Summary: Default spell checker is not persistent Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz In the compose window is settings->spellchecker, which offers to set the default language. This setting is not persistent, effectively making the setting superfluous as it needs to be set again for each new email. There is no equivalent setting in kmail->settings, perhaps that is the bug, and it's only ever being selectable for each composer window. kmail-settings->configure kmail->composer only has a language setting for autocorrection. My default spell checker is different (English - New Zealand, which isn't available in the autocorrections drop-down). Reproducible: Always Steps to Reproduce: 1. Set KDE to British English, with spell checkers for New Zealand English. 2. Compose a new email. 3. In the compower window, setting->spellchecker: select English (New Zealand). 4. Save, send etc this email. Actual Results: 5. Compose a another email, the spell checker default language is back to English (UK). Expected Results: When kmail is set to spellcheck new emails in English (New Zealand), it should not select another language. -- 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 323984] Address completion inserts nothing
https://bugs.kde.org/show_bug.cgi?id=323984 --- Comment #6 from Volker Kuhlmann --- What difference one word can make... I'm impressed. Thank you very much! -- 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 323984] Address completion inserts nothing
https://bugs.kde.org/show_bug.cgi?id=323984 --- Comment #4 from Volker Kuhlmann --- I never know, its all a big library, but both kontact and korganizer should get to it. I'll try to narrow it down. 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 323984] Address completion inserts nothing
https://bugs.kde.org/show_bug.cgi?id=323984 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #2 from Volker Kuhlmann --- This happens as well when selecting recipients for event invitations in kontact. I've seen it many times so there is a problem. It probably depends on some other condition which is different between us. I'll try to figure out what it might be. -- 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 324194] Recipient address auto-complete from address book doesn't work in kmail2
https://bugs.kde.org/show_bug.cgi?id=324194 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #1 from Volker Kuhlmann --- How to make completion from address book work: Disable semantic desktop, stop nepomuk service. Address book completions start working instantly!! There's some irony here, given that kmail suggests loudly that completions will not work until semantic desktop is enabled... but exactly that prevents them from working. Enabling both and restarting the feeder, waiting until indexing is complete - completions still work, but only until kmail is restarted. Disable nepomuk semantic desktop in system settings - completions start working instantly. But now of course searching emails no longer works - which however doesn't work anyway (bug#324189). -- 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 324194] New: Recipient address auto-complete from address book doesn't work in kmail2
https://bugs.kde.org/show_bug.cgi?id=324194 Bug ID: 324194 Summary: Recipient address auto-complete from address book doesn't work in kmail2 Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz When composing a new email or redirecting one, after typing some letters a popup should open with possible recipient matches, both from recent addresses and from the address book(s). Completion is only from recent addresses, the list of matches from the address book is not shown. There is an akonadi Personal Contacts address book, default, located at /home/user/.local/share/contacts/, which is populated and works with the explicit recipient picker list. akonadi and kmail were already restarted too many times. Nepomuk search is running (systemsettings → startup/shutdown → service manager → nepomuk search module). The akonadi nepomuk feeder (akonadiconsole, agents tab) was just deleted, and automatically recreated, and indexing is completed. I am making a new report, because bug#220608 and bug#237511 are years old and for kmail1 which nobody cares about any more. The bug is current! Reproducible: Always Steps to Reproduce: 1. Start nepomuk and tick autostart (systemsettings → startup/shutdown → service manager → nepomuk search module). 2. Enable desktop search (systemsettings → desktop search, tick enable semantic desktop, tick enable email indexer just in case; file indexer is off) 3. Check indexing is completed (akonadiconsole, agents, akonadi nepomuk feeder). 4. Compose an email. Put cursor into "To: field, type 2 letters of some address that is in the address book. Actual Results: The completion list only offers entries from "recent addresses", but not from the address book. Expected Results: Completions from recent addresses and all address books. -- 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 324043] Crash marking emails as read and selecting a new folder
https://bugs.kde.org/show_bug.cgi?id=324043 --- Comment #1 from Volker Kuhlmann --- Created attachment 82001 --> https://bugs.kde.org/attachment.cgi?id=82001&action=edit New crash information added by DrKonqi kmail (4.10.5) on KDE Platform 4.10.5 "release 1" using Qt 4.8.4 - What I was doing when the application crashed: Same as described above. Unsure whether the backtrace adds more info. -- Backtrace (Reduced): #6 QModelIndex (other=..., this=0x7fff23f90650) at /usr/include/QtCore/qabstractitemmodel.h:65 #7 KSelectionProxyModelPrivate::mapTopLevelToSource (this=this@entry=0x46dbf50, row=0, column=0) at /usr/src/debug/kdelibs-4.10.5/kdeui/itemviews/kselectionproxymodel.cpp:1623 #8 0x2ba3488b71c3 in KSelectionProxyModel::mapToSource (this=0x65e8ba0, proxyIndex=...) at /usr/src/debug/kdelibs-4.10.5/kdeui/itemviews/kselectionproxymodel.cpp:2151 #9 0x2ba3488b1cad in KSelectionProxyModel::data (this=0x65e8ba0, index=..., role=34) at /usr/src/debug/kdelibs-4.10.5/kdeui/itemviews/kselectionproxymodel.cpp:2255 #10 0x2ba34e8bf5a8 in data (arole=34, this=0x7fff23f90840) at /usr/include/QtCore/qabstractitemmodel.h:402 -- 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 324043] Crash marking emails as read and selecting a new folder
https://bugs.kde.org/show_bug.cgi?id=324043 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz -- 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 324189] New: Search finds nothing
https://bugs.kde.org/show_bug.cgi?id=324189 Bug ID: 324189 Summary: Search finds nothing Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz Email search gives no results. Select email, press "s", search in that folder, complete message, enter something, no results. Nepomuk is running (systemsettings → service manager → nepomuk search module). Semantic desktop search is enabled (systemsettings → desktop search, tick enable semantic desktop, tick enable email indexer) I enabled the file indexer too and configured it to index all the mail folders - no difference. The "akonadi nepomuk feeder" is enabled, running, and indexing of all email is completed. (akonadiconsole, agents). Deleting the feeder, exiting kmail, akonadictl stop, wait for stopped, restarting kmail - akonadi nepomuk feeder agent re-indexes mail, wait for that to finish. Still zero search results. Reproducible: Always Steps to Reproduce: 1. Start nepomuk and tick autostart (systemsettings → service manager → nepomuk search module). 2. Enable desktop search (systemsettings → desktop search, tick enable semantic desktop, tick enable email indexer) 3. Check email indexing is finished (akonadiconsole, agents, akonadi nepomuk feeder). 4. select an email, press "s", enter some search terms. Actual Results: Zero search results. Expected Results: Those emails found that I know exist. The email is in mixedmaildir resources, kmail folder indexing is complete and emails are shown by kmail. The quick search (input field abve the msg index) finds something, but I am not seeing the relationship between what is found and the search word(s). -- 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 324185] New: Headers can't be searched
https://bugs.kde.org/show_bug.cgi?id=324185 Bug ID: 324185 Summary: Headers can't be searched Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz Headers of mail in the current folder can't be searched. Right-clicking on the folder and selecting "search" only gives "enable nepomuk", but that "enables full-text search" of bodies. I have no interest in nepomuk, it's bloated and far more trouble than it's worth. And it's not needed for searching headers. Unfortunately the index/quick search (whatever it's called) leaves a few things to be desired, its mode of operation being one of them (is it "anywhere in headers"? who knows) , but almost always I want to know name or email address in either sender or receiver, so it's of not much use. And when I enable all that nepomuk stuff in desperation, kmail still says "not running, enable in system settings". Kmail does not have useable email header searching. 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 324043] New: Crash marking emails as read and selecting a new folder
https://bugs.kde.org/show_bug.cgi?id=324043 Bug ID: 324043 Summary: Crash marking emails as read and selecting a new folder Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz Application: kmail (4.10.5) KDE Platform Version: 4.10.5 "release 1" 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: Had selected a number of mbox file folders in a mixedmaildir resource. RMB -> mark all as read This operation was shown as finished by the activity display in the lower right corner (opened with the blue up arrow), but some folders were still showing unread emails in the folder list. I selected one of those folders when kmail crashed immediately after the click. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x2ab49c83ac00 (LWP 29439))] Thread 3 (Thread 0x2ab4a3000700 (LWP 29467)): #0 0x2ab488a15964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x2ab493cb27c7 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x2ab493cb27f9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x2ab488a11e0f in start_thread () from /lib64/libpthread.so.0 #4 0x2ab48686b7dd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x2ab4a3319700 (LWP 29468)): #0 0x2ab48686287d in poll () from /lib64/libc.so.6 #1 0x2ab48e585aa4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x2ab48e585bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x2ab485f352e6 in QEventDispatcherGlib::processEvents (this=0x2ab4a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x2ab485f05adf in QEventLoop::processEvents (this=this@entry=0x2ab4a3318e00, flags=...) at kernel/qeventloop.cpp:149 #5 0x2ab485f05d68 in QEventLoop::exec (this=0x2ab4a3318e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x2ab485e080f0 in QThread::exec (this=) at thread/qthread.cpp:542 #7 0x2ab485e0b0cc in QThreadPrivate::start (arg=0x7f0) at thread/qthread_unix.cpp:338 #8 0x2ab488a11e0f in start_thread () from /lib64/libpthread.so.0 #9 0x2ab48686b7dd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x2ab49c83ac00 (LWP 29439)): [KCrash Handler] #6 QModelIndex (other=..., this=0x7fff0858d9a0) at /usr/include/QtCore/qabstractitemmodel.h:65 #7 KSelectionProxyModelPrivate::mapTopLevelToSource (this=this@entry=0x38eefb0, row=0, column=0) at /usr/src/debug/kdelibs-4.10.5/kdeui/itemviews/kselectionproxymodel.cpp:1623 #8 0x2ab4841851c3 in KSelectionProxyModel::mapToSource (this=0x4155c80, proxyIndex=...) at /usr/src/debug/kdelibs-4.10.5/kdeui/itemviews/kselectionproxymodel.cpp:2151 #9 0x2ab48417fcad in KSelectionProxyModel::data (this=0x4155c80, index=..., role=34) at /usr/src/debug/kdelibs-4.10.5/kdeui/itemviews/kselectionproxymodel.cpp:2255 #10 0x2ab48a18d5a8 in data (arole=34, this=0x7fff0858db90) at /usr/include/QtCore/qabstractitemmodel.h:402 #11 Akonadi::EntityMimeTypeFilterModel::filterAcceptsRow (this=, sourceRow=, sourceParent=...) at /usr/src/debug/kdepimlibs-4.10.5/akonadi/entitymimetypefiltermodel.cpp:113 #12 0x2ab485839e60 in QSortFilterProxyModelPrivate::create_mapping (this=this@entry=0x1b0c570, source_parent=...) at itemviews/qsortfilterproxymodel.cpp:327 #13 0x2ab48583aadd in QSortFilterProxyModel::rowCount (this=, parent=...) at itemviews/qsortfilterproxymodel.cpp:1690 #14 0x2ab48ad552ed in MessageList::StorageModel::rowCount(QModelIndex const&) const () from /usr/lib64/libmessagelist.so.4 #15 0x2ab48ad14bb1 in MessageList::Core::Model::setStorageModel(MessageList::Core::StorageModel*, MessageList::Core::PreSelectionMode) () from /usr/lib64/libmessagelist.so.4 #16 0x2ab48ad1522e in ?? () from /usr/lib64/libmessagelist.so.4 #17 0x2ab485f1c29f in QMetaObject::activate (sender=0x2973670, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3548 #18 0x2ab485f1c29f in QMetaObject::activate (sender=0x35b4200, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3548 #19 0x2ab485efc986 in QAbstractItemModel::reset (this=0x35b4200) at kernel/qabstractitemmodel.cpp:2913 #20 0x2ab485f1c29f in QMetaObject::activate (sender=0x4155c80, m=, local_signal_index=, argv=0x7fff0858e2e0) at kernel/qobject.cpp:3548 #21 0x2ab485f66a14 in QAbstractItemModel::rowsRemoved (this=, _t1=..., _t2=0, _t3=7923) at .moc/release-shared/moc_qabstractit
[kmail2] [Bug 323984] New: Address completion inserts nothing
https://bugs.kde.org/show_bug.cgi?id=323984 Bug ID: 323984 Summary: Address completion inserts nothing Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz Address completion fails to insert anything at all when double-clicking, and the entry was already selected with a single-click. This happens in the To:, Cc:, Bcc: fields and in the redirect-popup. It's especially irritating because the list has only names, no addresses, so for multiple names with different addresses one has to pull tricks to find the correct one to use. Reproducible: Always Steps to Reproduce: 1. Compose an email. 2. Click into the recipient address field, wait for the autocompletion popup (type something if needed for the popup). 3. Click one address. 4. Double-click the same address to have it inserted into the recipient field. Actual Results: The recipient field is empty, nothing is inserted or completed. Expected Results: Less buggy software... ;;-)) -- 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 323948] New: Reply doesn't select identity to use from email being replied to
https://bugs.kde.org/show_bug.cgi?id=323948 Bug ID: 323948 Summary: Reply doesn't select identity to use from email being replied to Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz Reply to an email does not select the correct identity to use for the reply. It always uses the default identity, but it should use the identity matching my email adddress in the email I'm replying to. Reproducible: Always Steps to Reproduce: 1. Click reply on an email sent to one of your identities that is NOT your default one. 2. 3. Actual Results: The reply has the default identity selected. Expected Results: Reply uses the same identity as the email being replied to! This is a regression from kmail 1. Matching for identity selection should be made on email address only - not on other parts like name, that can change, especially when replying to an older 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
[kmail2] [Bug 323872] Failure to read write-protected mbox files
https://bugs.kde.org/show_bug.cgi?id=323872 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #2 from Volker Kuhlmann --- Thanks! But especially for compatibility I would expect write-protected historic mbox files to be accessible easily. -- 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 323875] New: mixedmaildir resource buggy and sloooow
https://bugs.kde.org/show_bug.cgi?id=323875 Bug ID: 323875 Summary: mixedmaildir resource buggy and slw Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz The mixedmaildir resource looks like a really good idea, but... To scan an mbox file with 6000 emails after 1 new mail has been added, mutt needs less than 1 second for a complete and accurate scan, and that without any kind of index caching or any other bloat at all. kmail needs 10s of seconds to 5 minutes And that will all that phenomenal SQL bloat hanging off it - or perhaps that's the real problem. A complete restart of akonadi and kmail will be necessary when selecting different folders and an email in each of them without making sure first that the previously selected Frequently kmail gets stuck "synchronising" altogether. The only recourse is to quit kmail, stop akonadi, wait for akonadi to exit (a minute is easily possible - dang it's tempting to use kill), and start again. But then it could be it's not a deadlock - difficult to tell how many hours to wait for a miraculous recovery, with tens of folders times 5 minutes. Reproducible: Always Steps to Reproduce: 1. Create a mixedmaildir resource for an existing directory with subdirectories, all containing only mbox files. 2. Try to get some work done: append an email with another program + with kmail, resync directories incl content because kmail's state isn't accurate or uptodate, select a folder and an email within, then select another folder and an email within that before the first one finished doing anything useful to the user (like show the selected email), ... 3. Actual Results: Unusably slow perofrmance, deadlocks. Expected Results: Speedy performance on modern hardware. -- 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 323872] New: Failure to read write-protected mbox files
https://bugs.kde.org/show_bug.cgi?id=323872 Bug ID: 323872 Summary: Failure to read write-protected mbox files Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz As part of a mixedmaildir resource one subdirectory contains write-protected mbox files. kmail is unable to read them: "failed to read Mbox folder .../.folder.direcotry/folder" (At least it no longer crashes, like it used to.) Reproducible: Always Steps to Reproduce: 1. Create mixedmaildir resource 2. Copy a write-protected mbox file into this 3. Try to get kmail to show its content Actual Results: Error message, no action. Expected Results: The contents of the mbox folder to be displayed. "write-protected" still means read, copy and search are expected actions. -- 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 320158] kmail2 doesn't display all emails
https://bugs.kde.org/show_bug.cgi?id=320158 --- Comment #2 from Volker Kuhlmann --- Well I found the problem. I refuse to have my mail stored in the bowels of kmail and want to know exactly hwere it is, so I shifted the "Local Mail" maildir folder to ~/Mail/local/. In the interim, something, somewhere, created a ~/Mail/.local.directory/ maildir folder instead and started using that instead. While the .XXX.directory symlink lafaffel is a good way to flag which subdirectories are part of the mail directory and which are not, in all other respects it's an abominable PITA!!! -- 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 320158] kmail2 doesn't display all emails
https://bugs.kde.org/show_bug.cgi?id=320158 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #1 from Volker Kuhlmann --- Having the same problem here: openSUSE 12.3, 4.10.5 kmail's default "Local Mail" maildir resource doesn't show all mail it contains, and can't be made to do so. Restarting kmail doesn't fix the problem, neithe rdoes restarting akonadi. "Updating" the "Local Mail" folder in or exxcluding all subfolders, does absolutely nothing. qdbus org.freedesktop.Akonadi.Control /AgentManager org.freedesktop.Akonadi.AgentManager.agentInstanceSynchronize akonadi_maildir_resource_0 Causes a synchronisation, as shown in kmail lower right corner (click blue up-arrow), but the sync itself seems to be broken as it doesn't align aknoadi's/kmail's brains to on-disk reality. This is both unusable and useless! -- 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
[kdepim] [Bug 323476] Sort akonadi resources by type
https://bugs.kde.org/show_bug.cgi?id=323476 --- Comment #3 from Volker Kuhlmann --- Thanks muchly!! I'm having big issues with akondai resources in general :-((, essentially not tracking sources sensibly. I'm working on reports. -- 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
[kdepim] [Bug 323476] Sort akonadi resources by type
https://bugs.kde.org/show_bug.cgi?id=323476 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #1 from Volker Kuhlmann --- This is particularly problematic when there are a dozen imap resources that all have to be checked because akonadi has yet another problem with them, and in between a longlist of other stuff they don't stand out. The quick search bar at the top is useless for this because it can only search by resource name; typing "imap" gives an empty list. -- 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 323572] Crash on start after I quit previous kmail because it got stuck on local folder
https://bugs.kde.org/show_bug.cgi?id=323572 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #1 from Volker Kuhlmann --- Before I started the second kmail2: user6427 2.9 0.7 1711652 118400 ? Sl 10:43 0:57 /usr/bin/kmail -caption KMail After I started the second kmail2 that crashed: user9582 0.0 0.1 405536 29148 ?S11:23 0:00 /usr/bin/kmail -caption KMail user9584 0.0 0.0 0 0 ?Z11:23 0:00 [kmail] Two new processes - one still stuck, the other undead. -- 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 323572] New: Crash on start after I quit previous kmail because it got stuck on local folder
https://bugs.kde.org/show_bug.cgi?id=323572 Bug ID: 323572 Summary: Crash on start after I quit previous kmail because it got stuck on local folder Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz Application: kmail (4.10.5) KDE Platform Version: 4.10.5 "release 1" 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: There are problems with kmail getting stuck synchronising folders in a mixedmaildir resource. I quit that kmail, but the process never exits. I start another kmail from the desktop, which crashed before opening any window. The backtraces of previous reports did not look similar to this one to me. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x2b904f563c00 (LWP 6427))] Thread 3 (Thread 0x2b9055f23700 (LWP 6431)): #0 0x2b903b73e964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x2b90469db7c7 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x2b90469db7f9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x2b903b73ae0f in start_thread () from /lib64/libpthread.so.0 #4 0x2b90395947dd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x2b9056244700 (LWP 6432)): #0 0x2b903958b87d in poll () from /lib64/libc.so.6 #1 0x2b90412aeaa4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x2b90412aebc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x2b9038c5e2e6 in QEventDispatcherGlib::processEvents (this=0x13a43c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x2b9038c2eadf in QEventLoop::processEvents (this=this@entry=0x2b9056243e00, flags=...) at kernel/qeventloop.cpp:149 #5 0x2b9038c2ed68 in QEventLoop::exec (this=0x2b9056243e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x2b9038b310f0 in QThread::exec (this=) at thread/qthread.cpp:542 #7 0x2b9038b340cc in QThreadPrivate::start (arg=0x13b5420) at thread/qthread_unix.cpp:338 #8 0x2b903b73ae0f in start_thread () from /lib64/libpthread.so.0 #9 0x2b90395947dd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x2b904f563c00 (LWP 6427)): [KCrash Handler] #6 KStatusNotifierItem::setStatus (this=0x1377c90, status=KStatusNotifierItem::Active) at /usr/src/debug/kdelibs-4.10.5/kdeui/notifications/kstatusnotifieritem.cpp:156 #7 0x2b9037aaa4fd in KMail::KMSystemTray::setMode (this=0x1377c90, newMode=0) at /usr/src/debug/kdepim-4.10.5/kmail/kmsystemtray.cpp:162 #8 0x2b9037ab80c6 in KMKernel::toggleSystemTray (this=0x7fff08394200) at /usr/src/debug/kdepim-4.10.5/kmail/kmkernel.cpp:2062 #9 0x2b9037b09bd7 in KMMainWidget::readConfig (this=this@entry=0x30db310) at /usr/src/debug/kdepim-4.10.5/kmail/kmmainwidget.cpp:980 #10 0x2b9037b0a0e1 in KMMainWidget::KMMainWidget (this=0x30db310, parent=, aGUIClient=0x2921680, actionCollection=, config=...) at /usr/src/debug/kdepim-4.10.5/kmail/kmmainwidget.cpp:267 #11 0x2b9037a6b25b in KMMainWin::KMMainWin (this=0x2921620, __in_chrg=, __vtt_parm=) at /usr/src/debug/kdepim-4.10.5/kmail/kmmainwin.cpp:67 #12 0x2b9037abb5ff in KMKernel::openReader (this=0x7fff08394200, onlyCheck=onlyCheck@entry=false) at /usr/src/debug/kdepim-4.10.5/kmail/kmkernel.cpp:578 #13 0x2b9037abb800 in KMKernel::action (this=this@entry=0x7fff08394200, mailto=mailto@entry=false, check=check@entry=false, to=..., cc=..., bcc=..., subj=..., body=..., messageFile=..., attachURLs=..., customHeaders=...) at /usr/src/debug/kdepim-4.10.5/kmail/kmkernel.cpp:1372 #14 0x2b9037abc157 in KMKernel::handleCommandLine (this=0x7fff08394200, noArgsOpensReader=true) at /usr/src/debug/kdepim-4.10.5/kmail/kmkernel.cpp:494 #15 0x004034e7 in KMailApplication::newInstance (this=0x7fff083941d0) at /usr/src/debug/kdepim-4.10.5/kmail/main.cpp:87 #16 0x2b9036ec9ad2 in KUniqueApplicationAdaptor::newInstance (this=0xf00020, asn_id=..., args=...) at /usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kuniqueapplication.cpp:442 #17 0x2b9036ec9b54 in qt_static_metacall (_a=0x7fff08393220, _id=, _o=, _c=) at /usr/src/debug/kdelibs-4.10.5/build/kdeui/kuniqueapplication_p.moc:58 #18 KUniqueApplicationAdaptor::qt_static_metacall (_o=, _c=, _id=, _a=0x7fff08393220) at /usr/src/debug/kdelibs-4.10.5/build/kdeui/kuniqueapplication_p.moc:52 #19 0x2b9036ec9c8b in KUniqueApplicationAdaptor::qt_metacall (this=0xf00020, _c=QMetaObject::InvokeMetaMethod,
[kmail2] [Bug 320313] Constant drivel from kmail, "Resouce KMail Folders is broken. This resource is now online"
https://bugs.kde.org/show_bug.cgi?id=320313 --- Comment #3 from Volker Kuhlmann --- This problem frequently occurs when synchronising mixedmaildir folders, e.g. I ran qdbus org.freedesktop.Akonadi.Control /AgentManager org.freedesktop.Akonadi.AgentManager.agentInstanceSynchronize akonadi_mixedmaildir_resource_0 and kmail is going bananas. It also takes exorbitant amounts of time to do that job - half an hour easily. -- 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 316888] Folder retrieval options are not preserved across reboot
https://bugs.kde.org/show_bug.cgi?id=316888 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #1 from Volker Kuhlmann --- Problem also occurs with openSUSE 12.3 KDE 4.10.5. I find this annoying and a waste of bandwidth - if I have downloaded it once, I don't need to download it again! Btw the reboot is not necessary. Just quitting kmail is enough; when starting it again the setting is reverted from "never" to 60 minutes. -- 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
[kaddressbook] [Bug 323519] New: Folder properties icon change makes folder name disappear
https://bugs.kde.org/show_bug.cgi?id=323519 Bug ID: 323519 Summary: Folder properties icon change makes folder name disappear Classification: Unclassified Product: kaddressbook Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz CC: to...@kde.org In kaddressbook with a 3-column view, the left column has an address book list. In RMB Folder properties the icon can be changed for each address book. The default is the "network server" icon. Changing the icon here and saving makes the address book name disappear from contacts displayed in the right column. The only way to reset this is to go to system settings→personal info (select address book source) →Modify→OK. Reproducible: Always Steps to Reproduce: 1. Configure a new address book in system settings→personal info, use any empty diretory. 2. Create a contact in this. 3. RMB on the address bok name in column 1 of the 3 column view in kontact, Folder→Properties. Change icon. 4. Select this contact in column 2. Actual Results: Column 3 no longer shows the name of the address book this contact came from. Expected Results: The name of the source address book is shown with the contacts info. -- 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 320313] Constant drivel from kmail, "Resouce KMail Folders is broken. This resource is now online"
https://bugs.kde.org/show_bug.cgi?id=320313 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #2 from Volker Kuhlmann --- Confirmed for openSUSE 12.3, kmail2 4.10.5. Happens with maildirmixed resource. The condition in comment#1 is not a requirement, it happens when kmail just scans the directory or otherwise keeps itself busy (which it does a lot on mixed maildir/mbox folders). The problem also occurs when using "update folder and subfolders" and when modifying the resource in system settings->personal info->akonadi -- 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 323515] New: Entering folder always shows email - unwanted when checking spam
https://bugs.kde.org/show_bug.cgi?id=323515 Bug ID: 323515 Summary: Entering folder always shows email - unwanted when checking spam Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz When selecting a folder in an IMAP mailbox, some email is always displayed. When I am checking the spam folder this is very much unwanted behaviour! I don't want to download this rubbish, I just need to read the subjects and mark stuff as read. And after moving an email, I don't want the next one shown either - only the message list. kmail is configured to "jump to unread email" when entering folder, but as long as it always displays the email (necessitating a download) it doesn't matter which one it jumps to. Reproducible: Always Steps to Reproduce: 1. Navigate to an IMAP mailbox. 2. Select its spam folder. 3. Actual Results: The last selected, first unread, or whatever other email is downlaoded and shown. Expected Results: Display of message list, option to move and mark emails as read WITHOUT displaying their bodies. -- 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 323513] New: Contacts resource (.vcf directory) synchronisation incomplete
https://bugs.kde.org/show_bug.cgi?id=323513 Bug ID: 323513 Summary: Contacts resource (.vcf directory) synchronisation incomplete Classification: Unclassified Product: Akonadi Version: 4.10 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Contacts resource Assignee: to...@kde.org Reporter: list0...@paradise.net.nz CC: kdepim-bugs@kde.org, vkra...@kde.org The akonadi contacts resource doesn't sync properly with on-disk vcard files. It notices new files and those that have gone absent, but does nothing about changed ones. The only solution is to delete all ~/.local/share/contacts/*.vcf first, and then synchronise the resource. Reproducible: Always Steps to Reproduce: 1. rm ~/.local/share/contacts/*.vcf 2. qdbus org.freedesktop.Akonadi.Control /AgentManager org.freedesktop.Akonadi.AgentManager.agentInstanceSynchronize akonadi_contacts_resource_0 3. kaddressbookmigrator 4. qdbus org.freedesktop.Akonadi.Control /AgentManager org.freedesktop.Akonadi.AgentManager.agentInstanceSynchronize akonadi_contacts_resource_0 Actual Results: Changed contacts are never picked up. Added/deleted contacts may be picked up eventually. Expected Results: After synchronisation, the address book content reflects the actual state of the on-disk resource (= directory full of vcard files). Only steps 3 and 4 above should be necessary. This is for loading address book data into KDE from scripts; whether to use kaddrbookmigrator or creating vcard files directly in the resource directory is beside the point. Unfortunately there appears to be no command line push/modify/delete of contacts. -- 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
[kmail] [Bug 220608] Kmail does not suggest/complete adresses from (external) adress books for new mails
https://bugs.kde.org/show_bug.cgi?id=220608 --- Comment #12 from Volker Kuhlmann --- The new warning in kmail that semantic desktop must be running is extremely misleading - but only goes away after turning on nepomuk. To get autocompletion working, one has to delete the tabs and feeder agents (the latter will be recreated) and turn nepomuk off completely. There are other bugs too - the address book resource synchronisation most of the time does nothing. It may detect new or deleted vcard files, but fails to do any action on changed ones. These are vcard files in ~/.local/share/contacts/ created by kaddressbookmigrator. No, restarting akonadi or restarting KDE does NOT help. All this feeder/resource/whatnot stuff is not in good shape. -- 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 301448] Only email addresses are saved to "Recent Addresses", full names are not
https://bugs.kde.org/show_bug.cgi?id=301448 --- Comment #2 from Volker Kuhlmann --- bug#283991 is a duplicate of this -- 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 283991] Email Address Completition Incomplete
https://bugs.kde.org/show_bug.cgi?id=283991 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #9 from Volker Kuhlmann --- Problem exists with kmail2 4.10.5, openSUSE 12.3 rpms. Problem did not exist with kmail 1.x. See https://bugs.kde.org/show_bug.cgi?id=301448 (bug#301448), of which this is a duplicate. -- 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
[kmail] [Bug 220608] Kmail does not suggest/complete adresses from (external) adress books for new mails
https://bugs.kde.org/show_bug.cgi?id=220608 --- Comment #10 from Volker Kuhlmann --- Will Stephenson suggests https://bugs.kde.org/show_bug.cgi?id=237511#c25 if you open "akonadiconsole" is the status of "Nepomuk contacts feeder" in the Agents tab "Indexing completed"? My "Akonadi Nepomuk Feeder" in the agents tab is running and indexing is complete. -- 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
[kmail] [Bug 220608] Kmail does not suggest/complete adresses from (external) adress books for new mails
https://bugs.kde.org/show_bug.cgi?id=220608 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #9 from Volker Kuhlmann --- openSUSE 12.3, KDE 4.10.5, kmail2 4.10.5 Address autocompletion IS NOT WORKING. Only autocompletion from recent addresses works. In my system settings there is a "Personal Contacts" configured; this is there automatically. It's located at ~/.local/share/contacts/ kmail warned that nepomuk semantic desktop must be running. I started nepomuk, turned on everything in it (but restricted file indexing to ~/.kde4, ~/.local, ~/.config - the rest is crazy), and make sure it is running. No autocompletion from address book. The "Select recipient" button works, from the same address book. -- 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 323474] New: Autocompletion from recent addresses needs restart to turn off
https://bugs.kde.org/show_bug.cgi?id=323474 Bug ID: 323474 Summary: Autocompletion from recent addresses needs restart to turn off Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz The autocompletion of addresses from the recent addresses list is controlled by Settings->Composer->"Use recent addreses for autocompletion". When this is off, turning it on gives autocompletion from recent addresses in the composer window. Turning it back off does not take effect until after a kmail restart. Reproducible: Always Steps to Reproduce: 1. Turn off Setting->Composer->"Use recent addreses for autocompletion" 2. restart kmail 3. Compose an email, verify recent addresses are not used for autocompletion. 4. Turn this on in the settings. 5. Compose an email, verify recent addresses are used for autocompletion. 6. Turn this off in the settings, 7. Compose an email, verify recent addresses are not used for autocompletion. Actual Results: Autocompletion is still used, although it is turned off in the settings. After restarting kmail this function is indeed off. Expected Results: Function only available when enabled. A kmail restart should not be necessary. -- 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 301448] Only email addresses are saved to "Recent Addresses", full names are not
https://bugs.kde.org/show_bug.cgi?id=301448 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #1 from Volker Kuhlmann --- Problem exists with kmail2 4.10.5, openSUSE 12.3 rpms. Problem did not exist with kmail 1.x. -- 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 323399] New: Closing kmail does not exit, crash on new start
https://bugs.kde.org/show_bug.cgi?id=323399 Bug ID: 323399 Summary: Closing kmail does not exit, crash on new start Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz Application: kmail (4.10.5) KDE Platform Version: 4.10.5 "release 1" 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: Exited kmail with ^Q intentionally, but the process didn't exit. Then I noticed I still had a composition window open - oops. I finished that email and sent it - the notice in the Notifications was that it was successfully sent. I was then expecting the kmail process to exit. When it didn't, I started another kmail, and got drkon It appears the newly started kmail crashed. user 23353 6.0 0.7 1688232 117092 ? Tl 18:01 1:13 /usr/bin/kmail -caption KMail user 24919 0.0 0.1 405536 29148 ? S18:16 0:00 /usr/bin/kmail -caption KMail user 24924 2.7 0.3 335268 51108 ? Sl 18:16 0:08 /usr/lib64/kde4/libexec/drkonqi -display :0 --appname kmail --apppath /usr/bin --signal 11 --pid 23353 --appversion 4.10.5 --programname KMail --bugaddress sub...@bugs.kde.org --startupid tui.site;1376288213;714460;2768_TIME14982720 user 24925 0.0 0.0 0 0 ? Z18:16 0:00 [kmail] -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x2ae15bd2ac00 (LWP 23353))] Thread 4 (Thread 0x2ae1626e9700 (LWP 23356)): #0 0x2ae147f05964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x2ae1531a27c7 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x2ae1531a27f9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x2ae147f01e0f in start_thread () from /lib64/libpthread.so.0 #4 0x2ae145d5b7dd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x2ae162a02700 (LWP 23357)): #0 0x7fff36fff743 in clock_gettime () #1 0x2ae145d6d53d in clock_gettime () from /lib64/libc.so.6 #2 0x2ae145350d94 in do_gettime (frac=0x2ae162a01b58, sec=0x2ae162a01b50) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x2ae145425bed in QTimerInfoList::updateCurrentTime (this=this@entry=0x2469ba0) at kernel/qeventdispatcher_unix.cpp:354 #5 0x2ae145425f33 in QTimerInfoList::timerWait (this=0x2469ba0, tm=...) at kernel/qeventdispatcher_unix.cpp:461 #6 0x2ae14542499c in timerSourcePrepareHelper (src=, timeout=0x2ae162a01c44) at kernel/qeventdispatcher_glib.cpp:136 #7 0x2ae145424a45 in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #8 0x2ae14da75338 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #9 0x2ae14da759cb in ?? () from /usr/lib64/libglib-2.0.so.0 #10 0x2ae14da75bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #11 0x2ae1454252e6 in QEventDispatcherGlib::processEvents (this=0x23345e0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #12 0x2ae1453f5adf in QEventLoop::processEvents (this=this@entry=0x2ae162a01e00, flags=...) at kernel/qeventloop.cpp:149 #13 0x2ae1453f5d68 in QEventLoop::exec (this=0x2ae162a01e00, flags=...) at kernel/qeventloop.cpp:204 #14 0x2ae1452f80f0 in QThread::exec (this=) at thread/qthread.cpp:542 #15 0x2ae1452fb0cc in QThreadPrivate::start (arg=0x257e550) at thread/qthread_unix.cpp:338 #16 0x2ae147f01e0f in start_thread () from /lib64/libpthread.so.0 #17 0x2ae145d5b7dd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x2ae1a6b87700 (LWP 24312)): #0 0x2ae14dab2810 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x2ae14dab2a69 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #2 0x2ae14da75343 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #3 0x2ae14da759cb in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x2ae14da75bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x2ae1454252e6 in QEventDispatcherGlib::processEvents (this=0x4811180, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x2ae1453f5adf in QEventLoop::processEvents (this=this@entry=0x2ae1a6b86dd0, flags=...) at kernel/qeventloop.cpp:149 #7 0x2ae1453f5d68 in QEventLoop::exec (this=0x2ae1a6b86dd0, flags=...) at kernel/qeventloop.cpp:204 #8 0x2ae1452f80f0 in QThread::exec (this=) at thread/qthread.cpp:542 #9 0x2ae1453d629f in QInotifyFileSystemWatcherEngine::run (this=0x5530fd
[kontact] [Bug 323397] New: Crash creating a todo
https://bugs.kde.org/show_bug.cgi?id=323397 Bug ID: 323397 Summary: Crash creating a todo Classification: Unclassified Product: kontact Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz Application: kontact (4.10.5) KDE Platform Version: 4.10.5 "release 1" 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: I have 3 calendars configured. One has a todo with sub todos, in which I added a sub todo, but stored in another calendar (because that's where I want it). Turning the display of all calendars off except the one in whcih the sub todo was just added shows the sub todo, but not the todo. That's one of the possible expected behaviours. Adding the todo into this calendar as well (it is empty and only there to provide a grouping heading) with the same name as already exists in the other calendar not currently displayed caused this crash. The reason for splitting todos into different calendars is that these calendars are for different purposes and may be shared differently between local users. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x2b807adde2c0 (LWP 6720))] Thread 3 (Thread 0x2b80804aa700 (LWP 6721)): #0 0x2b806f3fd964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x2b806b4077c7 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x2b806b4077f9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x2b806f3f9e0f in start_thread () from /lib64/libpthread.so.0 #4 0x2b8069ccb7dd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x2b80807c3700 (LWP 6722)): #0 0x2b8069cc287d in poll () from /lib64/libc.so.6 #1 0x2b80703b0aa4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x2b80703b0bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x2b80688f42e6 in QEventDispatcherGlib::processEvents (this=0xbaaa50, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x2b80688c4adf in QEventLoop::processEvents (this=this@entry=0x2b80807c2e00, flags=...) at kernel/qeventloop.cpp:149 #5 0x2b80688c4d68 in QEventLoop::exec (this=0x2b80807c2e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x2b80687c70f0 in QThread::exec (this=) at thread/qthread.cpp:542 #7 0x2b80687ca0cc in QThreadPrivate::start (arg=0xba9d80) at thread/qthread_unix.cpp:338 #8 0x2b806f3f9e0f in start_thread () from /lib64/libpthread.so.0 #9 0x2b8069ccb7dd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x2b807adde2c0 (LWP 6720)): [KCrash Handler] #6 deref (this=0x1001f) at /usr/include/QtCore/qatomic_x86_64.h:133 #7 deref (value=0x1f0001, d=0x10013) at /usr/include/QtCore/qsharedpointer_impl.h:340 #8 internalCopy (other=..., this=0x1fd3570) at /usr/include/QtCore/qsharedpointer_impl.h:412 #9 operator= (other=..., this=0x1fd3570) at /usr/include/QtCore/qsharedpointer_impl.h:483 #10 qCopy*, QSharedPointer*> (dest=0x1fd3570, end=0x1fd36a0, begin=0x1fd3580) at /usr/include/QtCore/qalgorithms.h:82 #11 QVector >::erase (this=this@entry=0x10e6978, abegin=, aend=aend@entry=0x1fd3570) at /usr/include/QtCore/qvector.h:634 #12 0x2b80c47a47f6 in remove (i=-1, this=0x10e6978) at /usr/include/QtCore/qvector.h:376 #13 IncidenceTreeModel::Private::insertNode (this=this@entry=0x10e6960, prenode=..., silent=silent@entry=false) at /usr/src/debug/kdepim-4.10.5/korganizer/views/todoview/incidencetreemodel.cpp:388 #14 0x2b80c47a56a7 in IncidenceTreeModel::Private::onRowsInserted (this=0x10e6960, parent=..., begin=8, end=256) at /usr/src/debug/kdepim-4.10.5/korganizer/views/todoview/incidencetreemodel.cpp:298 #15 0x2b80688db29f in QMetaObject::activate (sender=0xf602c0, m=, local_signal_index=, argv=0x7fff4ee32720) at kernel/qobject.cpp:3548 #16 0x2b8068925974 in QAbstractItemModel::rowsInserted (this=, _t1=..., _t2=8, _t3=256) at .moc/release-shared/moc_qabstractitemmodel.cpp:197 #17 0x2b80688c069d in QAbstractItemModel::endInsertRows (this=0xf602c0) at kernel/qabstractitemmodel.cpp:2433 #18 0x2b806938b994 in QSortFilterProxyModelPrivate::insert_source_items (this=this@entry=0xf602f0, source_to_proxy=..., proxy_to_source=..., source_items=..., source_parent=..., orient=orient@entry=Qt::Vertical, emit_signal=emit_signal@entry=true) at itemviews/qsortfilterproxymodel.cpp:695 #19 0x2b806938f238 in QSortFilterProxyModelPrivate::source_items_inserted (this=this@entry=0xf602f0, source_parent=..., start=, en
[kmail2] [Bug 323277] Lockup/crash when marking mails as read
https://bugs.kde.org/show_bug.cgi?id=323277 Volker Kuhlmann changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #1 from Volker Kuhlmann --- kmail restart by drkonqi failed. There are these processes: 8:volker 22949 0.0 0.1 405528 28956 ?S14:31 0:00 /usr/bin/kmail -caption KMail 9:volker 22952 0.0 0.0 0 0 ?Z14:31 0:00 [kmail] 16:volker 25816 0.1 0.1 405396 28428 ?S15:00 0:00 /usr/bin/kmail The ones from 14:31 are the crash ones, the 15:00 one would be the restart - but no window opens. I'll have to killall kmail. -- 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 323277] New: Lockup/crash when marking mails as read
https://bugs.kde.org/show_bug.cgi?id=323277 Bug ID: 323277 Summary: Lockup/crash when marking mails as read Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz Application: kmail (4.10.5) KDE Platform Version: 4.10.5 "release 1" 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: Enter local mail folder, select all emails with ^A, mark all as read with ^R. The whole box was unread emails, the first email was selected when selecting box. There are just over 2000 emails in this box. - Custom settings of the application: The local mailbox in question is a kmail mail directory, the box an mbox file. New emails are marked as "read" after 5 seconds. kmail is quiet slow at processing the status flags of 200 emails, I have observed this kind of problem repeatedly. Changing mail boxes quickly doesn't help, although this time I avoided this AFAICR until all kmail operations were completed. At a wild guess, the 5s timeout for the selected email hit before the update for the lot was completed, and status updating has a concurrency problem. 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 0x2b6f551a3c00 (LWP 22477))] Thread 3 (Thread 0x2b6f5bb60700 (LWP 22481)): #0 0x2b6f4137e964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x2b6f4c61b7c7 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x2b6f4c61b7f9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x2b6f4137ae0f in start_thread () from /lib64/libpthread.so.0 #4 0x2b6f3f1d47dd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x2b6f5be79700 (LWP 22482)): #0 0x2b6f3f1cb87d in poll () from /lib64/libc.so.6 #1 0x2b6f46eeeaa4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x2b6f46eeebc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x2b6f3e89e2e6 in QEventDispatcherGlib::processEvents (this=0x2b6f5c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x2b6f3e86eadf in QEventLoop::processEvents (this=this@entry=0x2b6f5be78e00, flags=...) at kernel/qeventloop.cpp:149 #5 0x2b6f3e86ed68 in QEventLoop::exec (this=0x2b6f5be78e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x2b6f3e7710f0 in QThread::exec (this=) at thread/qthread.cpp:542 #7 0x2b6f3e7740cc in QThreadPrivate::start (arg=0x2189d90) at thread/qthread_unix.cpp:338 #8 0x2b6f4137ae0f in start_thread () from /lib64/libpthread.so.0 #9 0x2b6f3f1d47dd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x2b6f551a3c00 (LWP 22477)): [KCrash Handler] #6 0x2b6f3cc1c1fb in KStatusNotifierItem::setStatus (this=0x20880c0, status=KStatusNotifierItem::Active) at /usr/src/debug/kdelibs-4.10.5/kdeui/notifications/kstatusnotifieritem.cpp:161 #7 0x2b6f3d6ea4fd in KMail::KMSystemTray::setMode (this=0x20880c0, newMode=0) at /usr/src/debug/kdepim-4.10.5/kmail/kmsystemtray.cpp:162 #8 0x2b6f3d6f80c6 in KMKernel::toggleSystemTray (this=0x7fff095d8780) at /usr/src/debug/kdepim-4.10.5/kmail/kmkernel.cpp:2062 #9 0x2b6f3d749bd7 in KMMainWidget::readConfig (this=this@entry=0x57f6d10) at /usr/src/debug/kdepim-4.10.5/kmail/kmmainwidget.cpp:980 #10 0x2b6f3d74a0e1 in KMMainWidget::KMMainWidget (this=0x57f6d10, parent=, aGUIClient=0x45ac5f0, actionCollection=, config=...) at /usr/src/debug/kdepim-4.10.5/kmail/kmmainwidget.cpp:267 #11 0x2b6f3d6ab25b in KMMainWin::KMMainWin (this=0x45ac590, __in_chrg=, __vtt_parm=) at /usr/src/debug/kdepim-4.10.5/kmail/kmmainwin.cpp:67 #12 0x2b6f3d6fb5ff in KMKernel::openReader (this=0x7fff095d8780, onlyCheck=onlyCheck@entry=false) at /usr/src/debug/kdepim-4.10.5/kmail/kmkernel.cpp:578 #13 0x2b6f3d6fb800 in KMKernel::action (this=this@entry=0x7fff095d8780, mailto=mailto@entry=false, check=check@entry=false, to=..., cc=..., bcc=..., subj=..., body=..., messageFile=..., attachURLs=..., customHeaders=...) at /usr/src/debug/kdepim-4.10.5/kmail/kmkernel.cpp:1372 #14 0x2b6f3d6fc157 in KMKernel::handleCommandLine (this=0x7fff095d8780, noArgsOpensReader=true) at /usr/src/debug/kdepim-4.10.5/kmail/kmkernel.cpp:494 #15 0x004034e7 in KMailApplication::newInstance (this=0x7fff095d8750) at /usr/src/debug/kdepim-4.10.5/kmail/main.cpp:87 #16 0x2b6f3cb09ad2 in KUniqueApplicationAdaptor::newInstance (this=0x1bbbe40, asn_id=..., args=...) at /usr/src/debug/kde
[Bug 41012] message numbering in index window
https://bugs.kde.org/show_bug.cgi?id=41012 Volker Kuhlmann changed: What|Removed |Added Status|RESOLVED|REOPENED CC||list0...@paradise.net.nz Resolution|WAITINGFORINFO |--- --- Comment #4 from Volker Kuhlmann --- Still valid. -- 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 61384] re-index folder function under RMB
https://bugs.kde.org/show_bug.cgi?id=61384 Volker Kuhlmann changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WAITINGFORINFO |--- -- 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 61384] re-index folder function under RMB
https://bugs.kde.org/show_bug.cgi?id=61384 --- Comment #12 from Volker Kuhlmann --- Yes, still valid. Some method of re-indexing mail files (mbox in particular, but also imap and maildir) is needed because kmail tends to get out of sync. -- 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 102965] Window shown at session restart: should *remember* if it was shown
http://bugs.kde.org/show_bug.cgi?id=102965 Volker Kuhlmann list0570 paradise net nz changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #4 from Volker Kuhlmann 2008-12-29 01:46:36 --- Confirmed for: KDE Version 1.9.10 (KDE 3.5.10 "release 21.11" , openSUSE ) Application E-Mail Client Operating System Linux (x86_64) release 2.6.27.7-9-default Compiler Target: x86_64-suse-linux kmail is closed, only the panel applet icon is showing. Saving this session state and login in again always shows kmail maximised. -- 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
