Bug 388400 - kactivitymanagerd does not allow unmounting external hard drive
Summary: kactivitymanagerd does not allow unmounting external hard drive
Status: RESOLVED WORKSFORME
Alias: None
Product: kactivitymanagerd
Classification: Plasma
Component: general (show other bugs)
Version: 5.11.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Ivan Čukić
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-12-31 15:17 UTC by Amitav
Modified: 2018-11-01 18:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Amitav 2017-12-31 15:17:36 UTC
I mounted a drive using Dolphin. After some usage, I tried unmounting by clicking "Safely remove" option. However, I got an error about device being busy.

[root@clown user]# fuser -vm /run/media/dknight/New\ Volume/
                     USER        PID ACCESS COMMAND
/run/media/user/New Volume:
                     user     612 ..c.. kactivitymanage

When I dug further, I saw kactivitymanagerd being the culprit. After stopping the daemon, unmounting was successful.
Comment 1 Ivan Čukić 2018-03-07 22:36:51 UTC
Do you have a custom activity-related setup? Automatic script execution when activities change ...?
Comment 2 Christoph Feck 2018-03-29 20:55:46 UTC
If you can provide the information requested in comment #1, please add it.
Comment 3 Amitav 2018-03-30 16:10:19 UTC
No, I do not have any such script enabled.
Comment 4 Ivan Čukić 2018-07-23 15:19:28 UTC
Can you check which file is open (with lsof)?
Comment 5 Andrew Crouthamel 2018-09-28 03:11:38 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Amitav 2018-10-02 12:40:06 UTC
First of all, the bug was reported months back. If the first response I get is after 3 months of reporting, I am not sure if it is fair that you set a deadline for me. Perhaps, allowing a few months for my response would be fine.

Secondly, I have already provided the process that was the culprit and I would like to understand why that process was interfering.

I will try to check with lsof which file is being accessed next time I hit this.
Comment 7 Andrew Crouthamel 2018-11-01 18:48:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!