User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Build Identifier: I installed Fedora 22 using the GUI options. I set up my partitions, with /boot being unencrypted (and /home, /, and swap being encrypted). When I booted into the newly installed machine, I saw an error (unrelated), a dot on the next line, and then the keyboard cursor. I never receive a prompt to enter my passphrase. If I modify the kernel options removing the "rhgb" argument, I get prompted for the passphrase. Removing just this option, I must enter my passphrase in three times (one for each partition), even though they have the same passphrase. If I modify the kernel options removing both the "rhgb" and "quiet" arguments, I get prompted for the passphrase. Removing both options, I only have to enter my passphrase once and all partitions unlock and mount successfully. Reproducible: Always Steps to Reproduce: 1.Boot to Fedora 22 with encrypted root 2.Wait for passphrase prompt 3. Actual Results: Nothing Expected Results: Prompted me to unlock the partitions
More information: When I boot without removing GRUB arguments, I see the following three lines: 1. [ <kernel time from boot> ] mmc0: Unknown controller version (3). You may experience problems 2. . 3. <kernel cursor> I do not believe the first displayed error is related to the reported issue. I included this information so we can rule out the first error as being part of the bug.
I found a further workaround to enable the decryption passphrase prompt. If I press "escape" after normal boot (see last comment with three lines), I get prompted for the decryption passphrase.
I found that you can enter the decryption passphrase without the prompt. Although these workarounds work consistently, this is still a bug even using the latest kernel (4.0.8) as of today.
I get identical symptoms with Lenovo Thinkpad W541 and kernel 4.1.3-201.fc22.x86_64
I am also running the Lenovo Thinkpad W541.
I think this is video driver related and the same/similar to Bug 1226106. So disabling the nouveau driver may work araound the problem.
I blacklisted nouveau via /etc/modprobe.d/ and see a graphical boot screen. Aly in Bug 1226106 describes a different initial problem, although I Nick Cross describes the same problem I see. Obviously, blacklisting nouveau is not the final solution and is still a workaround (although, it provides more information for the bug). Does this need to be fixed upstream (nouveau)?
(In reply to Clayton Casciato from comment #1) > More information: > > When I boot without removing GRUB arguments, I see the following three lines: > > 1. [ <kernel time from boot> ] mmc0: Unknown controller version (3). You may > experience problems This is bz1205070. > 2. . > 3. <kernel cursor> > > I do not believe the first displayed error is related to the reported issue. > I included this information so we can rule out the first error as being part > of the bug. I tried with the relevant modules blacklisted and no "Unknown controller" message but still see the same behavior (just a blinking cursor when the passphrase prompt should show). This is on a W541 on F23.
Just a note that, in my case at least, I don't even see the graphical grub screen, just the text based grub menu.
*** Bug 1299267 has been marked as a duplicate of this bug. ***
We get here a black screen with a cursor only in the left upper corner *after* entered the right password into graphical password prompt, for some time till cinnamon shows up. No idea if that's the same bug.
(In reply to Brad Hubbard from comment #9) > Just a note that, in my case at least, I don't even see the graphical grub > screen, just the text based grub menu. What happens if you use plymouth-set-default-theme and dracut? See bug #1304795.
(In reply to Raphael Groner from comment #12) > What happens if you use plymouth-set-default-theme and dracut? See bug > #1304795. You may definitely be onto something. $ sudo plymouth-set-default-theme -r -R The above did not completely fix the issue but it did change the behaviour substantially (I now get a strange text prompt instead of just a blank screen but still no graphical theme). Investigating this further and thanks for the tip Raphael!
So it turns out using plymouth:debug on the kernel line that plymouth was trying to use the "spinner" theme but it was not installed like the scenario in bz1304795. However, once I installed spinner and tried again I noticed that I would get the splash screen only occasionally and mostly I got just a blank screen (although not the screen with the cursor flashing in the corner). I then went into the BIOS and increased the graphics memory from 256 to 512 and now I see the theme (solar at the moment) more often than not but it is still not there 100% of the time. I'll see how this goes for now.
My case (bz1299267) recently started working again out of the blue. I could not trace it back to any particular update or change. I no longer have access to that computer.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I have done incremental upgrades from Fedora 22 > 23 and 23 > 24; my system is up-to-date. I disabled my "blacklist nouveau" in /etc/modprobe.d/ and rebooted. While connected to an external monitor through VGA, I booted an saw the (expected) graphical decryption passphrase prompt. $ lsmod | grep nouveau nouveau 1507328 1 mxm_wmi 16384 1 nouveau ttm 90112 1 nouveau i2c_algo_bit 16384 2 i915,nouveau drm_kms_helper 143360 2 i915,nouveau drm 339968 15 ttm,i915,drm_kms_helper,nouveau wmi 20480 2 mxm_wmi,nouveau video 40960 3 i915,thinkpad_acpi,nouveau As far as I can tell, this bug is resolved in Fedora 24. I'm leaving the Status as "CLOSED - EOL", as I don't know whether this was fixed in Fedora 22, 23, and/or 24; please update this if another status is applicable. Thanks!
I updated from kernel-4.6.4-301.fc24.x86_64 to kernel-4.6.5-300.fc24.x86_64. I then shut down and booted back up. I see the same results as my first post (with the same workarounds available). I have changed the Status of this bug to "NEW" and updated the version to "24".
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.