| Summary: | cups depends on ghostscript when it should depend on ghostscript-esp | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ian Kumlien <ian.kumlien> |
| Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | printing |
| Priority: | High | ||
| Version: | 2006.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Ian Kumlien
2006-07-26 15:21:22 UTC
(In reply to comment #0) > since gs invocation becomes a silent fail in debug logs it's almost impossible to find. Uhm? What silent fail? cups version? ghostscript-gnu version? emerge --info? Steps to reproduce? Sorry, there's no information here. > Please change this dependency. No, virtual/ghostscript needs to stay there. > Uhm? What silent fail? cups version? ghostscript-gnu version? emerge --info? > Steps to reproduce? Sorry, there's no information here. ghostscript-gnu does not work with GDI at all. cups with debug logging says that *everything worked* but nothing gets to the printer. Something in cups runs gs and doesn't care about the error message, thus silent fail. > No, virtual/ghostscript needs to stay there. Expect disapointed users, cups only works with ghostscript-esp. So one of the following would work: 1, change the dependency 2, remove all other ghostscripts 3, make gs-eps avail at all times eventhough another gs has been selected. This btw, is something that never happens on $other-distributions. (In reply to comment #2) > > No, virtual/ghostscript needs to stay there. > > Expect disapointed users, cups only works with ghostscript-esp. Erm, in Gentoo all ghostscript flavours are patched to work w/ cups and have been working w/ cups for quite some time, so no - there's nothing wrong w/ that dependency. It would be more useful to post the involved versions and some information to actually debug your problem. Didn't work: [ebuild N ] app-text/ghostscript-gnu-8.16-r1 USE="cups -X -cjk -gtk" 10,131 kB Complains with "Unknown device: gdi" when using foomatic drivers. Works: [ebuild R ] app-text/ghostscript-esp-8.15.2_p20060520 USE="cups threads xml -X -cjk -emacs -gtk" 0 kB This was with cups x86 and ~x86, which should be versions: [ebuild R ] net-print/cups-1.2.2 USE="dbus gnutls jpeg nls pam png ppds slp ssl tiff -samba" 0 kB (aswell as 1.2.1) And 1.1.x something. Yet again, to reiterate, ghostscript-gnu does not work with GDI drivers. Yet again, to reiterate, please change the dependency. And re other dists: http://packages.ubuntu.com/dapper/net/cupsys Older debian seems to have it as a recomendation though. And why gdi? well i have a Samsung ML 1510, for which the foomatic manual execution documentation states: (http://www.linuxprinting.org/execution.cgi?driver=gdi&printer=Samsung-ML-1510&.submit=Show+execution+details) gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=gdi -c "<</PageSize[<PageSizePS>]/ImagingBBox null>>setpagedevice" -c "<</HWResolution[<Resolution>]>>setpagedevice" -sOutputFile=- - | perl -p -e 's/PJL PAGE LETTER/PJL PAGE <PageSizeJCL>/; s/PJL PAGE (\S*) AUTO/PJL PAGE $1 <Manualfeed>/; s/PJL SET TONERSAVE = OFF/PJL SET TONERSAVE = <Economode>/; s/PJL SET PAPERTYPE = NORMAL/PJL SET PAPERTYPE = <MediaType>/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET RET = <RET>\r\n$1/; s/PJL COPIES = 1/PJL COPIES = <Copies>/; s/PJL SET DENSITY = 1/PJL SET DENSITY = <Density>/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET JAMRECOVERY = <JamRecovery>\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET REPRINT = <AllowReprint>\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL SET ALTITUDE = <Altitude>\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL DEFAULT TIMEOUT = <PageTimeout>\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL DEFAULT POWERSAVE = <PowerSaving>\r\n$1/; s/(\@PJL ENTER LANGUAGE)/\@PJL DEFAULT POWERSAVETIME = <PowerSaveTime>\r\n$1/; ' And, yes, this fails due to the -sDEVICE=gdi switch. Uhm, so use ghostscript-esp, nothing is preventing you from using it with cups. We won't be hardcoding a particular GS implementation into the dependencies just because your printer doesn't work. |
