[Bug 506552] Re: cryptdisks_start/stop bug: bad use of sub-shell variable causes incorrect failure reports

Karmic is still supported, but "supported" doesn't imply that all bugs will be fixed. If you believe this bug warrants fixing in karmic (personally I do not, it seems to be largely cosmetic), please see . -- cryptdisks_start/stop bug: bad u

[Bug 506552] Re: cryptdisks_start/stop bug: bad use of sub-shell variable causes incorrect failure reports

What does that mean for Karmic? Karmic is no longer supported even though Lucid hasn't been released yet? -- cryptdisks_start/stop bug: bad use of sub-shell variable causes incorrect failure reports https://bugs.launchpad.net/bugs/506552 You received this bug notification because you are a membe

[Bug 506552] Re: cryptdisks_start/stop bug: bad use of sub-shell variable causes incorrect failure reports

Thank you for taking the time to report this bug and help to improve Ubuntu. The problem code is not present in the lucid version of these scripts. Marking this bug as fixed. ** Changed in: cryptsetup (Ubuntu) Status: New => Fix Released -- cryptdisks_start/stop bug: bad use of sub-shell

[Bug 506552] Re: cryptdisks_start/stop bug: bad use of sub-shell variable causes incorrect failure reports

This is a potential fix which removes the need for the sub-shell by redirecting the initial egrep output to a temporary file and then redirecting standard input from that file for the while loop. The only reservation about this is whether it is acceptable to rely upon a writeable /tmp/ at all time