https://bugzilla.novell.com/show_bug.cgi?id=633468 https://bugzilla.novell.com/show_bug.cgi?id=633468#c yang xiaoyu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |werner@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=633468 https://bugzilla.novell.com/show_bug.cgi?id=633468#c2 Christian Trippe changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ctrippe@gmx.net Component|KDE4 Applications |OpenOffice.org AssignedTo|kde-maintainers@suse.de |bnc-team-ooo@forge.provo.no | |vell.com QAContact|qa@suse.de |cwei@novell.com --- Comment #2 from Christian Trippe 2010-08-23 09:23:45 UTC --- KDE3 bugs are no longer fixed, see http://en.opensuse.org/KDE3 -> Wontfix for kpdf. According to the Description Firefox and OpenOffice are also affected. Changing Component to OpenOffice -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=633468 https://bugzilla.novell.com/show_bug.cgi?id=633468#c6 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jsmeix@novell.com | --- Comment #6 from Johannes Meixner 2010-08-25 08:11:19 UTC --- The cupsd set up the filtering pipe, see "The Filter" at http://en.opensuse.org/SDB:CUPS_in_a_Nutshell For non-PostScript printers the filtering pipe usually contains a "gs" call but this does not at all mean that it is the cupsd itself which passes GenericResourceDir to gs (of course the CUPS sources do not contain "GenericResourceDir"). Remember that the reporter wrote in comment #0 that for him even a plain "gs" call from the comand line results the same behaviour. The Ghostscript documentation mentiones "GenericResourceDir" e.g. at /usr/share/ghostscript/8.62/doc/Use.htm#PS_resources which reads that the default value is (./Resource/) for Unix. But even calling gs -sGenericResourceDir=./Resource/ does not show any warning for me. I am not a sufficient Ghostscript expert to answer the question how this issue could happen off the top of my head and I cannot investigate the issue because I cannot reproduce it. But of course it is neither OOo nor any other program which passes an explicite "GenericResourceDir" to the gs call. Perhaps it is somewhere in the particular user's settings for "gs"? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=633468 https://bugzilla.novell.com/show_bug.cgi?id=633468#c8 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |matthias.hermanns@web.de AssignedTo|werner@novell.com |bnc-team-ooo@forge.provo.no | |vell.com --- Comment #8 from Johannes Meixner 2010-08-25 09:22:24 UTC --- Werner told me that the reporter may not call /usr/bin/gs or that whatever wrapper is run when he calls "gs" or that his particular Ghostscript environment is broken. Matthias Hermanns, please provide the exact full output of the following four commands: type -a gs file $( type -p gs ) gs -h rpm -q --changelog ghostscript-library | head -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=633468 https://bugzilla.novell.com/show_bug.cgi?id=633468#c10 --- Comment #10 from Dr. Werner Fink 2010-08-25 09:36:42 UTC --- I also want to see the output of printenv | grep GS_ and the output of ls -l /usr/share/ghostscript -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=633468 https://bugzilla.novell.com/show_bug.cgi?id=633468#c12 --- Comment #12 from Dr. Werner Fink 2010-08-25 11:26:01 UTC --- /usr/share/ghostscript/Resource belongs of one of the following packages: CID-keyed-fonts-MOE-20021114-346.5 ghostscript-cjk-20050315-151.5 CID-keyed-fonts-Wada-20021114-346.5 CID-keyed-fonts-Munhwa-20021114-346.5 CID-keyed-fonts-WadaH-20021114-346.5 .. the message *** Warning: GenericResourceDir doesn't point to a valid resource directory. the -sGenericResourceDir=... option can be used to set this. is a warning and does not matter. Nevertheless cups should not print such messages even if send to stdout. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=633468 https://bugzilla.novell.com/show_bug.cgi?id=633468#c14 --- Comment #14 from Dr. Werner Fink 2010-08-25 11:56:09 UTC --- (In reply to comment #13) No it's not for ghostscript. You may have a look to the old lpdfilter system how to avoid this. Some postscript files may print to stdout if interpreted. Therefore lpdfilter uses not stdout but its own file descriptor: # # Handling of file descriptors # 0 is input # 1 is for output # 2 is for error messages # 3 is for accounting or this bash script # We remap the following file descriptors # 4 is for output # 5 may later set for gs # 1 is for error messages too # exec 4>&1 1>&2 [...] # # Ghostscript OUT to printer IN filter on fd 5 if any. # OutPipe="-sOutputFile=/dev/fd/5" if test -x /etc/lpdfilter/${queue}/post ; then if link=$(readlink /etc/lpdfilter/${queue}/post) ; then exec 5> >(exec -a "${link##*/}" $link 1>&4) unset link else exec 5> >(exec -a "post" /etc/lpdfilter/${queue}/post 1>&4) fi elif test -n "$post" -a -x "${post%% *}" ; then arg0="${post%% *}" exec 5> >(exec -a "${arg0##*/}" $post 1>&4) unset arg0 else exec 5> >(exec -a "buffer" cat 1>&4) fi GS_OPTIONS="$GS_OPTIONS $OutPipe" export GS_OPTIONS -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=633468 https://bugzilla.novell.com/show_bug.cgi?id=633468#c16 --- Comment #16 from Johannes Meixner 2010-08-25 14:01:42 UTC --- After a plain mkdir /usr/share/ghostscript/Resource I can reproduce it and it appears on stdout: ----------------------------------------------------------------------------- gs -q -dQUIET 2>/dev/null *** Warning: GenericResourceDir doesn't point to a valid resource directory. the -sGenericResourceDir=... option can be used to set this. ----------------------------------------------------------------------------- In contrast with gs -sstdout=%stderr -q -dQUIET 2>/dev/null there is no longer the waring on stdout. Now I also get the GenericResourceDir warning message in the output of my test queue which uses the hpijs driver and foomatic-rip-hplip. After mv /usr/lib/cups/filter/foomatic-rip-hplip \ /usr/lib/cups/filter/foomatic-rip-hplip.orig ln -s /usr/bin/foomatic-rip /usr/lib/cups/filter/foomatic-rip-hplip the output of my test queue which uses the hpijs driver is clean again. Summary:

From my point of view the root cause is that Ghostscript outputs such warning messages on stdout. But because Ghsotscript did output unexpected messages on stdout all the time in the past this is probably intentionally by design so that it will not be changed by upstream Ghostscript or it cannot be changed without breaking backward compatibility.

The next cause from my point of view is that certain packages (see comment #12) seem to provide some kind of "invalid" stuff in /usr/share/ghostscript/Resource/ which lets Ghostscript output the above warning message. The last cause is that foomatic-rip-hplip calls gs in a meanwhile too traditional way which lets unexpected Ghostscript stdout output appear on the printer. I will file an upstream bug report at HPLIP regarding this particular cause. I don't know what to do regarding the other two causes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=633468 https://bugzilla.novell.com/show_bug.cgi?id=633468#c18 --- Comment #18 from Johannes Meixner 2010-08-25 15:09:31 UTC --- One more alternative workaround: To use foomatic-rip-hplip with a PPD for the hpijs driver you can change in the /etc/cups/ppd/.ppd file for the particular print queue the FoomaticRIPCommandLine as follows: Exchange in the FoomaticRIPCommandLine value the part ... gs -q -dBATCH ... with ... gs -sstdout=%stderr -q -dBATCH ... and the part ... -sOutputFile=- - ... with ... -sOutputFile=%stdout - ... Note that '&&' at the end of the line is used to split it and continue it at an arbitrary position on the next line like in ------------------------------------------------------------------------- *FoomaticRIPCommandLine: "gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPA&& USE -sDEVICE=ijs -sIjsServer=hpijs%A%B%C -dIjsUseOutputFD%Z -sOutputFi&& le=- -" ------------------------------------------------------------------------- but you can re-format it so that it is easier to read like ------------------------------------------------------------------------------ *FoomaticRIPCommandLine: "gs -sstdout=%stderr -q -dBATCH -dPARANOIDSAFER && -dQUIET -dNOPAUSE -sDEVICE=ijs -sIjsServer=hpijs%A%B%C -dIjsUseOutputFD%Z && -sOutputFile=%stdout -" ------------------------------------------------------------------------------ Now foomatic-rip-hplip calls gs as follows: gs -sstdout=%stderr -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE \ -sDEVICE=... -sOutputFile=%stdout - Probably the '-q' switch has now become dispensable. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=633468 https://bugzilla.novell.com/show_bug.cgi?id=633468#c20 Andrey S changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seldmail@gmail.com --- Comment #20 from Andrey S 2011-01-20 21:56:48 UTC --- On openSUSE 11.3 with HPLIP 3.10.9 and HP LaserJet 1022n (Ethernet network printer) this message ("GenericResourceDir doesn't point to a valid resource directory.") is the only thing I can get from the printer. After printing this message on one page it stops printing anything, though HPLIP writes "Job Sent" and "Job Completed" if you send any more documents on it. If I then "print" a blank page in OpenOffice (so printer just spits a blank page) and then send new job (with text or images) it prints one more page with error and then stops printing anything. So I cannot print anything except blank pages or one page with "GenericResourceDir ..." error message. On openSUSE 11.2 HP LaserJet 1022n worked just fine without any errors. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.