** Changed in: network-manager (Ubuntu)
Status: Triaged => In Progress
--
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/1034946
Title:
dnsmasq and network manager broken if dns
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed => In Progress
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsm
Any news about this?
There's actually multiple issues here; one of them being that loopback
probably isn't ready yet, which is something we fixed in NetworkManager
(which had the same issue) by depending on it through upstart before
starting the network-manager job.
Then, we now ship configuratio
** Also affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dnsmasq (Ubuntu)
Status: New => In Progress
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => High
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel
Should it really be evolution to do this or postfix directly?
AFAIUI it makes more sense if it's done by postfix, if only to avoid
duplicating work in every application that might want to send mail...
and also because someone might want to manually send mail, and then
translating manually to an AC
** Changed in: dnsmasq (Ubuntu Precise)
Status: In Progress => Triaged
--
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/1029977
Title:
dnsmasq-base should ship the dnsmasq dbus
** Description changed:
+ [Rationale]
+ Required for network-manager SRU for bug 1004775:
+ To properly handle updating DNS nameservers in the dnsmasq instance spawned
by NetworkManager; it would require starting dnsmasq with dbus enabled so that
all future dns changes could be done through that
Thanks Simon!
--
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/1029977
Title:
dnsmasq-base should ship the dnsmasq dbus configuration file
To manage notifications about this bug go t
are.
** Changed in: dnsmasq (Ubuntu Precise)
Status: New => In Progress
** Changed in: dnsmasq (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: dnsmasq (Ubuntu Precise)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug noti
ance: Medium
Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
Status: In Progress
** Changed in: dnsmasq (Ubuntu)
Status: New => In Progress
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => Medium
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) => M
This is either an issue that lo isn't ready yet; or more likely that NM
starts and spawns dnsmasq to listen on 127.0.0.1 before the standalone
daemon has a chance to start. It should be apparent if it is the case in
/var/log/syslog.
Please attach /var/log/syslog to this bug report. Thanks!
** Cha
The available parameters for the [vlan] block are defined in source:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/libnm-util/nm-setting-vlan.c#n608
However, the actual names to use (as key=) for the parameters are the
NM_SETTING_VLAN_* constants; which are defined here:
http://c
No, it's supported in NM regardless of the distro used; it's just not
easy to configure; depends on the proper use of the config files.
Closing as Fix Released.
To configure it you'll need to create a new connection manually in
/etc/NetworkManager/system-connections; something like a file "VLAN615
Well, first we'll ship the file for /etc/dnsmasq.d; changing it to bind-
dynamic after the fact is quick.
--
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/959037
Title:
NM-controlled
** Also affects: dnsmasq (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: pdnsd (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: pdns-recursor (
Thomas, Stéphane;
Yes, let's track the change for network-manager in bug #959037 -- marking the
task for n-m here as Invalid.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
** Changed in: network-manager (Ubuntu Precise)
Status: New => Invalid
--
You received this
This also affects ubuntu-orchestra-client-juju; which also needs to
update its Depends line.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1021418
Title:
Replace python-software
Public bug reported:
With software-properties 0.86 (https://launchpad.net/ubuntu/+source
/software-properties/0.86) which is about to land in quantal (in NEW at
the time of this writing); add-apt-repository is being moved from
python-software-properties to the software-properties-common package.
What this particular bug looks like is that after trying to resolve s4.
(as a TLD of some sort), dnsmasq simply returns NXDOMAIN (as it should).
Then libc goes and tries to resolve the names with the search domains
appended and that somehow also fails (or it's never tried).
I wonder if this could
Shantanu Tushar: Since you can't reproduce your issue with your new ISP,
I'm closing this bug as Invalid. If you manage to reproduce it, feel
free to reopen by setting it back to New.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Invalid
** Changed in: dnsmasq (Ubuntu)
uld
likely solve at least half of the problem cases here.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager (Ubuntu Prec
Listening on lo is fine; and blocking other DNS servers from being
started isn't. I think we're in violent agreement there. The problem is
how to fix this.
I'm not saying dnsmasq should be crippled, but that it should special-
case lo and not just listen on 0.0.0.0; because that binds to any
furth
This wouldn't really be different that=n using libc for resolving, so I
don't think it really qualifies as a security issue.
You can still perform DNSSEC validation, which is the actual difference
from if DNSSEC proxying wasn't supported by dnsmasq. Granted, it doesn't
automatically do the validat
I'll open a bug myself shortly for the VPN case; and reply here with the
bug number.
** No longer affects: network-manager
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Well, that would normally be correct, but the VPN plugins depend on
vpnc, pptp, openvpn, etc. to be running to establish and keep the VPN
connection up for rekeying and such. Those don't get a pid file in
/run/sendsigs.omit.d yet, and so they would get killed by the sendsigs
script shortly before u
That wouldn't be the right process though. The configuration itself
shipped by default should be patched, that can be done with a simple
patch to the dnsmasq package.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
ht
** Package changed: dhcp3 (Ubuntu) => isc-dhcp (Ubuntu)
** Changed in: isc-dhcp (Ubuntu)
Status: New => In Progress
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => High
** Changed in: isc-dhcp (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre
** Also affects: dhcp3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in Ubuntu.
https://bugs.launchpad.net/bugs/869635
Title:
long delay at shutdown/reboot - network-manage
Closing as Fix Released since the upstream bug was also closed. All
indicates that this works properly at this point.
** Changed in: network-manager (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscrib
Public bug reported:
Please sync quota 4.00-3 (main) from Debian unstable (main)
Changelog entries since current precise version 4.00-1:
quota (4.00-3) unstable; urgency=low
* Port to libnl3 version 3.2.3+.
Thanks to Mathieu Trudel-Lapierre (Closes: #653096)
* Fixed query for quota
This was an issue in NM, fixed in 0.9.1.90-0ubuntu6: we'll default to IPv6:
Ignore if creating an ad-hoc network:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/830178
Closing as Fix Released for n-m and Invalid for dnsmasq.
** Changed in: network-manager (Ubuntu)
Status:
It indeed appears to be directly related to bringing up IPv6.. However,
since IPv6 hotspots don't appear to currently being supported (no
iptables code, no parameters passed for it to dnsmasq, etc.; it probably
simply should be ignored in all cases.
** Changed in: network-manager (Ubuntu)
S
Closing vpnc/kvpnc/network-manager tasks. It's not an issue in network-
manager or vpnc; they were just inconvenienced by the fact that the
module wasn't available.
** Changed in: kvpnc (Ubuntu)
Status: New => Invalid
** Changed in: kvpnc (Ubuntu Lucid)
Status: New => Invalid
** Ch
Seems the symlinks in Samba were done on purpose for upgrade
compatibility, since samba doesn't depend on the installed DHCP client
and can't know which is the correct directory to put the hooks in. At a
later point in Debian samba should drop that symlink.
** Changed in: samba (Ubuntu)
Sta
as symlinks to the same
scripts in /etc/dhcp3; and changing this would need to be done in
Debian.
** Changed in: isc-dhcp (Ubuntu)
Status: In Progress => Triaged
** Changed in: isc-dhcp (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Also a
Alexey, this indeed has nothing to do with NetworkManager.
If you just do:
sudo ifdown eth0.20
sudo ifup eth0.20
Is the device properly initialized and brought up?
** Package changed: network-manager (Ubuntu) => vlan (Ubuntu)
** Changed in: vlan (Ubuntu)
Status: New => Incomplete
--
Y
It seems like this is a bug that has already been reported to the
developers of openSSH. Please consider commenting in the upstream bug
(https://bugzilla.mindrot.org/show_bug.cgi?id=1585) and proposing your
patch, possibly integrating some of the work in the draft patch that is
already included the
Hi, thanks for filing this bug and helping to make Ubuntu better!
Unfortunately, this does not appear to be a bug in debian-installer, and
also it doesn't seem to be a bug at all: named listens on port 953 only
for the localhost, and that port is used by things like ndc to control
the server (rest
Till, do you have files in /etc/apt/sources.list.d? This is likely where
the packages sources would come from.
This bug comes from the fact that at some point (or maybe you still do)
packages were installed from the ~network-manager team trunk PPA. The
issue is in network-manager, not dhcp3, so I'
Just ran 'dpkg --configure -a' after the end of the upgrade process and
the postinst script ran without issues.
--
package samba 2:3.5.4~dfsg-1ubuntu5 failed to install/upgrade: sous-processus
script post-installation installé tué par le signal (Complété)
https://bugs.launchpad.net/bugs/638479
Y
** Attachment added: "AptOrdering.txt"
https://bugs.edge.launchpad.net/bugs/638479/+attachment/1585571/+files/AptOrdering.txt
** Attachment added: "Dependencies.txt"
https://bugs.edge.launchpad.net/bugs/638479/+attachment/1585572/+files/Dependencies.txt
** Attachment added: "Df.txt"
h
Public bug reported:
Binary package hint: samba
After having the samba postinst script run and do nothing for well over
an hour, I killed it with a signal 15 in order to unjam an upgrade.
root 21390 18831 0 16:27 pts/000:00:00 /usr/bin/perl -w
/usr/share/debconf/frontend /var/lib/dpkg/i
Confirming; the same can be seen on my system. However, given that these
are false positives, and *some* false positives are to be expected when
dealing with security testing software, setting prioriy to Low.
Fabián, if you feel this needs to be re-evaluated, don't hesitate to
bring it up :)
** C
201 - 243 of 243 matches
Mail list logo
