Version-Release number of selected component: policycoreutils-devel-2.2.5-1.fc20 Additional info: reporter: libreport-2.1.10 cmdline: /usr/bin/python -Es /usr/bin/sepolicy gui executable: /usr/bin/sepolicy kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: Python uid: 500 Truncated backtrace: connection.py:651:call_blocking:DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/sepolicy/gui.py", line 2626, in change_default_mode self.dbus.change_default_mode(button.get_label().lower()) File "<string>", line 2, in change_default_mode File "/usr/lib/python2.7/site-packages/slip/dbus/polkit.py", line 121, in _enable_proxy return func(*p, **k) File "/usr/lib64/python2.7/site-packages/sepolicy/sedbus.py", line 44, in change_default_mode ret = self.dbus_object.change_default_mode(value, dbus_interface = "org.selinux") File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Local variables in innermost frame: byte_arrays: False self: <dbus._dbus.SystemBus (system) at 0x2d68a10> args: ('disabled',) object_path: '/org/selinux/object' signature: u's' bus_name: dbus.UTF8String(':1.2326') get_args_opts: {'byte_arrays': False, 'utf8_strings': False} timeout: -1.0 kwargs: {} dbus_interface: 'org.selinux' message: <dbus.lowlevel.MethodCallMessage path: /org/selinux/object, iface: org.selinux, member: change_default_mode dest: :1.2326> method: 'change_default_mode'
Created attachment 848619 [details] File: backtrace
Created attachment 848620 [details] File: dso_list
Created attachment 848621 [details] File: environ
What does # rpm -qa policycoreutils-* show?
policycoreutils-devel-2.2.5-1.fc20 is listed above. What were you trying to do with the gui when it blew up?
(In reply to Miroslav Grepl from comment #4) > What does > > # rpm -qa policycoreutils-* > > show? # rpm -qa policycoreutils-* policycoreutils-devel-2.2.5-1.fc20.x86_64 policycoreutils-python-2.2.5-1.fc20.x86_64 policycoreutils-gui-2.2.5-1.fc20.x86_64 policycoreutils-sandbox-2.2.5-1.fc20.x86_64 policycoreutils-restorecond-2.2.5-1.fc20.x86_64
Sorry, the packages were for Miroslav Grepl. Abrt showed up on start of the gui and I submitted the report w/o knowing what had happened. It could have to do with me first entering the root passwd when I should actually have entered the passwd of my user as the auth goes via sudo - just tried that, couldn't reproduce. I called "/usr/bin/system-config-selinux" from the KDE menu, which is in the Administration submenu.
Another user experienced a similar problem: SELinux configiruation after seelected YES at Disable ablility to run unconfined system Processes? reporter: libreport-2.1.11 cmdline: /usr/bin/python -Es /usr/bin/sepolicy gui event_log: 2014-01-18-13:19:05> ("report_uReport" ukończono pomyślnie) executable: /usr/bin/sepolicy kernel: 3.12.7-300.fc20.x86_64 package: policycoreutils-devel-2.2.5-1.fc20 reason: connection.py:651:call_blocking:DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. runlevel: N 5 type: Python uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.