plymouth splash screen doesn't close with slim

Bug #774644 reported by shachafgo
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Triaged
Medium
Unassigned
slim (Ubuntu)
Triaged
High
Unassigned

Bug Description

Binary package hint: plymouth

Since i started using slim as my login screen manager plymouth splash screen stays on until i manually kill plymouthd process

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu22
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: wl fglrx
Architecture: amd64
Date: Sun May 1 08:34:51 2011
DefaultPlymouth: /lib/plymouth/themes/solar/solar.plymouth
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: SAMSUNG ELECTRONICS CO., LTD. R540/R580/R780/SA41/E452/E852
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=3f2a27cf-43f5-4579-b0dd-79690dabd1a3 ro splash vga=786 splash
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UdevDb: Error: [Errno 2] No such file or directory
UpgradeStatus: Upgraded to natty on 2011-04-26 (4 days ago)
dmi.bios.date: 09/27/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 03KP.M008.20100927.LDG
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: R540/R580/R780/SA41/E452/E852
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 03KP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr03KP.M008.20100927.LDG:bd09/27/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR540/R580/R780/SA41/E452/E852:pvr03KP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR540/R580/R780/SA41/E452/E852:rvr03KP:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: R540/R580/R780/SA41/E452/E852
dmi.product.version: 03KP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
shachafgo (shachaf-gold) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

See bug #609163 for discussion of the correct way to fix this.

Changed in plymouth (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
shachafgo (shachaf-gold) wrote :

i have a plymouth version 0.8.2-2ubuntu22 while the one mentioned as fixed there is 0.8.2-2ubuntu7 so maybe there is a slight regression?

i switched back to gdm and it's gone now but i still think it's worth fixing

Revision history for this message
onli (onli) wrote :

What about people using no display-manager at all? playmouth should recognise that the booting process is over, maybe exit on the start of X?

Revision history for this message
Att Righ (attrigh) wrote :

This bug is a little worse that it may seem. If you use slim to launch unity then it subtly breaks compiz so that opengl doesn't work properly and all operations and slow - further you will only notice this once you reboot your machine after setting up slim because plymouth has already been killed.

I'm not sure how common the use case of wanting to replace lightdm / gdm but keep unity on a ubuntu box is, but I'd imagine it might common enough to merit this bug being pushed.

Revision history for this message
Att Righ (attrigh) wrote :

* pushed -> given a slightly higher priority.

Revision history for this message
Steve Langasek (vorlon) wrote :

This bug remains unfixed because the slim package in Ubuntu does not have an upstart job, giving us no way to specify the handling of plymouth in the presence of slim. Someone who cares about the slim package in Ubuntu should address this first, then we can update the plymouth package to match.

Or, users can continue to use the DM that's installed by default, which has been made to integrate with plymouth.

Changed in slim (Ubuntu):
status: New → Triaged
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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