Written "press return to shutdown the computer" does not appear.

Bug #1865161 reported by tofono
52
This bug affects 11 people
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Invalid
Critical
Unassigned
Focal
Invalid
Critical
Unassigned
plymouth (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned

Bug Description

Written "press return to shutdown the computer" does not appear.
When exiting the Ubuntu LIVE focal fossa, the message "press return to shutdown the computer" does not appear on the computer. This occurs from the version of 02.27.2020 iso. The computer stays on with the black screen. Sometimes pressing the button, in any case it turns off but without writing the user is forced to turn off the power.
Wouldn't it be the case, without further user intervention, that once the command is sent, the operating system turns off the computer directly?
Please check and resolve, thank you.

Tags: champagne
tofono (tofono)
description: updated
description: updated
Steve Langasek (vorlon)
affects: livecd-rootfs (Ubuntu) → casper (Ubuntu)
tags: added: rls-ff-incoming
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in casper (Ubuntu):
status: New → Confirmed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Confirmed on Ubuntu Desktop 20200303

Changed in casper (Ubuntu):
importance: Undecided → Critical
tags: added: champagne
tags: removed: rls-ff-incoming
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Potentially, casper hooks need adjusting to ensure all assets of the the new plymouth theme are cached for successful display of the RIM-and-reboot message.

Also need checking if the message is shown on tty63, and we just didn't switch to it.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

debugging tips, boot with systemd.debug-shell=1 to have a tty9 root shell that persists into the shutdown.

increase plymouth debugging & ensure it logs to a log in /run

observe it or kernel failing to access any files

most likely we need to add more files to fs cache which are used by the theme.

Revision history for this message
Sebastien Bacher (seb128) wrote :

I've tried the debugging tip but without luck, no error written to the journal...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The next thing to try (whoever has time first) will be to try just sending plymouth messages from tty9 to that that final screen. If those messages appear then the problem here may be just that casper-stop is running too soon, before plymouthd is ready to accept messages. Or plymouthd starting too late.

Certainly there's a suspicious delay and blank screen with just a cursor between the installer finishing and the final plymouth screen absent of messages.

Revision history for this message
hugh chao (hugh712) wrote :

I tried to add systemd.debug-shell=1, and switched to tty9 when the installation was done and switched back to tty1, then the message "Please remove the installation medium,then reboot" shown up.

Next step, I tried to send message via "plymouth message --text= ", but the messages didn't be updated.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

You will need to switch to a different VT where hopefully the graphical plymouthd screen is still running. If you can't find such a VT then run 'ps' to see if plymouthd is still running at all. If plymouthd has crashed, exited (without clearing the screen) or frozen then that would explain the bug.

Revision history for this message
hugh chao (hugh712) wrote :

plymouthd is in interruptible sleep state as:

@sbin/plymouthd --mode=reboot --attach-to-session

Revision history for this message
hugh chao (hugh712) wrote :

upload casper-stop log

Revision history for this message
hugh chao (hugh712) wrote :

seems after the installation, still can't use "plymouth dispaly-message" to send the text in desktop environment, maybe we can just debug in desktop enviroment...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It sounds like Seb might have a fix coming (in proposed):
https://launchpad.net/ubuntu/+source/plymouth/0.9.4git20200323-0ubuntu3

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Installing plymouth-label in a live session appears to fix the bug. So I am going to assume the above version has fixed it. No live ISO available includes it yet though.

Changed in plymouth (Ubuntu Focal):
status: New → Fix Released
Changed in casper (Ubuntu Focal):
status: Confirmed → Invalid
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Verified fixed in http://cdimage.ubuntu.com/daily-live/20200331/ though it's dated 20200401.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.