Bug 691834
| Summary: | DNS-SD printer not shown when adding printer | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tim Waugh <twaugh> |
| Component: | control-center | Assignee: | Marek Kašík <mkasik> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | control-center-maint, jarkko.torvinen, jjardon, mkasik, rstrode |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-09 12:08:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This still seems to be an issue in current F15 Default firewall rules in f15 block mdns, so cups cannot find the printer. You need to manually set mdns as trusted service from firewall configuration. Then gnome printer config works and cups can find printers from lan via http://localhost:631 Should the default rules allow mdns, or should cups open mdns from firewall? This is quite annoying propably for many users when printers are not found and there is no error message (In reply to comment #2) > Should the default rules allow mdns, or should cups open mdns from firewall? > This is quite annoying propably for many users when printers are not found and > there is no error message The control-center 'Printers' panel should do it. (cf. system-config-printer, which does this.) should but does not do it. I have tested this on two fresh installs of f15 and both fail to see network printers unless manually open mdns in firewall first (In reply to comment #4) > should but does not do it. Agreed. After consultation with system-config-firewall's maintainer I have to reconsider possible security implications of my patch in the bug https://bugzilla.redhat.com/show_bug.cgi?id=710061. A solution to this could be firewalld but enabling of mdns still can result in weaker system from the security point of view. Regards Marek The direction things are moving is that mDNS will be the *only* network discovery protocol for printing. http://pwg-wiki.wikispaces.com/IPP+Everywhere Yes, you need to open up a local port for that. Same goes for file sharing, print sharing, VNC, and so on. Allowing users to read their email makes for a weaker system. That's not a good argument for not doing it at all, only for making it safer. The alternative is that a user needs to print something right away, but can find no way to do so. I've added a patch enabling print-related services to this upstream bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=648784. Marek The fix is already available in F16. I'm closing this with nextrelease resolution. Marek |
Description of problem: When trying to add a network printer, I am not shown the device in the list. It is an HP DeskJet 990Cxi with a D-Link parallel-to-network adapter plugged into its parallel socket. Version-Release number of selected component (if applicable): control-center-2.91.93-1.fc15.x86_64 How reproducible: 100% Steps to Reproduce: 1.System Settings -> Printers 2.Click Unlock 3.Click + 4.Wait for devices search to finish 5.Click on Network Actual results: Empty list Expected results: The printer shown in the list. Additional info: In 'lpinfo -l -v' I see this: Device: uri = dnssd://dlk-08E206-P1._printer._tcp.local/ class = network info = dlk-08E206-P1 make-and-model = Unknown device-id = location =