Description of problem: On start of CUPS, these errors appear in the log. Dec 07 10:24:48 gigalith.gloomytrousers.co.uk cupsd[1685]: [CGI] cups-brf must be called as root Dec 07 10:24:48 gigalith.gloomytrousers.co.uk cupsd[1685]: [cups-deviced] PID 1897 (cups-brf) stopped with status 1! Dec 07 10:24:48 gigalith.gloomytrousers.co.uk cupsd[1685]: [cups-deviced] PID 1877 (gutenprint52+usb) stopped with status 1! So far I have not identified any ill effects from this (although I do have a problem printing from another machine on the network, which so far I believe to be unrelated). Version-Release number of selected component (if applicable): cups-2.2.8-6.fc29.x86_64 cups-client-2.2.8-6.fc29.x86_64 cups-filesystem-2.2.8-6.fc29.noarch cups-filters-1.20.3-10.fc29.x86_64 cups-filters-libs-1.20.3-10.fc29.x86_64 cups-ipptool-2.2.8-6.fc29.x86_64 cups-libs-2.2.8-6.fc29.x86_64 cups-pk-helper-0.2.6-6.fc29.x86_64 How reproducible: Every time Steps to Reproduce: 1. Start CUPS service, on boot or manually Actual results: Errors in journal Expected results: No errors Additional info:
Hi Russell! Thank you for reporting the issue! I can see the messages too in F28 during startup, but I can print just fine, so I do not find out the messages critical. Both binaries are backends (binaries which communicate or discovers the printers, part before "://" in printer's device uri - f.e. 'socket://192.168.1.1:9100' is printer uri with backend 'socket') - cups-brf is virtual backend for braille printers shipped in cups-filters project and gutenprint52+usb is backend for usb printers, which are supported in gutenprint. CUPS is reacting to 'Get-Devices' request, which starts cups-deviced binary, which starts every backend and returns all printers found by backends - cups-brf is needed to be run as root to work correctly (probably I can fix it in cups-filters) and gutenprint52+usb is probably called incorrectly or cannot cope up without any existing gutenprint supported printer. I'll get to it when there are not more urgent matters, I'm sorry.
Thanks, Zdenek. No urgency for me, I can print OK too. I would guess anyone with one of the printers supported by those backends might have trouble, though.
Hi Russell, I just fixed the cups-brf error message (it appears only after reboot or start of OS)- you can check it in update https://bodhi.fedoraproject.org/updates/FEDORA-2019-11ddefe76f . I'll try to fix gutenprint issue when I will have a time.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.