Bug 967199 - lightdm doesn't start with SELINUX=enforcing
Summary: lightdm doesn't start with SELINUX=enforcing
Keywords:
Status: CLOSED DUPLICATE of bug 969090
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 18
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-25 12:17 UTC by Eugene A. Pivnev
Modified: 2013-05-30 15:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-30 15:51:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Eugene A. Pivnev 2013-05-25 12:17:21 UTC
Description of problem:

LightDM can't start with SELINUX=enforcing.
"Permissive" or "Disabled" - ok.

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

* Fedora 18 (i686)
* lightdm-1.4.1-3.fc18.i686
* lightdm-razorqt-0.5.2-8.fc18.i686 (lightdm greeter)


How reproducible:


Steps to Reproduce:
1. yum install lightdm-razorqt
2. /etc/sysconfig/desktop: DISPLAYMANAGER=/usr/sbin/lightdm
3. /etc/selinux/config: SELINUX=enforcing
4. init 6

Additional info:

Problem appeared during creating QtDesktop spin (http://fedoraproject.org/wiki/QtDesktop_Spin).
After "yum remove selinux-policy" and install it again lightdm started ok.
Now QtDesktop's *.ks contains "selinux --permissive".

Comment 1 Rex Dieter 2013-05-25 12:34:45 UTC
For what it's worth, during testing, I set selinux in permissive to get lightdm with lightdm-razorqt greeter to start ok.  But I couldnt find anything relevant in /var/log/audit/audit.log (nothing mentioning lightdm anyway).

Comment 2 Miroslav Grepl 2013-05-27 13:48:59 UTC
Could it be tested with

# semodule -DB

re-test it and 

# ausearch -m avc,user_avc -ts recent |audit2allow

Comment 3 Rex Dieter 2013-05-30 15:51:45 UTC
sealert finally showed me the denial, see bug #969090

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


Note You need to log in before you can comment on or make changes to this bug.