Bug 857719 - system-config-selinux - could not open interface info [/var/lib/sepolgen/interface_info]
system-config-selinux - could not open interface info [/var/lib/sepolgen/inte...
Product: Fedora
Classification: Fedora
Component: policycoreutils (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Daniel Walsh
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-09-16 10:33 EDT by Flóki Pálsson
Modified: 2012-09-17 19:18 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-09-17 03:52:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Flóki Pálsson 2012-09-16 10:33:40 EDT
Description of problem:
Not possible to open system-config-selinux

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. $ system-config-selinux
Actual results:
could not open interface info [/var/lib/sepolgen/interface_info]

Expected results:
Se GUI to change SELinux 

Additional info:
Comment 1 Flóki Pálsson 2012-09-16 11:12:13 EDT
Now I can start system-config-selinux.
I was using Íslenska ( Iclandic) as Language.
After changing to English as language then I could start system-config-selinux.
Changing back to Íslenska then system-config-selinux works.


]$ system-config-selinux
/usr/share/system-config-selinux/system-config-selinux.py:71: Warning: g_object_get_valist: object class `GnomeProgram' has no property named `default-icon'
  xml = gtk.glade.XML ("/usr/share/system-config-selinux/system-config-selinux.glade", domain=PROGNAME)
[floki@localhost ~]$ 

warning is after root password
Comment 2 Daniel Walsh 2012-09-17 19:18:41 EDT

Is created in the selinux-policy and policycoreutils post install. 

You can also create this using sepolgen-ifgen

Note You need to log in before you can comment on or make changes to this bug.