http://permalink.gmane.org/gmane.linux.debian.printing hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.linux.debian.printing/3470 <pre>pplied this fix, too. Thank you very much. Commit: 1149c245e Till </pre> Till Kamppeter 2013-06-19T13:28:22 http://permalink.gmane.org/gmane.linux.debian.printing/3469 <pre> Hi Till, Thank you! I just checked the mainsteream git and it seems that the bug was propagated by copy&amp;paste even further: l.618 /* support colord and the "color-management=off" option */ l.619 device_inhibited = colord_get_inhibit_for_device_id (getenv("PRINTER")); This place should be reworked as well in exactly the same way: snprintf (tmpstr, sizeof(tmpstr), "cups-%s", getenv("PRINTER")); device_inhibited = colord_get_inhibit_for_device_id (tmpstr); Regards, Alex </pre> Alexey Galakhov 2013-06-19T13:11:39 http://permalink.gmane.org/gmane.linux.debian.printing/3468 <pre>I have applied the two patches now in Ghostscript's upstream GIT repository, commit #1b87b820. Thank you very much for the bug report and the patches. Till </pre> Till Kamppeter 2013-06-19T13:02:31 http://permalink.gmane.org/gmane.linux.debian.printing/3467 <pre>Package: ghostscript-cups Version: 9.05~dfsg-6.3 Followup-For: Bug #712045 Dear Maintainer, The current testing version (9.05~dfsg-6.3) is affected too. </pre> Alexey Galakhov 2013-06-19T11:54:22 http://permalink.gmane.org/gmane.linux.debian.printing/3466 <pre>Applying of the previous patch resulted in regression. Sometimes colord returns empty ICC filename which results in ghostscript failure. In this case no ICC option could be used. The attached patch fixes this. </pre> Alexey Galakhov 2013-06-19T11:33:38 http://permalink.gmane.org/gmane.linux.debian.printing/3464 <pre>Control: tags -1 +moreinfo Le mardi, 18 juin 2013 21.05:56, Adrian a écrit : Please follow the procedure outlined in https://wiki.ubuntu.com/DebuggingPrintingProblems [0] and attach the /var/log/cups/error_log file to the bugreport. Please also detail your exact setup with more details: what file did you try to print, on which cups server (local, distant), towards which printer (manufacturer, model), connected how (USB, Parallel, network, …), using which driver? Thanks in advance. OdyX [0] That we should really adapt to Debian and push to the Debian wiki, but that's another story. </pre> Didier 'OdyX' Raboud 2013-06-19T07:38:05 http://permalink.gmane.org/gmane.linux.debian.printing/3463 <pre>Package: cups Version: 1.5.3-5 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Squeeze-&gt;Wheezy upgrade. Done on 2 machines - both have the same problem now * What exactly did you do (or not do) that was effective (or ineffective)? Recreated printer, reinstalled CUPS, connected locally (instead over ipp) * What was the outcome of this action? Nope. Get-Printer-Attributes returned server-error-internal-error Unable to get printer status. * What outcome did you expect instead? That I'll be able to print. </pre> Adrian 2013-06-18T19:05:56 http://permalink.gmane.org/gmane.linux.debian.printing/3462 <pre>Filed upstream bug #694360 http://bugs.ghostscript.com/show_bug.cgi?id=694360 </pre> Dominique Brazziel 2013-06-18T16:55:42 http://permalink.gmane.org/gmane.linux.debian.printing/3461 <pre> Try https://wiki.ubuntu.com/DebuggingPrintingProblems </pre> Bastien ROUCARIES 2013-06-18T16:31:51 http://permalink.gmane.org/gmane.linux.debian.printing/3460 <pre>Processing commands for control-61a8vm9lEZVf4u+23C9RwQ&lt; at &gt;public.gmane.org: Bug #689084 [libcups2-dev] libcups2-dev is not Multi-Arch compatible There is no source info for the package 'libcups2-dev' at version '4.2-1' with architecture '' Unable to make a source version for version '4.2-1' No longer marked as fixed in versions 4.2-1. Bug #589084 {Done: Jonathan Nieder &lt;jrnieder-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt;} [bash] bash: basename variable: PS1="\W \w " in /boot reports "bott /boot" Bug #590052 {Done: Jonathan Nieder &lt;jrnieder-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt;} [bash] bash: Incorrect treatment of \W in prompt Bug #615880 {Done: Jonathan Nieder &lt;jrnieder-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt;} [bash] broken prompt (\W) for "/boot" Bug #647600 {Done: Jonathan Nieder &lt;jrnieder-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt;} [bash] PS1=\\W reports "pocc" for /proc Marked as fixed in versions bash/4.2-1. Marked as fixed in versions bash/4.2-1. Marked as fixed in versions bash/4.2-1. Marked as fixed in</pre> Debian Bug Tracking System 2013-06-18T16:00:16 http://permalink.gmane.org/gmane.linux.debian.printing/3459 <pre>Processing commands for control-61a8vm9lEZVf4u+23C9RwQ&lt; at &gt;public.gmane.org: Bug #689084 [libcups2-dev] libcups2-dev is not Multi-Arch compatible There is no source info for the package 'libcups2-dev' at version '4.2-1' with architecture '' Unable to make a source version for version '4.2-1' Marked as fixed in versions 4.2-1. Stopping processing here. Please contact me if you need assistance. </pre> Debian Bug Tracking System 2013-06-18T15:57:08 http://permalink.gmane.org/gmane.linux.debian.printing/3458 <pre>Le mardi, 18 juin 2013 14.10:38, Klaus Ethgen a écrit : Common-sense is still not the same as "just review and apply the patch that someone provided in the bugreport". Apparently it's not that easy common- sense: noone produced a patch for this issue yet. Sure. But it works. I am yet to see a bug _in_cups_, that was due to UTF-8. You're putting words in my mouth: I don't ignore that there are other encodings around, and didn't write that at all, please re-read my quote above. Cheers, OdyX </pre> Didier 'OdyX' Raboud 2013-06-18T13:19:59 http://permalink.gmane.org/gmane.linux.debian.printing/3457 <pre>Thanks, Brian. I played with TitlePref and cost factor just now. And use strings pdfoutputfile | grep Title to see anything interesting. After processing a tmp.c under 4 different conditions, I got the following results: - - /Title(tmp.c) 【TitlePref 0, cost factor 65】 - /Title(tmp.c) 【TitlePref 1, cost factor 65】 - /Title(\(\(stdin\)\))&gt;&gt;endobj 【TitlePref 0, cost factor 66】 - /Title(\(\(stdin\)\))&gt;&gt;endobj 【TitlePref 1, cost factor 66】 It seems as long as cost factor is 66, argv[3]=stdin. Changing TitlePref apparently can't help me any. Xiaolin -- 王晓林 On Tue, Jun 18, 2013 at 7:20 PM, Brian Potkin &lt;claremont102-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt;wrote: </pre> 王晓林 2013-06-18T13:05:42 http://permalink.gmane.org/gmane.linux.debian.printing/3456 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am Di den 18. Jun 2013 um 12:56 schrieb Didier 'OdyX' Raboud: Well, it is common sense to use iconv to produce output for every locale. Non-UTF-8 systems are not that uncommon. And UTF-8 is introducing new problems that you do not have with latin charset as there are byte combinations that drives your system cracy if it is set to UTF-8. So, no, UTF-8 is no solution for all problems. And just the fact that "it works" doesn't mean that it works good. But I cannot force you to solve the bug. But I think, it would be sad if you ignore the fact that there are other encodings around. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen &lt;Klaus-AFvVKsdj98azQB+pC5nmwQ&lt; at &gt;public.gmane.org&gt; Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQGcBAEBCgAGBQJRwE47AAoJEKZ8CrGAGfas3YsL/0V3ULW/nDuXuQ3JDqh6uBp4 l4dBWLyX</pre> Klaus Ethgen 2013-06-18T12:10:38 http://permalink.gmane.org/gmane.linux.debian.printing/3455 <pre>Your message dated Tue, 18 Jun 2013 13:56:36 +0200 with message-id &lt;201306181356.37946.odyx-8fiUuRrzOP0dnm+yROfE0A&lt; at &gt;public.gmane.org&gt; and subject line Re: Bug#520786: Localicing error has caused the Debian Bug report #520786, regarding Localicing error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner-61a8vm9lEZVf4u+23C9RwQ&lt; at &gt;public.gmane.org immediately.) </pre> Debian Bug Tracking System 2013-06-18T12:00:04 http://permalink.gmane.org/gmane.linux.debian.printing/3454 <pre>Your message dated Tue, 18 Jun 2013 13:54:34 +0200 with message-id &lt;201306181354.36215.didier.raboud-YMbw1J0jHOM&lt; at &gt;public.gmane.org&gt; and subject line Re: Bug#652817: Cannot print pages in reverse has caused the Debian Bug report #652817, regarding Cannot print pages in reverse to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner-61a8vm9lEZVf4u+23C9RwQ&lt; at &gt;public.gmane.org immediately.) </pre> Debian Bug Tracking System 2013-06-18T11:57:11 http://permalink.gmane.org/gmane.linux.debian.printing/3453 <pre>Hi Frank, Please provide the complementary informations asked below: Le mercredi, 21 novembre 2012 08.02:01, Don Armstrong a écrit : Can you try with a recent cups too (up-to-date Wheezy would be nice)? Thanks in advance, cheers, OdyX </pre> Didier 'OdyX' Raboud 2013-06-18T11:35:36 http://permalink.gmane.org/gmane.linux.debian.printing/3452 <pre>Your message dated Tue, 18 Jun 2013 13:30:37 +0200 with message-id &lt;201306181330.39254.odyx-8fiUuRrzOP0dnm+yROfE0A&lt; at &gt;public.gmane.org&gt; and subject line Re: Bug#581075: cups: bashism in /bin/sh script has caused the Debian Bug report #581075, regarding cups: bashism in /bin/sh script to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner-61a8vm9lEZVf4u+23C9RwQ&lt; at &gt;public.gmane.org immediately.) </pre> Debian Bug Tracking System 2013-06-18T11:33:14 http://permalink.gmane.org/gmane.linux.debian.printing/3451 <pre> This is a very sound argument and, after all, you are only reverting to the way Squeeze deals with PostScript files sent to cups-pdf. However, I just wanted to tidy up a loose end or two, so thanks for confirming that PDF quality does not depend on cost factor. And thank you for the level of detail you have provided during discussion. Always getting _stdin_.pdf results from a combination of a number of things. In the first place the name originates from the method used by Emacs to send the file to CUPS. Then CUPS simply processes the file in a normal and, as far as I can tell, non-buggy, way. We see this in your error_log: D [13/Jun/2013:10:44:42 +0800] [Job 102] argv[3]="(stdin)" argv[3] is the job title and is used on the command lines of pstopdf, pdftopdf and pdftops. If TitlePref is 1 in /etc/cups/cups-pdf.conf then argv[3].pdf becomes the output filename. For a TitlePref of 0 (the default) the output filename is taken from %Title in the PostScript file received from CUPS *after filtering by p</pre> Brian Potkin 2013-06-18T11:20:54 http://permalink.gmane.org/gmane.linux.debian.printing/3450 <pre>Le mardi, 18 juin 2013 10.17:15, Didier 'OdyX' Raboud a écrit : Grepping the output of 'nm -D' in a wheezy chroot showed that the following packages in Wheezy use symbols that move to libcupsfilters1 in unstable (cups- filters does use most of them, not listed here): printer-driver-c2esp: /usr/lib/cups/filter/c2esp 'cupsDitherDelete' 'cupsDitherLine' 'cupsDitherNew' 'cupsLutDelete' 'cupsLutNew' So printer-driver-c2esp uses some symbols from libcupsfilters1, but only depends on libcupsimage2 in Wheezy. I does depend on libcupsfilters1 in both Jessie and Sid. What do you think? Is there a way to untangle this circular depends by adding a breaks somewhere? Cheers, OdyX </pre> Didier 'OdyX' Raboud 2013-06-18T09:32:14 http://permalink.gmane.org/gmane.linux.debian.printing/3449 <pre>Le dimanche, 9 juin 2013 15.08:12, Bill Allombert a écrit : Indeed, it's a transfer of symbols without SOVERSION bump. I don't particularily like it, but it's there… Fair enough, but the dependencies ensure that dpkg is only happy with the two libraries installed at the same time, so the window of brokenness opportunity is quite small. What package do you have in mind? As for the symbols I don't know (but could probably given more work), but these reverse dependencies (from other source packages) are in place in Wheezy: libcupsimage2-dev ← libgs-dev libcupsimage2 ← cups-filters, depends on libcupsfilters1 libcupsimage2 ← libcupsfilters1 (shlibs dependency, can't be removed) libcupsimage2 ← ghostscript-cups, doesn't depend on libcupsfilters1 libcupsimage2 ← libescpr1 (dropped in Jessie) libcupsimage2 ← libgs9, doesn't depend on libcupsfilters1 libcupsimage2 ← lsb-printing, doesn't depend on libcupsfilters1 [0] libcupsimage2 ← printer-driver-c2esp, doesn't depend on libcupsfil</pre> Didier 'OdyX' Raboud 2013-06-18T08:17:15 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.debian.printing