Hide Forgot
Description of problem: system-config-printer executed in non-graphical environment throws a traceback: [root@rtt6 ~]# system-config-printer Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 30, in <module> from timedops import * File "/usr/share/system-config-printer/timedops.py", line 21, in <module> import gtk File "/usr/lib64/python2.6/site-packages/gtk-2.0/gtk/__init__.py", line 64, in <module> _init() File "/usr/lib64/python2.6/site-packages/gtk-2.0/gtk/__init__.py", line 52, in _init _gtk.init_check() RuntimeError: could not open display Version-Release number of selected component (if applicable): system-config-printer-1.1.16-17.el6.s390x How reproducible: always Steps to Reproduce: 1. login to a system using ssh -x username@name 2. run system-config-printer Actual results: traceback when running system-config-printer via ssh -x connection Expected results: User should see a human readable message, not any traceback, see system-config-lvm for example: [root@rtt6 ~]# system-config-lvm Unable to initialize graphical environment. Most likely cause of failure is that the tool was not run using a graphical environment. Please either start your graphical user interface or set your DISPLAY variable. Caught exception: could not open display
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
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. http://rhn.redhat.com/errata/RHBA-2011-1638.html