Description of problem: Updated my machine from koji (I realize the rawhide compose with this version hasn't happened yet). This did get the updated initscripts and plymouth. After a reboot, booting stops when plymouth is done. Can't use ctrl-alt-f2 to get to a console. Rebooting at runlevel 3 and doing a startx works. Rebooting at runlevel 3 and doing a telinit 5 works. Version-Release number of selected component (if applicable): upstart-0.6.3-3.fc13.x86_64 initscripts-9.03-1.x86_64 plymouth-0.8.0-0.2009129.fc13.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Works for me if I hit "ESC" at the initial plymouth screen. I watch the text reports of the services starting (with "OK" at the end of each line), and then get X/gdm screen. Does not work (as reported in #1) if I allow plymouth screen to run uniterrupted.
Did you try to downgrade initscripts and check if all works again. Maybe that's not a initscripts problem. Thanks your report and waiting for news. -- Fedora Bugzappers Team Member
Is it only the details plugin that works? Have you tried disabling modesetting?
nomodeset works
OK, assigning to plymouth.
Seems to be working for me now (without 'nomodeset'), but no changes to initscipts, plymouth or upstart. Booting now goes to gdm login screen/etc. without entering ESC at plymouth screen. Not sure what has changed.....
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Well I have the same error with Plymouth and KDM. I can boot fine without the rhgb quite line and it works well, otherwise I am just stuck at the fedora logo at the end of the plymouth theme.
Same problem here using GDM. Disabling rhgb or pressing ESC while plymouth shows up helps. Smoltprofile: http://www.smolts.org/show?uuid=pub_748daccf-258a-4ace-ac61-39957a414148+ I am using Fedora13
Lothar what version of plymouth and gdm do you have installed?
Created attachment 406599 [details] :0-slave.log logfile
Created attachment 406600 [details] :0-slave.log logfile when GDM does not start
I can duplicate this issue. GDM does not start unless I press ESC during plymouth. I added the :0-slave files (bugzilla wanted to add the files separately, sorry) for the cases with and without pressing ESC. plymouth-0.8.1-3.fc13.i686 gdm-2.29.92-5.fc13.i686 When GDM does not display, ps only has Xorg running under gdm-simple-slave: /usr/bin/Xorg :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-li7M6f/database -nolisten tcp
you need gdm-2.29.92-6 or later
those hitting this issue recently are seeing bug #577789 . It was identified and fixed but due to insufficient safeguards in Koji, an older gdm package got into the repos recently, so the problem has come back. This should be fixed tomorrow. Leaving this report open as it pre-dates that bug, so the original reporter here has a different (and more user-specific) issue. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I am using gdm-2.29.92-5. I am not able to test 2.29.92-6 because I am using a live image. As far as a updated live image is available I will continue testing.
Just making a note that I'm seeing this with the Intel Test Day gfx_test_week_20100414_i686.iso spin on this hardware: http://www.smolts.org/client/show/pub_528c8204-8c24-426f-8785-50d76ead6232
that's definitely not 577789. hard to know if it's the same bug as the OP here, though. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This appears to be fixed, now. At least it works for me.
This seems to be fixed for me in desktop-i386-20100418.17.iso
darrell, are you around? Any update from you? Thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I've held off because I've moved on to a different version. I'm a koji junkie (well past being a rawhide junkie) In the current rawhide/koji, the problem is fixed for me.
are you using the fc13 or fc14 stuff from koji? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I'm totally fc14.
This seems to be fixed for me in desktop-i386-20100418.17.iso (gdm-2.29.92-6), too
well, let's split the difference and close the bug, since no-one seems to be having trouble any more; it's possible Darrell's situation is broken in f13, but we can't really check that. Darrell, if you do get to testing f13 and find the bug is still there, please re-open or file a new bug. Thanks. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers