What’s happened to the graphical prompt for the passphrase for the encrypted FS during boot in openSUSE 13.1?
I’ve just tried setting up a VM with 13.1 configuring an encrypted LVM as offered but on booting I’m back to the old text console requesting the passphrase in amongst all the other info scrolling up the screen. Whilst I’m Ok with that it’s a real put-off for ordinary users like SWMBO. We’ve had a reasonably nice clean graphical prompt for the pasphrase since 12.1 (IIRC) and I was expecting it to get better not go away.
I tried installing 13.1 on the VM as an upgrade from an existing 12.3 and lost the graphical prompt so I did a fresh install and still didn’t get the graphical prompt.
There’s no way I can upgrade my wife’s netbook with this and I’m the one insisting she uses openSUSE with the encrypted FS in case she leaves it on a bus.
Have I done something wrong or it is supposed to be this sort of mess?
I didn’t see a specific bug report on on bugzilla for the lack of the gui prompt so I’ve put one in for it (#851767).
I did some investigation of my own some time back to try and find a way of getting a more user-friendly prompt for the passphrase at boot to discover it was part of the kernel internals and way out of my comfort zone although reports said that it was being investigated so I was really pleased when it appeared in openSUSE (I think it was in 12.1).
With gui prompt I felt much happier at putting openSUSE on my wife’s netbook and our shared laptop neither of which I wanted left without encryption.
How did a show-stopper like this get past testing? Surely I can’t be the only one about with an encrypted laptop - especially with so many people paranoid about security. Ok - so I should have checked out a RC and reported the problem earlier but 13.1 is the first release in a good while when I’ve just not had the time to do so.
> How did a show-stopper like this get past testing?
As said, it is a known issue. I knew about it, for instance, even though
I did not detect it. I tested encryption, but I intentionally remove the
graphical boot program, plymouth, so it did not hit me.
The issue was not classified as release stopper.
> Surely I can’t be the
> only one about with an encrypted laptop - especially with so many people
> paranoid about security. Ok - so I should have checked out a RC and
> reported the problem earlier but 13.1 is the first release in a good
> while when I’ve just not had the time to do so.
You should subscribe to the factory mail list (or use gmame gateway).
Many of the issues are commented there in advance, and devs read it.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
If I were to make an uneducated guess, they have a list of things that are important during the final polishing and then you have a list of bugs you simply don’t have the time to fix in time or don’t crop up with every possible combination of software or hardware, in this case perhaps they didn’t know about it properly (or weren’t given enough information on how to reproduce the issue).
