RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1247996 - sepolicy gui does not start because of traceback
Summary: sepolicy gui does not start because of traceback
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pygobject3
Version: 7.2
Hardware: All
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1222637 1246123 1246125 1259988
TreeView+ depends on / blocked
 
Reported: 2015-07-29 12:16 UTC by Milos Malik
Modified: 2015-11-19 07:33 UTC (History)
12 users (show)

Fixed In Version: pygobject3-3.14.0-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 07:33:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2215 0 normal SHIPPED_LIVE gnome utilities bug fix and enhancement update 2015-11-19 08:26:52 UTC

Description Milos Malik 2015-07-29 12:16:10 UTC 
Description of problem:
 * sepolicy gui is not able to start on RHEL-7.2, but it was able to start on RHEL-7.1

Version-Release number of selected component (if applicable):
policycoreutils-python-2.2.5-18.el7.x86_64
policycoreutils-sandbox-2.2.5-18.el7.x86_64
policycoreutils-restorecond-2.2.5-18.el7.x86_64
policycoreutils-2.2.5-18.el7.x86_64
policycoreutils-gui-2.2.5-18.el7.x86_64
policycoreutils-devel-2.2.5-18.el7.x86_64
policycoreutils-newrole-2.2.5-18.el7.x86_64

How reproducible:
always

Steps to Reproduce:
# sepolicy gui
Traceback (most recent call last):
  File "/usr/bin/sepolicy", line 644, in <module>
    args.func(args)
  File "/usr/bin/sepolicy", line 289, in gui_run
    import sepolicy.gui
  File "/usr/lib64/python2.7/site-packages/sepolicy/gui.py", line 32, in <module>
    from sepolicy.sedbus import SELinuxDBus
  File "/usr/lib64/python2.7/site-packages/sepolicy/sedbus.py", line 5, in <module>
    from slip.dbus import polkit
  File "/usr/lib/python2.7/site-packages/slip/dbus/__init__.py", line 6, in <module>
    import service
  File "/usr/lib/python2.7/site-packages/slip/dbus/service.py", line 28, in <module>
    from slip._wrappers import _gobject as GObject
  File "/usr/lib/python2.7/site-packages/slip/_wrappers/_gobject.py", line 47, in <module>
    setattr(_self, what, getattr(_mod, what))
  File "/usr/lib64/python2.7/site-packages/gi/__init__.py", line 62, in __getattr__
    raise AttributeError(_static_binding_error)
AttributeError: When using gi.repository you must not import static modules like "gobject". Please change all occurrences of "import gobject" to "from gi.repository import GObject". See: https://bugzilla.gnome.org/show_bug.cgi?id=709183
#

Expected results:
 * sepolicy gui starts successfully
Comment 4 Petr Lautrbach 2015-08-11 08:23:00 UTC 
This seems to be caused by a rebase of pygobject3 to 3.14.0, bug #1222637 

I'll take a look if we can make a fix for policycoreutils, but there might be other problems with the incompatible pygobject3 rebase in other packages or third party software.
Comment 5 Petr Lautrbach 2015-08-14 14:18:09 UTC 
I can't reproduce the reported problem but I've a problem with pygobject3 which could be related?

# python
Python 2.7.5 (default, Apr  9 2015, 11:03:32) 
[GCC 4.8.3 20140911 (Red Hat 4.8.3-9)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from gi.repository import Gtk
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python2.7/site-packages/gi/__init__.py", line 42, in <module>
    from . import _gi
ImportError: /usr/lib64/python2.7/site-packages/gi/_gi.so: undefined symbol: g_type_check_instance_is_fundamentally_a

# rpm -qf /usr/lib64/python2.7/site-packages/gi/_gi.so
pygobject3-base-3.14.0-2.el7.x86_64
Comment 6 Milos Malik 2015-08-14 16:08:45 UTC 
# rpm -qa pyg\*
pygobject3-3.14.0-2.el7.x86_64
pygobject2-2.28.6-11.el7.x86_64
pygpgme-0.3-9.el7.x86_64
pygtk2-2.24.0-9.el7.x86_64
pygobject3-base-3.14.0-2.el7.x86_64
pygtk2-libglade-2.24.0-9.el7.x86_64
#
Comment 7 Matthew Barnes 2015-09-15 16:11:32 UTC 
The quoted bug in the traceback [1] seems to me too aggressive for a stable enterprise update.  I think best back that change out for RHEL 7.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=709183
Comment 8 Matthew Barnes 2015-09-15 18:17:26 UTC 
Patched pygobject3-3.14.0-3.el7
Comment 9 Milos Malik 2015-09-16 08:09:49 UTC 
I can confirm that sepolicy gui starts successfully after updating pygobject3 packages to 3.14.0-3.el7 version.
Comment 10 errata-xmlrpc 2015-11-19 07:33:52 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2215.html
Note You need to log in before you can comment on or make changes to this bug.