Bug 426134 - system-config-selinux displays an error message on start
system-config-selinux displays an error message on start
Status: CLOSED DUPLICATE of bug 216685
Product: Fedora
Classification: Fedora
Component: pygtk2 (Show other bugs)
8
i686 Linux
low Severity low
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-18 14:01 EST by Michael Sedkowski
Modified: 2007-12-19 13:16 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-12-19 13:16:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michael Sedkowski 2007-12-18 14:01:22 EST
Description of problem:
When launching system-config-selinux from the console an error is displayed:

/usr/share/system-config-selinux/system-config-selinux.py:71: Warning:
IA__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)

The applet itself,however, works fine.

Version-Release number of selected component (if applicable):
Newest available in F8.  

How reproducible:
Launch system-config-securitylevel from the console

Steps to Reproduce:
1.
2.
3.
  
Actual results:
An error is being displayed

Expected results:
No error massage.

Additional info:
Comment 1 Thomas Woerner 2007-12-19 06:00:10 EST
Reassigning to policycoreutils.
Comment 2 Daniel Walsh 2007-12-19 13:08:07 EST
This is actually a well reported problem with pygtk and has nothing to do with
selinux.
Comment 3 Matthew Barnes 2007-12-19 13:16:34 EST
PyGTK is binding the GnomeProgram class from libgnome instead of libgnomeui,
which has the "default-icon" property.

*** This bug has been marked as a duplicate of 216685 ***

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