Comment 9 for bug 1051348

No, I'm not running any VPN client, and I don't have any non-Ubuntu software installed except for Ubuntu Tweak, Faenza Icons, and YannUbuntu's Boot Repair. I don't recall when (or whether) I installed YannBuntu's Boot Repair, which makes me slightly uncertain about which image I installed from when I installed 12.04. There are definitely only two possibilities here: either (i) I installed from ubuntu-12.04.1-desktop-amd64.iso (http://releases.ubuntu.com/12.04/ubuntu-12.04.1-desktop-amd64.iso) or (ii) I installed from YannUbuntu's "Ubuntu Secure Remix" version (which includes Boot Repair), meaning from ubuntu-secure-remix-12.04.1-64bits.iso (here: http://sourceforge.net/projects/ubuntu-secured/files/). I am *almost* positive that I installed from the first one (the standard 64-bit 12.04 iso), but the fact that Boot Repair is on my system and I don't recall how it got there, together with the fact that I do have an iso for YannUbuntu's Ubuntu Secure Remix, now has me uncertain. So, sorry that I can't be definite about that. (My initial bug report, filed using apport, says this: "InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1).")

By the way, I skimmed through the duplicate bug report (#1000244) and noticed something that seems to be common to my case and all of the other cases involving Ubuntu. All of the Ubuntu cases seem to involve amd64 iso's. There are Linux Mint cases that involve 32-bit iso's, and there is an Ubuntu case that is 32-bit, but it appears to involve someone's unique issues with creating their own iso's from remastersys. The only cases in that bug's thread where someone actually had the problem after installing from an official Ubuntu source -- again, as I *think* I did, though I can't be absolutely sure given the above -- and didn't have an /etc/resolv.conf file are cases where the installer was amd64. Not sure whether that's even possibly significant or not, though.