Version-Release number of selected component: policycoreutils-python-utils-2.8-1.fc28 Additional info: reporter: libreport-2.9.5 cmdline: /usr/bin/python3 -Es /sbin/semanage fcontext -d -t rpm_exec_t /usr/share/dnfdaemon/dnfdaemon-system crash_function: get_installed_policy exception_type: ValueError executable: /sbin/semanage interpreter: python3-3.6.6-1.fc28.x86_64 kernel: 4.17.9-200.fc28.x86_64 runlevel: N 5 type: Python3 uid: 0 Truncated backtrace: __init__.py:130:get_installed_policy:ValueError: No SELinux Policy installed Traceback (most recent call last): File "/sbin/semanage", line 28, in <module> import seobject File "/usr/lib/python3.6/site-packages/seobject.py", line 34, in <module> import sepolicy File "/usr/lib/python3.6/site-packages/sepolicy/__init__.py", line 165, in <module> raise e File "/usr/lib/python3.6/site-packages/sepolicy/__init__.py", line 161, in <module> policy_file = get_installed_policy() File "/usr/lib/python3.6/site-packages/sepolicy/__init__.py", line 130, in get_installed_policy raise ValueError(_("No SELinux Policy installed")) ValueError: No SELinux Policy installed Local variables in innermost frame: policies: [] path: '//etc/selinux/targeted/policy/policy' root: '/'
Created attachment 1471659 [details] File: backtrace
Created attachment 1471660 [details] File: cgroup
Created attachment 1471661 [details] File: cpuinfo
Created attachment 1471662 [details] File: environ
Created attachment 1471663 [details] File: mountinfo
Created attachment 1471664 [details] File: namespaces
Created attachment 1471665 [details] File: open_fds
Created attachment 1471666 [details] File: screencast-07-31-2018-07:22:30 AM.webm
Created attachment 1471667 [details] File: screencast-07-31-2018-07:23:01 AM.webm
Thank you for reporting the issue. Cold you please provide the output of the following commands? # sestatus # dnf list "selinux-policy*" Also, it would help if you could specify under what circumstances the traceback appeared.
*** Bug 1548037 has been marked as a duplicate of this bug. ***
*** Bug 1565057 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days