*** This bug is a duplicate of bug 978120 ***
https://bugs.launchpad.net/bugs/978120
Hi Christian,
So, my impression, from what you've described is that this isn't the
same issue as the others in this bug (not least because the Postscript
error is different: "typecheck" rather than "invalidac
We've had an update from URW++ and the glyph in question looks much
better to me, but not being a speaker/reader of any language(s) that use
that glyph, it would be great if the OP would be willing to check the
update before I commit and push it to our github repo (then Till can
pick it up for incl
I should note, these will be the "upstream" source repositories, not the
Ubuntu ones (that will take a bit longer).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871377
Title:
URW Nimbus font issue
Super, thank you. I'll update the relevant repositories later today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871377
Title:
URW Nimbus font issue
To manage notifications about this bug go to:
I've pushed the fixes fonts to:
https://github.com/ArtifexSoftware/urw-
base35-fonts/commit/c15105598aa7eb256b1ebfcecd3d078801521e73
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871377
Title:
URW
Sorry, but the file attached above (GoogleMapsPrintout.ps) appears to be
a direct export from Opera (the metadata has: "%%Creator: Opera"),
rather than the Postscript captured as detailed here:
https://wiki.ubuntu.com/DebuggingPrintingProblems#Getting_the_data_which_would_go_to_the_printer
--
Yo
Okay, that's what we need to see, thanks.
However, that Postscript comes from Opera, not from Ghostscript, so I'm
not really the upstream contact.
As far as I can tell, that's valid Postscript, so the problem is a bug
in the printer - it should really be reported to Kyocera.
--
You received thi
Again, that all points to the bug being in the printer. The fact you can
convert the PS to PDF is a strong indication that the PS is correct (as
per the PS specification).
Don't forget that both PDF and PS are vector formats, so have nearly
infinite variations in how to produce (near) identical ou
Okay, so it's clear that the Toshiba has an issue with how we handle
TrueType/Type42 fonts - I know I'm repeating myself, but the Postscript
is *totally* correct, many other interpreters from many source handle it
happily, and both myself and another engineer with a great deal of
Postscript experie
Tomas,
Thanks for taking the time to report it to the manufacturer (not many
users do!).
If I'm honest, I doubt you'll get much response (based on past
experience), but as I said before, I think we need to start making it
clear to printer makers that these broken implementations aren't
acceptable
Would it be fair to guess is this same as, or related to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1686568
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688636
Title:
Firefox gets stu
FWIW, I see the same symptoms with both Firefox and (just now)
Thunderbird, and I am using the Nouveau NVidia drivers - I mention that
as I seem to recall a vaguely similar sounding issue a couple of years
ago that could be worked around why switching away from the NVidia
proprietary drivers (which
It probably needs an admin - hopefully, they'll see it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688636
Title:
Firefox gets stuck in a page fault
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1686568 ***
https://bugs.launchpad.net/bugs/1686568
** This bug has been marked a duplicate of bug 1686568
Firefox Does Not Respond. Process can not be killed. Terminal commands to
kill the process freeze. Logout Freeze.
--
You received this bug notific
It looks like the poppler pstops tool defaults to 300 dpi, compared to
Ghostscript's ps2write's 720dpi. Normally, this would not matter (both
will always try to preserve scalability whenever possible), but when
flattening transparency, the resulting image is created at the requested
resolution. Bot
Till,
It is confusing why using the "native" resolution doesn't result in the
fastest printing.
Some thoughts (based on some experience with Kyocera products): there
may be some extremely poor buffer management going on, meaning that the
larger amount of data causes this kind of slow down.
Secon
After a *lot* of help from a user of the Kyocera printers which *seem*
to have the same problem, we've come up with a *possible* solution -
although, note that the Kyocera printer showed a different symptom: it
froze.
But, anyway, could someone with the Brother printers seeing this problem try
th
Richard,
Thanks for trying it. It's a shame it didn't work..
This is a bit of a long shot, but I've "instrumented" a simple PS file,
if you (or someone) wouldn't mind sending it to the printer with nc
(sorry, but without access to the actual printer, it's a bit of stabbing
in the dark):
http
Richard,
Thanks, that was helpful, but confusing. Here's another file for you to
try. It will print a series of "here xx" statments in column, can you
tell me what the last number "xx" is?
http://www.ghostscript.com/~chrisl/nearly-empty-ps2w-02.ps
Some other questions:
I understand some of the
Richard,
So, the line immediately after the "here 5" print is attempting to
retrieve the currently defined halftone for the printer. I wonder if
Brother have some "clever" halftone tech that they hobble the
currenthalftone operator..
This is the same test file as above, but with the line tryi
Folks,
A user joined us on IRC, and helped me further narrow the problem.
It turns out the Brother printers really do seem to dislike the
currenthalftone operator - but instead of giving an error, which is the
"correct" thing to do, it just chokes and spits the page out.
So we have the core of t
So, I looked at the logic in the Postscript prologue, and I may have
been a bit pessimistic in my assessment above - it really depends on how
"clever" Brother have been in their implementation of this
"feature".
Once again, can someone/anyone run this file:
http://www.ghostscript.com/~chrisl/prin
That's great, thanks for all the help, especially from Robert and
zanaga, really appreciate it.
Till,
I'm afraid it's a 3 lines, rather than just the one this time - to get
this working, I prepended the following to the file:
/currenthalftone {//null} bind def
/orig.sethalftone systemdict /seth
Till,
Yes, directly after the "%!..." line is fine.
In fact, if you can, it would be nice if you could include an extra
comment just before these additions (for this and the Kyocera bug) with
a note about why the extra lines are there - it might save come
confusion debugging future issues.
Chri
Bruce (or anyone else with the problem),
We *think* it might be a problem Type 3 fonts. I'm going to attach five
modifed Postscript files to this bug, please use the command mentioned
above:
lpr -P MFC-8680DN -oraw printout-uncompress-.ps
to send each directly to the printer.
Please tell us whi
** Attachment added: "printout-uncompressed-01.ps"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/93/+attachment/2874466/+files/printout-uncompressed-01.ps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment added: "printout-uncompressed-02.ps"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/93/+attachment/2874467/+files/printout-uncompressed-02.ps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment added: "printout-uncompressed-03.ps"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/93/+attachment/2874468/+files/printout-uncompressed-03.ps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment added: "printout-uncompressed-05.ps"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/93/+attachment/2874471/+files/printout-uncompressed-05.ps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment added: "printout-uncompressed-04.ps"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/93/+attachment/2874469/+files/printout-uncompressed-04.ps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Ian,
Still guessing here (this is possibly going to be *much* harder to track
down than the previous one).
This *should* disable the font glyph cache, so please try this
file..
Thanks,
Chris
** Attachment added: "printout-uncompressed-nocache.ps"
https://bugs.launchpad.net/ubuntu/+sou
Ian,
Can we just clarify what you meant when you said:
"All of them printed out 2 pages on my HL5250DN printer using the
Brother-HL-5250DN BR-Script3 driver."
There should not be any "driver" involved, these Postscript files should be
streamed directly to the printer. I just want to make sure
And a second method of disabling the glyph cache..
Please try this one, too.
** Attachment added: "printout-uncompressed-nocache-02.ps"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/93/+attachment/2875899/+files/printout-uncompressed-nocache-02.ps
--
You received this bug noti
Ian,
Thanks. And thanks for the clarification about sending the file - I'm
not doubting your testing, I'm just *stunned* by these results!
Can you just confirm that in *all* these tests so far the "header" part ("File:
/home/bruce" etc, and the horizontal rule) has bee present in all of the
Folks,
I ran out of time today, but I will have some more tests to try
tomorrow.
Chris
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/93
Title:
12.04 Beta 1: Brother MFC8680DN cannot print text
Bruce,
The PDF contains a CIDFont which, when coverted via Ghostscript's
ps2write device is converted in one (or more) Type 3 fonts - this is
because, as the name suggests, ps2write outputs Level 2 Postscript, and
CIDFonts are a Level 3 feature. I would assume that the PS the mail
client emitted w
Hi,
Thanks! It looks like I uploaded the wrong job, hence the second one
giving an error.
But the fact that we can reproduce the problem with my entirely hand-
coded Postscript is good - that will be much easier to experiment with.
We've shown the problem is with Type 3 glyphs with image masks i
That is very odd. I flipped the A glyph bit map upside down, so I would
have expected *some* difference to appear.
Two things: has anyone thought to take this up with Brother? *Loads* of
other interpreters work just fine with this Postscript, and whilst we're
willing accept the problem is with the
Richard,
Can you try this one:
http://www.ghostscript.com/~chrisl/brother-nofont-03.ps
Chris
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/93
Title:
12.04 Beta 1: Brother MFC8680DN cannot prin
Bruce,
See comment #10 from Till.
Chris
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/93
Title:
12.04 Beta 1: Brother MFC8680DN cannot print text file
To manage notifications about this bug g
Richard (or anyone else interested),
It seems astonishing that these *basic* Postscript capabilities are this
buggy on the printer!
Anyway, by way of another elimination:
http://www.ghostscript.com/~chrisl/brother-nofont-04.ps
On a *functional* Postscript interpreter, that prints 3 "A" character
Bruce,
Woohoo! Finally, some progress! The garbled third character in brother-
nofont-04.ps was the one with the naked binary, so the binary data
probably got mangled en-route to the printer. And brother-
npfont-04-nobin.ps only had the two characters in it.
*So*, it looks like the problem is wit
Hi Guys,
As promised, more tests to try.
This file is made from the original PDF attached above, nothing has been
cut out or modified in the *page content*. The Postscript differences as
described:
First has the glyph bitmaps uncompressed:
http://www.ghostscript.com/~chrisl/nocompression.ps
Sec
Bruce,
That is, indeed, progress.
The good news is that we now know exactly where the problem lies, and
what we can do work around it. The less good news is that there is no
way to achieve that without patching Ghostscript and the CUPS workflow.
I believe (although it's not my area of responsibi
The problem, I suspect, is the way Cairo rights PDF files (the gmap.pdf
file you attached above was created by Cairo). The Cairo *always* writes
the page contents into one or more PDF transparency groups - even when
all the contents are really opaque.
The issue is that, due to the way PDF works (a
Bruno,
To be honest, I don't know what differs between the two tools, as they
both come from Cairo, I assumed that pdftops was just a small wrapper
around the same code as pdftocairo but with the options pre-set for PS
output.
I'm a Ghostscript developer, so I can't really answer specifics about
Two things:
1) I *really* don't understand why Ghostscript configuration file are
being installed by poppler. It would be worth finding out how (and even
if) poppler actually uses them, because I rather feel poppler and
Ghostscript configurations *should* be separate. For example, if I get
time, I
Apologies, Till, for the delayed reply - I *thought* replying on a bug
also subscribed me to it, but clearly not! (I have subscribed now).
There is a bit of guess work here, as I don't fully understand the file
locations.
We are mainly concerned with the cidfmap file. Now, there is a set of
cidfm
The root problem here is that the Ubuntu package contains cidfmap
mappings that provide substitutions for various CIDFonts that may not be
embedded in incoming files. But the Ghostscript package does not depend
on the package(s) containing those font files, so those font files are
often not availab
That is the correct behaviour. Previous versions ignored the error, and
produced the incorrect output.
This is not a bug..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218350
Title:
stackunde
I should add that the previous bug was with without "UseCIEColor"
pdfwrite could not access/create device independent colours, hence was
emitting a PDF with device dependent colours despite the
"UseDeviceIndependentColor" setting.
The reason UseCIEColor has to be set explicitly, and can't be done
After a *lot* to-fro testing (and a lot patience and help from
Maximilian!), we've finally narrowed down the problem, and it is not a
simple resolution issue.
It seems that the Kyocera printer is having issues when the data filter chain
looks like:
ASCII85Decode->LZWDecode->ASCII85Decode
Which i
Steve,
Thanks for trying that, it's eliminated the compression filters as being
the problem.
Before I resort to "instrumenting" the Postscript, which will use up
paper, can you try this file, please?
Again, like this:
lpr -P -o raw stream1-uc2.ps
This changes the how the font data is encoded (
Bruce,
Thanks, that's good (well, sort of!). It appears, and I am guessing
here, that the printer has problems with certain conbinations of filter
- in particular, it seems that it has trouble, either when multiple
compression filters are chained, or multiple instances of the same
filter are in th
Already e-mailed to Till, but I made a mistake above, and the command
line options were:
-dNoT3CCITT -dEncodeMonoImages=false -dEncodeColorImages=false
So page and font streams get compressed, but Type 3 font bitmaps, mono
images and color images don't get *additional* compression.
Chris
--
Yo
> Is this the definitive solution now? Should I release cups-filters
1.0.8?
I just can't answer that. We're working around a bug in a version of the
Brother Postscript implementation, with no access to the internals of
the interpreter. My *best guess*, based on the testing we've done, is
that ther
Hi Vincent,
Thanks for the independent confirmation, I *really* appreciate it.
Chris
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/960666
Title:
12.04 Beta 1 : Brother MFC8680DN does not print ima
Vincent,
I'm very relieved to hear that your other files are working, too, thanks
for trying them.
On both these bugs, I have urged people to contact Brother technical
support, and report these problems, but no one seems willing. I feel
there is little point in myself or Till doing it, because Br
Bruce,
Thanks for the confirmation.
As far as reporting to Brother is concerned, there is no need to mention
that it worked printing from Ubuntu 10.10.
Basically, take one of the Postscript files that we established fail on
the printer, and tell Brother you have a Postscript file that fails to
w
I've done three tests, based on the investigations we've done:
1)
http://www.ghostscript.com/~chrisl/brother/a_line_of_text.ps
This test *should* print "A line of text" at the bottom left of the page, but
instead simply ejects a blank page, apparently with no error indicated.
We narrowed the pro
1)
http://www.ghostscript.com/~chrisl/brother/a_line_of_text.ps
This test *should* print "A line of text" at the bottom left of the page, but
instead simply ejects a blank page, apparently with no error indicated.
We narrowed the problem down to line 202 (it seems to be the "currenthalftone"
ope
2)
This should print two fairly large bitmap images of the upper case character
"A", about halfway up the page, one next to the other. From the description I
received from those that ran similar tests previously, I think on the Brother
you should see one "A" and next to it something like "_ _" -
As I mentioned, I posted the three files, with individual descriptions,
as attachments here (rather than linked to my web space, and risk them
disappearing).
See post #25 for my summary of what should be in a report to Brother.
If anyone needs more info, wants clarification, or if Brother come ba
3)
(This is quite big - 2.4Mb)
This contains two instances of the image from the test file for this bug
(#960666). If this behaves the same as the original file, you should get one
image printed correctly, and then an error (the actuall error may well be
different to the originally reported one,
Bruce,
That gives you two files you can go to Brother with, and Vincent can
reproduce the compressed-image-test.ps problem, so Brother will get a
report about that.
The "a_line_of_text.ps" test result is odd: the error message you've got
there *looks* like bytes from an encoded stream - but there
Rijk,
PDF can contain CIDFonts, but Postscript Level 2 cannot (CIDFonts are a
Postscript Language Level 3 feature). ps2write is a Level 2 output
device (hence "2" is ps2write).
So ps2write is *removing* the CIDFonts and (I think) "flattenning" them
to multiple "normal" fonts, but in doing so, all
As there is no transparency, no shaded fills and no CIDFonts in this
file, there is nothing which is really affected by changing the
resolution for ps2write.
Given the error observed above, I would guess this is another filter
problem.
If Felix can attach the PS from Till's test PDF, I can take a
Felix,
The main thing is, I need the PS that actually gets sent to the printer
so that I can get the device specific settings that are inserted by CUPS
(and are not present in the "bare" Ghostscript output). Then I can
create variants of the PS from Ghostscript, and "hand patch" the
Postscript to
Till,
Sorry, that's not quite what I meant by "inject Postscript". What I was
hoping for was a way to bypass the PDF print queue (PDF is *so*
unsuitable for that!), so that an end user can take Postscript directly
out of Ghostscript and push it into the CUPS "back end" to have the PPD
derived stuf
What we were talking about is, if you look in Acrobat Pro, in the dialogue for
creating Postscript, it has a drop down menu titled "Transparency Flattener
Preset" which has the options "High Resolution", "Medium Resoluiton" and "Low
Resolution". Those options are totally independent of the resol
Till,
AIUI,
lpr -o raw ...
Is just a passthrough direct to the printer, so I *still* have to
manually edit *every* test file to get it to work on the printer.
If it's the pdftops filter that adds (at least some of) the printer
specific stuff, then I'll assume there's no way for me to avoid the h
I can't answer that.
I can say that Ghostscript's ps2write output is valid Level 2 Postscript
- in other words, it is compliant with the language defined in the Adobe
Postscript Language Reference Manual Edition 2. And not especially
challenging Postscript, either.
Let me ask this: if gcc fails t
Steve,
Yes, Ghostscript has replaced poppler, mainly due to the color
management now available in GS, which currently only applies to printer
drivers which use raster output - rather than ones like yours that use
Postscript. Ultimately, the improved color management will apply to
Postscript (and P
Your file contains neither fonts nor CIDFonts, it is simply one big
image. Whilst it is common practice for scanner produced PDF to use OCR
to overlay the scanned image with non-marking characters (obviously,
being non-marking, the actual font used does not really matter), this
file does not do so.
The problem is already fixed in 9.18. If wanted to apply the fix to the 9.16
code in Ubuntu 15.10, you can pull the patch from:
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=668406a5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Odd, that "printout" file is from the cairo/poppler "pdftops" filter,
rather than the Ghostscript one that I deal with.
If you can repeat the tests after running:
lpadmin -p HP-Color-LaserJet-2550 -o pdftops-renderer-default=gs
And post your results and another "printout" file. If you want to, yo
Sorry, but that "printout" file is still the Poppler created one.
I'm afraid I'm going to need Till's input on this as my knowledge of
cups is limited (and now exhausted) - I only really do the Ghostscript
end of things..
--
You received this bug notification because you are a member of Ubun
If I am correct, and (like the cases we've hacked around with the Ghostscript
output) the Postscript is perfectly valid and correct,
you may find that the Opera developers aren't willing to change that perfectly
valid Postscript output to work around a bug in a printer.
Really this is very like
Sorry, I haven't spoken, read or written German since I was at school!
But Google translate did a good enough job to get the idea of what they
said and, frankly, I strongly disagree with what they say.
What they have written implies that they have not actually analysed the
Postscript you have sent
I'm confused: my understanding was that this bug was resolved.
Besides, the thread seems to have become rather convoluted and confused.
If a problem is still occurring, could you open a new bug (subscribe me
so I see it), and we'll take things from there, please?
--
You received this bug notifi
Till, you know I can't answer that. For the issues we're looked at *not
one* has actually highlighted any issue with Ghostscript's Postscript
output, the Postscript has *always* been valid and correct.
There's simply no way I can guess at what bugs other interpreters may or
may not have.
--
You
Oh, and no need to apologize - we all want to get this stuff working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998087
Title:
printer ERROR: invalidaccess OFFENDING COMMAND: filter
To manage
PDFs are vector format (with the option embed raster graphics "images"
in them) so they don't have an inherent resolution.
It's more likely that a "light" PDF doesn't have images, or other
"advanced" PDF features, that need converted into something else (PDF
supports features that Postscript does
Tomas,
As this bug was reported as a problem with a HP LaserJet 4050, for which
a fix has been released, I would ask you, please, to open a new bug, and
subscribe me (cliddell) to the new bug, and we'll work forward from
there.
The instructions of what to do are here:
https://wiki.ubunt
Tomas,
if you're getting the same "invalidfont" error as reported in #978120,
then we can continue with that bug, if your error is different, I'd
prefer a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Yes, that's probably the "subset prefix" - it's six random letters that
differentiate a complete font from a subset font.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998087
Title:
printer ERROR:
Okay. so the next thing I'll ask you to do is to try step 10 from this section:
http://tinyurl.com/p5cb4kf
And see if that works better, and if not, attach the non-compressed
file.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hmm, that's not producing a non-compressed file - hopefully, Till will
pipe up to tell us what's going wrong (as mentioned elsewhere, I'm not a
CUPS guy, I'm a Ghostscript guy.).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
OKay, I have "manually" decompressed the various parts of the contents
of the file (you'll note it is now double the size!). If you could
follow the procedure to send this file directly to the printer (-oraw)
and let me know the result. Thanks.
Note that, once again, five different Postscript int
Tomas, can you try this one, too, please - same procedure.
FWIW, I'm expecting this to fail in the same way as the previous one.
** Attachment added: "Cut down file"
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+attachment/4040998/+files/printout_testpage_really_noncomp
Hrm, that's not a surprise, but it is a pain. I need to give this some
thought.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978120
Title:
Toshiba Estudio 230 printer driver bug
To manage noti
Tomas,
Can you give this one a try, and tell us how it behaves, please?
Thanks
** Attachment added: "Uncompressed file with no ttf font"
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+attachment/4043114/+files/printout_testpage_noncompressed_chris_nottf_20140325.ps
--
So, it is *definitely* to do with how ps2write emits Type42/TrueType
fonts - that's a pain. As I said before, what ps2write does is slightly
ls odd for this, but it *totally* standard Postscript.
Anyway, can you try this one, too, please? Depending on the result of
this, I can make a recommendatio
As the file you have is PDF, you should be trying:
lpr -P -o psdebug .pdf
or
lp -d -o psdebug .pdf
If that works, let us know.
If not, you need to follow the instructions starting here:
https://wiki.ubuntu.com/DebuggingPrintingProblems#Getting_the_data_which_would_go_to_the_printer
And then
Frank,
We've made changes to address problems with Konica-Minolta printers, but
you may have found another problem.
We know how to track these problems down, but they take a lot of time
and effort (and paper!) on the part of the users as well as us, and so
far, no one has seemed willing to see th
> Does this info help to narrow down the problem ?
No, it does not.
If you run the test I posted in comment #44 and report the results, that
*would* help narrow down the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
So, how are you printing the PS file in post #44 if not with the lpr
command?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978120
Title:
Toshiba Estudio 230 printer driver bug
To manage notificati
Opening the file in Document Viewer and printing it from there is
completely useless in context because it just goes through the CUPS
filters, which I specifically said we needed to avoid for this test.
Your original problem, as reported, came about as a result of changing
the CUPS Postscript gene
Jacques,
Sorry, but I don't see anywhere above that you confirmed that the test I asked
for in post #44 worked for you. In fact, you said (post #51):
'So I do not need to do "lpr -P -oraw ko-nodebug-cut001.ps",
since there is no problem'
To me, that sounds like you didn't use lpr, but some oth
Laurent,
If you follow Till's instructions above, and do:
lpadmin -p printer -R pdftops-renderer-default
lpadmin -p printer -o psdebug-default=true
Then do whatever you did in post #43 to capture the data being sent to
the printer, and then post it here again.
Then I can check the result is what
1 - 100 of 155 matches
Mail list logo
