SUMMARY I have a vault with my work repositories. I mount my vault, and when I am going to commit or to perform any command on the folder, it gets lazy until it freezes. Umounting via cli needs to be forced, and then when I try to mount the folder again, it says that my credentials are wrong, and I need to reboot my pc to get the vault to work again. STEPS TO REPRODUCE 1. Mount Vault 2. Try to perform any command inside the folder 3. It freezes OBSERVED RESULT Vault freezes and dont allow you to perform anything on it. EXPECTED RESULT Vault works properly SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon Testing Edition (available in About System) KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Version of vault: plasma-vault/bionic,now 5.16.2+p18.04+git20190625.1500-0 amd64
By any chance, is it that Dolphin is using up 100% CPU while the vault is open, and that's the cause of the UI freeze?
I don't see dolphin using 100% of CPU, but when I try to access the mounted folder on terminal and on dolphin, both freezes.
cryfs vault? If so, I've also noticed that - no idea what is the cause. What happens if you call cryfs manually and mount.
If you can provide the information requested in comment #3, please add it.
(In reply to Ivan Čukić from comment #3) > cryfs vault? yes, on the mount shows fuse.cryfs Version: plasma-vault/bionic,now 5.16.4+p18.04+git20190730.1328-0 Will test tomorrow if it had any changes since the reported version on the behavior.
Please also test by manually mounting from shell. This should be an upstream issue.
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 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!