Hide Forgot
Description of problem: Since updating to selinux-policy-3.13.1-283.35, gdm is unable to start under the proprietary NVidia driver. SETroubleshoot logged this as a duplicate of bug 1500683, but that was closed last year so I'm opening a new bug for this. Version-Release number of selected component (if applicable): selinux-policy-3.13.1-283.35.fc27.noarch Additional info: ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gnome-shell should be allowed map access on the nvidiactl chr_file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell # semodule -X 300 -i my-gnomeshell.pp Additional Information: Source Context system_u:system_r:xdm_t:s0-s0:c0.c1023 Target Context system_u:object_r:xserver_misc_device_t:s0 Target Objects /dev/nvidiactl [ chr_file ] Source gnome-shell Source Path gnome-shell Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-283.35.fc27.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.17.3-100.fc27.x86_64 #1 SMP Tue Jun 26 14:19:03 UTC 2018 x86_64 x86_64 Alert Count 69 First Seen 2018-07-07 13:56:00 BST Last Seen 2018-07-07 15:02:43 BST Local ID 12464507-760d-4a21-976e-bb65ffe83528 Raw Audit Messages type=AVC msg=audit(1530972163.876:486): avc: denied { map } for pid=13407 comm="gnome-session-c" path="/dev/nvidiactl" dev="devtmpfs" ino=56363 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xserver_misc_device_t:s0 tclass=chr_file permissive=0 Hash: gnome-shell,xdm_t,xserver_misc_device_t,chr_file,map
Today I had the same problem with the proprietary NVidia driver.
After updating to selinux-policy-3.13.1-283.35 I am also experiencing the same exact issue with gdm and the NVidia driver.
same thing, just dnf upgraded the system and getting similar alerts
I had to downgrade selinux-policy from 3.13.1-283.35 to 3.13.1-283.14 to start GNOME.
selinux-policy-3.13.1-284.37.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-4bb4de2d86
selinux-policy-3.13.1-284.37.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-4bb4de2d86
I find that selinux-policy-3.13.1-284.37.fc27 does not fix this for me.
I can confirm that, selinux-policy-3.13.1-284.37.fc27 does not fix the issue. I had to dnf downgrade selinux-policy-3.13.1-283.14.fc27 to get gdm / graphical login screen back.
selinux-policy-3.13.1-284.37.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
selinux-policy-3.13.1-284.37.fc27 is not fixing the issue for me. Is there another solution?
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.