Description of problem: System-config-printer correctly detected a Ricoh Aficio MP 3350 network printer. I specified a custom PPD file that our sysadmin provided. In system-config-printer, the status is: 'Inactive - Filter "/usr/lib64/cups/filter/foomatic-rip" for printer "RICOH-Aficio-MP-3350" not available: no such file or directory. Indeed, foomatic-rip is not in /usr/lib64 but in /usr/lib. Version-Release number of selected component (if applicable): 4.0.4-12fc14 How reproducible: Always Steps to Reproduce: 1. Add a new network printer 2. Change the driver to a custom ppd 3. Check printer status in s-c-p Actual results: Error message in the status field Expected results: Status field without errors Additional info: I can work around the problem by creating a symbolic link from /usr/lib64/cups to /usr/lib/cups.
/usr/lib/cups/filter/foomatic-rip is the correct path for both 64- and 32-bit architectures.
Tim, and where does the /usr/lib64/cups/filter/foomatic-rip appear from ? From the custom PPD ? Reinout, can you attach the PPD ?
Jiri, Yes, it will be referenced from the custom PPD, probably in a *cupsFilter attribute.
Created attachment 447418 [details] The custom ppd file, for reference There's no mention of a lib64 library path in this ppd file.
Did you try to print with the automatically selected driver (PPD) ? Can you try it now ? I think there's no reason to use the sysadmin provided PPD.
(In reply to comment #5) > Did you try to print with the automatically selected driver (PPD) ? No. > Can you try it now ? > I think there's no reason to use the sysadmin provided PPD. The sysadmin stressed that I had to use this one because the printer has adapted firmware and the default Linux driver makes it lock up. I'd rather not create problems for the people working here just to provide information for this bug.
Oops, the cupsd message is misleading and is a result of trying first /usr/lib/cups/filter, then /usr/lib64/cups/filter, and finding it in neither place. Please install the 'foomatic-filters' package. It should have been installed already though -- how did you install this system?
Changing to MODIFIED as the message has been fixed in the git repository now. Question still remains: how was this system installed?
foomatic-filters-4.0.4-12.fc14.x86_64 is installed. I used a FC14 Alpha DVD to install the system from and then upgraded to the latest version of everything. I used system-config-printer to add the printer, if I recall correctly it caused some extra packages to be downloaded and installed.
On a hunch, I deleted the /usr/lib64/cups symlink that I made and I could still print without errors. So I'm not sure where the status error message came from but I can't reproduce it any more right now.
Strange. It was perhaps a stale error messages from before foomatic-filters was installed. Anyway, keeping this bug report just to the misleading CUPS message for now.
cups-1.4.4-10.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/cups-1.4.4-10.fc14
cups-1.4.4-10.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/cups-1.4.4-10.fc13
cups-1.4.4-9.fc12 has been submitted as an update for Fedora 12. https://admin.fedoraproject.org/updates/cups-1.4.4-9.fc12
cups-1.4.4-10.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update cups'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/cups-1.4.4-10.fc14
cups-1.4.4-10.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
cups-1.4.4-10.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
cups-1.4.4-9.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.