Since it's been reported by the original bug reporter that the issue has
"fixed itself", but we're not sure of the cause, marking as Invalid.
Michael, Vorik, if you're still having this issue please open a new bug
and report the number here so we can potentially different issues
separately, and I'
On Sat, 30 Oct 2010 04:04:28 you wrote:
> I have exactly the same issue. I have a static IP so I've been fixing
> it by manually editing resolv.conf every morning when I boot my machine
> at work. It's a small issue but it makes me question whether I upgraded
> to 10.10 too soon.
It seems to hav
I have exactly the same issue. I have a static IP so I've been fixing
it by manually editing resolv.conf every morning when I boot my machine
at work. It's a small issue but it makes me question whether I upgraded
to 10.10 too soon.
--
empty resolv.conf
https://bugs.launchpad.net/bugs/648367
Yo
I've got the same problem; upgraded to Maverick.
Contents of /etc/resolv.conf right after boot:
r...@huis:~# cat /etc/resolv.conf
# Generated by NetworkManager
search mydomain.nl
After running 'dhclient', the /etc/resolv.conf is filled properly.
r...@huis:~# cat /etc/resolv.conf
nameserver 192.
** Attachment added: "Dependencies.txt"
https://bugs.edge.launchpad.net/bugs/648367/+attachment/1640693/+files/Dependencies.txt
** Attachment added: "IfupdownConfig.txt"
https://bugs.edge.launchpad.net/bugs/648367/+attachment/1640694/+files/IfupdownConfig.txt
** Attachment added: "IpAddr
