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
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
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 Ghostscrip
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-bug
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
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 t
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
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
http
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
c
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 help
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
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-bu
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, wh
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 ar
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
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 work
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 maili
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
Y
** 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.ubunt
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 Ubun
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 notif
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 syste
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 /
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
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 lis
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.co
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?
** 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
ubunt
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 job is "man -Tps pthread_create | lpr".
The other job is from trying to print a page in
** 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.
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 bu
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 (
** 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
ht
** 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
34 matches
Mail list logo
