Bug 670494 - cups network printers not available on boot
Summary: cups network printers not available on boot
Keywords:
Status: CLOSED DUPLICATE of bug 354071
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 14
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-18 13:41 UTC by Miloslav Trmač
Modified: 2012-05-19 02:54 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-05-19 02:54:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Miloslav Trmač 2011-01-18 13:41:03 UTC
(Just guessing that this is NetworkManager-related, feel free to reassign)

I have cups set up with "BrowsePoll HOSTNAME" to automatically add remote printers from a specific server, on a company network


When I'm in the office:
- wired network directly connected to the company network
- wireless network that does not have access to the company network

The printers from "BrowsePoll" are not visible after boot and login, cups reports:
[cups-polld HOSTNAME:631] Unable to connect to HOSTNAME on port 631: Host name lookup failure

After (service cups reload), cups recognizes HOSTNAME and makes the printers visible.


When I'm at home, I only have a wireless network that is not connected to the company netwrok.  Therefore, cups can not access the printers.  However, after I open a VPN connection, the printers are automatically visible without needing to manually run (service cups reload).

Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-10.git20100831.fc14.x86_64
cups-1.4.4-11.fc14.x86_64


Actual results:
On boot when on the office wired network, cups can not find HOSTNAME.

Expected results:
On boot when on the office wired network, cups find HOSTNAME and printers are visible.

Comment 1 Jirka Klimes 2011-01-19 10:09:19 UTC
I think it's the same issue as bug 354071. cups-polld doesn't update its nameservers and thus can't resolve the HOSTMANE.
You could try to find out what's in /etc/resolv.conf when cupsd (and in turn cups-polld) starts.

I suggest duping this to bug 354071 and reopen it. https://bugzilla.redhat.com/show_bug.cgi?id=354071#c13 indicates that the issue is not resolved.

Comment 2 Dan Winship 2012-05-08 14:04:51 UTC
still a problem? if not, this is a dup of 354071

Comment 3 Miloslav Trmač 2012-05-19 02:54:39 UTC
Verified fixed in cups-1.5.2-9.fc16.x86_64 .  Thank you!

*** This bug has been marked as a duplicate of bug 354071 ***


Note You need to log in before you can comment on or make changes to this bug.