Description of problem: A cups server is already configured in my laptop(as part of my office lan). Now if I try to connect a USB based printer to my laptop. I cannot print using this, nor able to configure this printer. Please note, I can see the printer is detected properly by the laptop (using dmesg). BUT, I cannot configure the printer using the UI, neither be able to add the printer. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Have a cups server already configured. 2. Now, try to connect a local (USB based) printer. 3. Kernel detected the printer, but unable to get the printer configured at all. Actual results: Expected results: Configuring a local usb printer should be quite easy ( although I have a cups server configured) Additional info: $ rpm -qa | grep cups cups-filters-libs-1.0.69-2.fc22.x86_64 gutenprint-cups-5.2.10-11.fc22.x86_64 cups-filesystem-2.0.3-1.fc22.noarch cups-pk-helper-0.2.5-5.fc22.x86_64 cups-client-2.0.3-1.fc22.x86_64 cups-pdf-2.6.1-9.fc22.x86_64 cups-2.0.3-1.fc22.x86_64 cups-libs-2.0.3-1.fc22.i686 python3-cups-1.9.72-1.fc22.x86_64 cups-libs-2.0.3-1.fc22.x86_64 bluez-cups-5.29-2.fc22.x86_64 cups-filters-1.0.69-2.fc22.x86_64 $ cat /etc/cups/client.conf ServerName cups.country.company_name.com PS: Please note once I add "ServerName localhost" in client.conf, it is working. BUT, I Need to manually edit this. This should be easily doable using UI itself.
Could you attach some logs obtained via: # cupsctl LogLevel=debug # systemctl restart cups.service try to connect the printer # journalctl -u cups.service -e
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.