Bug 18999

Summary:	6_s1: plymouth-start.service: Main process exited, code=killed, status=11/SEGV
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, rverschelde
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	plymouth-0.9.2-4.mga6.src.rpm	CVE:
Status comment:

Description Bit Twister 2016-07-20 16:20:28 CEST

Description of problem:

]$ journalctl -b | grep plymouth
 dracut: Starting plymouth daemon
 systemd[1]: Starting Show Plymouth Boot Screen...
 plymouth[560]: error: unexpectedly disconnected from boot status daemon
 systemd[1]: plymouth-start.service: Main process exited, code=killed, status=11/SEGV
 systemd[1]: Failed to start Show Plymouth Boot Screen.
 systemd[1]: plymouth-start.service: Unit entered failed state.
 systemd[1]: plymouth-start.service: Failed with result 'signal'.
 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
 systemd[1]: Started Tell Plymouth To Write Out Runtime Data.


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


How reproducible: Always


Steps to Reproduce:
1. reboot
2. journalctl -b | grep plymouth
3.

Comment 1 Marja Van Waes 2016-07-20 18:33:29 CEST

Can't reproduce in my cauldron that was last updated yesterday.

However, I did not try in a cauldron that was started from 6RC

CC: (none) => marja11, rverschelde

Comment 2 Bit Twister 2016-07-20 20:41:51 CEST

Problem showed up with the new xorg and kernel update.
Noticed a new kernel in the build system.
system was a clean network install around the first of the month + updates.

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-desktop root=LABEL=cauldron noiswmd nokmsboot vga=794 ipv6.disable=1 audit=0

Comment 3 Bit Twister 2016-07-20 20:48:04 CEST

(In reply to Marja van Waes from comment #1)
> Can't reproduce in my cauldron that was last updated yesterday.
> 
> However, I did not try in a cauldron that was started from 6RC

Just checked and my test bed node and it does not have the problem.
I have opened a kernel bug report that also does not happen on my test bed node.
Maybe the clear up on next kernel update.

Comment 4 Bit Twister 2016-07-24 03:57:42 CEST

newest plymouth rpm must have fixed the problem.

Status: NEW => RESOLVED
Resolution: (none) => FIXED