If the someone installs packages in his user site directory then Blueman may start using one of these instead of the system package. This can create problems with compatibility and SELinux ( https://bugzilla.redhat.com/show_bug.cgi?id=2179800 ). To get rid of the SELinux messages I had to modify $ rpm -ql blueman | grep '/usr/\(bin\|libexec\)/' /usr/bin/blueman-adapters /usr/bin/blueman-applet /usr/bin/blueman-manager /usr/bin/blueman-sendto /usr/bin/blueman-services /usr/bin/blueman-tray /usr/libexec/blueman-mechanism /usr/libexec/blueman-rfcomm-watcher and add at least '-s'. Tuned uses similar approach: $ head -n 1 /usr/sbin/tuned #!/usr/libexec/platform-python -Es Reproducible: Always Steps to Reproduce: 1. Install Blueman 2. Login and try using it Actual Results: SELinux error message from the SELinux Troubleshooter. Expected Results: No SELinux errors and no python user site files being accessed.
Ok, so it seems this can be fixed quite easily by running %py3_shebang_fix on the installed files. This tool defaults to adding "-sP", but it's easy enough to change that to "-sPE". Any downside to having all three of those, or should I just go ahead?
IDK, "-sPE" sounds even better to me. IMHO if the user wants to run the app with custom libraries it would be logical to also run custom main app, not use the system-wide one.
FEDORA-2023-6f71ab0049 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6f71ab0049
FEDORA-2023-1e7501bfa3 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1e7501bfa3
FEDORA-2023-6f71ab0049 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-6f71ab0049` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-6f71ab0049 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-1e7501bfa3 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-1e7501bfa3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-1e7501bfa3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-6f71ab0049 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-1e7501bfa3 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.