Bug 862821

Summary:	can't reboot or shutdown from gnome
Product:	[Fedora] Fedora	Reporter:	Kamil Páral <kparal>
Component:	selinux-policy	Assignee:	Miroslav Grepl <mgrepl>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	awilliam, dominick.grift, dwalsh, mgrepl, robatino
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:	2012-10-04 10:19:48 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:
Bug Depends On:
Bug Blocks:	752660

Description Kamil Páral 2012-10-03 15:52:25 UTC

Description of problem:
I installed F18 Beta TC1 (any architecture) from PXE. The installed system boots and works, but can't be rebooted or shut down from gnome session or gdm. Every time I try that, I'm brought back to gdm.

With selinux=0 on the boot line, the problem is gone.

The same happens with netinst installations. But LiveCD installation doesn't have this problem.

Version-Release number of selected component (if applicable):
selinux-policy-3.11.1-25.fc18

How reproducible:
always

Steps to Reproduce:
1. install F18 Beta TC1 over PXE or netinst
2. try to reboot installed system from gnome session or gdm (using buttons)

Comment 1 Kamil Páral 2012-10-03 15:53:49 UTC

Ho ho, blocker.

" All release-blocking desktops' offered mechanisms (if any) for shutting down, logging out and rebooting must work "
https://fedoraproject.org/wiki/Fedora_18_Beta_Release_Criteria

Comment 2 Kamil Páral 2012-10-03 16:49:09 UTC

Antonio Olivares claims on test@ list that he sees this bug also on system installed via LiveCD Fedora 18 Alpha RC2, and updated.

Comment 3 Kamil Páral 2012-10-04 10:19:48 UTC

The problem happens with systemd-193-13fc18. The problem is solved with systemd-194-1.fc18. (no selinux-policy change needed).

Because systemd-194-1.fc18 is now in stable updates, closing.

Comment 4 Adam Williamson 2012-10-05 01:53:11 UTC


*** This bug has been marked as a duplicate of bug 859614 ***