Description of problem: cups-driverd errors at startup Version-Release number of selected component (if applicable): 28 (with or without updates) How reproducible: Easily, fresh install, out of the box. Steps to Reproduce: 1. Fresh install of Fedora 28 (KDE / Cinnamon spins, others not tested) 2. Start cups.service Actual results: Hundreds of '[cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/....ppd.gz"!' are logged to the journal. Expected results: No errors... Additional info: Printing still seems to work.
Hi Iestyn, thank you for reporting this issue! I'll look into it - it seems cups cannot read static ppds, which are gziped... and then recognizes them badly as .drv files, which causes the logs.
cups-2.2.6-15.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-5e48964321
cups-2.2.6-15.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-5e48964321
The reason I reported this as a separate bug #1589593 (cupsd ignoring LogLevel) was that I think the bad driver information files should be fixed. I agree the solution to the other bug stops the log being spammed with "bad driver" messages but these messages should not be produced in the first place (and would not be if the driver files themselves were corrected).
I take that back, it seems the bad driver messages are no longer reported even with LogLevel debug or debug2, to file or to journald.
That's because the source of the logs https://bugzilla.redhat.com/show_bug.cgi?id=1590123 is fixed in the same update.
Yes, understood. Don't have access to that bug so couldn't be sure. Thanks again, great work, much appreciated.
cups-2.2.6-15.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.