[jaunty post a-5] Printing is stuck to "processing"

[aldebx]

Upgraded from intrepid to jaunty today and ever since printing does not work any more.

I tried using both
Samsung ML-2010, SpliX V. 2.0.0 and
Samsung ML-2010, Foomatic/gdi

in both cases the printer state stucks to "Idle - Processing page 2..." although the job is just 1 page and 150k big (it's the test page - other documents are not printed as well).

This bug can be fixed by
1) accessing System -> Administration -> Printing panel
2) deleting the printer (rightclick -> delete)
3) adding the printer via Server -> New -> Printer (or using the New button), then proceeding through the wizard as usual.

Of course the upgrade should be more smooth.

Note that
1) keeping the old printer icon and simply changing the driver (which would supposedly update the driver in use) does NOT provide you with a working printer.
2) deleting the old printer icon and using the plung and play wizard (after you removed the old icon and plug in the usb printer cable a pop up should appear guiding you through the setup) does NOT provide you with a working printer.

[DanielRoesler (diafygi)]

I can confirm this bug. However, the workaround described does not work for me. I can add the printer just fine, but any print job gets stuck in "Processing". Deleting the printer and adding it again does not work. Currently, I am still not able to print. I am using a HP-LaserJet-1022.

[Rolf Leggewie (r0lf)]

please take a look at https://wiki.ubuntu.com/DebuggingPrintingProblems and execute "apport-collect 336902"

could this be a dupe of 336512?

[DanielRoesler (diafygi)]

In the past few days, the updates have fixed the problem. I can print regularly now. Can others confirm?

[Frank Bob (frankbob)]

I'm seeing the same bug in kubuntu jaunty.

printer is
Samsung ML-2510, SpliX V. 2.0.0

[Till Kamppeter (till-kamppeter)]

Frank Bob, the original poster wrote that his existing print queue had the problem and also a queue generated by Plug'n'Print (plug in the printer whjen there is no queue for it), but a print queue created by clicking "New" in system-config-printer and then following the wizard steps works.

So can you please create a print queue by clicking "New" in system-config-printer and then following the wizard steps, using a new queue name? Then you should have your old, already existing queue which does not work and a new one which works. Do

cancel -a
cupsctl LogLevel=debug

and then print one one-page file once into the new and once into the old queue. As soon as the job in the old queue gets stuck and the job in the new queue finishes printing do

sudo cp /var/log/cups/error_log ~
chmod 777 ~/error_log

and attach the ~/error_log file to this bug report.

[DanielRoesler (diafygi)]

I can confirm that this bug is still present in the Jaunty beta release.

[DanielRoesler (diafygi)]

I can confirm that this problem is fixed in Karmic 9.10 beta.

[Aisano (info-ais-sanmarino)]

I am experiencing this problem with a Samsung ML-1710, under Ubuntu 10.04 (something with "L") beta 2 (daily updates). The problem did not appear right after installing 10.04; I could print for several days. When I tried to print a PDF document (I had printed a similar one successfully before) the printer queue said "splix cannot read pixel line". Removing the job did not help. The message now is "processing page 2". (The document in question had 1 page.)

When I delete the printer in the CUPS console (system-config-printer 1.2.0) its title bar still displays "wird gedruckt" (= "printing" in German).

I will try to proceed as described above (remove the printer, then recreate it) but this will take some time as I have no idea how to find out the printer's "device URI". So at present I cannot tell if that fixes the problem.