Hide Forgot
Description of problem: Control-center's printer config util insists that firewalld be running in order to add a printer, but F16 does not seem to run firewalld by default, and it does not appear easy to make it work. If you start firewalld manually, control-center will then let you run the add printer wizard, but with firewalld running, system-config-firewall no longer works: on starting up it says "FirewallD is active, please use firewall-config", except there doesn't seem to be any "firewall-config" available in yum. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Open control center 2. Click on "Printers" 3. Click "add new printer" Actual results: Expected results: Additional info:
same here, I was able to find my printer once by manually adding IP (but it failed on isntalling drivers due to incomplete-yum-transaction). after firewalld got installed, the message is not displayed, but no printer found again can you give me where to look for logs?
Can someone provide a proper workaround for F16 to get network printers installed and post it in here? I have tried for quite a while now unsuccessfully to get a network printer setup. I have a number of apps I'm using that have iptables configs so I do not want to get this firewalld installed and screw everything up that is based on iptables. .
Ok, I found the old printer setup. It's under: Activities | Applications | Other | Printing It works fine and doesn't require this firewalld thing although it will prompt you about a half-dozen times to enter the root password. .
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.