Akonadi processes prevent you from safely removing a USB stick. Observed on Kubuntu 14.04, 64-bit, KDE 4.14.2, workspace 4.11.11. Selecting 'general' as the component because it seems to affect more than one thing. I know for a fact that it persists even while either akonadi_baloo_indexer or akonadi_sendlater_agent is the only remaining akonadi-related process I haven't terminated, but there's like 16 akonadi-related processes and it seems like I have to terminate every last one before I can remove my drive. FWIW, I have Desktop Search disabled, and my thumb drive automatically adds itself to the list "Do not search in these locations" when it's plugged in. Reproducible: Always Steps to Reproduce: From a fresh boot up: 0. Confirm there are no akonadi processes running. 1. Insert thumb drive containing a .eml file. [tested FS was NTFS] 2. Mount it and open dolphin. (default mount point is /media/<username>/<volume label>/ ) 3. Right-click .eml file, select Open With > KMail view. 4. Close KMail when it opens, and close Dolphin. Actual Results: There are still a plethora of akonadi-related processes running. Clicking the button "Click to safely remove this device." tells me, "Could not unmount the following device <volume label> One or more files on this device are open within an application." Expected Results: It shouldn't mess with my drive. Terminating all 16 akonadi-related processes or logging out is the only way to safely remove my USB stick. (I AM my own PIM; I hate Akonadi and have no use for it. If i can't get rid of it, it should at least stay the heck out of my way.)
Oh yeah. This should be helpful. It seems they're all retaining the folder on my thumb drive as the current working directory: $ lsof /media/owner/Portable COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME akonadi_c 5213 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadise 5215 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_a 5263 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_a 5264 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_b 5265 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_a 5266 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_f 5267 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_a 5268 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_a 5269 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_m 5270 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_m 5271 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_m 5272 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_n 5273 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_n 5274 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3 akonadi_s 5275 owner cwd DIR 8,17 4096 1382 /media/owner/Portable/stuff3
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.