Summary: | "Unable to perform the operation (error code 9)" when there is not enough memory | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Prem Kumar <prmsrswt> |
Component: | Vaults widget | Assignee: | Ivan Čukić <ivan.cukic> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | bharadwaj.raju777, ivan.cukic, kde, nate, sephiroth_pk |
Priority: | NOR | Keywords: | usability |
Version: | 6.0.0 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Prem Kumar
2019-10-10 23:18:42 UTC
Sadly, that error code is not covered by https://github.com/cryfs/cryfs/blob/develop/src/cryfs/impl/ErrorCodes.h I'l mark this as upstream as there is not much I can do here. Can you try to mount the vault manually with cryfs ~/.local/share/plasma-vault/VaultDir ~/Vaults/VaultDir and post the output? I had this same set of symptoms (error 9, directories created) and noticed that the CryFS process was getting OOM Killed — so this error suggests you don't have much free memory on your system, and CryFS was running out of memory part way through. For me, I was roughly a gig below the system limit and it still happened. Plasma Vault maybe could benefit by showing a clearer error message in this case? I should also note that subsequent resolution of the problem (by closing down memory hogs and trying again) led to error code 20 until I changed the name of the vault, so it appears that the vault is partially created and this blocks recreation (believe I read somewhere that errcode 20 corresponds to it already being in use, but not sure). (In reply to kde from comment #2) > I had this same set of symptoms (error 9, directories created) and noticed > that the CryFS process was getting OOM Killed — so this error suggests you > don't have much free memory on your system, and CryFS was running out of > memory part way through. > > For me, I was roughly a gig below the system limit and it still happened. > > Plasma Vault maybe could benefit by showing a clearer error message in this > case? I ran into the same message while trying to open a vault. I had ~3 GiB of free RAM and I was only able to open the vault after I had ~4.5 GiB free our of 16 GiB, which is way too much for such a feature. The message should be clearer and I think it would be good to reduce the memory impact as it is way too large at the moment. I'm marking this bug as "confirmed" and changing the title. |