Hello Reuben,
Thank you for submitting this bug and reporting a problem with cups and 
printing.  You made this bug report some time ago and Ubuntu has been updated 
since then. 
                                                         
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once):                 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.                      

Thank you again for helping make Ubuntu better. 
G

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/368977

Title:
  System print config "forgets" printer status / settings on reboot

Status in CUPS:
  New
Status in Gnome Print:
  Incomplete
Status in System Config Printer:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete
Status in kubuntu-meta package in Ubuntu:
  Invalid
Status in system-config-printer package in Ubuntu:
  Incomplete

Bug description:
  I will update this bug the next time it happens. If anybody can
  suggest debugging information that would be helpful, I'll include it.
  So far, this has happened twice, both in very recent versions of KDE
  4.2 (Kubuntu 9.04; I was on the RCs).

  I have a Laserjet 8150. I try to print (e.g. from Firefox), choose the
  printer, and nothing happens. Then I look in the KDE printer applet,
  and it says the printer is unavailable, or busy, or...

  No combination of restarting the printer, clearing the print job
  queue, or restarting the computer seems to work. The only workaround I
  have is to go through KDE's printer configuration and remove/install
  the printer. After that, it works. My working theory based on this is
  that something about the printer config is being screwed up.

  Before a week or so ago, I never had this problem, and the printer
  worked reliably. So, it's a recent bug.

  At what point in the workflow I don't know. More information when I
  have it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/368977/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to