Version-Release number of selected component: policycoreutils-gui-2.4-8.fc23 Additional info: reporter: libreport-2.6.2 cmdline: /usr/bin/python3 /usr/share/system-config-selinux/selinux_server.py executable: /usr/share/system-config-selinux/selinux_server.py kernel: 4.2.0-0.rc4.git0.1.fc23.x86_64 runlevel: N 5 type: Python3 uid: 0 Truncated backtrace: selinux_server.py:6:<module>:ImportError: No module named 'gobject' Traceback (most recent call last): File "/usr/share/system-config-selinux/selinux_server.py", line 6, in <module> import gobject ImportError: No module named 'gobject' Local variables in innermost frame: __loader__: <_frozen_importlib.SourceFileLoader object at 0x7f478e5aaf60> __doc__: None __package__: None __builtins__: <module 'builtins' (built-in)> __spec__: None dbus: <module 'dbus' from '/usr/lib64/python3.4/site-packages/dbus/__init__.py'> __name__: '__main__' __file__: '/usr/share/system-config-selinux/selinux_server.py' __cached__: None
Created attachment 1060678 [details] File: backtrace
Created attachment 1060679 [details] File: environ
Thanks for the report. It seems to be related to python3 port. We'll try to resolve the issue until Fedora 23 Beta.
Is it also the cause of: [pinkie@linux ~]$ sealert Traceback (most recent call last): File "/usr/bin/sealert", line 50, in <module> from setroubleshoot.util import get_identity, load_plugins, log_debug File "/usr/lib64/python2.7/site-packages/setroubleshoot/util.py", line 291, in <module> from sepolicy import get_all_file_types ImportError: No module named sepolicy ?
There are two different issue. The original report should be fixed by the latest policycoreutils-2.4-9.fc23 update. The problem from #c4 is due to wrong dependencies in not-yet-ported-to-python3 sealert. setroubleshoot-server requires policycoreutils-python-utils requires python3 policycoreutils while it's still python2. There'll be an update of setroubleshoot rewritten for python3 soon. There's already a pull request for that on github [1] and according to my testing, it works reasonably. [1] https://github.com/fedora-selinux/setroubleshoot/pull/8
setroubleshoot testing builds are available in my COPR repository https://copr.fedoraproject.org/coprs/plautrba/setroubleshoot/
Ah ok, thanks for the infos.
I believe that this issue is already solved by the latest update. If the problem persists feel free to reopen this bug.