[Touch-packages] [Bug 1577724] Re: NM doesn't sets the DNS properly, forces local dnsmasq as a resolver
If you choose to only get the IP address from DHCP and you don't specify and DNS servers to use, then there won't be any DNS servers configured (besides 127.0.1.1). What will happen is that a DNS request will be sent to 127.0.1.1 (dnsmasq). dnsmasq doesn't have any upstream servers configured, so unless the IP address for the domain is statically set somewhere in the configuration file, DNS won't work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577724 Title: NM doesn't sets the DNS properly, forces local dnsmasq as a resolver Status in network-manager package in Ubuntu: Incomplete Bug description: 1. Setup a network with DHCP address, gateway and DNS. 2. Connect to that network. 3. Check the resolver configured in /etc/resolv.conf Expected result: To find "nameserver" set to the DNS addresses provided by the external DHCP server Actual result: "nameserver=127.0.1.1" in any case. This related to https://bugs.launchpad.net/bugs/1577720 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 3 12:42:19 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-22 (10 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlxc4e9840ddc04 proto static metric 600 169.254.0.0/16 dev wlxc4e9840ddc04 scope link metric 1000 192.168.1.0/24 dev wlxc4e9840ddc04 proto kernel scope link src 192.168.1.95 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlxc4e9840ddc04wifi connected /org/freedesktop/NetworkManager/Devices/0 SIGKILL 2986445c-d935-4b58-b3ca-da614dd4 /org/freedesktop/NetworkManager/ActiveConnection/5 C0:EE:FB:44:15:8A btdisconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577724] Re: NM doesn't sets the DNS properly, forces local dnsmasq as a resolver
Alternatively, you can create a file (choose any file name) in /etc/NetworkManager/conf.d/ with the following in it: [main] dns=default This should have NetworkManager not use dnsmasq and update resolv.conf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577724 Title: NM doesn't sets the DNS properly, forces local dnsmasq as a resolver Status in network-manager package in Ubuntu: Incomplete Bug description: 1. Setup a network with DHCP address, gateway and DNS. 2. Connect to that network. 3. Check the resolver configured in /etc/resolv.conf Expected result: To find "nameserver" set to the DNS addresses provided by the external DHCP server Actual result: "nameserver=127.0.1.1" in any case. This related to https://bugs.launchpad.net/bugs/1577720 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 3 12:42:19 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-22 (10 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlxc4e9840ddc04 proto static metric 600 169.254.0.0/16 dev wlxc4e9840ddc04 scope link metric 1000 192.168.1.0/24 dev wlxc4e9840ddc04 proto kernel scope link src 192.168.1.95 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlxc4e9840ddc04wifi connected /org/freedesktop/NetworkManager/Devices/0 SIGKILL 2986445c-d935-4b58-b3ca-da614dd4 /org/freedesktop/NetworkManager/ActiveConnection/5 C0:EE:FB:44:15:8A btdisconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577724] Re: NM doesn't sets the DNS properly, forces local dnsmasq as a resolver
I believe this is by design. NetworkManager starts up a dnsmasq instance that then uses the DNS servers provided by the DHCP server to resolve queries. This is so that dnsmasq acts as a DNS caching application. If you run tcpdump or wireshark to log DNS queries made, you should see that the DNS servers provided by the DHCP server are used. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577724 Title: NM doesn't sets the DNS properly, forces local dnsmasq as a resolver Status in network-manager package in Ubuntu: Incomplete Bug description: 1. Setup a network with DHCP address, gateway and DNS. 2. Connect to that network. 3. Check the resolver configured in /etc/resolv.conf Expected result: To find "nameserver" set to the DNS addresses provided by the external DHCP server Actual result: "nameserver=127.0.1.1" in any case. This related to https://bugs.launchpad.net/bugs/1577720 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 3 12:42:19 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-22 (10 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlxc4e9840ddc04 proto static metric 600 169.254.0.0/16 dev wlxc4e9840ddc04 scope link metric 1000 192.168.1.0/24 dev wlxc4e9840ddc04 proto kernel scope link src 192.168.1.95 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlxc4e9840ddc04wifi connected /org/freedesktop/NetworkManager/Devices/0 SIGKILL 2986445c-d935-4b58-b3ca-da614dd4 /org/freedesktop/NetworkManager/ActiveConnection/5 C0:EE:FB:44:15:8A btdisconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509725] [NEW] Some ICMPv6 packets rejected due to rule ordering
Public bug reported: In the default before6.rules file, the following lines: # drop INVALID packets (logs these in loglevel medium and higher) -A ufw6-before-input -m conntrack --ctstate INVALID -j ufw6-logging-deny -A ufw6-before-input -m conntrack --ctstate INVALID -j DROP are present before the ICMPv6 rules. The problem is that this also captures echo replies (but, somehow, allows echo requests) and some IPv6 routing announcements. If I try to ping ff02::1 to ping all devices on the local network, I only get a response from my own device. Moving those three lines towards the end of the file (after all ICMP rules and before the COMMIT) fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ufw 0.34-2 Uname: Linux 4.3.0-rc5arcot x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sat Oct 24 18:07:40 2015 InstallationDate: Installed on 2012-10-19 (1099 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to wily on 2015-02-28 (238 days ago) mtime.conffile..etc.ufw.sysctl.conf: 2015-08-08T23:49:55.322401 ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1509725 Title: Some ICMPv6 packets rejected due to rule ordering Status in ufw package in Ubuntu: New Bug description: In the default before6.rules file, the following lines: # drop INVALID packets (logs these in loglevel medium and higher) -A ufw6-before-input -m conntrack --ctstate INVALID -j ufw6-logging-deny -A ufw6-before-input -m conntrack --ctstate INVALID -j DROP are present before the ICMPv6 rules. The problem is that this also captures echo replies (but, somehow, allows echo requests) and some IPv6 routing announcements. If I try to ping ff02::1 to ping all devices on the local network, I only get a response from my own device. Moving those three lines towards the end of the file (after all ICMP rules and before the COMMIT) fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ufw 0.34-2 Uname: Linux 4.3.0-rc5arcot x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sat Oct 24 18:07:40 2015 InstallationDate: Installed on 2012-10-19 (1099 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to wily on 2015-02-28 (238 days ago) mtime.conffile..etc.ufw.sysctl.conf: 2015-08-08T23:49:55.322401 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1509725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1162781] Re: bluez package out of date, 5.23 is available in debian sid/jessie
This likely won't be in vivid-backports, since there are many components that depends on bluez and only work with bluez 4. (See also https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1162781 Title: bluez package out of date, 5.23 is available in debian sid/jessie Status in bluez package in Ubuntu: Triaged Bug description: Looks like there have been a lot of improvements to bluez since the 4.x series. Would be nice to get the latest release pulled in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1162781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366207] Re: qgl.h typedefs GLdouble to float instead of double
Correction: the link to the actual change review is https://codereview .qt-project.org/#/c/93984/1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1366207 Title: qgl.h typedefs GLdouble to float instead of double Status in “qt4-x11” package in Ubuntu: Won't Fix Bug description: In qgl.h, for the OpenGL ES 2.0, GLdouble is typedef'ed to float. This causes a compile error in the armhf architcture in downstream programs including OpenSceneGraph and other programs. Recently, Qt committed a patch (https://codereview.qt-project.org/#/c/93984/1//ALL) for Qt 5 to change the typedef from float to double, since (according to the commit message), the typedef was from S60 and wasn't being used anywhere. I've backported the patch to Qt 4, but I wasn't able to do a full build for armhf; the build was taking 12+ hours for me. However, it does seem to have compiled the OpenGL source code files and a few examples related to this successfully. Therefore, I wasn't fully able to verify that this compiles successfully. This is intended to be a bugfix-only update; however, since the ABI is effectively being changed, this change might warrant some discussion here. The expectation for downstream packages on armhf is that more packages can be compiled, since some packages have this typedef error, but some packages may also fail to compile if they rely on the fact that this was a float. I'm expecting that the number for the latter case is low to 0, since this is a widening conversion. I've attached the raw patch file. This will need to be added to debian/patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1366207/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
