I'm also able to reliably reproduce this. I always see avahi-autoipd
processes like these pop up when the problem occurs:
$ ps aux | grep avahi-autoipd
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
avahi-a+ 31710 0.0 0.0 2440 816 ? S 10:15 0:00
avahi-autoipd: [eth0] bound 169.254.6.245
root 31711 0.0 0.0 2204 296 ? S 10:15 0:00
avahi-autoipd: [eth0] callout dispatcher
They disappear when I restart network manager.
$ sudo /etc/init.d/network-manager restart
But then they come back a few minutes later.
I haven't gotten any of the workarounds to resolve the issue so far.
Cheers,
Nathaniel Beaver
On 10/11/2014 02:41 AM, Stefano Zacchiroli wrote:
On Sat, Oct 11, 2014 at 12:48:25AM +0200, Tobias Hansen wrote:
Control: severity -1 serious
I'm also having this problem and setting AVAHI_DAEMON_DETECT_LOCAL=0
didn't help in my case. I also have this eth0:avahi entry in ifconfig.
Raising severity since we really don't want to have this bug in a release.
Same here: it is indeed avahi related (I invariably get a 169.254.7.253
address) but AVAHI_DAEMON_DETECT_LOCAL=0 doesn't help. I can now
reproduce it reliably at each suspend/resume cycle of my laptop.
Immediately after resume I connect properly to the local wi-fi then,
after 1-2 minutes, a new eth0 kicks in and kill the network. Opening the
settings panel and switching of the "wired" connection fixes the
problem, until the next suspend/resume cycle.
FWIW, I agree with your severity assessment.
Cheers.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
