Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
On 03/25/2015 10:24 AM, Michael Biebl wrote: Gordon, can you try systemd v219 from experimental? It has some tricks to suppress output from other jobs while a password prompt is running. I dunno how well that works, though so having someone with such a setup test this would be appreciated. Hi Michael, 219-5 is MUCH MUCH better. If I type the wrong password it's a bit glitchy (prints multiple prompts and starts a service to dispatch password prompts but then holds after a spurious prompt or two). I didn't wait to see if there was a hidden timeout. I got the system booted in one try which is a first. If v219 works reasonably well (without plymouth), we might consider backporting those patches (depending on how invasive they are). So far so good here. Best, -Gordon M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
Am 25.03.2015 um 17:40 schrieb Gordon Morehouse: On 03/25/2015 09:29 AM, Jonas Meurer wrote: [snip] Seems like there's some more discussion needed in order to fix the reported bug: a) do we want cryptsetup to recommend plymouth? this way at least for manual installation of cryptsetup, plymouth would be pulled in, fixing destroyed nasty boot-password-prompts introduced that were introduced by the switch to systemd. b) do we want plymouth to be installed per default on new installs? to my knowledge it's not _required_ for systemd to work, but as soon as an initscript with user interaction is invoked, apparently plymouth is required. This *is* an argument for installing plymouth by default. c) do we want any of the above to be fixed/changed in time for jessie? I'm Just A User(tm) but I really think this should be fixed in time for jessie, because it looks really, really terrible. Yes, there's a fix - if you can get your system booted, which takes me on average 3-5 tries with only two interactive password prompts. If I were a sysadmin and ran into this after installing jessie, I'd think strongly about uninstalling it and going with something else. It can't even boot right?! is the first question that came to mind after my first install of jessie - really unacceptable UX for a release soon to be marked stable and a distribution which people have relied upon for stability for well over a decade, including myself. I'll drop it after this, but I urge release maintainers to take the above into consideration and fix this in time for jessie. Thanks for all your hard work. New installation, when choosing the LVM+cryptsetup setup, will have a single cryptsetup prompt, which is run in the initramfs. So new installations are not affected, i.e, this only affects custom setups. As for upgrades, we do document this issue in the release notes [1], and when upgrading, you'll still have sysvinit around as fallback (which can be chosen from grub from the extended menu). So your system is hardly unbootable. As for adding plymouth to recommends: No matter if we add that to systemd to cryptsetup, it doesn't really solve the problem, as you'll need to add splash to the kernel command line. [1] https://www.debian.org/releases/testing/amd64/release-notes/ch-information.de.html#plymouth-required-for-boot-prompts -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
Am 25.03.2015 um 18:04 schrieb Michael Biebl: New installation, when choosing the LVM+cryptsetup setup, will have a single cryptsetup prompt, which is run in the initramfs. So new installations are not affected, i.e, this only affects custom setups. As for upgrades, we do document this issue in the release notes [1], and when upgrading, you'll still have sysvinit around as fallback (which can be chosen from grub from the extended menu). So your system is hardly unbootable. As for adding plymouth to recommends: No matter if we add that to systemd to cryptsetup, it doesn't really solve the problem, as you'll need to add splash to the kernel command line. Gordon, can you try systemd v219 from experimental? It has some tricks to suppress output from other jobs while a password prompt is running. I dunno how well that works, though so having someone with such a setup test this would be appreciated. If v219 works reasonably well (without plymouth), we might consider backporting those patches (depending on how invasive they are). Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
On 03/25/2015 09:29 AM, Jonas Meurer wrote: [snip] Seems like there's some more discussion needed in order to fix the reported bug: a) do we want cryptsetup to recommend plymouth? this way at least for manual installation of cryptsetup, plymouth would be pulled in, fixing destroyed nasty boot-password-prompts introduced that were introduced by the switch to systemd. b) do we want plymouth to be installed per default on new installs? to my knowledge it's not _required_ for systemd to work, but as soon as an initscript with user interaction is invoked, apparently plymouth is required. This *is* an argument for installing plymouth by default. c) do we want any of the above to be fixed/changed in time for jessie? I'm Just A User(tm) but I really think this should be fixed in time for jessie, because it looks really, really terrible. Yes, there's a fix - if you can get your system booted, which takes me on average 3-5 tries with only two interactive password prompts. If I were a sysadmin and ran into this after installing jessie, I'd think strongly about uninstalling it and going with something else. It can't even boot right?! is the first question that came to mind after my first install of jessie - really unacceptable UX for a release soon to be marked stable and a distribution which people have relied upon for stability for well over a decade, including myself. I'll drop it after this, but I urge release maintainers to take the above into consideration and fix this in time for jessie. Thanks for all your hard work. Best, -Gordon M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
Hello, Am 2015-03-20 16:49, schrieb Gordon Morehouse: On 03/19/2015 06:58 PM, Michael Biebl wrote: As pointed out, a recommends does not really help for new installs, since they have no effect when installing the base system. A recommends at least provides users a pointer towards fixing a really nasty problem (which they shouldn't even have, but, they currently will). Also, what Julien said. Therefor, I wonder if this bug report is useful in this form and if there's a point, keeping it open. Perhaps you could open a more appropriate bug to fix the problem for new installs? I'm not familiar enough with Debian to do so. Leaving this bug completely untouched is not a good idea. It makes Debian look cartoonishly bad when it bites. Seems like there's some more discussion needed in order to fix the reported bug: a) do we want cryptsetup to recommend plymouth? this way at least for manual installation of cryptsetup, plymouth would be pulled in, fixing destroyed nasty boot-password-prompts introduced that were introduced by the switch to systemd. b) do we want plymouth to be installed per default on new installs? to my knowledge it's not _required_ for systemd to work, but as soon as an initscript with user interaction is invoked, apparently plymouth is required. This *is* an argument for installing plymouth by default. c) do we want any of the above to be fixed/changed in time for jessie? I'm happy to implement the outcome of this discussion into the cryptsetup package, and I'm happy to prepare a quick upload with an added recommends on plymouth targeted at jessie. But at the moment I'm unsure which is the best solution, waiting for more opinions and especially for comments by the RMs ;) Cheers, jonas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
On 03/19/2015 06:58 PM, Michael Biebl wrote: As pointed out, a recommends does not really help for new installs, since they have no effect when installing the base system. A recommends at least provides users a pointer towards fixing a really nasty problem (which they shouldn't even have, but, they currently will). Also, what Julien said. Therefor, I wonder if this bug report is useful in this form and if there's a point, keeping it open. Perhaps you could open a more appropriate bug to fix the problem for new installs? I'm not familiar enough with Debian to do so. Leaving this bug completely untouched is not a good idea. It makes Debian look cartoonishly bad when it bites. Best, -Gordon M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
Am 09.03.2015 um 08:48 schrieb Julien Cristau: On Sun, Mar 8, 2015 at 12:45:28 +0100, Jonas Meurer wrote: Hi Gordon, thanks for the bugreport. I escalate this bugreport to the debian-release team, asking for advice: would you accept another cryptsetup upload targeted to jessie in order to add 'plymouth' to the list of recommended packages? Am 03.03.2015 um 03:43 schrieb Gordon Morehouse: Booting in jessie is currently nearly impossible with multiple cryptsetup volumes which are mounted at boot time. systemd spews messages over the prompt and there's a 90-second timeout while typing blind. Please see the bug report[1] and discussion on debian-qa[2]. The bug appears to be fixed by installing plymouth, so it's proposed that systemd-sysv and cryptsetup should at least recommend plymouth. I agree that plymouth should be pulled in per default on jessie installations with systemd and cryptsetup. While I don't know nothing about systemd without plymouth, when cryptsetup comes into play, plymouth is critical for the interactive password prompt at boot. Therefore I agree with the bug submitter, that cryptsetup in jessie should recommend plymouth. Does a recommend help at all, when plymouth doesn't do anything without a cmdline change? As pointed out, a recommends does not really help for new installs, since they have no effect when installing the base system. Also, what Julien said. Therefor, I wonder if this bug report is useful in this form and if there's a point, keeping it open. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
On Sun, Mar 8, 2015 at 12:45:28 +0100, Jonas Meurer wrote: Hi Gordon, thanks for the bugreport. I escalate this bugreport to the debian-release team, asking for advice: would you accept another cryptsetup upload targeted to jessie in order to add 'plymouth' to the list of recommended packages? Am 03.03.2015 um 03:43 schrieb Gordon Morehouse: Booting in jessie is currently nearly impossible with multiple cryptsetup volumes which are mounted at boot time. systemd spews messages over the prompt and there's a 90-second timeout while typing blind. Please see the bug report[1] and discussion on debian-qa[2]. The bug appears to be fixed by installing plymouth, so it's proposed that systemd-sysv and cryptsetup should at least recommend plymouth. I agree that plymouth should be pulled in per default on jessie installations with systemd and cryptsetup. While I don't know nothing about systemd without plymouth, when cryptsetup comes into play, plymouth is critical for the interactive password prompt at boot. Therefore I agree with the bug submitter, that cryptsetup in jessie should recommend plymouth. Does a recommend help at all, when plymouth doesn't do anything without a cmdline change? Cheers, Julien signature.asc Description: Digital signature
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
Hi Gordon, thanks for the bugreport. I escalate this bugreport to the debian-release team, asking for advice: would you accept another cryptsetup upload targeted to jessie in order to add 'plymouth' to the list of recommended packages? Am 03.03.2015 um 03:43 schrieb Gordon Morehouse: Booting in jessie is currently nearly impossible with multiple cryptsetup volumes which are mounted at boot time. systemd spews messages over the prompt and there's a 90-second timeout while typing blind. Please see the bug report[1] and discussion on debian-qa[2]. The bug appears to be fixed by installing plymouth, so it's proposed that systemd-sysv and cryptsetup should at least recommend plymouth. I agree that plymouth should be pulled in per default on jessie installations with systemd and cryptsetup. While I don't know nothing about systemd without plymouth, when cryptsetup comes into play, plymouth is critical for the interactive password prompt at boot. Therefore I agree with the bug submitter, that cryptsetup in jessie should recommend plymouth. I could upload cryptsetup packages with the added recommends immediately after the pre-approval of the jessie release team. Cheers, jonas PS: This mail goes directly to Niels as he suggested the recommends[3]. This is a major usability problem for users with multiple required cryptsetup volumes, e.g. on /var and /usr. I do not believe jessie should ship as stable with it unresolved. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768314 2. https://lists.debian.org/debian-qa/2015/02/msg00051.html [3] https://lists.debian.org/debian-qa/2015/02/msg00056.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
On Sun, 08 Mar 2015 12:45:28 +0100, Jonas Meurer jo...@freesources.org wrote: Hi Gordon, thanks for the bugreport. I escalate this bugreport to the debian-release team, asking for advice: would you accept another cryptsetup upload targeted to jessie in order to add 'plymouth' to the list of recommended packages? Thank you! I agree that plymouth should be pulled in per default on jessie installations with systemd and cryptsetup. While I don't know nothing about systemd without plymouth, when cryptsetup comes into play, plymouth is critical for the interactive password prompt at boot. Therefore I agree with the bug submitter, that cryptsetup in jessie should recommend plymouth. I could upload cryptsetup packages with the added recommends immediately after the pre-approval of the jessie release team. There are some differing opinions starting at about [1] on Bug#768314. I will attempt to direct them here. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768314#160 Best, -Gordon M. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
