This bug was fixed in the package system-config-printer -
1.3.1+20110222-0ubuntu8

---------------
system-config-printer (1.3.1+20110222-0ubuntu8) natty; urgency=low

  * debian/patches/35_set-connected-state-when-connecting-to-server-fails.patch:
    Set the "connected" state after a failure of connecting to CUPS, to
    avoid a runtime error (Red Hat bug 685098).
  * 
debian/patches/33_newprintergui-fix-traceback-with-self-printers-not-set.patch:
    New printer wizard crashes when adding a network (AppSocket/JetDirect)
    printer manually (LP: #734968, Red Hat bug #680683).
  * debian/patches/23_wait-for-cups-daemon-to-listen-after-sighup.patch,
    debian/patches/23_reconnect-automatically-on-cups-restart.patch:
    Replaced the patch to handle restarts of the CUPS daemon by the solution
    provided by upstream
    (https://fedorahosted.org/system-config-printer/ticket/219). Instead
    of waiting for the CUPS daemon coming back listening for a fixed timeout
    and only after that timeout showing the interface to handle the lost
    CUPS service, we show this screen immediately but in the background we
    listen to D-Bus signals of CUPS. If an appropriate signal appears, we
    cancel this interface immediately and show the CUPS queues again. So we
    can both manually switch to another CUPS server immediately in case of
    a total loss of the original CUPS server and do nothing and wait for
    the original server to come back.
 -- Till Kamppeter <[email protected]>   Wed, 16 Mar 2011 23:09:52 +0100

** Changed in: system-config-printer (Ubuntu)
       Status: In Progress => Fix Released

** Bug watch added: fedorahosted.org/system-config-printer/ #219
   https://fedorahosted.org/system-config-printer/ticket/219

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734968

Title:
  system-config-printer.py crashed with AttributeError in
  setNPButtons(): 'NewPrinterGUI' object has no attribute 'printers'

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to