Bug 1205610 - "A start job is running for Wait for Plymouth Boot Screen to Quit" when trying to use another TTY
Summary: "A start job is running for Wait for Plymouth Boot Screen to Quit" when tryin...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 22
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-25 10:27 UTC by Gwendal
Modified: 2015-12-28 18:29 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-03-27 08:51:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Photo taken after switching to other TTY (831.02 KB, image/jpeg)
2015-03-25 10:27 UTC, Gwendal
no flags Details

Description Gwendal 2015-03-25 10:27:54 UTC
Created attachment 1006267 [details]
Photo taken after switching to other TTY

Description of problem:

I cannot access another TTY (CTRL+ALT+F3), since it only shows me the message "A start job is running for Wait for Plymouth Boot Screen to Quit"

Version-Release number of selected component (if applicable): 22 alpha


How reproducible:
Always

Steps to Reproduce:
1. Start the computer
2. Before or after using the graphical gnome login screen, press CTRL+ALT+F3

Actual results:

There is this message and nothing else : "A start job is running for Wait for Plymouth Boot Screen to Quit", along with a time counter "[time] / no limit". See attached photo.

Expected results:

To be able to login using the textual login screen.

Comment 1 Gwendal 2015-03-26 11:49:18 UTC
Update - Here is what I've tried:

[xxx@yyy ~]$ ps -e |grep ply
  315 ?        00:00:07 plymouthd
  941 ?        00:00:00 plymouth
[xxx@yyy ~]$ sudo pkill plymouth
[sudo] password for xxx: 
[xxx@yyy ~]$ ps -e |grep ply

And after that I can access a terminal by pressing CTRL+ALT+F3

Comment 2 Ray Strode [halfline] 2015-03-26 19:35:46 UTC
this is fixed in gdm-2.16.0.1

Comment 3 Gwendal 2015-03-27 08:51:28 UTC
Fixed indeed with today's update. Thanks.

I've put closed resolved as "current release", but I'm now sure about which one to pick...

Comment 4 Jeremy Huddleston 2015-08-26 04:28:08 UTC
This reproduces for me when booting off of either:
Fedora-Live-Workstation-x86_64-23_Alpha-2.iso
Fedora-Live-Workstation-x86_64-22-3.iso

I don't think it is fixed (or it has regressed).


Note You need to log in before you can comment on or make changes to this bug.