|
Bugzilla – Full Text Bug Listing |
| Summary: | plymouth does not ask for cryptohome passphrase anymore | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Stefan Seyfried <seife> |
| Component: | Basesystem | Assignee: | Forgotten User sM9JzehKpy <forgotten_sM9JzehKpy> |
| Status: | VERIFIED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | arvidjaar, fcrozat, forgotten_sM9JzehKpy |
| Version: | 13.1 Milestone 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Third Party Developer/Partner | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
(In reply to comment #0) > > systemd-ask-password-console.service is "faster" than the plymouth password > asking service and thus always wins, so the password will be asked on the > console. > > I don't know how to fix that one :-) I am not sure where exactly the problem is. There could be multiple user agents offering to answer the same password request. All of them should wait for user input; and when one submits answer others should gracefully quit. So it is OK to have password prompt both on console and presented by plymouth. Or do you mean that systemd-ask-password-console.service blocks startup of other services, including plymouth? Exactly. It disables plymouth splash and switches to plain text console where I can then enter my password. Only if I fail to enter a wrong password on the console, then the plymouth password entry screen appears, but half-defunct (no dots for entered characters etc). So I think if plymouth is active, the priority of the password agents should be changed. Or something like that. after updating my "real" machine (laptop, not a virtual testmachine) today, everything works again as expected (got asked by graphical plymouth screen). Closing bug report as that the reporter indicated that everything works again. |
since the update to systemd > 44 and plymouth > 0.8.8, entering the passphrase does no longer work correctly. Plymouth has two problems: * systemd-tty-ask-password-agent is now in /usr/bin, but the service file has /bin configured * systemd-ask-password-plymouth.service waits for /run/plymouth/pid, but this is no longer created by plymouth-start.service I fixed those two in the following sr which I'm asking you to review and maybe accept and forward: 141258 State:new By:seife When:2012-11-14T10:11:02 submit: home:seife:branches:Base:System/plymouth -> Base:System Descr: - fix path to systemd-tty-ask-password-agent for newer systemd - create the pid file again during boot, the existence of this is a condition for systemd-ask-password-plymouth.service. A proper fix might look different but that get's it going again. Then there's another problem, this time with systemd. systemd-ask-password-console.service is "faster" than the plymouth password asking service and thus always wins, so the password will be asked on the console. I don't know how to fix that one :-)