Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 208824 - system-config-printer doesn't support connecting to remote servers as a client
Summary: system-config-printer doesn't support connecting to remote servers as a client
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC6Target
TreeView+ depends on / blocked
 
Reported: 2006-10-02 08:00 UTC by Saikat Guha
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: 0.7.32-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-02 16:44:48 UTC


Attachments (Terms of Use)

Description Saikat Guha 2006-10-02 08:00:01 UTC
Description of problem:
Cannot use system-config-printer when cups is configured as a client to another
server. i.e. the following line in /etc/cups/client.conf:
   ServerName print.server.domain.edu

Starting system-config-printer with the above line results in:
[saikat@sioux ~]$ system-config-printer 

(system-config-printer.py:3459): libgnomevfs-WARNING **: Failed to open session
DBUS connection: Unable to determine the address of the message bus (try 'man
dbus-launch' and 'man dbus-daemon' for help)
Volume monitoring will not work.
Traceback (most recent call last):
  File "/usr/share/system-config-printer/system-config-printer.py", line 2413, in ?
    main()
  File "/usr/share/system-config-printer/system-config-printer.py", line 2404,
in main
    mainwindow = GUI()
  File "/usr/share/system-config-printer/system-config-printer.py", line 308, in
__init__
    self.populateList()
  File "/usr/share/system-config-printer/system-config-printer.py", line 380, in
populateList
    self.printers = cupshelpers.getPrinters(self.cups)
  File "/usr/share/system-config-printer/cupshelpers.py", line 213, in getPrinters
    printers_conf = PrintersConf(connection)
  File "/usr/share/system-config-printer/cupshelpers.py", line 293, in __init__
    self.parse(self.fetch('/admin/conf/printers.conf'), 'Printer')
  File "/usr/share/system-config-printer/cupshelpers.py", line 306, in fetch
    raise e
cups.HTTPError: 403


Without that line, system-config-printer starts up just fine. However, clicking
'Go to server' and entering print.server.domain.edu blocks the process forever
(no UI refresh, nothing; needs to be kill'ed).


The ServerName line in /etc/cups/client.conf works for FC5 and allows the local
cups daemon to be a client of print.server.domain.edu
In FC5, the printers shared at that location show up on the local
system-config-printer.




Perhaps unrelated, but the warning:
 (system-config-printer.py:3459): libgnomevfs-WARNING **: Failed to open session
  DBUS connection: Unable to determine the address of the message bus (try 'man 
  dbus-launch' and 'man dbus-daemon' for help)

doesn't look healthy either.


Version-Release number of selected component (if applicable):
FC6 Pre-Release

How reproducible:
Always

Steps to Reproduce:
1. Install FC6 Test
2. system-config-printer
  
Actual results:
Hangs when attempting to contact a remote cups client, or if the ServerName
directive is present in /etc/cups/client.conf then doesn't start.

Expected results:
system-config-printer must always start up whether or not the ServerName
directive is present in /etc/cups/client.conf. When the directive is present, it
must like the remote printers. clicking the go-to server button and entering the
name of the upstream server shouldn't lock-up the client.

Additional info:

Comment 1 Tim Waugh 2006-10-02 16:07:04 UTC
Should be fixed in 0.7.32-1.  Thanks for testing!

I don't know about the dbus message, but it is harmless.  system-config-printer
doesn't use dbus.


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