Description of problem: When creating an encrypted filesystem as a file with cryptmount, the loopback kernel module ("loop") isn't loaded by default resulting in following error: [root@hal9000 ~]$ cryptmount-setup ... Enter password for target "mystuff": No available loopback devices Cannot open device "/home/nick/mnt/mystuff.fs" for target "mystuff" Version-Release number of selected component (if applicable): 4.3.3 How reproducible: Always Steps to Reproduce: 1. Install cryptmount 2. Run cryptmount-setup --> Error Reproducible: Steps to Reproduce:
Workaround: - short term: run 'modprobe loop' as root - long term: run 'echo loop >> /etc/modules' as root
Solution (?): Installing the package adds the "loop" entry to /etc/modules
Bug 9657 reports the same issue for TrueCrypt but it is closed as being invalid because TrueCrypt isn't provided by Mageia. Cryptmount, however, is.
Keywords: (none) => TriagedCC: (none) => tmbAssignee: bugsquad => guillomovitch
Loop device is a system facility that exists independent of any particular package, and which provides block device access to a file. Closing a bug related to it not being started is inappropriate; it should be started automatically at boot time, probably in the initrd though adding loop to /etc/modules works fine.
CC: (none) => jiml
It doesn't make much sense to force permanent loading of 'loop' module just because you install a package than may eventually need it. That's more an upstream issue for me, as cryptmount-setup usage should trigger relevant module loading dynamically if needed.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 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 Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
The bug still exists in Mageia 4 with cryptmount 4.4.1.
Status: RESOLVED => REOPENEDVersion: 3 => 4Resolution: OLD => (none)Source RPM: cryptmount-4.3-3.mga3.src.rpm => cryptmount-4.4.1-1.mga4.src.rpm
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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 Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: REOPENED => RESOLVEDResolution: (none) => OLD