[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 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 1096600] Re: Clicking "Edit Connections..." or "Connection Information" does nothing, "More networks" is empty
** 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/1096600 Title: Clicking "Edit Connections..." or "Connection Information" does nothing, "More networks" is empty Status in “network-manager-applet” package in Ubuntu: New Bug description: As the summary says. From time to time Network-manager breaks and after that clicking "Edit Connections" or "Connection Information" does nothing and "More Networks" is empty even though there are several WIFI access points in the area. Rebooting the machine is a workaround for this issue. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Sun Jan 6 16:05:03 2013 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) IpRoute: default via 192.168.178.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.25 metric 2 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-dev: DEVICE TYPE STATE DBUS-PATH usb0 gsm disconnected /org/freedesktop/NetworkManager/Devices/5 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-applet/+bug/1096600/+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
@tombert: Probably not the same issue, since the issue being discussed here is not fixed by restarting. Please file a new bug report against dnsmasq with a detailed description of your problem. -- You received this bug notification because you are a member of 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 1098152] Re: DNS resolve failed after upgrade from 12.04 to 12.10
/etc/resolv.conf containing 127.0.0.1 was correct, provided you have a local nameserver running that listens at IP address 127.0.0.1. In Ubuntu 12.10, the dnsmasq process controlled by NetworkManager listens at 127.0.1.1, not at 127.0.0.1, so it wasn't NetworkManager that registered 127.0.0.1 with resolvconf. My guess is that it was bind9 that did that, and that your problem was bug #933723. For background information please read the following blog posting. https://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/ ** 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/1098152 Title: DNS resolve failed after upgrade from 12.04 to 12.10 Status in “bind9” package in Ubuntu: Incomplete Bug description: I just upgraded from 12.04 to 12.10 and suddenly I couldn't resolve the host. The ip and DNS was correct. The nameserver in /etc/resolv.conf was 127.0.0.1. I changed it to the DNS directly and all went swell. I had to install dnsmasq for it to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1098152/+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 1098152] Re: DNS resolve failed after upgrade from 12.04 to 12.10
Not a NM problem; probably a dupe of #933723. ** Package changed: network-manager (Ubuntu) => bind9 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1098152 Title: DNS resolve failed after upgrade from 12.04 to 12.10 Status in “bind9” package in Ubuntu: Incomplete Bug description: I just upgraded from 12.04 to 12.10 and suddenly I couldn't resolve the host. The ip and DNS was correct. The nameserver in /etc/resolv.conf was 127.0.0.1. I changed it to the DNS directly and all went swell. I had to install dnsmasq for it to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1098152/+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 1098362] Re: DHCP settings for network manager shared connection are hard-coded source, should be editable
It's true. Looking at current NM src/nm-device.c line 1978:
static guint32
reserve_shared_ip (void)
{
guint32 start = (guint32) ntohl (0x0a2a0001); /* 10.42.0.1 */
guint32 count = 0;
This is upstream source code. Please file a bug report upstream.
https://bugzilla.gnome.org/browse.cgi?product=NetworkManager
** 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/1098362
Title:
DHCP settings for network manager shared connection are hard-coded
source, should be editable
Status in “network-manager” package in Ubuntu:
Invalid
Bug description:
1) Ubuntu 10.04, but it's in all versions.
2) any version of network manager
3) I want to be able to change the DHCP settings for a shared network
connection
4) YOUR OPERATING SYSTEM WON'T LET ME!
The file nm-device.c contains this line:
nm-device.c:guint32 start = (guint32) ntohl (0x0a2a2b01); /*
10.42.43.1 */
hard-coding DHCP settings that should obviously be editable by the
user is a TERRIBLE IDEA. PLEASE FIX.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1098362/+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 1098362] Re: DHCP settings for network manager shared connection are hard-coded source, should be editable
To reduce administration, closed the report in Launchpad. -- 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/1098362 Title: DHCP settings for network manager shared connection are hard-coded source, should be editable Status in “network-manager” package in Ubuntu: Invalid Bug description: 1) Ubuntu 10.04, but it's in all versions. 2) any version of network manager 3) I want to be able to change the DHCP settings for a shared network connection 4) YOUR OPERATING SYSTEM WON'T LET ME! The file nm-device.c contains this line: nm-device.c:guint32 start = (guint32) ntohl (0x0a2a2b01); /* 10.42.43.1 */ hard-coding DHCP settings that should obviously be editable by the user is a TERRIBLE IDEA. PLEASE FIX. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1098362/+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 1096853] Re: Wi-Fi disconnects then cannot connect to any network -- Broadcom BCM43224 bcma
Possibly a driver issue ** Summary changed: - WIFI disconnects then can not connect to any network + Wi-Fi disconnects then cannot connect to any network -- Broadcom BCM43224 bcma ** 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/1096853 Title: Wi-Fi disconnects then cannot connect to any network -- Broadcom BCM43224 bcma Status in “linux” package in Ubuntu: New Bug description: I start my laptop, the network connects and I can use it well. Then after some time (hours, or days) the WIFI disconnects and can't connect to the network, nor any other WIFI network. The ethernet works fine however. There is a kworker process that hangs on CPU. NM asks me the WIFI key several times, and does not success in connecting the network. I then need to reboot my computer, as any "service network-manager restart" or "service networking restart" does not work. dmesg contains informations about an exception, I copied it in the attached .txt . Those lines are repeated several times. I think there are two bugs : - One in the WIFI driver that prevents connecting to the network - One in the network-manager that does not understand there is an internal bug and keeps trying to reconnect, while asking me the keyphrase. NM should know that the last connection failes because of an internal failure. 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-0ubuntu9 Architecture: amd64 Date: Mon Jan 7 13:09:35 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2011-07-05 (551 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 192.168.1.254 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.80 metric 9 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 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-10-23 (76 days ago) 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.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096853/+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 1098298] Re: NetworkManager fails to detect link status change -- Intel 82577LM e1000e
Possibly a driver issue ** Summary changed: - network-manager fails to detect link status change + NetworkManager fails to detect link status change -- Intel 82577LM e1000e ** Description changed: Steps to reproduce: 1.) Start Ubuntu, with LAN plugged in, login - 2.) Verify Network Manager detects the Wired Connection - 3.) stop Network manager + 2.) Verify NetworkManager detects the Wired Connection + 3.) stop NetworkManager 4.) unplug LAN cable - 5.) start Network manager - Result: Network manager doesn't detect that eth0 is not in RUNNING state + 5.) start NetworkManager + Result: NetworkManager doesn't detect that eth0 is not in the RUNNING state Plugging in LAN cable doesn't change state either, i.e. eth0 remains unconfigured. - root@thinkpad:~# service network-manager stop network-manager stop/waiting root@thinkpad:~# ifconfig eth0 - eth0 Link encap:Ethernet HWaddr 00:26:2d:f6:06:8b - inet addr:10.201.4.52 Bcast:10.201.7.255 Mask:255.255.252.0 - inet6 addr: fe80::226:2dff:fef6:68b/64 Scope:Link - UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 - RX packets:17695 errors:0 dropped:0 overruns:0 frame:0 - TX packets:14813 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:1000 - RX bytes:17180328 (17.1 MB) TX bytes:3811166 (3.8 MB) - Interrupt:20 Memory:f250-f252 + eth0 Link encap:Ethernet HWaddr 00:26:2d:f6:06:8b + inet addr:10.201.4.52 Bcast:10.201.7.255 Mask:255.255.252.0 + inet6 addr: fe80::226:2dff:fef6:68b/64 Scope:Link + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 + RX packets:17695 errors:0 dropped:0 overruns:0 frame:0 + TX packets:14813 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:1000 + RX bytes:17180328 (17.1 MB) TX bytes:3811166 (3.8 MB) + Interrupt:20 Memory:f250-f252 ## unplug network cable root@thinkpad:~# ifconfig eth0 - eth0 Link encap:Ethernet HWaddr 00:26:2d:f6:06:8b - inet addr:10.201.4.52 Bcast:10.201.7.255 Mask:255.255.252.0 - inet6 addr: fe80::226:2dff:fef6:68b/64 Scope:Link - UP BROADCAST MULTICAST MTU:1500 Metric:1 - RX packets:17695 errors:0 dropped:0 overruns:0 frame:0 - TX packets:14813 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:1000 - RX bytes:17180328 (17.1 MB) TX bytes:3811166 (3.8 MB) - Interrupt:20 Memory:f250-f252 + eth0 Link encap:Ethernet HWaddr 00:26:2d:f6:06:8b + inet addr:10.201.4.52 Bcast:10.201.7.255 Mask:255.255.252.0 + inet6 addr: fe80::226:2dff:fef6:68b/64 Scope:Link + UP BROADCAST MULTICAST MTU:1500 Metric:1 + RX packets:17695 errors:0 dropped:0 overruns:0 frame:0 + TX packets:14813 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:1000 + RX bytes:17180328 (17.1 MB) TX bytes:3811166 (3.8 MB) + Interrupt:20 Memory:f250-f252 ## dmesg: [ 894.264179] init: network-manager main process (6194) killed by KILL signal [ 899.925268] e1000e: eth0 NIC Link is Down root@thinkpad:~# service network-manager start network-manager start/running, process 7702 # nm-tool [...] - Device: eth0 [Wired connection 1] --- - Type: Wired - Driver:e1000e - State: connecting (getting IP configuration) - Default: no - HW Address:00:26:2D:F6:06:8B + Type: Wired + Driver:e1000e + State: connecting (getting IP configuration) + Default: no + HW Address:00:26:2D:F6:06:8B - Capabilities: + Capabilities: - Wired Properties - Carrier: on + Wired Properties + Carrier: on # dmesg: [ 1043.488154] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1046.290181] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1046.290428] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready root@thinkpad:~# ifconfig eth0 - eth0 Link encap:Ethernet HWaddr 00:26:2d:f6:06:8b - UP BROADCAST MULTICAST MTU:1500 Metric:1 - RX packets:17695 errors:0 dropped:0 overruns:0 frame:0 - TX packets:14813 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:1000 - RX bytes:17180328 (17.1 MB) TX bytes:3811166 (3.8 MB) - Interrupt:20 Memory:f250-f252 - + eth0 Link encap:Ethernet HWaddr 00:26:2d:f6:06:8b + UP BROADCAST MULTICAST MTU:1500 Metric:1 + RX packets:17695 errors:0 dropped:0 overruns:0 frame:0 + TX packets:14813 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:1000 + RX bytes:17180328 (17.
[Desktop-packages] [Bug 1093622] Re: NM doesn't react to disconnect and connect commands for WiFi networks for very long time (or ever)
Please run "apport-collect 1093622" to provide more information. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete ** Changed in: ac100 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) Status in Enablement project for the Toshiba AC100 NetBook: Incomplete 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 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 1093353] Re: NetworkManager disconnects Wi-Fi and can't reconnect -- Broadcom BCM4312 wl
Possibly a driver issue ** Summary changed: - NetworkManager disconnects wifi and can't reconnect + NetworkManager disconnects Wi-Fi and can't reconnect -- Broadcom BCM4312 wl ** 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/1093353 Title: NetworkManager disconnects Wi-Fi and can't reconnect -- Broadcom BCM4312 wl Status in “linux” package in Ubuntu: New Bug description: NetworkManager drops connection regulary on my Linksys WRT54GC and can't reconncet. Only solution is to reset wifi card. I know there is a similar bug affecting network manager and linksys wrt54gc but released fix doesn't help. It also can't reconnect automatically. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sun Dec 23 23:12:41 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) IpRoute: default via 192.168.0.1 dev eth2 proto static 169.254.0.0/16 dev eth2 scope link metric 1000 192.168.0.0/24 dev eth2 proto kernel scope link src 192.168.0.9 metric 2 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-06-03 (202 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 eth2 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 enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1093353/+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 1100273] Re: transient dns errors
*** This bug is a duplicate of bug 1003842 *** https://bugs.launchpad.net/bugs/1003842 ** 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/1100273 Title: transient dns errors Status in “network-manager” package in Ubuntu: New Bug description: I have been getting random "site not found" errors when web browsing on the campus network and these seem to be cured by disabling the dnsmasq config used by NetworkManager. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.2 Uname: Linux 3.8.0-030800rc2-generic x86_64 ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Wed Jan 16 15:16:17 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) IpRoute: default via 10.20.1.1 dev wlan0 10.20.0.0/16 dev wlan0 proto kernel scope link src 10.20.206.118 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/zsh SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:9889): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1100273/+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 1100568] Re: nm-applet doesn't appear to be connecting after resume -- Intel Centrino Wireless-N 2230 iwlwifi
** Summary changed: - nm-applet doesn't appear to be connecting after resume + nm-applet doesn't appear to be connecting after resume -- Intel Centrino Wireless-N 2230 iwlwifi ** Description changed: - After I resume, nm-applet seems to go from disconnected to connected, not giving any feedback while it's connecting. - It's a bit uncomfortable because you can't tell if you should manually connect or not. + After I resume, nm-applet seems to go from disconnected to connected, + not giving any feedback while it's connecting. + + It's a bit uncomfortable because you can't tell if you should manually + connect or not. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Wed Jan 16 22:00:33 2013 EcryptfsInUse: Yes 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 2013-01-01 (15 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121231) 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 9 + 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 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= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + 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 - CiscoHome2c8e6ab4e-d778-4e40-8f50-bcfab71d35bd 802-11-wireless 1358384397 Wed 16 Jan 2013 09:59:57 PM ARTyes no /org/freedesktop/NetworkManager/Settings/2 - AndroidAP a5bf3d4d-b3d7-4116-a7f5-7bce0367b268 802-11-wireless 1358346689 Wed 16 Jan 2013 11:31:29 AM ARTyes no /org/freedesktop/NetworkManager/Settings/1 - internet 86d8e9d6-7dde-4cdc-9547-846b3c168d54 802-11-wireless 1357250704 Thu 03 Jan 2013 07:05:04 PM ARTyes no /org/freedesktop/NetworkManager/Settings/0 - Wired connection 1dff391ff-7206-4f51-babe-c0143ada0346 802-3-ethernet1358359590 Wed 16 Jan 2013 03:06:30 PM ARTyes no /org/freedesktop/NetworkManager/Settings/3 + NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH + CiscoHome2c8e6ab4e-d778-4e40-8f50-bcfab71d35bd 802-11-wireless 1358384397 Wed 16 Jan 2013 09:59:57 PM ARTyes no /org/freedesktop/NetworkManager/Settings/2 + AndroidAP a5bf3d4d-b3d7-4116-a7f5-7bce0367b268 802-11-wireless 1358346689 Wed 16 Jan 2013 11:31:29 AM ARTyes no /org/freedesktop/NetworkManager/Settings/1 + internet 86d8e9d6-7dde-4cdc-9547-846b3c168d54 802-11-wireless 1357250704 Thu 03 Jan 2013 07:05:04 PM ARTyes no /org/freedesktop/NetworkManager/Settings/0 + Wired connection 1dff391ff-7206-4f51-babe-c0143ada0346 802-3-ethernet1358359590 Wed 16 Jan 2013 03:06:30 PM ARTyes 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 + 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.7.0connected enabled enabled enabledenabled
[Desktop-packages] [Bug 1101825] Re: IPv6 static default route added incorrectly by network-manager
** Description changed: The relevant part of the IPv6 routing table looks like this: - fe80::/64 dev wlan0 proto kernel metric 256 - default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 + fe80::/64 dev wlan0 proto kernel metric 256 + default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec + I believe the proto static metric 1 route is an error, since it persists + even when the router stops advertising. This breaks the IPv6 + architecture for router redundancy. - I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. - - I am in control of this networt and can alter router advertisement + I am in control of this network and can alter router advertisement parameters if needed. 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-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IpRoute: - default via 192.168.4.1 dev wlan0 proto static - 169.254.0.0/16 dev wlan0 scope link metric 1000 - 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 + default via 192.168.4.1 dev wlan0 proto static + 169.254.0.0/16 dev wlan0 scope link metric 1000 + 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 MarkForUpload: True 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: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 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.0connected enabled enabled enabledenabled enabled + RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN + running 0.9.6.0connected enabled enabled enabledenabled enabled -- 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/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in “network-manager” package in Ubuntu: New Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. 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-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Q
[Desktop-packages] [Bug 1100273] Re: transient dns errors
*** This bug is a duplicate of bug 1004775 *** https://bugs.launchpad.net/bugs/1004775 "This bug was fixed in the package network-manager - 0.9.6.0~git201207271115.edb85e9-0ubuntu1". ** Description changed: - I have been getting random "site not found" errors when web browsing on the campus network and these - seem to be cured by disabling the dnsmasq config used by NetworkManager. + I have been getting random "site not found" errors when web browsing on + the campus network and these seem to be cured by disabling the dnsmasq + config used by NetworkManager. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.2 Uname: Linux 3.8.0-030800rc2-generic x86_64 ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Wed Jan 16 15:16:17 2013 IfupdownConfig: - auto lo - iface lo inet loopback + auto lo + iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) IpRoute: - default via 10.20.1.1 dev wlan0 - 10.20.0.0/16 dev wlan0 proto kernel scope link src 10.20.206.118 + default via 10.20.1.1 dev wlan0 + 10.20.0.0/16 dev wlan0 proto kernel scope link src 10.20.206.118 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) - LANG=en_US.UTF-8 - SHELL=/bin/zsh + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/zsh SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: - Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: - ** (process:9889): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files - Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. + Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: + ** (process:9889): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files + Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: - RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN - not running unknownunknown unknown unknown unknownunknown unknown + RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN + not running unknownunknown unknown unknown unknownunknown unknown ** This bug has been marked a duplicate of bug 1004775 NetworkManager restarts dnsmasq and adds host route on every IPv6 route lookup -- 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/1100273 Title: transient dns errors Status in “network-manager” package in Ubuntu: New Bug description: I have been getting random "site not found" errors when web browsing on the campus network and these seem to be cured by disabling the dnsmasq config used by NetworkManager. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.2 Uname: Linux 3.8.0-030800rc2-generic x86_64 ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Wed Jan 16 15:16:17 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) IpRoute: default via 10.20.1.1 dev wlan0 10.20.0.0/16 dev wlan0 proto kernel scope link src 10.20.206.118 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/zsh SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:9889): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all'
[Desktop-packages] [Bug 1100445] Re: wireless network name in network settings drop down list should be selectable from anywhere along the length of the name not just at the end
** 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/1100445 Title: wireless network name in network settings drop down list should be selectable from anywhere along the length of the name not just at the end Status in “network-manager-applet” package in Ubuntu: New Bug description: When selecting a wireless network name in the network settings app (System Settings -> Network), under Network Name you can see the name of the currently associated network, with the ability to cause the drop down list to expand by selecting the down arrow at the far right hand edge of the box. I shouldn't have to navigate to that far right edge to select the small that is the down arrow in order to bring up the list, I should be able to select anywhere along the length of the box containing the Network Name. When hovering over the network name, the mouse pointer takes on a text entry style, yet this is not a text entry box; selecting the network name does nothing. Description: Ubuntu 12.10 Release: 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1100445/+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 1098362] Re: DHCP settings for network manager shared connection are hard-coded source, should be editable
** Changed in: network-manager (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/1098362 Title: DHCP settings for network manager shared connection are hard-coded source, should be editable Status in “network-manager” package in Ubuntu: Confirmed Bug description: 1) Ubuntu 10.04, but it's in all versions. 2) any version of network manager 3) I want to be able to change the DHCP settings for a shared network connection 4) YOUR OPERATING SYSTEM WON'T LET ME! The file nm-device.c contains this line: nm-device.c:guint32 start = (guint32) ntohl (0x0a2a2b01); /* 10.42.43.1 */ hard-coding DHCP settings that should obviously be editable by the user is a TERRIBLE IDEA. PLEASE FIX. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1098362/+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 1101182] Re: Shared Connection gets 10.42.0.X IP addresses even if those are taken
*** This bug is a duplicate of bug 1098362 *** https://bugs.launchpad.net/bugs/1098362 ** This bug has been marked a duplicate of bug 1098362 DHCP settings for network manager shared connection are hard-coded source, should be editable -- 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/1101182 Title: Shared Connection gets 10.42.0.X IP addresses even if those are taken Status in “network-manager” package in Ubuntu: New Bug description: When you choose "Shared to other computers" in network-manager to create a network, the IP addresses are always 10.42.0.X. This is bad enough, but it doesn't check if those addresses are already in use on another interface, blowing up both networks and messing up routes. A fix would be to un-hardcode the addresses, but even warning/stopping the user from creating two networks with the same IPs would be better than the status quo. (In my setup one Ubuntu computer shares its network on a wired connection. Another Ubuntu computer tries to share that connection via WiFi. I'm not sure whether Network Manager warns if both the networks are created on the same computer.) 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 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Fri Jan 18 14:48:24 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-10 (69 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/1101182/+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 1099949] Re: NM disables virtual machine manager's virbr0
** Summary changed: - Disables virtual machine manager's virbr0 + NM disables virtual machine manager's virbr0 -- 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/1099949 Title: NM disables virtual machine manager's virbr0 Status in “network-manager” package in Ubuntu: New Bug description: This is similar to #961089 and may well be a duplicate, but I believe that there's a distinction since NM is disabling a bridge that's been created automatically by virt-manager, and so the explanation that it's not a normal way of configuring bridges doesn't (or at least shouldn't) apply. Basically, what I've done is: 1) Install virt-manager 2) Create some VMs 3) Leave my machine on for a while 4) Notice that the bridge disappears and none of the machines can speak to the host (or get DHCP leases). I noticed this earlier today, and so added the mac address of the bridge to Network Manager's config, but it appears to have ignored this, too: root@amazing:/home/avi# tail -n1 /etc/NetworkManager/NetworkManager.conf unmanaged-devices=mac:fe:54:00:43:19:37 root@amazing:/home/avi# ifconfig virbr0 virbr0Link encap:Ethernet HWaddr fe:54:00:43:19:37 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1723 errors:0 dropped:0 overruns:0 frame:0 TX packets:2140 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:200990 (200.9 KB) TX bytes:1822872 (1.8 MB) root@amazing:/home/avi# I see this in syslog at about the same time (grepping for virbr0): Jan 15 17:50:13 amazing NetworkManager[1261]: (virbr0): now managed Jan 15 17:50:13 amazing NetworkManager[1261]: (virbr0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jan 15 17:50:13 amazing NetworkManager[1261]: (virbr0): bringing up device. Jan 15 17:50:13 amazing avahi-daemon[652]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jan 15 17:50:13 amazing avahi-daemon[652]: New relevant interface virbr0.IPv4 for mDNS. Jan 15 17:50:13 amazing avahi-daemon[652]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Jan 15 17:50:13 amazing NetworkManager[1261]: (virbr0): carrier now ON (device state 20) Jan 15 17:50:13 amazing NetworkManager[1261]: (virbr0): deactivating device (reason 'managed') [2] Jan 15 17:50:13 amazing avahi-daemon[652]: Withdrawing address record for 192.168.122.1 on virbr0. Jan 15 17:50:13 amazing avahi-daemon[652]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jan 15 17:50:13 amazing avahi-daemon[652]: Interface virbr0.IPv4 no longer relevant for mDNS. Jan 15 17:50:13 amazing NetworkManager[1261]: (virbr0): device state change: unavailable -> disconnected (reason 'none') [20 30 0] Jan 15 17:50:17 amazing dnsmasq-dhcp[1932]: DHCP packet received on virbr0 which has no address Jan 15 17:50:19 amazing dnsmasq-dhcp[1932]: DHCP packet received on virbr0 which has no address Jan 15 17:50:26 amazing dnsmasq-dhcp[1932]: DHCP packet received on virbr0 which has no address Jan 15 17:50:27 amazing dnsmasq-dhcp[1932]: DHCP packet received on virbr0 which has no address ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0 Uname: Linux 3.7.0-7-generic x86_64 ApportVersion: 2.7-0ubuntu2 Architecture: amd64 Date: Tue Jan 15 17:57:47 2013 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-09-10 (127 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120910) IpRoute: default via 192.168.1.254 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.67 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2012-11-26 (50 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-01-15T16:36:47.133697 nmcli-dev: DEVICE TYPE STATE DBUS-PATH virbr0 bridgedisconnected /org/freedesktop/NetworkManager/Devices/2 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.7.0connected enabled enabled enabledenabled enabled To manage
[Desktop-packages] [Bug 1099976] Re: NetworkManager falsely reports WPA network "out of range"
** Summary changed: - Raring network manager msg false out of range WPA network + NetworkManager falsely reports WPA network "out of range" ** Description changed: - On boot, Raring amd64 Broadcom BCM43225 the network manager correctly - detects the network name, then network manager falsely reports "out of - range". What the raring network manager is trying to do is to connect - without using the WPA encryption key which it already has. + On boot with amd64 Broadcom BCM43225, Raring NetworkManager correctly + detects the network name, then NM falsely reports "out of range". What + NM is trying to do is to connect without using the WPA encryption key + which it already has. - This is similar to bug 1097002 except in 1097002 the network manager - doesn't even see the hidden network name even though it already has the - encryption key for that network. + This is similar to bug 1097002 except in 1097002 NM doesn't even see the + hidden network name even though it already has the encryption key for + that network. In syslog below, says "has security but secrets are required". That's - right, has security, but network manager already has the secret - encryption key, network manager is supposed to use the key instead of - disconnecting. + right, has security, but NM already has the secret encryption key; NM is + supposed to use the key instead of disconnecting. - Obviously network manager doesn't even look to see it already has the - key which it does. + Obviously NM doesn't even look to see it already has the key which it + does. - The branch in the network manager script that sees "secrets are - required" should go right ahead, see that it already has the "secrets", - and use them. Network manager either doesn't have this path or is - refusing to use it. + The branch in the NM script that sees "secrets are required" should go + right ahead, see that it already has the "secrets", and use them. + NetworkManager either doesn't have this path or is refusing to use it. I go on to connect manually with settings > network using the encryption key network manager already had and should have used. - In any case, when network manager finally does ask the kernel to - connect, the kernel connects just fine. Not a kernel problem. + In any case, when NetworkManager finally does ask the kernel to connect, + the kernel connects just fine. Not a kernel problem. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Auto-activating connection 'LAUREL'. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) starting connection 'LAUREL' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0/wireless): access point 'LAUREL' has security, but secrets are required. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0/wireless): connection 'LAUREL' has security, and secrets exist. No new secrets needed. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'ssid' value 'LAUREL' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'scan_ssid' value '1'
[Desktop-packages] [Bug 1099696] Re: nmcli con up id **** does not work for second time
** Description changed: - when I try to connect with connection named Hutch which is asocited with - 3G dongle and HSPA connection. + I try to connect with connection named "Hutch" which is associated with + a 3G dongle and HSPA service. - at first time it connects.but if it is disconnected and try to re - connect it in the same session it does not work. + 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 - ** (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 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. ** Summary changed: - nmcli con up id does not work for second time + Can't reconnect 3G HSPA after disconnect ; log out and in fixes it -- 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: New 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 1077079] Re: network-manager doesn't display connected network or signal strength
** 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/1077079 Title: network-manager doesn't display connected network or signal strength Status in “network-manager-applet” package in Ubuntu: New Bug description: 1. connect to a wireless network by clicking on the name in the applet. 2. check that the connection works. 3. see that there is no network listed on "Wireless Networks" in the applet. (Although the "Disconnect" words are there and functional.) 4. see that the signal strength is apparantly empty on the applet icon. (Yet the signal strength is actually quit strong.) My hardware is the following: 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) 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 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Fri Nov 9 11:55:01 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2010-05-18 (906 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) IpRoute: default via 142.157.166.1 dev wlan0 proto static 142.157.166.0/23 dev wlan0 proto kernel scope link src 142.157.167.35 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-30 (10 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH BC:0D:A5:38:6E:92 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/2 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.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1077079/+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 1077523] Re: Fails to connect to Wi-Fi several times after resume from suspend -- Ralink RT3090 rt2800pci
** Summary changed: - fails to connect to wifi for a while after suspend + Fails to connect to Wi-Fi several times after resume from suspend -- Ralink RT3090 rt2800pci -- 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/1077523 Title: Fails to connect to Wi-Fi several times after resume from suspend -- Ralink RT3090 rt2800pci Status in “network-manager” package in Ubuntu: New Bug description: After wake-up from suspend, I'm not connected automatically to wlan. Network-manager does automatically attempt to connect but I get a password dialog (containing the correct password). Upon confirmation it retries, fails after ~8 s, and shows dialog again. By 3-5 retries it will succeed. I'm on Quantal on a Lenovo S205. In Precise I didn't have this problem. Nothing has been changed in the wlan configuration. 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 x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CRDA: country GB: (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 Date: Sun Nov 11 01:03:17 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-04-27 (197 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) 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.105 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-10-25 (16 days ago) WifiSyslog: Nov 11 00:55:52 hemul wpa_supplicant[1142]: wlan0: WPA: Group rekeying completed with 1c:af:f7:2c:06:e8 [GTK=TKIP] 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.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1077523/+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 1078050] Re: Wireless network not working after resume from suspend -- Intel Centrino Advanced-N 6235 iwlwifi
Possibly a driver issue. ** Summary changed: - Wireless network stopped working after resume from suspend + Wireless network not working after resume from suspend -- Intel Centrino Advanced-N 6235 iwlwifi ** 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/1078050 Title: Wireless network not working after resume from suspend -- Intel Centrino Advanced-N 6235 iwlwifi Status in “linux” package in Ubuntu: Incomplete Bug description: Resumed the computer from suspend. The wireless network icon indicated a connection, but could not connect anywhere. Disabling & re-enabling wireless or restarting network-manager service did not help either. Could be a bug in wireless driver though... ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 Uname: Linux 3.2.33-030233-generic x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 CheckboxSubmission: 0d5c27421b37576825ce8be42984af2d CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a Date: Mon Nov 12 19:47:22 2012 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) IpRoute: default via 192.168.10.1 dev wlan0 proto static 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.105 metric 2 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-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/ubuntu/+source/linux/+bug/1078050/+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 1077571] Re: Unknown username "dnsmasq" in message bus configuration file
I see this too. Looking at the logs on my machine I see that the message is printed once or twice per day. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed ** Summary changed: - Unknown username "dnsmasq" in message bus configuration file + Message in /var/log/upstart/dbus.log: 'Unknown username "dnsmasq" in message bus configuration file' -- 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/1077571 Title: Message in /var/log/upstart/dbus.log: 'Unknown username "dnsmasq" in message bus configuration file' Status in “network-manager” package in Ubuntu: Confirmed Bug description: Get that error logged inside /var/log/upstart/dbus.log ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.7.0-0.5-generic 3.7.0-rc4 Uname: Linux 3.7.0-0-generic i686 ApportVersion: 2.6.2-0ubuntu3 Architecture: i386 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sun Nov 11 08:10:33 2012 IpRoute: default via 192.168.1.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no 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: WpaSupplicantLog: nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Connexion filaire 2 f023ceed-00a1-404d-ac10-3211d2834dcc 802-3-ethernet1352614380 dim. 11 nov. 2012 07:13:00 CET yes no /org/freedesktop/NetworkManager/Settings/1 Connexion filaire 1 72df9ef1-ebe6-4b11-8f73-40f25abdf859 802-3-ethernet1352617679 dim. 11 nov. 2012 08:07:59 CET yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetunavailable /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 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1077571/+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 1102092] Re: network-manager: pkla file missing -- Connecting to a wifi network requires org.freedesktop.NM.settings.modify.system privileges
** Summary changed: - network-manager: Connecting to a wifi network requires org.freedesktop.NM.settings.modify.system privileges + network-manager: pkla file missing -- Connecting to a wifi network requires org.freedesktop.NM.settings.modify.system privileges -- 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/1102092 Title: network-manager: pkla file missing -- Connecting to a wifi network requires org.freedesktop.NM.settings.modify.system privileges Status in “network-manager” package in Ubuntu: New Status in “network-manager” package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/642136: Package: network-manager Version: 0.9.0-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Since NetworkManager 0.9, a simple user is not allowed to connect to some wireless network unless it is granted (through policy kit or appropriate permissions) org.freedesktop.NetworkManager.settings.modify.system. This permission allows to alter existing connections as well. An active user should be authorized to use any wireless network if he wants to by default (like in previous versions). Or it should be possible to configure network manager to allow users to connect to wireless networks without enabling them to modify other system settings. - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager depends on: ii adduser3.113 ii dbus 1.4.14-1 ii isc-dhcp-client4.1.1-P1-17 ii libc6 2.13-21 ii libdbus-1-31.4.14-1 ii libdbus-glib-1-2 0.94-4 ii libgcrypt111.5.0-3 ii libglib2.0-0 2.28.6-1 ii libgnutls262.12.10-2 ii libgudev-1.0-0 172-1 ii libnl1 1.1-7 ii libnm-glib40.9.0-2 ii libnm-util20.9.0-2 ii libpolkit-gobject-1-0 0.102-1 ii libuuid1 2.19.1-5 ii lsb-base 3.2-28 ii udev 172-1 ii wpasupplicant 0.7.3-3.1 Versions of packages network-manager recommends: ii dnsmasq-base 2.58-3 ii iptables 1.4.12-1 ii modemmanager 0.5-1 ii policykit-1 0.102-1 ii ppp 2.4.5-5 Versions of packages network-manager suggests: pn avahi-autoipd - -- Configuration Files: /etc/NetworkManager/NetworkManager.conf changed: [main] plugins=ifupdown,keyfile no-auto-default=60:eb:69:ce:6e:a0, [ifupdown] managed=false - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk53hrAACgkQKFvXofIqeU7MZgCfUhWv55uMe7XwAloAlsV5luLq fI8AnRgNNKT/2gFxN/zbNdDvO/wDPOCf =PlLS -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1102092/+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 1101825] Re: IPv6 static default route added incorrectly by network-manager
** Also affects: network-manager via https://bugzilla.gnome.org/show_bug.cgi?id=692279 Importance: Unknown Status: Unknown -- 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/1101825 Title: IPv6 static default route added incorrectly by network-manager Status in NetworkManager: Unknown Status in “network-manager” package in Ubuntu: New Bug description: The relevant part of the IPv6 routing table looks like this: fe80::/64 dev wlan0 proto kernel metric 256 default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1 default via fe80::5054:ff:fe9c:741e dev wlan0 proto kernel metric 1024 expires 8sec default via fe80::5054:ff:fe64:aad0 dev wlan0 proto kernel metric 1024 expires 10sec I believe the proto static metric 1 route is an error, since it persists even when the router stops advertising. This breaks the IPv6 architecture for router redundancy. I am in control of this network and can alter router advertisement parameters if needed. 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-0ubuntu10 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sat Jan 19 10:47:05 2013 InstallationDate: Installed on 2012-11-15 (65 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) IpRoute: default via 192.168.4.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.64 metric 9 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) WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-25T12:30:38.408468 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.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1101825/+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 service stopped at boot
(For future reference) Reading the syslog I see 5 boots. 1. Jan 21 22:25:34 Kernel boots and dhclient starts and gets a reply. Seems that network- manager is not installed yet. 2. Jan 21 22:41:32 Kernel boots and dhclient starts but doesn't get a reply right away. Then there's a "NETDEV WATCHDOG: eth0 (sis900): transmit queue 0 timed out" warning. Then dhclient gets a reply. Then (immediately) NetworkManager starts and fails to configure wlan0, wlan1 and eth0. Interesting error message: b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found 3. Jan 21 23:42:29 Kernel boots and dhclient starts but doesn't get a reply . 4. Jan 22 09:03:43 Kernel boots and dhclient starts but doesn't get a reply . Then NetworkManager starts and configures wlan1 and later wlan0. 5. Jan 22 09:24:49 Ditto. -- 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 service stopped at boot 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 1103042] Re: network-manager service stopped at boot
Do you have connectivity on graphical login, just no indicator in the menu bar? -- 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 service stopped at boot 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 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
[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 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 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]: Starting VPN service 'vpnc'... NetworkManager[899]: VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 4760 NetworkManager[899]: VPN service 'vpnc' appeared; activating connections NetworkManager[899]: 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]: VPN plugin state changed: starting (3) NetworkManager[899]: VPN connection 'Synchronica' (Connect) reply received. NetworkManager[899]:SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/tun0, iface: tun0) NetworkManager[899]: VPN plugin failed: 1 NetworkManager[899]: VPN plugin state changed: stopped (6) NetworkManager[899]: VPN plugin state change reason: 0 NetworkManager[899]: error disconnecting VPN: Could not process the request because no VPN connection was active. NetworkManager[899]: Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS. Jan 21 10:48:22 Myriad-HP-EliteBook-8460p NetworkManager[899]: 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 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]: DNS: starting dnsmasq... Jan 18 23:12:50 samsung NetworkManager[987]: [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]: [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]: DNS: plugin dnsmasq update failed Jan 18 23:12:50 samsung NetworkManager[987]: ((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= 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= 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 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 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting
> the current default installation wherein network-manager starts > an instance of dnsmasq to act as a DHCP, DNS and TFTP server. NetworkManager starts an instance of dnsmasq to act only as a non- caching DNS nameserver forwarder. This instance listens only on the loopback interface 127.0.1.1. If your client is DHCPing with a dnsmasq instance on an Ubuntu server then that dnsmasq instance is most probably a "standalone" instance, configured by means of files included in the "dnsmasq" package (not to be confused with the "dnsmasq-base" package which contains little more than the dnsmasq binary and which both the dnsmasq package and the network-manager package depend on) and started by an initscript, not by NetworkManager. In reading further into your text my understanding is hampered by the fact that I am not entirely sure which machine you are referring to at different points in your text. > The problem is that the LTSP client, after successfully getting > DHCP assignments, fails to download the pxelinux boot image. > It reports "PXE-E32: TFTP open timeout." > To be more specific on the DHCP assignments, it identifies > my hardware router as the DHCP server and the default gateway. > It identifies the LTSP server as proxy and boot server. Is your LTSP server running Ubuntu and standalone dnsmasq? Then shouldn't the client use your LTSP server as the DHCP server? > So dnsmasq is not binding to my server IP during boot. > If I remove /etc/dnsmasq.d/network-manager > (which issues the sole dnsmasq directive to bind all the > interfaces instead of listening on 0.0.0.0) and restart the > server it allows the client to boot normally. I think I know what is happening. The network-manager package causes (by means of the /etc/dnsmasq.d/network-manager file) the standalone dnsmasq to start in "bind-interfaces" mode. In that mode dnsmasq doesn't listen on the wildcard IP address; it only listens on the addresses assigned to interfaces that are up when it (dnsmasq) starts. At boot, dnsmasq starts before the external interface is configured via DHCP, so dnsmasq doesn't listen on the external interface. If dnsmasq is restarted after the external interface is configured then dnsmasq listens on that interface too. If you remove /etc/dnsmasq.d/network-manager then standalone dnsmasq listens on the wildcard address when it starts and all is well except that now standalone dnsmasq conflicts with the NetworkManager-controlled dnsmasq instance. To fix this you have to disable the latter. Edit /etc/NetworkManager/NetworkManager.conf and comment out the line "dns=dnsmasq": put a '#' at the beginning of the line. In the future we hope that standalone dnsmasq running in bind-interfaces mode will be enhanced such that it listens on interfaces that are brought up after it (dnsmasq) starts. The author of dnsmasq, Simon Kelley, has already implemented this enhancement experimentally. Once that work is done it will be possible to run dnsmasq in bind-interfaces mode without causing the problem that you ran into. -- 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: Fix Released 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 1083111] Re: network-manager doesn't configure DNS properly and name resolution fails
> In my network dnsmasq should not try to connect directly > to the DNS root servers(which it looks like it does), It doesn't. Dnsmasq only ever forwards DNS requests to other nameservers which can do iterative queries. > But there is nothing telling it to use them, since both > /var/run/nm-dns-dnsmasq.conf and > /etc/NetworkManager/dnsmasq.d (which dnsmasq > is set to use when started by network-manager) > are empty. You can't go by those files. In Quantal, NM sends nameserver addresses to dnsmasq via D-Bus. How to see what NM has told dnsmasq: nmcli -f IP4 dev list | grep DNS > but resolvconf just won't use them, since it keeps > getting localhost from /run/resolvconf/interface/lo.dnsmasq. The latter file is created by the standalone dnsmasq server. When the latter is started with its initscript, the initscript registers the address 127.0.0.1 with resolvconf. If all is well then the standalone dnsmasq server instance uses the NM-controlled dnsmasq instance as its sole upstream nameserver, but perhaps this isn't happening in your case because of some some misconfiguration. If you don't want to use the standalone dnsmasq server then it's best to purge the "dnsmasq" package. Leave the "dnsmasq-base" package installed: it includes the dnsmasq binary which is used both by NetworkManager and by the "dnsmasq" package. ** Project changed: network-manager => network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Status: New => Incomplete ** Tags added: 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/1083111 Title: network-manager doesn't configure DNS properly and name resolution fails Status in “network-manager” package in Ubuntu: Incomplete Bug description: My network is configured in such a way that I can only exit through a HTTP proxy and the this it is set with proxy.pac so for getting the proxy configuration I also need the DNS to work... When using dnsmasq for DNS, dnsmasq is getting started by network- manager, /etc/resolv.conf is pointing to localhost, but dnsmasq is unable to resolv any DNS names. In my network dnsmasq should not try to connect directly to the DNS root servers(which it looks like it does), but it should just use the DNS servers I get through DHCP. But there is nothing telling it to use them, since both /var/run/nm-dns- dnsmasq.conf and /etc/NetworkManager/dnsmasq.d (which dnsmasq is set to use when started by network-manager) are empty. -when not using dnsmasq for DNS in network-manager, I get the right DNS servers set inside /run/resolvconf/interface/NetworkManager, but resolvconf just won't use them, since it keeps getting localhost from /run/resolvconf/interface/lo.dnsmasq. The problem goes away after removing this file and restarting resolvconf. I think the problem can be worked around in two ways: -if using dnsmasq, network-manager should configure the reachable name servers in /etc/NetworkManager/dnsmasq.d -if using just resolvconf, /run/resolvconf/interface/lo.dnsmasq should not be created. Ubuntu version: 12.10 network-manager version: 0.9.6.0-0ubuntu7 expected results: DNS resolution should work current status: DNS resolution does not work unless I do a workaround each time I connect to the network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1083111/+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 1083111] Re: network-manager doesn't configure DNS properly and name resolution fails
By the way... You wrote: > [...]from /run/resolvconf/interface/lo.dnsmasq. The problem > goes away after removing this file and restarting resolvconf If you change something in resolvconf's database then don't restart resolvconf; just do "sudo resolvconf -u". -- 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/1083111 Title: network-manager doesn't configure DNS properly and name resolution fails Status in “network-manager” package in Ubuntu: Incomplete Bug description: My network is configured in such a way that I can only exit through a HTTP proxy and the this it is set with proxy.pac so for getting the proxy configuration I also need the DNS to work... When using dnsmasq for DNS, dnsmasq is getting started by network- manager, /etc/resolv.conf is pointing to localhost, but dnsmasq is unable to resolv any DNS names. In my network dnsmasq should not try to connect directly to the DNS root servers(which it looks like it does), but it should just use the DNS servers I get through DHCP. But there is nothing telling it to use them, since both /var/run/nm-dns- dnsmasq.conf and /etc/NetworkManager/dnsmasq.d (which dnsmasq is set to use when started by network-manager) are empty. -when not using dnsmasq for DNS in network-manager, I get the right DNS servers set inside /run/resolvconf/interface/NetworkManager, but resolvconf just won't use them, since it keeps getting localhost from /run/resolvconf/interface/lo.dnsmasq. The problem goes away after removing this file and restarting resolvconf. I think the problem can be worked around in two ways: -if using dnsmasq, network-manager should configure the reachable name servers in /etc/NetworkManager/dnsmasq.d -if using just resolvconf, /run/resolvconf/interface/lo.dnsmasq should not be created. Ubuntu version: 12.10 network-manager version: 0.9.6.0-0ubuntu7 expected results: DNS resolution should work current status: DNS resolution does not work unless I do a workaround each time I connect to the network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1083111/+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
> the LTSP server defers to the router handling DHCP. OK, I get it. > I don't understand what you said about standalone dnsmasq > conflicting with network-manager's instance of dnsmasq > when /etc/dnsmasq.d/network-manager is removed. When /etc/dnsmasq.d/network-manager is present, standalone dnsmasq starts in bind-interfaces mode and only listens on the addresses assigned to configured network interfaces. This does not include 127.0.1.1, since 127.0.1.1 is not the address of any configured interface. So in this mode standalone dnsmasq does not conflict with NM- dnsmasq which listens on 127.0.1.1. (At most one process can listen on any given address:port combination.) Remove that file and standalone dnsmasq starts in a mode where it tries to listen at all addresses. But it can't do this if NM-dnsmasq is already listening at some address. > Should this conflict be manifesting itself somehow? > Everything seems to be working right now. Well, I am not sure which workaround, if any, you are currently relying on. If you commented out "dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf then there is no conflict because NM doesn't start the NM-dnsmasq process. > And would disabling network-manager's DNS-handling > instance of dnsmasq then result in the need to set up > an alternative DNS handler? No. If NM-dnsmasq is enabled then resolv.conf contains "nameserver 127.0.1.1" so that applications using the resolver library access NM- dnsmasq; NM-dnsmasq forwards queries to the upstream nameserver at the address A.A.A.A which was obtained via DHCP or otherwise. If NM-dnsmasq is disabled then resolv.conf simply contains "nameserver A.A.A.A". > I'm willing to apply another solution blindly, as I did > in removing /etc/dnsmasq.d/network-manager, > but it would be nice to understand more about it. If you are running Ubuntu 12.04 then the best solution for now is to * comment out the "bind-interfaces" line in /etc/dnsmasq.d/network-manager; * comment out the "dns=dnsmasq" line in /etc/NetworkManager/NetworkManager.conf. If you are running Ubuntu 12.10 and have dnsmasq version 2.63-1ubuntu1 then you can, instead, * replace the "bind-interfaces" line in /etc/dnsmasq.d/network-manager with a "bind-dynamic" line. The "bind-dynamic" mode is the new mode that I referred to above and which Simon referred to earlier in comment #94. Please test it! If it works well then it should become the default, as mentioned above in comments ##99, 102. -- 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: Fix Released 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 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting
Question: Why did everything work on your machine when standalone dnsmasq wasn't in bind-interfaces mode but /etc/NM/NM.conf contained "dns=dnsmasq"? Hypothesis: Standalone dnsmasq started first; network-manager second. NM tried to start NM-dnsmasq but this failed because of the address conflict and NM fell back to non-dnsmasq mode, which works fine. If this hypothesis is correct then there may be lines in the syslog that look like this: [date] [hostname] NetworkManager[pid]: DNS: starting dnsmasq... [date] [hostname] dnsmasq[pid]: 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/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: Fix Released 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 1042233] Re: NM DSL connection: DNS server addresses not added to resolv.conf
Ron: You report that manually-added-in-NetworkManager DNS search domain names are not added to resolv.conf. Can you please give step-by-step instructions for reproducing this bug (as Uqbar did)? Also, please post the output of this command: ls -l /etc/resolv.conf ** 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/1042233 Title: NM DSL connection: DNS server addresses not added to resolv.conf Status in “network-manager” package in Ubuntu: Incomplete Bug description: How to trigger (I used KDE widget) 1. Select Network Manager Settings 2. Select DSL tab 3. Select "Add ... +" button 4. Select "System connection" 5. Select IPv4 address 6. Select method: Automatic (address only) 7. In DNS servers add your own DNS server (I used 8.8.8.8; 8.8.4.4) 8. Click on OK 9. From a terminal, as root, type: "sudo vi /etc/NetworkManager/system-connections/New\ DSL\ connection \ connection" (or whater is in your language). 10. Check in the IPv4 stanza that the configuration is the same as above 11. Enable the DSL conection from the widget. 12. From a terminal type " cat /etc/resolv.conf" and see that the DNSs are not the ones specified in step #7. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CRDA: Error: [Errno 2] File o directory non esistente Date: Mon Aug 27 15:21:36 2012 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120424) IpRoute: default via 151.6.169.72 dev ppp0 proto static 151.6.169.72 dev ppp0 proto kernel scope link src 151.75.205.26 169.254.0.0/16 dev ppp0 scope link metric 1000 IwConfig: ppp0 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-07-09T21:19:25.556916 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Nuova connessione DSL beffe487-f324-4584-8160-5574dcd541ba pppoe 1346073509 lun 27 ago 2012 15:18:29 CEST yes no /org/freedesktop/NetworkManager/Settings/1 Wired Default d1a1bd2d-e077-4b4f-aafd-fffe09d19f86 802-3-ethernet1346010011 dom 26 ago 2012 21:40:11 CEST 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/+bug/1042233/+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 1042233] Re: NM DSL connection: DNS server addresses not added to resolv.conf
What was originally reported is expected behavior. NetworkManager starts a dnsmasq process to forward DNS queries. NM puts (via resolvconf) "nameserver 127.0.0.1" in resolv.conf and sends the upstream nameserver addresses to the dnsmasq process over D-Bus. On the other hand, if DNS search domain names are not included in resolv.conf (as Ron just reported) then that *is* a bug. ** Changed in: network-manager (Ubuntu) Status: Confirmed => 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/1042233 Title: NM DSL connection: DNS server addresses not added to resolv.conf Status in “network-manager” package in Ubuntu: Incomplete Bug description: How to trigger (I used KDE widget) 1. Select Network Manager Settings 2. Select DSL tab 3. Select "Add ... +" button 4. Select "System connection" 5. Select IPv4 address 6. Select method: Automatic (address only) 7. In DNS servers add your own DNS server (I used 8.8.8.8; 8.8.4.4) 8. Click on OK 9. From a terminal, as root, type: "sudo vi /etc/NetworkManager/system-connections/New\ DSL\ connection \ connection" (or whater is in your language). 10. Check in the IPv4 stanza that the configuration is the same as above 11. Enable the DSL conection from the widget. 12. From a terminal type " cat /etc/resolv.conf" and see that the DNSs are not the ones specified in step #7. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CRDA: Error: [Errno 2] File o directory non esistente Date: Mon Aug 27 15:21:36 2012 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120424) IpRoute: default via 151.6.169.72 dev ppp0 proto static 151.6.169.72 dev ppp0 proto kernel scope link src 151.75.205.26 169.254.0.0/16 dev ppp0 scope link metric 1000 IwConfig: ppp0 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-07-09T21:19:25.556916 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Nuova connessione DSL beffe487-f324-4584-8160-5574dcd541ba pppoe 1346073509 lun 27 ago 2012 15:18:29 CEST yes no /org/freedesktop/NetworkManager/Settings/1 Wired Default d1a1bd2d-e077-4b4f-aafd-fffe09d19f86 802-3-ethernet1346010011 dom 26 ago 2012 21:40:11 CEST 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/+bug/1042233/+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
That the last syslog entries are made by ntpd doesn't necessarily mean that the machine is hanging because of ntpd. It could be hanging at the next step, for example. Bug #999725 reports that ntp doesn't work properly when it is started before NIS, which is not to be confused with DNS. Probably not related. Unfortunately I don't have any idea why the second client hangs whereas the first one doesn't. -- 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: Fix Released 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 1085706] [NEW] gnome-screensaver-dialog: pam_ecryptfs: seteuid error
Public bug reported: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected quantal running-unity ** Package changed: ecryptfs-utils (Ubuntu) => gnome-screensaver (Ubuntu) ** Tags added: apport-collected quantal running-unity ** Description changed: I get this error message in the syslog when I authenticate succesfully in the screensaver. Ubuntu 12.10. + --- + ApportVersion: 2.6.1-0ubuntu6 + Architecture: amd64 + DistroRelease: Ubuntu 12.10 + EcryptfsInUse: Yes + GnomeSessionIdleInhibited: No + GnomeSessionInhibitors: None + GsettingsGnomeSession: + org.gnome.desktop.session idle-delay uint32 600 + org.gnome.desktop.session session-name 'ubuntu' + InstallationDate: Installed on 2012-06-13 (172 days ago) + InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) + MarkForUpload: True + Package: gnome-screensaver 3.6.0-0ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 + Tags: quantal running-unity + Uname: Linux 3.5.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error Status in “gnome-screensaver” package in Ubuntu: New Bug description: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+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 1085706] GsettingsGnomePowerManager.txt
apport information ** Attachment added: "GsettingsGnomePowerManager.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449987/+files/GsettingsGnomePowerManager.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error Status in “gnome-screensaver” package in Ubuntu: New Bug description: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+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 1085706] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449990/+files/XorgLogOld.txt ** Description changed: I get this error message in the syslog when I authenticate succesfully in the screensaver. - Ubuntu 12.10. - --- + --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: - org.gnome.desktop.session idle-delay uint32 600 - org.gnome.desktop.session session-name 'ubuntu' + org.gnome.desktop.session idle-delay uint32 600 + org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error Status in “gnome-screensaver” package in Ubuntu: New Bug description: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+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 1085706] GsettingsGnomeScreensaver.txt
apport information ** Attachment added: "GsettingsGnomeScreensaver.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449988/+files/GsettingsGnomeScreensaver.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error Status in “gnome-screensaver” package in Ubuntu: New Bug description: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+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 1085706] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449985/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error Status in “gnome-screensaver” package in Ubuntu: New Bug description: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+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 1085706] GsettingsGnomeLockdown.txt
apport information ** Attachment added: "GsettingsGnomeLockdown.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449986/+files/GsettingsGnomeLockdown.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error Status in “gnome-screensaver” package in Ubuntu: New Bug description: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+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 1085706] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449989/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error Status in “gnome-screensaver” package in Ubuntu: New Bug description: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+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
>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 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= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + 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.
[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= 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]: 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]: (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]: 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 initi
[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]: (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]: (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= 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= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Tags: quantal running-unity
[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= 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= 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 NET-ENA
[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 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. 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 -- 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 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 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 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
