Leaving a domain breaks NetworkManager DHCP
Bug #354498 reported by
Thierry Carrez
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
likewise-open (Ubuntu) |
Fix Released
|
Medium
|
Thierry Carrez | ||
likewise-open5 (Ubuntu) |
Fix Released
|
High
|
Thierry Carrez |
Bug Description
Binary package hint: likewise-open5
As reported in bug 352934:
After the uninstall, and reboot, when I login (with a local account) my network no longer works. I just see the animated connecting icon. This never stops and I never get an address. If I reconfigure to use a static address, then networking is OK. If I change back to DHCP (good for home and work), then no address again. Not good.
Changed in likewise-open5 (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in likewise-open (Ubuntu): | |
assignee: | nobody → ttx |
importance: | Undecided → Medium |
status: | New → In Progress |
To post a comment you must log in.
Leaving the domain fails to correctly restore various modified files, including /etc/apparmor. d/abstractions/ nameservice. likewise>
It removes everything at the end of the original file:
# likewise
#include <abstractions/
# mdnsd
#include <abstractions/mdns>
# kerberos kerberosclient>
#include <abstractions/
# TCP/UDP network access
network inet stream,
network inet6 stream,
network inet dgram,
network inet6 dgram,
This triggers various apparmor rules resulting in applicative breakage, of which DHCP failure in NetworkManager is probably just the visible tip of the iceberg.
Workaround is to run: d/abstractions/ nameservice. lwidentity. orig /etc/apparmor. d/abstractions/ nameservice
sudo cp /etc/apparmor.
Then reboot the machine