Bug 13557 - Failed to start Wait for Plymouth Boot Screen after update
Summary: Failed to start Wait for Plymouth Boot Screen after update
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: http://blogdrake.net/consulta/problem...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-20 20:41 CEST by Joaquim Bernà i Torres
Modified: 2015-10-27 06:58 CET (History)
1 user (show)

See Also:
Source RPM: kernel 3.12.21-server-2mga4
CVE:
Status comment:


Attachments

Description Joaquim Bernà i Torres 2014-06-20 20:41:43 CEST
Description of problem:
After updating kernel and reboot normally system cannot get the login screen showing an error and asking to get more data in systemctl status on plymouth-quit-wait.service

Version-Release number of selected component (if applicable):
kernel 3.12.21-server-2mga4

How reproducible:
It stucks also with older kernel versions from grub

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Joaquim Bernà i Torres 2014-06-20 20:59:45 CEST
It works with previous kernel 3.12.20-server-1.mga4 

I've tried others from grub but it didn't.
Comment 2 Joaquim Bernà i Torres 2014-06-22 20:46:49 CEST
Solved!

just did:

#urpme nvidia-current-kernel-3.12.21-server-2.mga4

And then: 

#urpmi nvidia-current-kernel-3.12.21-server-2.mga4

#reboot

#uname -r
#3.12.21-server-2.mga4
Comment 3 Mészáros Csaba 2015-06-25 12:03:01 CEST
Currently, I also have this sort of problem. :-(
When I upgraded from Mageia 5 of my computer Eeepc 1011PX.
This computer using intel driver.

Error messages:
# journalctl | grep plymouth
jún 25 10:51:26 asus.mageia systemd[1]: plymouth-quit-wait.service start operation timed out. Terminating.
jún 25 10:51:26 asus.mageia systemd[1]: Unit plymouth-quit-wait.service entered failed state.
jún 25 10:51:26 asus.mageia systemd[1]: plymouth-quit-wait.service failed.

If typing it "service dm start" or "systemctl start dm" then kdm started, and all right.
Now probed Lightdm....

CC: (none) => pingvin

Comment 4 Samuel Verschelde 2015-09-21 13:21:22 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 5 Marja Van Waes 2015-10-27 06:58:22 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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


Note You need to log in before you can comment on or make changes to this bug.