Running Slackware64-14.2 with a Dell C1760nw color laser printer. The driver is the Xerox Phaser 6000B v.1.0. It worked fine until I had to reinstall it.

Now when I try printing a test page CUPS displays, Idle -
"File "/usr/lib/cups/filter/Xerox_Phaser_6000_6010/XRM_MF" has insecure
permissions (0100500/uid=1000/gid=100)." Originally the perms were 755 and I gradually reduced them.

Files in this directory are: # ls
XRM_AL5CB* XRM_DF* XRM_FXR* XRM_MF* XRM_SBP* XRM_TRC*
XRM_CC* XRM_EE* XRM_HBPL* XRM_PR* XRM_TP*

I deleted and re-added the printer using CUPS. No difference.

What should the perms be?

TIA,

Rich

Update: I changed owners for /usr/lib/cups/filter/Xerox_Phaser_6000_6010/* to root.root. Now a test page fails with the message that the filter failed.

I'm out of ideas. Help's needed.

Rich

There is more detailed info in CUPS log and you can increase verbosity if needed.

Good point; I didn't think of looking at the log.

I've trimmed the error log to contain only yesterday's attempts to print a text file. Because I don't see the problem (actually, I see what appears to be many issues) I've attached the 26K file.

I hope this helps!

Rich

Attached Files

error_log.txt (25.4 KB, 11 views)

Your log starts with an error, often what happens immediately before error is the reason, I'd stop cupsd, purge all logs, restart cupsd and see what's in them. Then attempt printing and keep an eye on logs, again. If still nothing I'd increase verbosity, I think there is such an option in cupsd conf file.

Does the Xerox printer have a proprietary driver? You say you deleted and re-added it using cups, but if it has a proprietary driver then maybe you should try that.

In fact, searching I found drivers from xerox. Although old (the printer is old), they might make a difference.

I suspect the complaint about permissions should lead you to adjusting the permissions and ownership to match the surrounding files and directories.

Looking at this line from the error log
E [29/Mar/2021:11:01:59 -0700] colorp: File "/usr/lib/cups/filter/Xerox_Phaser_6000_6010/XRM_MF" has insecure permissions (0100744/uid=1000/gid=100).

I would say the ownership is likely wrong. I suspect that UID=1000 is your user, and GID=100 is group users. I believe those files should all be 755 or 750 with UID root and GID users. or UID root and GID cups.

The Xerox_Phaser_6000_6010 directory is showing the same ownership errors.

edit
I searched for drivers for the dell printer model you posted and found a couple of very good hits, including this one that claims to solve the issues.

everything in '/usr/lib/cups/filter/' should be root:root. Is your user still in group 'lp'? You didn't say which Xerox Phaser 6000/6000B package you installed from the Xerox site. Although the rpm version claims both 32- and 64-bit, it looks to be 32-bit only. From what I see you will need a multilib set-up since you are using Slackware64-14.2. The directory '/usr/lib/cups/filter/' doesn't exist on a pure 64-bt system, nor do the required CUPS compat32 files. The permision error my be a red herring due to missing 32-bit libraries.

Did you skip an installation step?

Ed,

All files in /usr/lib/cups/filters are owned by root.root.

Yes, my username is in /etc/groups/lp.

The Xerox Phaser 6000/6000B package was downloaded when I bought the printer. It's now in my installed package directory: /data/installed-SBo-pkgs/Xerox-Phaser_6000_6010-1.0-1.i686.tgz. IICR, I downloaded the .deb, ran it through deb2tgz and installed that. Worked fine until I unintentionally removed all non-core-distribution packages and reinstalled them.

Permission error resolved yesterday by changing owner to root.root.

AlienBOB's multilib and compat32 files reinstalled; system rebooted.

Issue now is 'Filter failed.'

Thanks,

Rich

Ha! Today's cups log tells me that I need to replace the toner cartridges (doesn't specify which one) and the trash try is full. Those messages hadn't appeared before. I'll order a set of toner cartridges today. Will report here after they arrive and I install them.

Stay tuned.

New toner cartridges ordered and should be here tomorrow.

In the meantime I tried printing a test page again. I don't understand the error_log[1]; it may be empty toner cartridges (but I'll change them anyway since the installed ones came with the printer).

There are errors of filters not being found even though they're in /etc/cups/filters/, failures in CreatDevice and CreateProfile, and much more.

The attached is the entire log after restarting cups server and trying to print a test page on the Dell/Xerox color laser.

Rich
[1] Attached

Attached Files

error_log.txt (17.0 KB, 4 views)

I note the following reported errors

User Emerson already advised to put CUPS into debug mode for more verbosity. You can do that with
That might yield more useful diagnostic output. Other than that, I recommend searching onine for similar errors reported.

1 members found this post helpful.

The driver I'm using is the same driver that worked before:
Xerox-Phaser_6000_6010-1.0-1.i686.tgz.

Ed,
usr/lib/cups]# ll
total 28
drwxr-xr-x 2 root root 4096 Jun 23 2016 backend/
drwxr-xr-x 2 root root 4096 Jun 14 2016 cgi-bin/
drwxr-xr-x 2 root root 4096 Jun 14 2016 daemon/
drwxr-xr-x 2 root root 4096 Jun 14 2016 driver/
drwxr-xr-x 3 root root 4096 Apr 1 08:22 filter/
drwxr-xr-x 2 root root 4096 Jun 14 2016 monitor/
drwxr-xr-x 2 root root 4096 Jun 14 2016 notifier/

Xerox-Phaser_6000_6010-1.0-1.i686.tgz. Converted from .deb using deb2tgz; this driver worked before and was reinstalled using slackpkg install ...

New color cartridges installed; cleaned, too.

Rich

That answered my question of how to turn on more verbose debugging.

I changed the verbosity to debug-logging and reinstalled ghostscript. Same error starting line 645 through 661. (NB: Every time I try to upload the latest error log the attachment management box tells me it's an invalid file: both ASCII text and gzipped. The 265K file can be downloaded from
<http://www.fileconvoy.com/dfl.php?id=g5bf007ec94a17c9710003405704c6c6a0d9ebe7eae>).

Please suggest how to determine why ghostscript is now failing.

Thanks,

Rich

You're best advised to use pastebin or similar for sharing lengthy output. Many will not risk wanting to download and open files like this. Anyway, all I see of interest is

Unfortunately, I can't really advise/help any further than this.