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: