Bug 477121

Summary: SeLinux ConsoleKit incompatibility
Product: [Fedora] Fedora Reporter: bob mckay <urilabob>
Component: ConsoleKitAssignee: jmccann
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 9CC: cschalle, eager, jmccann
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-14 15:33:57 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:
Attachments:
Description Flags
Selinux alert regarding connectkit failur none

Description bob mckay 2008-12-19 08:24:55 UTC
Description of problem:
SeLinux prevents X11 session management running. This seems to be a consolekit interaction.
There is consequent failure of PackageKit etc.

Nov 20 00:45:57 Updated: selinux-policy-3.3.1-107.fc9.noarch
Nov 20 00:50:57 Updated: selinux-policy-targeted-3.3.1-107.fc9.noarch
Dec 14 01:32:54 Updated: selinux-policy-3.3.1-111.fc9.noarch
Dec 14 01:33:59 Updated: selinux-policy-targeted-3.3.1-111.fc9.noarch
(I'm running targeted/enforcing)

Can't find a way to get ConsoleKit details, but 
ck-list-sessions 0.2.10

How reproducible:
Always

Steps to Reproduce:
1. Start X session
2. Run Package installer (or anything else that depends on ConsoleKit)

Actual results:
Package installer fails to launch (no messages, just appears in the list of applications at the screen bottom for a few seconds, then disappears without launching a window).

Expected results:
Package installer runs normally

Additional info:
Although the symptoms are slightly different, I think this is probably the same problem as I previously documented as Bug 476402 (the primary difference in that case being that the X11 session was running from vnc) - I finally got an opportunity to run the machine with a directly connected monitor. I'm raising a separate bug mainly to make sure it's clear that it's not just a vncserver problem.

I note that I may not be the only user reporting this problem as arising recently:
http://n2.nabble.com/Nautilus-doesn%27t-start-td1633015.html
seems to be referring to a similar problem.

setroubleshoot reports a problem with ck-get-x11-serv (I assume it's the cause
of the above). See sel_ckgetx11serv.pdf

I don't think it's just a labeling problem, as this problem recurred
immediately after an autorelabel. However I can't guarantee that the
autorelabel was successful, as selinux reported some problems with restorecon
at about the time the autorelabel should have been happening (see
sel_restorecon.pdf). I can't figure any way to check this.

Comment 1 bob mckay 2008-12-19 08:25:33 UTC
*** Bug 476402 has been marked as a duplicate of this bug. ***

Comment 2 bob mckay 2008-12-19 08:27:22 UTC
Created attachment 327419 [details]
Selinux alert regarding connectkit failur

Comment 3 Bug Zapper 2009-06-10 03:26:34 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 WONTFIX if it remains open with a Fedora 
'version' of '9'.

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 prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-07-14 15:33:57 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.

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