Bug 17530 - 6_s1: plymouth-reboot is delaying reboots
Summary: 6_s1: plymouth-reboot is delaying reboots
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-18 23:27 CET by Bit Twister
Modified: 2017-01-24 09:42 CET (History)
1 user (show)

See Also:
Source RPM: plymouth-0.9.2-3.mga6.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2016-01-18 23:27:31 CET 
Description of problem:
plymouth-reboot is delaying reboots.

Screen is showing:
Failed to start Show Plymouth Reboot Screen
See systemctl status service plymoth-reboot


$ journalctl | grep plymouth  snippet
Jan 18 13:15:48 tb.home.test 
  plymouth[24882]: error: unexpectedly disconnected from boot status daemon
 systemd[1]: plymouth-reboot.service: Main process exited, code=killed, status=11/SEGV
 systemd[1]: plymouth-reboot.service: Unit entered failed state.
 systemd[1]: plymouth-reboot.service: Failed with result 'signal'.


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


How reproducible: Always


Steps to Reproduce:
1. add "audit=0" and remove "splash=whatever" and "quiet" from /boot/grub/menu.lst kernel line and reboot.
2. reboot and watch shutdown messages



Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2016-02-06 17:44:32 CET 
There's no maintainer for plymouth, so assigning to all packagers collectively.

CC: (none) => marja11
Assignee: bugsquad => pkg-bugs

Comment 2 Bit Twister 2016-07-06 20:03:09 CEST 
reboot can be caused with removal of splash on kernel boot line.

Summary: mga6: plymouth-reboot is delaying reboots => 6_s1: plymouth-reboot is delaying reboots

Comment 3 Bit Twister 2017-01-24 09:42:22 CET 
problem no longer exists.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.