Still happens on precise.
Looks like it's also reported in upstram tracker:
http://savannah.gnu.org/bugs/?25752
** Bug watch added: GNU Savannah Bug Tracker #25752
http://savannah.gnu.org/bugs/?25752
** Changed in: screen (Ubuntu)
Status: Invalid => New
--
You received this bug notif
@marrusl: fix doesn't seem to be in precise or even precise-updates yet,
the version mentioned byt @ingenium is probably from ppa:mathieu-tl/nm.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.
Thanks for the prompt response. I have to say I don't really agree with this
reasoning: the virbr0 interface is created
and managed by libvirt, and after libvirt is removed it will currently
disappear on system restart. I have a hard time imagining
someone removing libvirt and intending/expecting
Public bug reported:
The virbr0 interface with a rfc1918 address stays around after removing
libvirt-bin. I also tried reinstalling it and "stop libvirt-bin", that
didn't work either. Google found me some virsh incantations and "virsh
net-destroy default" finally did the trick.
ProblemType: Bug
D
This bug is ~2 years old and cripples ssh use pretty badly. People waste time
hunting it down and working around it by disabling avahi or ssh's gss-api
stuff. I just upgraded to Jaunty alpha and it's still the same.
Is there some mechanism to propose this be fixed before Jaunty is out (i'm not
t
