Description of problem: ecryptfs-mount-private and ecryptfs-umount-private both increment/decrement /dev/shm/ecryptfs-$USER-Private even if they fail Version-Release number of selected component (if applicable): ecryptfs-utils-111-2.fc25.x86_64 How reproducible: When ecryptfs-mount-private fails because passphrase signature is not on root's keyring (see bug #1480793) Steps to Reproduce: 1. try to mount ~/.Private if mount passphrase is not on root's keyring 2. 3. Actual results: mount operation fails, and /dev/shm/ecryptfs-$USER-Private is incremented Expected results: Since the operation failed, /dev/shm/ecryptfs-$USER-Private should not be incremented. Now, trying to umount ~/.Private gives an error: ~ ecryptfs-umount-private Sessions still open, not unmounting Additional info: The error is cumulative: the more I run ecryptfs-mount-private, the more the counter is incremented. On the other hand, ecryptfs-umount-private also decrements the counter even if it fails: ~ ecryptfs-mount-private Enter your login passphrase: Inserted auth tok with sig [XXX] into the user session keyring mount: No such file or directory ~ cat /dev/shm/ecryptfs-costa-Private 1 ~ ecryptfs-mount-private Enter your login passphrase: Inserted auth tok with sig [XXX] into the user session keyring mount: No such file or directory ~ cat /dev/shm/ecryptfs-costa-Private 3 ~ ecryptfs-umount-private Sessions still open, not unmounting ~ cat /dev/shm/ecryptfs-costa-Private 2 ~ ecryptfs-umount-private Sessions still open, not unmounting ~ cat /dev/shm/ecryptfs-costa-Private 1 ~ ecryptfs-umount-private ~ cat /dev/shm/ecryptfs-costa-Private 0 ~ ecryptfs-umount-private ~ cat /dev/shm/ecryptfs-costa-Private 0
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.