Bug 1318559

Summary: update fedora(4.4.4-301.fc23.x86_64) 23 workstation edition boot fail
Product: [Fedora] Fedora Reporter: lijun.bai <blj2009r>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 23CC: blj2009r, elad, fedora, rstrode, sgrubb
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 19:29:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
boot fail image none

Description lijun.bai 2016-03-17 08:58:35 UTC
Created attachment 1137331 [details]
boot fail image

Description of problem:

when i update to 4.4.4-301.fc23.x86_64 my computer boot fail ,boot hang up.

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

4.4.4-301.fc23.x86_64
How reproducible:


Steps to Reproduce:
1.my computer is thinkpad e460
2.update from 4.4.4-300.fc23.x86_64  to 4.4.4-301.fc23.x86_64 


Actual results:
boot fail,boot hang up 

Expected results:

boot normal to gui
Additional info:
when i select 4.4.4-300.fc23.x86_64 it boot fine.

Comment 1 Steve Grubb 2016-03-17 12:47:54 UTC
Event 1130 is a service start event. Its saying that the plymouth-start service failed to start. Beyond interpreting this audit event, I don't know how I can help you. This problem is with another package and not audit.

Comment 2 lijun.bai 2016-03-18 04:21:56 UTC
(In reply to Steve Grubb from comment #1)
> Event 1130 is a service start event. Its saying that the plymouth-start
> service failed to start. Beyond interpreting this audit event, I don't know
> how I can help you. This problem is with another package and not audit.

thank you i change to plymouth .

Comment 3 Ray Strode [halfline] 2016-03-18 19:11:27 UTC
does putting plymouth.enable=0 on the kernel command line make it boot?

Comment 4 lijun.bai 2016-03-20 09:43:25 UTC
how can i do it ? from previous kernel? to set plymouth.enable= then restart?

Comment 5 Fedora End Of Life 2016-11-24 16:07:14 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2016-12-20 19:29:38 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.