[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Note that after having done the tests you have to apply the short- circuit workaround again in order to be able to print. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Sorry, I have given you the wrong cupsfilter command lines, so do exactly the following: Undo the short circuit for the following test doing sudo mv /usr/lib/cups/filter/pdftopdf.orig /usr/lib/cups/filter/pdftopdf It looks like that one of the filter produces broken PDF and the next filter (most probably cpdtocps which calls pdftops which in turn calls /usr/bin/pdftops and that one uses libpoppler as the PDF renderer). The errors and warnings in the error log show that libpoppler is complaining and not Ghostscript (Linux has two PDF renderers: libpoppler and Ghostscript). Let us run the filter chain stopping one step before cpdftocps: cupsfilter -m application/vnd.cups-pdf -p /etc/cups/ppd/yourbrokenqueue.ppd /usr/share/cups/data/testprint.ps output.pdf 2 error_log.txt Attach the two output files output.pdf and error_log.txt to this bug report. Does error_log.txt contain warnings or errors? Does output.pdf get created and is it not empty? Try to display output.pdf on the screen. Start with evince. Is it correctly displayed? Or does it show artifacts similar to your printouts? Try to display it with Ghostscript by running gs output.pdf Does this work better? Or does it show the same problems? Try also cupsfilter -m application/pdf -p /etc/cups/ppd/yourbrokenqueue.ppd /usr/share/cups/data/testprint.ps output2.pdf 2 error_log2.txt This leaves out the pdftopdf filter (so doing this test makes only sense if you did not short-circuit pdftopdf). Do the same steps as described above with the output files. Try finally cupsfilter -m application/vnd.cups-postscript -p /etc/cups/ppd/yourbrokenqueue.ppd /usr/share/cups/data/testprint.ps output3.ps 2 error_log3.txt This adds the execution of cpdftocps. Proceed with the output files as described above. For screen-displaying the output, use only Ghostscript: gs output3.ps Does this file display correctly? Note that instead of /usr/share/cups/data/testprint.ps you can also use any other PostScript or PDF file, but use the same file for all tests. Please attach all output* and error_log* files, also if you cannot display the files with Ghostscript and/or evince. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
I have just tried printing for the first time since updating to Intrepid. PowerPc TiBook G4 Latest Intrepid updates I get a few lines when trying to print a PDF but no text. I ran the troubleshooting and here's the output attached. I'll try the pdftopdf short circuit workaround and see if that helps. BTW, how to undo the workaround? ** Attachment added: troubleshoot.txt http://launchpadlibrarian.net/19653102/troubleshoot.txt -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Hmmm...tried to run the workaround this way. Is this right? seems weird $ sudo mv /usr/lib/cups/filter/pdftopdf /usr/lib/cups/filter/pdftopdf.orig [sudo] password for brianokeefe: [EMAIL PROTECTED]:/usr/lib/cups/filter$ ls commandtocanon hplipjspstopdf rastertogutenprint.5.2 commandtoepson imagetopdf pstops rastertohp commandtoescpx imagetops pstopxl rastertolabel commandtopclx imagetoraster pstoqpdlrastertopclx cpdftocps oopstops pstoraster rastertoqpdl cupsomatic pdftoijs pstoturboprint rastertoturboprint foomatic-rippdftopdf.orig rastertodymotextonly gziptoany pdftopsrastertoepson texttopdf hpgltopspdftorasterrastertoescpx texttops [EMAIL PROTECTED]:/usr/lib/cups/filter$ sudo cat /usr/lib/cups/filter/pdftopdf EOF #!/bin/sh cat \$6 EOF bash: /usr/lib/cups/filter/pdftopdf: Permission denied [EMAIL PROTECTED]:/usr/lib/cups/filter$ sudo cat /usr/lib/cups/filter/pdftopdf EOF #!/bin/sh cat \$6 sudo EOF chmod 755 /usr/lib/cups/filter/pdftopdf [EMAIL PROTECTED]:/usr/lib/cups/filter$ ls commandtocanon hplipjspstopdf rastertogutenprint.5.2 commandtoepson imagetopdf pstops rastertohp commandtoescpx imagetops pstopxl rastertolabel commandtopclx imagetoraster pstoqpdlrastertopclx cpdftocps oopstops pstoraster rastertoqpdl cupsomatic pdftoijs pstoturboprint rastertoturboprint foomatic-rippdftopdf.orig rastertodymotextonly gziptoany pdftopsrastertoepson texttopdf hpgltopspdftorasterrastertoescpx texttops -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
the short circuit got a complaint from test page printing that the pdftopdf file didn't exist. I moved the file back and the test page printed all of the color but no text on the page. PDF's did the same as before-a few lines but no text. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
The short-circuit filter did not get created for you. Do the following commands: sudo -s mv /usr/lib/cups/filter/pdftopdf /usr/lib/cups/filter/pdftopdf.orig cat /usr/lib/cups/filter/pdftopdf EOF #!/bin/sh cat \$6 EOF chmod 755 /usr/lib/cups/filter/pdftopdf exit Note that all commands between sudo -s and exit are executed as root (you have a prompt ending with #). Does your printing work correctly now? -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
If you get the same broken results as before after doing my pdftopdf short circuit, do not undo the short circuit for the following test. Otherwise, undo it with sudo mv /usr/lib/cups/filter/pdftopdf.orig /usr/lib/cups/filter/pdftopdf It looks like that one of the filter produces broken PDF and the next filter (most probably cpdtocps which calls pdftops which in turn calls /usr/bin/pdftops and that one uses libpoppler as the PDF renderer). The errors and warnings in the error log show that libpoppler is complaining and not Ghostscript (Linux has two PDF renderers: libpoppler and Ghostscript). Let us run the filter chain stopping one step before cpdftocps: cupsfilter -m application/vnd.cups-pdf -p /etc/cups/ppd/yourbrokenqueue.ppd output.pdf 2 error_log.txt Attach the two output files output.pdf and error_log.txt to this bug report. Does error_log.txt contain warnings or errors? Does output.pdf get created and is it not empty? Try to display output.pdf on the screen. Start with evince. Is it correctly displayed? Or does it show artifacts similar to your printouts? Try to display it with Ghostscript by running gs output.pdf Does this work better? Or does it show the same problems? Try also cupsfilter -m application/pdf -p /etc/cups/ppd/yourbrokenqueue.ppd output2.pdf 2 error_log2.txt This leaves out the pdftopdf filter (so doing this test makes only sense if you did not short-circuit pdftopdf). Do the same steps as described above with the output files. Try finally cupsfilter -m application/vnd.cups-postscript -p /etc/cups/ppd/yourbrokenqueue.ppd output3.ps 2 error_log3.txt This adds the execution of cpdftocps. Proceed with the output files as described above. For screen-displaying the output, use only Ghostscript: gs output3.ps Does this file display correctly? -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Thanks Till! The short-circuit filter got created and printing is working. Good job. (now to figure out why my key-mapping got screwed up...) -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Great. Thank you. So undo the short-circuit and do the tests of my last posting. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
I will do that but I have a question. Do I need to re-do the short circuit to print again? Here's what happened with the tests: None of the error_log.txt contain anything. The output.pdf and output3.pd fwill not open at all with any viewer. [EMAIL PROTECTED]:~/Desktop# gs output.pdf GPL Ghostscript 8.63 (2008-08-01) Copyright (C) 2008 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Error: /undefined in Usage: Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop 1904 1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- Dictionary stack: --dict:1148/1684(ro)(G)-- --dict:0/20(G)-- --dict:70/200(L)-- Current allocation mode is local Current file position is 7 GPL Ghostscript 8.63: Unrecoverable error, exit code 1 [EMAIL PROTECTED]:~/Desktop# gs output3.ps GPL Ghostscript 8.63 (2008-08-01) Copyright (C) 2008 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Error: /undefined in Usage: Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop 1904 1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- Dictionary stack: --dict:1148/1684(ro)(G)-- --dict:0/20(G)-- --dict:70/200(L)-- Current allocation mode is local Current file position is 7 GPL Ghostscript 8.63: Unrecoverable error, exit code 1 -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
After updating cups, I'm still affected by this issue. Also, now sending the test page to the printer results in 100% CPU usage until I don't cancel the printing job. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
after updating cups, still the same issue as I reported in (duplicate) bug #283605 -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
bhouchmandzadeh, please check whether your problem is bug 289759 and try the suggested fix (new pstopdf filter) there. Anyone else, please try this, too. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
I have the same problem, my network printer (Xereox Phaser 8400) stopped working after updating to 8.10 : after an attempted printing, I get the stopped message. the problem is probably due to some filters : I can use lp from command line and send pdf or text files to the printer and it works fine. From within cups however, printing test pages get the stopped message. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Alas, I'll have to wait for the cups 1.3.9-2ubuntu1 powerpc build to hit the intrepid-proposed archives before I can test... -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Sorry, I forgot to mention that the workaround pdftopdf does not work for me. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Mi problem is solved. It was a cartridge issue. Now mi printer works fine. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
jfyi, problem still present on todays intrepid packages (and maybe duplicate Bug #283605 contains some useful additional information...) -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
** Tags added: ppc -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
I got the same problem with a Pixma iP1800, my printer stopped working just after update to Intrepid. ** Attachment added: troubleshoot.txt http://launchpadlibrarian.net/18956750/troubleshoot.txt -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
I got the same problem with a Pixma iP4300, see the bug #286456, my printer stopped working just after update to Intrepid, with a Specified ColorSpace is not supported error. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Sorry for the delay, the printer was connected to a x86 machine for some time (it has *other* problems with that... like printing for a certain frame of time and then it says the printer is disconnected even if it isn't). Anyway, I got round to connect the printer back to the PPC machine, and this is the error log. Is the short-circuited pdftopdf file right to print the six parameter passed? It says D [06/Oct/2008:21:06:22 +0200] [Job 40] /usr/lib/cups/filter/pdftopdf: Exec format error Just guessing. Thanks! ** Attachment added: error_log http://launchpadlibrarian.net/18271286/error_log -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Sorry, the short-circuit filter was wrong. I have found it out when using it by myself to track down another bug. The right way to create it is sudo mv /usr/lib/cups/filter/pdftopdf /usr/lib/cups/filter/pdftopdf.orig sudo cat /usr/lib/cups/filter/pdftopdf EOF #!/bin/sh cat \$6 EOF chmod 755 /usr/lib/cups/filter/pdftopdf The dummy pdftopdf does only use the 6th parameter as input file name (and reads stdin if the 6th parameter does not exist). The first five are ignored, and therefore page management options (like number-up, page-ranges, ...) will not work. This way we can see whether the damage of the PDF data comes from pdftopdf or not. Please try also to update your system to the current state of Intrepid. Several bugs in the PDF filters got fixed. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Of course, it lacked the shebang! I should have thought about that myself. Anyway, now printing works, so it may very well be due to pdftopdf. By the way, printing a PDF from evince results in wrong paper margins, but I believe that's the job of pdftopdf, so I guess it is to be expected. My system is upgraded to all the latest packages (cups is at version 1.3.8-12). I'm attaching error_log just for the sake of completeness. ** Attachment added: error_log.txt http://launchpadlibrarian.net/18273760/error_log.txt -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Can you post the error_log with the short-circuited pdftopdf filter? -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Can you do the following: sudo mv /usr/lib/cups/filter/pdftopdf /usr/lib/cups/filter/pdftopdf.orig sudo cat /usr/lib/cups/filter/pdftopdf EOF cat \$6 EOF chmod 755 /usr/lib/cups/filter/pdftopdf This short-circuits the pdftopdf filter (page management filter). Can you try your jobs again now? Can you print correctly now? ** Changed in: cups (Ubuntu) Status: New = Incomplete -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Nope, no success. Nothing gets printed. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
** Changed in: cups (Ubuntu) Status: Incomplete = New -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Till can you have a look at this possible regression? Matteo, could you run the script referenced here to gather more information? Thanks. https://wiki.ubuntu.com/PrintingBugInfoScript ** Changed in: cups (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Till Kamppeter (till-kamppeter) Status: New = Incomplete -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
Can you start system-config-printer (System - Administration - Printing) and inside system-config-printer call Help - Troubleshoot in the menu? Go throgh the steps of the wizard to do printing tests with appropriate logging and recording of all relevant data. Attach the resulting file to this bug report. Attach also files which failed to get printed. -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
** Attachment added: printingbuginfo http://launchpadlibrarian.net/17735308/printingbuginfo -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
I had to cancel printing of test pages, because as you can see in the attached log it says there was an ubalanced at the trailing of input and 700 of pages were to be printed. So I stopped that. The stdin job is man -Tps pthread_create | lpr. The other job is from trying to print a page in evince. None of them worked (no pages printed at all). ** Attachment added: troubleshoot.txt http://launchpadlibrarian.net/17735397/troubleshoot.txt -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
** Attachment added: error_log http://launchpadlibrarian.net/17693426/error_log -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271350] Re: Printing stopped working after upgrade to Intrepid
** Tags added: regression-potential -- Printing stopped working after upgrade to Intrepid https://bugs.launchpad.net/bugs/271350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
