Fedora Account System
Red Hat Associate
Red Hat Customer
Version-Release number of selected component: setroubleshoot-3.3.17-1.fc27 Additional info: reporter: libreport-2.9.3 crash_function: get exception_type: GLib.GError executable: /usr/bin/seapplet kernel: 4.15.6-300.fc27.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: proxy.py:47:get:GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying (4) Traceback (most recent call last): File "/usr/bin/seapplet", line 164, in <module> my = SEApplet() File "/usr/bin/seapplet", line 85, in __init__ '/org/fedoraproject/Setroubleshootd' File "/usr/lib/python3.6/site-packages/pydbus/proxy.py", line 47, in get 0, timeout_to_glib(timeout), None) GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying (4) Local variables in innermost frame: timeout: None kwargs: {} object_path: '/org/fedoraproject/Setroubleshootd' bus_name: 'org.fedoraproject.Setroubleshootd' self: <pydbus.bus.Bus object at 0x7fd26e510940>
Created attachment 1406405 [details] File: backtrace
Created attachment 1406406 [details] File: cpuinfo
Similar problem has been detected: Crashed after a reboot. reporter: libreport-2.9.3 cmdline: /usr/bin/python3 /usr/bin/seapplet crash_function: get exception_type: GLib.GError executable: /usr/bin/seapplet kernel: 4.15.7-300.fc27.x86_64 package: setroubleshoot-3.3.17-1.fc27 reason: proxy.py:47:get:GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying (4) runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: After system bootup reporter: libreport-2.9.3 cmdline: /usr/bin/python3 /usr/bin/seapplet crash_function: get exception_type: GLib.GError executable: /usr/bin/seapplet kernel: 4.15.14-300.fc27.i686+PAE package: setroubleshoot-3.3.17-1.fc27 reason: proxy.py:47:get:GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying (4) runlevel: N 5 type: Python3 uid: 1000
*** Bug 1614758 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Running under VirtualBox, ran dnf update. The problem occurred on the first reboot after the update completed. As an aside, I did other (user mode) maintenance while dnf update was running. After seeing a diagnostic screen (and expecting a failure), the reboot continued. I'm assuming I can (but have not tried to) reproduce this problem by reinstalling the update from the 9/4 update base. reporter: libreport-2.9.3 cmdline: /usr/bin/python3 /usr/bin/seapplet crash_function: get exception_type: GLib.GError executable: /usr/bin/seapplet kernel: 4.18.9-100.fc27.x86_64 package: setroubleshoot-3.3.17-1.fc27 reason: proxy.py:47:get:GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying (4) runlevel: N 5 type: Python3 uid: 1000
The "message recipient disconnected" could easily have occurred because I needed to create both a gmail id and a bugzilla id in order to report the problem, and it took some time before I could reply to the automated error reporting tool. The actual problem I had occurred during the boot process. I got an automated pop-up to initiate error reporting, and it appears that the failure of this reporting is what actually got reported, not the error itself. In any case, during a second reboot, no problem occurred. I don't see anything in the journalctl output to indicate that any boot problem occurred, can't find any other saved diagnostic information that might relate to a boot problem, and the original issue was a one-time glitch that didn't appear to cause any operational problem when it occurred, other than the "Report This" pop-up.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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.
*** This bug has been marked as a duplicate of bug 1541607 ***