SUMMARY When opening or closing a vault via the context menu you expected that the action effect is reflected into dolphin (changing the vault icon) as soon as it completed, instead nothing change until you manually refresh the folder, not providing the user any feedback about the completion of the action. STEPS TO REPRODUCE (case a) 1. Open a vault in any way 2. Go to the vault's parent folder in dolphin 3. Right click on the vault and select "Close this Plasma Vault" OBSERVED RESULT (case a) The folder doesn't refresh and so the vault folder icon remain the one of a open vault. EXPECTED RESULT (case a) Dolphin is refreshed and so the vault folder is now shown as a regular folder (as any close vault mount point is shown usually) STEPS TO REPRODUCE (case b) 1. Go to a vault's parent folder in dolphin 2. Right click on the vault and select "Open this Plasma Vault" 3. Insert the password and press "ok" OBSERVED RESULT (case b) The folder doesn't refresh and so the vault folder icon remain the one of a regular folder. EXPECTED RESULT (case b) Dolphin is refreshed and so the vault folder is now shown using the open vault icon. SOFTWARE/OS VERSIONS Linux: 5.15.2 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2
This works for me. I wonder if your system ran out of kernel filesystem watches...
(In reply to Nate Graham from comment #1) > This works for me. I wonder if your system ran out of kernel filesystem > watches... How can I check this/give you a better bug report?
What does `sysctl fs.inotify.max_user_watches` say? When it happens, what does `tail -f /var/log/dmesg` say?
(In reply to Nate Graham from comment #3) > What does `sysctl fs.inotify.max_user_watches` say? fs.inotify.max_user_watches = 16384 > When it happens, what does `tail -f /var/log/dmesg` say? Used 'dmesg -w' instead, but it didn't show anything (only messages about pam because I used sudo to run it). I also checked with KSystemLog (with all priorities enabled) but it didn't seem to show any problem: 07/12/21 19:31 cryfs Filesystem started. 07/12/21 19:31 kded5 OUT: "CryFS Version 0.11.0\n\nPassword: \nDeriving encryption key (this can take some time)...done\n\n----------------------------------------------------\nFilesystem configuration:\n----------------------------------------------------\n- Filesystem format version: 0.10\n- Created with: CryFS 0.11.0\n- Last opened with: CryFS 0.11.0\n- Cipher: xchacha20-poly1305\n- Blocksize: 16384 bytes\n- Filesystem Id: 2F8A58DA5A9A259B91AF52CED41B6973\n----------------------------------------------------\n\nMounting filesystem. To unmount, call:\n$ cryfs-unmount \"/home/user/Vaults/test\"\n\n" 07/12/21 19:31 kded5 ERR: "" 07/12/21 19:31 dolphin kf.service.services: The desktop entry file "/home/user/Vaults/test/.directory" has Type= "Application" but no Exec line 07/12/21 19:32 systemd home-user-Vaults-test.mount: Deactivated successfully. 07/12/21 19:32 cryfs Filesystem stopped. (The log has been made while opening the vault by the context menu, manually refresh dolphin and then close it by the context menu again, and the bug still appeared both when opening and closing the vault)
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 mark the bug 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!
This is working now in recent versions of Dolphin.