Mailinglist Archive: opensuse (4054 mails)

[Johannes Meixner <jsmeix@xxxxxxx>]

Hello,

didn't it work with the included GimpPrint when you set it up
as a RX600?

On Jan 3 23:01 Dave Howorth wrote (shortened):
> > I [02/Jan/2006:16:31:51 +0000] Started
> > filter /usr/lib64/cups/filter/rastertopips (PID 20234) for job 17.
...
> > E [02/Jan/2006:16:31:51 +0000] PID 20234 stopped with status 22!
...
> I've just taken another look. There is
> *no* /usr/lib64/cups/filter/rastertopips. There is
> a /usr/lib/cups/filter/rastertopips. The PPD file doesn't specify
> a path to the filter.

Either add the full path to the filter in the cupsFilter line
in the PPD file in /etc/cups/ppd/ or create a link
/usr/lib64/cups/filter/rastertopips -> /usr/lib/cups/filter/rastertopips

When the PPD doesn't specify the full path to the filter,
cupsd assumes it is located in the CUPS default path.

In any case make sure the user "lp" (this user runs the filters
and the backend) can execute them.


> How does CUPS decide whether a filter is 32-bit or 64-bit?

CUPS doesn't care which kind of executable a filter is.
It can be a bash script or any other kind of executable file.
The cupsd simply starts a process to execute it.
If it is a dynamically linked binary then it is the linker
which cares whether it is 32-bit or 64-bit.


> PS Epson aren't being at all helpful.

Even if they are not helpful at the moment, it is crucial
that many Linux users contact the manufacturers directly.
Otherwise nothing changes, see
http://portal.suse.com/sdb/en/2000/08/jsmeix_print-kompatibel.html
"If your printer is not supported"

By the way:
See
http://lists.suse.com/archive/suse-linux-e/2006-Jan/0392.html
At least you are not the only one with problems on 64bit AMD
with proprietary 32-bit-only drivers from manufacturers
which claim to provide Linux support.


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5      Mail: jsmeix@xxxxxxx
90409 Nuernberg, Germany                    WWW: http://www.suse.de/