Version-Release number of selected component: setroubleshoot-server-3.3.11-2.fc26 Additional info: reporter: libreport-2.9.0 executable: /usr/sbin/setroubleshootd kernel: 4.10.0-0.rc0.git8.1.fc26.x86_64 runlevel: unknown type: Python3 uid: 985 Truncated backtrace: server.py:706:RunFaultServer:SystemError: <built-in function init> returned a result with an error set ValueError: unable to open /sys/fs/selinux/policy: Device or resource busy The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/sbin/setroubleshootd", line 107, in <module> RunFaultServer(timeout) File "/usr/lib/python3.6/site-packages/setroubleshoot/server.py", line 706, in RunFaultServer audit2why.init() SystemError: <built-in function init> returned a result with an error set Local variables in innermost frame: timeout: 10 Potential duplicate: bug 1378940
Created attachment 1236081 [details] File: backtrace
Created attachment 1236082 [details] File: environ
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
Similar problem has been detected: Triggered with Gnome Boxes reporter: libreport-2.9.1 cmdline: /usr/bin/python3 -Es /usr/sbin/setroubleshootd -f '' crash_function: RunFaultServer exception_type: SystemError executable: /usr/sbin/setroubleshootd kernel: 4.11.10-20170605.amdmainhyb.fc26.x86_64 package: setroubleshoot-server-3.3.12-1.fc26 reason: server.py:706:RunFaultServer:SystemError: <built-in function init> returned a result with an error set runlevel: unknown type: Python3 uid: 990
*** Bug 1475990 has been marked as a duplicate of this bug. ***
*** Bug 1476693 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I switched on my system from and this error appeared reporter: libreport-2.9.1 cmdline: /usr/bin/python3 -Es /usr/sbin/setroubleshootd -f '' crash_function: RunFaultServer exception_type: SystemError executable: /usr/sbin/setroubleshootd kernel: 4.11.9-300.fc26.x86_64 package: setroubleshoot-server-3.3.12-1.fc26 reason: server.py:706:RunFaultServer:SystemError: <built-in function init> returned a result with an error set runlevel: N 5 type: Python3 uid: 991
*** Bug 1492836 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I was in Evolution, and clicked REPLY on a message (Evolution EWS mailbox). Once again as so often happens when I use evolution, Gnome FROZE with high disk usage. The only solution is to flip to a text console (CTRL-ALT-F4) and log in is root an execute: killall -3 gnome-shell I noticed that the high disk was caused by gnome-shell writing a core dump. reporter: libreport-2.9.1 crash_function: RunFaultServer exception_type: SystemError executable: /usr/sbin/setroubleshootd kernel: 4.12.13-300.fc26.x86_64 package: setroubleshoot-server-3.3.12-1.fc26 reason: server.py:706:RunFaultServer:SystemError: <built-in function init> returned a result with an error set runlevel: N 5 type: Python3 uid: 974
Absurd error lost since Alpha!!!!!
Similar problem has been detected: this machine has a kernel panic keyboard flashing reporter: libreport-2.9.1 crash_function: RunFaultServer exception_type: SystemError executable: /usr/sbin/setroubleshootd kernel: 4.12.5-300.fc26.i686+PAE package: setroubleshoot-server-3.3.12-1.fc26 reason: server.py:706:RunFaultServer:SystemError: <built-in function init> returned a result with an error set runlevel: unknown type: Python3 uid: 987
With great regret passed momentarily to Windows 10 in that with an ATI R5 M230 with Open notebook driver warmed up too and every time I ran the fan was shooting at 1000, creating a crash..... Wifi and network no longer connect with latest kernels..... Hardware isn't ' recent, however I don't think it should create all these problems.... I have an Asus laptop with an I7-4510U Hopefully within a year Fedora come back to shine!!!!!
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.