FWIW: We've had problems with avahi-daemon getting stuck in registering
on 12.04 and ended up patching it from:
http://lists.freedesktop.org/archives/avahi/2014-March/002291.html
Work is available here:
http://bazaar.launchpad.net/~lmas/avahi/simpad/revision/107
--
You received this bug
Same problem on ubuntu 11.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/116984
Title:
Applications can't connect to avahi-daemon until avahi is restarted
once.
To manage notifications about
For streaming to an AirportExpress see lp:stream2ip for a GUI to stream
directly to the IP without the need for an Avahi name resolution.
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because
Still got this issue on Lucid 10.04...I always need to restart avahi-
daemon once to see the available services on the network.
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a
Same her on Lucid 10.04 LTS. Maybe this is all related to improper
handling updates of available services. My recent report (Bug #586229)
puts focus on this but still waits for confirmation. IMHO this bugreport
here is dead.
--
Applications can't connect to avahi-daemon until avahi is restarted
In lucid RC, restarting avahi-daemon or network-manager don't fix the
problem
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm having no success restarting avahi-daemon or network-manager - I
still get nothing with avahi-browse
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs,
I have the same issue as Takkat withe pulseaudio-raop module with an
airport express. Sometimes pulseaudio will just lose sight of the
Airport Express device on the network, and the only way to get it to
come back is by restarting avahi or the network.
--
Applications can't connect to
Similar or same (?) issue here on Karmic 9.10 am64 using avahi for
pulseaudio-streaming to an AirportExpress.
Avahi needs a restart of avahi-daemon or restart of network-manager
(both works) to resolve the airport.local device.
--
Applications can't connect to avahi-daemon until avahi is
** Branch linked: lp:ubuntu/karmic/avahi
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Right, I've tried to reproduce this with the help of my laptop. After
configuring it to make a wireless connection (with the iwl3945 Intel
PRO/Wireless driver) on boot, outside of NetworkManager, and installing
patched mt-daapd it successfully appears on a wired client's shared
library list in
Thanks a lot jay (jcornwall) for your precious help... My problem might
be related to some sort of bad NIC/router/something else combination...
(still, it's weird that it happens only since Jaunty upgrade, on 2
machines...)
Anyway, I've found a workaround, with a script that runs at boot to
The bad news is I wasn't able to reproduce this last night.
To simulate the problem, I did:
1) /etc/init.d/mt-daapd stop
2) /etc/init.d/avahi-daemon stop
3) /etc/init.d/networking stop
4) /etc/init.d/avahi-daemon start
5) /etc/init.d/mt-daapd start
(At this point, mt-daapd is registered but
Thanks for testing that.
This means it is likely that the problem lies with Avahi or in
miscommunication between mt-daapd and Avahi. The problem seems to be
this:
1) Avahi starts up.
2) mt-daapd connects and advertises its service.
3) DHCP assigns an IP to the system.
4) Avahi acknowledges the
... Yes, restarting mt-daapd (without restarting Avahi) fixes the
problem... So maybe the problem is not related to the current bug
report...?
As for the NIC, I doubt it is the cause of the problem, since I'm
experiencing the problem on 2 machines, with 2 different NICs (one using
ath9k driver
Can you paste your syslog entries for Avahi following a bad startup and
successful daemon restart?
From davebv's syslog, it appears that avahi-daemon is being started
before an IP address has been assigned to the machine. That's a startup
ordering issue (and secondarily a weakness in Avahi's
Regarding my above comment, I think I read that log a little too
quickly. avahi-autoipd is detecting a Zeroconf address but this is after
registering the correct IP on eth0, so this should work fine.
In addition to the relevant entries from your syslog, could you also say
which NIC you're using?
My NIC is an Atheros AR928X using the ath9k driver.
Heres my syslog after a bad startup:
May 11 06:25:11 ml-linux NetworkManager: info starting...
May 11 06:25:11 ml-linux avahi-daemon[3060]: Found user 'avahi' (UID 108) and
group 'avahi' (GID 120).
May 11 06:25:11 ml-linux
Hmm, that looks OK.
All I can think of is that mt-daapd registers with Avahi after it starts
but before it has registed an address record (due to the late DHCP). On
my system mt-daapd registers after Avahi has registered addesses.
One would expect Avahi to handle this gracefully but I am not
Same problem here on Jaunty. This problem is quite new for me, as I'm
using DAAP (i.e. mt-daapd or Firefly media server) since a couple of
years and I the problem was not occurring with previous versions
(Intrepid and others).
--
Applications can't connect to avahi-daemon until avahi is
I had this problem. After some digging, it turned out it was simply a
problem of python-avahi not being installed. After installation, it
seems to have resolved itself.
Since gajim without python-avahi isn't really a charm, why isn't python-
avahi at least recommended (or depended) by gajim? (Now
** Branch linked: lp:~rawler/ubuntu/jaunty/gajim/fix-avahi
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Branch unlinked: lp:~rawler/ubuntu/jaunty/gajim/fix-avahi
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I upgraded to Jaunty and it happens again, In intrepid worked ok.
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This is the log in syslog
http://paste.ubuntu.com/145289/
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I upgraded to Jaunty and it happens again, In intrepid worked ok.
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Sebastain,
I have heard nothing on this bug - disappointing. I will try again when I
have a chance to upgrade.
On Wed, Feb 25, 2009 at 1:22 AM, sebastianmarkow
i...@bastianmayhem.comwrote:
Ubuntu 8.10
avahi-daemon 0.6.23
same behavior here, disappears after a few minutes.
fyi, strange
Ubuntu 8.10
avahi-daemon 0.6.23
same behavior here, disappears after a few minutes.
fyi, strange behavior in addition to ssh, if the daemon is running ssh
establishment takes like 5 seconds.
if its stopped it doesn't take a blink to ask for pw, it's almost instantly.
i couldn't get in touch
Ubuntu 8.10
avahi-daemon 0.6.23
If the service provider is started after the client ( Ubuntu or Windows
XP) services are discovered. But if the service provider is already
running then no services are discovered when the client fires up.
invoke-rc.d avahi-daemon reload on provider allows
Reproduced this issue on Hardy.
Screen shot with (slightly) more info enclosed.
** Attachment added: avahi-no-boot.png
http://launchpadlibrarian.net/17132501/avahi-no-boot.png
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
** Changed in: avahi (Ubuntu)
Status: New = Confirmed
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I seem to have this problem on Hardy (tested with avahi-discover and
Gajim).
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
One more update:
I reverted to Feisty (for another reason) and tried employing the
workaround in /etc/init.d/avahi-daemon described above. It did not
work! Avahi-daemon did not detect the file change, so it did not reload
itself, and the services were not successfully established.
However,
Had same problem in Feisty
Still have same problem in Gutsy current (dist-upgraded Feisty -- Gutsy)
This is not limited to Gajim, as others have said
My avahi services do not get started reliably. Sometimes, after
rebooting, they start. 4 out of 5 times, they do not. I will give some
outputs
This bug was fixed in the package avahi - 0.6.22-2ubuntu2
---
avahi (0.6.22-2ubuntu2) hardy; urgency=low
* debian/patches/01_avahi-daemon.conf.patch: Disable IPv6 by default again.
It is not supported/recommended by upstream yet. (LP: #116984)
-- Martin Pitt [EMAIL PROTECTED]
the change fix issues but not likely this one
** Changed in: avahi (Ubuntu)
Importance: Undecided = Medium
Status: Fix Released = New
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification
Still seems present in hardy as well.
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I do appear to have the same issue under current gutsy.
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
This appears to be fixed in current Gutsy.
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I just tried and as far as I can tell this bug is not present in gutsy.
So if there is no chance to get a fix in feisty this bug should probably be
closed.
But if this chance exists there is still some work to be done tracking down the
change that fixed it.
Candidates are as far as I can tell:
It looks like avahi.daemon gets stuck while registering
(well, I know this is not really a good way of debugging at all, maybe someone
has better suggestions?)
Directly after booting:
[EMAIL PROTECTED]:~$ ps axf | grep avahi
5431 ?Ss 0:00 avahi-daemon: registering [silmaril.local]
I got exactly the same problem with telepathy-salut on Feisty. I have to
manually restart avahi-daemon and then it works just fine.
--
Applications can't connect to avahi-daemon until avahi is restarted once.
https://bugs.launchpad.net/bugs/116984
You received this bug notification because you
Just tested it. You seem to be correct that this does not only happen with
gajim (It just was the only application I noticed this with.
I changed the summary.
** Summary changed:
- Gajim can't connect to avahi until avahi is restarted once.
+ Applications can't connect to avahi-daemon until
43 matches
Mail list logo
