[kmail2] [Bug 364558] Flagging as "unread" triggers multiple-selection
https://bugs.kde.org/show_bug.cgi?id=364558 --- Comment #2 from Tim Holy --- Apologies, but I now use my institution's webmail rather than kmail. Sounds like it may have been fixed, though, thanks! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."
https://bugs.kde.org/show_bug.cgi?id=246027 Tim Holy changed: What|Removed |Added CC||h...@pcg.wustl.edu --- Comment #21 from Tim Holy --- I'm seeing this upon upgrade from Kubuntu 12.04 to 14.04. Doing strace -f -e trace=file /usr/bin/kmail revealed the following interesting lines: kmail2(8480)/libakonadi Akonadi::GetLockJob::Private::timeout: Timeout trying to get lock. Check who has acquired the name "org.kde.pim.SpecialCollections" on DBus, using qdbus or qdbusviewer. kmail2(8480)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::lockResult: Failed to get lock: "Timeout trying to get lock." kmail2(8480) MailCommon::Kernel::emergencyExit: "The Email program encountered a fatal error and will terminate now. The error was: Timeout trying to get lock." $ qdbus org.kde.pim.SpecialCollections / /Debug /MailDispatcherAgent /MainApplication /Settings $ qdbus | grep -C5 org.kde.pim.SpecialCollections org.kde.akonadi_baloo_indexer-2841 :1.65 org.freedesktop.Akonadi.Agent.akonadi_maildispatcher_agent org.freedesktop.Akonadi.MailDispatcherAgent org.kde.akonadi_maildispatcher_agent-2843 org.kde.pim.SpecialCollections :1.66 org.freedesktop.Akonadi.Agent.akonadi_migration_agent org.kde.akonadi_migration_agent-2845 :1.67 org.freedesktop.Akonadi.Agent.akonadi_newmailnotifier_agent I moved my ~/.config/akonadi and ~/.local/share/akonadi out of the way and rebooted, but this didn't help. One oddity is that new local-mail resources get added each time I fail to start kontact. I can delete them in the Akonadi Configuration module, so I have only one left. My mail is stored in ~/.local/share/local-mail. I have two POP3 accounts configured. -- 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 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."
https://bugs.kde.org/show_bug.cgi?id=246027 --- Comment #22 from Tim Holy --- I did some random sequence of deleting all akonadi resources (multiple times), starting kontact (multiple times), manually specifying a resource at ~/.local/share/local-mail, and restarting the mysql server. At a certain point I got to a stage where there was just one "Local Folders" resource listed in Akonadi Control. At the time is was listed as "syncing," so I waited until that finished and said Ready. From that point forward I have a better sense for my specific steps and the consequences were. I started Akonadi Control (with kontact not running) and then restarted the akonadi server. This produced two resources labeled "Local Folders" with status Ready. Restarting a second time, without launching kontact, kept it at 2 (it did not go to 3). Then, I tried starting kontact. For the first time, it did not crash, and I could even send a mail to myself. (yay!) However, there are two "Local Folders" in my list of mailboxes. One with a blue folder icon is empty. The other with some other icon (a computer?) seems to have my mail. "outbox", "sent-mail", and "trash" are not in their usual places near the top, instead they are sorted in alphabetical order, and they have standard folder-icons rather than the custom icons for things like "inbox", "outbox", etc. The new message I sent ended up inside the "new" (empty) Local Folders sent-mail folder, not my old one. I opened the properties on it, and unchecked "Act on new/unread mail in this folder". Then I sent another test message. It still ended up in the new (undesired) resource. I haven't yet dared to download my email, there will be quite a lot waiting and I am concerned it will target the wrong set of folders. I quit kontact, went back to Akonadi Control, and deleted the resource that was named something like ~/.local/share/akonadi_resource_6 or something. (Not my ".local/share/local-mail" one.) Then I restarted mysql to see if it would created a 2nd resource again. This time it did what it had done at the beginning: it gave me a startup error, and clicking on the link showed a file with lines like InnoDB: Unable to lock .libdata1, error:11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. I'm going to try logging out and logging back in again, so I'll hit submit here. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."
https://bugs.kde.org/show_bug.cgi?id=246027 --- Comment #23 from Tim Holy --- Well, in fact just waiting longer and/or stopping mysql made the InnoDB error go away, and now things seem to be mostly working. The worst consequences I've noticed so far are that: - My filter rules seem broken. All the old filters exist, but they ask me to specify the target directory. I presume this is a consequence of having gone through a period where certain folders didn't exist. This is a little sad, since I have something like 300 filters. - My addressbook settings seem to have been lost. I have an old (from 2012) backup std.vcf file, so I can recover some but not all. If anyone has tips about getting past these, I'm happy to hear about it. On the plus side: things seem noticeably faster, I am really looking forward to that. -- 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 334133] KMail filter does not find emails
https://bugs.kde.org/show_bug.cgi?id=334133 Tim Holy changed: What|Removed |Added CC||h...@pcg.wustl.edu --- Comment #2 from Tim Holy --- Searching inside sent-mail is only finding emails I wrote today. Given that there are >40k messages in that folder, going through and finding an email I sent sometime last year will not be pleasant. I hope someone responds soon with some tips for debugging 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 334133] KMail filter does not find emails
https://bugs.kde.org/show_bug.cgi?id=334133 --- Comment #3 from Tim Holy --- Update: in 333403 it seems that a fix has been implemented, it's just not in kubuntu yet. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 Tim Holy changed: What|Removed |Added CC||h...@pcg.wustl.edu --- Comment #61 from Tim Holy --- Are there any chances this will be backported to 4.8 and hence appear in the default packages for Kubuntu 12.04? Or should I upgrade to 4.9? -- 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 159634] kmail autosave function not saving at all after the requested time
http://bugs.kde.org/show_bug.cgi?id=159634 Tim Holy holy pcg wustl edu changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #7 from Tim Holy 2008-11-07 12:24:42 --- With Kubuntu Intrepid packages (kmail 1.10.1), the autosave feature often works for me. HOWEVER, there is at least one serious problem with the design of this feature. This can be revealed by doing the following (first, finish and send out any in-progress messages or save them as drafts, because otherwise you will lose all your work): 1. In konsole, navigate to ~/.kde/share/apps/kmail/autosave 2. Type "kontact &" 3. In kontact, start a new message 4. Wait for the autosave interval---you will see output on the command line when autosave executes 5. Examine cur/ for messages; you should see a file corresponding to your in-progress message (at least on Kubuntu, that is; from the above it seems this might not work for some people...) 6. Quit kontact. Wait a moment for it to really quit. Then restart kontact. Your in-progress message should pop up in a composer window, suggesting that all is right and good with the universe. 7. Quickly, in konsole examine the cur/ directory. You'll see it's _empty_. And there's nothing in new/ or tmp/, either. 8. Before the autosave interval expires, quit kontact. Wait. Restart it. Presto, you'll see that you've lost the in-progress message! Aside from this systematic way to replicate the problem, I should also mention that, over years of using kontact in KDE3, I've also lost in-progress messages after a kontact crash, even ones that had been autosaved previously. It's possible that these "bad" crashes always occurred in the first 1-2 minutes of starting kontact (and thus before the first new autosave), but my memory does not let me be sure of this. I wonder if it might be worth checking to see whether there is a brief moment in which the old autosaved files are deleted but the new ones are not written---if kontact crashes between those events, work is lost. So, to make autosave robust, kontact should: 1. at startup, stop deleting the files corresponding to autosaved messages, or execute autosave immediately after reloading any autosaved messages---that way if kontact crashes in the first minute or two after starting (something I've seen happen more than once...), the user doesn't lose data 2. execute autosave upon quitting (that way any changes that have been made since the last autosave are not lost) 3. in the middle of an autosave, insure that old autosaved files are never deleted until after new ones are written -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 159634] Autosaved KMail messages shouldn't be auto-removed on next application startup
https://bugs.kde.org/show_bug.cgi?id=159634 --- Comment #16 from Tim Holy 2010-07-11 23:11:18 --- Thomas, is there any chance the fix to this bug caused the following new one? https://bugs.kde.org/show_bug.cgi?id=236229 Or is that an independent issue? While the message is not deleted, you have to descend to the command line and your .kde directory to discover that. So the net effect, for many users, is the same. (For me, the current situation is an improvement because there is no real data loss.) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 242371] "Add to Address Book" does not work (akonadi MySQL down?)
https://bugs.kde.org/show_bug.cgi?id=242371 Tim Holy changed: What|Removed |Added CC||h...@pcg.wustl.edu --- Comment #1 from Tim Holy 2010-07-12 17:29:46 --- I get this too. It wouldn't shock me if this is related to this issue: http://randomguy3.wordpress.com/2010/06/01/d-bus-threading-issues/ But I don't know how to test that. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 184307] Template suddenly become %BLANK - no quote text in replies
https://bugs.kde.org/show_bug.cgi?id=184307 Tim Holy changed: What|Removed |Added CC||h...@pcg.wustl.edu --- Comment #30 from Tim Holy 2010-08-05 23:33:19 --- I don't know whether this will be helpful, but I triggered this bug when I changed the server for my POP3 account. This was Kubuntu Lucid, 4.4.2. Many thanks for posting the work-around! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 159634] Autosaved KMail messages shouldn't be auto-removed on next application startup
https://bugs.kde.org/show_bug.cgi?id=159634 --- Comment #14 from Tim Holy 2010-02-21 21:53:24 --- Thanks, Thomas! I'm looking forward to this! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 236229] dead letters not recovered on restart
https://bugs.kde.org/show_bug.cgi?id=236229 Tim Holy changed: What|Removed |Added CC||h...@pcg.wustl.edu -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 216043] Send Queued Messages button and menu items partially inoperative
https://bugs.kde.org/show_bug.cgi?id=216043 Tim Holy changed: What|Removed |Added CC||h...@pcg.wustl.edu --- Comment #1 from Tim Holy 2010-01-24 14:30:13 --- You can trigger this even if you don't directly queue to send later. I'm copying this from ubuntu bug 511524: Steps to reproduce this problem: 1. Put your network in some state where you can't send email (e.g., disconnect from the cable or wireless). 2. Compose a message to yourself and send it. After a while you will get the dialog saying the message can't be sent, and will be placed in your outbox 3. Under the file menu, you will now see that "Send queued messages" and "Send queued messages via..." will be enabled. If, at this point, you chose one of them, everything would be fine. 4. However, in this case don't do it right away: navigate to another folder, read some messages, etc. 5. Now check the file menu again: "Send queued messages" and "Send queued messages via..." will now be greyed out, even though that message is still queued in your outbox. You can send the message by selecting your outbox, which will re-enable those two menu options. I would think that the proper behavior would be to enable "Send queued messages" and "Send queued messages via..." anytime there are messages waiting in your outbox. ProblemType: Bug Architecture: i386 Date: Sat Jan 23 04:40:49 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/kontact Package: kontact 4:4.3.2-0ubuntu6 ProcEnviron: LANGUAGE=en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic SourcePackage: kdepim Uname: Linux 2.6.31-17-generic i686 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 159634] Autosaved KMail messages shouldn't be auto-removed on next application startup
https://bugs.kde.org/show_bug.cgi?id=159634 --- Comment #11 from Tim Holy 2010-02-08 16:07:05 --- Since I haven't updated this report recently, I thought it would be of value to report that the issues in comment #7 are still present in KDE 4.3.2 (Kubuntu 9.10). Does anyone have information about whether this has been fixed in the upcoming KDE SC 4.4? (I don't have a spare machine/hard drive space to test it myself, so I rely on distributor updates.) Or is this the kind of issue that the developers intend to fix via the transition to Akonadi? Best, --Tim -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 285809] Kmail dead slow while stuck synchronizing two folders in KMail maildirs
https://bugs.kde.org/show_bug.cgi?id=285809 Tim Holy changed: What|Removed |Added CC||h...@pcg.wustl.edu --- Comment #2 from Tim Holy --- I'm having this problem too, under 4.8.2 (Kubuntu 12.04). Details: My inbox has about 25000 messages in it. This process is running: usr/sbin/mysqld --defaults-file=/home/tim/.local/share/akonadi/mysql.conf --datadir=/home/tim/.local/share/akonadi/db_data/ --socket=/home/tim/.local/share/akonadi/socket-diva/mysql.socket Here are the agents under akonadiconsole: akonadi_pop3_resource_0 (POP3 E-Mail Server) akonadi_akonotes_resource_0 (AkoNotes) akonadi_pop3_resource_1 (POP3 E-Mail Server) akonadi_maildispatcher_agent (Mail Dispatcher Agent) akonadi_ical_resource_0 (ICal Calendar File) akonadi_maildir_resource_1 (Maildir) akonadi_mailfilter_agent (Mail Filter Agent) akonadi_nepomuk_feeder (Akonadi Nepomuk Feeder) akonadi_contacts_resource_0 (Personal Contacts) -- 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 80995] IMAP: attachment icons not immediately displayed
http://bugs.kde.org/show_bug.cgi?id=80995 Tim Holy holy pcg wustl edu changed: What|Removed |Added CC||h...@pcg.wustl.edu --- Comment #17 from Tim Holy 2009-01-18 22:48:36 --- FYI this is relevant for more than IMAP---it holds for POP too. The main problem is that in the absence of an attachment icon, the implication is that there _isn't_ an associated attachment; there is no way for the user to distinguish between "not enough information" and "this message doesn't have an attachment." It seems that the old (KDE3) Kontact must have maintained some type of database that stored information about the status of each message (attachment, reply/forward, etc). Wouldn't it be possible to migrate that database when the user upgrades to KDE4? Presumably it's too late for those of us who have already upgraded? I for one would appreciate a script that went through all the messages once and fixed their status. I even helped write such a script for a different purpose (migrating UTC->localized times in korganizer, see bug 165212), but in this case I don't yet know enough about how this information is stored to help out. -- 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
[kmail] [Bug 183348] Kmail filter extremely slow
https://bugs.kde.org/show_bug.cgi?id=183348 Tim Holy changed: What|Removed |Added CC||h...@pcg.wustl.edu --- Comment #10 from Tim Holy --- I'm using Kubuntu 16.04 (Kontact 5.1.3). I copied several hundred thousand emails over from an older install. I realized I had made a mistake in ordering the priority of my filters, so I modified them and then selected a folder with about 33K messages in it, selected all messages, and hit Ctrl-J. The progress was extremely slow, under 10 messages per second, running at least 2 threads (one kontact and one mysql) constantly. Note that, because this is a new installation, I have only 6 filters defined so far (in contrast to my hundreds of filters in my old installation), and the filter rules are extremely simple (all single-rule, most looking at List-Id). While preparing to comment here, I went and selected Help>Kontact Introduction to get my version number. When I came back to the folder, the filtering had stopped. I'm not certain whether it finished or terminated. If it finished, then I have a theory: display of folder contents is interfering with progress in filtering. -- 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 183348] Kmail filter extremely slow
https://bugs.kde.org/show_bug.cgi?id=183348 --- Comment #11 from Tim Holy --- Just a follow-up: I tried it again, and after selecting 33K emails and starting filtering, I switched to a different mail directory (one with very few emails in it) for display. This did *not* appear to help anything. But because I was watching it carefully I noticed more detail this time. The filtering was stuck on "Mail Filter Agent...0%" for several (10ish?) minutes, with `mysqld`, `akonadiserver`, `akonadi_maildir_resource`, and `kontact` being among the main processes. None of them were using a lot of CPU, this seems to be a disk-bound process. Then, after no visible sign of progress for many minutes, all of a sudden it ran through all 33K messages in fewer than 10 seconds. So I'd guess the main filtering is plenty fast. It seems to be some "preparatory" step that is really slow, and because it gives no visible sign of progress it's a likely source of complaints/trouble for users (I was pretty close to trying to cancel/reboot my laptop by the time it started making progress). Should this bug be changed from RESOLVED to something else? Or should I file this observation as a separate bug report? -- 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 364558] New: Flagging as "unread" triggers multiple-selection
https://bugs.kde.org/show_bug.cgi?id=364558 Bug ID: 364558 Summary: Flagging as "unread" triggers multiple-selection Product: kmail2 Version: 5.1.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: h...@pcg.wustl.edu I use threaded display, and I typically go through my mails hitting "+" to advance to the next unread message. I've had a long-standing bug that causes kmail to (unexpectedly) selected multiple messages, which can be dangerous: if you hit delete, then it affects all selected mails, not just the one you're reading now. Moreover, if there is more than a screenfull of messages between the initially-selected message and the next unread one, you may not even realize that multiple messages have been selected. Reproducible: Always Steps to Reproduce: - Select 2 consecutive mails in your inbox, hit "Ctrl-U" to flag them as unread - Select a message above the 2 unread message - Hit "+" to advance to the first unread message - Say to yourself, "hmmm, I'll deal with this later" and hit "Ctrl-U" to re-mark it as unread - Hit "+" to advance to the next unread message Actual Results: You should notice that both messages are selected. Expected Results: Only the 2nd message should be selected. -- 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
