Bug 198769

Summary: Reboot after disabling selinux occurs after logging in.
Product: [Fedora] Fedora Reporter: Stefan Geuns <bitrain>
Component: firstbootAssignee: Chris Lumens <clumens>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-07-21 13:59:59 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:

Description Stefan Geuns 2006-07-13 13:27:27 UTC
Description of problem:
During firstboot I disabled SELinux and firstboot told me that it needed to 
reboot when it was finished. But when it was done I got the login screen 
instead. So I rebooted manually thinking this was a bug.
But when my system was back up and after I logged in, it rebooted without 
telling me what was going on.

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


How reproducible:


Steps to Reproduce:
1. Disable SELinux during firstboot
2. Log in
3.
  
Actual results:
Reboot after I did the reboot and logging in

Expected results:
Before I get the login screen firstboot should tell me it is going to reboot 
and then reboot. There should be no need to log in first.
Also if the reboot is done manually, there should be no need to reboot 
anymore.

Additional info:
Using kde not gnome (also not installed).

Comment 1 Chris Lumens 2006-07-20 20:50:05 UTC
This works for me post-test 1.  I haven't heard any other reports of this sort
of behavior, and I can't think of why not having GNOME installed would affect
this.  Can you think of anything else to help me debug what might be going on?

Comment 2 Stefan Geuns 2006-07-21 06:59:17 UTC
I have no idea why it didn't work. I'll try again around the the release of 
test 3 and see if it happens again then. I installed FC5 again and it works 
correctly here.

Comment 3 Chris Lumens 2006-07-21 13:59:59 UTC
Okay, feel free to reopen this bug if you experience this problem again with test 3.