*** This bug is a duplicate of bug 173470 ***
https://bugs.launchpad.net/bugs/173470
This problem can be linked too to the fact that CUPS 1.3.x has a regression :
it only detects/lists network interfaces, IPs and netmasks at startup (instead
of the normal way of operation that is to
*** This bug is a duplicate of bug 173470 ***
https://bugs.launchpad.net/bugs/173470
This is caused by an upstream bug in CUPS. CUPS stops broadcasting if it
gets a HUP signal for reloading its configuration. This happens every
night via the logrotate cron job and a full stop and restart of
I found a Cleaner solution:-)
Add the cupsserver ip to your /etc/hosts file.
That did it for me
--
Cups printer sharing needs restart to work
https://bugs.launchpad.net/bugs/172297
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I have exactly the same problem, after a server reboot clients can not see the
shared printer
I tried to change cups to S99 in startup folder but it didn`t work.
My solution was add /etc/inid.d/cupsys restart in rc.local, so cups is started
by the system scripts and is restarted by rc.local.
i really don`t think that`s a clean solution.
For example, if i change the server ip i will have to update all clients.
And if i have , let`s say 300 clients [not all of them with ssh enabled] i will
have a few problems to change hosts in each one.
restart cups in rc.local seems not cleaner , but
Oh i can see that.
But for the standard home user, i still think that adding the ip i best.
But, perhaps the best solution would be, if the Ubuntu devs, corrected the
bug:-)
--
Cups printer sharing needs restart to work
https://bugs.launchpad.net/bugs/172297
You received this bug notification
