Bug 739258
Summary: | Graphical firstboot runs, even if /etc/sysconfig/firstboot has RUN_FIRSTBOOT=NO | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jared Smith <jsmith.fedora> |
Component: | firstboot | Assignee: | Martin Gracik <mgracik> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | awilliam, bcl, dmach, mads, mgracik |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-09-22 21:24:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 713564 |
Description
Jared Smith
2011-09-16 22:56:04 UTC
er, you did? I chatted with you a bit, but I didn't say I'm seeing this. I'm not. I tested it, and couldn't get the same thing, either in graphical or text mode. Trying to call firstboot directly also caused it to quit immediately, as it should. does firstboot run if you simply call it directly? Discussed at the 2011-09-21 go/no-go meeting (note: in #fedora-meeting-1), acting as a blocker review meeting. Agreed to leave this one till Friday, as it's potentially a serious issue, but no-one besides Jared can reproduce it, or see how it could be possible. Jared, please look into this more closely and try to figure out how the check in /etc/init.d/firstboot is being circumvented in your case. thanks! You mean firstboot started when you booted the livecd? Not the installed system? Yes, firstboot started when I booted the LiveCD (before I had a chance to install the system), but I've since re-installed the LiveCD image to my USB key, and am no longer seeing that behavior. Not sure what (if anything) is different, besides the fact that maybe the SELinux bug was somehow having an effect. Let's go ahead and close this bug, and I'll re-open it if I can reproduce it in my testing again. |