Printer support broken (Feisty -> Gutsy upgrade)

Bug #138680 reported by Morten Siebuhr
10
Affects Status Importance Assigned to Milestone
cupsys (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

After upgrading from Feisty -> Gutsy, my printer would not print anything.

Whenever I would print something with lpr xxxxx.pdf, the notification-icon shows up, and the job is in the list. Likewise, the job appears with the lpq command.

After inspecting /var/log/cups/error_log (empty), I tried the printer-settings - where there were set no default printer and all printers had the "Enabled" unchecked. I enabled my printer and set it as default (which, by the way, unchecks the "enabled"-option...) and re-checked the "enabled".

Now it works like usual.

Revision history for this message
Vangelis Tasoulas (cyberang3l) wrote :

My HP Deskjet 840C Stopped working after dist-upgrade to gutsy.....

Revision history for this message
Brian Murray (brian-murray) wrote :

Vangelis - could you please add the full contents of your '/etc/cups/printers.conf' file as attachment to your bug report? Thanks in advance.

Changed in cupsys:
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

msiebuhr, which printer do you have? Can you post your /etc/cups/printers.conf?

Vangelis, your problem is most probably bug 147369. Please try the proposed fix presented there.

Revision history for this message
Vangelis Tasoulas (cyberang3l) wrote :

I have fixed my printer but let me explain exactly what it happened...
When I upgraded to gutsy, the printer was existed in the printer module of System Settings on my Kubuntu as it was installed on feisty, but I could not print at all.
The documents were entering on the queue but they would stay there forever.

By opening the hp-toolbox I could see my printer but the hp-toolbox was reporting the printer disconnected.
If I was removing it and added a new one from the hp-toolbox utility, it could find the printer on the usb connected. It was installing it (At least it was saying OK) but again the status was disconnected So I had the same behaviour with the final point: I Could not print.
After many tests with the hp-toolbox that I could`t fix the problem I used the printer module of System Settings. I removed the printer from the printer module and I installed it again.
After that the printer was fixed!

Now I can print flawlessly but the hp-toolbox reports that no printer is installed to my system at all!
I have no problem with that as even my cups printer server works fine for my other two network PC`s, but it`s just something that wasn`t happening on my feisty before.

I think that I have backed up my old (problematic one) printers.conf but you will have to wait for one/two days because we are painting the house inside, and my desktop PC is on the mess and I can`t open it :)

Revision history for this message
Vangelis Tasoulas (cyberang3l) wrote :

Now that I opened again the PC with the printer on it, I realized that I had erased the printers.conf :(

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Can you please do a complete update of your system

sudo apt-get update
sudo apt-get dist-upgrade

to get the latest version of HPLIP, then delete your printer with system-config-printer and turn it off and on again. Your printer should get reconfigured now. As soon as you get the appropriate desktop notification try to print.

Revision history for this message
Adam Barbary (home-adambarbary) wrote :

Am not sure if I have the exact same probelem, however I have lost all network printers since the upgrade. After the print command is issued, from any program, the print queue appears, the job is marked completed but not printing. I beleive it is a cupsys issue as I have downgraded the package on all machines and printing is now working again.

Joe

Revision history for this message
Muhammad Takdir (muhammad-takdir) wrote :

I think problem solved, Vangelis said "After that the printer was fixed!". So We can close this bug report. don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Revision history for this message
Muhammad Takdir (muhammad-takdir) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information. Thank you.

Changed in cupsys:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.