[Bug 997200] New: luks decryption screen fails to show up on boot frequently
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=997200 Bug ID: 997200 Summary: luks decryption screen fails to show up on boot frequently Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: email@chanjp.me QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 690797 --> http://bugzilla.opensuse.org/attachment.cgi?id=690797&action=edit Output from journalctl --boot=-1 for most recent boot failure On occasion, the graphical page (presumably running Plymouth) for typing in my lvm-luks passphrase fails to appear on bootup, and a terminal interface pops up instead. Since the past few snapshots, the situation has deteriorated and sometimes no passphrases can be entered, and the computer hangs on bootup. I can only log into Tumbleweed after rebooting the computer several times. I have attached the journalctl output for the last known failure to boot with journalctl --boot=-1 -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=997200 http://bugzilla.opensuse.org/show_bug.cgi?id=997200#c1 --- Comment #1 from Ju_Ping Chan <email@chanjp.me> --- Created attachment 690798 --> http://bugzilla.opensuse.org/attachment.cgi?id=690798&action=edit Example of successful boot log from journalctl I am adding this additional log from the successful boot up in case it helps. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=997200 http://bugzilla.opensuse.org/show_bug.cgi?id=997200#c2 A.H.M. Donkers <contact@maridonkers.info> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |contact@maridonkers.info --- Comment #2 from A.H.M. Donkers <contact@maridonkers.info> --- On my two monitor system (laptop with external monitor) the luks decryption window doesn't appear. When I disconnect the external monitor and reboot it does show. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=997200 http://bugzilla.opensuse.org/show_bug.cgi?id=997200#c3 --- Comment #3 from Ju_Ping Chan <email@chanjp.me> --- I just keep rebooting until the decryption screen reappears, because it should not be an inherent problem with the display itself, as the following error messages are displayed while the system hangs. EDAC sbridge: ECC is disabled. Aborting EDAC sbridge: Couldn't find mci handler EDAC sbridge: Failed to register device with error -19. Furthermore, I have an Ubuntu partition on the same system which loads without issue. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=997200 http://bugzilla.opensuse.org/show_bug.cgi?id=997200#c4 --- Comment #4 from Ju_Ping Chan <email@chanjp.me> --- Created attachment 703685 --> http://bugzilla.opensuse.org/attachment.cgi?id=703685&action=edit New failure log from kernel 4.8 I am adding another boot failure output because the problem appears to have gotten worse with the latest updates. I rebooted 12 times to no avail before booting into the previous kernel. Is there a way to not load the GUI for the luks unlocking mechanism, so I can type it into the cli instead? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=997200 Ismail Donmez <idonmez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sreeves@suse.com Assignee|idonmez@suse.com |qzhao@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=997200 http://bugzilla.opensuse.org/show_bug.cgi?id=997200#c5 --- Comment #5 from Ju_Ping Chan <email@chanjp.me> --- Latest update seems to have forced installed plymouth after I installed it, and it seems to be working fine on my desktop. Unfortunately, the plymouth instance running on my laptop is now experiencing this problem of not providing an option to unlock. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=997200 Jeroen Mathon <jeroenmathonmac@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeroenmathonmac@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=997200 http://bugzilla.opensuse.org/show_bug.cgi?id=997200#c6 --- Comment #6 from Ju_Ping Chan <email@chanjp.me> --- Potentially related to https://bugzilla.novell.com/show_bug.cgi?id=1020283 -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=997200 http://bugzilla.opensuse.org/show_bug.cgi?id=997200#c7 Ju_Ping Chan <email@chanjp.me> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Ju_Ping Chan <email@chanjp.me> --- This appears to be a duplicate of a bug that is more clearly identified and has more activity. *** This bug has been marked as a duplicate of bug 1020283 *** -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com