until we know why resolvconf is failing to start for you on boot
We know that the resolvconf job starts, otherwise /run/resolvconf
wouldn't exist. The problem is that the job also get stopped.
I added touch commands to the scripts which show this.
Yes, I think that Debian bug report #483098 gives the background
information needed to understand what's going on here.
Bind9 should certainly not by default send its (loopback) address to
resolvconf. Bind9 should only send its address to resolvconf if it is
known that named can provide general
I actually upgraded to 1.4-0ubuntu7 yesterday so when I look in
/var/log/upstart/resolvconf.log now I see the results of several
reboots: yes, there they are, repeated instances of:
cp: cannot create regular file `/var/spool/postfix/etc/resolv.conf':
Read-only file system^M
run-parts:
Thomas, is there any chance that you have postfix installed
in the environment where you're seeing the resolvconf job
fail at boot?
Yes, postfix was installed and was causing the resolvconf job to fail at boot.
See https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/933566/comments/6.
So the answer to my question (#16) was that the resolvconf Upstart job
was failing to start at boot time because of #927803.
The misbehavior reported here (#929552) occurs post-boot so I am
doubtful that it has the same cause.
--
You received this bug notification because you are a member of
I installed postfix 2.8.7-1ubuntu1. It still causes the resolvconf job
to fail at boot.
$ status resolvconf
resolvconf stop/waiting
$ dpkg -l postfix|grep ^ii
ii postfix
2.8.7-1ubuntu1
Regarding comment #29: Report #933723 was traced to a bug in bind9 --
different issue from the one here (#923685).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/923685
Title:
Installing resolvconf
Steve Langasek wrote:
Conceptually, I think there's no reason not to use
post-stop since the post-stop script is run before
the stopped event is emitted, so I'll go ahead with
committing this fix [...]
Using post-stop has the consequence that any error during the resolvconf update
run in
An alternative might be to use post-start (whose exit status is ignored)
so long as we use post-stop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933566
Title:
Stopping resolvconf doesn't disable
*** This bug is a duplicate of bug 929552 ***
https://bugs.launchpad.net/bugs/929552
asbenicio: Is this behavior reproducible? What if you upgrade from
11.10?
We need more information before we can make any progress with this bug.
--
You received this bug notification because you are a
In natty, Compiz plays a sound for the beep (e.g., the terminal bell) if
you do this first:
* pactl upload-sample /usr/share/sounds/gnome/default/alerts/glass.ogg bell.ogg
* xset b 100
I have added these commands to my ~/.xprofile script.
--
You received this bug notification because you are a
5) gnome-volume-control doesn't.
The Sound Effects tab of gnome-volume-control
offers to set the volume and sound for system bell
events, but these have no effect. This is because
gnome-volume-control is trying to control system
bells through metacity. Ideally, it should be rewritten
to
Regarding ThinkPad throttling the CPU when powered by the 65 W AC adapter and
no battery, see
http://forums.lenovo.com/t5/X-Series-Tablet-ThinkPad-Laptops/X61-Your-power-adapter-may-be-cheating-you/td-p/17870
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
It was mentioned earlier but not so explicitly: ThinkPad firmware
throttles the CPU if the machine is running on a 65W power supply with
no battery installed.
See, e.g., http://forums.lenovo.com/t5/X-Series-Tablet-ThinkPad-
Laptops/X61-Your-power-adapter-may-be-cheating-you/td-p/17870
--
You
I experienced this problem (sudden shutdown due to overheating) on a
ThinkPad X61. I worked around it by manually setting the fan speed
higher when performing CPU-intensive tasks (e.g., installing an OS on a
guest virtual machine).
Will now install thinkfan which should automate this.
--
You
Yes, there is an Alert volume slider with Mute button. I didn't
realize that you were referring to this when you said system bell ---
I didn't know that they were the same thing. My apologies. It's true
that this slider has no effect on the volume of the sound that gets
played when the
I have since discovered that it is necessary to put
pactl upload-sample /usr/share/sounds/gnome/default/alerts/glass.ogg
in ~/.xprofile, and
xset b 100
in ~/.bashrc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
a workaround for bugs
in applications which don't work properly with
127.0.1.1 --- HOSTNAME.
But it is better to fix those bugs than to rely upon a
workaround.
This report can be closed.
--
Thomas Hood
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Although problems with resolving the local hostname appear finally to be
getting solved, I think it would still be good to create an explicit
policy describing the (default) contents of /etc/hostname,
/etc/nsswitch.conf and /etc/hosts. The policy should also describe how
applications are expected
Reported to be a bug in krdc rather than in resolvconf.
** Package changed: resolvconf (Ubuntu) = kdenetwork (Ubuntu)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdenetwork in Ubuntu.
https://bugs.launchpad.net/bugs/262042
Title:
Just a comment about the earlier alleged bug in resolvconf. If
resolvconf and NetworkManager are fighting over resolv.conf then the
solution is to make NetworkManager use resolvconf rather than fight it.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is
*** This bug is a duplicate of bug 349469 ***
https://bugs.launchpad.net/bugs/349469
Submitter (Fabio Tinteri): How did you solve this problem? Was a reboot
sufficient?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 349469 ***
https://bugs.launchpad.net/bugs/349469
Submitter (y.srinivas): How did you solve this problem? Was a reboot
sufficient?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- package resolvconf 1.63ubuntu9 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
+ dist-upgrade: resolvconf 1.63ubuntu9 postinst fails with start: Unknown job:
resolvconf
--
You received this bug notification because
Hmm, must read up on biosdevnames At
http://en.community.dell.com/techcenter/b/techcenter/archive/2011/10/06
/announcing-the-release-of-biosdevname-0-3-11.aspx we learn:
Embedded devices: emX_Y (X = embedded LOM ID, Y = NPAR NIC index) -- e.g.,
em1_1, em1_2, em2,
Add-in cards:
Here's a patch I have just applied to the Debian package (in git) to add
the biosdevnames patterns. Beyond that it fixes a documentation bug.
** Patch added: Patch to add biosdevnames patterns and tweak documentation
OK, thanks for the clarification. Here's an updated patch.
** Patch added: Patch to add biosdevnames patterns and tweak documentation
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/949473/+attachment/2836989/+files/resolvconf-add-biosdevnames_20120308th3.patch
--
You received
*** This bug is a duplicate of bug 349469 ***
https://bugs.launchpad.net/bugs/349469
** This bug has been marked a duplicate of bug 349469
debconf: DbDriver config: /var/cache/debconf/config.dat is locked by
another process: Resource temporarily unavailable
--
You received this bug
*** This bug is a duplicate of bug 349469 ***
https://bugs.launchpad.net/bugs/349469
Submitter of #960907: Please read #349469 which includes suggestions for
working around the bug and requests for information about what happens
when this bug bites. Please follow up to #349469.
--
You
* In one of the dupes (#380491) the submitter says that running tasksel
(not as root) simultaneously with dpkg --configure --pending (as root)
results in the error message.
* In #419100 the submitter suggests that update-manager is conflicting
with itself when spawned in Automatic update /
** Changed in: resolvconf (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957679
Title:
package resolvconf 1.63ubuntu9 failed to install/upgrade:
Public bug reported:
When running dpkg-reconfigure I don't think I should get a warning about
something over which I have no control, namely, the running of /lib/init
/upstart-job by dpkg-reconfigure.
# dpkg-reconfigure -pcritical resolvconf
Rather than invoking init scripts through
There is no shortage of duplicates of this report. I am inclined to
guess that in many cases faulty package scripts are leaving processes
around which fail to release the config.dat lock under some
circumstances.
In order to test this hypothesis I'd like to go back in time and in each
of the
Thanks for the report!
I have applied the attached patch to the Debian package.
--
Thomas
** Patch added: resolvconf manpage fix
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/953257/+attachment/2861349/+files/resolvconf-manpage-dhcp-fix.patch
--
You received this bug
** Changed in: resolvconf (Ubuntu)
Status: New = Confirmed
** Changed in: resolvconf (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949473
** Changed in: resolvconf (Ubuntu)
Status: New = Confirmed
** Changed in: resolvconf (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953257
I think we agree on the main principle, which is: append, unless we are
confident that dynamic nameserver information will be supplied. In the
case of ifupdown the condition means: there is a logical interface
definition that is either dhcp or contains dns-nameservers.
#26 differs from #33 only
Upstart sees resolvconf as a persistent job and keeps track of its
state, running or stopped. One significance of this is that Upstart
won't start resolvconf if it is already running or stop it if it is
already stopped.
The part of resolvconf that conforms to this model is the enabling and
Public bug reported:
For background see #933566.
When Upstart attempts to start a job and the pre-start script returns an
error, Upstart will consider the job not to have been started.
Because resolvconf is treated as an Upstart job, resolvconf updates
being enabled/disable should correspond to
The original issue here (#933566), Stopping resolvconf doesn't disable
updates, has already been addressed (by switching to post-stop from
pre-stop) so I will open a new bug report (#936835) about the additional
measure of ignoring errors on enabling/disabling updates.
--
You received this bug
Note the parentheses around update_and_exit -u. They are needed
because the update_and_exit function execs run-parts. With the
parentheses the || : won't have any effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
s/With the parentheses/Without the parentheses/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936835
Title:
Resolvconf error condition on enable/disable update should reflect
success of just that
(we can guard against the possibility of a reboot between
preinst and postinst easily enough[...])
Fix for this has been committed: http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/precise/resolvconf/precise/revision/47
--
You received this bug notification because you are a member of
Once #936835 is fixed, the likelihood of the resolvconf Upstart job
failing to start will be reduced and the installation failures reported
here (#929552, #929641) might disappear --- without the underlying
cause(s) being eliminated.
Once #936835 is fixed, that is, the resolvconf Upstart job
*** This bug is a duplicate of bug 933723 ***
https://bugs.launchpad.net/bugs/933723
** Changed in: resolvconf (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 933723 ***
https://bugs.launchpad.net/bugs/933723
Steve: I don't see the similarity between this report (about
/sbin/resolvconf exit status) and #933723 (about bind9 calling
resolvconf when it shouldn't). Can you explain a bit?
In any case, I see you have
*** This bug is a duplicate of bug 927803 ***
https://bugs.launchpad.net/bugs/927803
I have installed 1.63ubuntu8 and everything seems to work perfectly now
on my Oneiric-with-some-Precise-bits laptop.
$ dpkg -l resolvconf postfix upstart
[...]
ii postfix2.8.7-1ubuntu2
my /etc/resolv.conf file got blown away
[...]
But guess what, no more clean reboots. Each reboot requires an ifdown/ifup
ritual.
As Steve mentioned, the resolvconf package was not an official part of
Ubuntu prior to 12.04. In earlier releases it was available from the
Universe repository
If and when that bug is fixed, the pre-stop script will
have the exact same effect.
If and when the bug is fixed the wiki documentation at
http://upstart.ubuntu.com/wiki/Stanzas#pre-stop
should also be updated so that it no longer implies
(by omission, compared with post-stop) that the
/resolvconf/resolv.conf.d/) end up with an absent resolv.conf file.) I
would appreciate if you would update to 1.63ppa6 and let me know whether or not
everything still works as it should on your systems.
--
Thomas Hood
--
You received this bug notification because you are a member of Ubuntu
Bugs
Well, if there was a dns-search option in a stanza that was activated
then the corresponding search option should have appeared in
resolv.conf. If that didn't happen then we need to figure out why it
did not.
Please let me know if, after fixing /etc/network/interfaces, resolv.conf
still isn't
that should precede dynamic and base material in resolv.conf should
be placed in /etc/resolvconf/resolv.conf.d/head.
--
Thomas Hood
Debian resolvconf maintainers
** Bug watch added: Debian Bug tracker #64
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=64
--
You received this bug
Now on the subject of what you are trying to do.
You say:
In an effort to make sure my libvirt dnsmasq is always
first in my list of resolvers, I have installed the resolvconf
package and added the following to
/etc/resolvconf/resolv.conf.d/base:
[...]
nameserver 192.168.122.1
But
Question: What has to happen before 32-bit keycodes can be used in
Ubuntu? If the work will be done, when is it likely to be finished?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/408903
Title:
*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
Thanks for the report.
This bug was fixed in version 1.63. Please install the latest
resolvconf package from the Precise archive. This will work fine on
11.10.
** Changed in: resolvconf (Ubuntu)
*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
** This bug has been marked a duplicate of bug 366967
ifupdown-udev integration should be thought-out more thoroghly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Further to the advice in #72 above, I'd just like to point out that as
of udev version 175, default udev keymapping can be overridden by means
of a file in /etc/udev/keymaps/ named the same as the file in
/lib/udev/keymaps/ that it overrides.
Suppose, for example, you want to make use of the Zoom
** 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/911241
Title:
resolvconf ignoring dns-nameservers, dns-search in iface-stanzas
This bug report looks a lot like #366967 and its twelve duplicates,
which was closed by version 1.63ubuntu1.
Which version of the resolvconf package are you using?
If you aren't using at least 1.63ubuntu1, please upgrade, try again, and report
back.
--
Thomas Hood
--
You received this bug
** Changed in: resolvconf (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/911241
Title:
resolvconf ignoring dns-nameservers, dns-search in
The microphone mute key yields Linux key input event KEY_MICMUTE which
has the value 248. Add 8 to get the X KeyCode number, you get 256.
This is greater than the maximum KeyCode that X handles, 255.
See: http://www.x.org/wiki/XI2
The problem is similar to the problem with the Zoom hotkey
The dns-* lines in /etc/network/interfaces only affect ifup/ifdown. Are
you using ifup to configure your interfaces? Or are you using
NetworkManager, the default network configuration tool in Ubuntu?
What is the version number of the resolvconf package you have installed?
--
Thomas Hood
--
You
Try resolvconf 1.63ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/911241
Title:
resolvconf ignoring dns-nameservers, dns-search in iface-stanzas
To manage notifications about this bug go
Thanks very much for testing!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750423
Title:
update-rc.d: warning: resolvconf stop runlevel arguments (none) do not
match LSB Default-Stop values
To
Sander van Grieken is working with the Debian maintainers on an Ubuntu version
of upcoming Debian release 1.62. Follow developments on the resolvconf-devel
mailing list: http://lists.alioth.debian.org/mailman/listinfo/resolvconf-devel
--
Thomas Hood
Debian resolvconf developers
--
You
** Changed in: resolvconf (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894417
Title:
Please merge resolvconf 1.61 (universe) from Debian
** Changed in: resolvconf (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871058
Title:
package bind9 1:9.7.3.dfsg-1ubuntu2.2 failed to install/upgrade:
** Changed in: resolvconf (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797339
Title:
apparmor profile for bind. resolvconf error
To manage
** Changed in: resolvconf (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/378844
Title:
resolvconf fails to install/upgrade because of immutable
** Changed in: resolvconf (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750423
Title:
update-rc.d: warning: resolvconf stop runlevel arguments
** Changed in: resolvconf (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366967
Title:
ifupdown-udev integration should be thought-out more
** Changed in: resolvconf (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/471975
Title:
Installing bind9 and resolvconf at the same time fails
To
/resolvconf) and let me know whether or
not you have any problems with it.
--
Thomas Hood
Debian resolvconf maintainers
resolvconf-de...@lists.alioth.debian.org
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
/resolvconf) and let me know whether or
not you have any problems with it.
--
Thomas Hood
Debian resolvconf maintainers
resolvconf-de...@lists.alioth.debian.org
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
the resolvconf package from ppa:jdthood/resolvconf
(https://launchpad.net/~jdthood/+archive/resolvconf) and let me know whether or
not you have any problems with it.
--
Thomas Hood
Debian resolvconf maintainers
resolvconf-de...@lists.alioth.debian.org
--
You received this bug notification because you
the resolvconf package from ppa:jdthood/resolvconf
(https://launchpad.net/~jdthood/+archive/resolvconf) and let me know whether or
not you have any problems with it.
--
Thomas Hood
Debian resolvconf maintainers
resolvconf-de...@lists.alioth.debian.org
--
You received this bug notification because you
the resolvconf package from ppa:jdthood/resolvconf
(https://launchpad.net/~jdthood/+archive/resolvconf) and let me know whether or
not you have any problems with it.
--
Thomas Hood
Debian resolvconf maintainers
resolvconf-de...@lists.alioth.debian.org
--
You received this bug notification because you
Thanks to Paul Smith for explaining (#27) how resolvconf is supposed to
work. For a more detailed explanation please read the README file in
the resolvconf package.
When resolvconf and NM are both installed the current behavior is this:
The Ubuntu version of resolvconf immediately returns an
or
not you have any problems with it.
--
Thomas Hood
Debian resolvconf maintainers
resolvconf-de...@lists.alioth.debian.org
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871058
Title:
package bind9
or
not you have any problems with it.
--
Thomas Hood
Debian resolvconf maintainers
resolvconf-de...@lists.alioth.debian.org
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797339
Title:
apparmor
or
not you have any problems with it.
--
Thomas Hood
Debian resolvconf maintainers
resolvconf-de...@lists.alioth.debian.org
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750423
Title:
update-rc.d
or
not you have any problems with it.
--
Thomas Hood
Debian resolvconf maintainers
resolvconf-de...@lists.alioth.debian.org
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/471975
Title:
Installing
or
not you have any problems with it.
--
Thomas Hood
Debian resolvconf maintainers
resolvconf-de...@lists.alioth.debian.org
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/378844
Title:
resolvconf
and you can help to
improve the quality of the package ultimately uploaded, thus benefitting other
users.
--
Thomas Hood
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/448095
Title:
resolvconf starts
Is there really no solution to this, in an LTS distro? Seriously?
Keep in mind that resolvconf is from universe.
But still, if resolvconf is going to be offered for Ubuntu then critical
bugs in the Ubuntu patch need to be fixed.
--
You received this bug notification because you are a member
Fixed in Debian resolvconf 1.59.
** Changed in: resolvconf (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/378844
Title:
resolvconf fails to install/upgrade
resolvconf -a $X for some value of X. By convention X
has the value ${INTERFACE}.${SUPPLIER} but not all suppliers follow
this convention. So resolvconf can't be sure what interface should be
checked. If a workaround were implemented it would have to be narrowly
focussed on the vpnc case.
--
Thomas
Possibly the same issue as http://bugs.debian.org/258553 -- gnome-
system-tools incompatible with resolvconf
** Bug watch added: Debian Bug tracker #258553
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=258553
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is Debian bug #551999 which was fixed in Debian resolvconf release
1.49. The current version of resolvconf in Debian is 1.58.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/471975
Title:
It is hard to see how the described (mis)behavior can be the fault of
the resolvconf package. If there is (still) a bug, then this report
needs to be reassigned.
--
Thomas Hood
Debian resolvconf maintainers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
. It's a helper for update scripts.
No bug here.
--
Thomas Hood
Debian resolvconf maintainers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/58417
Title:
resolvconf's list-records should chdir
names
different from physical interfaces. Basically, g-s-t does not play well
with Debian network configuration tools.
So either don't use resolvconf or don't use the network configuration feature
of g-s-t.
--
Thomas Hood
Debian resolvconf maintainers
--
You received this bug notification
** Changed in: resolvconf (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/471975
Title:
Installing bind9 and resolvconf at the same time fails
To
** Changed in: resolvconf (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366967
Title:
ifupdown-udev integration should be thought-out more thoroghly
To
** 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/172367
Title:
resolv.conf search list truncated - not to specification
To
** Summary changed:
- resolvconf does not play nicely with dhclient.conf customisations
+ gnome-system-tools network-admin does not play nicely with resolvconf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: resolvconf (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/58417
Title:
resolvconf's list-records should chdir to resolv.conf.d
To manage
** Summary changed:
- /etc/init.d/resolvconf start clobbers resolv.conf information
+ /etc/init.d/resolvconf start is run too late, clobbering resolv.conf
information
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
not, depend on anything in
/usr.
Because /sbin/resolvconf runs under bash, and bash contains a [ builtin,
there is no need to access /usr/bin/[.
--
Thomas Hood
Debian resolvconf maintainers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Public bug reported:
Xsession(5) still says that $HOME/.xsession can contain commands for
invoking X clients. But in natty $HOME/.xsession does not get run.
(/etc/X11/Xsession sources all the scripts in /etc/X11/Xsession.d/ and
/etc/X11/Xsession.d/50x11-common_determine-startup only sources the
501 - 600 of 3724 matches
Mail list logo
