| Summary: | plymouth does not release active terminal | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paolo Bonzini <pbonzini> |
| Component: | plymouth | Assignee: | Ray Strode [halfline] <rstrode> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | ajax, fedora, mcepl, petter, rstrode, xgl-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-07 18:20:24 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Booting with graphical boot, and pressing Esc mid-boot to bail to text screen, also works. (In reply to comment #1) > Booting with graphical boot, and pressing Esc mid-boot to bail to text screen, > also works. OK, so this is problem just in plymouth? I.e., when you remove "rhgb quiet" from the kernel command line, everything works correctly and you get gdm login (or X via startx if you are one of those)? Yes, I get gdm login. I think if I used startx there wouldn't be a problem because plymouth would relinquish control of the display to let me see the login prompt. So it might be plymouth indeed. Here is where the X server is stuck:
63 switch_to(int vt, const char *from)
64 {
65 if (ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt) < 0)
66 FatalError("%s: VT_ACTIVATE failed: %s\n", from, strerror(errno));
67
68 if (ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt) < 0)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
69 FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
70 }
Changing component to plymouth.
Version of plymouth installed (and "dracut -f" done):
plymouth-0.8.4-0.20110330.1.fc15.x86_64
Any updates on this? The bug is still alive and kicking: At least I think it is the same one: If I run a graphical boot process, I get a nice graphical interface until gdm is supposed to start, at which point I get a black screen and a waiting cursor; if I exit the graphical boot interface (Plymouth?), gdm starts normally and properly. Let me know if any debug info I can provide would be any use. This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
Description of problem: Booting with graphical boot I get a black screen. Booting with text boot works. Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.14.0-5.fc15.x86_64 xorg-x11-server-Xorg-1.10.1-13.fc15.x86_64 xorg-x11-server-common-1.10.1-13.fc15.x86_64 libdrm-2.4.25-3.fc16.x86_64 How reproducible: 100% on this machine /var/log/Xorg.1.log ends at: [ 40.350] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge [ 40.351] (--) using VT number 7 The next line (from the Xorg.1.log file without rhgb---up to this point the files are perfectly identical except for timestamps!) should have been [ 40.357] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so Additional info: libdrm-2.4.25-1.fc15.x86_64 to libdrm-2.4.25-3.fc16.x86_64 should only be packaging changes. I'm not sure where the bug is (server or drivers). I'll try getting a backtrace of Xorg.