Version-Release number of selected component: setroubleshoot-server-3.3.11-3.fc26 Additional info: reporter: libreport-2.9.0 cmdline: /usr/bin/python3 -Es /usr/sbin/setroubleshootd -f '' crash_function: sighandler exception_type: SystemExit executable: /usr/sbin/setroubleshootd kernel: 4.11.0-0.rc0.git9.1.fc26.x86_64 runlevel: N 5 type: Python3 uid: 981 Truncated backtrace: service.py:647:_message_cb:SystemError: <built-in function isinstance> returned a result with an error set Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/dbus/connection.py", line 521, in _signal_func def _signal_func(self, message): File "/usr/lib/python3.6/site-packages/setroubleshoot/server.py", line 114, in sighandler sys.exit() SystemExit The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/dbus/service.py", line 647, in _message_cb if not isinstance(message, MethodCallMessage): SystemError: <built-in function isinstance> returned a result with an error set Local variables in innermost frame: self: <setroubleshoot.server.SetroubleshootdDBusObject at /org/fedoraproject/Setroubleshootd at 0x7f748d12d198> message: <dbus.lowlevel.MethodCallMessage path: /org/fedoraproject/Setroubleshootd, iface: org.fedoraproject.SetroubleshootdIface, member: avc dest: org.fedoraproject.Setroubleshootd> connection: <dbus._dbus.SystemBus (system) at 0x7f7485087518> Potential duplicate: bug 1352209
Created attachment 1260581 [details] File: backtrace
Created attachment 1260582 [details] File: cgroup
Created attachment 1260583 [details] File: environ
Created attachment 1260584 [details] File: mountinfo
Created attachment 1260585 [details] File: namespaces
Created attachment 1260586 [details] File: open_fds
Similar problem has been detected: Found this after first boot of a Fedora 26 i686 Workstation install. Not sure what triggered it. reporter: libreport-2.9.1 cmdline: /usr/bin/python3 -Es /usr/sbin/setroubleshootd -f '' crash_function: sighandler exception_type: SystemExit executable: /usr/sbin/setroubleshootd kernel: 4.11.0-0.rc5.git0.1.fc26.i686+PAE package: setroubleshoot-server-3.3.11-3.fc26 reason: service.py:647:_message_cb:SystemError: <built-in function isinstance> returned a result with an error set runlevel: N 5 type: Python3 uid: 990
Proposed as a Blocker for 26-final by Fedora user genodeftest using the blocker tracking app because: This crasher happens at first boot, thus violating https://fedoraproject.org/wiki/Fedora_26_Final_Release_Criteria#SELinux_and_crash_notifications
Discussed during the 2017-04-24 blocker review meeting: [1] The decision to delay the classification of this bug was made as we need more data to make an informed decision. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2017-04-24/f26-blocker-review.2017-04-24-16.00.txt
Discussed during the 2017-05-01 blocker review meeting: [1] The decision to classify this bug as a RejectedBlocker was made as it does not seem to be widespread enough to warrant a blocker status. If this is found to be more widespread, we will reconsider it's blocker status. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2017-05-01/f26-blocker-review.2017-05-01-16.02.txt
Related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1366004 (probably a duplicate)
(In reply to Christian Stadelmann from comment #11) > Related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1366004 (probably a > duplicate) It is a duplicate, just on F26. Line numbers changed but its the same thing.
(In reply to Steve Grubb from comment #12) > (In reply to Christian Stadelmann from comment #11) > > Related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1366004 (probably a > > duplicate) > > It is a duplicate, just on F26. Line numbers changed but its the same thing. That BZ was moved to dbus-python and this one is still on setroubleshoot BTW. I annot reproduce it reliably but I hit it quite often. And it might be partially related to bug caused by "rpm --rebuilddb" bugzilla.redhat.com/show_bug.cgi?id=1461313#c2. I just want to let you know.
For my sysem, this issue (crash) only occurs when the installation is entirely on btrfs.
*** This bug has been marked as a duplicate of bug 1366004 ***