Yes, I'd say that wontfix is appropriate unless someone comes forward
with a reason why ntpd *should* listen at 127.0.1.1.
P.S. I earlier wrote the following.
It appears that bind9 operates in the same way.
I added a virtual interface eth0:0 with a bogus address
and named started listening
** No longer affects: bind
** Also affects: bind9 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483098
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Link to similar upstream bug report with title Please default to
RESOLVCONF=no (Upstream bug report #483098 is now being tracked in
Launchpad by wishlist bug #1091602 with title Please add resolvconf
hook script to generate dynamic forwarders list.)
** Bug watch added: Debian Bug tracker
** Description changed:
- This is a wish. It is requested that the bind9 package include a
- resolvconf hook script /etc/resolvconf/update.d/bind9 which writes a
- forwarders{} statement to /var/run/named/forwarders based on the
- nameserver information in resolvconf's database. Then in order
** Description changed:
It is requested that the bind9 package be enhanced such that named uses
forwarder addresses obtained from resolvconf's database.
Such a feature would normally be implemented by means of a resolvconf
update hook script, in this case
** Bug watch added: Debian Bug tracker #687507
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687507
** Also affects: resolvconf (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687507
Importance: Unknown
Status: Unknown
--
You received this bug notification
Stéphane?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1003842
Title:
dnsmasq sometimes fails to resolve private names in networks with non-
equivalent nameservers
To manage
To anyone else who wants this feature: You are cordially invited to add
your voice here. :-) Please explain how you intend to use the feature.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
David T wrote in comment #8:
- Loaded Ubuntu 12.04
- Tried to install [a package]
- couldn't resolve dns
Possibly this is just another instance of bug #1000244.
David T, can you reproduce the failure?
** Description changed:
ARGH! Every release causes new problems :(
If you have:
David, I suggest you get a Linux expert to help you at your location.
** Changed in: bind9 (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
@tombert: Probably not the same issue, since the issue being discussed
here is not fixed by restarting. Please file a new bug report against
dnsmasq with a detailed description of your problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Not a NM problem; probably a dupe of #933723.
** Package changed: network-manager (Ubuntu) = bind9 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1098152
Title:
DNS resolve
** Summary changed:
- dnsmasq 2.6.1 package update required for precise
+ Please backport dnsmasq 2.6.1 or later to Precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1103357
*** This bug is a duplicate of bug 1006898 ***
https://bugs.launchpad.net/bugs/1006898
** Description changed:
Ubuntu Precise currently ships with dnsmasq 2.59, but due to the issue
- reported in https://lists.launchpad.net/openstack/msg11696.html we
- require that to be updated in Precise
*** This bug is a duplicate of bug 933723 ***
https://bugs.launchpad.net/bugs/933723
** This bug has been marked a duplicate of bug 933723
bind9 registers itself with resolvconf even though it's unable to provide
name service
--
You received this bug notification because you are a
Compare bug #113417.
** Summary changed:
- host crashed with SIGSEGV in start_thread()
+ host crashed with SIGSEGV in start_thread() on login
** Summary changed:
- host crashed with SIGSEGV in start_thread() on login
+ host -t soa local. SIGSEGV in start_thread() on login
--
You received
** Summary changed:
- [apport] host crashed with SIGSEGV
+ [apport] host -t soa local crashed after resume from suspend
** Summary changed:
- [apport] host -t soa local crashed after resume from suspend
+ [apport] host -t soa local SIGSEGV after resume from suspend
--
You received this bug
** Description changed:
- The system dnsmasq is preventing nameservice from working with
- NetworkManager. By setting /etc/deafault/dnsmasq ENABLED=1 to ENABLED=0,
- nameservice started working again.
+ The standalone Dnsmasq (from the dnsmasq package) is preventing the
+
Robie is right. In the failure case the resolver is contacting
127.0.1.1, where the NetworkManager-controlled dnsmasq process listens,
rather than 127.0.0.1, where BIND named is listening.
Robie is right, too, in saying that the instructions you followed have
to be reinterpreted for Ubuntu. In
there's still the unresolved question
of whether re-enabling --strict-order
will suffice as a workaround, since
12.10 relies on DBus to populate the
nameservers. Is there any extra
information on this?
Please try it and report back. :-)
(Put strict-order in a file in
Simon in #49:
It doesn't work [...] the order of servers given to the DBus
interface isn't preserved internally
Aha, so the answer to my question
Will switching on strict-order have the same effect
now that nameserver addresses are sent over D-Bus?
(in comment #42) is No. So switching
Hi Simon.
Before I forget to ask: can you please update dnsmasq(8) to include
under --strict-order a description of what happens when nameserver
addresses are passed in via D-Bus instead of via a file?
You wrote,
you can very easily provide the same behaviour - only pass the first
nameserver
[...cont'd after in order to fix...] bug #1072899, dnsmasq will have
to be enhanced such that proposition #1 is true. But we can discuss the
details of that in bug #1072899.
parenthesis
There is a close analogy between the problem here (bug #1003842) and a problem
we have with avahi. Avahi
Simon wrote:
Consider
[...]
server=/google.com/3.3.3.3
server=/google.com/4.4.4.4
[...]
Queries sent to *google.com will be sent 3.3.3.3 or 4.4.4.4 in the
same way as if strict order was set, ie, to 3.3.3.3 first, and only to
4.4.4.4 if 3.3.3.3 returns a SERVFAIL or REFUSED error, or doesn't
Earlier there was some dispute about what the RFCs say about multiple
nameservers.
I found the following RFC which does have something to say about these
issues.
http://www.zoneedit.com/doc/rfc/rfc2182.txt
Here are a couple of passages...
Request for Comments: 2182
Category: Best Current
The target milestone should be adjusted, I guess.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1003842
Title:
dnsmasq sometimes fails to resolve private names in networks with
Put a line into /etc/dhcp/dhclient.conf like so:
prepend domain-name-servers 192.168.122.1;
The following doesn't address the main issue but does seem to me to be
worth mentioning.
Since the introduction of resolvconf in Ubuntu 12.04 it is more
advisable to configure nameserver addresses
Where did you get the uvt program?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1163147
Title:
can't resolve lan hosts (regression)
To manage notifications about this bug go to:
The instructions say you should comment out dns=dnsmasq in order to
disable the system dnsmasq. But commenting out that line (and
restarting network-manager) will only disable the NetworkManager-
controlled dnsmasq instance (which listens at 127.0.1.1 in Quantal and
higher, at 127.0.0.1 in
*** This bug is a duplicate of bug 1126488 ***
https://bugs.launchpad.net/bugs/1126488
I guess this is the same as bug #1126488.
** This bug has been marked a duplicate of bug 1126488
libvirt instance of dnsmasq in raring fails to forward DNS requests
--
You received this bug
** This bug is no longer a duplicate of bug 1126488
libvirt instance of dnsmasq in raring fails to forward DNS requests
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1163147
For the record, please say which version of the uvt script you are
using.
In the description you say:
This configuration worked for 12.04 LTS, 12.10, but does not work for Raring.
In comment #6 you say:
I don't think this is a duplicate of bug #1126488 since I made the
conscious decision to
*** This bug is a duplicate of bug 1126488 ***
https://bugs.launchpad.net/bugs/1126488
** This bug has been marked a duplicate of bug 1126488
libvirt instance of dnsmasq in raring fails to forward DNS requests
--
You received this bug notification because you are a member of Ubuntu
** Changed in: dnsmasq (Ubuntu)
Status: Expired = Confirmed
** Description changed:
- dnsmasq does not resolve DNS names correcty.
+ Dnsmasq sometimes does not resolve DNS names correcty.
- Applications like Thunderbird or tools like ssh rely on working name
- resolution. However, if
Arno,
Does disabling NetworkManager-controlled dnsmasq fix the problem? (To
disable NetworkManager-controlled dnsmasq, comment out dns=dnsmasq in
/etc/NetworkManager/NetworkManager.conf and then restart network-
manager.)
Hypothesis: dnsmasq is given two nameserver addresses. The first
The feature was dropped from the resolvconf package in Ubuntu 13.04. The
bind9 maintainers have been invited to add a similar feature to support
BIND 9. Your contribution may help to convince them to take action.
Until this feature actually appears in bind9 you will have to implement
it locally
** Description changed:
First, apologies for the complicated configuration.
I use the 'uvt' front-end to libvirt-managed kvm guest machines. I also
have a LAN with a router that does local dynamic DNS configuration with
the client-provided dhcp hostnames.
I would like to resolve
Hi Seth,
Just read your bug report again.
It appears that you have two nameservers, neither of which has complete
DNS information. You need to configure things such that each nameserver
listed in resolv.conf can resolve all names you want resolved.
On a LAN, for example, there is sometimes a
** Changed in: dnsmasq (Ubuntu)
Status: Triaged = Invalid
** Summary changed:
- Validate DNSSEC by default
+ Please enhance NetworkManager such that DNSSEC validation is done whenever
possible
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Summary changed:
- dnsmasq should not register 127.0.0.1 with resolvconf if it's not listening
on lo
+ Please enhance dnsmasq to talk directly to resolvconf and to register only
its actual listening address(es)
--
You received this bug notification because you are a member of Ubuntu
Server
The dnsmasq package is still not included on the Server ISO in 13.04.
The dnsmasq package is about 15KiB in size.
** Summary changed:
- The dnsmasq package isn't available on the server ISO
+ Please include the dnsmasq package on the Server ISO
--
You received this bug notification because
** Package changed: dnsmasq (Ubuntu) = ubuntu-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/661599
Title:
Please include the dnsmasq package on the Server ISO
To
** Package changed: network-manager (Ubuntu) = dnsmasq (Ubuntu)
** Summary changed:
- NetworkManager uses dnsmasq with negative DNS cache enabled
+ Dnsmasq caches negative results if it starts before the network is up
--
You received this bug notification because you are a member of Ubuntu
Stéphane wrote:
Can you confirm that you have the dnsmasq package installed and not only
dnsmasq-base?
If so, then that bug is invalid as when you install dnsmasq on your system,
that'll bypass NetworkManager's own instance and so will run with the
default dnsmasq settings (including
What do you think, Simon?
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1172467
Title:
Dnsmasq caches negative
You need to configure things such that each nameserver listed in resolv.conf
can resolve all names you want resolved.
This requirement feels impossible to meet; the dnsmasq spawned by libvirt
on my laptop knows only the VMs running on my laptop. It is not possible
for this dnsmasq to know
I think that this is ultimately an enhancement request for libvirt.
** Package changed: dnsmasq (Ubuntu) = libvirt (Ubuntu)
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
** Summary changed:
- Can't resolve both VM names and LAN names
+ Please run dnsmasq in such a way that it
** Changed in: resolvconf (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/797339
Title:
apparmor profile for bind. resolvconf error
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
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/797339
Title
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
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.
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
*** 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
Server Team, which is subscribed to openssh in
** Summary changed:
- resolvconf creating bogus resolv.conf file
+ bind9 registering itself with resolvconf but not set up to forward queries
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
*** This bug is a duplicate of bug 437783 ***
https://bugs.launchpad.net/bugs/437783
This not a duplicate of #437783 which is related to postfix and
resolvconf. The failure from DpkgTerminalLog.txt is:
Setting up bind9 (1:9.6.1.dfsg.P1-3ubuntu0.3) ...
* Starting domain name service...
The original problem was postconf failing to open main.cf and
/etc/resolvconf/update-libc.d/postfix trying to copy /etc/resolv.conf
onto itself at the line
cp /etc/resolv.conf $(/usr/sbin/postconf -h
queue_directory)/etc/resolv.conf
because postconf -h queue_directory returns a null string.
Now to address the bug which all the *duplicates*, except #511314 and
#437783, are about, namely, that installing bind9 aborts with
resolvconf: Error: /etc/resolv.conf must be a symlink.
First, resolvconf in Precise no longer returns an error condition if
/etc/resolv.conf is not a symlink, so the
** Summary changed:
- resolvconf uses wrong path for bind9 and resovconf
+ resolvconf uses wrong path for bind9 and resolvconf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/693002
People continue to report the problem that named registers 127.0.0.1
with resolvconf even though named is not set up to forward queries. So I
suppose that the upload promised in #6 should happen before Precise is
released.
--
You received this bug notification because you are a member of Ubuntu
I said:
Second, bind9 in Precise no longer defaults to registering 127.0.0.1 with
resolvconf on start
This is not quite correct. LaMont Jones wrote on 2012-02-17 in #933723
The next upload of bind9 will default to not enabling resolvconf but
this upload hasn't happened yet.
--
You received
*** This bug is a duplicate of bug 797339 ***
https://bugs.launchpad.net/bugs/797339
This is also fixed in Ubuntu. Resolvconf no longer generates
/var/run/bind/named.options.
** This bug has been marked a duplicate of bug 797339
apparmor profile for bind. resolvconf error
--
You
** Also affects: postfix (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/437783
Title:
bind9 failed to start : resolvconf: Error:
With reference to comment #8, does this issue still affect ntpd and
should it therefore be additionally-assigned accordingly?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/604283
From the terminal log:
useradd: no se puede bloquear /etc/passwd; inténtelo más tarde.
adduser: `/usr/sbin/useradd -d /var/cache/bind -g bind -s /bin/false -u 116
bind' devolvió el código de error 1. Saliendo.
** Summary changed:
- package bind9 1:9.7.0.dfsg.P1-1ubuntu0.1 failed to
Any idea why bind9 failed to start on installation?
Does it start by hand?
Does it start on reboot?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/790372
Title:
package bind9
Fix has been released; fixed in Precise. In 9.7.3 the postinst tried to
do
chgrp bind /var/run/named
but since bzr rev 42 it no longer does so.
** Changed in: bind9 (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server
*** This bug is a duplicate of bug 790372 ***
https://bugs.launchpad.net/bugs/790372
The original report did not involve resolvconf. Just mysterious failure
as in #790372.
Reports #5 and following relate to resolvconf and are duplicates of
#491387 et al.
#10 is a duplicate of #437783.
#11
** Summary changed:
- network servers do not listen on 127.0.1.1
+ Certain services do not listen on 127.0.1.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/604283
Title:
Certain
*** This bug is a duplicate of bug 790372 ***
https://bugs.launchpad.net/bugs/790372
** This bug is no longer a duplicate of bug 437783
bind9 failed to start : resolvconf: Error: /etc/resolv.conf must be a symlink
** Summary changed:
- package bind9 1:9.6.1.dfsg.P1-3ubuntu0.3 failed to
This is not a duplicate. The failure message is:
Setting up bind9 (1:9.6.1.dfsg.P1-3) ...
* Starting domain name service... bind9 [80G usage: named [-4|-6] [-c
conffile] [-d debuglevel] [-f|-g] [-n number_of_cpus]
[-p port] [-s] [-t chrootdir] [-u username]
[-m
*** This bug is a duplicate of bug 790372 ***
https://bugs.launchpad.net/bugs/790372
** This bug has been marked a duplicate of bug 790372
package bind9 1:9.7.0.dfsg.P1-1ubuntu0.2 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
--
** Summary changed:
- post installation script fails with exit status 1
+ bind9 postinst fails on rndc-confgen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/898004
Title:
bind9
*** This bug is a duplicate of bug 790372 ***
https://bugs.launchpad.net/bugs/790372
** This bug has been marked a duplicate of bug 790372
package bind9 1:9.7.0.dfsg.P1-1ubuntu0.2 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
--
*** This bug is a duplicate of bug 790372 ***
https://bugs.launchpad.net/bugs/790372
** This bug has been marked a duplicate of bug 790372
package bind9 1:9.7.0.dfsg.P1-1ubuntu0.2 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
--
*** This bug is a duplicate of bug 790372 ***
https://bugs.launchpad.net/bugs/790372
** This bug has been marked a duplicate of bug 790372
package bind9 1:9.7.0.dfsg.P1-1ubuntu0.2 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
--
** Changed in: bind9 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/797339
Title:
apparmor profile for bind. resolvconf error
To
*** This bug is a duplicate of bug 790372 ***
https://bugs.launchpad.net/bugs/790372
Same as #790372 except that here a restart was done instead of a start.
The stop part succeeded; the start part failed.
** This bug has been marked a duplicate of bug 790372
package bind9
Precise now has bind9 1:9.8.1.dfsg.P1-4 so bug #920061 et al (re:
/etc/resolv.conf must be a symlink) may now have been fixed.
As I mentioned earlier (in #10), *this* report, #437783, originally
reported a distinct bug, namely that of postconf failing to open main.cf
and consequently
It is postfix's resolvconf-hook-script (/etc/resolvconf/update-
libc.d/postfix) which causes the failure. See also #437783.
** Package changed: bind9 (Ubuntu) = postfix (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix
The failure originally reported here has been reported again at #980682
so #980682 can be used to track the bug in postfix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/437783
Title:
** Summary changed:
- Installing bind9 in a chroot
+ Please install bind9 in a chroot
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/127184
Title:
Please install bind9 in a chroot
See comment #8.
** Package changed: bind9 (Ubuntu) = ntp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/604283
Title:
Certain services do not listen on 127.0.1.1
To manage
** Summary changed:
- integrate with bind package
+ samba4: integrate with bind package
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/975973
Title:
samba4: integrate with bind
** Summary changed:
- package bind9 1:9.7.0.dfsg.P1-1ubuntu0.2 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
+ package bind9 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
--
You
Last lines of DpkgTerminalLog.txt:
Running newaliases
newaliases: warning: valid_hostname: invalid character 40(decimal):
ubuntu.(null)
newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad
parameter value: ubuntu.(null)
--
You received this bug notification because you are
** Summary changed:
- package bind9 1:9.8.1.dfsg.P1-3 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
+ postconf can't open main.cf with the result that
/etc/resolvconf/update-libc.d/postfix fails trying to copy /etc/resolv.conf
onto itself
** Summary changed:
- named does not shut down after service bind9 stop
+ DNSSEC-enabled named sometimes does not die on service bind9 stop
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
*** This bug is a duplicate of bug 982917 ***
https://bugs.launchpad.net/bugs/982917
Last lines of DpkgTerminalLog:
Running newaliases
newaliases: warning: valid_hostname: numeric hostname: 04
newaliases: fatal: file /etc/postfix/main.cf: parameter mydomain: bad parameter
value: 04
dpkg:
Compare #982917.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/897632
Title:
package postfix 2.8.5-2~build0.11.04 failed to install/upgrade:
подпроцесс установлен сценарий
*** This bug is a duplicate of bug 982917 ***
https://bugs.launchpad.net/bugs/982917
** This bug has been marked a duplicate of bug 982917
package postfix 2.9.1-2 failed to install/upgrade: le sous-processus script
post-installation installé a retourné une erreur de sortie d'état 75
--
Submitter: What does your /bin/sh point to?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/820870
Title:
package postfix 2.8.1-1~lucid1 failed to install/upgrade: sub-processo
*** This bug is a duplicate of bug 982917 ***
https://bugs.launchpad.net/bugs/982917
** This bug has been marked a duplicate of bug 982917
package postfix 2.9.1-2 failed to install/upgrade: le sous-processus script
post-installation installé a retourné une erreur de sortie d'état 75
--
Based on the information you have provided so far I think that dnsmasq
is the most likely culprit so I will reassign this issue over there.
If you get your hands on an affected machine then please let us know so
that we can continue the investigation.
** Package changed: resolvconf (Ubuntu) =
This may have been a bug in resolvconf, specifically #366967 et al. If
so then it has been fixed in Precise. Please check.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/875950
Lieven Van Acker: Can you investigate this further to figure out why
dnsmasq isn't being asked to look up 'host2.domain2.local'?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/781557
Just checked http://nl.releases.ubuntu.com/12.04/ubuntu-12.04-alternate-
amd64.list. Lists dnsmasq-base but not dnsmasq.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/661599
Title:
Is there some officially correct way of disabling the NM-driven dnsmasq?
If so, what is it?
When dnsmasq is disabled as above, does this problem (#993794) go away?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
Sergio: When dnsmasq is disabled (by commenting out the entry in
/etc/NetworkManager/NetworkManager.conf) does the problem (#993794) go
away?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
** Changed in: resolvconf (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/993794
Title:
Precise resolvconf+dnsmasq setup breaks login in
This issue doesn't affect resolvconf directly, so someone please remove
resolvconf from the Affects list.
The malfunction described here is probably caused by #1003842.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in
1 - 100 of 351 matches
Mail list logo
