Red Hat Bugzilla – Bug 508448
system-config-printer crash if root use it for managing printers
Last modified: 2009-06-29 07:22:27 EDT
Description of problem:
If root try to manage printers, application crash on final phase or show "permission deny" message.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open terminal (I use konsole under KDE)
2. su -
4. add new printer
5. confirm changing
Caught fatal exception. Traceback:
File "/usr/share/system-config-printer/system-config-printer.py", line 6501, in on_btnNPApply_clicked
device=uri, info=info, location=location)
File "/usr/share/system-config-printer/authconn.py", line 183, in <lambda>
return lambda *args, **kwds: self._authloop (fname, fn, *args, **kwds)
File "/usr/share/system-config-printer/authconn.py", line 198, in _authloop
result = fn.__call__ (*args, **kwds)
File "/usr/share/system-config-printer/cupspk.py", line 486, in addPrinter
File "/usr/share/system-config-printer/cupspk.py", line 230, in _call_with_pk_and_fallback
debugprint ('PolicyKit call to %s did not work: %s' %
NameError: global name 'debugprint' is not defined
All changes are commited. New printer is available for use.
user can manage printers by system-config-printer.
There are two problems here:
1. The traceback, which occurs when authentication fails. This is fixed in the system-config-printer package available in updates-testing and is tracked by bug #496722.
2. PolicyKit denies operations when requested by root. This is a PolicyKit issue and is tracked by bug #447266.
*** This bug has been marked as a duplicate of bug 447266 ***