[Bug 1871377] Re: URW Nimbus font issue
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 Nimbus font issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/+bug/1871377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871377] Re: URW Nimbus font issue
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/+bug/1871377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871377] Re: 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: https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/+bug/1871377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871377] Re: URW Nimbus font issue
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 inclusion in a Ubuntu update). The font files (and metrics) here: https://ghostscript.com/~chrisl/afii10084-glyph-bug/ Thanks! -- 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: https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/+bug/1871377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
*** 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 "invalidaccess". It *looks* to me like this is an problem with pstops, or an incompatibility between the way pstops manipulates its input and how the Ghostscript/ps2write output works. Can I suggest you open a new bug? And (if you can) make sure I'm subscribed to it (or post a link to the new bug here). On the new bug, if you could attach (ideally) three files: the input to Ghostscript, the output from Ghostscript and the output from pstops. Also, include the command lines you have listed above. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688636] Re: Firefox gets stuck in a page fault
*** 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 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: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688636] Re: Firefox gets stuck in a page fault
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: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686568] Re: Firefox Does Not Respond. Process can not be killed. Terminal commands to kill the process freeze. Logout Freeze.
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 the OP in this seems to be using). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686568 Title: Firefox Does Not Respond. Process can not be killed. Terminal commands to kill the process freeze. Logout Freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1686568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688636] Re: Firefox gets stuck in a page fault
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 stuck in a page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438494] Re: ghostscript fails to correctly substitute cidf fonts
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. I'd guess that's because either the OCR function was disabled, or it simply could not recognise the handwritten characters. Anyway, as our 9.16 release fails with the same error as you saw (i.e. the error is not caused by the Ubuntu packaging), but the 9.18 release (which I assume is what you tested) works without error, I had a hunt, and found that the fix is this one: http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=668406a5 I would suggest, if you want the maintainer to pull in this patch, you *may* want to open a new bug report, referencing the above commit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438494 Title: ghostscript fails to correctly substitute cidf fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler-data/+bug/1438494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525225] Re: gs has issues with pdfs which only consist of large images
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 Ubuntu. https://bugs.launchpad.net/bugs/1525225 Title: gs has issues with pdfs which only consist of large images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1525225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1476705] Re: postscript printer hideously slow in some cases (pdftops)
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 Cairo - I know about the problems with the Cairo PDF output, as we've performance problems in Ghostscript with those, and have had some fairly lengthy (and heated) discussions with Cairo developers on the subject. And I have helped debug a lot of these problems with the Ghostscript output, so I can give general suggestions as I did above. If I had to guess, I would say that pdftocairo is possibly spotting that the PDF originated as a Cairo file, and is using inside knowledge of how those are constructed to convert it back into Cairo internal representation, which is then outputs to Postscript - with that level of extra information, it can probably be much, much smarter about when there is real transparency that it has to render, and when everything opaque, and remain in high level form. Whilst, pstops may be doing a simpler, one step PDF to Postscript conversion. Ideally, what you'd want to try is (if possible) to keep the ProRes (I thought it was ImageRET) mode, but still tell pdftocairo to use 600 dpi, as you then may get the benefits of more the accurate dot placement, better halftone results, and possibly better color management, whilst keeping the quicker processing of the smaller image data. It's hard to know without deep inside knowledge, but (again) if I had to guess, I would suggest that the slightly lower quality halftone screen is what's causing the slight intensity shift you mention. HP are pretty tight lipped about these technologies, but I know other such systems tend to allow the halftoning to represent more shades of the color, without losing detail (generally there is a trade off: you can approximate lots of shades, but lose detail, or have great detail, but very few shades). Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1476705 Title: postscript printer hideously slow in some cases (pdftops) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1476705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1476705] Re: postscript printer hideously slow in some cases (pdftops)
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 (and PDF transparency in particular) the only way to be sure that all the page contents are opaque would be to pre-process each page, checking for non-opaque content, and then re-interpret the page using the information gleaned in the first pass - which would, frankly, result in an unacceptable performance drop for the vast majority of PDF files. Most interpreters I know will pre-scan the quickly accessible elements of a PDF page, and if no transparency constructs are found, will then elide the extra processing transparency requires. Unfortunately, those easily accessible elements don't contain (or, at least, don't reliably contain) the actual opacity information. So, in most cases I know, just the existence of the transparency constructs means that extra processing is enabled, regardless of the actual opacity values. Now, secondly, Postscript cannot represent PDF transparency in high level (vector etc) operations. So, the only way to get a visually accurate representation of a PDF containing transparency in Postscript is to flatten the transparency by rendering it to a sampled image - and clearly, sampled images end up being larger than vector graphics. Hence we have the result that basically every Cairo produced PDF will convert to Postscript as one or more sampled images per page. And that explains why the Postscript is so much larger than the PDF. Now, looking at the Postscript file you posted, it *appears* that the rendering for transparency flattening is being done at 1200dpi which is, frankly, ridiculous for a couple of reasons. First is, your printer has a maximum physical resolution of 600dpi (the ImageRET modes provide enhanced quality, claimed to be equivalent to 2400 and, IIRC, 3600 dpi, but the printer is still a 600 dpi printer). Secondly, our experience with Ghostscript's Postscript output, is that many printers are much, *much* faster at upsampling images than downsampling. So, my first suggestion would be to poke around the CUPS dialogues and/or the PPD, and see if you can drop the claimed resolution of the printer to at most 600dpi and, frankly, I'd even try 300 dpi. As a rule of thumb, in the printing world, it's generally claimed that dropping continuous tone, sampled image resolution by 50% from the physical resolution results in almost no visible loss of quality. Where that falls down, in cases like this, is because there is text involved, and the small details inherent in text shapes may well suffer visibly. Another thing we've found with the Postscript output from Ghostscript is that many printers are very, very slow at decompressing data, so if you can find an option to avoid compressing image data, that *might* make a difference - but that is highly printer dependent. I'd like to take this opportunity to rant (again): this kind of thing is the reason that PDF is such poor, poor choice as a print spool format. PDF has a *hugely* rich imaging model, *far* more so than Postscript, PCL5/PXL or any of the proprietary page description languages (PDL), which means for almost any low/midrange PDL based printer, there is a very high chance that the PDF content cannot be converted to a high level, vector representation, and must be rendered and sent as sampled images (bitmaps). Perhaps a PDF/A or PDF/X variant would be a better choice.. And I'm sure someone will point out that more and more printers are supporting direct PDF printing, but that really just moves the bottleneck: PDF transparency is (over!) complex, and is extremely processor and memory intensive. So a low/mid range printer, with limited memory and processing power, is going to struggle to print a file like these ones. In truth, many such PDF printers get around this by either not supporting transparency at all, or supporting only relatively trivial subset of the full PDF transparency model. Also, with more and more applications integrating Cairo to do their PDF output, with the transparency problems outlined above, the situation is only set to get worse. /rant Anyway, as I said, look into adjusting the resolution, and possibly compression settings, and let us know how you fare. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1476705 Title: postscript printer hideously slow in some cases (pdftops) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1476705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438494] Re: ghostscript fails to correctly substitute cidf fonts
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'll probably be tweaking the capabilities of cidfmap at some point, which could, potentially, break poppler's use of these files. 2) the question of whether poppler will fall back to some other substitute CIDFont is moot since, if poppler *does* use those configuration files, it won't (normally) find the font files they reference anyway. So even if poppler does use them, splitting them off into a separate package and fixing the dependencies will work better for poppler, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438494 Title: ghostscript fails to correctly substitute cidf fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler-data/+bug/1438494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438494] Re: ghostscript fails to correctly substitute cidf fonts
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 cidfmap files in /etc/ghostscript/cidfmap.d/ and those (it appears) are used by the /usr/sbin/update-gsfontmap script (poor name, as it adds to the confusion that Fonts and CIDFonts are the same thing!), to update the *actual* cidfmap which is in /var/lib/ghostscript/fonts/cidfmap. It is not at all clear to me how the update-gsfontmap script gets run - possibly only as a package post-install step? The files in /etc/ghostscript/cidfmap.d/ are as follows (file name + TTF font(s) referenced): 90gs-cjk-resource-cns1.conf - ukai.ttc, uming.ttc 90gs-cjk-resource-gb1.conf - ukai.ttc, uming.ttc 90gs-cjk-resource-japan1.conf - fonts-japanese-mincho.ttf, fonts-japanese-gothic.ttf 90gs-cjk-resource-japan2.conf - ttf-japanese-mincho.ttf, ttf-japanese-gothic.ttf 90gs-cjk-resource-korea1.conf - NanumMyeongjo.ttf, NanumBarunGothic.ttf, NanumBarunGothicBold.ttf, NanumGothic.ttf NOTE: there is some inconsistency (possibly bitrot) there with fonts- japanese-*.ttf used in one file and ttf-japanese-*.ttf used in another - clearly the same font, but likely different generations of name. My two alternate solutions are that the Ghostscript package should be augmented to include the fonts listed above (with the names and paths updated to reflect the current directory tree etc) as dependencies, thus they always get installed with Ghostscript. *Or* to split off (I *think*) the files in /etc/ghostscript/cidfmap.d/ into something like a ghostscript-cjk-cidfonts package, which has those fonts listed above as dependencies (again with names and paths revised for a modern system). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438494 Title: ghostscript fails to correctly substitute cidf fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1438494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438494] Re: ghostscript fails to correctly substitute cidf fonts
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 available. Historically, Ghostscript has assumed that such system level configuration was correct, and did minimal error checking on them, thus by the time Ghostscript realises the font files are not available, it is too late to recover gracefully, and we have to error out. The most recent Ghostscript releases are more rigorous in that area, and should cope better. Nevertheless, it would be preferable if the fonts references in the mappings were made dependencies of the Ghostscipt package. *Or* remove those mappings altogether, as they are much less relevant since we now have a built-in CIDFont substitution in Ghostscript, using DroidSansFallback.ttf. A final suggestion would be to remove the mappings from the default Ghostscript package, and rely on the DroidSansFallback.ttf substitution, and move the existing mappings to a separate package which holds the mapping configuration, and depends on the packages containing the relevant font files. I feel the last suggestion would be the most desirable, since the DroidSansFallback.ttf substitution will work work just fine for the vast majority of people, who don't need to be forced to install a load of KANJI fonts, but allows the flexibility for those who genuinely need more accurate CIDFont substitution than simply falling back to DroidSansFallback.ttf. Finally, the generic mappings such as Adobe-Identity and Adobe- Japan1 should be removed altogether as, except in very rare circumstances, those should all fall through to the DroidSansFallback.ttf substitution. I can provide a complete list of those generic mappings if required. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438494 Title: ghostscript fails to correctly substitute cidf fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1438494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366743] Re: Ubuntu 14.04 only prints LibreOffice Docs
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366743 Title: Ubuntu 14.04 only prints LibreOffice Docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1366743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366743] Re: Ubuntu 14.04 only prints LibreOffice Docs
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, you can open the printout file in a text editor and look at the comments in the first 20 lines or so, and see whether it was created by Poppler or Ghostscript. Thanks I'll leave it to Till to decide whether to contact the appropriate Cairo/poppler folks. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366743 Title: Ubuntu 14.04 only prints LibreOffice Docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1366743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366743] Re: Ubuntu 14.04 only prints LibreOffice Docs
As the file you have is PDF, you should be trying: lpr -P printer -o psdebug file.pdf or lp -d printer -o psdebug file.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 that should give you a Poscript file which, hopefully you can then use the instructions to send unfiltered to the printer. If the printer does not print, then attach that Postscript file here, and we can hopefully start the (usually lengthy!) process of debugging it. OTOH, if sending the file unfiltered works (unlikely!) , tell us that, too. Finally, once you've done all that, as a workaround, you can do: lpadmin -p printer -o pdftops-renderer-default=pdftops and try printing. Again let us know whether that works, doesn't work, or whatever. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366743 Title: Ubuntu 14.04 only prints LibreOffice Docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1366743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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 experience have carefully reviewed it, found nothing incorrect (although, we both agree it is not how we would have written it!). So, again, I would urge you (Tomas) to contact Toshiba and report this as a bug - their interpreter is failing to interpret valid and logically correct Postscript. Anyway, back to our immediate concern. The issue can be worked around by adding the following to the Ghostscript command line (when called from CUPs): -dHaveTrueTypes=false -c /MaxFontItem 50 setuserparams -f input file What we have is the HaveTrueTypes setting which tells ps2write whether it should emit TrueType/Type42 fonts. Setting it to false means we convert the TTF outlines into bitmaps. This can happen in two ways: the bitmaps can be used to create a Type 3 Postscript font (this is preferred as it results in smaller file size, executes quicker on the target and often results in better quality output), or they are just normal image data in the PS. The choice between the two approaches is dictated by the value of MaxFontItem - any glyph larger than MaxFontItem will end up as normal image data, rather than in a Type 3 font. Hence, I included code to set the value of MaxFontItem quite high, meaning we'll use the Type 3 font approach as often as is reasonable - but I'm wary about setting it too high, as I don't want to trigger resource problems on the target printers. Till, this definitely should only apply to Toshiba printers (maybe just the Estudio range), and ideally, it would be good to set the resolution for Ghostscript to that of the target printer, or an integer division thereof: i.e. if the printer is 600dpi, you could reasonably set the resolution to 300dpi. It would preferable to avoid scaling by a non- integer value from both a performance and quality point of view. Any questions, just ask.. (although, I can't promise a good answer!) -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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 recommendation to Till about a workaround ** Attachment added: printout_testpage_noncompressed_chris_nottf_20140326.ps https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+attachment/4044333/+files/printout_testpage_noncompressed_chris_nottf_20140326.ps -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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 -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
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.ubuntu.com/DebuggingPrintingProblems#Getting_the_data_which_would_go_to_the_printer But there is no point in attaching the two sets of output since the Postscript from Poppler is totally different to the Postscript from Ghostscript, and thus there's no chance of using a comparison to help. Just attach the failing Postscript - but note the next paragraph I'm happy to work through the issue and track down the source of the problem, but it will mean a lot of hand editing of Postscript files by me, and having to rely on you to send them to the printer and report the results back to me (and possibly mean burning through paper, too). We can probably find a workaround for the problem *if* we can narrow it down. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
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.net/bugs/998087 Title: printer ERROR: invalidaccess OFFENDING COMMAND: filter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
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: invalidaccess OFFENDING COMMAND: filter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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 Ubuntu. https://bugs.launchpad.net/bugs/978120 Title: Toshiba Estudio 230 printer driver bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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. https://bugs.launchpad.net/bugs/978120 Title: Toshiba Estudio 230 printer driver bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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 interpreters from five different vendors all handle the original file without an error, so I assume this is a bug in the printer. Even if we can find a workaround, I would *strongly* encourage you to send a bug report to Toshiba about this - it is disgraceful that so many manufacturers are shipping PS printers that fail to interpret fairly basic Postscript, and I really feel we need to let them know it's just not acceptable! ** Attachment added: Properly uncompressed version https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+attachment/4040928/+files/printout_testpage_really_noncompressed_chris_20140324 -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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_noncompressed_chris_20140324_2 -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263415] Re: Kyocera FS-1100D cannot print Google Maps - limitcheck --image--
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, they have simply looked at the error message, and replied based on that. Valid Postscript adheres to a standard (written and published by Adobe), and whilst various companies have their own additional customisations, the core language must adhere to the standard or it is not valid Postscript. I have access to six different Postscript implementations: Adobe Distiller, Global Graphics Harlequin, Global Graphics JaWS, a Postscript implementation also from Kyocera(!!), Ghostscript (of course!), and with sufficient prior arrangement, Adobe CPSI. All the above run your file to completion without errors or warnings (including the Kyocera one). In addition, I've looked fairly carefully at the Postscript myself, and I see no problems with it. Based on the above, the Opera Postscript output is valid, correct Postscript, and the bug is with the printer. FWIW, I am quite happy for you to quote me on that, or even to follow up with Kyocera Germany on your behalf (assuming they can accept e-mails in English!). There is almost no point trying to compare the Postscript produced by different applications - Postscript is a turing complete programming language, as well as page description language, there are, therefore, an almost infinite number of totally different ways a given page can be represented. It's *highly* unlikely you (or anyone) will be able to look at the two sets of output, and pin-point the cause of the problem. The only way to narrow down the problem is, as I described before, for someone like me to hand edit the Postscript, progressively cutting it down, and possibly instrumenting it, so that you can try the each iteration on your printer, until we reach the one thing (or set of things) that causes the problem. It is a laborious process, that takes time, paper and toner, but it really is the only option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263415 Title: Kyocera FS-1100D cannot print Google Maps - limitcheck --image-- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1263415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263415] Re: Kyocera FS-1100D cannot print Google Maps - limitcheck --image--
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 likely a Kyocera problem, not an Opera (nor a CUPS) problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263415 Title: Kyocera FS-1100D cannot print Google Maps - limitcheck --image-- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1263415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
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 not). Or possibly the lighter PDF doesn't embed fonts, or doesn't embed as many or as large fonts. It's *really* impossible to guess without an awful lot of work from someone like me, and an awful of help from you to narrow down the printer's bug, and assess if there is a workaround. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263415] Re: Kyocera FS-1100D cannot print Google Maps - limitcheck --image--
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 output. In addition, PS is a Turing complete programming language, which adds another almost infinite range of possibilities! One thought springs to mind: does Opera allow you to change the Postscript printing settings? For example, does it allow you to select Language Level 2 instead of Language Level 3? Doing that might avoid the problem area for the printer. If it's helpful, I could help to narrow down the exact cause of the error, that might help a report to Kyocera, the Opera people produce a workaround, or maybe even find a workaround in cups. But a) that will need help, patience and paper from you (kniffte), and b) will have to wait until after the 6th Jan when I'm actually back at my desk (officially, I'm currently on vacation). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263415 Title: Kyocera FS-1100D cannot print Google Maps - limitcheck --image-- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1263415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263415] Re: Kyocera FS-1100D cannot print Google Maps - limitcheck --image--
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263415 Title: Kyocera FS-1100D cannot print Google Maps - limitcheck --image-- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1263415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263415] Re: Kyocera FS-1100D cannot print Google Maps - limitcheck --image--
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263415 Title: Kyocera FS-1100D cannot print Google Maps - limitcheck --image-- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1263415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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 the process through to a conclusion. If I had direct access to these printers, things would be much quicker, but that's not really practical, unfortunately. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1218350] Re: stackunderflow in .setdistillerparams
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: stackunderflow in .setdistillerparams To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1218350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1218350] Re: stackunderflow in .setdistillerparams
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 as part of the /printer PDFSETTINGS is that the PDFSETTINGS is a parameter (or set of parameters) for the pdfwrite device, whilst UseCIEColor is an interpreter parameter. -- 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: stackunderflow in .setdistillerparams To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1218350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
The file you attached in comment #71 definitely comes from Ghostscript (the meta-data comments at the head of the file show that), and not from poppler, so that was the configuration that gave you the error in 12.10. If you grab the attachment from #71, decompress/untar it, then do: lpr -P printer name -oraw printout With printer name being the name of the print queue for your Toshiba printer, and printout being the name of file - the -oraw ensures that will send the file directly to the printer, avoiding any regeneration by an application, and any additional filtering by cups. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
Laurent, Could you post the error message you get from that file, please? I'm a bit confused because the file you posted in comment #71 seems different to the ones I remember looking at before in this bug - it's *much* simpler, which is good, but I need to be sure where I should look before I start poking around. BTW, I'm going to be away from my office for a few days, so it will probably be next week before I can look in detail. Thanks, Chris -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072915] Re: brother hl-5240 problems after upgrade to quantal
Thanks. Hmm, the psdebug option is not working as I understood it - I *thought* it was supposed to produce very plain uncompressed, and (as far as possible) unfiltered output. But what you've got out of it is exactly the same as the non-psdebug output. Till, can you confirm (or deny) what psdebug should do? Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072915 Title: brother hl-5240 problems after upgrade to quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1072915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053443] Re: Unable to print to Konica Minolta C552DS printer - job history
On the BizHub unit referenced in the above Ghostscript bug, investigation by KonicaMinolta UK suggested that this was a firmware bug which has been addressed in the most recent revisions - I've yet to receive confirmation from the user on that, but KM were unable to reproduce the crash on their own test units with up to date firmware. The first step should really be to arrange a firmware update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053443 Title: Unable to print to Konica Minolta C552DS printer - job history To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1053443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072915] Re: brother hl-5240 problems after upgrade to quantal
Could you repeat the capture the data going to the printer stage after applying the psdebug setting to the testing print queue (that is, the new print you created to send the printer data to a file), and attach the output here, please? Could also confirm which version of Ghostscript is installed (gs -v will tell you)? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072915 Title: brother hl-5240 problems after upgrade to quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1072915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157814] Re: Xerox Workcentre doesn't print any more in Ubuntu 12.10 and newer
Till, I believe we've been through enough of these that you should know the basic groundwork required before I can really do anything. To start with, try the uncompressed CUPS option, and if that doesn't work, then gather the (preferably uncompressed) Postscript that is being sent to the printer to attach to this bug. Also, please include the instructions on how to send PS data direct to the printer (both netcat and the normal method). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157814 Title: Xerox Workcentre doesn't print any more in Ubuntu 12.10 and newer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1157814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157814] Re: Xerox Workcentre doesn't print any more in Ubuntu 12.10 and newer
Jeremy, Whilst we will investigate this, we are confident that the Postscript being emitted by Ghostscript is valid and correct, based on our own inspection of the Postscript code, and since it works correctly on a large number of devices. Given that, it seems almost certain that there is a bug in the Postscript implementation on this printer. As I said, we'll investigate, and hopefully find a workaround, but I would *STRONGLY* urge you, once Till posts instructions on how to gather the Postscript being sent to the printer, to report the problem to Xerox (including the problematic Postscript file in your report). On a printer of this spec and cost, there is no excuse for the Postscript interpreter being broken. I feel quite strongly on this: if Ghostscript fails to interpret valid Postscript or PDF (and even many, many invalid PDFs!) we are expected/obligated to fix Ghostscript - we would be berated heavily for suggesting that the producer be changed to work around our bug. I don't see why bugs in other consumers be treated differently. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157814 Title: Xerox Workcentre doesn't print any more in Ubuntu 12.10 and newer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1157814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157814] Re: Xerox Workcentre doesn't print any more in Ubuntu 12.10 and newer
Jeremy, Your next step should be to try doing: lpadmin -p printer -o psdebug=true where printer is the name of the Xerox print queue, and try printing normally. If that still gives the error on the printer, refer to: https://wiki.ubuntu.com/DebuggingPrintingProblems#Getting_the_data_which_would_go_to_the_printer And attach the result here. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157814 Title: Xerox Workcentre doesn't print any more in Ubuntu 12.10 and newer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1157814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157814] Re: Xerox Workcentre doesn't print any more in Ubuntu 12.10 and newer
Jeremy, If you don't mind, could you do me favour, and repeat the test print after doing: lpadmin -p test -o psdebug=true (assuming you called your file output queue test as suggested in Getting the data which would go to the printer), please? It's just it will save time if I don't have to manually decompress the file content. Thanks, Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157814 Title: Xerox Workcentre doesn't print any more in Ubuntu 12.10 and newer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1157814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
Once again, that is a PDF from the CUPS print queue, not the Postscript that is actually being sent to the printer. Note you are not supposed to be using the *default* configuration, you have to apply the settings from Till in post #57. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
Sorry, I know I'm repeating myself, but I'm *not* a CUPS developer (I work on Ghostscript), so I don't know the ins and outs of getting the data out of CUPS. Hopefully, Till will pipe up... -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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 we want/expect. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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://bugs.launchpad.net/bugs/978120 Title: Toshiba Estudio 230 printer driver bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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 generation from a Poppler based solution to a Ghostscript based solution - this was done to allow future use of high fidelity color reproduction, and some other features available in Ghostscript that were not going to be available in Poppler in the near future. As often happens with such a change, a few teething troubles have come up, hence Till allowed a fallback to the the Poppler tools while we work through them. The: lpadmin -p printer -o pdftops-renderer-default=pdftops setting is that fallback - it does not solve anything, at best it works around the problem. I am trying to establish what needs done to get the Ghostscript output compatible with your printer, so sending a file to the printer via CUPS with the poppler based filter in force does nothing to help me (or, ultimately, yourself!). *PLEASE*, when I give instructions for testing, do not ignore them - I write them for a reason... -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
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 printer name -oraw ko-nodebug-cut001.ps, since there is no problem' To me, that sounds like you didn't use lpr, but some other method, which is why I asked for clarification of how you printed the output. Sounds like there been some miscommunication, so if you ran the lpr test, and it worked okay, then I think we have all we need. I will ping Till tomorrow, and we'll get these Toshiba printers added to the exceptions list of printers that can't use the compression filter(s) in Postscript. Hopefully he can get a cups update out in the near future. Once that happens, you will need to do reset the cups filter to the default - I think this does it: lpadmin -p printer -R pdftops-renderer-default -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
Realy?!?!? I did *not* expect that. That suggests that there is a bug either with the LZW decode filter, or with that filter's interaction with other aspects of the interpreter. I have seen such things before. Thanks for testing it Marty. Okay, so if I can ask as many interested parties from this bug to download the file above (ko-nodebug-cut001.ps), and send it to your printers as described in coment #44, and report back, please? There is no need to change your cups configuration for this, just use the lpr command above. We have options in Ghostscript which will produce output the same as I manually created above, it just requires that Till add these Toshiba printers to the list of printers that use these options (they are not used as a default since some printers suffer unfeasibly poor performance without the use of the compression). Thanks again. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
Laurent. I'm afraid that https://wiki.ubuntu.com/DebuggingPrintingProblems#Capturing_print_job_data; is wrong, or at least misleading these days. What it captures is the file(s) from the cups print queue, which is printer independent (PDF, as a matter of fact), and not the final page description language that is sent to the printer - hence why I didn't just post a link to that page. I need the printer specific data. Chris -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
Huh, debug option doesn't do everything I thought it did - never mind, that gave me enough I could get what I need with a little manual hacking. First of all, your printer is broken!!! Four different Postscript interpreters, all from different vendors (include Adobe) all agree that this is valid, conforming Postscript, and interpret and render the file just fine. Thus, your first port of call really should be the printer vendor - the printer is faulty! Anyway, here is a version of the file with the same content as the Ghostscript one you supplied, but with all the compression removed: http://www.ghostscript.com/~chrisl/ko-nodebug-cut001.ps You need to send this to your printer using the following command: lpr -P printer name -oraw ko-nodebug-cut001.ps (the -oraw bypasses the cups filters, and sends the file straight through) Once you have done this, can you confirm (or otherwise) that ko- nodebug-cut001.ps still causes the same error on your printer as before. BTW, as this could be a protracted process, is there a preferable communications channel for you? E-mail, or whatever? Chris -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
Laurent, 1 - Erm, dunno! As I said, I just copied the instruction from a comment from Till on another bug. I don't know the best way to find which PPD your printer is actually using, but the PPD name *usually* reflects the make/model of the printer - for example, mine is HP- Officejet-h470.ppd. 2 - lpadmin -p printer -o pdftops-renderer-default=gs sets it back to the default. We also need: lpadmin -p printer -o psdebug as that disables various features which can a) fix the problem or b) make the problem easier (or even possible) to debug. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
Jacques, Did the: lpadmin -p printer -o psdebug=true have any effect? Also, can you try a different font from Ubuntu-Medium? Myabe one of the DejaVu ones if you have them. If we have to really debug this, it will take quite a bit of effort from both us (and possible a fair amount of paper!). Chris -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
What normally happens is that someone posts the Postscript that is sent to the printer from the Ghostscript workflow, preferably uncompressed by using the psdebug=true option. Ideally, in cases like this, also from the Postscript from the Poppler workflow. We then go through a process where I cut the Ghostscript file down bit- by-bit, and a willing volunteer sends my edited files to their printer, and tells me whether it fails or not. That way we find the smallest file that will fail. I may then have to instrument the Postscript to get further debug information back to narrow down *exactly* what causes the error, and hoepfully work out why - possibly by comparing it to the Poppler output. Although the Poppler output is often not directly comparable. Obviously this can be a tiresome process for everyone involved, and can take some time. Equally obviously, the simpler the file we start with, the better! Unfortunately, I can never remember how to tell CUPS to save the Postscript, instead of sending it to the printer. I'm not a CUPS guy. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
Aha, assuming nothing has changed, grabbing the printer PS can be done like this (originally from Till): cupsctl FileDevice=yes lpadmin -p test -E -v file:/tmp/printout /etc/cups/ppd/your printer's PPD.ppd Now print the job which failed on the printer test and as soon as the job disappears from the queue attach the file /tmp/printout to this bug report. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978120] Re: Toshiba Estudio 230 printer driver bug
dac922, Did you (or could you) try the: lpadmin -p printer -o pdftops-renderer-default=gs lpadmin -p printer -o psdebug As I understand it, the psdebug option disables a bunch of compression stuff in the Ghostscript output. It seems lots of printers have really bad decompression implementations :-( Thanks, Chris -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1042111] Re: gs can't render some fonts. Example was created with 10.04
It seems that the fix for this was: http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=8031fd57 For me (using git cherry-pick) the patch applies cleanly to the 9.05 sources. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042111 Title: gs can't render some fonts. Example was created with 10.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1042111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049635] Re: Cannot print a PDF on Kyocera Laser Printer
I've attached the result of printing the first page from Acrobat, through the KPDL Windows driver. It looks similar to the poppler output (it builds the clipping path using charpath operations). The Kyocera driver does, indeed, include a Print As Image option - although it comes out grayscale, for some reason. I can only assume that option is there to deal with cases like this one. ** Attachment added: Page 1 from the Kyocera Windows driver https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1049635/+attachment/3316099/+files/beispielrezepte-kyo-driver.ps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049635 Title: Cannot print a PDF on Kyocera Laser Printer To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1049635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049635] Re: Cannot print a PDF on Kyocera Laser Printer
Well, I think it's fair to say that if Kyocera's very own driver does not/cannot produce PS that the printer can interpret, it's not unreasonable that we don't. I'm not saying if there were a reasonable way for us to workaround the problem that we wouldn't, on that basis - but frankly, none of us can see a way to do that without taking ps2write away from it's intended purpose, which is to output as accurate a representation of the input as possible, within the limitations of the imaging models and the Ghostscript internals. I guess it's something to Till to consider, and discuss with the other cups devs: should there be a Print As Image option in cups? That option is in all the Windows Postscript drivers which I have access to, right now, so I have to assume it is included for a reason - and the only reason I can think of is cases like this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049635 Title: Cannot print a PDF on Kyocera Laser Printer To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1049635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049635] Re: Cannot print a PDF on Kyocera Laser Printer
No, we're not going to add that option to ps2write, that would, frankly, defeat the whole point of ps2write. There is already a cups imagetops filter, so it would be a lot less work to have the option have Ghostscript convert to pnm and then do imagetops on the pnm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049635 Title: Cannot print a PDF on Kyocera Laser Printer To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1049635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049635] Re: Cannot print a PDF on Kyocera Laser Printer
I'll need the exact Postscript being sent to the printer, and the command line invoking Ghostscript to create the 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/1049635 Title: Cannot print a PDF on Kyocera Laser Printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1049635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049635] Re: Cannot print a PDF on Kyocera Laser Printer
Okay, so we think we know the source of the problem. All the text in the PDF is drawn with text rendering mode 7, which means add to clip. So drawing the text accumulates an enormous path, which is then use to clip. Hence the limitcheck error on clip. Now the Ghostscript ps2write output (for some architectural reasons) simply emits the accumulated path, and drops the fonts from the output. The poppler output retains the fonts, and uses the Postscript charpath operator to create the path which it then uses to clip. So, the question is: does the poppler output work? There really should be no difference in the complexity of the path that Ghostscript emits explicitly, and the one that poppler creates via charpath, by the time the clip operator gets called. There is a small chance that Ghostscript could be changed to also emit the fonts and use charpath for this class of file, but it would be a lot of work, and rather pointless if it still won't work. It's possible that the answer is simply: the Postscript resulting from that PDF is simply too complicated for your printer to handle. So, in conclusion, can we test the poppler output? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049635 Title: Cannot print a PDF on Kyocera Laser Printer To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1049635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049635] Re: Cannot print a PDF on Kyocera Laser Printer
Frankly, that's what I feared. The Adobe produced Postscript can be made to resemble either the Ghostscript output or the poppler output (depending on the settings used in Acrobat), and it looks to me as though this is simply a case where the (mostly minor) differences in the imaging capabilities of PDF and Postscript result in a Postscript file with a very long path. In such cases, limited resource printers are going to struggle. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049635 Title: Cannot print a PDF on Kyocera Laser Printer To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1049635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049635] Re: Cannot print a PDF on Kyocera Laser Printer
I can't see any way to reproduce the page description accurately without running into the same problem. IIRC, some Windows Postscript drivers have the option to produce the page as an image, which I believe is intended to work around this type of issue. Thus reducing the PDL complexity, for such limited printers, at expense of comms traffic. I'm intrigued by Till's results with the HP because, as I stated above, the path(s) in question, whether they are explicitly described in the PS, or result from character outlines are equivalent in complexity at the time the printer executes the clip operator. I would expect it to always be slow, because making marks through such a hugely complex clipping path is a very time consuming operation. Sorry the news isn't better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049635 Title: Cannot print a PDF on Kyocera Laser Printer To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1049635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026974] Re: Printing Bahn ticket with gs backend takes 6:03 minutes on Kyocera 1350DN
I'm relieved to put another issue to bed! BIG thanks to Felix for his patience (and paper!) in helping us track this down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026974 Title: Printing Bahn ticket with gs backend takes 6:03 minutes on Kyocera 1350DN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1026974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026974] Re: Printing Bahn ticket with gs backend takes 6:03 minutes on Kyocera 1350DN
Right, again with much help from Felix, we're narrowed the problem down
to the fact that the images in the originating PDF request
interpolation, thus so does Ghostscript's Postscript output, and it
seems that, for the class of image in question, at least, the 1350D's
implementation of interpolation is unacceptably slow.
There may or may not be a future enhancement in GS to control whether it
preserves the interpolation requestion, but for now, at least, the
quickest solution would be to add bit more to the Postscript workaround
CUPS already prepends to PS for these Kyocera printers.
Augmenting the existing workaround as per below, improves the speed to ~12
seconds for the job in question:
%%BeginProlog
% = Workaround insertion by pdftops CUPS filter =
% Kyocera's PostScript interpreter crashes on early name binding,
% so eliminate all binds by redifining bind to no-op
/bind {} bind def
% Some Kyocera printers have an unacceptably slow implementation
% of image interpolation.
/image
{
dup /Interpolate known
{
dup /Interpolate undef
} if
systemdict /image get exec
} def
% =
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026974
Title:
Printing Bahn ticket with gs backend takes 6:03 minutes on Kyocera
1350DN
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1026974/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
For tracking the Ghostscript end of this, see: http://bugs.ghostscript.com/show_bug.cgi?id=693197 ** Bug watch added: Ghostscript (AFPL) Bugzilla #693197 http://bugs.ghostscript.com/show_bug.cgi?id=693197 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
sigh Again, I really didn't expect that :-( http://www.ghostscript.com/~chrisl/printout-004.ps That one should (on a fully functional printer) produce no output at all - not even a blank page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
Felix joined us on #ghostscript and with his help, I narrowed the problem down to the fonts in the file. The way ps2write currently works is that it writes a pfb (binary encoded Type 1 Postscript font) and ASCII85 encodes it so the binary data doesn't trip up the communications channels. The Kyocera printer here seems unable to cope with the pfb font data, it seems to require it in pfa (ASCII encoded Type 1 Postscript font). We'll investigate solutions, and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
Felix, First of all, (and I may have told you this before, but I would like it recorded in this, and all relevant bugs): this is *not* a bug with the Ghostscript Postscript output. The GS Postscript is valid - we spent a lot of time confirming that when these bugs started to come to light. The fault is with the printer, and the problem really should be reported to Kyocera. Even if they can't fix it in printers in the field they should be able to debug the problem directly on the printer, rather than the kind of arm's length reverse engineering we'll have to undertake. If we're going to track down the problem it will probably involve many interations of me instrumenting the Postscript file, you running the revised PS, and telling me the result. However, based on past experience, tells me to look at compression filters first, and the only one left in there was LZW. So, as a first punt, can you try: http://www.ghostscript.com/~chrisl/nolzw.ps IMPORTANT: it must be send directly to the printer (not opened in evince or other viewer, and printed from there - that would lose all my changes!). So you need to use: lpr -P printer name -oraw nolzw.ps There is also a method using netcat but I cannot remember the details.. If you can try that, and let us know the result. Thanks, Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
Darn it! Sorry, I forgot I needed to add the device specific stuff to the file. http://www.ghostscript.com/~chrisl/nolzw2.ps Should be more what we want apologies again. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
Okay, so it is not a problem with the LZW filter. That still leaves another (non-compressing) filter that could be at fault, but I'll try to narrow things down a bit before we get to that. On that basis, I'll work on modifying the version with the compression, since it's a lot smaller (obviously!). http://www.ghostscript.com/~chrisl/printout-002.ps Please use the same method to send that to the printer. All I have done in this one is add a blank first page. The reason for this is to narrow down whether the error is happening during the prolog of the file, or during the actual marking operations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
Felix, by the way, if there is a more convenient way of communicating for you than using launchpad (e-mail or IRC or something) then let me know. I can summarise progress on the problem here as required. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
Hmm, I did *not* expect that :-( If you can try this one: http://www.ghostscript.com/~chrisl/printout-003.ps In this one I have removed all the ps2write marking content, and replaced it with just a blank page. If IRC would be easier, I'm on #ghostscript on freenode most days (I'm on UK time) - my nick is chrisl. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
I can't find a gs command line anywhere in the logs. Could someone post the command line cups gives to GS these days? Perhaps that could be added to the cups logging? Also any PS that gets prepended. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
Oh, it looks like this is one of the printers we opted to disable page stream compression, but IIRC, Till, you put in user controls to allow disabling of font compression - that might be a good place to start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
I'll need the Postscript that gets sent to the printer, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1025061] Re: Kyocera FS-1300DN cannot print with gs backend
Felix, that's the poppler emitted PS (which is useful, I would probably have asked for it down the line anyway), but I really need the PS generated by Ghostscript, if you could thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025061 Title: Kyocera FS-1300DN cannot print with gs backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1025061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
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 printer name -o raw stream1-uc2.ps This changes the how the font data is encoded (note, for any Postscript afficianados reading this: it doesn't change the font's Encoding array). Again, please post your result. ** Attachment added: pfa font version https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+attachment/3152259/+files/stream1-uc2.ps -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
Steve, Could I ask you to send this file (stream1-uc.ps) to your printer, please? It is the same content as your original, but with the compression removed. You need to use: lpr -P printer name -o raw stream1-uc.ps If the HP in question is your only only, or your CUPS default printer, you can probably leave out the -P printer name option. The most important thing to note is the -o raw option, as this will cause the test to be streamed to the printer exactly as it stands - we don't want it going through the normal CUPS workflow (and thus changing the Postscript), in this case. If you can let me know the result. Thanks, Chris ** Attachment added: No compression version https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+attachment/3150232/+files/stream1-uc.ps -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
Steve, Till is looking into the possibility of providing an option to use the poppler tool as a workaround, I'll leave it to him to update on that when/if he has news. Obviously, in the long term, we'd like to resolve these issues that various printers have with the Postscript output from Ghostscript - note that Adobe CPSI consumes the GS output just fine, as does Adobe's Distiller, and several other Postscript interpreters. If I could ask you to attach a Postscript file here on which your printer gives this error - hopefully, Till can post the instructions on how to do that. After that, if you are willing, I'd like to give you some (possibly many!) Postscript files to send to your printer, to see if we can establish for sure what the problem is - if we can. Chris -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
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 PDF) output from Ghostscript. I seem to remember that there is a comment in the ps2write code to the effect that some filters on HP printers erroneously always close their underlying data source (closing it should be optional). I can't think of any other way for a call to create a decode filter to produce an invalidaccess error. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
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 to compile C code that is demonstrably compliant with the C89 spec (for example), is that the fault of the coder who wrote the failing code, or a bug in gcc? None of the issues that have arisen so far have highlighted any problem with our Postscript output. And did poppler's output always just work, or did they go through similar issues, possibly over a longer period? -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950713] Re: Brother printer fails to print anything but a blank page
Not being over sensitive, but: What is discussed here is the broken postscript code that makes Brother printers to fail completely. The Postscript is *not* broken, it is demonstrably valid. But it hits a breakage in the Brother printer - the problem is with the printer, not the Postscript. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950713 Title: Brother printer fails to print anything but a blank page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/950713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980616] Re: Printing Deutsche Bahn ticket on Kyocera PS printer takes 5 minutes (regression to 11.10)
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 look, and create some tests to *possibly* help track down the problem. Also, can we confirm *exactly* the command line being used to drive Ghostscript in this case (sorry, but with all the changes recently, I've slightly lost track!). Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980616 Title: Printing Deutsche Bahn ticket on Kyocera PS printer takes 5 minutes (regression to 11.10) To manage notifications about this bug go to: https://bugs.launchpad.net/libcairo/+bug/980616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980616] Re: Printing Deutsche Bahn ticket on Kyocera PS printer takes 5 minutes (regression to 11.10)
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 include the device specific settings - that way we can try different options to Ghsotscript, without having to create new CUPS packages for every option to test. I'm somewhat hopeful that fixing the error with Till's PDF will also address the performance problem with yours. Till, Is there a method to inject Postscript into the CUPS workflow at the point that Ghostscript would normally have created the PS? (I'm just wondering if there is an easier method for testing that me hand editing the printer specific stuff into the Postscript, and having the user nc it to the printer). Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980616 Title: Printing Deutsche Bahn ticket on Kyocera PS printer takes 5 minutes (regression to 11.10) To manage notifications about this bug go to: https://bugs.launchpad.net/libcairo/+bug/980616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980616] Re: Printing Deutsche Bahn ticket on Kyocera PS printer takes 5 minutes (regression to 11.10)
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 stuff added, and CUPS related workarounds added, and then sent to the printer. It would save me having to hand edit all the Postscript files to add the PJL, the bind workaround, the PPD settings and such to every test job we try. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980616 Title: Printing Deutsche Bahn ticket on Kyocera PS printer takes 5 minutes (regression to 11.10) To manage notifications about this bug go to: https://bugs.launchpad.net/libcairo/+bug/980616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977912] Re: Kyocera FS1320D needs resolution set in ghostscript filter
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 resolution of the target printer. It gives the user the option of I want the best quality, however long it takes, I want it as fast as possible, and damn the quality or something in-between. So, in a similar manner, it might be good to allow users to specify the flattening resolution (passed to Ghostscript) independently of the printer resolution (default behaviour would obviously be as it works now). You could even do something like High (current behaviour), Medium (flattener resolution == printer res / 2), Low (flattener res == printer res / 3), or Custom (allowing the user the specify their own flattener resolution). As mentioned above, this is a *feature* suggestion/request for your consideration, not a bug report. It's just something that occurred to me might be useful for a future CUPS release. Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977912 Title: Kyocera FS1320D needs resolution set in ghostscript filter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/977912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980616] Re: Printing Deutsche Bahn ticket on Kyocera PS printer takes 5 minutes (regression to 11.10)
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 hand editing :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980616 Title: Printing Deutsche Bahn ticket on Kyocera PS printer takes 5 minutes (regression to 11.10) To manage notifications about this bug go to: https://bugs.launchpad.net/libcairo/+bug/980616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
