Bug 1615270

Summary: system-config-printer does not start when pygobject2 is missing
Product: Red Hat Enterprise Linux 7 Reporter: GV <rhel>
Component: system-config-printerAssignee: Zdenek Dohnal <zdohnal>
Status: CLOSED ERRATA QA Contact: Petr Sklenar <psklenar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.5CC: ayadav, ij2fdc402, kzilkova, psklenar, rhel, thozza, tkorbar
Target Milestone: rcKeywords: AutoVerified, EasyFix, FastFix, Patch, Reproducer
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: system-config-printer-1.4.1-23.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-31 19:43:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1709724, 1716960    

Description GV 2018-08-13 08:21:53 UTC
Description of problem:
system-config-printer does not start. The problem persist since rhel7.0.

# system-config-printer
/usr/share/system-config-printer/system-config-printer.py:31: PyGIWarning: GdkPixbuf was imported without specifying a version first. Use gi.require_version('GdkPixbuf', '2.0') before import to ensure that the right version gets loaded.
  from gi.repository import GdkPixbuf
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
/usr/share/system-config-printer/system-config-printer.py:33: PyGIWarning: Gdk was imported without specifying a version first. Use gi.require_version('Gdk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gdk
Traceback (most recent call last):
  File "/usr/share/system-config-printer/system-config-printer.py", line 76, in <module>
    import installpackage
  File "/usr/share/system-config-printer/installpackage.py", line 23, in <module>
    import glib
ImportError: No module named glib


Steps to Reproduce:
1. install rhel 7 minimal
2. install and start cups cups
3. install and run system-config-printer

Easy fix: require pygobject2 and pycairo.

Comment 2 Zdenek Dohnal 2018-08-13 10:38:03 UTC
Hi Gabriel,

thank you for reporting this issue! pycairo is already as require, but pygobject2 isn't. I don't have a minimal RHEL 7 install, but I achieved the same behavior when I uninstalled pygobject2.

I agree adding pygobject2 as Requires: fixes it.

Comment 4 Zdenek Dohnal 2018-08-13 10:44:57 UTC
Gabriel,

do you have active RHEL subscription? It would help us to prioritize the issue.

Comment 5 GV 2018-08-13 11:25:29 UTC
Hi.

My company have one. But it uses a different email address.


Sincerely,
Gabriel

Comment 6 Zdenek Dohnal 2018-08-13 11:33:22 UTC
Can someone in your company (who has an access to subscription and has account at access.redhat.com) file a customer case at access.redhat.com? Or would you mind telling us Red Hat customer account number of your company?

Comment 7 GV 2018-08-13 11:47:49 UTC
I have access to the subscription account. No problem here.

Still, I want this bug to be public. I really hate when I see the changelog for a package and I'm denied access to the details in bugzilla. If you can guarantee that the bug will remain public we can discuss about this. Thank you.

Comment 8 Zdenek Dohnal 2018-10-05 08:48:50 UTC
Gabriel,

would you mind sending your subscription number or creating customer case? It is needed for our support people.

Comment 9 GV 2018-10-05 09:04:13 UTC
If you __guarantee__ that the bug will remain public, yes.

Comment 10 Zdenek Dohnal 2018-10-05 09:38:47 UTC
Yes, the bug will remain public.

Comment 11 Zdenek Dohnal 2018-10-05 10:16:42 UTC
Gabriel,

I'm deeply sorry for mystification - I talked with colleagues with experience from support team and explained to me that only way to get this bug priority is to open customer case.

For information on how to contact the Red Hat production support team, please visit:
    https://www.redhat.com/support/process/production/#howto

Comment 12 Steve Bonds 2018-10-31 20:06:28 UTC
I also ran into this issue and opened RedHat case 02243588 on it.

A simple workaround:

# yum install pygobject2 pycairo

Comment 13 Zdenek Dohnal 2018-11-05 09:56:17 UTC
Thank you for opening the customer case, Steve! Now we can prioritize the issue!

Comment 16 Steve Bonds 2019-07-17 13:29:25 UTC
I see that a TestCaseNeeded flag was added. It seems like we have a fairly simple manual bug-reproduction process. What additional info is needed to create a test case?

Comment 33 errata-xmlrpc 2020-03-31 19:43:16 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://access.redhat.com/errata/RHBA-2020:1044