Description of problem: After upgrade from F33 to F34 Beta. SELinux is preventing gnome-shell from read, write access on the fichier /memfd:wayland-cursor (deleted). ***** Plugin restorecon (99.5 confidence) suggests ************************ Si vous souhaitez corriger l'étiquette. L'étiquette par défaut de /memfd:wayland-cursor (deleted) devrait être etc_runtime_t. Then vous pouvez lancer restorecon. La tentative d’accès pourrait avoir été stoppée due à des permissions insuffisantes d’accès au dossier parent, auquel cas essayez de changer la commande suivante en conséquence. Do # /sbin/restorecon -v /memfd:wayland-cursor (deleted) ***** Plugin catchall (1.49 confidence) suggests ************************** Si vous pensez que gnome-shell devrait être autorisé à accéder read write sur memfd:wayland-cursor (deleted) file 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 autoriser cet accès pour le moment en exécutant : # 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:tmpfs_t:s0 Target Objects /memfd:wayland-cursor (deleted) [ file ] Source gnome-shell Source Path gnome-shell Port <Inconnu> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-3.14.7-27.fc34.noarch Local Policy RPM selinux-policy-targeted-3.14.7-27.fc34.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.11.9-300.fc34.x86_64 #1 SMP Wed Mar 24 12:06:51 UTC 2021 x86_64 x86_64 Alert Count 3 First Seen 2021-03-27 07:56:01 CET Last Seen 2021-03-27 07:58:23 CET Local ID 67dca9f0-161d-4f88-8770-3db05766d79a Raw Audit Messages type=AVC msg=audit(1616828303.792:989): avc: denied { read write } for pid=3925 comm="gnome-shell" path=2F6D656D66643A7761796C616E642D637572736F72202864656C6574656429 dev="tmpfs" ino=20 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:tmpfs_t:s0 tclass=file permissive=0 Hash: gnome-shell,xdm_t,tmpfs_t,file,read,write Version-Release number of selected component: selinux-policy-targeted-3.14.7-27.fc34.noarch Additional info: component: selinux-policy reporter: libreport-2.14.0 hashmarkername: setroubleshoot kernel: 5.11.9-300.fc34.x86_64 type: libreport Potential duplicate: bug 1941851
Similar problem has been detected: After login hashmarkername: setroubleshoot kernel: 5.11.9-300.fc34.x86_64 package: selinux-policy-targeted-3.14.7-28.fc34.noarch reason: SELinux is preventing gnome-shell from read, write access on the file /memfd:wayland-cursor (deleted). type: libreport
Still present with: selinux-policy-3.14.7-29.fc34.noarch selinux-policy-targeted-3.14.7-29.fc34.noarch
*** Bug 1941851 has been marked as a duplicate of this bug. ***
*** Bug 1941852 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Upgraded to fedora 34 hashmarkername: setroubleshoot kernel: 5.11.11-300.fc34.x86_64 package: selinux-policy-targeted-3.14.7-29.fc34.noarch reason: SELinux is preventing gnome-shell from read, write access on the file /memfd:wayland-cursor (deleted). type: libreport
*** Bug 1948072 has been marked as a duplicate of this bug. ***
*** Bug 1950178 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Booted fc34 WS and logged in. hashmarkername: setroubleshoot kernel: 5.11.14-300.fc34.x86_64 package: selinux-policy-targeted-34.3-1.fc34.noarch reason: SELinux is preventing gnome-shell from read, write access on the file /memfd:wayland-cursor (deleted). type: libreport
Similar problem has been detected: I switched between users in GNOME Workstation. hashmarkername: setroubleshoot kernel: 5.11.14-300.fc34.x86_64 package: selinux-policy-targeted-34.3-1.fc34.noarch reason: SELinux is preventing gnome-shell from read, write access on the file /memfd:wayland-cursor (deleted). type: libreport
Happens to me too when resuming from suspend.
Similar problem has been detected: Happened right after first login after an upgrade from Fedora 33 to Fedora 34. hashmarkername: setroubleshoot kernel: 5.11.15-300.fc34.x86_64 reason: SELinux is preventing gnome-shell from read, write access on the file /memfd:wayland-cursor (deleted). type: libreport
Similar problem has been detected: DEFAULTH hashmarkername: setroubleshoot kernel: 5.11.16-300.fc34.x86_64 package: selinux-policy-targeted-34.3-1.fc34.noarch reason: SELinux is preventing gnome-shell from read, write access on the file /memfd:wayland-cursor (deleted). type: libreport
Similar problem has been detected: Unknown. System upgrade and reboot. hashmarkername: setroubleshoot kernel: 5.11.16-300.fc34.x86_64 package: selinux-policy-targeted-34.3-1.fc34.noarch reason: SELinux is preventing gnome-shell from 'map' accesses on the file /memfd:wayland-cursor (deleted). type: libreport
Similar problem has been detected: This happened on update from F33->F34 after autorelabel. hashmarkername: setroubleshoot kernel: 5.11.16-300.fc34.x86_64 package: selinux-policy-targeted-34.3-1.fc34.noarch reason: SELinux is preventing gnome-shell from 'map' accesses on the file /memfd:wayland-cursor (deleted). type: libreport
Similar problem has been detected: Upgraded to Fedora 34 hashmarkername: setroubleshoot kernel: 5.11.16-300.fc34.x86_64 package: selinux-policy-targeted-34.3-1.fc34.noarch reason: SELinux is preventing gnome-shell from read, write access on the file /memfd:wayland-cursor (deleted). type: libreport
Similar problem has been detected: Upgraded to Fedora 34 from Fedora 33. hashmarkername: setroubleshoot kernel: 5.11.16-300.fc34.x86_64 package: selinux-policy-targeted-34.3-1.fc34.noarch reason: SELinux is preventing gnome-shell from read, write access on the file /memfd:wayland-cursor (deleted). type: libreport
*** Bug 1957076 has been marked as a duplicate of this bug. ***
*** Bug 1957780 has been marked as a duplicate of this bug. ***
*** Bug 1957810 has been marked as a duplicate of this bug. ***
This is a known problem, the straightforward solution did not succeed though: https://github.com/fedora-selinux/selinux-policy/pull/653 A more complex approach is required to resolve it.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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. Thank you for reporting this bug and we are sorry it could not be fixed.