[Touch-packages] [Bug 1651799] Re: /sbin/wpa_supplicant:11:p2p_group_assoc_resp_ie:send_assoc_resp:handle_assoc:ieee802_11_mgmt:ap_mgmt_rx

[Aron Xu]

** Changed in: wpa (Ubuntu)
 Assignee: Aron Xu (happyaron) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1651799

Title:
  
/sbin/wpa_supplicant:11:p2p_group_assoc_resp_ie:send_assoc_resp:handle_assoc:ieee802_11_mgmt:ap_mgmt_rx

Status in wpa package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
wpa.  This problem was most recently seen with package version 2.4-0ubuntu8, 
the problem page at 
https://errors.ubuntu.com/problem/bc564179f462736692df400cd76ad669355cff07 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1651799/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Aron Xu]

** Changed in: network-manager (Ubuntu)
 Assignee: Aron Xu (happyaron) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1633874

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1598051] Re: /usr/sbin/NetworkManager:11:_cancel_activation:_set_state_full:dhcp4_state_changed:ffi_call_unix64:ffi_call

[Aron Xu]

** Changed in: network-manager (Ubuntu)
 Assignee: Aron Xu (happyaron) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1598051

Title:
  
/usr/sbin/NetworkManager:11:_cancel_activation:_set_state_full:dhcp4_state_changed:ffi_call_unix64:ffi_call

Status in NetworkManager:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.2.0-0ubuntu0.16.04.2, the problem page at
  https://errors.ubuntu.com/problem/678c30fda8966b4a1ba01fd02d8c96821a408a95
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1598051/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1390623] Re: VPN with IPv6 connectivity but no IPv6 DNS server results in broken DNS config

[Aron Xu]

** Changed in: network-manager-openvpn (Ubuntu)
 Assignee: Aron Xu (happyaron) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1390623

Title:
  VPN with IPv6 connectivity but no IPv6 DNS server results in broken
  DNS config

Status in NetworkManager-OpenVPN:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  In Progress

Bug description:
  When connecting to a VPN that provides both a default route over IPv4
  and IPv6, but only DNS servers over IPv4, you can end up with the IPv4
  DNS servers set up as "split DNS". When that happens, the user is left
  without a working DNS configuration.

  See the attached log file for an example.

  I think the cause is that the patch for avoiding split DNS on VPNs
  with default routes[1] stops looking when it finds the first VPN
  configuration with a default route. If that configuration happens to
  be the IPv6-side of the VPN connection, then it will still add the
  IPv4 configuration with split DNS.

  A workaround is to simply add a IPv6 DNS server to the configuration
  in addition to the IPv4 DNS servers. In that case, the IPv6 DNS server
  is added without split DNS.

  This has been tested with both Ubuntu 14.04 LTS and Xubuntu 14.04.

  Package versions (on Xubuntu 14.04):
   network-manager 0.9.8.8-0ubuntu7
   network-manager-openvpn 0.9.8.2-1ubuntu4
   openvpn 2.3.2-7ubuntu3

  [1] http://bazaar.launchpad.net/~network-manager/network-
  manager/ubuntu/view/head:/debian/patches/dnsmasq-vpn-dns-
  filtering.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1390623/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1598055] Re: /usr/sbin/NetworkManager:11:act_stage2_config:activate_stage2_device_config:activation_source_handle_cb:activation_source_handle_cb4:g_main_dispatch

[Aron Xu]

** Changed in: network-manager (Ubuntu)
 Assignee: Aron Xu (happyaron) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1598055

Title:
  
/usr/sbin/NetworkManager:11:act_stage2_config:activate_stage2_device_config:activation_source_handle_cb:activation_source_handle_cb4:g_main_dispatch

Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.2.0-0ubuntu0.16.04.2, the problem page at
  https://errors.ubuntu.com/problem/34f383d56de666d32da07d12436db8493e077f37
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1598055/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1603898] Re: DNS resolution fails when using VPN and routing all traffic over it

[Aron Xu]

*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1603898

Title:
  DNS resolution fails when using VPN and routing all traffic over it

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  Confirmed

Bug description:
  When using our company VPN, the Network Manager configured dnsmasq
  ends up in a weird state where its unable to answer queries because
  it's (incorrectly) sending them to 127.0.0.1:53 where nothing is
  listening.

  | root@ornery:~# nmcli con show 'Canonical UK - All Traffic' | grep -i dns
  | ipv4.dns:
  | ipv4.dns-search:
  | ipv4.dns-options:   (default)
  | ipv4.ignore-auto-dns:   no
  | ipv6.dns:
  | ipv6.dns-search:
  | ipv6.dns-options:   (default)
  | ipv6.ignore-auto-dns:   no
  | IP4.DNS[1]: 10.172.192.1
  | root@ornery:~# ps auxfw | grep [4]035
  | nobody4035  0.0  0.0  52872  1620 ?SJun29   6:39  \_ 
/usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
  | root@ornery:~# 

  Querying the DNS server provided by the VPN connection works; querying
  dnsmasq doesn't:

  | root@ornery:~# dig +short @10.172.192.1 www.openbsd.org
  | 129.128.5.194
  | root@ornery:~# dig @127.0.1.1 www.openbsd.org
  | 
  | ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @127.0.1.1 www.openbsd.org
  | ; (1 server found)
  | ;; global options: +cmd
  | ;; Got answer:
  | ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 6996
  | ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
  | 
  | ;; QUESTION SECTION:
  | ;www.openbsd.org.   IN  A
  | 
  | ;; Query time: 0 msec
  | ;; SERVER: 127.0.1.1#53(127.0.1.1)
  | ;; WHEN: Mon Jul 18 10:25:48 CEST 2016
  | ;; MSG SIZE  rcvd: 33
  | 
  | root@ornery:~# 

  While running 'dig @127.0.1.1 www.openbsd.org':

  | root@ornery:~# tcpdump -i lo port 53 -v -n
  | tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 
bytes
  | 10:26:04.728905 IP (tos 0x0, ttl 64, id 56577, offset 0, flags [none], 
proto UDP (17), length 72)
  | 127.0.0.1.54917 > 127.0.1.1.53: 32273+ [1au] A? www.openbsd.org. (44)
  | 10:26:04.729001 IP (tos 0x0, ttl 64, id 49204, offset 0, flags [DF], proto 
UDP (17), length 61)
  | 127.0.1.1.53 > 127.0.0.1.54917: 32273 Refused$ 0/0/0 (33)

  | root@ornery:~# netstat -anp | grep 127.0.[01].1:53
  | tcp0  0 127.0.1.1:530.0.0.0:*   LISTEN  
4035/dnsmasq
  | udp0  0 127.0.1.1:530.0.0.0:*   
4035/dnsmasq
  | root@ornery:~# 

  You can see below a) that dnsmasq thinks it is configured to use a DNS
  server provided by the VPN, and/but that b) it tries to answer a non
  local query like www.openbsd.org locally.

  | root@ornery:~# kill -USR1 4035; tail /var/log/syslog | grep dnsmasq
  | Jul 18 09:29:22 ornery dnsmasq[4035]: time 1468830562
  | Jul 18 09:29:22 ornery dnsmasq[4035]: cache size 0, 0/0 cache insertions 
re-used unexpired cache entries.
  | Jul 18 09:29:22 ornery dnsmasq[4035]: queries forwarded 1880976, queries 
answered locally 375041
  | Jul 18 09:29:22 ornery dnsmasq[4035]: queries for authoritative zones 0
  | Jul 18 09:29:22 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 
792, retried or failed 0
  | root@ornery:~# dig +short @127.0.1.1 www.openbsd.org
  | root@ornery:~# kill -USR1 4035; tail /var/log/syslog | grep dnsmasq
  | Jul 18 09:29:22 ornery dnsmasq[4035]: queries for authoritative zones 0
  | Jul 18 09:29:22 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 
792, retried or failed 0
  | Jul 18 09:29:37 ornery dnsmasq[4035]: time 1468830577
  | Jul 18 09:29:37 ornery dnsmasq[4035]: cache size 0, 0/0 cache insertions 
re-used unexpired cache entries.
  | Jul 18 09:29:37 ornery dnsmasq[4035]: queries forwarded 1880976, queries 
answered locally 375042
  | Jul 18 09:29:37 ornery dnsmasq[4035]: queries for authoritative zones 0
  | Jul 18 09:29:37 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 
792, retried or failed 0
  | root@ornery:~# 

  This is on Ubuntu 16.04, with the following packages:

  | james@ornery:~$ COLUMNS=200 dpkg -l dnsmasq-base network-manager 
network-manager-openvpn | grep ^ii
  | ii  dnsmasq-base 2.75-1ubuntu0.16.04.1  
 amd64   

[Touch-packages] [Bug 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt

[Aron Xu]

*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1644098

Title:
  Network Manager + OpenVPN does not respond to DNS server change on
  second connection attempt

Status in dnsmasq:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Scenario:
  Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I 
only have the one computer to test with, the 16.10 is definitely relevant (I 
did not have this problem on 16.04)  but I can't tell if the upgrade is part of 
it,  (the upgrade may or may not be relevant).

  Have "full time"  wired or wireless connection  (does not matter which used)
  Part time OpenVPN connection set up via NetworkManager.

  Steps to reproduce
  1. Fresh boot
  2.  ping a device on the VPN network  (eg amachine.remotelan ) Result:  
"ping: amachine.remotelan: Name or service not known"
  3.  Connect to the VPN service via Network Manager.
  4. ping amachine.remotelan  -  result:
   PING amachine.remotelan (192.168.68.44) 56(84) bytes of data.
64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 
time=7.75 ms
  5.  Disconnect from the VPN service again.
ping result again "ping: amachine.remotelan: Name or service not known"

  6. Reconnect to the VPN again, and ping again

  Observed: 
 "ping: amachine.remotelan: Name or service not known"

However "ping 192.168.68.44"  responds successfully as expected

  Expected:
  PING ... 192.168 64 bytes from .. etc   to the ping by name

  ---
  Further info I'm going to add in a subsequent comment. (just annotating 
syslog right now!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dnsmasq/+bug/1644098/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

[Aron Xu]

*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1671606

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1671964] Re: DNS fails after reconnecting to a VPN

[Aron Xu]

*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

** This bug is no longer a duplicate of bug 1671606
   DNS server from vpn connection is not being used after network-manager 
upgrade to 1.2.6-0ubuntu0.16.04.1
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1671964

Title:
  DNS fails after reconnecting to a VPN

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since update 1.2.2-0ubuntu0.16.04.3 of network-manager, when I
  reconnect (i.e. connect, disconnect, connect) to a VPN (OpenVPN), DNS
  resolution stops working.

  Workaround: systemctl restart NetworkManager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671964/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1672491] Re: New NetworkManager breaks VPN DNS.

[Aron Xu]

*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

** This bug is no longer a duplicate of bug 1671606
   DNS server from vpn connection is not being used after network-manager 
upgrade to 1.2.6-0ubuntu0.16.04.1
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1672491

Title:
  New NetworkManager breaks VPN DNS.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Alright, this is going to be a frustrating bug for everyone involved I
  expect, but here goes.

  On Ubuntu 16.04, using a non-released VPN client (making this _much_
  harder for anyone to reproduce), upgrading the network-manager
  packages from 1.2.2-0ubuntu0.16.04.3 to 1.2.6-0ubuntu0.16.04.1 quite
  handily broke DNS over the VPN.

  And it broke it really oddly.

  dnsmasq binds to socket 12 for the new interface, just fine.

  strace shows that it does the sendto for the DNS request, and that the
  poll calls are working, just fine.

  tcpdump shows the response messages, they are coming back from the
  correct host and port, going to my IP and the port that dnsmasq is
  sending from.

  There are no iptables rules involved, nothing is set to deny.

  dnsmasq is never getting the response packet.

  The request thus times out.

  Doing a host or dig directly to the DNS server works just fine.

  And this is completely reproducible, and goes away the moment I
  downgrade back to 1.2.2-0ubuntu0.16.04.3.

  Was there some change to how network-manager handles VPN
  interfaces/tap0 in the new version?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1672491/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Aron Xu]

*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1675519

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1675519/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1675820] Re: Network manager fails to set domain server in some circumstances

[Aron Xu]

*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

** This bug is no longer a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1675820

Title:
  Network manager fails to set domain server in some circumstances

Status in network-manager package in Ubuntu:
  New

Bug description:
  Occasionally, after a resume from an update, network manager starts
  behaving strangely, not setting the DomainServer for the network.

  This happens when resuming the laptop to a location where:
  - an additional ethernet card (which is the one to use) is attached via USB
  - configuring that ethernet card NM is set up to clone a given mac address 
and get addresses only from dhcp, while the dns server is set manually in the 
network manager configuration
  - there are also free wifi signals to which NM tends to connect

  In this setup, NM fails to set the dns name in dnsmasq

  The issue gets worked around by either

  1) Using qdbus to call the dnsmasq dbus method to set the domain
  server. In this case the solution is temporary. Namely when NM is
  asked to disconnect from the net and then to reconnect, the issue
  comes again; or

  2) Killing dnsmasq. In this case, dnsmasq ia automatically restarted
  and everything starts working fine; or

  3) Restarting NM itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Mar 24 16:22:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1197 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 10.143.1.254 dev enx0050b61af5c1  proto static  metric 100 
   10.143.0.0/19 dev enx0050b61af5c1  proto kernel  scope link  src 
10.143.20.139  metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2017-01-10 (73 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675820/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1675353] Re: Network manager does not resolve dns names

[Aron Xu]

*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

** This bug is no longer a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1675353

Title:
  Network manager does not resolve dns names

Status in network-manager package in Ubuntu:
  New

Bug description:
  NM seems completely broken in 16.10.

  I use NM, wifi and several VPN connections.

  Expected behaviour:

  1. Connect NM to default wlan -> name resolution works without interuption 
and permanently
  2. Connection to Cisco Anyconnect (via openconnect) -> DNS servers sent via 
DHCP should be added to the resolver list, name resolution should work in 
destination network, routes adjusted accordingly
  3. Connect NM to foreign network (WPA2) -> DNS resolution sent via DHCP 
should be taken as default

  Current behaviour:

  NM starts dnsmasq by default (I commented the start line to fix
  issues). DNS resolution stops after some minutes.

  Removing dnsmasq fron NetworkManager.conf (as I did) allows for name
  resolution except for web browsers (neither Firefox nor Chromium use
  the systemd.resolver).

  5 minutes of inactivity on the network suffice for the name resolution
  to stop working. Have to reestablish network connection (sudo
  resolveconf -u does not work).

  This violates expectation 1

  NM connects via openconnect. In the settings I added additional DNS
  servers and domain searches. They are ignored by dnsmasq. Name
  resolution does not work.

  *Worksaround* -> enter IP-addresses in /etc/hosts.

  dig @server-ip returns the correct IP address for target services but
  Firefox and Chromium do not utilize these services. dnsmasq does not
  return the correct address.

  This violates expectation 2

  Entering a foreign but known network, DNS resolution stops after a
  while (5 minutes inactivity suffice).

  Summarizing:

  a. DNS resolution using VPN connections does not work (I use openvpn, 
openconnect and pptp).
  b. dnsmasq does not resolve dns names correctly in wlan situations
  c. dnsmasq conflicts with systemd.resolver
  d. Firefox and Chromium ignore systemd.resolver
  e. removing dnsmasq from NetworkManager.conf releaves the issue a little 
(resolution drop-outs do not occur so frequently)

  Comparison to plain Debian demonstrated that Debian does not start
  dnsmasq. This led to the elimination of my dns=dnsmaq line in
  NetworkManager.conf

  Comparison to Raspian demonstrated that Raspian uses wpa_supplicant to
  control dns name resolution. I have not tried this setup in Ubuntu
  yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Mar 23 11:28:21 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-27 (54 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 10.1.0.254 dev wlp4s0  proto static  metric 600 
   10.0.0.0/8 dev wlp4s0  proto kernel  scope link  src 10.1.0.168  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   172.16.199.0/24 dev vmnet8  proto kernel  scope link  src 172.16.199.1 
   192.168.31.0/24 dev vmnet1  proto kernel  scope link  src 192.168.31.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-03-23T11:24:00.888213
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
rsb_hs  7a8389dc-afd3-444b-a106-1974e9e74dff  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   vmnet1  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ---- 

   vmnet8  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ---- 

   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/3  --   
   ----
  

[Touch-packages] [Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

[Aron Xu]

Adding a network-manager task here to have it tracked because reports
flows in to the package a lot, but marking as invalid since the cause is
actually in dnsmasq.

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

** Changed in: network-manager (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: network-manager (Ubuntu Xenial)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1639776

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Committed
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1679928] Re: Dns lookups fail after going out of sleep mode

[Aron Xu]

*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

This is actually the same issue in Bug #1675519, even though the title
says different stuff, thus I'm marking it as duplicate.

** This bug has been marked a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing

** This bug is no longer a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1679928

Title:
  Dns lookups fail after going out of sleep mode

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04, 64bits, Dell XPS 15.

  When I wake up from sleep mode, I can no longer reach any domain by
  name, but still ping any IP address.

  Other users reported this problem here:
  http://askubuntu.com/questions/837575/dns-resolution-fails-after-
  wakeup-from-standby-ubuntu-16-10

  One of the proposed workaround is to disable dns caching by commenting
  out "dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf.

  Since dnsmasq is espacially useful when you use VPN, I must add I have
  openvpn setup on my machine so it could be part of the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1679928/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1680226] Re: Broken SplitDNS resolution in networ-manager VPN after disconnect and reconnect

[Aron Xu]

*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

** This bug has been marked a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing

** This bug is no longer a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1680226

Title:
  Broken SplitDNS resolution in networ-manager VPN after disconnect and
  reconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 16.04.2 LTS
  network-manager package version: 1.2.6-0ubuntu0.16.04.1

  I'm using Ubuntu Desktop 16.04 x64 and I have some VPN (OpenVPN and
  Cisco vpnc) connections defined. In all these connections I use both
  split tunnel and split dns.

  When I connect to a remote VPN server, my Ubuntu client correctly resolves 
DNS names in zones pushed by the remode server using the remote DNS server.
  For example: the remote VPN server pushes to the client "DNS resolver is 
192.168.10.1 for domain "vpndom.net"", then "host srv1.vpndom.net" is correctly 
resolved bu 192.168.10.1 and I get 192.168.10.7.

  After disconnecting and reconnecting to the VPN server, my Ubuntu
  client is no longer able to resolve DNS names in zones pushed by the
  VPN servers: "host srv1.vpndom.net" returns host not found.

  As a temporary solution, I downgraded netowrk manager to
  1.2.2-0ubuntu0.16.04.4 and all is working fine. So I think the problem
  is in network-manager 1.2.6-0ubuntu0.16.04.1

  As a workaround, with the connected VPN tunnel, I just "sudo killall
  dnsmasq": NetworkManager will then restart dnsmasq passing it all
  correct DNSes. There is no need to disconnect from the vpn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1680226/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Aron Xu]

*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

** Also affects: dnsmasq (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1675519

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1675519/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1669643] Re: Wifi WPA2-PSK 4-Way Handshake Faliure

[Aron Xu]

** Package changed: network-manager (Ubuntu) => wpa (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1669643

Title:
  Wifi WPA2-PSK 4-Way Handshake Faliure

Status in wpa package in Ubuntu:
  New

Bug description:
  After I upgraded to Ubuntu 17.04 yesterday, I started having this
  problem. My device will only connect to unsecured (public) WiFi
  networks. I tried booting into an older series kernel (4.8.0) and the
  issue persisted.

  I ran `sudo systemctl status network-manager` and got this:

  device (wlx501ac505fcbc): supplicant interface state: associating -> 4-way 
handshake
  sup-iface[0x55eb41e5bc20,wlx501ac505fcbc]: connection disconnected (reason 15)
  device (wlx501ac505fcbc): supplicant interface state: 4-way handshake -> 
disconnected
  device (wlx501ac505fcbc): Activation: (wifi) disconnected during association, 
asking for new key
  device (wlx501ac505fcbc): state change: config -> need-auth (reason 
'supplicant-disconnect') [50 60 8]
  device (wlx501ac505fcbc): supplicant interface state: disconnected -> inactive

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  2 20:55:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-04 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  IpRoute:
   default via 192.168.42.129 dev enp0s20u2 proto static metric 100 
   169.254.0.0/16 dev enp0s20u2 scope link metric 1000 
   192.168.42.0/24 dev enp0s20u2 proto kernel scope link src 192.168.42.246 
metric 100
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  ProcEnviron:
   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-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   enp0s20u2  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/4  Wired connection 1  
474aac38-e4d8-4102-b2eb-c5cc6bdb17aa  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   AC:37:43:7C:B4:57  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   wlx501ac505fcbcwifi  disconnected  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1669643/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1669758] Re: Centrino Wireless-N 1000 not working on 16.10

[Aron Xu]

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1669758

Title:
  Centrino Wireless-N 1000 not working on 16.10

Status in linux package in Ubuntu:
  New

Bug description:
  Summary
  Wifi is not working on Centrino Wireless-N 1000 not working on 16.10, but 
does work on windows.

  Please see following

  http://paste.ubuntu.com/24101344/
  
http://askubuntu.com/questions/887257/device-not-ready-wifi-not-working-on-ubuntu-16-10
  https://ubuntuforums.org/showthread.php?t=2354116=13615105#post13615105

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669758/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1585863

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project xenial series:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1664748] Re: wifi connection drops, reconnects every 10 minutes

[Aron Xu]

Hi Dustin,

I would like to know which version of Ubuntu are you running on your
laptop? Specifically, I want to know what's behaving as your dhcp
client, is it dhclient or systemd-networkd?

Requesting IP addresses from two interfaces on the same machine to one
DHCP server is sometimes causing trouble because in systemd-networkd it
sends Client-Identifier to the server (which is about your D-Bus
machine-id), and some DHCP server (as far as I know at least some
versions of ISC DHCP Server) will take Client-Identifier as precedence
over the interface mac address, thus generating IP address allocation
problem.

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1664748

Title:
  wifi connection drops, reconnects every 10 minutes

Status in maas package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I recently moved my home DHCP and DNS server over to MAAS (2.1.3 from
  xenial-updates).

  Since doing so, I've noticed that my wifi connection drops and
  reconnects (with corresponding Unity pop-up notifications) exactly
  every 10 minutes.

  I suppose this is due to the fact that MAAS sets DHCP leases to 10
  minutes by default?

  Has anyone else noticed this behavior?

  Is there a suitable workaround?  Increasing the DHCP lease time?
  Using static addresses?  Something else?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1664748/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1571882] Re: 5GHz Wi-Fi Intermittently Disconnects on Dell Latitude 3340

[Aron Xu]

This looks more likely to be a kernel (driver) issue, reassigning.

** Package changed: network-manager (Ubuntu) => linux-lts-wily (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1571882

Title:
  5GHz Wi-Fi Intermittently Disconnects on Dell Latitude 3340

Status in linux-lts-wily package in Ubuntu:
  New

Bug description:
  When connected to a 5GHz (802.11ac) WPA2 wireless network with UFW firewall 
enabled at system startup , I experience intermittent issues where the Wi-Fi 
completely disconnects and the 5G network is no longer displayed in the list of 
Wi-Fi Networks.
  Toggling the "Enable Wi-Fi" option resets the Wi-Fi and allows the user to 
reconnect.

  The latest A10 firmware version is installed on the laptop.

  I confirmed that the 5G network was still up and running , so the issue is 
most likely not on the router network end.
  I have no custom firewall rules that would cause this behaviour , but I do 
see a lot of multicast address resolution requests being blocked in the ufw 
logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-35-generic 4.2.0-35.40~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 18:32:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-03 (45 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-wily/+bug/1571882/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1675519] Re: Network Manager w/ dnsmasq Dies when VPN-ing

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1675519

Title:
  Network Manager w/ dnsmasq Dies when VPN-ing

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello.

  Within the past week or so, a new bug has cropped up on Network
  Manager on 16.04.

  When Network Manager on 16.04 is configured to use dnsmasq and not
  systemd-resolved, one is expecting VPN DNS servers to be properly set
  and dnsmasq to properly route DNS requests to the Internet.

  However, when connecting to my OpenVPN connection, dnsmasq now fails
  extremely hard and no longer replies or routes data for DNS requests
  properly.  This results in me having to use a fail-over workaround of
  enforcing resolvconf to use my local `bind9` instance on my own system
  for DNS, which is configured to route to Google for DNS requests.
  This, however, prohibits me from using my own DNS on my VPN connect,
  which are on the remote location and serve internal ranges and domains
  that I should be permitted to access.

  Given these issues, with `dnsmasq` just outright exploding in our
  faces and no longer being usable for DNS request routing over the VPN,
  I'm not even sure we can consider VPN DNS as a viable option anymore
  with 16.04.

  Note that this is only *very* recently a problem within the past few
  weeks, and I can't find any updates which would have impacted this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 23 14:04:06 2017
  InstallationDate: Installed on 2016-12-20 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675519/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1675353] Re: Network manager does not resolve dns names

[Aron Xu]

*** This bug is a duplicate of bug 1675519 ***
https://bugs.launchpad.net/bugs/1675519

** This bug has been marked a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1675353

Title:
  Network manager does not resolve dns names

Status in network-manager package in Ubuntu:
  New

Bug description:
  NM seems completely broken in 16.10.

  I use NM, wifi and several VPN connections.

  Expected behaviour:

  1. Connect NM to default wlan -> name resolution works without interuption 
and permanently
  2. Connection to Cisco Anyconnect (via openconnect) -> DNS servers sent via 
DHCP should be added to the resolver list, name resolution should work in 
destination network, routes adjusted accordingly
  3. Connect NM to foreign network (WPA2) -> DNS resolution sent via DHCP 
should be taken as default

  Current behaviour:

  NM starts dnsmasq by default (I commented the start line to fix
  issues). DNS resolution stops after some minutes.

  Removing dnsmasq fron NetworkManager.conf (as I did) allows for name
  resolution except for web browsers (neither Firefox nor Chromium use
  the systemd.resolver).

  5 minutes of inactivity on the network suffice for the name resolution
  to stop working. Have to reestablish network connection (sudo
  resolveconf -u does not work).

  This violates expectation 1

  NM connects via openconnect. In the settings I added additional DNS
  servers and domain searches. They are ignored by dnsmasq. Name
  resolution does not work.

  *Worksaround* -> enter IP-addresses in /etc/hosts.

  dig @server-ip returns the correct IP address for target services but
  Firefox and Chromium do not utilize these services. dnsmasq does not
  return the correct address.

  This violates expectation 2

  Entering a foreign but known network, DNS resolution stops after a
  while (5 minutes inactivity suffice).

  Summarizing:

  a. DNS resolution using VPN connections does not work (I use openvpn, 
openconnect and pptp).
  b. dnsmasq does not resolve dns names correctly in wlan situations
  c. dnsmasq conflicts with systemd.resolver
  d. Firefox and Chromium ignore systemd.resolver
  e. removing dnsmasq from NetworkManager.conf releaves the issue a little 
(resolution drop-outs do not occur so frequently)

  Comparison to plain Debian demonstrated that Debian does not start
  dnsmasq. This led to the elimination of my dns=dnsmaq line in
  NetworkManager.conf

  Comparison to Raspian demonstrated that Raspian uses wpa_supplicant to
  control dns name resolution. I have not tried this setup in Ubuntu
  yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Mar 23 11:28:21 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-27 (54 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 10.1.0.254 dev wlp4s0  proto static  metric 600 
   10.0.0.0/8 dev wlp4s0  proto kernel  scope link  src 10.1.0.168  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   172.16.199.0/24 dev vmnet8  proto kernel  scope link  src 172.16.199.1 
   192.168.31.0/24 dev vmnet1  proto kernel  scope link  src 192.168.31.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-03-23T11:24:00.888213
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
rsb_hs  7a8389dc-afd3-444b-a106-1974e9e74dff  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   vmnet1  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ---- 

   vmnet8  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ---- 

   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/3  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  

[Touch-packages] [Bug 1675820] Re: Network manager fails to set domain server in some circumstances

[Aron Xu]

*** This bug is a duplicate of bug 1675519 ***
https://bugs.launchpad.net/bugs/1675519

** This bug has been marked a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1675820

Title:
  Network manager fails to set domain server in some circumstances

Status in network-manager package in Ubuntu:
  New

Bug description:
  Occasionally, after a resume from an update, network manager starts
  behaving strangely, not setting the DomainServer for the network.

  This happens when resuming the laptop to a location where:
  - an additional ethernet card (which is the one to use) is attached via USB
  - configuring that ethernet card NM is set up to clone a given mac address 
and get addresses only from dhcp, while the dns server is set manually in the 
network manager configuration
  - there are also free wifi signals to which NM tends to connect

  In this setup, NM fails to set the dns name in dnsmasq

  The issue gets worked around by either

  1) Using qdbus to call the dnsmasq dbus method to set the domain
  server. In this case the solution is temporary. Namely when NM is
  asked to disconnect from the net and then to reconnect, the issue
  comes again; or

  2) Killing dnsmasq. In this case, dnsmasq ia automatically restarted
  and everything starts working fine; or

  3) Restarting NM itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Mar 24 16:22:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1197 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 10.143.1.254 dev enx0050b61af5c1  proto static  metric 100 
   10.143.0.0/19 dev enx0050b61af5c1  proto kernel  scope link  src 
10.143.20.139  metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2017-01-10 (73 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675820/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1613751

Title:
  journald forwards to syslog with facility=KERN on everything

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Confirmed

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1613751/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1675436] Re: After Security Updates PHP 7 Randomly stops resolving DNS

[Aron Xu]

** Package changed: network-manager (Ubuntu) => glibc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1675436

Title:
  After Security Updates PHP 7 Randomly stops resolving DNS

Status in glibc package in Ubuntu:
  New

Bug description:
  I think this is related to this

  https://people.canonical.com/~ubuntu-
  security/cve/2015/CVE-2015-5180.html

  I have 10 servers, randomly  one will start having this issue. it will
  be unable to resolve DNS. Curl will all of the sudden start reporting
  in newrelic about being unable to resolve host names, and it will
  throw SSL invalidation errors.

  restarting will fix the issue and it might be good for several more
  hours.

  I have spoken with rackspace techs and they reported to me that this
  was a bug related to ubuntu and a recent update so I thought I would
  reach out and see if there was any way I could help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1675436/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Aron Xu]

** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

  needed by:
  lp #1647283

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1667968] Re: Ubuntu 16.10 kernel 4.8.0-39 No network connectivity

[Aron Xu]

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1667968

Title:
  Ubuntu 16.10 kernel 4.8.0-39  No network connectivity

Status in linux package in Ubuntu:
  New

Bug description:
  My last kernel update changed something that is causing the network
  manager to fail to load anything but the lo device.

  If I reboot into the previous kernel (4.8.0-38) everything works fine.

  I'm not certain that this issue is related to the NetworkManger or the
  Kernel, but the bottom line is I have not ethernet when I boot using
  the latest kernel.

  This is one of three computers I built a few years back.
  It's based on an Asus motherboard: P5G41T-M LX PLUS, BIOS 050210/21/2011
  The eth0 NIC is on the motherboard.

  Any info you need, I will try and provide.
  Any help you might offer would be appreciated.

  I run apt-get update followed by apt-get dist-upgrade every day.
  This is the first time I've had a serious problem as a byproduct of updating.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667968/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Aron Xu]

I've walked through the tests I can do and the yakkety version works,
tagging  verification-done-yakkety.

** Tags added: verification-done-yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Aron Xu]

@cyphermox, most of the common cases are covered before I push changes
to the git repo. I've made some minor updates to
NetworkManager/DistroTesting page and let's continue use it for smoke
testing.

** Description changed:

  [Impact]
  
  This SRU would try to have the latest well-tested upstream point release
  (1.2.6) of 1.2.x land in Xenial, which is the successor of the current
  1.2.2 version, fixing quite some bugs that's suitable to land in the
  stable branch.
  
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2
  
  [Test Case]
  
  After installing the updated version, users should be able to avoid some
  mem leaks in some cases and have generally improved DNS related
  experiences.
  
+ Also, as this is a general point release update, cases described in
+ https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used for
+ smoke testing.
+ 
  [Regression Potential]
  
  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.
  
  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.
  
  Parallel building was enabled in xenial to keep the diff between xenial
  and yakkety minimal since they are basically in sync now. Parallel
  building was enabled in the yakkety package in May 2016 so it's been
  working fine for a while.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698

Title:
  [SRU] Upgrade network-manager to latest point release

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

[Aron Xu]

Can you provide your NetworkManager.conf as well as your
/etc/network/interface file? Normally these two files should look like
this:

1. NetworkManager.conf:
[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq

[ifupdown]
managed=false

2. interfaces:
auto lo
iface lo inet loopback

That is to say, have dnsmasq and ifupdown plugins enabled and set
[ifupdown] to "managed=false", at the same time don't include anything
other than "lo" in /etc/network/interfaces.

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1658921

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 997200] Re: Test for captive portal before putting applications in online mode

[Aron Xu]

Just did some testing with up-to-date 16.04 LTS:

1. Initial state:
Wi-Fi enabled, but not connected to any network; ethernet is unplugged.

$ nmcli general 
STATE CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
disconnected  none  enabled  enabled  enabled  enabled

2. Connect to a SSID that has captive portal:
$ nmcli general 
STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
connected  full  enabled  enabled  enabled  enabled

This means network-manager has put the state to connected and emits a
signal of full connectivity, which makes other applications "think" the
device is online with full access to the Internet.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/997200

Title:
  Test for captive portal before putting applications in online mode

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in update-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Precise:
  Won't Fix
Status in update-manager source package in Precise:
  Won't Fix
Status in network-manager source package in Quantal:
  Won't Fix
Status in update-manager source package in Quantal:
  Won't Fix
Status in network-manager source package in Raring:
  Won't Fix
Status in update-manager source package in Raring:
  Won't Fix

Bug description:
  When in a hotel there is a often a T page that is delivered when
  connecting to the network.  Some combination of network manager and
  update manager (or something else entirely) doesn't seem to be able to
  handle this, and update are left in a non-working state after not
  being able to read package headers file.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 17:27:02 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 10.155.32.1 dev wlan0  proto static 
   10.155.32.0/19 dev wlan0  proto kernel  scope link  src 10.155.38.82  metric 
2 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-03-07 (63 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.4.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/997200/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Aron Xu]

** Changed in: network-manager (Ubuntu Xenial)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698

Title:
  [SRU] Upgrade network-manager to latest point release

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Aron Xu]

@jbicha, would be great to make another new upload to zesty, I've
prepared an update of 1.4.4 in git repo:

https://code.launchpad.net/~network-manager/network-
manager/+git/ubuntu/+ref/master

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698

Title:
  [SRU] Upgrade network-manager to latest point release

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Triaged
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1656785] Re: nc -d -l does not return data (only empty strings)

[Aron Xu]

** Bug watch added: Debian Bug tracker #849192
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849192

** Also affects: netcat-openbsd (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849192
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu.
https://bugs.launchpad.net/bugs/1656785

Title:
  nc -d -l does not return data (only empty strings)

Status in netcat-openbsd package in Ubuntu:
  New
Status in netcat-openbsd package in Debian:
  Unknown

Bug description:
  The Zesty (17.04) version of nc (1.130-1ubuntu1) no longer returns the
  received data when using the '-d' (do not listen on stdin) flag
  together with the '-l' (listen on socket) flag. This used to work in
  previous releases (1.105-7ubuntu1 Trusty-Yakkety). In fact, in the
  previous version, the '-d' flag seems to be required to make the data
  transfer more reliable in scripts.

  Testcase: Attached script passes on older versions, fails with the
  current version of nc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1656785/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Aron Xu]

- d/rules: yes that helped a lot for testing

- commenting out patch: in xenial branch we haven't switched to gbp-pq
yet, and historically some patches were commented out when not used, and
I'm following it

- it was believed not useful during a bunch update of n-m 1.2 packages
(both debian and ubuntu), but later we switched back to hook up the
service in WantedBy=network-online.target dynamically. This change makes
it easier to disable the service and is what we have in yakkety, but the
change can be dropped if it's not appropriate for SRU.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698

Title:
  [SRU] Upgrade network-manager to latest point release

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Triaged
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Aron Xu]

@ubuntu-sponsor, please help sponsor the following branch xenial, which has 
been updated to 1.2.6 as well:
https://code.launchpad.net/~network-manager/network-manager/+git/ubuntu/+ref/xenial

** Description changed:

  [Impact]
  
  This SRU would try to have the latest well-tested upstream point release
- (1.2.4) of 1.2.x land in Xenial, which is the successor of the current
+ (1.2.6) of 1.2.x land in Xenial, which is the successor of the current
  1.2.2 version, fixing quite some bugs that's suitable to land in the
  stable branch.
  
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2
- 
- For xenial, we'll also backporting a patch from 1.2.6 that should fix a
- no-networking-after-resuming-from-sleep issue. This patch was applied to
- Debian testing and zesty in 1.4.2-3ubuntu1.
- 
- For yakkety, this is an update to 1.2.6. Once 1.2.6 has been in use for
- a while without new problems, we'll look into doing a separate SRU for
- Xenial.
  
  [Test Case]
  
  After installing the updated version, users should be able to avoid some
  mem leaks in some cases and have generally improved DNS related
  experiences.
  
  [Regression Potential]
  
- This version has been in yakkety for sometime, and there's no report of
- regressions until now.
+ This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
+ complete.

** Tags removed: verification-failed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698

Title:
  [SRU] Upgrade network-manager to latest point release

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Triaged
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

[Aron Xu]

Hi chih, the patch can't apply cleanly in nm-1.2, needs some porting.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647283

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  New
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION 
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged-- 

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1568829] Re: nm-applet icon not showing when /proc is mounted with hidepid!=0

[Aron Xu]

** Changed in: network-manager (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1568829

Title:
  nm-applet icon not showing when /proc is mounted with hidepid!=0

Status in Network Manager Applet:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  Steps to reproduce:

  1. (Re-)mount /proc with hidepid=1 (or =2)
  2. Restart nm-applet

  nm-applet's icon does not reappear after the restart. This used to
  work with version 1.0.

  
  Original bug description:

  Since I upgraded to -proposed network-manager and network-manager-gnome 
versions, nm-applet no longer works.
  Manually starting it on a console give:

  $ nm-applet

  (nm-applet:6250): nm-applet-WARNING **: 
GDBus.Error:org.freedesktop.NetworkManager.AgentManager.PermissionDenied: 
Unable to determine request sender and UID.
  (nm-applet:6250): libnm-CRITICAL **: nm_client_get_nm_running: assertion 
'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_get_state: assertion 
'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_networking_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_hardware_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_get_enabled: assertion 
'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_hardware_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_get_devices: assertion 
'NM_IS_CLIENT (client)' failed

  What's odd is the NM and NM-gnome base versions are not identical:

  $ apt-cache policy network-manager network-manager-gnome
  network-manager:
    Installed: 1.1.93-0ubuntu1
    Candidate: 1.1.93-0ubuntu1
    Version table:
   *** 1.1.93-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.4-0ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  network-manager-gnome:
    Installed: 1.1.93-1ubuntu1
    Candidate: 1.1.93-1ubuntu1
    Version table:
   *** 1.1.93-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.10-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.1.93-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 11 08:16:59 2016
  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-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 1:
   (process:7301): nmcli-CRITICAL **: Error: Could not create NMClient object: 
Unable to authenticate request..
  nmcli-dev:
   Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 1:
   (process:7297): nmcli-CRITICAL **: Error: Could not create NMClient object: 
Unable to authenticate request..
  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/network-manager-applet/+bug/1568829/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Aron Xu]

Mark as Fix Released in Zesty.

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698

Title:
  [SRU] Upgrade network-manager to latest point release

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Triaged
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.4) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  For xenial, we'll also backporting a patch from 1.2.6 that should fix
  a no-networking-after-resuming-from-sleep issue. This patch was
  applied to Debian testing and zesty in 1.4.2-3ubuntu1.

  For yakkety, this is an update to 1.2.6. Once 1.2.6 has been in use
  for a while without new problems, we'll look into doing a separate SRU
  for Xenial.

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This version has been in yakkety for sometime, and there's no report
  of regressions until now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Aron Xu]

** Tags added: nm-touch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Released
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1495453] Re: atk6-flood_router26 wlan0 makes network crash

[Aron Xu]

When you run atk6-flood_router26 it is supposed to crash your network,
not a bug in the system.

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1495453

Title:
  atk6-flood_router26 wlan0 makes network crash

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Install thc-ipv6 and do a sudo atk6-flood_router26 wlan0 (it was wireless 
network in my case) and the internet connection is lost. You can't access the 
web you can't ping or do anything on the world wide web. If you stop the 
operation (Ctrl + C) the state continues, so still nothing, only after manually 
connecting to the network will it work, and sometimes when trying to reconnect 
it will give me:
  Device disconnect failed. I'm using Ubuntu 15.04 64-bit.
  Neither should my internet access stop, or the network manager behave like 
that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1495453/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1484908] Re: autologin not working 15.10

[Aron Xu]

** Package changed: network-manager (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1484908

Title:
  autologin not working 15.10

Status in Ubuntu:
  Confirmed

Bug description:
  after one of the updates through the update manager, auto login no longer 
works.
  Ive tried disabling and re-enabling with no luck.

  Each time the system boots it now goes to the login screen, when it
  should go to the desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1484908/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

[Aron Xu]

** Tags added: nm-touch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1478319

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  current build number: 68
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-24 08:00:20
  version version: 68
  version ubuntu: 20150724
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  My ISP (Free in France) provides a hotspot service so that customers
  can use the connection of any other customer using a generic open Wifi
  connection (for reference http://www.free.fr/assistance/2303.html - in
  French)

  The SSID is called 'FreeWifi' on all the boxes but obviously APs are
  all different since it's customers' DSL routers.

  When I connect  to one of this access point, suspend the phone and
  resume it in another location where the SSID is available but from a
  different AP, the phone doesn't connect to this AP and the list of
  networks in the network-indicator doesn't refresh and still show the
  list of network from the previous location. I have to forget the
  network called 'FreeWifi' and reconnect in order to refresh the list
  and make it work.

  It's 100% reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1495735] Re: /usr/sbin/NetworkManager:11:nm_device_get_act_request:wifi_secrets_cb:get_secrets_cb:agent_secrets_done_cb:get_complete_cb

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1495735

Title:
  
/usr/sbin/NetworkManager:11:nm_device_get_act_request:wifi_secrets_cb:get_secrets_cb:agent_secrets_done_cb:get_complete_cb

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 0.9.10.0-4ubuntu15.2, the problem page at
  https://errors.ubuntu.com/problem/5eaf0f867af89007f24a1301a62ce28621fb09a8
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1495735/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1482636] Re: Ubuntu Touch on MX4 doesn't connect to WLAN with WEP

[Aron Xu]

** Tags added: nm-touch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1482636

Title:
  Ubuntu Touch on MX4 doesn't connect to WLAN with WEP

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  while it is no problme to connect to a WLAN with WPA2 it is impossible
  to connect with a WLAN with WEP. Given that I'm the admin of the WLAN
  I changed to WPA temporarily and then it was no problem to connect.
  Thus it is not a hardware problem.

  Regards

  Ubuntu Touch Ver.  15.04 (r3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1482636/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1496741] Re: NetworkManager crashed with SIGSEGV

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1496741

Title:
  NetworkManager crashed with SIGSEGV

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  It shows NetworkManager crashed when Ubuntu 15.10 started.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: i386
  Date: Thu Sep 17 01:22:05 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2011-12-01 (1385 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   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.13  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en
   PATH=(custom, no user)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SegvAnalysis:
   Segfault happened at: 0x80d83fc: mov(%eax),%eax
   PC (0x080d83fc) ok
   source "(%eax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: NetworkManager crashed with SIGSEGV
  UpgradeStatus: Upgraded to wily on 2015-08-12 (36 days ago)
  UserGroups:
   
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
vodafoneE509  af9db9ab-35e5-40d8-ac17-06a719f176f5  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   ttyACM0  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  
------  
   
   eth0 ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/1  
------  
   
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
------
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1496741/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1499739] Re: NetworkManager should check for Internet connection

[Aron Xu]

** Tags added: nm-touch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1499739

Title:
  NetworkManager should check for Internet connection

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  Have SIM with bad data plan.*
  Wi-FI OFF.
  Cellular data ON (and ofono reports Attached = 1)
  $ gdbus call -e -d com.ubuntu.connectivity1 -o 
/com/ubuntu/connectivity1/NetworkingStatus -m 
org.freedesktop.DBus.Properties.Get com.ubuntu.connectivity1.NetworkingStatus 
Status

  What happens
  (,) (NM_STATE_CONNECTED_GLOBAL) [1]

  What should happen:
  (,) (NM_STATE_DISCONNECTED) [1]

  This assumes that NetworkManager's State property definition of
  “Connected” is equal to “Connected to the Internet”. If it's not, then
  this needs to be resolved elsewhere.

  * Not sure what the exact definition of a bad data plan is, but assume
  “out of cash”, but ofono still attaches.

  [1] https://developer.gnome.org/NetworkManager/0.9/spec.html#type-
  NM_STATE

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1499739/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1495099] Re: g_type_instance_get_private: assertion 'instance != NULL && instance->g_class != NULL' failed

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1495099

Title:
  g_type_instance_get_private: assertion 'instance != NULL &&
  instance->g_class != NULL' failed

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  First, my usual network disappeared from the list, and I had to
  connect to another. It worked great, but I needed to communicate with
  a machine on the old network, so I replugged my USB WLAN adapter, and
  I could connect again. A few minutes later, network-manager crashed.
  The connection still works though.

  This seems to be the problem:

  Sep 12 16:58:19 zeus NetworkManager[751]: (NetworkManager:751): GLib-
  GObject-CRITICAL **: g_type_instance_get_private: assertion 'instance
  != NULL && instance->g_class != NULL' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Sep 12 17:01:51 2015
  IpRoute:
   default via 192.168.2.1 dev wlan0  proto static  metric 1024
   192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.109
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-19 (146 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-03-16T23:56:17.808964
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
9: Error: nmcli (0.9.10.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: 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/1495099/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1497975] Re: systemctl service NetworkManager reports GLib errors in status

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1497975

Title:
  systemctl service NetworkManager reports GLib errors in status

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Wily (packages updated today latest):

  Visual:
  nm-applet is not showing up
  network not configured

  background:
  sudo systemctl status network-manager -l

  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Mo 2015-09-21 14:07:47 CEST; 18s ago
   Main PID: 5605 (NetworkManager)
 CGroup: /system.slice/NetworkManager.service
 └─5605 /usr/sbin/NetworkManager --no-daemon

  Sep 21 14:07:47 myhost NetworkManager[5605]:   devices added (path: 
/sys/devices/virtual/net/lo, iface: lo)
  Sep 21 14:07:47 myhost NetworkManager[5605]:   device added (path: 
/sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
  Sep 21 14:07:47 myhost NetworkManager[5605]:   end _init.
  Sep 21 14:07:47 myhost NetworkManager[5605]:   Loaded settings plugin 
ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager 
mailing list. 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ifupdown.so)
  Sep 21 14:07:47 myhost NetworkManager[5605]:   Loaded settings plugin 
keyfile: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the 
NetworkManager mailing list.
  Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): 
GLib-GObject-WARNING **: cannot register existing type 'NMSetting'
  Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): 
GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed
  Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): 
GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' 
failed
  Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): 
libnm-util-CRITICAL **: _nm_register_setting: assertion 'type != 
G_TYPE_INVALID' failed
  Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): 
GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1497975/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1497944] Re: /usr/sbin/NetworkManager:11:platform_link_added:_platform_link_cb_idle:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1497944

Title:
  
/usr/sbin/NetworkManager:11:platform_link_added:_platform_link_cb_idle:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.0.4-0ubuntu3, the problem page at
  https://errors.ubuntu.com/problem/fd5d9b9dd219a1d76abc6f6a5525dd95fa737669
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1497944/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1498246] Re: /usr/sbin/NetworkManager:11:platform_link_added:platform_query_devices:nm_manager_start:main

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1498246

Title:
  
/usr/sbin/NetworkManager:11:platform_link_added:platform_query_devices:nm_manager_start:main

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.0.4-0ubuntu3, the problem page at
  https://errors.ubuntu.com/problem/827ad1b30ce85cf3c6ea9335ee3736d40b689905
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1498246/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1500482] Re: /usr/sbin/NetworkManager:11:nm_device_uses_assumed_connection:_set_state_full:nm_device_state_changed:link_timeout_cb:g_timeout_dispatch

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1500482

Title:
  
/usr/sbin/NetworkManager:11:nm_device_uses_assumed_connection:_set_state_full:nm_device_state_changed:link_timeout_cb:g_timeout_dispatch

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.0.4-0ubuntu3, the problem page at
  https://errors.ubuntu.com/problem/5ac0ed7e87bfe523f99d6f9703c9a501fab74014
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1500482/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1507530] Re: VPN service 'pptp' disappeared

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1507530

Title:
  VPN service 'pptp' disappeared

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  hello

   my vpn service is not working from the last update .vpn seems to be 
disappeared .
  logs:-
  Oct 19 16:08:43 Xalted-Testing NetworkManager[776]:  Starting VPN 
service 'pptp'...
  Oct 19 16:08:43 Xalted-Testing NetworkManager[776]:  VPN service 'pptp' 
started (org.freedesktop.NetworkManager.pptp), PID 3895
  Oct 19 16:08:43 Xalted-Testing NetworkManager[776]:  VPN service 'pptp' 
appeared; activating connections
  Oct 19 16:08:43 Xalted-Testing NetworkManager[776]:  VPN plugin state 
changed: init (1)
  Oct 19 16:08:43 Xalted-Testing NetworkManager[776]:  VPN plugin state 
changed: starting (3)
  Oct 19 16:08:43 Xalted-Testing NetworkManager[776]:  VPN connection 
'US-VPN' (Connect) reply received.
  Oct 19 16:08:43 Xalted-Testing pppd[3899]: Plugin 
/usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded.
  Oct 19 16:08:43 Xalted-Testing pppd[3899]: pppd 2.4.5 started by root, uid 0
  Oct 19 16:08:43 Xalted-Testing pppd[3899]: Using interface ppp0
  Oct 19 16:08:43 Xalted-Testing pppd[3899]: Connect: ppp0 <--> /dev/pts/10
  Oct 19 16:08:43 Xalted-Testing pptp[3902]: nm-pptp-service-3895 
log[main:pptp.c:314]: The synchronous pptp option is NOT activated
  Oct 19 16:08:43 Xalted-Testing NetworkManager[776]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
  Oct 19 16:08:43 Xalted-Testing NetworkManager[776]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown 
configuration found.
  Oct 19 16:08:43 Xalted-Testing NetworkManager[776]:  
/sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
  Oct 19 16:08:43 Xalted-Testing pptp[3917]: nm-pptp-service-3895 
log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 
'Start-Control-Connection-Request'
  Oct 19 16:08:44 Xalted-Testing pptp[3917]: nm-pptp-service-3895 
log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply
  Oct 19 16:08:44 Xalted-Testing pptp[3917]: nm-pptp-service-3895 
log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established.
  Oct 19 16:08:44 Xalted-Testing pptp[3917]: nm-pptp-service-3895 
log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 
'Outgoing-Call-Request'
  Oct 19 16:08:45 Xalted-Testing pptp[3917]: nm-pptp-service-3895 
log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply.
  Oct 19 16:08:45 Xalted-Testing pptp[3917]: nm-pptp-service-3895 
log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's 
call ID 29696).
  Oct 19 16:09:02 Xalted-Testing CRON[3919]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Oct 19 16:09:14 Xalted-Testing pppd[3899]: LCP: timeout sending 
Config-Requests
  Oct 19 16:09:14 Xalted-Testing pppd[3899]: Connection terminated.
  Oct 19 16:09:14 Xalted-Testing NetworkManager[776]:  VPN plugin failed: 
1
  Oct 19 16:09:14 Xalted-Testing NetworkManager[776]:SCPlugin-Ifupdown: 
devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
  Oct 19 16:09:14 Xalted-Testing pptp[3902]: nm-pptp-service-3895 
warn[decaps_hdlc:pptp_gre.c:204]: short read (-1): Input/output error
  Oct 19 16:09:14 Xalted-Testing pptp[3902]: nm-pptp-service-3895 
warn[decaps_hdlc:pptp_gre.c:216]: pppd may have shutdown, see pppd log
  Oct 19 16:09:14 Xalted-Testing pppd[3899]: Modem hangup
  Oct 19 16:09:14 Xalted-Testing pppd[3899]: Exit.
  Oct 19 16:09:14 Xalted-Testing NetworkManager[776]:  VPN plugin failed: 
1
  Oct 19 16:09:14 Xalted-Testing NetworkManager[776]:  VPN plugin state 
changed: stopped (6)
  Oct 19 16:09:14 Xalted-Testing NetworkManager[776]:  VPN plugin state 
change reason: 0
  Oct 19 16:09:14 Xalted-Testing NetworkManager[776]:  Policy set 'Wired 
connection 1' (eth0) as default for IPv4 routing and DNS.
  Oct 19 16:09:14 Xalted-Testing pptp[3917]: nm-pptp-service-3895 
log[callmgr_main:pptp_callmgr.c:234]: Closing connection (unhandled)
  Oct 19 16:09:14 Xalted-Testing pptp[3917]: nm-pptp-service-3895 
log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 
'Call-Clear-Request'
  Oct 19 16:09:14 Xalted-Testing pptp[3917]: nm-pptp-service-3895 
log[call_callback:pptp_callmgr.c:79]: Closing connection (call state)
  Oct 19 16:09:14 Xalted-Testing NetworkManager[776]:  error 
disconnecting VPN: Could not process the request because no VPN connection was 
active.
  Oct 19 16:09:19 Xalted-Testing NetworkManager[776]:  VPN service 'pptp' 
disappeared

  thanks

To manage notifications about this bug go 

[Touch-packages] [Bug 1540460] Re: network-manager crash

[Aron Xu]

Can you provide more information about the crash?

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1540460

Title:
  network-manager crash

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Network manager does not start!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1540460/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1541245] Re: Missing and loose of ethernet e1000 driver in Ubuntu 14.04

[Aron Xu]

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1541245

Title:
  Missing and loose of ethernet e1000 driver in Ubuntu 14.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I made a fresh install of 14.04 on a Dell XPS-8900 there is about two  or 
three month.
  The driver was missing, and I have installed manually a driver. It has 
worked, but with an ennoying problem.

  Each time a new Linux version is updated and then the computer is
  reboot, driver is lost and must install again.

  As it's not my computer, but the one of a friend which doesn't know
  about computers, I had to go and  reinstall and reboot the machine. I
  have made a script which allows the user to do that, but it's really a
  pain ...

  Is there a way to avoid such things ?

  Thanks
  A+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541245/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1542252] Re: Network unavailable after Libreoffice-5 PPA install

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1542252

Title:
  Network unavailable after Libreoffice-5 PPA install

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  This bug is a result of solving bug #1454310. After rebooting various
  system error messages appeared. Networking was unavailable. According
  to one Askubuntu suggestion, removed trusty-security package sources,
  apt-get update, upgrade, reinstall network-manager but same problem.
  After almost a week's work I was able to reactivate networking via
  /etc/network/interface and  sudo ifup xxx, first with wired then
  finally connecvting to hidden WiFi which I'm using now. If I reinstall
  network-manager and its gui companion installation goes well, but at
  reboot the same thing happens as described in the beginning. Presently
  network-maneger and its gui companion is completely removed. My system
  is on an Acer Laptop, 14.04.3 LTS and64, and it has been regularly
  updated according to notices. No special or custom programs are
  installed or no unusual customization was made.

  I'm attaching a file describing what happened a week ago leading to
  this system problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb  5 05:00:08 2016
  InstallationDate: Installed on 2013-10-31 (826 days ago)
  InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to trusty on 2014-08-31 (522 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1542252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1542523] Re: IPv6 temporary addresses accumulate over time

[Aron Xu]

This is really a feature but not a bug, it's called IPv6 privacy
extension.

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1542523

Title:
  IPv6 temporary addresses accumulate over time

Status in NetworkManager:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  On my office desktop machine I observe that it accumulates temporary
  IPv6 addresses over time, even though all except one are marked as
  deprecated already.

  E.g. right now my IP list looks like this:
  2: eno1:  mtu 1500 qlen 1000
  inet6 2620:101:80fc:224:ad8a:b15b:f83e:99e9/64 scope global temporary 
dynamic 
 valid_lft 594471sec preferred_lft 75471sec
  inet6 2620:101:80fc:224:7484:af8e:1051:52b9/64 scope global temporary 
deprecated dynamic 
 valid_lft 508673sec preferred_lft 0sec
  inet6 2620:101:80fc:224:3855:ba9f:c4ab:5784/64 scope global temporary 
deprecated dynamic 
 valid_lft 422875sec preferred_lft 0sec
  inet6 2620:101:80fc:224:ac16:b27:9fa4:4f5d/64 scope global temporary 
deprecated dynamic 
 valid_lft 337078sec preferred_lft 0sec
  inet6 2620:101:80fc:224:f0c6:8f9f:74b8:99ca/64 scope global temporary 
deprecated dynamic 
 valid_lft 251280sec preferred_lft 0sec
  inet6 2620:101:80fc:224:e070:5f9b:9783:bd0d/64 scope global temporary 
deprecated dynamic 
 valid_lft 165483sec preferred_lft 0sec
  inet6 2620:101:80fc:224:f46a:182b:e2c8:d026/64 scope global temporary 
deprecated dynamic 
 valid_lft 79685sec preferred_lft 0sec
  inet6 2620:101:80fc:224:baca:3aff:fea3:1b50/64 scope global mngtmpaddr 
noprefixroute dynamic 
 valid_lft 2591996sec preferred_lft 604796sec
  inet6 fe80::baca:3aff:fea3:1b50/64 scope link 
 valid_lft forever preferred_lft forever

  Once I reboot the interface has only the one IP addressed based on MAC
  address plus one temporary address.

  I verified manually via 'netstat -anp' that no active network
  connections or listening sockets remain on the interfaces which are
  marked as deprecated.

  I think the deprecated addresses should be removed once no socket is
  any longer using the address.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  5 14:33:40 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-01-20 (16 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 10.252.24.1 dev eno1  proto static  metric 100 
   10.252.24.0/21 dev eno1  proto kernel  scope link  src 10.252.25.160  metric 
100 
   10.252.75.120 via 10.252.24.1 dev eno1  proto dhcp  metric 100
  IwConfig:
   eno1  no wireless extensions.
   
   lono 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)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Wired connection 1  9950bc89-c72d-4964-9a18-e3187649321e  802-3-ethernet  
1454711368  Fri 05 Feb 2016 02:29:28 PM PST  yes  0 
no/org/freedesktop/NetworkManager/Settings/0  yes eno1activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eno1ethernet  connected  /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  9950bc89-c72d-4964-9a18-e3187649321e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  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/network-manager/+bug/1542523/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe 

[Touch-packages] [Bug 1547575] Re: network manager crashes constantly. FIX IS UPSTREAM

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1547575

Title:
  network manager crashes constantly. FIX IS UPSTREAM

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  # cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="15.10 (Wily Werewolf)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 15.10"
  VERSION_ID="15.10"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;

  
  $ dpkg -l network-manager
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion   
   Architecture Description
  
+++-===---===
  ii  network-manager 1.0.4-0ubuntu5.2  
   amd64network management framework (daemon and 
userspace tools)

  from: _usr_sbin_NetworkManager.0.crash
  SegvReason: reading NULL VMA
  SourcePackage: network-manager
  Stacktrace:
   #0  0x00497b07 in on_bss_proxy_acquired (proxy=0xeefbb0 
[GDBusProxy], result=0x17dfb40, user_data=) at 
supplicant-manager/nm-supplicant-interface.c:157
   self = 0xf5e0b0 [NMSupplicantInterface]
   error = 0x0
   properties = 0x0
   props = 0x0
   builder = {x = {0, 15699024, 15699025, 0, 0, 18446744073709551615, 
17780224, 8, 0, 3, 1033660112, 0, 0, 0, 0, 0}}
   iter = 
   __func__ = "on_bss_proxy_acquired"
   #1  0x7fab9c9b85f3 in g_task_return_now (task=0x17dfb40 [GTask]) at 
/build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gtask.c:1104
   #2  0x7fab9c9b8c7e in g_task_return (task=0x17dfb40 [GTask], 
type=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gtask.c:1162
   source = 0x7fab8e54a140
   #3  0x7fab9ca10efd in init_second_async_cb (source_object=, res=, user_data=0x17dfb40) at 
/build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gdbusproxy.c:1805
   task = 0x17dfb40 [GTask]
   error = 0x0
   #4  0x7fab9c9b85f3 in g_task_return_now (task=0x17dc8f0 [GTask]) at 
/build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gtask.c:1104

  NetworkManager$ git show 33527341b1e35034a4f1736df4bc98f8ac8418ab
  commit 33527341b1e35034a4f1736df4bc98f8ac8418ab
  Author: Jiří Klimeš 
  Date:   Thu May 7 11:27:26 2015 +0200

  wifi: fix a crash in on_bss_proxy_acquired()
  
  g_dbus_proxy_get_cached_property_names() function can return NULL.
  
   Program received signal SIGSEGV, Segmentation fault.
   on_bss_proxy_acquired (proxy=0x7fffe4003880 [GDBusProxy], 
result=0x895490, user_data=) at 
supplicant-manager/nm-supplicant-interface.c:159
   159while (*iter) {
   (gdb) bt
   #0  0x0048fac7 in on_bss_proxy_acquired (proxy=0x7fffe4003880 
[GDBusProxy], result=0x895490, user_data=)
   at supplicant-manager/nm-supplicant-interface.c:159
   #1  0x003bf84728b7 in g_simple_async_result_complete 
(simple=0x895490 [GSimpleAsyncResult]) at gsimpleasyncresult.c:763
   #2  0x003bf8472919 in complete_in_idle_cb (data=) at 
gsimpleasyncresult.c:775
   #3  0x003bf5c497fb in g_main_context_dispatch (context=0x7d6420) at 
gmain.c:3111
   #4  0x003bf5c497fb in g_main_context_dispatch 
(context=context@entry=0x7d6420) at gmain.c:3710
   #5  0x003bf5c49b98 in g_main_context_iterate (context=0x7d6420, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
gmain.c:3781
   #6  0x003bf5c49ec2 in g_main_loop_run (loop=0x7d64e0) at gmain.c:3975
   #7  0x004349d6 in main (argc=1, argv=0x7fffe598) at 
main.c:486

  diff --git a/src/supplicant-manager/nm-supplicant-interface.c 
b/src/supplicant-manager/nm-supplicant-interface.c
  index 4731ad7..19795bf 100644
  --- a/src/supplicant-manager/nm-supplicant-interface.c
  +++ b/src/supplicant-manager/nm-supplicant-interface.c
  @@ -156,7 +156,7 @@ on_bss_proxy_acquired (GDBusProxy *proxy, GAsyncResult 
*result, gpointer user_da
  g_variant_builder_init (, G_VARIANT_TYPE ("a{sv}"));
   
  iter = properties = g_dbus_proxy_get_cached_property_names (proxy);
  -   while (*iter) {
  +   while (iter && *iter) {
  GVariant *copy = g_dbus_proxy_get_cached_property (proxy, 
*iter);
   
  g_variant_builder_add (, "{sv}", *iter++, copy);

To manage notifications about this bug go to:

[Touch-packages] [Bug 1559734] Re: error : brokencount>(0)

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1559734

Title:
  error : brokencount>(0)

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  sudo apt-get install 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  You might want to run 'apt-get -f install' to correct these.
  The following packages have unmet dependencies:
   audacious : Depends: libaudcore3 (= 3.7.1-1~webupd8~xenial0) but 3.6.2-2 is 
installed
   audacious-plugins : Depends: libaudcore3 (>= 3.7.1-1~webupd8~xenial0) but 
3.6.2-2 is installed
  E: Unmet dependencies. Try using -f.
  prakash@prakash-Inspiron-3542:~$ sudo apt-get install -f
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
libaudgui3 libaudtag2 libbinio1v5 libpgm-5.1-0 libpoppler57 libzmq3
linux-headers-4.4.0-10 linux-headers-4.4.0-10-generic linux-headers-4.4.0-11
linux-headers-4.4.0-11-generic linux-headers-4.4.0-12
linux-headers-4.4.0-12-generic linux-headers-4.4.0-13
linux-headers-4.4.0-13-generic linux-image-4.4.0-10-generic
linux-image-4.4.0-11-generic linux-image-4.4.0-12-generic
linux-image-4.4.0-13-generic linux-image-extra-4.4.0-10-generic
linux-image-extra-4.4.0-11-generic linux-image-extra-4.4.0-12-generic
linux-image-extra-4.4.0-13-generic qtdeclarative5-qtfeedback-plugin
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libaudcore3
  The following packages will be upgraded:
libaudcore3
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/244 kB of archives.
  After this operation, 512 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  (Reading database ... 396704 files and directories currently installed.)
  Preparing to unpack .../libaudcore3_3.7.1-1~webupd8~xenial0_amd64.deb ...
  Unpacking libaudcore3:amd64 (3.7.1-1~webupd8~xenial0) over (3.6.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libaudcore3_3.7.1-1~webupd8~xenial0_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libaudgui.so.3', which is 
also in package libaudgui3:amd64 3.6.2-2
  Processing triggers for libc-bin (2.23-0ubuntu1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libaudcore3_3.7.1-1~webupd8~xenial0_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1559734/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1577382] Re: Network fails to start if VLAN have bigger MTU than default

[Aron Xu]

@Martins, I want to know what's the MTU configured on eno3 interface,
that one should be >= mtu of vlan interface.

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1577382

Title:
  Network fails to start if VLAN have bigger MTU than default

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Looks like a bug for me.
  If I configure interface VLAN with bigger MTU than 1500, which is default, 
interface with VLAN fail to start.

  May  2 14:40:16 demo-host systemd[1]: Started ifup for eno3.1009.
  May  2 14:40:16 demo-host sh[2184]: Set name-type for VLAN subsystem. Should 
be visible in /proc/net/vlan/config
  May  2 14:40:16 demo-host sh[2184]: RTNETLINK answers: Numerical result out 
of range
  May  2 14:40:16 demo-host sh[2184]: Failed to bring up eno3.1009.

  auto eno3
  iface eno3 inet manual
   mtu 1550

  auto eno3.805
  iface eno3.805 inet manual
  vlan-raw-device eno3
  mtu 1500

  auto eno3.1009
  iface eno3.1009 inet static
  vlan-raw-device eno3
  address 10.20.30.7
  netmask 255.255.255.0
  mtu 1550

  eno3 and eno3.805 starts successfully, but eno3.1009 not. If I look at
  syslog, I can see, that interface boot order goes from last interface
  in config to first:

  ~# cat /var/log/syslog|grep -i "Started ifup for eno3"
  May  2 14:40:16 demo-host systemd[1]: Started ifup for eno3.1009.
  May  2 14:40:16 demo-host systemd[1]: Started ifup for eno3.805.
  May  2 14:40:16 demo-host systemd[1]: Started ifup for eno3.

  This is really strange, I suppose it should have some kind of order in such 
cases.
  If I change configuration, e.g., eno3.1009 configure before eno3, host boots 
successfully with configured VLAN, but I suppose it could fail in some cases 
anyway.

  So looks like we need some kind of "order" configuration in which we
  can setup after what cases we can take up interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577382/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1573856] Re: NetworkManager resets spoofed mac address to physical mac

[Aron Xu]

This would be great to report upstream as a feature request.

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: network-manager (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1573856

Title:
  NetworkManager resets spoofed mac address to physical mac

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 bumped NetworkManager to version 1.1.93. Unlike 15.10
  (with v1.0.4) and earlier NetworkManager now resets temporary mac of
  an interface to actual physical mac effectively disabling typical wifi
  anonymization technics.

  Same issue is present in just released NetworkManager 1.2.

  It appears that sometime between 1.0.10 and 1.1.93 there was a change
  in src/devices/wifi/nm-device-wifi.c from

   /* Set spoof MAC to the interface */
   cloned_mac = nm_setting_wireless_get_cloned_mac_address (s_wireless);
   if (cloned_mac)
    nm_device_set_hw_addr (device, cloned_mac, "set", LOGD_WIFI);
  to

   /* Set spoof MAC to the interface */
   cloned_mac = nm_setting_wireless_get_cloned_mac_address (s_wireless);
   nm_device_set_hw_addr (device, cloned_mac, "set", LOGD_WIFI);

  cloned_mac is NULL if not specified in NetworkManager GUI. When called
  with NULL nm_device_set_hw_addr sets the mac to physical mac of the
  interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1573856/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1592550] Re: nm-applet does not appear in notification area

[Aron Xu]

** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1592550

Title:
  nm-applet does not appear in notification area

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  I have to log in to a wifi service via PEAP at my university. After
  doing this, on each successive reboot my nm-applet does not appear in
  my notification area (all my other applets are still there). I can get
  the applet to appear by running "nm-applet" in a terminal. I do get
  two notifications in the terminal as nm-applet loads:

  (nm-applet:3100): Gtk-WARNING **: Theme parsing error: gtk-
  main.css:69:33: Failed to import: Error opening file: No such file or
  directory

  (nm-applet:3100): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates:
  assertion 'window->update_and_descendants_freeze_count > 0' failed

  I have installed Ubuntu Mate twice on my system, and the applet works fine 
after logging into various networks until I set up the PEAP login. Also, even 
if the applet doesn't appear I am still connected to any saved wifi network 
within range.
  I am running Ubuntu Mate 16.04, with Mate 1.12.1 on a Dell Latitude e6410.
  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1592550/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1614978] Re: wifi connection lost after several minutes.

[Aron Xu]

Can you provide more details about your system? Probably you can use
apport to report your problem as described in
https://help.ubuntu.com/community/ReportingBugs

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1614978

Title:
  wifi connection lost after several minutes.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  My device is lenovo g510 ideapad ; my wireless chip is Broadcom Corporation 
BCM43142 802.11b/g/n [14e4:4365] (rev 01)
  I assume the driver isn't working as well or isn't there at all but don't 
know the right way to fix the problem.
  any useful help please ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1614978/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1637700] Re: Caching dnsmasq stops resolving after some time

[Aron Xu]

*** This bug is a duplicate of bug 1631241 ***
https://bugs.launchpad.net/bugs/1631241

** No longer affects: ubuntu

** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1637700

Title:
  Caching dnsmasq stops resolving after some time

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since upgrading to yakkety my network sometimes stops working - it
  might be related to suspending the laptop. The NetworkManager-managed
  caching dnsmasq just stops resolving at some point:

   dig google.com @127.0.1.1

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 22521
  ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;google.com.IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.1.1#53(127.0.1.1)
  ;; WHEN: Sat Oct 29 09:12:33 CEST 2016
  ;; MSG SIZE  rcvd: 28

  
  Networking and upstream DNS are fine:

   dig google.com @8.8.8.8

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @8.8.8.8
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63345
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;google.com.IN  A

  ;; ANSWER SECTION:
  google.com. 299 IN  A   46.134.208.30
  [...]

  ;; Query time: 43 msec
  ;; SERVER: 8.8.8.8#53(8.8.8.8)
  ;; WHEN: Sat Oct 29 09:12:31 CEST 2016
  ;; MSG SIZE  rcvd: 295

  
  Killing it resolves the issue, dnsmasq gets restarted and works again:

   ps aux | grep dnsmasq
  nobody4262  0.0  0.0  54308  2740 ?S01:30   0:00 
/usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
   sudo kill 4262
   dig google.com @127.0.1.1

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @127.0.1.1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58324
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;google.com.IN  A

  ;; ANSWER SECTION:
  google.com. 299 IN  A   46.134.208.59
  [...]

  ;; Query time: 41 msec
  ;; SERVER: 127.0.1.1#53(127.0.1.1)
  ;; WHEN: Sat Oct 29 09:12:54 CEST 2016
  ;; MSG SIZE  rcvd: 295

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 29 09:13:04 2016
  InstallationDate: Installed on 2016-05-06 (175 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-06 (175 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: network-manager 1.2.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Tags: yakkety third-party-packages
  Uname: Linux 4.8.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin lxd plugdev 
sambashare sbuild sudo vboxusers
  _MarkForUpload: True
  
modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla:
 [deleted]
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1637700/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1637123] Re: mythtv-frontend: missing dependencies

[Aron Xu]

** Package changed: network-manager (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1637123

Title:
  mythtv-frontend: missing dependencies

Status in Ubuntu:
  Confirmed

Bug description:
  After a clean install of Ubuntu 16.10 it is not possible to install
  the package "mythtv-frontend" because it depends on the package
  "transcode". The package "transcode" is not available anymore. It
  seems that in 16.10 a special package for transcoding purposes in
  mythtv was created. But the package dependencies were not adjusted.

  BTW: I cannot install Cinnamon due to unresolved dependecies too. Are
  there more "dead dependencies" in 16.10?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1637123/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1639699] Re: network-manager Down after Laptop Suspend mode

[Aron Xu]

Would you mind to confirm whether there is wpa_supplicant process
running after suspend/resume?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1639699

Title:
  network-manager Down after Laptop Suspend mode

Status in Ubuntu GNOME:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed Ubuntu Gnome 16.10 in Dell XPS-13 (9350)

  network-manager does not function properly when latop re-opened.(can't
  use network. but IP address is still allocated.) After executing the
  following command, the network runs again. "sudo service network-
  manager restart"

  $ lspci
  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 08)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
  00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 08)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless 
Network Adapter (rev 08)
  3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
  3c:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller (rev 01)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1639699/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1644626] Re: Login does not work with krb5 after upgrade to 16.04.1 from 14.04.5

[Aron Xu]

** Package changed: network-manager (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1644626

Title:
  Login does not work with krb5 after upgrade to 16.04.1 from 14.04.5

Status in Ubuntu:
  New

Bug description:
  After having managed to have a 1024x768 lightdm screen displayed
  begging to login, I've tried and being prompted with "You where logged
  in with cached credentials".

  Not really: I am logged in, but immediately thrown out again. It is
  impossible to work!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 19:32:58 2016
  InstallationDate: Installed on 2014-02-10 (1017 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IpRoute:
   default via 10.160.0.1 dev eth1 
   10.160.0.0/16 dev eth1  proto kernel  scope link  src 10.160.2.45 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   172.18.8.0/24 dev eth0  proto kernel  scope link  src 172.18.8.141
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago)
  ftp_proxy: http://proxy01-muc.bfs.de:8080/
  http_proxy: http://proxy01-muc.bfs.de:8080/
  nmcli-con:
   NAME   UUID  TYPE
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH 
   Kabelnetzwerkverbindung 1  c6be5d5a-c232-41e9-ae61-28f7974f30a9  
802-3-ethernet  1397215392  Fr 11 Apr 2014 13:23:12 CEST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  no  --   
   -- --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   eth0ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----   
   eth1ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  none  enabled enabled  
enabled  enabled  enabled
  no_proxy: 127.0.0.1, localhost

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1644626/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1646844] Re: Crashes when inserting (micro)SD-card in card reader, lenovo

[Aron Xu]

** Package changed: network-manager (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1646844

Title:
  Crashes when inserting (micro)SD-card in card reader, lenovo

Status in Ubuntu:
  New

Bug description:
  Recently, when i insert my SD-card (in Adapter) into my lenovo T410s (card 
reader, left side), the mounting applet doesn't pop up any longer. 
  I did a bit more of research and find a crash whenever I insert the card, 
also after a reboot, reproducably.

  dmesg tells me:

  [14297.018647] sdhci-pci :05:00.0: no hotplug settings from platform
  [14297.018667] pci :05:00.1: no hotplug settings from platform
  [14299.031485] irq 19: nobody cared (try booting with the "irqpoll" option)
  [14299.031493] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G   OX 
3.13.0-103-generic #150-Ubuntu
  [14299.031495] Hardware name: LENOVO 2924WEG/2924WEG, BIOS 6UET70WW (1.50 ) 
10/11/2012
  [14299.031496]   8801bbd83e60 8172ce29 
8801b25f3400
  [14299.031499]  8801b25f34a4 8801bbd83e88 810c5ac2 
8801b25f3400
  [14299.031501]  0013  8801bbd83ec8 
810c5ffc
  [14299.031503] Call Trace:
  [14299.031505][] dump_stack+0x64/0x82
  [14299.031518]  [] __report_bad_irq+0x32/0xd0
  [14299.031520]  [] note_interrupt+0x24c/0x2a0
  [14299.031522]  [] handle_irq_event_percpu+0xe9/0x220
  [14299.031524]  [] handle_irq_event+0x3d/0x60
  [14299.031526]  [] handle_fasteoi_irq+0x5a/0x100
  [14299.031531]  [] handle_irq+0x1e/0x30
  [14299.031534]  [] do_IRQ+0x4d/0xc0
  [14299.031538]  [] common_interrupt+0x6d/0x6d
  [14299.031539][] ? cpuidle_enter_state+0x4f/0xc0
  [14299.031546]  [] ? cpuidle_enter_state+0x48/0xc0
  [14299.031548]  [] cpuidle_idle_call+0xdc/0x220
  [14299.031552]  [] arch_cpu_idle+0xe/0x30
  [14299.031554]  [] cpu_startup_entry+0xc1/0x2b0
  [14299.031559]  [] start_secondary+0x21d/0x2d0
  [14299.031560] handlers:
  [14299.031563] [] usb_hcd_irq
  [14299.031601] [] sdhci_irq [sdhci]
  [14299.031605] [] ips_irq_handler [intel_ips]
  [14299.031606] Disabling IRQ #19

  It used to work earlier, though. I wonder what has changed? Though,
  before the SD-card was a different one, with a different capacity. The
  card itself works splendidly elsewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1646844/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1647259] Re: GUI issue with VPN connection state

[Aron Xu]

Which VPN plugin are you using?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647259

Title:
  GUI issue with VPN connection state

Status in network-manager package in Ubuntu:
  New

Bug description:
  1. Connect to a wifi network.
  2. Connect to a VPN.
  3. Disconnect from the wifi network.
  4. Connect to the wifi network.

  After these steps VPN is still checked in the GUI and toggling it
  doesn't do anything.

  Workaround to get VPN working again (after doing previous steps):

  1. Disconnect from the wifi network.
  2. Disconnect from the VPN.
  3. Connect to the wifi network.
  4. Connect to the VPN.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647259/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Aron Xu]

** Changed in: network-manager (Ubuntu Xenial)
   Status: Fix Committed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698

Title:
  [SRU] Upgrade network-manager to latest point release

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Xenial:
  Triaged
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.4) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  For xenial, we'll also backporting a patch from 1.2.6 that should fix
  a no-networking-after-resuming-from-sleep issue. This patch was
  applied to Debian testing and zesty in 1.4.2-3ubuntu1.

  For yakkety, this is an update to 1.2.6. Once 1.2.6 has been in use
  for a while without new problems, we'll look into doing a separate SRU
  for Xenial.

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This version has been in yakkety for sometime, and there's no report
  of regressions until now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1645698] Re: [SRU] network-manager

[Aron Xu]

Failed verification, will give another try next week.

** Tags removed: verification-needed
** Tags added: verification-failed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698

Title:
  [SRU] network-manager

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.4) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  For xenial, we'll also backporting a patch from 1.2.6 that should fix
  a no-networking-after-resuming-from-sleep issue. This patch was
  applied to Debian testing and zesty in 1.4.2-3ubuntu1.

  For yakkety, this is an update to 1.2.6. Once 1.2.6 has been in use
  for a while without new problems, we'll look into doing a separate SRU
  for Xenial.

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This version has been in yakkety for sometime, and there's no report
  of regressions until now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Aron Xu]

** No longer affects: network-manager

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1585863

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1587131] Re: 4-Way Handshake failed" connecting Wi-Fi after boot or suspend; retrying repeatedly eventually succeeds

[Aron Xu]

*** This bug is a duplicate of bug 1550538 ***
https://bugs.launchpad.net/bugs/1550538

** This bug has been marked a duplicate of bug 1550538
   periodically after suspend/resume wpasupplicant fails to authenticate

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1587131

Title:
  4-Way Handshake failed" connecting Wi-Fi after boot or suspend;
  retrying repeatedly eventually succeeds

Status in wpa package in Ubuntu:
  New

Bug description:
  This is in someway related to bug 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/931303 that is 
that this last was marked by fix-released (maybe related to just Broadcom 
BCM4321 wl) but it's still present and it's not related to one card rather than 
another.
  This bug is present, for example, in Ubuntu 12.04 and Intel Corporation 
PRO/Wireless 3945ABG as well as in both Ubuntu 14.04 and 16.04 and Realtek 
RTL8723BE PCIe Wireless Network Adapter (full bios update).
  Rebooting the router fix the issue immediately (this bug is only present in 
my linux machines and not in any android or Windows mobile devices).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1587131/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1460201] Re: wpa_supplicant chrashes when trying to look for wireless networks / on boot with a segfault

[Aron Xu]

*** This bug is a duplicate of bug 1651799 ***
https://bugs.launchpad.net/bugs/1651799

** This bug has been marked a duplicate of bug 1651799
   
/sbin/wpa_supplicant:11:p2p_group_assoc_resp_ie:send_assoc_resp:handle_assoc:ieee802_11_mgmt:ap_mgmt_rx

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1460201

Title:
  wpa_supplicant chrashes when trying to look for wireless networks / on
  boot with a segfault

Status in wpa package in Ubuntu:
  New

Bug description:
  The wirless worked just fine after a fresh install of ubuntu 15.04,
  but after a few minutes of using the internet (installing chromium,
  and downloading a theme (flat studio dark) wpa supplicant now chrashes
  on boot, and when I try to start it again with a segfault.

  Here's the output of dmesg: http://paste.ubuntu.com/11438910/, the
  segfault is at the bottom of the paste

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: wpasupplicant 2.1-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Fri May 29 22:21:21 2015
  InstallationDate: Installed on 2015-05-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1460201/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1637896] Re: No wifi connection after suspend

[Aron Xu]

*** This bug is a duplicate of bug 1651799 ***
https://bugs.launchpad.net/bugs/1651799

** This bug has been marked a duplicate of bug 1651799
   
/sbin/wpa_supplicant:11:p2p_group_assoc_resp_ie:send_assoc_resp:handle_assoc:ieee802_11_mgmt:ap_mgmt_rx

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1637896

Title:
  No wifi connection after suspend

Status in wpa package in Ubuntu:
  New

Bug description:
  Bug occurs  after upgrade 14.04 to 16.04.
  After suspend laptop then Network manager icon changed to 2 arrow, but 
doesn't work wifi connection.
  Please fix this quickly. I did 

  sudo apt-get update
  sudo apt-get upgrade
  sudo apt-get dist-upgrade

  But it still doesn't fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1637896/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1587131] Re: 4-Way Handshake failed" connecting Wi-Fi after boot or suspend; retrying repeatedly eventually succeeds

[Aron Xu]

*** This bug is a duplicate of bug 1550538 ***
https://bugs.launchpad.net/bugs/1550538

** Package changed: wpasupplicant (Ubuntu) => wpa (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1587131

Title:
  4-Way Handshake failed" connecting Wi-Fi after boot or suspend;
  retrying repeatedly eventually succeeds

Status in wpa package in Ubuntu:
  New

Bug description:
  This is in someway related to bug 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/931303 that is 
that this last was marked by fix-released (maybe related to just Broadcom 
BCM4321 wl) but it's still present and it's not related to one card rather than 
another.
  This bug is present, for example, in Ubuntu 12.04 and Intel Corporation 
PRO/Wireless 3945ABG as well as in both Ubuntu 14.04 and 16.04 and Realtek 
RTL8723BE PCIe Wireless Network Adapter (full bios update).
  Rebooting the router fix the issue immediately (this bug is only present in 
my linux machines and not in any android or Windows mobile devices).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1587131/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1651799] Re: /sbin/wpa_supplicant:11:p2p_group_assoc_resp_ie:send_assoc_resp:handle_assoc:ieee802_11_mgmt:ap_mgmt_rx

[Aron Xu]

** Changed in: wpa (Ubuntu)
   Importance: Undecided => High

** Changed in: wpa (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1651799

Title:
  
/sbin/wpa_supplicant:11:p2p_group_assoc_resp_ie:send_assoc_resp:handle_assoc:ieee802_11_mgmt:ap_mgmt_rx

Status in wpa package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
wpa.  This problem was most recently seen with package version 2.4-0ubuntu8, 
the problem page at 
https://errors.ubuntu.com/problem/bc564179f462736692df400cd76ad669355cff07 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1651799/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1587131] Re: 4-Way Handshake failed" connecting Wi-Fi after boot or suspend; retrying repeatedly eventually succeeds

[Aron Xu]

** Package changed: network-manager (Ubuntu) => wpasupplicant (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1587131

Title:
  4-Way Handshake failed" connecting Wi-Fi after boot or suspend;
  retrying repeatedly eventually succeeds

Status in wpasupplicant package in Ubuntu:
  New

Bug description:
  This is in someway related to bug 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/931303 that is 
that this last was marked by fix-released (maybe related to just Broadcom 
BCM4321 wl) but it's still present and it's not related to one card rather than 
another.
  This bug is present, for example, in Ubuntu 12.04 and Intel Corporation 
PRO/Wireless 3945ABG as well as in both Ubuntu 14.04 and 16.04 and Realtek 
RTL8723BE PCIe Wireless Network Adapter (full bios update).
  Rebooting the router fix the issue immediately (this bug is only present in 
my linux machines and not in any android or Windows mobile devices).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1587131/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1592514] Re: 3G usb Card - mmcli and network manager broken compatibility

[Aron Xu]

** Tags added: nm-improvements

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1592514

Title:
  3G usb Card - mmcli and network manager broken compatibility

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This bug is specific to "ipv4 only" 3g providers

  Here is syslog

  Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]:   [1465928772.9535] 
device (cdc-wdm1): Activation: starting connection 'XXXx X / XXX XXX XXX' 
(1554021e-ff2e-44f9-8e2d-c16cae73bfe0)
  Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]:   [1465928772.9538] 
audit: op="connection-activate" uuid="1554021e-ff2e-44f9-8e2d-c16cae73bfe0" 
name="XXXx X / XXX XXX XXX" pid=1663 uid=1000 result="success"
  Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]:   [1465928772.9542] 
device (cdc-wdm1): state change: disconnected -> prepare (reason 'none') [30 40 
0]
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Simple connect 
started...
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Simple connect 
state (4/8): Wait to get fully enabled
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Simple connect 
state (5/8): Register
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Simple connect 
state (6/8): Bearer
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Simple connect 
state (7/8): Connect
  Jun 14 19:26:12 Latitude-E5440 ModemManager[675]:   Modem 
/org/freedesktop/ModemManager1/Modem/2: state changed (registered -> connecting)
  Jun 14 19:26:15 Latitude-E5440 ModemManager[675]:   error: couldn't get 
current settings: Cannot send message: QMI service 'wds' version '1.2' 
required, got version '1.1'
  Jun 14 19:26:15 Latitude-E5440 ModemManager[675]:   Modem 
/org/freedesktop/ModemManager1/Modem/2: state changed (connecting -> connected)
  Jun 14 19:26:15 Latitude-E5440 ModemManager[675]:   Simple connect 
state (8/8): All done
  Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]:   [1465928775.2418] 
(cdc-wdm1): failed to connect modem: invalid bearer IP configuration
  Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]:   [1465928775.2419] 
device (cdc-wdm1): state change: prepare -> failed (reason 'config-failed') [40 
120 4]
  Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]:   [1465928775.2421] 
policy: disabling autoconnect for connection 'Tunisie Télécom / TUNTEL WEB 
DATA'.
  Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]:   [1465928775.2423] 
device (cdc-wdm1): Activation: failed for connection 'Tunisie Télécom / TUNTEL 
WEB DATA'
  Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]:   [1465928775.2428] 
device (cdc-wdm1): state change: failed -> disconnected (reason 'none') [120 30 
0]
  Jun 14 19:26:15 Latitude-E5440 ModemManager[675]:   Modem 
/org/freedesktop/ModemManager1/Modem/2: state changed (connected -> 
disconnecting)
  Jun 14 19:26:15 Latitude-E5440 ModemManager[675]:   Modem 
/org/freedesktop/ModemManager1/Modem/2: state changed (disconnecting -> 
registered)

  i managed to make it work using this shell script

  #!/bin/bash
  mmcli -m 0 -b $1 --connect
  ifconfig wwp0s29u1u8u3i3 up
  mmcli -m 0 -b $1
  dhclient -d wwp0s29u1u8u3i3 &
  echo "nameserver 8.8.8.8" >> /etc/resolv.conf

  i also disabled ipv6 with gui

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592514/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1598054] Re: /usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:nm_dhcp_listener_get:dispose:g_object_unref

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1598054

Title:
  
/usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:nm_dhcp_listener_get:dispose:g_object_unref

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.2.0-0ubuntu0.16.04.2, the problem page at
  https://errors.ubuntu.com/problem/c984f3ecadf9e7a82d7c41775f083d07aa6ac706
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1598054/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1598050] Re: /usr/sbin/NetworkManager:11:nm_device_get_act_request:wired_secrets_cb:_do_cancel_secrets:dispose:g_object_unref

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1598050

Title:
  
/usr/sbin/NetworkManager:11:nm_device_get_act_request:wired_secrets_cb:_do_cancel_secrets:dispose:g_object_unref

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.2.0-0ubuntu0.16.04.2, the problem page at
  https://errors.ubuntu.com/problem/a0310f22806142fcc2c4bfaf2089f1f9887231fc
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1598050/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1639337] Re: Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-xorg-evdev

[Aron Xu]

** Package changed: network-manager (Ubuntu) => xserver-xorg-input-evdev
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1639337

Title:
  Ubuntu 16.10 Abs_pressure not reported from kernel evdev to xserver-
  xorg-evdev

Status in xserver-xorg-input-evdev:
  Unknown
Status in xserver-xorg-input-evdev package in Ubuntu:
  Confirmed

Bug description:
  Please refer to bug filed with freedesktop.org:

  https://bugs.freedesktop.org/show_bug.cgi?id=98575

  I modified a driver for the Bosto Tablet 22HD and others, this has
  been working without problems across the last several releases and
  continues to work with 16.04.1 LTS.

  When I upgraded to 16.10, pressure readings are lost from all
  applications, X & Y data still visible.

  evtest shows correct EV_ data for ABS_X ABS_Y and ABS_PRESSURE, but
  when xinput is used.

  xinput --list --long 

  The Valuator for pressure is listed, but no changes occur as the tool
  is used. The parameters of the Valuator can still be modified using
  xinput tweaking tools, but no pressure reported.

  All X apps requiring pressure data fail.

  I made a fresh install of 16.10, loaded the driver  same issue.

  I run 16.04.1 LTS, everything fine.
  I have others users of my driver code also using 16.04.1 without issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evdev/+bug/1639337/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com

[Aron Xu]

** Tags added: nm-improvements

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/991481

Title:
  Constant dns traffic for daisy.ubuntu.com

Status in Whoopsie:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged
Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  Watching GNetworkMonitor's network-changed signal causes constant DNS
  traffic.

  Andy Whitcroft points out that the NETLINK_ROUTE socket set up by
  GNetworkMonitor will fire events every time an ARP entry appears or
  disappears.

  Unfortunately, we currently need an additional layer of connectivity
  checking because checking NetworkManager's state for CONNECTED_GLOBAL
  is not enough to know whether we're really online. Ubuntu does not yet
  use the NetworkManager connectivity check [1].

  The likely solution to this bug is a replacement for GNetworkMonitor
  in whoopsie.

  1: http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326

  Original report follows:

  Every few seconds, I see a dns query for daisy.ubuntu.com. After
  removing whoopsie, the traffic goes away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1629932] Re: /usr/bin/nmcli:11:nmc_find_connection:nmc_secrets_requested:ffi_call_VFP:ffi_call:g_cclosure_marshal_generic_va

[Aron Xu]

** Tags added: nm-touch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1629932

Title:
  
/usr/bin/nmcli:11:nmc_find_connection:nmc_secrets_requested:ffi_call_VFP:ffi_call:g_cclosure_marshal_generic_va

Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.2.2-0ubuntu1~vivid3, the problem page at
  https://errors.ubuntu.com/problem/b3b7dae5bf05fa65c302fd75344f7924a83e66c1
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629932/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1639668] Re: Webapp crashes when opening a tab

[Aron Xu]

** Package changed: network-manager (Ubuntu) => canonical-devices-
system-image

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1639668

Title:
  Webapp crashes when opening a tab

Status in Canonical System Image:
  Incomplete

Bug description:
  It's not the first time I try to report this bug.

  On Ubuntu Touch, when I open a new tab inside a webapp, when closing
  it, the webapp crashes since OTA 11. I've reset m phone but it's still
  there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639668/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1629611] Re: dns server priority broken

[Aron Xu]

** Tags added: nm-improvements

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1629611

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1610750] Re: nm-applet constantly prompts for password, leaks memory

[Aron Xu]

** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1610750

Title:
  nm-applet constantly prompts for password, leaks memory

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Network Manager is constantly asking me for a WIFI password, as
  frequently as once a minute. I do not get this problem on my phone,
  even though it is using the same WIFI network. The problem does not
  occur on other WIFI networks, so I suspect this is a problem with the
  WIFI network itself, and is possibly not Network Manager's fault. So
  this is annoying, but liveable.

  However, np-applet is also leaking an absurd amount of memory each
  time I enter my password and click "Connect". It's ridiculous for it
  to be using up over 2 GB of resident memory, and to be constantly
  increasing that number, after running for only a few hours.

  This is a not a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager-applet/+bug/684599. In that issue, which has been
  closed with a "Fix Released" status, the reports are hundreds of
  megabytes of memory, not gigabytes, so I suspect this is a
  fundamentally different problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug  7 19:08:52 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-08-26 (1077 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 10.2.61.69 dev wlan0  proto static  metric 600 
   10.0.1.4 via 10.2.61.69 dev wlan0  proto dhcp  metric 600 
   10.2.61.68/30 dev wlan0  proto kernel  scope link  src 10.2.61.70  metric 
600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  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: Upgraded to xenial on 2016-04-26 (103 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH

   wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/0  
EHS New Yorker Residence  c06e0703-cd04-4294-9f99-8624c834f389  
/org/freedesktop/NetworkManager/ActiveConnection/53 
   eth0ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/1  
------  

   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  
------
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1610750/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1646859] Re: Wifi not working after suspend on 16.10

[Aron Xu]

*** This bug is a duplicate of bug 1631241 ***
https://bugs.launchpad.net/bugs/1631241

** This bug is no longer a duplicate of bug 1642507
   Not internet after waking from suspend
** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1646859

Title:
  Wifi not working after suspend on 16.10

Status in network-manager package in Ubuntu:
  New

Bug description:
  After waking from suspend, nm doesn't automatically connect to WiFi,
  instead nm indicator is showing RJ45 icon like it's connected on wired
  network but it's not. NM indicator panel doesn't show any WiFi
  networks and there is no connection. restarting the service or
  stopping the WiFi antenna using keyboard shortcut don't fix the
  problem. Only relogging the account or restart fixes the issue.

  OS: Ubuntu 16.10
  Device: DELL Inspiron 13" 7000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1646859/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1000419] Re: NetworkManager crashed with SIGABRT in __assert_fail_base()

[Aron Xu]

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1000419

Title:
  NetworkManager crashed with SIGABRT in __assert_fail_base()

Status in network-manager package in Ubuntu:
  New

Bug description:
  NetworkManager crashed with SIGABRT in raise()

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
  Uname: Linux 3.2.0-24-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  Date: Wed May 16 09:14:44 2012
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  IpRoute:
   default via 10.64.64.64 dev ppp0  proto static 
   10.64.64.64 dev ppp0  proto kernel  scope link  src 10.112.82.128 
   169.254.0.0/16 dev ppp0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WiMAXEnabled=true
  ProcCmdline: NetworkManager
  ProcEnviron:
   LANGUAGE=en_PH:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_PH.UTF-8
  Signal: 6
  SourcePackage: network-manager
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   __assert_fail () from /lib/i386-linux-gnu/libc.so.6
   rtnl_link_build_get_request () from /usr/lib/libnl-route-3.so.200
  Title: NetworkManager crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-03-03 (74 days ago)
  UserGroups:
   
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   ttyUSB0gsm   connected 
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/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.4.0connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1000419/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1642507] Re: Not internet after waking from suspend

[Aron Xu]

*** This bug is a duplicate of bug 1631241 ***
https://bugs.launchpad.net/bugs/1631241

** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1642507

Title:
  Not internet after waking from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Release Information:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  Package Information:
  network-manager:
Installed: 1.2.4-0ubuntu1
Candidate: 1.2.4-0ubuntu1
Version table:
   *** 1.2.4-0ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  System Information:
  Dell XPS 15 9550
  Wireless: Network controller: Broad com Limited BCM43602 802.11ac Wireless 
LAN SoC (rev 01)
  Wired: Wired Ethernet via Apple USB Ethernet Adapter (ID 05ac:1402 Apple, 
Inc. Ethernet Adapter [A1277])

  Problem Description:
  I have noticed the problem on both wired and wireless. Ever since upgrading 
to 16.10(from 16.04), the system loses internet after waking from suspend. 
Internet works fine after a reboot or when powering on normally.

  "service network-manager restart" fixes the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 17 09:37:30 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-31 (169 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.80.1 dev enx7cc3a187f0f2  proto static  metric 100 
   default via 192.168.80.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.80.0/24 dev enx7cc3a187f0f2  proto kernel  scope link  src 
192.168.80.209  metric 100 
   192.168.80.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.80.225  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-10-28 (19 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enx7cc3a187f0f2  ethernet  connected  
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
e6493319-b925-3b33-92a7-259922dccdaa  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp2s0   wifi  connected  
/org/freedesktop/NetworkManager/Devices/1  whymusticry_fast 1  
b51f9098-d053-45d7-ba42-97bf2e87bda2  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo   loopback  unmanaged  
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1642507/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

[Aron Xu]

** Tags added: nm-touch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1607684

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

[Aron Xu]

** Tags added: nm-improvements

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1631241

Title:
  Name resolution stops working after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1631241/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1633845] Re: network-manager does not connect to wifi

[Aron Xu]

*** This bug is a duplicate of bug 1631241 ***
https://bugs.launchpad.net/bugs/1631241

** This bug is no longer a duplicate of bug 1642507
   Not internet after waking from suspend
** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1633845

Title:
  network-manager does not connect to wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When trying to connect to wifi network, network-manager remains
  blocked in waiting for authentification state then fails after cca
  1min. This started to happen after I updated to kubuntu 16.10.

  Stopping network manager from service and trying to manually connect
  with wpa_supplicant works fine.

  The only way to fix this for me was to stop network manager and/or
  networking and restart the services sometimes more than once.

  os: Kubuntu 16.10
  network-manager: 1.2.4
  hardware: dell xps 9550 
  network controller: BCM43602

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1625116] Re: RT3290 not working

[Aron Xu]

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1625116

Title:
  RT3290 not working

Status in linux package in Ubuntu:
  New

Bug description:
  My WiFi RT3290 does not work on Ubuntu. Neither I remember it working
  on any previous version. I don't have good knowledge of command line
  or linux. But I am using ubuntu as my primary OS. Currently I am using
  usb wifi adapter to connect to internet. I have followed almost every
  guide available on internet like downloading driver from mediatek
  website or someone's dropbox folder and then compiling or changing
  linux kernels. I don't know why still I can't make it work. I want
  this device to work out of box for next ubuntu version. Let me know if
  you need any further information about collecting logs of my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Sep 19 15:45:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-09-07 (12 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlxaca2131a2daf  proto static  metric 600 
   169.254.0.0/16 dev wlxaca2131a2daf  scope link  metric 1000 
   192.168.0.0/24 dev wlxaca2131a2daf  proto kernel  scope link  src 
192.168.0.109  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION   CON-UUID  CON-PATH   

   wlxaca2131a2daf  wifi  connected
/org/freedesktop/NetworkManager/Devices/2  UnitedNepal  
ff526f85-e18b-4713-ae67-f3fbfa290c4b  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp1s0   ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/0  --   --  
  -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625116/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1618839] Re: Regression: WiFi connection reconnects, but dead, after waking from standby

[Aron Xu]

*** This bug is a duplicate of bug 1631241 ***
https://bugs.launchpad.net/bugs/1631241

** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1618839

Title:
  Regression: WiFi connection reconnects, but dead, after waking from
  standby

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Bug introduced somewhere between Ubuntu 14.04.3 and 16.04.1

  If my Thinkpad T420s awakes from standby, very often the last
  connected WiFi network is reconnected immediately, but the connection
  is dysfunctional.

  ifconfig shows a valid connection with an IPv4 address assigned for
  the wlp3s0 interface.

  But there is no traffic, no success on DNS queries on the connection.

  If I reconnect by clicking the connection in the nm-applet menu, all
  is fine again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1618839/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1617772] Re: Ubuntu Phone: Unable to connect FritzBox 7490

[Aron Xu]

** Tags added: nm-touch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1617772

Title:
  Ubuntu Phone: Unable to connect FritzBox 7490

Status in network-manager package in Ubuntu:
  New

Bug description:
  On Ubuntu Phone (OTA-12): Unable to connect FritzBox 7490.

  Aug 28 18:13:42 ubuntu-phablet NetworkManager[1535]: ... device
  (wlan0): Activation: (wifi) access point 'FRITZ!Box 7490' has security
  but secrets are required.

  But the WPA password was applied in the previous dialog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1617772/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1633912] Re: Problem with DNS resolution after suspend

[Aron Xu]

*** This bug is a duplicate of bug 1631241 ***
https://bugs.launchpad.net/bugs/1631241

** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1633912

Title:
  Problem with DNS resolution after suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I
  have network issues, one time I was not able to connect to a wifi
  network (might report another bug if this occurees again, but maybe it
  is related, as in network-manager is in some broken state after
  suspend).

  Here is whats happening pretty often: After resume from suspend I have
  a solid network connection, no problem to ping machines in LAN or on
  the internet. But DNS resolution is broken until I restart the
  network-manager service.

  I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it
  should be in there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 21:01:09 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-09-28 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev br-541a0f9bec93  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-541a0f9bec93  proto kernel  scope link  src 172.18.0.1 
   192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.0.118  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1629620] Re: DNS resolver stops accepting queries

[Aron Xu]

*** This bug is a duplicate of bug 1631241 ***
https://bugs.launchpad.net/bugs/1631241

** This bug has been marked a duplicate of bug 1631241
   Name resolution stops working after resume from suspend

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1629620

Title:
  DNS resolver stops accepting queries

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After a while / after resume from suspend, the system becomes unable
  to respond to DNS queries, with the following output for example:

  $ nslookup google.com 127.0.1.1
  Server:   127.0.1.1
  Address:  127.0.1.1#53

  ** server can't find google.com: REFUSED

  
  This is on an up to date yakkety install.  Changing resolv.conf to use 
8.8.8.8, or restarting network-manager appears to fix this, at least until it 
recurs again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct  1 21:28:51 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-08-21 (407 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION   CON-UUID  CON-PATH
   
   docker0bridgeconnected 
/org/freedesktop/NetworkManager/Devices/1  docker0  
63f0b05b-f699-4a68-81ce-f62d2c1a247d  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlp3s0 wifi  connected 
/org/freedesktop/NetworkManager/Devices/4  HOME-1622-5  
6df3f2f0-fb86-43b5-802a-d59bc5734be3  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   24:DA:9B:B9:09:0E  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629620/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp