cups printers not advertised via avahi after upgrade from jaunty to karmic

Bug #484823 reported by Thawn
54
This bug affects 10 people
Affects Status Importance Assigned to Milestone
avahi (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This bug reported for cups might also be caused by/affecting avahi:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/465916

Summary:

After upgrading from Jaunty to Karmic, cups printers are no longer advertised via bonjour/dns-sd/mDNS/Zeroconf/Avahi.
This most severely affects Mac clients where sharing via the cups protocol is deactivated by default.

avahi version:
0.6.25-1ubuntu5

cups version:
1.4.1-5ubuntu2.1

expected behavior:
after turning on printer sharing in the cups web frontend, cups printers should be advertised by avahi

actual behavior:
even if printer sharing is turned on, avahi does not advertise the printers
(tested with mac clients on the local network and with "avahi-browse --all" on the server machine)
this used to work with Jaunty

Revision history for this message
dude (matt108a-deactivatedaccount) wrote :

This affects windows PCs as well, if they use bonjour for printer discovery.

Revision history for this message
Friedrich Graeter (graeter) wrote :

I can confirm this bug. Also the SFTP / SSH access to the machine is not published any more.

Revision history for this message
Jouke (digigram) wrote :

confirm on 9.10 server edition. only the workstation entry appears, ssh, printers, nothing else is published.

Revision history for this message
Jouke (digigram) wrote :

OK no response so far. I am trying to collect more info:

1) avahi-publish-service test _test._tcp 80
This works the service is published.

2) adding a service file to /etc/avahi/services works

3) tried "use-ipv6=no" setting to yes as is suggested hereL http://lists.freedesktop.org/archives/avahi/2007-August/001136.html
but only made the workstation and services in /etc/avahi/services appear twice

4) checked output of avahi which looks good:
root@247JT:~# avahi-daemon
Found user 'avahi' (UID 105) and group 'avahi' (GID 111).
Successfully dropped root privileges.
avahi-daemon 0.6.25 starting up.
Successfully called chroot().
Successfully dropped remaining capabilities.
Loading service file /services/afpd.service.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::213:20ff:fe64:156c.
New relevant interface eth0.IPv6 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.100.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::213:20ff:fe64:156c on eth0.*.
Registering new address record for 192.168.1.100 on eth0.IPv4.
Registering HINFO record with values 'I686'/'LINUX'.
Server startup complete. Host name is 247JT.local. Local service cookie is 1342462579.
Service "247JT" (/services/afpd.service) successfully established.

5) compared configuration files to working hardy installation, and found no differences.

6) Set rhytm box to sharing (on 9.10 Desktop edition, fresh install). Shares are published if rhythm box is started after avahi is started. Tried to restart ssh and cups, turn on and turn of sharing in cups, but nothing is published.

7) ldd /usr/lib/libcups.so.2 shows a dependency on avahi

OK I ran out of ideas

Jouke (digigram)
Changed in avahi (Ubuntu):
status: New → Confirmed
Revision history for this message
lofgole (lofgole) wrote :

Since the problem is on avahi side not cups: Here is the upstream bug. I think the duplicate status should be vice versa.

http://www.avahi.org/ticket/303

Revision history for this message
Luke Symes (allsymes) wrote :

Well the problem is not so much with Avahi. Even if we get CUPS to compile with Avahi support, it won't be able to share printers via DNS-SD, because the patch for CUPS doesn't support that yet. I'm not sure if it's being actively developed either.

Revision history for this message
John Rose (johnaaronrose) wrote :

This bug has returned on Precise 32 bit. I have a feeling that some dnsd packages were updated recently.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.