Ubuntu
plymouth package

No smooth transition out of X on shutdown

Bug #540816 reported by unggnu on 2010-03-18

124

This bug affects 25 people

Affects		Status	Importance	Assigned to	Milestone
	plymouth (Ubuntu)	Triaged	Wishlist	Unassigned

Bug Description

Binary package hint: plymouth

This isn't serious but annoying. If you use the shutdown function in X it closes and you see the console with all the usual text and error messages which looks like something has crashed. After one second or something like that Plymouth kicks in and shows the usual boot/shutdown screen.

Isn't it possible to let X directly change to Plymouth on shutdown (at least with KMS)? It would look much more coherent and professional.

As soon as this and Bug #535108 is fixed Ubuntu would look really coherent, professional and great and a normal user would never see "annoying" console messages. This is what the whole boot experience blueprint is about I think.

ProblemType: Bug
Architecture: i386
Date: Thu Mar 18 11:17:49 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100315)
MachineType: MSI MS-6702
Package: plymouth 0.8.0~-17
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=3c0dcd65-8c85-4908-a73e-7ec4b9a04f74 ro quiet splash
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB:
0 radeondrmfb
1 VGA16 VGA
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SourcePackage: plymouth
Uname: Linux 2.6.32-16-generic i686
dmi.bios.date: 04/02/01
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Version 07.00T
dmi.board.name: MS-6702
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: Uknown Chassis Manufacture
dmi.chassis.version: Version 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrVersion07.00T:bd04/02/01:svnMSI:pnMS-6702:pvr1.0:rvnMSI:rnMS-6702:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00:
dmi.product.name: MS-6702
dmi.product.version: 1.0
dmi.sys.vendor: MSI

Tags:

Revision history for this message

unggnu (unggnu) wrote on 2010-03-18:

#1

BootDmesg.txt Edit (37.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (14.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (458 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (570 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.9 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (90.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (200.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Steve Langasek (vorlon) wrote on 2010-03-18:

#2

Sorry, we have to let the X server stop first before plymouth is started, so there's always going to be a gap here when we've dropped out to text mode on shutdown. I don't know any way to transition directly from X to plymouth on shutdown, and I think if Scott knew one it would already be implemented.

Changed in plymouth (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

unggnu (unggnu) wrote on 2010-03-18:

#3

Thanks for the info. I just thought since the change from Plymouth to X is directly possible in Lucid the opposite would be too. Maybe Plymouth can run the whole time on one console or it is possible to change to a black screen from X but like I said it is not so important.
With installed cryptsetup/fixed Bug #535108 it just would look so great. :)

Revision history for this message

Steve Langasek (vorlon) wrote on 2010-03-18:

#4

The difference is that plymouth is written to let other programs tell it that they're taking over the display and to exit leaving a splash screen up, but the X server is not. (Not to mention the extra layer of management, the display manager, that's in charge of the X server.)

Revision history for this message

Scott James Remnant (Canonical) (canonical-scott) wrote on 2010-03-18:

#5

Running Plymouth on a different console would not allow for a seamless transition; there would be a black screen of a VT switch between Plymouth and X - and the startup situation would be worse since X would not be able to inherit the screen contents.

As Steve says, in order to provide a smooth transition *out* of X, we need the X server to co-operate in the same way that Plymouth does on the way in

This may never happen; at least not before we change display servers and stop using X!

Changed in plymouth (Ubuntu):
status:	New → Triaged
importance:	Medium → Wishlist
summary:	- Plymouth isn't shown directly after using shutdown in X so it looks like - a crash + No smooth transition out of X on shutdown

Revision history for this message

davidetkarine (saveurlinux) wrote on 2010-03-28:

#6

I've got Thinkpad lenovo R61 with nvidia nvs 140 card:

When closing session I've got this message:
- avahi-deamon main process terminated with status 255
and
- usplash terminated with status 2When closing session I've got this message:
- avahi-deamon main process terminated with status 255
and
- usplash terminated with status 2

Revision history for this message

Timo Jyrinki (timo-jyrinki) wrote on 2012-04-19:

#7

Just to mention, bug #967229 (I marked it as duplicate now) has a short video of showing what is meant by this bug.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #960533

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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