Guess you'd have to ask Clem and team about that one. I realize that
Linux Mint is based on Ubuntu as is Kubuntu. Recall, I run the KDE
version of Mint. So perhaps the Kubuntu folks made the change?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for checking, Bob.
I am only surprised that /etc/resolv.conf points to
../var/run/resolvconf/resolv.conf instead of
../run/resolvconf/resolv.conf (as is normal in Ubuntu). Did Linux Mint
make this change, and if so, why?
--
You received this bug notification because you are a member of
Hey Thomas -
Okay, I just installed Linux Mint 14 64-bit KDE. (I was running Mint 13
KDE LTS.)
Immediately after the install the first thing I did was run the
following:
bob@elaterite ~ $ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 33 Dec 23 14:58 /etc/resolv.conf -
I wrote that. The last sentence is a bit ugly but I was trying to keep
it short. More explicit would have been the following.
After a typical installation of Ubuntu 12.04, /etc/resolv.conf is a
symbolic link to ../run/resolvconf/resolv.conf. If, at the time the
machine is upgraded to Ubuntu
FYI Thomas: follow this link
https://wiki.ubuntu.com/QuantalQuetzal/ReleaseNotes/Kubuntu and scroll
down to Networking it states:
Networking
In order to improve compatibility with other local nameserver packages,
NetworkManager now assigns IP address 127.0.1.1 to the local nameserver process
If you ever re-install the system please check, right after initial
installation, before upgrading, whether or not /etc/resolv.conf is a
symlink.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Sure. It looks like the Mint team has released a version 14 RC in KDE.
When the stable comes out I might switch to it. For some reason, I can't
seem to resolve an annoying issue with Dolphin that I'm having in Mint
13.
--
You received this bug notification because you are a member of Ubuntu
Same thing happened to resolvconf--upon running the upgrades.
What was the resolvconf version before the upgrade? And after? What
packages were upgraded? Can you attach the /var/log/apt/history.log,
/var/log/apt/term.log and /var/log/dpkg.log files covering the upgrade?
These might contain
Looks like:
resolvconf:amd64 1.63ubuntu14
with
resolvconf:amd64 1.63ubuntu16
Hope that helps!
** Attachment added: Requested log files
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+attachment/3451232/+files/logs.txt
--
You received this bug notification because you
Thanks for the info — very helpful.
Looking at the apt logs I see an upgrade done at 2012-12-03 18:23:13.
Do I understand correctly that resolvconf worked correctly before this
upgrade? Thus /etc/resolv.conf was a symbolic link to
../run/resolvconf/resolv.conf before the upgrade?
During the
(Just filed bug #1086336 against kppp.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
/etc/resolv.conf symlink does not exist after initial installation of
resolvconf package
To
Thomas -
Both installs began with fresh ISOs of Linux Mint 13, 64bit KDE.
After the initial install I have no idea if there were any errors as I
didn't bother to look at the install logs.
The only time I've noted the resolvconf error was doing the requisite
post install package upgrades, which
I had interpreted your comment #85 as meaning that the problem appeared
when you upgraded, but it turns out that we can't be sure that the
problem wasn't there from the beginning. I would guess, then, that the
problem was there at the beginning, after installation, because we have
seen other
@Bob: Thanks for the information. Interesting case.
* /etc/resolv.conf is not a symbolic link to ../run/resolvconf/resolv.conf
* Updates are not enabled
* A postponed update has been scheduled
* Nothing has been stored in the interfaces database
I can only guess how this set of conditions came
@Thomas thanks for the update. FYI: I did a re-install with a new copy
of the image freshly downloaded from the Linux Mint repository. Same
thing happened to resolvconf--upon running the upgrades. (I think I
forget to mention that before.) ;)
Cheers!
--
You received this bug notification
Okay, so I installed Linux Mint 13 KDE 64bit last night and received
this resolv symlink does not exist error.
So I've recorded the outputs that @Thomas request below. I hope they
help!
---
elaterite ~ # ls -l /etc/resolv.conf
ls: cannot access /etc/resolv.conf: No such file or directory
I just heard (http://askubuntu.com/questions/139654/network-connection-
on-ubuntu-12-04-20-seconds-to-load-a-web-
site/140201#comment260660_140201) that FortiClient SSL VPN client is
another third-party program guilty of trashing /etc/resolv.conf.
Here's a new summary of the possible causes of
@rjasmin: If you are running Debian, please file a bug report in the
Debian bug tracking system. See http://www.debian.org/Bugs/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
this is a debain bug, once again working its way into UBUNTU core.
Running WHEEZY.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
/etc/resolv.conf symlink does not exist after initial
I wrote:
I will file a new bug report requesting that this finally be implemented.
Filed as bug #1072341.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
/etc/resolv.conf symlink
@Cerin: You say that disabling and re-enabling wireless connection
corrects resolv.conf. Please run the following commands when
resolv.conf is correct, so we know what you mean by that.
cat /etc/resolv.conf
ls -l /run/resolvconf/interface
for F in /run/resolvconf/interface/* ; do
On Wed, Oct 24, 2012 at 7:39 AM, Thomas Hood 1000...@bugs.launchpad.net wrote:
@Cerin: You say that disabling and re-enabling wireless connection
corrects resolv.conf. Please run the following commands when
resolv.conf is correct, so we know what you mean by that.
cat /etc/resolv.conf
Cerin, in your earlier comment (#75) you posted the results of several
commands. The content of /etc/resolv.conf was incorrect. It was:
# Generated by NetworkManager
domain home
search home
nameserver 127.0.0.1
If this file had been generated by resolvconf, it would have begun
On Tue, Sep 18, 2012 at 5:43 PM, Thomas Hood 1000...@bugs.launchpad.net wrote:
@Cerin: We need to find out which program it is that is not interfacing
correctly with resolvconf.
So far as I know all Ubuntu software interfaces correctly with
resolvconf. It is known that some third party
Another data point. I just stumbled across AskUbuntu question #137037
and noticed that seven people have voted up the answer to run dpkg-
reconfigure resolvconf. That suggests that seven people had to run
that command, i.e., that seven people were lacking the symlink for some
reason.
OK, got a reply from Linode. I will pursue the matter and report back
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
/etc/resolv.conf symlink does not exist after initial
@Solomon: Linode tech support has told me that Linode intentionally
removed the /etc/resolv.conf symlink. By default, all of their
distribution templates use DHCP to obtain the IPv4 address on the first
boot; dhclient is configured to write out a valid resolv.conf file at
/etc/resolv.conf. That's
@Solomon: Thanks for a very complete report.
Another faulty image, presumably because a faulty image-building tool
is being used.
More later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
I have just sent e-mail to Linode customer service bringing the issue to
the company's attention. I don't see a BTS open to non-customers, but
someone let me know if I've overlooked a more suitable communication
channel.
--
You received this bug notification because you are a member of Ubuntu
+++ I had the same problem as described above.. after doing sudo dpkg-
reconfigure resolvconf everything appears to be OK now. Repro and diag
info below +++
- Setup a new box with www.Linode.com. Took their image of: Ubuntu 12.04 LTS
64bit.
## Welcome to Ubuntu 12.04.1 LTS (GNU/Linux
Here's a new summary of the possible causes of the missing symlink for
each contributor to this report or to one of its duplicates.
Bad Linux Mint image (bug #1004421): toby-murray, albert-bendicho
Bad Ubuntu EC2 cloud image (bug #1003595): louisli
Bad Ubuntu Secure Remix image (bug #1051348):
I just completed an upgrade on a Precise Pangolin VM that wrote a file
to resolv.conf and which caused the name resolution to fail completely
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Hi Lisa. To address your problem we'll need some information. Please
post the output of the following commands.
dpkg -l resolvconf network-manager dnsmasq dnsmasq-base
ls -l /etc/resolv.conf
cat /etc/resolv.conf
ls -l /run/resolvconf
ls -l /run/resolvconf/interface
for F
@Cerin: The resolvconf package only creates the symbolic link
/etc/resolv.conf -- ../run/resolvconf/resolv.conf once, on initial
installation. The package can be caused to repeat this action by running
dpkg-reconfigure resolvconf and agreeing to linkify
/etc/resolv.conf. However, it is certainly
On Tue, Sep 18, 2012 at 10:52 AM, Thomas Hood
1000...@bugs.launchpad.net wrote:
if resolvconf locks up
Note that resolvconf doesn't lock up. It's not a daemon. It's just a
script that gets run by other software that needs to update nameserver
information.
That's what I mean. As you
@Cerin: We need to find out which program it is that is not interfacing
correctly with resolvconf.
So far as I know all Ubuntu software interfaces correctly with
resolvconf. It is known that some third party software doesn't interface
correctly with resolvconf. Are you using a VPN client? Which
An issue I've noticed is that `sudo dpkg-reconfigure resolvconf` doesn't
always fix the issue, because, as the program notes, a reboot is
sometimes required to actually refresh the cached dns info. This makes
using this on a laptop occasionally frustrating when traveling between
wifi hotspots or
@Taylor: Possibly the pre-Precise-release version of resolvconf had a
bug causing it to fail to create the symlink (or another pre-Precise-
release package had a bug causing it to remove the symlink); resolvconf
only makes one attempt to create the symlink, so even if the bug was
later fixed you
@Thomas
Sorry if my explanation doesn't suffice but... First I took the 12.04 image
that is the desktop-i386-32bit that was originally posted on Ubuntu website.
I installed it and added some minor stuff like Skype and VLC. Then to create a
bootable/redistributable copy of it I use remastersys
@BlueLight: Interesting, thanks. The message you referred to talks
about Debian Live. Seems that its live-installer program clobbers
resolv.conf. Unfortunately no one has filed a bug report about this ---
there's nothing relevant at http://bugs.debian.org/live-installer or at
still present on up-to-date Ubuntu installer iso 12.04 32-bit with Ubiquity
installer
Running sudo dpkg-reconfigure resolvconf fixes the issue (I have yes to
both questions that appear).
More info needed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Bendi: I believe that your problem arises from a bad image. See #bug
#1004421.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
/etc/resolv.conf symlink does not exist after initial
@BlueLight: Just to be clear, what is the exact image that you used to
install? Where did you get it? What is its md5sum?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
Here's a summary of (possible) causes of the missing symlink for the
contributors to this report.
Bad Mint image (bug #1004421): toby-murray, albert-bendicho
Bad EC2 cloud image (bug #1003595): louisli
Possibly some issue with ubuntu 12.04 amd64+mac image: cerin, peterlauri
Juniper AnyConnect
The dpkg-reconfigure indeed solved the problem. My initial install was
from the Maverick cycle, and I've usually done a commandline
distrubution upgrade around the Alpha2-3 of every cycle since.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Thomas Hood (jdthood): yes, I have to run it after installation, accept
defaults and it's all good after that.
NOTE: the installer ISO has no problem connecting though. I think it might have
to do with Ubiquity installer not doing it as the last step and skipping the
reconfiguration of
I have done a new installation with Linux Mint Maya (MATE-32 bit) and again I
have the same issue (no /etc/resolv.conf created).
This time, it is a brand new installation. No Updates installed, no VPN
software added.
Running sudo dpkg-reconfigure resolvconf fixes the issue (I have yes to
both
@Bendi: Thanks for providing good information about this failure case.
Would it be possible to mail me your /var/log/dpkg.log* and
/var/log/apt/* log files (in a tarball) and also let me know the exact
time of the sudo dpkg-reconfigure resolvconf you did? The log files
are time-stamped so if I
@BlueLight: to fix the problem on the affected system does it suffice to
do sudo dpkg-reconfigure resolvconf?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
/etc/resolv.conf symlink
** Changed in: resolvconf (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
/etc/resolv.conf symlink does not exist after initial
same issue here after creating a custom iso from a working system (with
remastersys) and installing from it.
/etc/resolv.conf not populated
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
** Tags added: mysterious
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
/etc/resolv.conf symlink does not exist after initial installation of
resolvconf package
To manage
Toby wrote:
However this does seem to be a move
Can you please check this with strace(1)? The move function is
rename(2). If you see something like the following in the output
[...]
rename(resolv.conf, resolv.conf.vpnbackup)= 0
[...]
Had to attach strace to the vpanagentd process that runs in the
background. Here is grep resolv.conf from the log covering firing up
the UI, connecting and disconnecting. So yes, it is indeed doing a
rename.
stat(/etc/resolv.conf, {st_mode=S_IFREG|0644, st_size=126, ...}) = 0
Good work. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
/etc/resolv.conf symlink does not exist after initial installation of
resolvconf package
To manage notifications about
Trying to find a solution for my problems with a clean installation of Linux
Mint 13/Maya (32bit-MATE) I got here.
I think I have the same issue.
BTW, as I see Cisco VPN mentioned, I have the vpnc packaged installed.
Output of commands requested previously to other users;
me@hostname ~ $ ls -l
What Toby and Bendi report is similar to what has been reported at
(Linux Mint) bug #1004421. There people say that doing dpkg-reconfigure
resolvconf and agreeing to linkify suffices to fix the problem.
Toby has the Cisco AnyConnect client installed. The submitter of bug
#1002783 (a duplicate of
Regarding the Cisco AnyConnect client (version 2.5.3041-k9):
$ strings vpnagentd | grep resolv.conf
/etc/resolv.conf
/etc/resolv.conf.vpnbackup
Regarding the Juniper Network Connect VPN client:
http://askubuntu.com/questions/156154/how-to-prevent-juniper-
Yes, the contents of my /etc/resolv.conf is the same as
/etc/resolvconf/resolv.conf.d/original
I'm pretty sure I didn't manually answer any questions about resolv.conf
when setting things up. I did a standard linux mint install and then at
a later point installed the Cisco AnyConnect client from
** Summary changed:
- resolv.conf not populated because /etc/resolv.conf symlink was not created
+ /etc/resolv.conf symlink does not exist after initial installation of
resolvconf package
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
60 matches
Mail list logo
