I had the same problem. I did evrythin you said. Now printer is recognized by
avahi-daemon and other pcs. But still the problem is there:
* Starting Reload cups, upon starting avahi-daemon to make sure remote queues
are populated [ OK ]
* Starting Reload cups, upon starting avahi-daemon to make
Mauro, the problem you have initially complained about is solved for
you. Now the other machines in your network will find your printers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158686
Title:
After following instructions in comment #19 and restarted cups, here is
cupsctl output:
_debug_logging=0
_remote_admin=0
_remote_any=0
_share_printers=0
_user_cancel_any=0
BrowseLocalProtocols=dnssd
DefaultAuthType=Basic
JobPrivateAccess=default
JobPrivateValues=default
MaxLogSize=0
SubscriptionPr
Mauro, I was assuming that printer broadcasting via Avahi does not work
for you. Your cupsd.conf makes the impression to me that your CUPS is
not sharing your printers and that you perhaps need to adjust your
configuration.
If your printers are actually broadcasted and your only problem is the
ugl
I'm referring to this report
I see two instances of the reload cups job in /var/log/boot.log, and the second
one fails:
* Starting Reload cups, upon starting avahi-daemon to make sure remote queues
are populated [ OK ]
* Starting Reload cups, upon starting avahi-daemon to make sure remote queu
Mauro, are you actually sharing your printers? My cupsd.conf contains
--
...
Browsing On
BrowseLocalProtocols dnssd
...
Order allow,deny
Allow @LOCAL
...
--
Your cupsd.conf contains
--
...
Browsing Off
BrowseLocalProtocols dnssd
...
Order allow,deny
...
here you are with /etc/avahi/avahi-daemon.conf
** Attachment added: "avahi-daemon.conf"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1158686/+attachment/3655258/+files/avahi-daemon.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
/etc/cups/cups-files.conf
** Attachment added: "cups-files.conf"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1158686/+attachment/3655242/+files/cups-files.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Here you are with /etc/cups/cupsd.conf
** Attachment added: "cupsd.conf"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1158686/+attachment/3655241/+files/cupsd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
So if you restart avahi-daemon and after that restart cups you do not
get your printers broadcasted?
Can you attach your /etc/cups/cupsd.conf, /etc/cups/cups-files.conf,
/etc/cups/printers.conf, and /etc/avahi/avahi-daemon.conf files?
--
You received this bug notification because you are a membe
No printers discovered by avahi-discover after restarting of services nor after
restarting again avahi-daemon.
Printers work correctly, however.
Don't know what else I can do, the issue still remains.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Mauro, can you follow the instructions of the section "CUPS error_log"
on https://wiki.ubuntu.com/DebuggingPrintingProblems. Please boot your
system (or restart avahi-daemon and cups manually, avahi-daemon first)
and check whether your printers get broadcasted using avahi-discover.
Now restart avah
cat /var/log/boot.log
...
* Starting Reload cups, upon starting avahi-daemon to make sure remote queues
are populated [ OK ]
* Starting cups-browsed - Bonjour remote printer browsing daemon [ OK ]
* Starting Reload cups, upon starting avahi-daemon to make sure remote queues
are populated [ fail ]
Find attached avahi-discover screenshot. It seems no printers are
listed.
** Attachment added: "avahi-discover.png"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1158686/+attachment/3647143/+files/avahi-discover.png
--
You received this bug notification because you are a member of Ubu
Can you run avahi-discover (install the package avahi-discover if
needed). Are your printers listed as IPP printers (Internet Printing
Protocol)? If you run avahi-discover on a client, are the IPP printers
of the server listed?
--
You received this bug notification because you are a member of Ubu
Requested info are attached.
dpkg -s avahi-daemon
Package: avahi-daemon
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 341
Maintainer: Ubuntu Developers
Architecture: amd64
Multi-Arch: foreign
Source: avahi
Version: 0.6.31-1ubuntu3
Depends: libavahi-common3 (>= 0.6.1
Mauro, which version of the avahi-daemon package do you have installed?
Do you have a /etc/init/avahi-cups-reload.conf file? What does it
contain? Can you also attach /var/log/boot.log and /var/log/syslog.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
The bug is not solved for me with avahi - 0.6.31-1ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158686
Title:
When restarting avahi-daemon cups does not reconnect to it -
workaround
To m
I see two instances of the reload cups job in /var/log/boot.log, and the second
one fails:
* Starting Reload cups, upon starting avahi-daemon to make sure remote queues
are populated [ OK ]
* Starting Reload cups, upon starting avahi-daemon to make sure remote queues
are populated [ fail ]
So
This bug was fixed in the package avahi - 0.6.31-1ubuntu3
---
avahi (0.6.31-1ubuntu3) raring; urgency=low
* Reload cups to refresh remote queues, when avahi-daemon starts. (LP:
#1158686). Until cups learns to reconnect to avahi by itself
https://www.cups.org/str.php?L4300 .
All working correctly with avahi-daemon 0.6.31-1ubuntu3. Thank you very
much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158686
Title:
When restarting avahi-daemon cups does not reconnect to it
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
** Changed in: avahi (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158686
Looks correct sequence of events to me, this is avahi-daemon restart:
1 2013-03-22 10:22:12.696810 stopping JOB='avahi-daemon' INSTANCE=''
RESULT='ok'
2 2013-03-22 10:22:12.704692 stopping JOB='cups-browsed' INSTANCE=''
RESULT='ok'
3 2013-03-22 10:22:12.705150 sta
Reading cookbook
http://upstart.ubuntu.com/cookbook/#restart-a-job-on-a-particular-event
This extra task job should solve both start & restart of avahi-daemon and
reload cups appropriately.
$ cat /etc/init/avahi-cups-reload.conf
start on started avahi-daemon
task
exec reload cups
Thus with no c
post-start script
if status cups | grep start/running; then
reload cups;
fi
end script
See http://upstart.ubuntu.com/cookbook, we want to check for cups that
we are managing (not any other) & reload will send to our cups HUP to
reload.
--
You received this bug notification becaus
25 matches
Mail list logo
