Bug 1067213 - SELinux is preventing /usr/bin/sddm-greeter from connectto access on the unix_stream_socket
Summary: SELinux is preventing /usr/bin/sddm-greeter from connectto access on the unix...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 20
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1071671 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-19 23:26 UTC by Branislav Blaškovič
Modified: 2015-06-30 01:34 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-30 01:34:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
grep sddm /var/log/audit/audit.log (45.18 KB, text/plain)
2014-02-19 23:26 UTC, Branislav Blaškovič
no flags Details

Description Branislav Blaškovič 2014-02-19 23:26:51 UTC
Created attachment 865288 [details]
grep sddm /var/log/audit/audit.log

Description of problem:
  I can see only black screen after sddm launch.

Version-Release number of selected component (if applicable):
  sddm-0.2.0-0.24.20131125git7a008602.fc21.x86_64
  selinux-policy-3.13.1-25.fc21.noarch

Steps to Reproduce:
  1. systemctl stop gdm; systemctl start sddm (or just enable & restart)

Actual results:
  Black screen

Expected results:
  sddm greater!

Additional info:
journalctl:

feb 20 00:18:07 localhost.localdomain setroubleshoot[2422]: SELinux is preventing /usr/bin/sddm-greeter from read access on the directory . For complete SELinux messages. run sealert -l d0a69736-dc9a-4eb
feb 20 00:18:07 localhost.localdomain python[2422]: SELinux is preventing /usr/bin/sddm-greeter from read access on the directory

Comment 1 Branislav Blaškovič 2014-02-19 23:28:03 UTC
Testing on clean rawhide installation of 20140218 Live desktop iso. (just installed sddm)

Comment 2 Daniel Walsh 2014-02-20 20:06:23 UTC
/usr/bin/sddm-greeter  should be labeled as xdm_exec_t/

d1f821b85308c5d79da2f1de938c66861dbad421 fixes this in git.

Comment 3 Paweł Sikora 2014-02-28 18:20:58 UTC
i ran into this sddm blocker during regular fc20 update. please push fixed selinux-policy to updates asap ....

Comment 4 Miroslav Grepl 2014-03-03 10:32:57 UTC
*** Bug 1071671 has been marked as a duplicate of this bug. ***

Comment 5 Miroslav Grepl 2014-03-03 10:42:04 UTC
Please

yum update selinux-policy-targeted --enablerepo=updates-testing

to see if it works.

Comment 6 Fedora End Of Life 2015-05-29 10:59:16 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 7 Fedora End Of Life 2015-06-30 01:34:42 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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


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