Bug 1074137

Summary:	failed to start lsb
Product:	[Fedora] Fedora	Reporter:	Peter H. Jones <jones.peter.busi>
Component:	lsb	Assignee:	Elena Zannoni <ezannoni>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	bugzilla, Tejeevpatel
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 11:07:03 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:
Embargoed:

Description Peter H. Jones 2014-03-08 05:12:00 UTC

Description of problem:
When I boot Fedora-Live-Jam-KDE-x86_64-rawhide-20140305.iso on a TOSHIBA Qosmio X770/PGRAA, BIOS 1.60 12/22/2011, the boot hangs with a Failed to start LSB. Console messages suggest issuing a "systemctl status LSB" (I think), but I am not able to get get a console where I can enter commands. If I try CTRL-ALT-Fn, I always get a blank screen.

Version-Release number of selected component (if applicable):
I searched for "lsb" and "LSB" in http://kojipkgs.fedoraproject.org//work/tasks/2931/6602931/livecd.log, but could not find it.

How reproducible:
Every time.

Steps to Reproduce:
1. Boot the CD
2. In Troubleshooting menu, edit "Start with basic graphics" by removing rhgb, quiet and threadirqs, and adding a 3 to start in text mode

Actual results:
Messages on screen indicating progress of boot. Eventually, the messages show one or more attempts to start LSB, and then failure 5 1/2 minutes later.

Expected results:
Normal boot. Perhaps LSB can be inhibited on the boot line.

Additional info:
This DVD is a couple of days old. Building of more recent versions has failed for the Mar 6 and 7.

Comment 1 Peter H. Jones 2014-03-08 05:31:33 UTC

I looked at the messages again. I think the system is trying to start a service starting with "live", maybe liveuser or livesys. The hang occurs after firewalld is started succesfully.

Comment 2 Peter H. Jones 2014-03-08 18:20:25 UTC

I tried booting in single, mode 1 and mode 2. In single and mode 1, I went into rescue mode and was asked for the root password. Hitting Enter did not log me in, although the root password is removed when the system has finished booting.

The text at the bottom of the screen reads:
"Started firewalld
A start job is running for LSB: Init script for live...nn / 5min31s)", where nn counts over and over again from 0 to 59 five times.

After five minutes or so, the last line is replaced by:
"[FAILED} failed to start LSB: Init script for live image.."

I see Fedora-Live-Jam-KDE-x86_64-rawhide-20140305.iso is available. I'll give it a shot.

Comment 3 Peter H. Jones 2014-03-08 18:24:27 UTC

See also bug 1034414.

Comment 4 Jaroslav Reznik 2015-03-03 15:33:24 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 5 Steve 2015-05-31 05:17:09 UTC

I can confirm this bug in Fedora 22 Final (Fedora-Live-Workstation-x86_64-22-3.iso).

Comment 6 Tejeevpatel 2015-09-27 20:28:11 UTC

Same here.  I was attempting to boot xfce spin of 22 a Samsung I7.  Was running off a multisession dvd though.

Comment 7 Fedora End Of Life 2016-07-19 11:07:03 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.