This bug was fixed in the package resolvconf - 1.63ubuntu14
---
resolvconf (1.63ubuntu14) precise-proposed; urgency=low
* Call db_go after the db_input command so that the debconf error
message is actually shown to the user.
resolvconf (1.63ubuntu13) precise-proposed;
** Changed in: resolvconf (Ubuntu Precise)
Assignee: Steve Langasek (vorlon) = sidnei (sidneilord)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989585
Title:
resolvconf failed to
sidnei: Please don't change the assignee of the bug unless you're the
one working on the fix.
** Changed in: resolvconf (Ubuntu Precise)
Assignee: sidnei (sidneilord) = Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tested here with two LXC containers, both of them running up to date oneiric
amd64 with chattr +i /etc/resolv.conf.
I then updated the sources.list for s/oneiric/precise/, updated the list and
installed resolvconf. First container didn't have -proposed, the second one did.
Log for the first
Looking through the diff, it looks like we want the debconf warning to
show up in such case, but it doesn't.
So I wouldn't consider the SRU verification-done just yet, I'll check
with Steve whether that was indeed the planned behaviour and if not, add
a db_go call after the db_input entry in
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989585
Title:
resolvconf failed to install/upgrade because /etc/resolv.conf
This now works properly with ubuntu14 (only delta from ubuntu13 is the
added db_go call).
** Tags removed: verification-failed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: bugpattern-written
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989585
Title:
resolvconf failed to install/upgrade because /etc/resolv.conf
immutable
To manage notifications
hi Steve,
maybe i've too quickly blame that newest package: before upgrading it ip was
resolved normally, then after upgraded ubuntu13 i've got cant resolve url
error, so i've downgraded to ubuntu12 and the issue was solved. That why i've
posted the comment #22 above. So now i'm using ubuntu12
WARNING:
latest Precise-proposed resolvconf 1.63ubuntu13 break the network, need
to downgrade to ubuntu12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989585
Title:
resolvconf failed to
On Tue, May 08, 2012 at 07:20:09AM -, dino99 wrote:
latest Precise-proposed resolvconf 1.63ubuntu13 break the network,
It certainly does not, the only changes between 12 and 13 are to fix the
detection of an immutable bit on /etc/resolv.conf. What exactly is the
problem you're seeing?
--
Hello Chris, or anyone else affected,
Accepted resolvconf into precise-proposed. The package will build now
and be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in
** Branch linked: lp:ubuntu/precise-proposed/resolvconf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989585
Title:
resolvconf failed to install/upgrade because /etc/resolv.conf
immutable
To
Unfortunately, bug #994539 is a regression introduced by this change.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989585
Hello Chris, or anyone else affected,
Accepted resolvconf into precise-proposed. The package will build now
and be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in
Another report of this issue was #378844.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989585
Title:
resolvconf failed to install/upgrade because /etc/resolv.conf
immutable
To manage
This bug was fixed in the package resolvconf - 1.65ubuntu1
---
resolvconf (1.65ubuntu1) quantal; urgency=low
* Merge from debian unstable. Remaining changes:
- Make /etc/resolv.conf a relative symlink so that it works when
setting up chroots.
- Instead of throwing an
Steve: I've been looking at #989096. I Googled upon a Turkish-language
discussion of using chattr to solve resolv.conf problems. In that
discussion there is talk of doing chattr +a or chattr +ia.
If the a attribute is set on a file then ln -nsf fails to remove the
file.
--
You received this
** Changed in: resolvconf (Ubuntu Precise)
Status: Triaged = In Progress
** Changed in: resolvconf (Ubuntu Quantal)
Status: Triaged = In Progress
** Changed in: resolvconf (Ubuntu Precise)
Assignee: (unassigned) = Steve Langasek (vorlon)
** Changed in: resolvconf (Ubuntu
** Description changed:
+ [Impact] because Network Manager historically would overwrite users'
+ local DNS resolver settings on the desktop, a fair number of users have
+ marked this file immutable on the filesystem. This causes an upgrade
+ failure when going to 12.04, which makes resolvconf a
Good to hear.
Although this is a problem arising from administrator actions and
although it's easy to fix by hand, the large number of reports justifies
automating the solution, as Steve argues (and has already implemented
and committed).
--
You received this bug notification because you are a
Hi. My system was set up for a static IP and a local area name server.
Network Manager was at one point overwriting my resolv.conf changes ...
I may have set the immutable attribute at some point while wrestling
with that process. In fact, I am fairly certain I did. I followed the
procedure (dpkg
I think that fixed it
Good to hear.
How did /etc/resolv.conf become immutable on the affected system? Did
the administrator do it with chattr?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989585
Honestly, I don't knowI am the Admin and its my desktop. I don't
remember messing with /etc/resolv.conf, but I can't swear I didn't at
some point in the past.
I just thought that the error thrown up was caused by a glitch in the
upgrade process. Usually, I don't upgrade OS'esI wipe and
Your report is actually very helpful. Without reports like yours we
wouldn't know that people are encountering problems.
You aren't the first one to report that /etc/resolv.conf was immutable
when the resolvconf package was installed. It was in response to an
earlier such report that code was
On Fri, Apr 27, 2012 at 01:49:10PM -, Thomas Hood wrote:
But when enough people report exactly the same error it has to make one
wonder if there isn't something else going on. Is there, for example, a
web page out there somewhere that advises people to set the immutable bit
on
We may want to deal with this automatically on upgrade. Reopening.
** Changed in: resolvconf (Ubuntu)
Status: Invalid = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989585
Title:
** Changed in: resolvconf (Ubuntu)
Importance: Undecided = High
** Also affects: resolvconf (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: resolvconf (Ubuntu Quantal)
Importance: High
Status: Triaged
** Changed in: resolvconf (Ubuntu Precise)
I don't know of a specific web page to point to,, but a quick Google
search for resolv.conf chattr turns up quite a number of hits...
However, it seems like people who have done this on their machines have
had some specific reason to take an interest in the specific contents of
their resolv.conf
On Fri, Apr 27, 2012 at 08:57:51PM -, Nathan Stratton Treadway wrote:
However, it seems like people who have done this on their machines have
had some specific reason to take an interest in the specific contents of
their resolv.conf file, and I wonder if silently undoing that will
causes
Initial proposed fix for this pushed to bzr.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989585
Title:
resolvconf failed to install/upgrade because /etc/resolv.conf
immutable
To manage
** Branch linked: lp:~vorlon/ubuntu/precise/resolvconf/lp.989585
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989585
Title:
resolvconf failed to install/upgrade because /etc/resolv.conf
Yes, there is a web page. I set mine because the network manager keep
trying to switch me over to DHCP from a static IP address and searching
on the internet turned up this solution, which worked great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
33 matches
Mail list logo
