[Desktop-packages] [Bug 1637700] Re: Caching dnsmasq stops resolving after some time
Edit /etc/NetworkManager/NetworkManager.conf and comment out the line "dns=dnsmasq" with a leading '#'. Then reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1637700 Title: Caching dnsmasq stops resolving after some time Status in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Since upgrading to yakkety my network sometimes stops working - it might be related to suspending the laptop. The NetworkManager-managed caching dnsmasq just stops resolving at some point: dig google.com @127.0.1.1 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 22521 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com.IN A ;; Query time: 0 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sat Oct 29 09:12:33 CEST 2016 ;; MSG SIZE rcvd: 28 Networking and upstream DNS are fine: dig google.com @8.8.8.8 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63345 ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 299 IN A 46.134.208.30 [...] ;; Query time: 43 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Sat Oct 29 09:12:31 CEST 2016 ;; MSG SIZE rcvd: 295 Killing it resolves the issue, dnsmasq gets restarted and works again: ps aux | grep dnsmasq nobody4262 0.0 0.0 54308 2740 ?S01:30 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d sudo kill 4262 dig google.com @127.0.1.1 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58324 ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 299 IN A 46.134.208.59 [...] ;; Query time: 41 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sat Oct 29 09:12:54 CEST 2016 ;; MSG SIZE rcvd: 295 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 29 09:13:04 2016 InstallationDate: Installed on 2016-05-06 (175 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-06 (175 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: network-manager 1.2.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Tags: yakkety third-party-packages Uname: Linux 4.8.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin lxd plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla: [deleted] nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1637700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1637700] Re: Caching dnsmasq stops resolving after some time
Compare bug #1631241. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1637700 Title: Caching dnsmasq stops resolving after some time Status in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Since upgrading to yakkety my network sometimes stops working - it might be related to suspending the laptop. The NetworkManager-managed caching dnsmasq just stops resolving at some point: dig google.com @127.0.1.1 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 22521 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com.IN A ;; Query time: 0 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sat Oct 29 09:12:33 CEST 2016 ;; MSG SIZE rcvd: 28 Networking and upstream DNS are fine: dig google.com @8.8.8.8 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63345 ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 299 IN A 46.134.208.30 [...] ;; Query time: 43 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Sat Oct 29 09:12:31 CEST 2016 ;; MSG SIZE rcvd: 295 Killing it resolves the issue, dnsmasq gets restarted and works again: ps aux | grep dnsmasq nobody4262 0.0 0.0 54308 2740 ?S01:30 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d sudo kill 4262 dig google.com @127.0.1.1 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58324 ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 299 IN A 46.134.208.59 [...] ;; Query time: 41 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sat Oct 29 09:12:54 CEST 2016 ;; MSG SIZE rcvd: 295 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 29 09:13:04 2016 InstallationDate: Installed on 2016-05-06 (175 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-06 (175 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: network-manager 1.2.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Tags: yakkety third-party-packages Uname: Linux 4.8.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin lxd plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla: [deleted] nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1637700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637700] Re: Caching dnsmasq stops resolving after some time
NetworkManager is starting a dnsmasq instance whereas it shouldn't do that any more. ** Package changed: dnsmasq (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1637700 Title: Caching dnsmasq stops resolving after some time Status in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Since upgrading to yakkety my network sometimes stops working - it might be related to suspending the laptop. The NetworkManager-managed caching dnsmasq just stops resolving at some point: dig google.com @127.0.1.1 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 22521 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com.IN A ;; Query time: 0 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sat Oct 29 09:12:33 CEST 2016 ;; MSG SIZE rcvd: 28 Networking and upstream DNS are fine: dig google.com @8.8.8.8 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63345 ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 299 IN A 46.134.208.30 [...] ;; Query time: 43 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Sat Oct 29 09:12:31 CEST 2016 ;; MSG SIZE rcvd: 295 Killing it resolves the issue, dnsmasq gets restarted and works again: ps aux | grep dnsmasq nobody4262 0.0 0.0 54308 2740 ?S01:30 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d sudo kill 4262 dig google.com @127.0.1.1 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58324 ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 299 IN A 46.134.208.59 [...] ;; Query time: 41 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sat Oct 29 09:12:54 CEST 2016 ;; MSG SIZE rcvd: 295 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 29 09:13:04 2016 InstallationDate: Installed on 2016-05-06 (175 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-06 (175 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: network-manager 1.2.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Tags: yakkety third-party-packages Uname: Linux 4.8.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin lxd plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla: [deleted] nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1637700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1637700] Re: Caching dnsmasq stops resolving after some time
In yakkety there is no longer supposed to be a local forwarding nameserver (instance of dnsmasq) listening at 127.0.1.1. Instead an instande of resolved is started. Name resolution requests are fed to it via the name service switch (configured with nsswitch.conf) rather than via the libc resolver (configured with resolv.conf). Announcement: https://lists.ubuntu.com/archives/ubuntu- devel/2016-May/039350.html Please post the output of the /usr/share/resolvconf/dump-debug-info utility. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1637700 Title: Caching dnsmasq stops resolving after some time Status in dnsmasq package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Since upgrading to yakkety my network sometimes stops working - it might be related to suspending the laptop. The NetworkManager-managed caching dnsmasq just stops resolving at some point: dig google.com @127.0.1.1 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 22521 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com.IN A ;; Query time: 0 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sat Oct 29 09:12:33 CEST 2016 ;; MSG SIZE rcvd: 28 Networking and upstream DNS are fine: dig google.com @8.8.8.8 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63345 ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 299 IN A 46.134.208.30 [...] ;; Query time: 43 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Sat Oct 29 09:12:31 CEST 2016 ;; MSG SIZE rcvd: 295 Killing it resolves the issue, dnsmasq gets restarted and works again: ps aux | grep dnsmasq nobody4262 0.0 0.0 54308 2740 ?S01:30 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d sudo kill 4262 dig google.com @127.0.1.1 ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58324 ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 299 IN A 46.134.208.59 [...] ;; Query time: 41 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Sat Oct 29 09:12:54 CEST 2016 ;; MSG SIZE rcvd: 295 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 29 09:13:04 2016 InstallationDate: Installed on 2016-05-06 (175 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-06 (175 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: network-manager 1.2.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Tags: yakkety third-party-packages Uname: Linux 4.8.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin lxd plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla: [deleted] nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
[Desktop-packages] [Bug 1169437] Re: network-manager does not configure local resolver or dnsmasq to use the nameserver addresses received from the VPN server
Vincent: Which VPN client are you using? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1169437 Title: network-manager does not configure local resolver or dnsmasq to use the nameserver addresses received from the VPN server Status in network-manager-openvpn package in Ubuntu: Fix Released Bug description: NetworkManager/dnsmasq does not set the DNS servers given by the OpenVPN server when I connect. I can see in my syslog that I do receive the name server addresses correctly along with all the routes: Apr 16 08:14:09 homer NetworkManager[4014]:Internal DNS: 192.168.11.90 Apr 16 08:14:09 homer NetworkManager[4014]:Internal DNS: 192.168.11.190 However, they are not used: oscar@homer:~$ nmcli -f IP4 dev list | grep DNS IP4.DNS[1]: 192.168.0.1 oscar@homer:~$ (That is my default DNS/Gateway and it should still be queried for all DNS queries outside of VPN network) If I comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf and restart NetworkManager then DNS starts to work properly again, VPN nameservers are used for domain names on the VPN network and others through my default nameserver. Let me know if I kan provide further info about this issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Apr 16 08:16:42 2013 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-22 (144 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IpRoute: default via 192.168.0.1 dev eth1 proto static 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.44 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-04-16T08:12:17.691993 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1179bc6d7-cd13-4cfb-b73f-e8da8362a511 802-3-ethernet1364485020 tor 28 mar 2013 16:37:00 yes no /org/freedesktop/NetworkManager/Settings/2 Wiggum2a818c4e-494c-4b91-be56-630636608f07 802-11-wireless 1366092808 tis 16 apr 2013 08:13:28 yes no /org/freedesktop/NetworkManager/Settings/1 81e14bde-0b0b-42be-8b56-3bfda6ca60fc vpn 1366092850 tis 16 apr 2013 08:14:10 yes no /org/freedesktop/NetworkManager/Settings/0 aad98317-a8e1-4ff7-b3b5-7c43c1bcfd32 802-11-wireless 1358879064 tis 22 jan 2013 19:24:24 yes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1169437] Re: network-manager does not configure local resolver or dnsmasq to use the nameserver addresses received from the VPN server
You may be encountering a new problem. For background read this thread: https://lists.ubuntu.com/archives/ubuntu-devel/2016-May/039350.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1169437 Title: network-manager does not configure local resolver or dnsmasq to use the nameserver addresses received from the VPN server Status in network-manager-openvpn package in Ubuntu: Fix Released Bug description: NetworkManager/dnsmasq does not set the DNS servers given by the OpenVPN server when I connect. I can see in my syslog that I do receive the name server addresses correctly along with all the routes: Apr 16 08:14:09 homer NetworkManager[4014]:Internal DNS: 192.168.11.90 Apr 16 08:14:09 homer NetworkManager[4014]:Internal DNS: 192.168.11.190 However, they are not used: oscar@homer:~$ nmcli -f IP4 dev list | grep DNS IP4.DNS[1]: 192.168.0.1 oscar@homer:~$ (That is my default DNS/Gateway and it should still be queried for all DNS queries outside of VPN network) If I comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf and restart NetworkManager then DNS starts to work properly again, VPN nameservers are used for domain names on the VPN network and others through my default nameserver. Let me know if I kan provide further info about this issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Apr 16 08:16:42 2013 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-22 (144 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IpRoute: default via 192.168.0.1 dev eth1 proto static 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.44 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-04-16T08:12:17.691993 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1179bc6d7-cd13-4cfb-b73f-e8da8362a511 802-3-ethernet1364485020 tor 28 mar 2013 16:37:00 yes no /org/freedesktop/NetworkManager/Settings/2 Wiggum2a818c4e-494c-4b91-be56-630636608f07 802-11-wireless 1366092808 tis 16 apr 2013 08:13:28 yes no /org/freedesktop/NetworkManager/Settings/1 81e14bde-0b0b-42be-8b56-3bfda6ca60fc vpn 1366092850 tis 16 apr 2013 08:14:10 yes no /org/freedesktop/NetworkManager/Settings/0 aad98317-a8e1-4ff7-b3b5-7c43c1bcfd32 802-11-wireless 1358879064 tis 22 jan 2013 19:24:24 yes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1169437] Re: network-manager does not configure local resolver or dnsmasq to use the nameserver addresses received from the VPN server
QkiZ: Can you please provide details of the malfunction in your case? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1169437 Title: network-manager does not configure local resolver or dnsmasq to use the nameserver addresses received from the VPN server Status in network-manager-openvpn package in Ubuntu: Fix Released Bug description: NetworkManager/dnsmasq does not set the DNS servers given by the OpenVPN server when I connect. I can see in my syslog that I do receive the name server addresses correctly along with all the routes: Apr 16 08:14:09 homer NetworkManager[4014]:Internal DNS: 192.168.11.90 Apr 16 08:14:09 homer NetworkManager[4014]:Internal DNS: 192.168.11.190 However, they are not used: oscar@homer:~$ nmcli -f IP4 dev list | grep DNS IP4.DNS[1]: 192.168.0.1 oscar@homer:~$ (That is my default DNS/Gateway and it should still be queried for all DNS queries outside of VPN network) If I comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf and restart NetworkManager then DNS starts to work properly again, VPN nameservers are used for domain names on the VPN network and others through my default nameserver. Let me know if I kan provide further info about this issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Apr 16 08:16:42 2013 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-22 (144 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IpRoute: default via 192.168.0.1 dev eth1 proto static 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.44 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-04-16T08:12:17.691993 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1179bc6d7-cd13-4cfb-b73f-e8da8362a511 802-3-ethernet1364485020 tor 28 mar 2013 16:37:00 yes no /org/freedesktop/NetworkManager/Settings/2 Wiggum2a818c4e-494c-4b91-be56-630636608f07 802-11-wireless 1366092808 tis 16 apr 2013 08:13:28 yes no /org/freedesktop/NetworkManager/Settings/1 81e14bde-0b0b-42be-8b56-3bfda6ca60fc vpn 1366092850 tis 16 apr 2013 08:14:10 yes no /org/freedesktop/NetworkManager/Settings/0 aad98317-a8e1-4ff7-b3b5-7c43c1bcfd32 802-11-wireless 1358879064 tis 22 jan 2013 19:24:24 yes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1522057] Re: DNS resolution stops working after some time
This possibly arises from bug #1003842. What is possibly happening: the second or third nameserver on the list of available nameservers supplied to dnsmasq replies quickly to dnsmasq's query with a negative answer and dnsmasq immediately passes that negative answer back to the resolver. When dnsmasq is not used, the resolver tries the first nameserver on the list first, only trying the second nameserver after a timeout period. If this is the problem then the "correct" solution is to fix the malfunctioning nameserver or to remove it from the list. ** Changed in: dnsmasq (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1522057 Title: DNS resolution stops working after some time Status in dnsmasq package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: DNS resolution stops working after sometime (usually 10-20 minutes) in Lubuntu 15.10 The problem can be temporarily corrected after restarting network- manager using systemctl, but it starts again after 10-20 minutes. Looks like network-manager is not configuring dnsmasq properly. Output from 'nslookup google.com': ~ Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find google.com: REFUSED ~ Output from 'tcpdump -i lo port 53' while running above command: ~ 20:16:59.235879 IP localhost.38045 > comp0.arhome.info.domain: 28529+ A? google.com. (28) 20:16:59.286851 IP comp0.arhome.info.domain > localhost.38045: 28529 Refused 0/0/0 (28) ~ ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) CurrentDesktop: LXDE Date: Wed Dec 2 20:14:32 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-25 (68 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 172.16.84.1 dev wlan0 proto static metric 600 172.16.84.0/22 dev wlan0 proto kernel scope link src 172.16.84.50 metric 600 200.1.1.2 via 172.16.84.1 dev wlan0 proto dhcp metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-11-06 (25 days ago) nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/1 nn0.arhome.info bab29dc2-8a79-4170-8253-277286712124 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- vboxnet0 ethernet unmanaged/org/freedesktop/NetworkManager/Devices/3 -- ---- loloopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- 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/dnsmasq/+bug/1522057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1522057] Re: DNS resolution stops working after some time
** Summary changed: - DNS resolution stops working after sometime + DNS resolution stops working after some time -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1522057 Title: DNS resolution stops working after some time Status in dnsmasq package in Ubuntu: New Status in network-manager package in Ubuntu: Confirmed Bug description: DNS resolution stops working after sometime (usually 10-20 minutes) in Lubuntu 15.10 The problem can be temporarily corrected after restarting network- manager using systemctl, but it starts again after 10-20 minutes. Looks like network-manager is not configuring dnsmasq properly. Output from 'nslookup google.com': ~ Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find google.com: REFUSED ~ Output from 'tcpdump -i lo port 53' while running above command: ~ 20:16:59.235879 IP localhost.38045 > comp0.arhome.info.domain: 28529+ A? google.com. (28) 20:16:59.286851 IP comp0.arhome.info.domain > localhost.38045: 28529 Refused 0/0/0 (28) ~ ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) CurrentDesktop: LXDE Date: Wed Dec 2 20:14:32 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-25 (68 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 172.16.84.1 dev wlan0 proto static metric 600 172.16.84.0/22 dev wlan0 proto kernel scope link src 172.16.84.50 metric 600 200.1.1.2 via 172.16.84.1 dev wlan0 proto dhcp metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-11-06 (25 days ago) nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/1 nn0.arhome.info bab29dc2-8a79-4170-8253-277286712124 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- vboxnet0 ethernet unmanaged/org/freedesktop/NetworkManager/Devices/3 -- ---- loloopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- 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/dnsmasq/+bug/1522057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568787] Re: resolveconf does not reliable receive nameserver information from network manager
** Description changed: - resolveconf does not reliable receive nameserver information from - network manager. + resolvconf does not reliable receive nameserver information from + NetworkManager. In the journal I see things like: Apr 11 11:13:52 ottawa dnsmasq[3122]: setting upstream servers from DBus Apr 11 11:13:52 ottawa dnsmasq[3122]: using nameserver fe80::1#53 Apr 11 11:13:52 ottawa dnsmasq[3122]: using nameserver 192.168.1.254#53 Apr 11 11:13:52 ottawa dbus[978]: [system] Rejected send message, 13 matched rules; type="method_return", sender=":1.99" (uid=0 pid=3122 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=1017 comm="/usr/sbin/NetworkManager --no-daemon ") Apr 11 11:04:21 ottawa NetworkManager[1017]: DNS: starting dnsmasq... Apr 11 11:04:21 ottawa NetworkManager[1017]: dnsmasq not available on the bus, can't update servers. Apr 11 11:04:21 ottawa NetworkManager[1017]: [1460369061.825658] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name - - Doing this via dbus seems really odd, but I suspect messages between NetworkManager and the dnsmasq it spawns should not be rejected. + Doing this via dbus seems really odd, but I suspect messages between + NetworkManager and the dnsmasq it spawns should not be rejected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq-base 2.75-1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 11 11:17:34 2016 InstallationDate: Installed on 2016-01-26 (76 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - resolveconf does not reliable receive nameserver information from network manager + resolvconf does not reliable receive nameserver information from NetworkManager -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1568787 Title: resolvconf does not reliable receive nameserver information from NetworkManager Status in dbus package in Ubuntu: New Status in dnsmasq package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: resolvconf does not reliable receive nameserver information from NetworkManager. In the journal I see things like: Apr 11 11:13:52 ottawa dnsmasq[3122]: setting upstream servers from DBus Apr 11 11:13:52 ottawa dnsmasq[3122]: using nameserver fe80::1#53 Apr 11 11:13:52 ottawa dnsmasq[3122]: using nameserver 192.168.1.254#53 Apr 11 11:13:52 ottawa dbus[978]: [system] Rejected send message, 13 matched rules; type="method_return", sender=":1.99" (uid=0 pid=3122 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=1017 comm="/usr/sbin/NetworkManager --no-daemon ") Apr 11 11:04:21 ottawa NetworkManager[1017]: DNS: starting dnsmasq... Apr 11 11:04:21 ottawa NetworkManager[1017]: dnsmasq not available on the bus, can't update servers. Apr 11 11:04:21 ottawa NetworkManager[1017]: [1460369061.825658] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Doing this via dbus seems really odd, but I suspect messages between NetworkManager and the dnsmasq it spawns should not be rejected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq-base 2.75-1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 11 11:17:34 2016 InstallationDate: Installed on 2016-01-26 (76 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1568787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast
Do you have the "dnsmasq" package installed and is the instance of the dnsmasq program started by the "dnsmasq" package configured to listen at 127.0.1.1? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1534501 Title: [URGENT] dnsmasq errors fills up syslogs extremely fast Status in dnsmasq package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in resolvconf package in Ubuntu: New Status in rsyslog package in Ubuntu: New Bug description: snippet of logs. Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq exited with error: Network access problem (address in use; permissions; etc) (2) Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq child quit unexpectedly; refreshing DNS Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: starting dnsmasq... Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq not available on the bus, can't update servers. Jan 15 00:28:24 localhost NetworkManager[1211]: [1452846504.397836] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq exited with error: Network access problem (address in use; permissions; etc) (2) Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq child quit unexpectedly; refreshing DNS Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: starting dnsmasq... Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq not available on the bus, can't update servers. Jan 15 00:28:24 localhost NetworkManager[1211]: [1452846504.407691] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq exited with error: Network access problem (address in use; permissions; etc) (2) Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq child quit unexpectedly; refreshing DNS Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: starting dnsmasq... Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq not available on the bus, can't update servers. Jan 15 00:28:24 localhost NetworkManager[1211]: [1452846504.419365] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq exited with
[Desktop-packages] [Bug 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast
First, it appears that NetworkManager doesn't handle the error well and retries without sleeping. Needs fixing. Separate issue: Why is the error occurring on your machine? Why do you get "dnsmasq[30613]: failed to create listening socket for 127.0.1.1: Address already in use"? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1534501 Title: [URGENT] dnsmasq errors fills up syslogs extremely fast Status in dnsmasq package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in resolvconf package in Ubuntu: New Status in rsyslog package in Ubuntu: New Bug description: snippet of logs. Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq exited with error: Network access problem (address in use; permissions; etc) (2) Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq child quit unexpectedly; refreshing DNS Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: starting dnsmasq... Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq not available on the bus, can't update servers. Jan 15 00:28:24 localhost NetworkManager[1211]: [1452846504.397836] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq exited with error: Network access problem (address in use; permissions; etc) (2) Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq child quit unexpectedly; refreshing DNS Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: starting dnsmasq... Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq not available on the bus, can't update servers. Jan 15 00:28:24 localhost NetworkManager[1211]: [1452846504.407691] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq exited with error: Network access problem (address in use; permissions; etc) (2) Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq child quit unexpectedly; refreshing DNS Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: starting dnsmasq... Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq not available on the bus, can't update servers. Jan 15 00:28:24 localhost NetworkManager[1211]: [1452846504.419365] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15
[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Christian, the workaround is to comment out the line dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in dnsmasq source package in Precise: Confirmed Status in network-manager source package in Precise: Triaged Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and nameserver 127.0.0.1 to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430077] Re: [vivid] VPN connection breaks /etc/resolv.conf
Should this be reassigned to network-manager-openvpn? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1430077 Title: [vivid] VPN connection breaks /etc/resolv.conf Status in network-manager package in Ubuntu: Confirmed Bug description: After some recent update in vivid, connecting to my employer's VPN with network-manager-openvpn has resulted in broken name resolution. Previously, the VPN-provided nameserver setting would be pushed into the config of the dnsmasq run by NM. Now, it is being pushed instead to /etc/resolv.conf. nameserver 10.99.244.1 nameserver 127.0.1.1 This is breaking the DNS handling for libvirt-bin, which has its own forwarding dnsmasq instance which it expects to be able to talk to the first nameserver listed here. The nameserver in question does not work (and is not meant to be used) for any name lookups except company-internal domains. Connecting to the VPN also pushes search paths to /etc/resolv.conf - overriding the search domains that I have already configured, and which should take precedence. (This part is not a regression.) I understand that the purpose of these provided domains is to specify the domains for which DNS lookups should be forwarded to the VPN DNS server, and *not* to modify the system's DNS lookups for non-FQDN requests. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 9 17:16:05 2015 InstallationDate: Installed on 2010-09-24 (1627 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WWanEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2014-12-06 (93 days ago) 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/1430077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
** Changed in: network-manager (Ubuntu) Status: In Progress = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in dnsmasq source package in Precise: Confirmed Status in network-manager source package in Precise: Triaged Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and nameserver 127.0.0.1 to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430077] Re: [vivid] VPN connection breaks /etc/resolv.conf
Now, it is being pushed instead to /etc/resolv.conf. nameserver 10.99.244.1 nameserver 127.0.1.1 [...] Connecting to the VPN also pushes search paths to /etc/resolv.conf - overriding the search domains that I have already configured, and which should take precedence. Is this being done in NM itself, i.e., does NM send these two addresses in this order to resolvconf? Or does something else send the 10.99.244.1 address to resolvconf? Or does something else write directly to /etc/resolv.conf? This is breaking the DNS handling for libvirt-bin, which has its own forwarding dnsmasq instance which it expects to be able to talk to the first nameserver listed here. (As an aside, you may be interested in the discussion at #1163147. It is proposed there that the forwarding dnsmasq instance for libvirt compile its nameserver list using a resolvconf hook script, in the same manner as the plain dnsmasq does. Then if it is configured to listen on some loopback address it can be used on the host system to look up names of vm guests as well as other names.) The nameserver in question does not work (and is not meant to be used) for any name lookups except company-internal domains. Ah, so the VPN nameserver does not provide general DNS service; you rely on dnsmasq to route queries. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1430077 Title: [vivid] VPN connection breaks /etc/resolv.conf Status in network-manager package in Ubuntu: Confirmed Bug description: After some recent update in vivid, connecting to my employer's VPN with network-manager-openvpn has resulted in broken name resolution. Previously, the VPN-provided nameserver setting would be pushed into the config of the dnsmasq run by NM. Now, it is being pushed instead to /etc/resolv.conf. nameserver 10.99.244.1 nameserver 127.0.1.1 This is breaking the DNS handling for libvirt-bin, which has its own forwarding dnsmasq instance which it expects to be able to talk to the first nameserver listed here. The nameserver in question does not work (and is not meant to be used) for any name lookups except company-internal domains. Connecting to the VPN also pushes search paths to /etc/resolv.conf - overriding the search domains that I have already configured, and which should take precedence. (This part is not a regression.) I understand that the purpose of these provided domains is to specify the domains for which DNS lookups should be forwarded to the VPN DNS server, and *not* to modify the system's DNS lookups for non-FQDN requests. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 9 17:16:05 2015 InstallationDate: Installed on 2010-09-24 (1627 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WWanEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2014-12-06 (93 days ago) 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/1430077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 434477] Re: Nameserver addresses 4.2.2.1 and 4.2.2.2 end up in resolv.conf instead of ISP nameserver addresses -- Huawei E220
Does this bug still affect anyone? ** Changed in: network-manager (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/434477 Title: Nameserver addresses 4.2.2.1 and 4.2.2.2 end up in resolv.conf instead of ISP nameserver addresses -- Huawei E220 Status in network-manager package in Ubuntu: Incomplete Bug description: Binary package hint: network-manager When connecting in Karmic to my broadband connection the DNS informations isn't received around 70-80% of the times I connect, so I need to disconnect and reconnect until the info is received. (Confirmed by /etc/resolv.conf being empty except for a comment by the network manager) I don't know if this relates to the same problem, but I also some times have a problem accessing pages after a while, like it somehow decided to block all signals. (resolv.conf still has the info and the modem shows it's connected) I hope there's information enough to fix it, otherwise please instruct me on what to do to help debugging. ProblemType: Bug Architecture: amd64 CheckboxSubmission: 2483b723db6bd40eab5dccee54ef36fb CheckboxSystem: fb5f7a2788cceff50ba915d7273d1642 Date: Tue Sep 22 08:43:42 2009 DistroRelease: Ubuntu 9.10 IfupdownConfig: auto lo iface lo inet loopback IpRoute: 10.64.64.64 dev ppp0 proto kernel scope link src 95.209.250.39 169.254.0.0/16 dev ppp0 scope link metric 1000 default via 10.64.64.64 dev ppp0 proto static Package: network-manager 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6 ProcEnviron: LANGUAGE=en_US.UTF-8 LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.34-generic SourcePackage: network-manager Uname: Linux 2.6.31-10-generic x86_64 WpaSupplicantLog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/434477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1319805] Re: DNS confused with multiple interfaces (eth/wlan)
A workaround may be to edit /etc/NetworkManager/NetworkManager.conf and comment out the line dns=dnsmasq. ** Description changed: - Using a laptop with a hardware switch for enable/disable WLAN. - Connected to two different LANs using DHCP on ETH/WLAN. + I have a laptop with a hardware switch to enable or disable the WLAN + interface. - When both interfaces are active (in different networks), the system uses the LAN interface as the default route as expected. - But it does not use the the nameserver on that interface consistently. - It often tries to use the WLAN nameserver which leads to trouble as the WLAN nameserver does not know about the hosts on the LAN. + I am connected to two different LANs using DHCP via eth and wlan, + respectively. + + When both interfaces are active (in different networks), the system uses + the LAN interface as the default route as expected. + + However, it does not use the the nameserver on that interface + consistently. It often tries to use the WLAN nameserver which leads to + trouble as the WLAN nameserver does not know about the hosts on the LAN. The nameserver should be taken from the same interface as the default route to avoid messups. Ubuntu 12.04 did not have that behavior. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 Uname: Linux 3.15.0-031500rc2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu May 15 14:28:46 2014 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2014-04-24 (20 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) IpRoute: - default via 10.1.1.254 dev eth0 proto static - 8.0.0.0/24 dev vboxnet0 proto kernel scope link src 8.0.0.1 - 10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.42 metric 1 + default via 10.1.1.254 dev eth0 proto static + 8.0.0.0/24 dev vboxnet0 proto kernel scope link src 8.0.0.1 + 10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.42 metric 1 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true RfKill: - 0: phy0: Wireless LAN - Soft blocked: yes - Hard blocked: yes + 0: phy0: Wireless LAN + Soft blocked: yes + Hard blocked: yes SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-04-30T15:18:11.879306 nmcli-con: - NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH - Wired connection 158608da7-d199-4c51-a8f4-a7913363637f 802-3-ethernet1400156985 Do 15 Mai 2014 14:29:45 CEST yes no /org/freedesktop/NetworkManager/Settings/2 - afxhome 213a5a1b-daf7-4b28-b682-6c8934b20e4d 802-11-wireless 1400132352 Do 15 Mai 2014 07:39:12 CEST yes no /org/freedesktop/NetworkManager/Settings/1 - AtSec guest 6d860806-d458-4de0-bfcb-8e40c2185437 802-11-wireless 1400141574 Do 15 Mai 2014 10:12:54 CEST yes no /org/freedesktop/NetworkManager/Settings/0 + NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH + Wired connection 158608da7-d199-4c51-a8f4-a7913363637f 802-3-ethernet1400156985 Do 15 Mai 2014 14:29:45 CEST yes no /org/freedesktop/NetworkManager/Settings/2 + afxhome 213a5a1b-daf7-4b28-b682-6c8934b20e4d 802-11-wireless 1400132352 Do 15 Mai 2014 07:39:12 CEST yes no /org/freedesktop/NetworkManager/Settings/1 + AtSec guest 6d860806-d458-4de0-bfcb-8e40c2185437 802-11-wireless 1400141574 Do 15 Mai 2014 10:12:54 CEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: - DEVICE TYPE STATE DBUS-PATH - wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/1 - eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 + DEVICE TYPE STATE DBUS-PATH + wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/1 + eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: - RUNNING
[Desktop-packages] [Bug 929403] Re: Wireless login is not pre-filled with its stored password
** Summary changed: - Wireless login ignores its stored password + Wireless login is not pre-filled with its stored password -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/929403 Title: Wireless login is not pre-filled with its stored password Status in “network-manager” package in Ubuntu: Incomplete Bug description: On the Precise beta, every time I log in, the wireless login prompt appears, asking me to log into our password-protected wifi network. This is similar to what you get when you lose wifi signal, *except* that now the password entry box is empty, not pre-filled with the stored password. This could be related to warnings I've been getting from e.g. apt-get about not having a keyring socket to connect to. I would reproduce the exact message, except I don't seem to be getting it now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/929403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239316] Re: Network Manager asks for the password it already have
*** This bug is a duplicate of bug 1084364 *** https://bugs.launchpad.net/bugs/1084364 ** This bug has been marked a duplicate of bug 1084364 Network-Manager Repeatedly Asks for Authorization (WPA2 Password) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1239316 Title: Network Manager asks for the password it already have Status in “network-manager” package in Ubuntu: New Bug description: Network Manager asks for the password it already have, every time the WiFi goes down and up, even if it has saved it. I think this got fixed upstream sometime ago, not sure this is a regression or didn't got the fix in Kubuntu ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 13 13:15:07 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-10 (2 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.100 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH hussain 357764b9-8e9a-46f3-8d2c-1afbce5573b9 802-11-wireless 1381577113 12 أكت, 2013 AST 02:25:13 مyes no /org/freedesktop/NetworkManager/Settings/2 New 802-11-wireless connection 26eedf69-821e-4178-b4a8-3eb2b3d62edf 802-11-wireless 1381484555 11 أكت, 2013 AST 12:42:35 مyes no /org/freedesktop/NetworkManager/Settings/1 Saad 984440ea-af1b-46b1-b755-a865abddd155 802-11-wireless 1381659310 13 أكت, 2013 AST 01:15:10 مyes no /org/freedesktop/NetworkManager/Settings/0 Wired connection 1d57d073f-1609-48ed-8a35-a49c791f0691 802-3-ethernet1381649411 13 أكت, 2013 AST 10:30:11 صyes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1239316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1044955] Re: Xorg.log contains BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)'
Sorry, I no longer own the laptop where I had the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1044955 Title: Xorg.log contains BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)' Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: If I use Displays... to resize the display of the external monitor I get the following messages, repeated about forty times (with different time stamp, obviously). [ 12472.040] (II) intel(0): Allocated new frame buffer 2752x1050 stride 11264, tiled [ 12472.075] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)' BUG: ../../dix/getevents.c:850 in scale_to_desktop() [ 12472.075] Backtrace: [ 12472.075] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f922a950846] [ 12472.075] 1: /usr/bin/X (0x7f922a7c8000+0x622fe) [0x7f922a82a2fe] [ 12472.075] 2: /usr/bin/X (0x7f922a7c8000+0x62f6d) [0x7f922a82af6d] [ 12472.075] 3: /usr/bin/X (GetPointerEvents+0xe4) [0x7f922a82c304] [ 12472.075] 4: /usr/bin/X (0x7f922a7c8000+0x1730a6) [0x7f922a93b0a6] [ 12472.075] 5: /usr/bin/X (miPointerWarpCursor+0xe7) [0x7f922a93b527] [ 12472.075] 6: /usr/bin/X (0x7f922a7c8000+0x871b1) [0x7f922a84f1b1] [ 12472.075] 7: /usr/bin/X (0x7f922a7c8000+0x173a7c) [0x7f922a93ba7c] [ 12472.075] 8: /usr/bin/X (0x7f922a7c8000+0x112183) [0x7f922a8da183] [ 12472.075] 9: /usr/bin/X (0x7f922a7c8000+0xfd06e) [0x7f922a8c506e] [ 12472.075] 10: /usr/bin/X (RRPointerScreenConfigured+0x75) [0x7f922a8c5295] [ 12472.075] 11: /usr/bin/X (RRScreenSizeNotify+0x124) [0x7f922a8c7774] [ 12472.075] 12: /usr/bin/X (0x7f922a7c8000+0xc9876) [0x7f922a891876] [ 12472.075] 13: /usr/bin/X (ProcRRSetScreenSize+0x1e1) [0x7f922a8c7c81] [ 12472.076] 14: /usr/bin/X (0x7f922a7c8000+0x4e8a1) [0x7f922a8168a1] [ 12472.076] 15: /usr/bin/X (0x7f922a7c8000+0x3d7ba) [0x7f922a8057ba] [ 12472.076] 16: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f922898376d] [ 12472.076] 17: /usr/bin/X (0x7f922a7c8000+0x3daad) [0x7f922a805aad] System information ThinkPad X220 Ubuntu 12.04 with some packages upgraded to Quantal linux-image-3.5.0-10-generic 3.5.0-10.10 linux-image-extra-3.5.0-10-generic3.5.0-10.10 udev175-0ubuntu10 xserver-xorg 1:7.6+12ubuntu1 xserver-xorg-core 2:1.11.4-0ubuntu10.7 xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1 $ uname -a Linux tenerife 3.5.0-10-generic #10-Ubuntu SMP Mon Aug 13 15:23:58 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux $ lspci -s 00:02.0 -v 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 21da Flags: bus master, fast devsel, latency 0, IRQ 44 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 Kernel modules: i915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1044955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting
I just tried Trusty (dnsmasq 2.68-1), and network manager ships /etc/dnsmasq.d/network-manager with: bind-interfaces So now dnsmasq only binds 127.0.0.1 for its tftp service: udp 0 0 127.0.0.1:69 0.0.0.0:* 954/dnsmasq udp6 0 0 ::1:69 :::* 954/dnsmasq ...and of course that breaks everything. Removing that file makes tftp work again. Alkis, does it work properly if you change bind-interfaces to bind- dynamic? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/959037 Title: NM-controlled dnsmasq prevents other DNS servers from starting Status in “djbdns” package in Ubuntu: Confirmed Status in “dnsmasq” package in Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Confirmed Status in “pdns-recursor” package in Ubuntu: Invalid Status in “pdnsd” package in Ubuntu: Invalid Status in “djbdns” source package in Precise: Confirmed Status in “dnsmasq” source package in Precise: Triaged Status in “network-manager” source package in Precise: Triaged Status in “pdns-recursor” source package in Precise: Invalid Status in “pdnsd” source package in Precise: Invalid Bug description: As described in https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-dns- resolving, network manager now starts a dnsmasq instance for local DNS resolving. That breaks the default bind9 and dnsmasq installations, for people that actually want to install a DNS server. Having to manually comment out #dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf doesn't sound good, and if it stays that way, it should be moved to the bind9 and dnsmasq postinst scripts. Please make network-manager smarter so that it checks if bind9 or dnsmasq are installed, so that it doesn't start the local resolver in that case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
I see that a lot of work has been done to get this change into precise, but it is not clear to me what the status of this change is for raring and saucy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Confirmed Status in OEM Priority Project raring series: Won't Fix Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “libx11” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Fix Released Status in “x11proto-core” package in Ubuntu: New Status in “xkeyboard-config” package in Ubuntu: New Status in “xserver-xorg-input-evdev” package in Ubuntu: Won't Fix Status in “gnome-settings-daemon” source package in Precise: New Status in “libx11” source package in Precise: Fix Released Status in “udev” source package in Precise: Fix Released Status in “x11proto-core” source package in Precise: Fix Released Status in “xkeyboard-config” source package in Precise: New Status in “xserver-xorg-input-evdev” source package in Precise: Won't Fix Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “libx11” source package in Raring: New Status in “udev” source package in Raring: Triaged Status in “x11proto-core” source package in Raring: New Status in “xkeyboard-config” source package in Raring: New Status in “xserver-xorg-input-evdev” source package in Raring: Won't Fix Bug description: [Impact] * People buying thinkpad hardware are not able to use a mic mute key, that comes with their machine [Test Case] * Press mic mute key * Observe that nothing happens [Regression Potential] * Very low. This is very isolated code. All it does is add functionality. In fact there are very few deletions in the diffs. * There is an existing acpi solution, that's already been mentioned in this bug. I'm not sure how these users would be affected once the upgrade hits, but it was never released as an official fix. [Original Report] Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 0080 101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1231893] Re: dnsmasq sometimes lose primary dns (saucy)
@Franck: See bug #1003842 for information about using dnsmasq with non- equivalent upstream nameservers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1231893 Title: dnsmasq sometimes lose primary dns (saucy) Status in “network-manager” package in Ubuntu: Invalid Bug description: Since I upgraded to Saucy, my local dnsmasq instance seems to lose its primary dns server and fallback to secondary dns. Since the primary dns is a dnsmasq instance that knows of local servers, and the secondary one is external, my local dnsmasq instance fails to resolv local server names. This does not happen on startup, it happens after some time. Restarting solves the issue. It does not happen on Raring... not sure where to look for to resolve this issue... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 27 09:25:37 2013 InstallationDate: Installed on 2013-02-16 (222 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216) MarkForUpload: True SourcePackage: dnsmasq UpgradeStatus: Upgraded to saucy on 2013-09-19 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1231893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1015493] Re: If it obtains the same nameserver address for multiple interfaces, NM fails to de-duplicate the list of addresses it gives to dnsmasq via nm-dns-dnsmasq.conf and j
This bug still exists even though NM now communicates with dnsmasq over D-Bus. Aug 25 21:31:33 sanrife dnsmasq[7027]: using nameserver 192.168.1.254#53 Aug 25 21:31:33 sanrife dnsmasq[7027]: using nameserver 192.168.1.254#53 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1015493 Title: If it obtains the same nameserver address for multiple interfaces, NM fails to de-duplicate the list of addresses it gives to dnsmasq via nm-dns-dnsmasq.conf and just includes the same address multiple times Status in “network-manager” package in Ubuntu: Confirmed Bug description: From /var/log/syslog: Jun 20 10:03:25 tenerife dhclient: DHCPREQUEST of 192.168.2.103 on eth0 to 255.255.255.255 port 67 Jun 20 10:03:25 tenerife dhclient: DHCPOFFER of 192.168.2.103 from 192.168.2.254 Jun 20 10:03:25 tenerife dhclient: DHCPACK of 192.168.2.103 from 192.168.2.254 Jun 20 10:03:25 tenerife dhclient: bound to 192.168.2.103 -- renewal in 276336 seconds. Jun 20 10:03:25 tenerife NetworkManager[1090]: info (eth0): DHCPv4 state changed preinit - bound Jun 20 10:03:25 tenerife NetworkManager[1090]: info address 192.168.2.103 Jun 20 10:03:25 tenerife NetworkManager[1090]: info prefix 24 (255.255.255.0) Jun 20 10:03:25 tenerife NetworkManager[1090]: info gateway 192.168.2.254 Jun 20 10:03:25 tenerife NetworkManager[1090]: info nameserver '192.168.2.254' Jun 20 10:03:25 tenerife NetworkManager[1090]: info Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Jun 20 10:03:25 tenerife NetworkManager[1090]: info Activation (eth0) Stage 5 of 5 (IPv4 Commit) started... # cat /var/run/nm-dns-dnsmasq.conf server=192.168.2.254 server=192.168.2.254 --- ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 12.04 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 192.168.20.254 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.20.0/24 dev eth0 proto kernel scope link src 192.168.20.103 metric 1 192.168.20.0/24 dev wlan0 proto kernel scope link src 192.168.20.196 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 0.9.4.0+git201206081144.2efeac8-0ubuntu1th1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Tags: precise Uname: Linux 3.2.0-26-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-07-04T09:47:16.565166 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1015493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1180368] Re: Network indicator displays random text for bluetooth network name
I just tested again with network-manager 0.9.8.0-0ubuntu16 I see the same problem. Actually, after connecting twice to phone the indicator disappeared entirely. The nmcli c list command run in a terminal shows the correct name of the connection and nmcli c up can be used to activate it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1180368 Title: Network indicator displays random text for bluetooth network name Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: The attached images tell most of the story. I set up Bluetooth tethering on my phone with name Searle. I boot my Ubuntu laptop. Searle is shown in the network indicator menu. After I connect nm-applet is shown. After I disconnect _Configure VPN... is shown. At other times I have seen the words separator, Label Empty and I have also een undisplayable characters. network-manager 0.9.8.0-0ubuntu6 on machine recently upgraded to Ubuntu 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1180368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1180368] Re: Network indicator displays random text for bluetooth network name
(cont'd) I logged out and in and the indicator was back. I connected and disconnect the bluetooth connection and saw Label Empty as the connection name. (Sometimes I see random characters instead.) I then did sudo restart network-manager in a terminal and this caused the indicator to disappear momentarily; after it reappeared it listed (when clicked on) the bluetooth connection under the correct name. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1180368 Title: Network indicator displays random text for bluetooth network name Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: The attached images tell most of the story. I set up Bluetooth tethering on my phone with name Searle. I boot my Ubuntu laptop. Searle is shown in the network indicator menu. After I connect nm-applet is shown. After I disconnect _Configure VPN... is shown. At other times I have seen the words separator, Label Empty and I have also een undisplayable characters. network-manager 0.9.8.0-0ubuntu6 on machine recently upgraded to Ubuntu 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1180368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 980579] Re: It's impossible to ignore VPN provided DNS servers
Hi Alkis, Do you still have this problem? Or was it fixed in resolvconf 1.67ubuntu2: resolvconf (1.67ubuntu2) quantal; urgency=low [...] * Update ppp hooks to also exit when passed /org/freedesktop/NetworkManager/PPP/* (LP: #994575) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/980579 Title: It's impossible to ignore VPN provided DNS servers Status in “network-manager-pptp” package in Ubuntu: Triaged Bug description: I have a desktop Precise installation with a normal dnsmasq installed, so I disabled the nm-spawned dnsmasq instance from NetworkManager.conf. I create a VPN connection in Network Manager without specifying any DNS servers. When I connect to it, I get: $ cat /var/run/dnsmasq/resolv.conf nameserver 150.140.1.4 nameserver 150.140.1.25 nameserver 127.0.0.1 nameserver 194.63.238.4 nameserver 8.8.8.8 I want to ignore the first two entries which are provided by my VPN. So I go to the VPN connection editor and I declare DNS=127.0.0.1. But again I get the same /var/run/dnsmasq/resolv.conf, so my DNS server entry there is completely ignored by network-manager and/or resolvconf. How can I tell Network Manager and/or resolvconf to ignore the DNS servers provided by my VPN connection? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/980579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 980579] Re: It's impossible to ignore VPN provided DNS servers
If you have a chance to test a more recent resolvconf release, please report back with your findings. ** Changed in: network-manager-pptp (Ubuntu) Status: Triaged = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/980579 Title: It's impossible to ignore VPN provided DNS servers Status in “network-manager-pptp” package in Ubuntu: Incomplete Bug description: I have a desktop Precise installation with a normal dnsmasq installed, so I disabled the nm-spawned dnsmasq instance from NetworkManager.conf. I create a VPN connection in Network Manager without specifying any DNS servers. When I connect to it, I get: $ cat /var/run/dnsmasq/resolv.conf nameserver 150.140.1.4 nameserver 150.140.1.25 nameserver 127.0.0.1 nameserver 194.63.238.4 nameserver 8.8.8.8 I want to ignore the first two entries which are provided by my VPN. So I go to the VPN connection editor and I declare DNS=127.0.0.1. But again I get the same /var/run/dnsmasq/resolv.conf, so my DNS server entry there is completely ignored by network-manager and/or resolvconf. How can I tell Network Manager and/or resolvconf to ignore the DNS servers provided by my VPN connection? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/980579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995332] Re: Validate DNSSEC by default
** 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 Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/995332 Title: Please enhance NetworkManager such that DNSSEC validation is done whenever possible Status in “dnsmasq” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Triaged Bug description: Network Manager in Precise uses a local forwarding DNS server (dnsmasq). This does not perform DNSSEC validation, although it is configured to proxy the DNSSEC validation result from the upstream server, for which the manpage mentions the following caveat: You should only do this if you trust all the configured upstream nameservers and the network between you and them. Since not all networks or upstream DNS servers are trustworthy, the safest place to perform DNSSEC validation is on the client. Using a local DNS server which cannot validate is a missed opportunity; by replacing dnsmasq with a more-capable DNS server (e.g. Unbound) security against DNS poisoning and MITM attacks could be improved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/995332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1191680] Re: nameserver in /etc/resolv.conf didn't update when changing network
*** This bug is a duplicate of bug 1000244 *** https://bugs.launchpad.net/bugs/1000244 To solve, please open a terminal window and run sudo dpkg-reconfigure resolvconf. ** This bug has been marked a duplicate of bug 1000244 Symlink /etc/resolv.conf does not exist after installation or upgrade of resolvconf -- various causes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1191680 Title: nameserver in /etc/resolv.conf didn't update when changing network Status in “network-manager” package in Ubuntu: New Bug description: When changeing network and connecting to a new router,(sitecom cfe88) i couldn't surf. Surfing worked in windows in my dual boot, and in another lan a home, so i knew it should work. Everything seemed ok in nw-manager - connected fine, got an ip and so on - and i had turned off ipv6 just to be sure. Then i had a look at /etc/resolv.conf - and there it was - it had one nameserver entry, and it was the one from my homenetwork - wtf. I changed that manually to the router i was connecting to - and it worked. Now, why didn't it update this by itself when switching networks. A less techical user would be stuck. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Mon Jun 17 08:13:26 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-09 (68 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130409) IpRoute: default via 192.168.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.107 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1191680/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1172467] Re: NetworkManager uses dnsmasq with negative DNS cache enabled
** 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 Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1172467 Title: Dnsmasq caches negative results if it starts before the network is up Status in “dnsmasq” package in Ubuntu: New Bug description: Since NetworkManager uses dnsmasq to resolve its DNS names, it sometimes enables the system to use dnsmasq before the network connection has been successfully established. This causes dnsmasq to try and fail to resolve some hostnames, it then caches them to its negative DNS cache. To prevent this from happening I had to add no-negcache to /etc/dnsmasq.d/network-manager Should this be the default? I don't think any endpoint user benefits from negative DNS cache, not even network admins as the DNS system is robust enough to handle those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1172467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170353] Re: Host names intermittently resolve to 0.0.0.0
Could it have been a problem with your nameserver? ** Changed in: network-manager (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1170353 Title: Host names intermittently resolve to 0.0.0.0 Status in “network-manager” package in Ubuntu: Invalid Bug description: About 5% of DNS queries resolve to 0.0.0.0. A couple of times an hour during normal browsing, Firefox resolves a domain to 0.0.0.0. Opening the same site in Chrome has a 50% chance of it working, then it normally works after a few reloads. Thunderbird has also occasionally resolved googlemail.com to 0.0.0.0. Domains include google.com, wikipedia.org, harvestapp.com and many more. I couldn't reproduce this with dig/nslookup for a while, but after 5 minutes of (re)trying random domains) did: $ dig mail.google.com ; DiG 9.8.1-P1 mail.google.com ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 22905 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;mail.google.com. IN A ;; ANSWER SECTION: mail.google.com. 60 IN A 0.0.0.0 ;; Query time: 0 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Thu Apr 18 13:57:04 2013 ;; MSG SIZE rcvd: 49 Note the 0 msec, so I'm pretty sure this is dnsmasq's local cache. Using Xubuntu 12.10, NetworkManager 0.9.6.0, Dnsmasq 2.63rc6. NetworkManager has DNS servers set to 8.8.8.8, 8.8.4.4 (also tried setting it to my router's DNS server, with no effect). /etc/resolve.conf just has nameserver 127.0.1.1 dnsmasq is currently running: /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind- interfaces --pid-file=/var/run/sendsigs.omit.d/network- manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run /nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec --enable- dbus=org.freedesktop.NetworkManager.dnsmasq --conf- dir=/etc/NetworkManager/dnsmasq.d ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Apr 18 14:27:33 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-11 (97 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) IpRoute: default via 10.0.0.1 dev eth0 proto static 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.10 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Apr 18 09:48:24 base100 kernel: [ 3679.586853] xhci_hcd :00:14.0: WARN Event TRB for slot 1 ep 0 with no TDs queued? Apr 18 10:09:03 base100 kernel: [ 4916.445925] xhci_queue_intr_tx: 39 callbacks suppressed Apr 18 10:09:06 base100 kernel: [ 4919.096387] xhci_hcd :00:14.0: WARN Event TRB for slot 1 ep 0 with no TDs queued? Apr 18 13:50:09 base100 kernel: [18155.501321] xhci_hcd :00:14.0: WARN Event TRB for slot 1 ep 0 with no TDs queued? mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-01-11T14:15:17.434186 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH YB SmarTrack 71694158-7304-4ff6-9092-7cc19e22acf4 vpn 1366020364 Mon 15 Apr 2013 11:06:04 BST nono /org/freedesktop/NetworkManager/Settings/1 Wired connection 181386800-1e66-4f17-88d3-37233ab45958 802-3-ethernet1366291620 Thu 18 Apr 2013 14:27:00 BST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1169437] Re: network-manager dnsmasq openvpn DNS issue
Please look through the bugs already filed against network-manager- openvpn to see if this issue has been reported before. ** Package changed: network-manager (Ubuntu) = network-manager-openvpn (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1169437 Title: network-manager dnsmasq openvpn DNS issue Status in “network-manager-openvpn” package in Ubuntu: Confirmed Bug description: NetworkManager/dnsmasq does not set the DNS servers given by openvpn server when I connect. I can see in my syslog that I do receive the name servers correctly along with all the routes: Apr 16 08:14:09 homer NetworkManager[4014]: info Internal DNS: 192.168.11.90 Apr 16 08:14:09 homer NetworkManager[4014]: info Internal DNS: 192.168.11.190 However they are not used: oscar@homer:~$ nmcli -f IP4 dev list | grep DNS IP4.DNS[1]: 192.168.0.1 oscar@homer:~$ (That is my default DNS/Gateway and it should still be queried for all DNS queries outside of VPN network) If I comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf and oc restart NetworkManager all DNS start to work properly again, VPN DNS's are used for those resources on the VPN network and others through my default DNS. Let me know if I kan provide further info about this issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Apr 16 08:16:42 2013 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-22 (144 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IpRoute: default via 192.168.0.1 dev eth1 proto static 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.44 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-04-16T08:12:17.691993 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1179bc6d7-cd13-4cfb-b73f-e8da8362a511 802-3-ethernet1364485020 tor 28 mar 2013 16:37:00 yes no /org/freedesktop/NetworkManager/Settings/2 Wiggum2a818c4e-494c-4b91-be56-630636608f07 802-11-wireless 1366092808 tis 16 apr 2013 08:13:28 yes no /org/freedesktop/NetworkManager/Settings/1 81e14bde-0b0b-42be-8b56-3bfda6ca60fc vpn 1366092850 tis 16 apr 2013 08:14:10 yes no /org/freedesktop/NetworkManager/Settings/0 aad98317-a8e1-4ff7-b3b5-7c43c1bcfd32 802-11-wireless 1358879064 tis 22 jan 2013 19:24:24 yes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1163047] Re: with multiple connections, puts dnsmasq servers in wrong order
*** This bug is a duplicate of bug 1003842 *** https://bugs.launchpad.net/bugs/1003842 As of Ubuntu 12.10 you can't deal with bug #1003842 (dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers) by turning on strict-order in /etc/NetworkManager/dnsmasq.d/. The reason is that, since 12.10, NM sends nameserver addresses to dnsmasq over D-Bus; and in that case the order of the nameservers is not preserved. https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1003842/comments/49 The best workaround is to comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf and then restart network- manager. ** Summary changed: - with multiple connections, puts dnsmasq servers in wrong order + NM + dnsmasq: server addresses in the wrong order ** This bug has been marked a duplicate of bug 1003842 dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1163047 Title: NM + dnsmasq: server addresses in the wrong order Status in “network-manager” package in Ubuntu: Confirmed Bug description: My corporate DHCP servers send 3 DNS servers: 2 internal ones, and a tertiary backup of 8.8.8.8. If I only connect wired or wireless, everything appears to work fine as long as I've added strict-order to /etc/NetworkManager/dnsmasq.d/options, but if I connect both, it appears to invert the first list sent to dnsmasq, and I end up unable to resolve internal hostnames. nm-tool output: - Device: eth0 [Auto eth0] ... DNS: 10.0.5.25 DNS: 10.0.5.26 DNS: 8.8.8.8 - Device: wlan0 [Auto COMPANY AP] --- ... DNS: 10.0.5.25 DNS: 10.0.5.26 DNS: 8.8.8.8 syslog output: Apr 1 16:04:42 taplop NetworkManager[1744]: info ((null)): writing resolv.conf to /sbin/resolvconf Apr 1 16:04:42 taplop dnsmasq[2155]: setting upstream servers from DBus Apr 1 16:04:42 taplop dnsmasq[2155]: using nameserver 8.8.8.8#53 Apr 1 16:04:42 taplop dnsmasq[2155]: using nameserver 10.0.5.26#53 Apr 1 16:04:42 taplop dnsmasq[2155]: using nameserver 10.0.5.25#53 Apr 1 16:04:42 taplop dnsmasq[2155]: using nameserver 10.0.5.25#53 Apr 1 16:04:42 taplop dnsmasq[2155]: using nameserver 10.0.5.26#53 Apr 1 16:04:42 taplop dnsmasq[2155]: using nameserver 8.8.8.8#53 nslookup outputs hitting dnsmasq vs/ internal nameserver directly: $ nslookup rb 127.0.1.1 Server: 127.0.1.1 Address: 127.0.1.1#53 Non-authoritative answer: Name: rb.company.com Address: [www.company.com] $ nslookup rb 10.0.1.25 Server: 10.0.1.25 Address: 10.0.1.25#53 rb.company.comcanonical name = rbp01.company.com. Name: rbp01.company.com Address: 10.0.1.35 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Apr 1 16:05:18 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2010-04-19 (1078 days ago) InstallationMedia: Ubuntu 10.04 Lucid Lynx - Release Candidate amd64 (20100419.1) IpRoute: default via 10.9.5.1 dev eth0 proto static 10.9.5.0/24 dev eth0 proto kernel scope link src 10.9.5.59 metric 1 10.9.5.0/24 dev wlan0 proto kernel scope link src 10.9.5.58 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-10-05 (178 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/2 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1163047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
I was about to test the new versions of the various packages but then I noticed that x11proto-core isn't currently installed on my Ubuntu Desktop 13.04 system. So clearly I am failing to understand something. Exactly which package versions should I install on Ubuntu Desktop 13.04 in order to test the newly added support for the ThinkPad microphone mute button? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Confirmed Status in OEM Priority Project raring series: Won't Fix Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Fix Released Status in “x11proto-core” package in Ubuntu: New Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Precise: New Status in “udev” source package in Precise: New Status in “x11proto-core” source package in Precise: Fix Committed Status in “xserver-xorg-input-evdev” source package in Precise: New Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “x11proto-core” source package in Raring: New Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: [Impact] * People buying thinkpad hardware are not able to use a mic mute key, that comes with their machine [Test Case] * Press mic mute key * Observe that nothing happens [Regression Potential] * Very low. This is very isolated code. All it does is add functionality. In fact there are very few deletions in the diffs. * There is an existing acpi solution, that's already been mentioned in this bug. I'm not sure how these users would be affected once the upgrade hits, but it was never released as an official fix. [Original Report] Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 0080 101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1180368] Re: Network indicator displays random text for bluetooth network name
Not fixed by this: https://launchpad.net/ubuntu/+source/libdbusmenu/12.10.3daily13.06.19~13.04-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1180368 Title: Network indicator displays random text for bluetooth network name Status in “network-manager-applet” package in Ubuntu: New Bug description: The attached images tell most of the story. I set up Bluetooth tethering on my phone with name Searle. I boot my Ubuntu laptop. Searle is shown in the network indicator menu. After I connect nm-applet is shown. After I disconnect _Configure VPN... is shown. At other times I have seen the words separator, Label Empty and I have also een undisplayable characters. network-manager 0.9.8.0-0ubuntu6 on machine recently upgraded to Ubuntu 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1180368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878277] Re: Keyboard Layout Options | Alt/Win behavior incomprehensible
No improvement in Ubuntu 13.04. ** Tags added: quantal raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/878277 Title: Keyboard Layout Options | Alt/Win behavior incomprehensible Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just upgraded to oneiric. The Keyboard Layout Options | Alt/Win key behavior alternatives are: * Default - So what is the default? * Add the standard behaviour to Menu key - What is the standard behaviour? What is its relation to the default? - Which is the Menu key? * Alt is mapped to Right Win, Super to Menu - What does mapped to mean? The term map is symmetrical, but the application here is asymmetrical. Does this option map the Alt function to the Right Win key, or the Right Win function to the Alt keys? Presumably the first, but it isn't clear. Please say something like Alt functionality * Alt and Meta are on Alt keys - Does this mean that Alt functionality is mapped to the left Alt key and Meta to the right Alt key? Or what? Not clear. * Left Alt is swapped with Left Win - This and other options are not inherently mutually exclusive. So why are these options on radio buttons? A Help button on the dialog would be nice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/878277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 989900] Re: Various people have a bunch of unrelated problems with name resolution in Ubuntu 12.04
Can someone please tell set the status back to incomplete? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/989900 Title: Various people have a bunch of unrelated problems with name resolution in Ubuntu 12.04 Status in “network-manager” package in Ubuntu: Fix Released Bug description: I just updated to Ubuntu 12.04. After the update I cannot resolve hostnames reliably: I use Konsole in Unity. There sometimes the DNS resolving works fine and suddenly after two commands or so it fails for the same address. E.g. I ping a machine without DNS-Suffix (the suffix is shown in my network config correctly aside 3 valid nameserver IPs) and everything works fine. Then I try to log into the machine with the same address via ssh and I get a Name or service not known. Trying again, it works with a fully qualified name containing the suffix. I also had cases, when the IP wasn't resolved although I put in the fully qualified name. When I am more lucky, it starts working again with machine names only (without suffix, which is configured and worked perfectly up to now) Is there probably a bug in the new Ubuntu Version? --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.4.0-0ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: precise Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-05-09T05:01:02.241358 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1a76f352c-6e8c-49c7-bc05-b890445abb22 802-3-ethernet1336943434 Sun 13 May 2012 05:10:34 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 Ladner Computer Repair L.N.A 47560d22-54ec-491b-b90f-a41535d69f00 802-11-wireless 1337213171 Wed 16 May 2012 08:06:11 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/989900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 989900] Re: Various people have a bunch of unrelated problems with name resolution in Ubuntu 12.04
Can someone please set the status back to incomplete? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/989900 Title: Various people have a bunch of unrelated problems with name resolution in Ubuntu 12.04 Status in “network-manager” package in Ubuntu: Fix Released Bug description: I just updated to Ubuntu 12.04. After the update I cannot resolve hostnames reliably: I use Konsole in Unity. There sometimes the DNS resolving works fine and suddenly after two commands or so it fails for the same address. E.g. I ping a machine without DNS-Suffix (the suffix is shown in my network config correctly aside 3 valid nameserver IPs) and everything works fine. Then I try to log into the machine with the same address via ssh and I get a Name or service not known. Trying again, it works with a fully qualified name containing the suffix. I also had cases, when the IP wasn't resolved although I put in the fully qualified name. When I am more lucky, it starts working again with machine names only (without suffix, which is configured and worked perfectly up to now) Is there probably a bug in the new Ubuntu Version? --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.4.0-0ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: precise Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-05-09T05:01:02.241358 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1a76f352c-6e8c-49c7-bc05-b890445abb22 802-3-ethernet1336943434 Sun 13 May 2012 05:10:34 PM EDTyes no /org/freedesktop/NetworkManager/Settings/1 Ladner Computer Repair L.N.A 47560d22-54ec-491b-b90f-a41535d69f00 802-11-wireless 1337213171 Wed 16 May 2012 08:06:11 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/989900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1180368] [NEW] Network indicator displays random text for bluetooth network name
Public bug reported: The attached images tell most of the story. I set up Bluetooth tethering on my phone with name Searle. I boot my Ubuntu laptop. Searle is shown in the network indicator menu. After I connect nm-applet is shown. After I disconnect _Configure VPN... is shown. At other times I have seen the words separator, Label Empty and I have also een undisplayable characters. network-manager 0.9.8.0-0ubuntu6 on machine recently upgraded to Ubuntu 13.04. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1180368 Title: Network indicator displays random text for bluetooth network name Status in “network-manager-applet” package in Ubuntu: New Bug description: The attached images tell most of the story. I set up Bluetooth tethering on my phone with name Searle. I boot my Ubuntu laptop. Searle is shown in the network indicator menu. After I connect nm-applet is shown. After I disconnect _Configure VPN... is shown. At other times I have seen the words separator, Label Empty and I have also een undisplayable characters. network-manager 0.9.8.0-0ubuntu6 on machine recently upgraded to Ubuntu 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1180368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1180368] Re: Network indicator displays random text for bluetooth network name
** Attachment added: network indicator menu - 1 - after boot.png https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1180368/+attachment/3677285/+files/network%20indicator%20menu%20-%201%20-%20after%20boot.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1180368 Title: Network indicator displays random text for bluetooth network name Status in “network-manager-applet” package in Ubuntu: New Bug description: The attached images tell most of the story. I set up Bluetooth tethering on my phone with name Searle. I boot my Ubuntu laptop. Searle is shown in the network indicator menu. After I connect nm-applet is shown. After I disconnect _Configure VPN... is shown. At other times I have seen the words separator, Label Empty and I have also een undisplayable characters. network-manager 0.9.8.0-0ubuntu6 on machine recently upgraded to Ubuntu 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1180368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1180368] Re: Network indicator displays random text for bluetooth network name
** Attachment added: network indicator menu - 2 - after connect.png https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1180368/+attachment/3677286/+files/network%20indicator%20menu%20-%202%20-%20after%20connect.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1180368 Title: Network indicator displays random text for bluetooth network name Status in “network-manager-applet” package in Ubuntu: New Bug description: The attached images tell most of the story. I set up Bluetooth tethering on my phone with name Searle. I boot my Ubuntu laptop. Searle is shown in the network indicator menu. After I connect nm-applet is shown. After I disconnect _Configure VPN... is shown. At other times I have seen the words separator, Label Empty and I have also een undisplayable characters. network-manager 0.9.8.0-0ubuntu6 on machine recently upgraded to Ubuntu 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1180368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1180368] Re: Network indicator displays random text for bluetooth network name
** Attachment added: network indicator menu - 3 - after disconnect.png https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1180368/+attachment/3677287/+files/network%20indicator%20menu%20-%203%20-%20after%20disconnect.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1180368 Title: Network indicator displays random text for bluetooth network name Status in “network-manager-applet” package in Ubuntu: New Bug description: The attached images tell most of the story. I set up Bluetooth tethering on my phone with name Searle. I boot my Ubuntu laptop. Searle is shown in the network indicator menu. After I connect nm-applet is shown. After I disconnect _Configure VPN... is shown. At other times I have seen the words separator, Label Empty and I have also een undisplayable characters. network-manager 0.9.8.0-0ubuntu6 on machine recently upgraded to Ubuntu 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1180368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034725] Re: System will not create adhoc network.
** Package changed: gnome-control-center (Ubuntu) = network-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1034725 Title: System will not create adhoc network. Status in “network-manager” package in Ubuntu: New Bug description: Attempts to do so for about 60 seconds, then gives message Wireless network disconnected The feature worked fine until about 8-9 days ago. I did recommended updates on 29 July and 30 July. The problem started after that, so I believe it might be a problem with an updated package somewhere. Perhaps I need to change back to an earlier version of a package, but I do not know which one. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.4 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Thu Aug 9 11:02:05 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1685): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed (gnome-settings-daemon:1652): GLib-CRITICAL **: g_variant_get_int32: assertion `g_variant_is_of_type (value, G_VARIANT_TYPE_INT32)' failed (nm-applet:1702): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `dest_y = 0 dest_y + dest_height = dest-height' failed (gnome-settings-daemon:1652): GnomeDesktop-WARNING **: Timed out waiting for GL_MAX_TEXTURE_SIZE helper (firefox:1994): Gdk-CRITICAL **: IA__gdk_window_get_user_data: assertion `GDK_IS_WINDOW (window)' failed usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1034725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1130326] Re: No Certificate Authority Certificate Dialog doesn't receive focus
** Package changed: network-manager (Ubuntu) = network-manager-applet (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1130326 Title: No Certificate Authority Certificate Dialog doesn't receive focus Status in “network-manager-applet” package in Ubuntu: New Bug description: Using Gnome 3.Ubuntu 12.04.2 LTS network-manager 0.9.4.0-0ubuntu4.2 - I'm adding a new wireless network that uses certificates; tunneled tls - I do not select a CA certificate in the initial dialog Authentication required by wireless network - I get a warning popup No certificate authority certificate chosen with ignore and select (or similar) - But this popup is not in focus, the buttons can't be clicked and the dialog can't be dismissed. - I can't proceed except by clicking cancel in the partially-obscured Authentication dialog. The result of this is that I can't use a self-signed certificate, and so can't use the network. When I do go to select a certificate, it filters by file extension. The filter can't be disabled, so I don't see and can't select my certificates. Note that when exporting certs e.g. from Thunderbird, the extension is not added automatically, so it's likely that certs won't have an appropriate extension. Then in continuing interaction, gnome-settings manager segfaults. I've used the autoreport function to file that separately. peace, isaac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1130326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1129076] Re: Network manager becomes partly unresponsive
** Package changed: network-manager (Ubuntu) = network-manager-applet (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1129076 Title: Network manager becomes partly unresponsive Status in “network-manager-applet” package in Ubuntu: New Bug description: After some amount of time working, or especially after a suspend-awake cycle, the gnome network manager controls under the network icon on my top bar stops working. When I click on it, I get a normal list of wired/wireless choices. But selecting something (e.g. to turn the network off, or wireless on/off) has no effect. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Feb 18 08:02:51 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-12-13 (67 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IpRoute: default via 132.206.112.1 dev eth0 proto static 132.206.112.0/26 dev eth0 proto kernel scope link src 132.206.112.10 metric 1 142.157.168.0/23 dev wlan0 proto kernel scope link src 142.157.168.7 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-12-12T20:12:59.480551 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1129076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1128985] Re: NM tries to run VPN service with wrong path
The latest version in raring is 0.9.7.995+git201301311547.17123fc- 0ubuntu1. Does it still have the bug? ** Changed in: network-manager (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1128985 Title: NM tries to run VPN service with wrong path Status in “network-manager” package in Ubuntu: Incomplete Bug description: Raring. $ dpkg -l network-manager network-manager-openvpn ii network-manager 0.9.6.0+git2013010 i386 network management framework (daemon and userspace tools) ii network-manager-openvpn 0.9.6.0-0ubuntu2 i386 network management framework (OpenVPN plugin core) Use NM. Install network-manager-openvpn. Configure. Start VPN interface via applet or app. Syslog: Feb 18 05:48:44 localhost NetworkManager[1053]: info Starting VPN service 'openvpn'... Feb 18 05:48:44 localhost NetworkManager[1053]: warn VPN service 'openvpn': could not launch the VPN service. error: (8) Failed to execute child process /usr/lib/network-manager-openvpn/nm-openvpn-service (No such file or directory). Feb 18 05:48:44 localhost NetworkManager[1053]: warn connection /org/freedesktop/NetworkManager/Settings/48 failed to activate: (3) Failed to execute child process /usr/lib/network-manager-openvpn/nm-openvpn-service (No such file or directory) This continues until you restart network-manager altogether. $ dpkg -L network-manager-openvpn |grep lib /usr/lib /usr/lib/NetworkManager /usr/lib/NetworkManager/nm-openvpn-service /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1128985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1128705] Re: Mobile broadband many times slower and unstable on Ubuntu 12.04 than Win Vista -- Micromax MMX352G
Possibly helpful: http://askubuntu.com/questions/143394/configure- micromax-mmx-352g-usb-3g-modem-and-aircel-in-ubuntu-server-12-04-to-co ** Summary changed: - Mobile broadband many times slower and unstable on Ubuntu 12.04 than Win Vista + Mobile broadband many times slower and unstable on Ubuntu 12.04 than Win Vista -- Micromax MMX352G -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1128705 Title: Mobile broadband many times slower and unstable on Ubuntu 12.04 than Win Vista -- Micromax MMX352G Status in “network-manager” package in Ubuntu: Incomplete Bug description: Using Ubuntu 12.04.1 Lts, 32 bit, Intel core 2 duo processor I use USB modem for mobile broadband, model micromax MMX352G. I have both Ubuntu and Win Vista on two different partitions. I have noticed that my internet speed on Win vista is far more stable and higher than in Ubuntu. If anyone needs any more information or info from any configuration file please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1128705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1128705] Re: Mobile broadband many times slower and unstable on Ubuntu 12.04 than Win Vista -- Micromax MMX352G
This modem is not listed upstream as supported. https://live.gnome.org/NetworkManager/MobileBroadband Please file a report in the upstream bug tracker https://bugzilla.gnome.org/browse.cgi?product=NetworkManager asking for the modem to be supported. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1128705 Title: Mobile broadband many times slower and unstable on Ubuntu 12.04 than Win Vista -- Micromax MMX352G Status in “network-manager” package in Ubuntu: Incomplete Bug description: Using Ubuntu 12.04.1 Lts, 32 bit, Intel core 2 duo processor I use USB modem for mobile broadband, model micromax MMX352G. I have both Ubuntu and Win Vista on two different partitions. I have noticed that my internet speed on Win vista is far more stable and higher than in Ubuntu. If anyone needs any more information or info from any configuration file please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1128705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1125016] Re: Stacked menus unaccessible
** Package changed: network-manager (Ubuntu) = network-manager-applet (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1125016 Title: Stacked menus unaccessible Status in “network-manager-applet” package in Ubuntu: New Bug description: When opening the connection settings for a secured wifi and i did not chose a certificate, i am asked wether i want to accept it without certificate. In this case i cannot access the topmost popup. Neither with keyboard nor with touchpad. I cannot click the checkbox and i cannot click the button. This might be a bug with modal dialogs in gtk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1125016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1125929] Re: Network Manager routing problem
*** This bug is a duplicate of bug 47379 *** https://bugs.launchpad.net/bugs/47379 ** This bug has been marked a duplicate of bug 47379 NM assigns a lower metric to the default route over wlan than ifup assigns to the default route over eth. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1125929 Title: Network Manager routing problem Status in “network-manager” package in Ubuntu: New Bug description: Conditions: Workstation with alone network interface into local net with dhcp server. Dist.: kubuntu 12.04 amd64 Problem: Network manager sets incorrect metrics for local and default routes: default route has METRIC=0 local route has METRIC=1 As result, local addresses are looked for into Internet instead of local net. Removing of Network Manager with configuring of interface into /etc/network/interface decides the problem: local route has METRIC=0 default route has METRIC=100 Security issue: results are like as for arp spoofing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1125929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1126991] Re: 'connect' switch to nmcli does not work
What version of netwok-manager do you have? I cannot reproduce the problem with network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1. Does upgrading to this version fix it for you? ** Changed in: network-manager (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1126991 Title: 'connect' switch to nmcli does not work Status in “network-manager” package in Ubuntu: Incomplete Bug description: Expectation: nmcli dev wifi connect 'SSID' password 'password' This command should cause nmcli to connect to a wifi network. It works this way on every other Linux distribution. However, on Ubuntu nmcli returns: Error: 'dev wifi' command 'connect' is not valid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1126991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1123829] Re: NM fails to recognize already configured Wi-Fi connection
** Summary changed: - problem in wifi network configuration + NM fails to recognize already configured Wi-Fi connection -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1123829 Title: NM fails to recognize already configured Wi-Fi connection Status in “network-manager” package in Ubuntu: New Bug description: i am using wifi network at my office. we have multiple routers at different buildings given names like rd1, rd2 etc. they are password protetced for access and my laptop has a static ip. when i connect to any router it asks for password which is remembered. when i move around the router is selected automatically. the routers are from CISCO mainly with model no linksys E1500. the problem is if i am connected to rd1 and the move to rd2 router location, after some time it if i come back to rd1 location it detects rd1 as rd1 1 , asks password for router again. it coonects with automatic ipv4 setting which are not the configuration of my static settings. this causes non connectivity to network please help how do i solve this ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Wed Feb 13 12:34:10 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-03-24 (325 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120324) IpRoute: default via 192.168.87.254 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.87.0/24 dev wlan0 proto kernel scope link src 192.168.87.121 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-01-25 (19 days ago) ftp_proxy: ftp://192.168.90.94:8080/ http_proxy: http://192.168.90.94:8080/ nmcli-dev: DEVICE TYPE STATE DBUS-PATH 04:18:0F:3D:2E:00 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/5 A0:75:91:60:B4:B6 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/4 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.995 connected enabled enabled enabledenabled disabled no_proxy: localhost,127.0.0.0/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1123829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1123353] Re: problem in internet connection reliance netconnect
The Huawei EC1260 is not listed upstream as a supported model https://live.gnome.org/NetworkManager/MobileBroadband Nevertheless, I found a bug report in the upstream bugzilla related to this model. https://bugzilla.gnome.org/show_bug.cgi?id=663535 ** Bug watch added: GNOME Bug Tracker #663535 https://bugzilla.gnome.org/show_bug.cgi?id=663535 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1123353 Title: problem in internet connection reliance netconnect Status in “network-manager” package in Ubuntu: New Bug description: I am using huawei EC1260 intenet dongle on ubuntu 11.10. And unfortunately i am not able to connect to internet.. While connecting to the net the modem automaticall connects and disconnects itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1123353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
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 Practice Selection and Operation of Secondary DNS Servers Abstract The Domain Name System requires that multiple servers exist for every delegated domain (zone). This document discusses the selection of secondary servers for DNS zones. Both the physical and topological location of each server are material considerations when selecting secondary servers. The number of servers appropriate for a zone is also discussed, and some general secondary server maintenance issues considered. [...] With multiple servers, usually one server will be the primary server, and others will be secondary servers. Note that while some unusual configurations use multiple primary servers, that can result in data inconsistencies, and is not advisable. The distinction between primary and secondary servers is relevant only to the servers for the zone concerned, to the rest of the DNS there are simply multiple servers. All are treated equally at first instance, even by the parent server that delegates the zone. Resolvers often measure the performance of the various servers, choose the best, for some definition of best, and prefer that one for most queries. That is automatic, and not considered here. [...] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in “dnsmasq” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “dnsmasq” source package in Precise: Confirmed Status in “network-manager” source package in Precise: Triaged Status in “dnsmasq” package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and nameserver 127.0.0.1 to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
The target milestone should be adjusted, I guess. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in “dnsmasq” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “dnsmasq” source package in Precise: Confirmed Status in “network-manager” source package in Precise: Triaged Status in “dnsmasq” package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and nameserver 127.0.0.1 to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
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 to dnsmasq Because NM doesn't use dnsmasq to cache, if NM were to give dnsmasq only one address then I guess the only service that dnsmasq would still provide is that of name-to-server mapping. And it turns out that the way NM currently uses dnsmasq to do this is seriously flawed. So I conclude that it's better for NM not to use dnsmasq at all until these problems are solved. [That NM only supplies one nameserver address per domain name] is a different problem, and could be solved. From the man page it's not completely clear how to solve it. Can you confirm (1) that it's possible to give multiple server options as follows server=/google.com/1.2.3.4 server=/google.com/5.6.7.8 and that the result will be that 1.2.3.4 and 5.6.7.8 will be treated equally for the purpose of resolving names in domain google.com? (2) And likewise via D-Bus? (3) What effect does strict-order have on this? Ironically, I think the problem arises because for nameservers associated with particular domains, the equivalent of --strict-order is always in play. What you say here suggests that my proposition #1 above is false. If #1 is false then it seems that in order to fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in “dnsmasq” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “dnsmasq” source package in Precise: Confirmed Status in “network-manager” source package in Precise: Triaged Status in “dnsmasq” package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and nameserver 127.0.0.1 to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
[...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 resolves names in the domain .local. Networks should not use this TLD, but many do and at least in the past Microsoft actually recommended doing so. When users connect to such networks with avahi enabled the result is malfunction. Upstream purisitically says[*] If you come across a network where .local is a unicast DNS domain, please contact the local administrator and ask him to move his DNS zone to a different domain. If this is not possible, we recommend not to use Avahi in such a network at all. In practice avahi attempts to detect bad networks and disables itself if it thinks it is on a bad network, subject unfortunately both to false positives (bug #327362) and false negatives (bug #80900). We aren't yet doing even that well. We say that networks ought to have equivalent nameservers and we make no attempt to detect networks that have non-equivalent nameservers, of which there are very many. [*]http://avahi.org/wiki/AvahiAndUnicastDotLocal /parenthesis -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in “dnsmasq” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “dnsmasq” source package in Precise: Confirmed Status in “network-manager” source package in Precise: Triaged Status in “dnsmasq” package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and nameserver 127.0.0.1 to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
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 reply at all. This should be changed, but the code which implements it is knarly and old, and won't stand more tinkering, it needs rewriting. I've not found the time, as of yet. That doesn't sound as if it's urgently needed for anything we are talking about here. What we do need is for strict-order to work when addresses are provided over D-Bus. (That this requires work: see #49. That this is needed: see below.) We say that networks ought to have equivalent nameservers and we make no attempt to detect networks that have non-equivalent nameservers, of which there are very many. Detect non-equivalent servers is hard. I'm very much in favour of doing it, if a way can be found. Well, let's look at the ideas that have been put forward so far. Solution #1. Disable NM-dnsmasq by default. This is the only solution we have right now. Other ideas that probably need more thought... Solution #2. Enhance dnsmasq such that it can be given an ordered list of nameservers via D-Bus and can process this list in strict-order fashion. Then do every lookup in strict-order fashion, but detect offline nameservers and omit them temporarily from the list. (This is my interpretation of Stéphane's suggestion in #37.) Solution #3. Enhance dnsmasq such that it can be given an ordered list of nameservers via D-Bus and can process this list in strict-order fashion. Then do a given lookup in strict-order fashion if * the lookup is being routed to a specific nameserver due to a server option; * the name is in one of the search domains returned by DHCP (as suggested my M T-L in #34); * the name is not in any of the recognized TLDs; or * we have detected nameserver nonequivalence since the last time the list of nameservers changed. The detection mechanism is as described in #28: on encountering NODATA or NXDOMAIN, dnsmasq returns the negative result immediately but also reiterates the query to all nameservers listed earlier than the one that answered. If one of those nameservers later returns an address then nameserver nonequivalence has been detected. (This combines several earlier suggestions.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in “dnsmasq” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “dnsmasq” source package in Precise: Confirmed Status in “network-manager” source package in Precise: Triaged Status in “dnsmasq” package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and nameserver 127.0.0.1 to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1115061] Re: [quantal] modem-manager doesn't handle usb modem
What is the exact model number of your device? Googling for your USB device IDs I found, e.g., this: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=155. ** Changed in: network-manager (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1115061 Title: [quantal] modem-manager doesn't handle usb modem Status in “network-manager” package in Ubuntu: Incomplete Bug description: Open WifiSyslog.txt to see error log. When I killed modem-manager process (kill -9 at 10:12:27) and it started to recognize the GSM modem at 10:13:08. According to http://forums.gentoo.org/viewtopic-t-941134-start-0.html it seams to be related with a compilation flag introduced in network-manager 0.9.6. People seams to encounter the same trouble on http://ubuntuforums.org/showthread.php?t=2102852. Bug #1071408 may also be related. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 Uname: Linux 3.4.17-030417-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Mon Feb 4 10:23:00 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-11 (84 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH ttyUSB2gsm connected /org/freedesktop/NetworkManager/Devices/2 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1115061/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1114600] Re: wifi network named as number not found
** Description changed: - After Upgrading from 11.04 to 12.10 the wifi Network named 300 isn't - available anymore in networkmanager. + After upgrading from 11.04 to 12.10 the Wi-Fi network named 300 isn't + available any more in NetworkManager. ** Summary changed: - wifi network named as number not found + Wi-Fi network with numerical name not available -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1114600 Title: Wi-Fi network with numerical name not available Status in “network-manager” package in Ubuntu: New Bug description: After upgrading from 11.04 to 12.10 the Wi-Fi network named 300 isn't available any more in NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1114600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1114107] Re: Please backport ability to customize NM-dnsmasq to 12.04
** Summary changed: - No way to customize built-in dnsmasq configuration in 12.04 + Please backport ability to customize NM-dnsmasq to 12.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1114107 Title: Please backport ability to customize NM-dnsmasq to 12.04 Status in “network-manager” package in Ubuntu: New Bug description: The integration of Dnsmasq into NetworkManager is, overall, very convenient: it makes dealing with _some_ VPN connections on Ubuntu much easier. However, there are still a number of VPN connections that NetworkManager doesn't support, or doesn't support fully (e.g. a number of OpenVPN configuration options). In these cases, it's necessary to configure the VPN connections the old-fashioned way: on the command line. There's also the issue that nm-applet doesn't gracefully support multiple simultaneous VPN connections (though the Network control panel now apparently does). Unfortunately, there really isn't a way to gracefully handle the DNS changes that these manual VPN connections require in 12.04's version of Dnsmasq. It seems that 12.10's version offers /etc/NetworkManager/dnsmasq.d/, and also a D-Bus interface-- either of which would likely work. Neither of these options (or any others I'm aware of) exist for 12.04. Right now, I find myself in the somewhat bizarre situation of considering a switch off of the LTS 12.04 release to 12.10 just to get support for a couple of VPN connections. Is there any chance that the dnsmasq.d and/or D-Bus support could be backported to 12.04? Apologies if this is the wrong forum for such a request-- couldn't think of a better one. FYI: Such a backport was actually first suggested by one of the NetworkManager devs on dnsmasq-discuss [1]. [1] http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2012q4/006370.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1114107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1113703] Re: Trying to connect using a GSM modem without SIM card is not reported to user
** Changed in: gnome-shell (Ubuntu)
Status: New = Invalid
** Description changed:
- Trying to connect using a GSM modem that lacks a SIM card does just give
- the user a general connection failure message without any hints about
- the missing SIM card.
-
- This can fool the user into thinking something other is wrong than the
- fact that he forgot to insert the SIM card, or inserted it improperly.
+ When the user tries to connect using a GSM modem that lacks a SIM card,
+ NM just gives the user a general connection failure message; it does not
+ give any hint about the missing SIM card. This can fool the user into
+ thinking something other is wrong than the fact that he forgot to insert
+ the SIM card, or inserted it improperly.
Latest modemmanager master branch gives in log:
Feb 2 20:21:24 marius-T1005 ModemManager[1105]: warn Modem couldn't
be initialized: Couldn't check unlock status: SIM failure
but there is no indication to the user (nm-applet behaves as if mobile
broadband is unavailable).
Seems I get (from src/mm-error-helpers.c):
{ MM_MOBILE_EQUIPMENT_ERROR_SIM_FAILURE,
simfailure,SIM failure },
but should have got:
{ MM_MOBILE_EQUIPMENT_ERROR_SIM_NOT_INSERTED,
simnotinserted,SIM not inserted }
Anyway (any of them should be enough hint to the user), it seems like
the error state is not propagated (src/mm-broadband-modem.c):
static void
iface_modem_initialize_ready (MMBroadbandModem *self,
GAsyncResult *result,
InitializeContext *ctx)
{
GError *error = NULL;
/* If the modem interface fails to get initialized, we will move the modem
* to a FAILED state. Note that in this case we still export the
interface. */
if (!mm_iface_modem_initialize_finish (MM_IFACE_MODEM (self), result,
error)) {
/* Report the new FAILED state */
mm_warn (Modem couldn't be initialized: %s, error-message);
g_error_free (error);
mm_iface_modem_update_state (MM_IFACE_MODEM (self),
MM_MODEM_STATE_FAILED,
MM_MODEM_STATE_CHANGE_REASON_UNKNOWN);
/* Jump to the firmware step. We allow firmware switching even in
failed
* state */
ctx-step = INITIALIZE_STEP_IFACE_FIRMWARE;
initialize_step (ctx);
return;
}
Network Manager logs:
20:21:24 marius-T1005 NetworkManager[1128]: warn (ttyUSB2): unusable
modem detected
** Changed in: networkmanagement (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1113703
Title:
Trying to connect using a GSM modem without SIM card is not reported
to user
Status in ModemManager (with NetworkManager support):
New
Status in NetworkManager:
Confirmed
Status in “gnome-shell” package in Ubuntu:
Invalid
Status in “modemmanager” package in Ubuntu:
New
Status in “network-manager” package in Ubuntu:
New
Status in “network-manager-applet” package in Ubuntu:
New
Status in “networkmanagement” package in Ubuntu:
Invalid
Bug description:
When the user tries to connect using a GSM modem that lacks a SIM
card, NM just gives the user a general connection failure message; it
does not give any hint about the missing SIM card. This can fool the
user into thinking something other is wrong than the fact that he
forgot to insert the SIM card, or inserted it improperly.
Latest modemmanager master branch gives in log:
Feb 2 20:21:24 marius-T1005 ModemManager[1105]: warn Modem
couldn't be initialized: Couldn't check unlock status: SIM failure
but there is no indication to the user (nm-applet behaves as if mobile
broadband is unavailable).
Seems I get (from src/mm-error-helpers.c):
{ MM_MOBILE_EQUIPMENT_ERROR_SIM_FAILURE,
simfailure,SIM failure },
but should have got:
{ MM_MOBILE_EQUIPMENT_ERROR_SIM_NOT_INSERTED,
simnotinserted,SIM not inserted }
Anyway (any of them should be enough hint to the user), it seems like
the error state is not propagated (src/mm-broadband-modem.c):
static void
iface_modem_initialize_ready (MMBroadbandModem *self,
GAsyncResult *result,
InitializeContext *ctx)
{
GError *error = NULL;
/* If the modem interface fails to get initialized, we will move the modem
* to a FAILED state. Note that in this case we still export the
interface. */
if (!mm_iface_modem_initialize_finish (MM_IFACE_MODEM (self), result,
error)) {
/* Report the new FAILED state */
mm_warn (Modem couldn't be initialized: %s,
[Desktop-packages] [Bug 1102317] Re: Unable to disable networking/wireless through network indicator
Could bug #1102092 be related? ** Package changed: network-manager (Ubuntu) = network-manager-applet (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1102317 Title: Unable to disable networking/wireless through network indicator Status in “network-manager-applet” package in Ubuntu: New Bug description: If I click the Enable Networking or Enable Wireless menu items, nothing happens. The computer stays connected to any networks and the menu items still have check marks. Related to bug #824998 and bug #1059529 - this gives me unavoidable popup dialog spam. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Jan 21 11:01:53 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-10 (71 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IpRoute: default via 10.42.0.1 dev eth0 proto static 10.42.0.0/24 dev eth0 proto kernel scope link src 10.42.0.15 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1102317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1101534] Re: Cannot connect to WiFi network
From WifiSyslog.txt (eth1 is the Wi-Fi interface): Jan 31 19:50:37 samsung wpa_supplicant[1307]: eth1: Trying to associate with 2e:c7:9f:d6:30:40 (SSID='[...]' freq=2412 MHz) Jan 31 19:50:37 samsung wpa_supplicant[1307]: eth1: Association request to the driver failed Jan 31 19:50:37 samsung NetworkManager[1159]: info (eth1): supplicant interface state: scanning - associating Jan 31 19:50:42 samsung wpa_supplicant[1307]: eth1: Authentication with 2e:c7:9f:d6:30:40 timed out. Jan 31 19:50:42 samsung NetworkManager[1159]: info (eth1): supplicant interface state: associating - disconnected ** Summary changed: - Cannot connect to WiFi network + Cannot connect to WiFi network -- Broadcom BCM4313 wl -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1101534 Title: Cannot connect to WiFi network -- Broadcom BCM4313 wl Status in “linux” package in Ubuntu: New Bug description: Since ubuntu 12.10, my wifi is correctly detected and network-manager try to connect to it, but it seems unable to connect : it asks again and again the wifi password. If I try to connect to an open wifi network, it just fails after some time. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw' Date: Fri Jan 18 23:35:33 2013 InstallationDate: Installed on 2012-07-05 (196 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 192.168.100.254 dev eth0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.4 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-10-31 (79 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Bull 028f785a-2c07-4a97-8103-94b75c42a91a vpn 1344399678 mer. 08 août 2012 06:21:18 CESTyes no /org/freedesktop/NetworkManager/Settings/2 eth0 6c727f94-1091-4bf8-bd39-61152ca9788b 802-3-ethernet1358548545 ven. 18 janv. 2013 23:35:45 CETyes no /org/freedesktop/NetworkManager/Settings/1 Laurent_Vivierb774eb6c-736b-46d1-a7a7-83e39181a79b 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/0 Vodafone Internet Facile fe010041-967a-4240-b9c2-c9af9365cd25 gsm 1356510304 mer. 26 déc. 2012 09:25:04 CET nono /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 eth1 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled disabled enabled disabled --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type DistroRelease: Ubuntu 12.10 InstallationDate: Installed on 2012-07-05 (209 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 192.168.100.254 dev eth0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.4 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: wl Package: network-manager 0.9.6.0-0ubuntu7 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Tags: quantal
[Desktop-packages] [Bug 1101534] Re: Cannot connect to WiFi network -- Broadcom BCM4313 wl
Possible wl driver problem ** Package changed: network-manager (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1101534 Title: Cannot connect to WiFi network -- Broadcom BCM4313 wl Status in “linux” package in Ubuntu: New Bug description: Since ubuntu 12.10, my wifi is correctly detected and network-manager try to connect to it, but it seems unable to connect : it asks again and again the wifi password. If I try to connect to an open wifi network, it just fails after some time. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw' Date: Fri Jan 18 23:35:33 2013 InstallationDate: Installed on 2012-07-05 (196 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 192.168.100.254 dev eth0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.4 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-10-31 (79 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Bull 028f785a-2c07-4a97-8103-94b75c42a91a vpn 1344399678 mer. 08 août 2012 06:21:18 CESTyes no /org/freedesktop/NetworkManager/Settings/2 eth0 6c727f94-1091-4bf8-bd39-61152ca9788b 802-3-ethernet1358548545 ven. 18 janv. 2013 23:35:45 CETyes no /org/freedesktop/NetworkManager/Settings/1 Laurent_Vivierb774eb6c-736b-46d1-a7a7-83e39181a79b 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/0 Vodafone Internet Facile fe010041-967a-4240-b9c2-c9af9365cd25 gsm 1356510304 mer. 26 déc. 2012 09:25:04 CET nono /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 eth1 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled disabled enabled disabled --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type DistroRelease: Ubuntu 12.10 InstallationDate: Installed on 2012-07-05 (209 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 192.168.100.254 dev eth0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.4 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: wl Package: network-manager 0.9.6.0-0ubuntu7 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Tags: quantal running-unity Uname: Linux 3.5.0-22-generic x86_64 UpgradeStatus: Upgraded to quantal on 2012-10-31 (92 days ago) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare sudo mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-01-31T19:45:23.150893 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 eth1 802-11-wireless connecting (configuring) /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE
[Desktop-packages] [Bug 1093622] Re: NM doesn't react to disconnect and connect commands for WiFi networks for very long time (or ever) -- Ralink rt2800usb
Am I correct in understanding that the Wi-Fi device in question is a Ralink and the driver is rt2800usb? ** Summary changed: - NM doesn't react to disconnect and connect commands for WiFi networks for very long time (or ever) + NM doesn't react to disconnect and connect commands for WiFi networks for very long time (or ever) -- Ralink rt2800usb ** Changed in: network-manager (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1093622 Title: NM doesn't react to disconnect and connect commands for WiFi networks for very long time (or ever) -- Ralink rt2800usb Status in Enablement project for the Toshiba AC100 NetBook: New Status in “network-manager” package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 12.04 on Toshiba AC100 (ARM). network-manager 0.9.4.0-0ubuntu4.1 network-manager-gnome0.9.4.1-0ubuntu2 It often happens that whenever I want to connect to another WiFi network through the menu of the applet, there is no reaction for very long time (10 mins, or for ever). I tried to select Disconnect: no reaction. I tried to select the new network many times: no reaction. Workaround (as root): service network-manager restart --- ApportVersion: 2.0.1-0ubuntu13 Architecture: armhf DistroRelease: Ubuntu 12.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.9 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 0.9.4.0-0ubuntu4.2 PackageArchitecture: armhf PciNetwork: Tags: precise running-unity Uname: Linux 3.0.27-1-ac100 armv7l UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/9 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled enabled --- ApportVersion: 2.0.1-0ubuntu13 Architecture: armhf DistroRelease: Ubuntu 12.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.142 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 0.9.4.0-0ubuntu4.2 PackageArchitecture: armhf PciNetwork: Tags: precise Uname: Linux 3.0.27-1-ac100 armv7l UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ac100/+bug/1093622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1099696] Re: Can't reconnect 3G HSPA after disconnect ; log out and in fixes it
What is the exact model name of your dongle. Please reboot, reproduce the failure, connect and then run apport- collect 1099696 in a terminal to provide more information. ** Changed in: network-manager (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1099696 Title: Can't reconnect 3G HSPA after disconnect ; log out and in fixes it Status in “network-manager” package in Ubuntu: Incomplete Bug description: I try to connect with connection named Hutch which is associated with a 3G dongle and HSPA service. The first time it connects, but if it is disconnected and I try to reconnect it does not work. nmcli con up id Hutch ** (process:21044): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/19: Method Get with signature ss on interface org.freedesktop.DBus.Properties doesn't exist ** (process:21044): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/19: Method Get with signature ss on interface org.freedesktop.DBus.Properties doesn't exist to make this work I need to unplug and plug dongle again or logout and login again.This wos working on 12.04 and I doubt after update it to 12.04.1 this occured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1099696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1114600] Re: Wi-Fi network with numerical name not available
Please reboot and then run apport-collect 1114600 to provide more information about the affected system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1114600 Title: Wi-Fi network with numerical name not available Status in “network-manager” package in Ubuntu: New Bug description: After upgrading from 11.04 to 12.10 the Wi-Fi network named 300 isn't available any more in NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1114600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1103809] Re: nm-applet stops accepting keyboard input
** Changed in: network-manager-applet (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1103809 Title: nm-applet stops accepting keyboard input Status in “network-manager-applet” package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. right-click on the network manager icon in system tray, and choose 'edit connections' 2. Select a connection in the dialog which opens, and click 'edit...' 3. in the 'connection name' textbox, type something (to confirm that your keyboard works) 4. click on the 'ipv4 settings' tab 5. select 'manual' in the 'method' dropdown 6. click 'add' to add an address 7. try to type in an IP address (or anything!) in the 'Address' field of the new row you just created 8. to confirm that it's not just the one control but all keyboard input, try changing the name of the connection again (you can't) Required information: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu Description: Ubuntu 12.04.1 LTS Release: 12.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center network-manager: Installed: 0.9.4.0-0ubuntu4.2 Candidate: 0.9.4.0-0ubuntu4.2 Version table: *** 0.9.4.0-0ubuntu4.2 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.9.4.0-0ubuntu3 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ precise/main amd64 Packages 3) What you expected to happen whatever I type should appear in the currently focused text box 4) What happened instead nothing ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Jan 24 15:01:39 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.100.2 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 172.16.81.0/24 dev vmnet1 proto kernel scope link src 172.16.81.1 172.16.244.0/24 dev vmnet8 proto kernel scope link src 172.16.244.1 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.115 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-01-17T15:01:22.853009 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH LAN deb828ff-f2b5-4563-b238-c152e65217c8 802-3-ethernet135988 Thu 24 Jan 2013 15:01:28 EST yes no /org/freedesktop/NetworkManager/Settings/1 Freerunner (USB) 42ca67f0-41f6-4a1b-b299-db236a3b5ed2 802-3-ethernet1358404607 Thu 17 Jan 2013 17:36:47 EST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1103809/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1099633] Re: network manager static ip gui bug
I can reproduce this. ** Changed in: network-manager-applet (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1099633 Title: network manager static ip gui bug Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: While trying to enter static ipv4 information in network-manager- gnome, if numlock is disabled and you press the 8 key on the numpad with focus in the ip field, the netmask field will glitch. This makes it hard to edit, (sometimes it is even impossible to click apply) making this a usibility issue. It becomes even worse if 8 is pressed twice with num lock off. The only way to make it go away is to close the window and edit again, now with num lock on. This bug was found while trying to type an ip that starts with 88 with num lock accidentally disabled. Also there seems to be a graphical miss-alignment when tabbing from ip to netmask (only happens if all rows have been deleted and window has been closed and reopened and a new address line has been added), however this is minor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1099633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
This may also help: http://www.thinkwiki.org/wiki/Installing_Ubuntu_11.04_(Natty_Narwhal)_on_a_ThinkPad_X220#Fix_for_hotkey_shortcomings -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Triaged Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “udev” source package in Raring: Triaged Status in “xserver-xorg-input-evdev” source package in Raring: Triaged Bug description: Ubuntu 9.04 Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 0080 101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/408903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
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 strict-order back on is no solution. And solutions depending on strict-order including mine in #28 also won't work. Unless dnsmasq is somehow changed such that it remembers the order in which nameserver addresses come in over D-Bus so that strict-order is useful in the D-Bus case, if we want to avoid breaking name service on machines connected to NNNs then we have to disable dnsmasq by default; or disable it initially and only enable it when we know that we aren't on a NNN. (NNN = nonequivalent-nameserver network. As discussed in comment #5, such networks are not properly configured. But as observed several times, there are many NNNs out there. Which is why *many* people have been commenting out dns=dnsmasq.) There is another problem with NM-dnsmasq (bug #1072899). Some VPNs have multiple nameservers. NM uses dnsmasq to direct VPN domain name queries to the *first* one. But then, if the first one goes down, the second one is not tried. Once again, for the sake of speed enhancement in the favorable case, users suffer radical name service failure in the unfavorable case. This is not a good deal, IMHO. NM-dnsmasq should be disabled by default until these problems are solved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in “dnsmasq” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “dnsmasq” source package in Precise: Confirmed Status in “network-manager” source package in Precise: Triaged Status in “dnsmasq” package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and nameserver 127.0.0.1 to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1114570] Re: DNS suddenly stops working despite adding 8.8.8.8 as an additional server
Try this. Edit the connection using the Connection Editor and set IPv4 Settings | Method to Automatic (DHCP) addresses only instead of Automatic (DHCP). Make sure 8.8.8.8 is still included in the Additional DNS servers field. Another thing to try is to disable the local forwarding nameserver. Edit /etc/NetworkManager/NetworkManager.conf, comment out dns=dnsmasq by putting a '#' at the beginning of the line, and restart network-manager. You'll need sudo to accomplish this. ** Description changed: I see this problem somewhere between once a week and once a day: DNS lookups suddenly stop working causing the browser to fail to load pages and time out. After the last time it happened, I figured must be comcast's flaky DNS so I added Google's DNS server 8.8.8.8 as an additional server via network-manager but it just happened again. Even while it was broken, I could still ping 8.8.8.8 so I'm not really sure what's going on. I had a look in resolv.conf but it seems to be the same whether it's - working or not. Wither way it only has 127.0.1.1 as the nameserver. I - was expecting to see the actual nameserver in there but I guess Ubuntu - is using some sort of local proxy DNS? Since I'm not sure how DNS works - anymore, I'm not sure if this is the right package to report against. - Please advise. + working or not. Either way it only has 127.0.1.1 as the nameserver + address. I was expecting to see the actual nameserver in there but I + guess Ubuntu is using some sort of local proxy DNS? Since I'm not sure + how DNS works anymore, I'm not sure if this is the right package to + report against. Please advise. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sun Feb 3 12:02:14 2013 IfupdownConfig: - auto lo - iface lo inet loopback + auto lo + iface lo inet loopback InstallationDate: Installed on 2012-09-26 (130 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2) IpRoute: - default via 192.168.0.1 dev wlan0 proto static - 169.254.0.0/16 dev wlan0 scope link metric 1000 - 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.102 metric 9 + default via 192.168.0.1 dev wlan0 proto static + 169.254.0.0/16 dev wlan0 scope link metric 1000 + 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.102 metric 9 MarkForUpload: True NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: - NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH - Wired connection 1db3b0216-bf13-4ec6-a5a8-20ffef4c1b22 802-3-ethernet1359824609 Sat 02 Feb 2013 09:03:29 AM PSTyes no /org/freedesktop/NetworkManager/Settings/1 - PinotGrigio 72706fea-5902-4f1f-ad56-891711e12ae9 802-11-wireless 1359921642 Sun 03 Feb 2013 12:00:42 PM PSTyes no /org/freedesktop/NetworkManager/Settings/0 + NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH + Wired connection 1db3b0216-bf13-4ec6-a5a8-20ffef4c1b22 802-3-ethernet1359824609 Sat 02 Feb 2013 09:03:29 AM PSTyes no /org/freedesktop/NetworkManager/Settings/1 + PinotGrigio 72706fea-5902-4f1f-ad56-891711e12ae9 802-11-wireless 1359921642 Sun 03 Feb 2013 12:00:42 PM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: - DEVICE TYPE STATE DBUS-PATH - wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 - eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 + DEVICE TYPE STATE DBUS-PATH + wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 + eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: - RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN - running 0.9.6.0
[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
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 /etc/NetworkManager/dnsmasq.d/; stop network-manager; make sure all dnsmasq processes are dead; start network-manager.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in “dnsmasq” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “dnsmasq” source package in Precise: Confirmed Status in “network-manager” source package in Precise: Triaged Status in “dnsmasq” package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and nameserver 127.0.0.1 to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1101534] Re: Cannot connect to WiFi network
I notice a possibly unrelated problem in your syslog. NM can't communicate with its slave dnsmasq. To work around this, comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf and then sudo restart network-manager. Jan 18 23:12:50 samsung NetworkManager[987]: info DNS: starting dnsmasq... Jan 18 23:12:50 samsung NetworkManager[987]: error [1358547170.410316] [nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update servers. Jan 18 23:12:50 samsung NetworkManager[987]: error [1358547170.410374] [nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Jan 18 23:12:50 samsung NetworkManager[987]: warn DNS: plugin dnsmasq update failed Jan 18 23:12:50 samsung NetworkManager[987]: info ((null)): writing resolv.conf to /sbin/resolvconf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1101534 Title: Cannot connect to WiFi network Status in “network-manager” package in Ubuntu: New Bug description: Since ubuntu 12.10, my wifi is correctly detected and network-manager try to connect to it, but it seems unable to connect : it asks again and again the wifi password. If I try to connect to an open wifi network, it just fails after some time. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw' Date: Fri Jan 18 23:35:33 2013 InstallationDate: Installed on 2012-07-05 (196 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 192.168.100.254 dev eth0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.4 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-10-31 (79 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Bull 028f785a-2c07-4a97-8103-94b75c42a91a vpn 1344399678 mer. 08 août 2012 06:21:18 CESTyes no /org/freedesktop/NetworkManager/Settings/2 eth0 6c727f94-1091-4bf8-bd39-61152ca9788b 802-3-ethernet1358548545 ven. 18 janv. 2013 23:35:45 CETyes no /org/freedesktop/NetworkManager/Settings/1 Laurent_Vivierb774eb6c-736b-46d1-a7a7-83e39181a79b 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/0 Vodafone Internet Facile fe010041-967a-4240-b9c2-c9af9365cd25 gsm 1356510304 mer. 26 déc. 2012 09:25:04 CET nono /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 eth1 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled disabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1101534/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1101534] Re: Cannot connect to WiFi network
Please shut down; disconnect Ethernet cable; boot; enable Wi-Fi; attempt to connect to Wi-Fi network (and presumably fail); plug in Ethernet cable. Then run apport-collect 1101534 to submit more information including a useful syslog. ** Package changed: network-manager-applet (Ubuntu) = network-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1101534 Title: Cannot connect to WiFi network Status in “network-manager” package in Ubuntu: New Bug description: Since ubuntu 12.10, my wifi is correctly detected and network-manager try to connect to it, but it seems unable to connect : it asks again and again the wifi password. If I try to connect to an open wifi network, it just fails after some time. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw' Date: Fri Jan 18 23:35:33 2013 InstallationDate: Installed on 2012-07-05 (196 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 192.168.100.254 dev eth0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.4 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-10-31 (79 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Bull 028f785a-2c07-4a97-8103-94b75c42a91a vpn 1344399678 mer. 08 août 2012 06:21:18 CESTyes no /org/freedesktop/NetworkManager/Settings/2 eth0 6c727f94-1091-4bf8-bd39-61152ca9788b 802-3-ethernet1358548545 ven. 18 janv. 2013 23:35:45 CETyes no /org/freedesktop/NetworkManager/Settings/1 Laurent_Vivierb774eb6c-736b-46d1-a7a7-83e39181a79b 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/0 Vodafone Internet Facile fe010041-967a-4240-b9c2-c9af9365cd25 gsm 1356510304 mer. 26 déc. 2012 09:25:04 CET nono /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 eth1 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled disabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1101534/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1107975] Re: VPNC not working
@Rob Gar EsP: Do you see the same symptoms as in bug #1104173? ** Package changed: network-manager (Ubuntu) = network-manager-vpnc (Ubuntu) ** Summary changed: - VPNC not working + NM-VPNC stopped working; Cisco client still works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1107975 Title: NM-VPNC stopped working; Cisco client still works Status in “network-manager-vpnc” package in Ubuntu: New Bug description: Hi, I'm using Ubuntu 12.04. One VPN configured in network manager VPNC used to work until some days ago. The same VPN is still working using CIsco's Windows VPN client. This is the gnome network manager error I see in /var/log: NetworkManager[899]: info Starting VPN service 'vpnc'... NetworkManager[899]: info VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 4760 NetworkManager[899]: info VPN service 'vpnc' appeared; activating connections NetworkManager[899]: info VPN plugin state changed: init (1) NetworkManager[899]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/tun0, iface: tun0) NetworkManager[899]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found. NetworkManager[899]: info VPN plugin state changed: starting (3) NetworkManager[899]: info VPN connection 'Synchronica' (Connect) reply received. NetworkManager[899]:SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/tun0, iface: tun0) NetworkManager[899]: warn VPN plugin failed: 1 NetworkManager[899]: info VPN plugin state changed: stopped (6) NetworkManager[899]: info VPN plugin state change reason: 0 NetworkManager[899]: warn error disconnecting VPN: Could not process the request because no VPN connection was active. NetworkManager[899]: info Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS. Jan 21 10:48:22 Myriad-HP-EliteBook-8460p NetworkManager[899]: info VPN service 'vpnc' disappeared I have tried some tricks like --enable-1des, I have also tried IP addresses instead DNS for the GW definition, and some more recommendations posted in other forums, nothing seems to work. I think this is actually a bug. Please assist. ///RGB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/1107975/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 112789] Re: network manager should have weighting
*** This bug is a duplicate of bug 366780 *** https://bugs.launchpad.net/bugs/366780 ** This bug is no longer a duplicate of bug 46123 Define priorities for different networks ** This bug has been marked a duplicate of bug 366780 Please provide a mechanism whereby Wi-Fi networks can be prioritized -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/112789 Title: network manager should have weighting Status in “network-manager” package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager When in an environment where multiple networks are visible it would be useful to be able to set an order of precedence. This could enable the user to coerce/bias network manager towards one network. This could be achieved with a gconf key with a weight from 1 to 5. In the user interface for network-manager this can be implemented with stars in a similar way to iTunes/Rhythmbox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/112789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 92872] Re: network-manager should be able to have priority networks
*** This bug is a duplicate of bug 366780 *** https://bugs.launchpad.net/bugs/366780 ** This bug is no longer a duplicate of bug 46123 Define priorities for different networks ** This bug has been marked a duplicate of bug 366780 Please provide a mechanism whereby Wi-Fi networks can be prioritized -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/92872 Title: network-manager should be able to have priority networks Status in “network-manager” package in Ubuntu: Incomplete Bug description: Binary package hint: network-manager Hello, this is a enhancement wish which would gretly help to increase the usability. I have a cable network which I want to use as default network when being at my working desk. There are also a number of WLAN-nets around of which one I have access and which has been secured by a keyphrase. Whenever I log into Ubuntu there's a small window asking me for my master WLAN password. If I don't type that one in I won't get any connection (IMAP/browser sessions, etc.) thus it isn't neccessary since I have always a cable plugged in. Would it be feasible to have the cable network as a default? Then it would recognize to use the cable LAN as preferred network when I have that plugged. Thanks for addressing this. using Ubuntu Edgy Eft (2.6.17-11-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/92872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 102555] Re: network-manager-gnome needs a default network checkbox
*** This bug is a duplicate of bug 366780 *** https://bugs.launchpad.net/bugs/366780 ** This bug is no longer a duplicate of bug 46123 Define priorities for different networks ** This bug has been marked a duplicate of bug 366780 Please provide a mechanism whereby Wi-Fi networks can be prioritized -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/102555 Title: network-manager-gnome needs a default network checkbox Status in “network-manager” package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager-gnome Feature Request The network-manager automatically connects to open wireless networks before any WEP/WPA protected wireless networks. Network-manager-gnome needs a checkbox on the interface so a default network can be selected and network-manager will always connect to your chosen wireless network every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/102555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 46123] Re: Define priorities for different networks
*** This bug is a duplicate of bug 366780 *** https://bugs.launchpad.net/bugs/366780 ** Changed in: network-manager (Ubuntu) Status: Invalid = New ** This bug has been marked a duplicate of bug 366780 Please provide a mechanism whereby Wi-Fi networks can be prioritized -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/46123 Title: Define priorities for different networks Status in NetworkManager: Invalid Status in “network-manager” package in Ubuntu: New Bug description: Hello, it would be great if there is a way to define an order for the networks to log in. I have several networks in my neighbourhood with different essids and sometimes network-manager is not connecting to my network. So setting a priority which networks to try first would be great. Thanks Christoph To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/46123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 74678] Re: allow prioritizing of whitelisted networks
*** This bug is a duplicate of bug 366780 *** https://bugs.launchpad.net/bugs/366780 ** This bug is no longer a duplicate of bug 46123 Define priorities for different networks ** This bug has been marked a duplicate of bug 366780 Please provide a mechanism whereby Wi-Fi networks can be prioritized -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/74678 Title: allow prioritizing of whitelisted networks Status in “network-manager” package in Ubuntu: New Bug description: it would be great to have the option of asigning priorities to networks to which one has connected in the past -- I work in any area with several overlapping networks, of which I use one in particular unless it's down. prioritizing that network over the other ones would ensure that it always gets chosen over them. obviously this is a wishlist item. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/74678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 366780] Re: Please provide a mechanism whereby Wi-Fi networks can be prioritized
Quote from upstream report (https://bugzilla.gnome.org/show_bug.cgi?id=359556): There won't ever be user-defined priorities in NM. NM connects to the last network you've connected to that it can find. When you connect, NM timestamps the network, and it will first connect to the most recent network you have chosen. NM 0.7 also matches security settings, so if you have a WPA-enabled 'linksys' and an open 'linksys' saved it will pick the right one. 0.7 also has a connection editor that will allow for easy removal of networks, but with 0.6.5 you can also use gconftool-2 --recursive-unset /path/to/your/network to remove it. If you dont' want NM connecting to a network, remove it from the network list and dont' manually connect to it again. ** Bug watch added: GNOME Bug Tracker #359556 https://bugzilla.gnome.org/show_bug.cgi?id=359556 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/366780 Title: Please provide a mechanism whereby Wi-Fi networks can be prioritized Status in “network-manager” package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager I've got few wifi network profiles. NM connects to 1st available network in alphabetical order. But at my home NM connects to slow and unstable free network and I want to connect to my own wifi router. I suggest to add some priorities to different networks to set the order which network to connect to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/366780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 31286] Re: Displays repeated keyring dialogs on resume from suspend and login
** Bug watch added: GNOME Bug Tracker #665503 https://bugzilla.gnome.org/show_bug.cgi?id=665503 ** Changed in: network-manager Importance: Medium = Unknown ** Changed in: network-manager Status: Invalid = Unknown ** Changed in: network-manager Remote watch: GNOME Bug Tracker #676278 = GNOME Bug Tracker #665503 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/31286 Title: Displays repeated keyring dialogs on resume from suspend and login Status in NetworkManager: Unknown Status in “network-manager” package in Ubuntu: Fix Released Bug description: scenario: Dapper FL3 + updates Network-manager + applet .5.1 Suspend - resume working properly Booted with wired network connected. Wireless network not activated during this session. Pressed the Shutdown toolbar icon and selected Suspend. Saw that the Gnome keyring dialog popped up just before the system went to sleep. On resume, there were at least 5 pending Gnome keyring dialogs. After having typed my password in each of these, the system went momentarily to sleep and woke up within a couple of seconds by itself (5 sec?). After the last password-suspend-resume cycle, the system is working perfectly. Anders To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/31286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 31286] Re: Displays repeated keyring dialogs on resume from suspend and login
Update. The bug has been fixed, but not in Precise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/31286 Title: Displays repeated keyring dialogs on resume from suspend and login Status in NetworkManager: Confirmed Status in “network-manager” package in Ubuntu: Fix Released Bug description: scenario: Dapper FL3 + updates Network-manager + applet .5.1 Suspend - resume working properly Booted with wired network connected. Wireless network not activated during this session. Pressed the Shutdown toolbar icon and selected Suspend. Saw that the Gnome keyring dialog popped up just before the system went to sleep. On resume, there were at least 5 pending Gnome keyring dialogs. After having typed my password in each of these, the system went momentarily to sleep and woke up within a couple of seconds by itself (5 sec?). After the last password-suspend-resume cycle, the system is working perfectly. Anders To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/31286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1067555] Re: nm-applet keyring dialog flood
*** This bug is a duplicate of bug 31286 *** https://bugs.launchpad.net/bugs/31286 Reported fixed in quantal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1067555 Title: nm-applet keyring dialog flood Status in “network-manager” package in Ubuntu: New Bug description: nm-applet dialog flood I found to reproduce this bug by 2 ways: 1. When not connected to a secured (without password saved) wifi, try to connect to the secured wifi (do not type password or do anything), go take a rest, unlock computer and see a lot of nm-applet dialog. 2. When not connected to a secured (without password saved) wifi, try to connect to the secured wifi (do not type password or do anything); repeat from the begining. To fix this, the dataflow should be like this: On connect event: If keyring-dialog is visible, do nothing, else if connection needs password and password is not saved, display keyring-dialog. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Oct 16 20:29:30 2012 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH GVT-9479 d334e046-2442-45ce-ab45-f248e0cecfd1 802-11-wireless 1350430093 Tue 16 Oct 2012 08:28:13 PM BRTyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 190f3908f-e8a5-488c-8d49-c8b4fc7c9bd4 802-3-ethernet1350188369 Sun 14 Oct 2012 01:19:29 AM BRTyes no /org/freedesktop/NetworkManager/Settings/1 SCHMIDT b19233da-7189-4ce8-84eb-ea7d0170f595 802-11-wireless 1350359585 Tue 16 Oct 2012 12:53:05 AM BRTyes no /org/freedesktop/NetworkManager/Settings/0 Steinmacher2 5fb2a919-2898-4718-af77-471ff4a8a790 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connecting (need authentication) /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connecting enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1067555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1103042] Re: network-manager not started at boot after installing Ubuntu Server and then ubuntu-desktop
** Summary changed: - network-manager service stopped at boot + network-manager not started at boot after installing Ubuntu Server and then ubuntu-desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1103042 Title: network-manager not started at boot after installing Ubuntu Server and then ubuntu-desktop Status in “network-manager” package in Ubuntu: New Bug description: The network-manager service does not start up automatically at boot. This is only after an update. This seems to affect two machines with different hardware. I've also noticed at boot that on both machines it waits a long time for network configuration. Steps to reproduce: 1) Install Ubuntu 12.04.1 Server 32-bit 2) Reboot 3) Install ubuntu-desktop 4) Reboot 5) Log in graphically What happens: In Unity network-manager does not show up Expected: Network Manager should start with the session, nm-applet should be visible. Workaround: sudo service network-manager restart ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic-pae 3.2.35 Uname: Linux 3.2.0-36-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Tue Jan 22 09:37:07 2013 InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) IpRoute: default via 192.168.1.254 dev wlan1 proto static default dev eth0 scope link metric 1002 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.9.64 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.116 metric 2 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.117 metric 2 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH seriesoftubes 1 aa949574-af61-4426-9e2e-1d512e30aef3 802-11-wireless 1358868984 Tue 22 Jan 2013 09:36:24 AM CSTyes no /org/freedesktop/NetworkManager/Settings/1 seriesoftubes ffa4f6e0-2fd8-44bc-99c1-301b73a3262a 802-11-wireless 1358868990 Tue 22 Jan 2013 09:36:30 AM CSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunmanaged /org/freedesktop/NetworkManager/Devices/1 wlan1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1103042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1103809] Re: networkmanager stops accepting keyboard input
I followed the instructions and couldn't reproduce (i.e., I *can* enter the IP address at step 7). ** Summary changed: - networkmanager stops accepting keyboard input + nm-applet stops accepting keyboard input ** Package changed: network-manager (Ubuntu) = network-manager-applet (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1103809 Title: nm-applet stops accepting keyboard input Status in “network-manager-applet” package in Ubuntu: New Bug description: Steps to reproduce: 1. right-click on the network manager icon in system tray, and choose 'edit connections' 2. Select a connection in the dialog which opens, and click 'edit...' 3. in the 'connection name' textbox, type something (to confirm that your keyboard works) 4. click on the 'ipv4 settings' tab 5. select 'manual' in the 'method' dropdown 6. click 'add' to add an address 7. try to type in an IP address (or anything!) in the 'Address' field of the new row you just created 8. to confirm that it's not just the one control but all keyboard input, try changing the name of the connection again (you can't) Required information: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu Description: Ubuntu 12.04.1 LTS Release: 12.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center network-manager: Installed: 0.9.4.0-0ubuntu4.2 Candidate: 0.9.4.0-0ubuntu4.2 Version table: *** 0.9.4.0-0ubuntu4.2 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.9.4.0-0ubuntu3 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ precise/main amd64 Packages 3) What you expected to happen whatever I type should appear in the currently focused text box 4) What happened instead nothing ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Jan 24 15:01:39 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.100.2 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 172.16.81.0/24 dev vmnet1 proto kernel scope link src 172.16.81.1 172.16.244.0/24 dev vmnet8 proto kernel scope link src 172.16.244.1 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.115 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-01-17T15:01:22.853009 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH LAN deb828ff-f2b5-4563-b238-c152e65217c8 802-3-ethernet135988 Thu 24 Jan 2013 15:01:28 EST yes no /org/freedesktop/NetworkManager/Settings/1 Freerunner (USB) 42ca67f0-41f6-4a1b-b299-db236a3b5ed2 802-3-ethernet1358404607 Thu 17 Jan 2013 17:36:47 EST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1103809/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102317] Re: Unable to disable networking/wireless through network indicator
Hmm. Do you have multiple user accounts on your system? Are you logged in to an account other than the initial one? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1102317 Title: Unable to disable networking/wireless through network indicator Status in “network-manager” package in Ubuntu: New Bug description: If I click the Enable Networking or Enable Wireless menu items, nothing happens. The computer stays connected to any networks and the menu items still have check marks. Related to bug #824998 and bug #1059529 - this gives me unavoidable popup dialog spam. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Jan 21 11:01:53 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-10 (71 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IpRoute: default via 10.42.0.1 dev eth0 proto static 10.42.0.0/24 dev eth0 proto kernel scope link src 10.42.0.15 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1102317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1098941] Re: sudo service networking restart causes the GUI to crash
** Summary changed: - GUI drops out when restarting networking services. + sudo service networking restart causes the GUI to crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1098941 Title: sudo service networking restart causes the GUI to crash Status in “network-manager” package in Ubuntu: New Bug description: In Ubuntu 12.10 Desktop x64 and the Gnome Desktop version of Ubuntu; when you restart the networking via: sudo service networking stop (or restart) the GUI for the entire desktop crashes and you are left either at the cli or the GUI doesn't completely close but any terminal windows left open do not function. $ lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 What I was expecting to happen was for the networking to restart during normal operation of the GUI. What happened instead was that the GUI crashed I am using an ASUS N56VM laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1098941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1098941] Re: sudo service networking restart causes the GUI to crash
I understand that it was once commonplace to do /etc/init.d/networking restart but (the latter's Upstart replacement) sudo restart networking is deprecated. ** Changed in: network-manager (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1098941 Title: sudo service networking restart causes the GUI to crash Status in “ifupdown” package in Ubuntu: New Bug description: In Ubuntu 12.10 Desktop x64 and the Gnome Desktop version of Ubuntu; when you restart the networking via: sudo service networking stop (or restart) the GUI for the entire desktop crashes and you are left either at the cli or the GUI doesn't completely close but any terminal windows left open do not function. $ lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 What I was expecting to happen was for the networking to restart during normal operation of the GUI. What happened instead was that the GUI crashed I am using an ASUS N56VM laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1098941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1098941] Re: sudo service networking restart causes the GUI to crash
/etc/init/networking.conf is in ifupdown ** Package changed: network-manager (Ubuntu) = ifupdown (Ubuntu) ** Changed in: ifupdown (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1098941 Title: sudo service networking restart causes the GUI to crash Status in “ifupdown” package in Ubuntu: New Bug description: In Ubuntu 12.10 Desktop x64 and the Gnome Desktop version of Ubuntu; when you restart the networking via: sudo service networking stop (or restart) the GUI for the entire desktop crashes and you are left either at the cli or the GUI doesn't completely close but any terminal windows left open do not function. $ lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 What I was expecting to happen was for the networking to restart during normal operation of the GUI. What happened instead was that the GUI crashed I am using an ASUS N56VM laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1098941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1091610] Re: Using NM, Wi-Fi disconnects with heavy traffic; doesn't happen with wicd or Windows 7 -- Realtek RTL8191SEvA
** Summary changed:
- wifi connection loss on Realtek RTL8191SEvA
+ Using NM, Wi-Fi disconnects with heavy traffic; doesn't happen with wicd or
Windows 7 -- Realtek RTL8191SEvA
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1091610
Title:
Using NM, Wi-Fi disconnects with heavy traffic; doesn't happen with
wicd or Windows 7 -- Realtek RTL8191SEvA
Status in “linux” package in Ubuntu:
Incomplete
Status in “network-manager” package in Ubuntu:
New
Bug description:
I am running 12.04, on an asus 1201n EEEPC and the wifi connection
drops out during sustained heavy traffic, eg video conf.
When I boot the same amchine to WIN7, there is no problem, ever.
There seems to be no way to get the connection back without rebooting.
I am at a loss as to how to proceed, but am very willing to help out.
Please let me know, I am desperate.
Thanks, your faithful Ubuntu supporter from day-0,
Bob
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: NVidia [HDA NVidia], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
CRDA:
country BE:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xf9f78000 irq 20'
Mixer name : 'Nvidia MCP79/7A HDMI'
Components : 'HDA:10ec0269,104383ce,0014
HDA:10de0007,10de0101,00100100'
Controls : 22
Simple ctrls : 11
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=10f62a6a-1fbf-4081-9120-c5a01b145048
InstallationMedia: Ubuntu-Netbook 10.10 Maverick Meerkat - Release i386
(20101007)
MachineType: ASUSTeK Computer INC. 1201N
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-35-generic
root=UUID=ea6ffad6-ec2d-4fd3-acf5-01306240865c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.2.0-35-generic N/A
linux-backports-modules-3.2.0-35-generic N/A
linux-firmware1.79.1
Tags: precise
Uname: Linux 3.2.0-35-generic i686
UpgradeStatus: Upgraded to precise on 2012-06-09 (191 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
dmi.bios.date: 03/17/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0325
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1201N
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0325:bd03/17/2010:svnASUSTeKComputerINC.:pn1201N:pvrx.x:rvnASUSTeKComputerINC.:rn1201N:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1201N
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1091610/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1088984] Re: 3G connection is established, but no data is transferred -- ZTE MF 118
Note: The ZTE MF 118 isn't listed upstream https://live.gnome.org/NetworkManager/MobileBroadband as supported, but the ZTE MF 110 is listed. ** Description changed: - The connection is established properly and signal is strong, yet I cannot access any website or other network service. Using ZTE MF 118 on 3g Mobile Broadband (Aircel INDIA). Worked when connecte with sakis3g script. - My Ubuntu version is Ubuntu 12.04.1 LTS 64bit and network-manager version is 0.9.4.0. Modem manager version is 0.5.2.0 + The connection is established properly and signal is strong, yet I + cannot access any websites or other network service. Using ZTE MF 118 on + 3G Mobile Broadband (Aircel INDIA). Worked when connected with sakis3g + script. + + My Ubuntu version is Ubuntu 12.04.1 LTS 64-bit and network-manager + version is 0.9.4.0. Modem-manager version is 0.5.2.0. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1088984 Title: 3G connection is established, but no data is transferred -- ZTE MF 118 Status in “network-manager” package in Ubuntu: New Bug description: The connection is established properly and signal is strong, yet I cannot access any websites or other network service. Using ZTE MF 118 on 3G Mobile Broadband (Aircel INDIA). Worked when connected with sakis3g script. My Ubuntu version is Ubuntu 12.04.1 LTS 64-bit and network-manager version is 0.9.4.0. Modem-manager version is 0.5.2.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1088984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1073662] Re: NM loses connection and can't reconnect; No keyring secrets -- Intel PRO/Wireless 2200BG ipw2200
Are the credentials in a file in /etc/NetworkManager/system-connections/ ? ** Summary changed: - network manager looses connection, reconnect not possible + NM loses connection and can't reconnect; No keyring secrets -- Intel PRO/Wireless 2200BG ipw2200 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1073662 Title: NM loses connection and can't reconnect; No keyring secrets -- Intel PRO/Wireless 2200BG ipw2200 Status in “network-manager” package in Ubuntu: New Bug description: Whenever a new wireless router comes up, network manager tries to reconnect. It does not succeed. The nm-applet reports: ** Message: No keyring secrets found for rsb/802-11-wireless-security; asking user. (nm-applet:11812): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed There is no key in the keyring store. However on boot, the connection is established So there are several questions: 1. Where is the WLAN credential stored that is generated using the network manager connection dialog 2. Why does the nm-applet look for the key in the keyring 3. Why is the WLAN credential not stored there ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Wed Oct 31 18:29:44 2012 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-10-26 (5 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) IpRoute: default via 10.1.0.254 dev eth1 proto static 10.0.0.0/8 dev eth1 proto kernel scope link src 10.1.0.199 metric 9 169.254.0.0/16 dev eth1 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1df03d4ed-6f6a-404d-82b6-242fbe8e6896 802-3-ethernet1351703962 Mit 31 Okt 2012 18:19:22 CET yes no /org/freedesktop/NetworkManager/Settings/1 rsb 690f1d18-c26e-4abd-91da-2dc1d35fdea3 802-11-wireless 1351704562 Mit 31 Okt 2012 18:29:22 CET yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1073662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1067555] Re: nm-applet keyring dialog flood
*** This bug is a duplicate of bug 31286 *** https://bugs.launchpad.net/bugs/31286 ** This bug has been marked a duplicate of bug 31286 Displays repeated keyring dialogs on resume from suspend and login -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1067555 Title: nm-applet keyring dialog flood Status in “network-manager” package in Ubuntu: New Bug description: nm-applet dialog flood I found to reproduce this bug by 2 ways: 1. When not connected to a secured (without password saved) wifi, try to connect to the secured wifi (do not type password or do anything), go take a rest, unlock computer and see a lot of nm-applet dialog. 2. When not connected to a secured (without password saved) wifi, try to connect to the secured wifi (do not type password or do anything); repeat from the begining. To fix this, the dataflow should be like this: On connect event: If keyring-dialog is visible, do nothing, else if connection needs password and password is not saved, display keyring-dialog. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Oct 16 20:29:30 2012 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH GVT-9479 d334e046-2442-45ce-ab45-f248e0cecfd1 802-11-wireless 1350430093 Tue 16 Oct 2012 08:28:13 PM BRTyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 190f3908f-e8a5-488c-8d49-c8b4fc7c9bd4 802-3-ethernet1350188369 Sun 14 Oct 2012 01:19:29 AM BRTyes no /org/freedesktop/NetworkManager/Settings/1 SCHMIDT b19233da-7189-4ce8-84eb-ea7d0170f595 802-11-wireless 1350359585 Tue 16 Oct 2012 12:53:05 AM BRTyes no /org/freedesktop/NetworkManager/Settings/0 Steinmacher2 5fb2a919-2898-4718-af77-471ff4a8a790 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connecting (need authentication) /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connecting enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1067555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 31286] Re: Displays repeated keyring dialogs on resume from suspend and login
From bug #1067555: I found to reproduce this bug by 2 ways: 1. When not connected to a secured (without password saved) wifi, try to connect to the secured wifi (do not type password or do anything), go take a rest, unlock computer and see a lot of nm-applet dialog. 2. When not connected to a secured (without password saved) wifi, try to connect to the secured wifi (do not type password or do anything); repeat from the begining. To fix this, the dataflow should be like this: On connect event: If keyring-dialog is visible, do nothing, else if connection needs password and password is not saved, display keyring-dialog. ** Bug watch added: GNOME Bug Tracker #676278 https://bugzilla.gnome.org/show_bug.cgi?id=676278 ** Changed in: network-manager Importance: Low = Unknown ** Changed in: network-manager Status: Invalid = Unknown ** Changed in: network-manager Remote watch: GNOME Bug Tracker #359532 = GNOME Bug Tracker #676278 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/31286 Title: Displays repeated keyring dialogs on resume from suspend and login Status in NetworkManager: Unknown Status in “network-manager” package in Ubuntu: Fix Released Bug description: scenario: Dapper FL3 + updates Network-manager + applet .5.1 Suspend - resume working properly Booted with wired network connected. Wireless network not activated during this session. Pressed the Shutdown toolbar icon and selected Suspend. Saw that the Gnome keyring dialog popped up just before the system went to sleep. On resume, there were at least 5 pending Gnome keyring dialogs. After having typed my password in each of these, the system went momentarily to sleep and woke up within a couple of seconds by itself (5 sec?). After the last password-suspend-resume cycle, the system is working perfectly. Anders To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/31286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 31286] Re: Displays repeated keyring dialogs on resume from suspend and login
This bug needs to be reopened because there are new reports of the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/31286 Title: Displays repeated keyring dialogs on resume from suspend and login Status in NetworkManager: Confirmed Status in “network-manager” package in Ubuntu: Fix Released Bug description: scenario: Dapper FL3 + updates Network-manager + applet .5.1 Suspend - resume working properly Booted with wired network connected. Wireless network not activated during this session. Pressed the Shutdown toolbar icon and selected Suspend. Saw that the Gnome keyring dialog popped up just before the system went to sleep. On resume, there were at least 5 pending Gnome keyring dialogs. After having typed my password in each of these, the system went momentarily to sleep and woke up within a couple of seconds by itself (5 sec?). After the last password-suspend-resume cycle, the system is working perfectly. Anders To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/31286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
