Description of problem: Hello, I am getting this error at each boot. I have enabled autologin (and LUKS). SELinux is preventing gdm-session-wor from 'read' accesses on the key Unknown. ***** Plugin catchall (100. confidence) suggests ************************** If vous pensez que gdm-session-wor devrait être autorisé à accéder read sur Unknown key par défaut. Then vous devriez rapporter ceci en tant qu'anomalie. Vous pouvez générer un module de stratégie local pour autoriser cet accès. Do allow this access for now by executing: # ausearch -c 'gdm-session-wor' --raw | audit2allow -M my-gdmsessionwor # semodule -X 300 -i my-gdmsessionwor.pp Additional Information: Source Context system_u:system_r:xdm_t:s0-s0:c0.c1023 Target Context system_u:system_r:kernel_t:s0 Target Objects Unknown [ key ] Source gdm-session-wor Source Path gdm-session-wor Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-225.3.fc25.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 4.8.14-300.fc25.x86_64 #1 SMP Mon Dec 12 16:31:04 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-12-18 10:33:17 CET Last Seen 2016-12-18 10:33:17 CET Local ID 2d110b13-bdf6-4c1d-a9f2-dc52ef7671f8 Raw Audit Messages type=AVC msg=audit(1482053597.781:135): avc: denied { read } for pid=1406 comm="gdm-session-wor" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:system_r:kernel_t:s0 tclass=key permissive=1 Hash: gdm-session-wor,xdm_t,kernel_t,key,read Version-Release number of selected component: selinux-policy-3.13.1-225.3.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.8.14-300.fc25.x86_64 type: libreport
Description of problem: notification appeared at boot Version-Release number of selected component: selinux-policy-3.13.1-225.11.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.10.5-200.fc25.x86_64 type: libreport
Description of problem: This AVC is triggered just after login with a X.Org session. Version-Release number of selected component: selinux-policy-3.13.1-225.11.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.10.8-200.fc25.x86_64 type: libreport
Oh and BTW, just the the original reporter, I have also enabled LUKS and autologin.
Oh and BTW, just like the original reporter, I have also enabled LUKS and autologin.
Description of problem: This AVC is triggered after each login. I'm using F25 with Xorg, a fulldisk encryption and autologin. Version-Release number of selected component: selinux-policy-3.13.1-225.11.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.10.8-200.fc25.x86_64 type: libreport
*** Bug 1446838 has been marked as a duplicate of this bug. ***
*** Bug 1487242 has been marked as a duplicate of this bug. ***
*** Bug 1487996 has been marked as a duplicate of this bug. ***
*** Bug 1497516 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.