[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
I enabled -proposed on jammy, and updated pcscd to 1.9.5-3ubuntu1. I verified that the socket is now enabled: $ systemctl status pcscd.socket ● pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; enabled; vendor preset: enabled) Active: active (listening) since Fri 2023-07-21 12:57:49 EDT; 6s ago Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) CGroup: /system.slice/pcscd.socket Jul 21 12:57:49 brain systemd[1]: Listening on PC/SC Smart Card Activation Socket. I also verified that when I plug in my Nitrokey HSM2, that it's now recognized by the system: $ sc-hsm-tool Using reader with a card: Nitrokey Nitrokey HSM (...) ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Committed Status in pcsc-lite source package in Kinetic: Fix Committed Status in pcsc-lite source package in Lunar: Fix Committed Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Description changed: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket - Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) - Active: inactive (dead) -Triggers: ● pcscd.service - Listen: /run/pcscd/pcscd.comm (Stream) + Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) + Active: inactive (dead) + Triggers: ● pcscd.service + Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. + + As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: + - jammy + - kinetic + - lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Confirmed Status in pcsc-lite source package in Jammy: Triaged Status in pcsc-lite source package in Kinetic: Triaged Status in pcsc-lite source package in Lunar: Triaged Status in pcsc-lite package in Debian: Unknown Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Description changed: - Ubuntu Mate 22.04 with the latest updates. - Problem is present with internal smart-card reader and also external usb smart-card reader. + [ Impact ] - eid-viewer sees no card reader,but When i do: + The pscc-lite package provides an open source implementation of PC/SC, + the de-facto standard to interface Personal Computers with Smart + Cards/Readers. - sudo pcscd -f + This bug is in the upstream debian packaging, and results in the + pcscd.socket being disabled after installation. This prevents automatic + startup of the associated pcscd.service, thus preventing automatic + handling of Smart Cards/Readers w/out manual intervention to enable the + socket (which doesn't persist across reboots). - it is working, also following the tips of Ludovic: - https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html + This is especially painful for users that require Smart Authentication + for login. - sudo systemctl stop pcscd.socket - sudo systemctl start pcscd.socket + [ Test Plan ] - It is working until next restart. + Steps to reproduce: - libacsccid1 version: 1.1.8-1 - libccid version: 1.5.0-2 - pcscd version: 1.9.5-3 - eid-archive version: 2022.3 - eid-mw version: 5.0.28v5.0.28-0u2204-1 - eid-viewer version: 5.0.28v5.0.28-0u2204-1 + 1. If installed, remove and do a fresh install of the package pcscd + (the sole version released for jammy is 1.9.5-3). - In Firefox, my eid card is then also recognized, but only in the ESR - version, but this is a know Mozilla bug. + 2. Verify that the pcscd.socket is disabled: + + $ systemctl status pcscd.socket + ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket + Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) + Active: inactive (dead) +Triggers: ● pcscd.service + Listen: /run/pcscd/pcscd.comm (Stream) + + 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or + Nitrokey) that's known to work on Ubuntu and verify that it fails to + work. + + Repeating the same steps with a package built with the patch attached to + comment #27 should ensure that the socket is enabled, and that + interaction with a Smart Card or Crypto Token should work w/out manual + intervention. + + [ Where problems could occur ] + + This is a back-ported change from upstream and is a result of a bug in + dh_installsystemd (see comment #26). As such the risk is minimal. + + The only potential risk of failure I can come up with is a snap that + stages the old version of the client library, as it would be looking in + the wrong place for the socket. + + [ Other Info ] + + This bug was originally reported against Ubuntu Mate 22.04, however it + applies to all derivatives of Ubuntu Desktop 22.04 LTS. + + Note - while there's some disagreement as to whether this bug occurs + 100% of the time across all 22.04 installations, it's pretty clear from + the upstream Debian bug and subsequent packaging fix that we should land + this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Confirmed Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Summary changed: - pcscd 1.9.5-3 do not start automatically, only manual + pcscd.socket is disabled after installation -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
I ran into this bug earlier this week while trying to setup my new Nitrokey HSM2 (https://docs.nitrokey.com/hsm/linux/) on a Thinkpad running 22.04 LTS. I've confirmed that the upstream commit from 1.9.9-2 fixes the problem, and am uploading this as a patch. ** Patch added: "Backported packaging fix from upstream 1.9.9-2" https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+attachment/5672739/+files/0001-Fix-dh_installsystemd-doesn-t-handle-files-in-usr-li.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi
** Changed in: network-manager (Ubuntu) Assignee: Tony Espy (awe) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported
** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1781597 Title: [SRU] WoWLAN settings are not supported Status in network-manager package in Ubuntu: Confirmed Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packages over the wifi connection. This is something requested by some OEM projects, for bionic server images. NM 1.12 supports configuring this feature, so this can be achieved by backporting that support to 1.10 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1392012] Re: [MIR] libteam
Re-opened, as there's some interest from OEMs in seeing NM teaming support land in 18.04. ** Description changed: Availability: The package is available in universe, built on all architectures. Rationale: - The package is a new (Build-)Depends for network-manager, for network device bonding support. + The package is a new (Build-)Depends for network-manager, for network device teaming (aka user-space bonding) support. Security: Could not find any related security advisories. Quality assurance: The package is well-maintained in Debian and expected to not require extensive effort to maintain in Ubuntu. UI standards: Not applicable. Dependencies: - All build and binary dependencies are in main; with one exception: - - Build-Depends: libjeansson-dev (bug 1392023) + All build and binary dependencies are in main. Standards compliance: The package meets requirements. Maintenance: The package meets requirements. Background information: libteam is a library for communicating with the netlink kernel layer in order to create bonded interfaces. ** Changed in: libteam (Ubuntu) Status: Expired => Confirmed ** Changed in: libteam (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libteam in Ubuntu. https://bugs.launchpad.net/bugs/1392012 Title: [MIR] libteam Status in libteam package in Ubuntu: New Bug description: Availability: The package is available in universe, built on all architectures. Rationale: The package is a new (Build-)Depends for network-manager, for network device teaming (aka user-space bonding) support. Security: Could not find any related security advisories. Quality assurance: The package is well-maintained in Debian and expected to not require extensive effort to maintain in Ubuntu. UI standards: Not applicable. Dependencies: All build and binary dependencies are in main. Standards compliance: The package meets requirements. Maintenance: The package meets requirements. Background information: libteam is a library for communicating with the netlink kernel layer in order to create bonded interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libteam/+bug/1392012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
My point is that we shouldn't release these patches as an SRU without being able to reproduce the bugs that the patches claim to fix first. Otherwise we risk introducing additional regressions. So if we want to consider an SRU for NM with one or more of Aaron's patches, then yes we need to go through each one of his patches, try to re-create the problem, validate that the patch fixes it, and then submit the patch upstream for comment as well. I'll put this bug back on the agenda for next week's network/telephony meeting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: Triaged 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
There's no evidence (ie. syslogs, package versions, output of wpa_cli) provided which is a basis for re-opening the bug. Also, please point us to the *exact* patch that is supposed to fix the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: Triaged 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
This bug was marked FixReleased based on the upload of network-manager 1.2.6-0ubuntu0.16.04.1 to xenial updates and the comments from a many people that the issue was resolved. Recently there were two comments (#96 and #97) that claim that the bug still exists. Comment #96 doesn't even list which release, and #97 has very little detail. For this bug, the specific case is that after S3, NM failed to restart scanning. So for someone to confirm they've hit this bug, they need to use 'sudo wpa_cli' to check whether or NM is scanning or not. If NM's scan logic is working, you'll see CTRL-EVENT- SCAN-RESULTS messages output by wpa_cli. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: Triaged 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
@Kevin NetworkManager already has code to monitor system signals related to suspend/resume, so no adding additional scripts to /usr/lib/systemd /system-sleep isn't the answer. @Dan Different bug... this bug is caused by NetworkManager's WiFi scanning logic stalling due to a race condition. You can tell this by running 'sudo wpa_cli' and watching for scan events. If you don't see any, then you've hit the bug. I've also unfortunately confirmed that dropping the original patch from 1.2.6 doesn't fix the problem either. I tried a cycle of 100 with my version of 1.2.6 with the original ScanDone patch dropped and I still tripped the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/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: Confirmed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1055068] Re: Guest user can use arbitrary MAC addresses
Updated the Status to "FixReleased" as it's not possible to do this anymore on the latest 16.04 LTS release with NetworkManager 1.2.x, as guest users no longer have sufficient permission to add new connections. Retrofitting this to the version of NM in 14.04 might be a challenging as the version of NM (and other components) in trusty is currently based on NM 0.9.8.*. If this is important to anyone, please first confirm the behavior on a 14.04 LTS system and detail your testing in this bug, although it's doubtful we'd fix. ** Changed in: network-manager (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055068 Title: Guest user can use arbitrary MAC addresses Status in network-manager package in Ubuntu: Fix Released Bug description: In Quantal, as a guest user you can create a network connection with an arbitrary mac address - I take that as a security hole (being able to break another machine on the network). (actually in this case the guest user you get to register a remote desktop account, you can get a terminal in it - that might be another security issue) Go to the network manager icon and edit connections Wired network Add connection Choose the eth0/deault device mac address Type in a MAC address of your own evil making in the 'cloned mac address' box Untick 'available to all users' and Save Now, you have a new connection, but it's not up Open a terminal and use nmcli con to list the network connections, and note the UUID of your new one. Now do nmcli con up uuid .where . is the UUID you just got. You're now spoofing someone elses MAC address. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sun Sep 23 16:41:47 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120905.2) IpRoute: default via 192.168.122.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.34 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 190a0ede6-43a8-4ad1-a26c-b17a52146725 802-3-ethernet1348414780 Sun 23 Sep 2012 16:39:40 BST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1055068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1055068] Re: Guest user can use arbitrary MAC addresses
** Changed in: network-manager (Ubuntu) Status: Triaged => Won't Fix ** Changed in: network-manager (Ubuntu) Status: Won't Fix => Fix Released ** Changed in: network-manager (Ubuntu) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055068 Title: Guest user can use arbitrary MAC addresses Status in network-manager package in Ubuntu: Fix Released Bug description: In Quantal, as a guest user you can create a network connection with an arbitrary mac address - I take that as a security hole (being able to break another machine on the network). (actually in this case the guest user you get to register a remote desktop account, you can get a terminal in it - that might be another security issue) Go to the network manager icon and edit connections Wired network Add connection Choose the eth0/deault device mac address Type in a MAC address of your own evil making in the 'cloned mac address' box Untick 'available to all users' and Save Now, you have a new connection, but it's not up Open a terminal and use nmcli con to list the network connections, and note the UUID of your new one. Now do nmcli con up uuid .where . is the UUID you just got. You're now spoofing someone elses MAC address. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sun Sep 23 16:41:47 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120905.2) IpRoute: default via 192.168.122.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.34 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 190a0ede6-43a8-4ad1-a26c-b17a52146725 802-3-ethernet1348414780 Sun 23 Sep 2012 16:39:40 BST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1055068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
Ugh, and then I wake my Thinkpad 410s just now, and I hit the bug on the 201st cycle. ;(- Guess I'll go back to dropping the patch again from 1.2.6 and see how many cycles I can run on it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/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: Confirmed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
@taiebot65 Thanks. I'll take a look. Regarding this bug, it turns out that when I was testing my version of NM with the dropped 'ScanDone' patch (wifi-Signal-on-the-wifi- device...), I'd been doing so on top of the newly re-based 1.2.6, and it turns out there was an actual fix in 1.2.6 which seems to fix the bug: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-2=b749f7d31b7e5f57f18026a14b6a444e59a488cf This new version of NM hasn't yet been SRU'd for xenial, as version 1.2.4-0ubuntu0.16.04.1 is still in -proposed. I'll see if maybe we can expedite this landing and skip 1.2.4 altogether. Note, I've managed to run 200 cycles of S3 on my Thinkpad without hitting the bug. This included about 25 cycles of manual suspend/resume, and 175 iterations using fwts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/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: Confirmed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
** Changed in: oem-priority/xenial Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/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: Confirmed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
I've reproduced this on a Thinkpad 410s running 16.04 LTS. The version of network-manager I used is the latest from xenial-updates: 1.2.2-0ubuntu0.16.04.3. A few comments: 1) The fwts s3 test uses a low-level API to exercise suspend/resume. I've been working with the fwts maintainer on an extension to fwts that allows it to call out to a hook script on each iteration. This makes it possible to ensure that scanning is active for each iteration. 2) I've done some preliminary testing of the version of NM in xenial- proposed (1.2.4-0ubuntu0.16.04.1), and although it looked promising at first, I was still able to reproduce the bug. 3) We're pretty sure we know which patch [1] caused the issue, and are working to determine the best way to fix it. The fix provided in comment #5 appears to resolve it, but unfortunately it breaks the original patch's behavior. @taiebot65 It sounds like you're hitting a different problem, so it'd probably be best if you filed a new bug. [1] wifi-Signal-on-the-wifi-device-when-its-supplicant-i.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1023277] Re: Please provide option to make NetworkManager verify only the root certificate of the signed cert chain (WPA2-Enterprise)
Just moved this to Incomplete, as it's been posited that the fix for bug #1104476 resolves the issue. If anyone can confirm that this is still broken, we can investigate further. ** Changed in: network-manager (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1023277 Title: Please provide option to make NetworkManager verify only the root certificate of the signed cert chain (WPA2-Enterprise) Status in network-manager package in Ubuntu: Incomplete Bug description: I have to use a chain certificate, that had all certificates involved in the verification of the AP. this seems uncomfortable and breaks design (of at least the eduroam networks). The (German) eduroam networks are all signed with a certificate of the corresponding university or college CA, which is signed by the DFN (german scientific network) which is signed by Deutsche Telekom Root CA (installed by default on ubuntu) By opting to verify the complete chain, I have to set up various configurations for various locations. The eduroam network is designed to enable students from all over the world to log in to worldwide higher education networks with their home-university's login. There should be an option to only verify the root certificate of the signed cert chain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1023277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
@Alfonso Let's put this on the agenda for this weeks' net/telephony meeting. I'm not sure I'm comfortable with releasing your workaround just yet as it introduces latency when the APs are properly configured for roaming. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1478319 Title: Wifi doesn't reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Confirmed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551823] Re: PPTP connection does not work and dies after 2 minutes (on the phone)
** Changed in: network-manager (Ubuntu) Assignee: Tony Espy (awe) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1551823 Title: PPTP connection does not work and dies after 2 minutes (on the phone) Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Status in network-manager-pptp package in Ubuntu: Confirmed Bug description: $ system-image-cli -i current build number: 378 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu last update: 2016-03-01 15:10:52 version version: 378 version ubuntu: 20160301 version device: 20160112 version custom: 20160301 Also confirmed for krillin. Reproduce: 1. Create PPTP connection that you know works (my PPTP connection works on the desktop) 2. Enable it Logs from enabling to “ppp up”: http://pastebin.ubuntu.com/15260269/ What happens: No data flow, can't load anything inside/outside the domain (?) What should happen: Expected this to work, I see a pptp connection in ifconfig [1] Error log from death of pptp connection: http://pastebin.ubuntu.com/15259871/ [1] ppp0 Link encap:Point-to-Point Protocol inet addr:xxx.xxx.xxx.xxx P-t-P:xxx.xxx.xxx.xxx Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1400 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:30658 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1024 (1.0 KB) TX bytes:13791931 (13.7 MB) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1588126] Re: [regression] Adding new wifi networks (with long passwords) never connect at all in OTA-11 and OTA-12
Added an 'Ubuntu RTM' task for network-manager to be clearer about where
the fix lands ( ie. in the overlay PPA, not the archive ).
** Also affects: network-manager (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu RTM)
Status: New => Fix Committed
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: network-manager (Ubuntu RTM)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Assignee: Tony Espy (awe) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1588126
Title:
[regression] Adding new wifi networks (with long passwords) never
connect at all in OTA-11 and OTA-12
Status in Canonical System Image:
Fix Committed
Status in indicator-network package in Ubuntu:
Invalid
Status in network-manager package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu RTM:
Fix Committed
Bug description:
I've just flashed clean images of OTA-11 from the stable channel onto
a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
phones can see the wifi networks but can't connect to any of them any
more.
The wifi networks continue to work for non-Ubuntu devices.
Also, forcefully flashing a device with OTA-10 fixes the problem. The
regression began in OTA-11.
Explanation:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1588126] Re: [regression] [OTA-11] Adding new wifi networks (with long passwords) never connect at all since OTA-11
The fix is currently in silo 005, and was just marked 'Lander Approved'. The version containing the fix will be 1.2.2-0ubuntu1~xenial3, and should hopefully land in the next few days. ** Changed in: network-manager (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1588126 Title: [regression] [OTA-11] Adding new wifi networks (with long passwords) never connect at all since OTA-11 Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Committed Bug description: I've just flashed clean images of OTA-11 from the stable channel onto a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the phones can see the wifi networks but can't connect to any of them any more. The wifi networks continue to work for non-Ubuntu devices. Also, forcefully flashing a device with OTA-10 fixes the problem. The regression began in OTA-11. Explanation: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1588126] Re: [regression] [OTA-11] Adding new wifi networks (with long passwords) never connect at all since OTA-11
** Changed in: network-manager (Ubuntu) Status: Confirmed => In Progress ** Changed in: indicator-network (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1588126 Title: [regression] [OTA-11] Adding new wifi networks (with long passwords) never connect at all since OTA-11 Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: In Progress Bug description: I've just flashed clean images of OTA-11 from the stable channel onto a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the phones can see the wifi networks but can't connect to any of them any more. The wifi networks continue to work for non-Ubuntu devices. Also, forcefully flashing a device with OTA-10 fixes the problem. The regression began in OTA-11. Explanation: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1587808] Re: Ubuntu-emulator no network on latest image
The attached script prevents the route flush from occurring when the hostname is set. This script is owned by lxc-android-config, so I'll add a new task to the bug. Note, we may even want to make additional changes to that this script doesn't flush then routing table on VPN events. I made an attempt to do this ( ie. added an additional check for the prefix "vpn-" when checking $status ), but was having trouble getting it working. The attached change just prevents it from running when the hostname is set, which is what's causing the emulator regression. ** Attachment added: "02default_route_workaround" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1587808/+attachment/4708304/+files/02default_route_workaround ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc-android-config (Ubuntu) Status: New => In Progress ** Changed in: network-manager (Ubuntu) Status: In Progress => Invalid ** Changed in: lxc-android-config (Ubuntu) Assignee: (unassigned) => Tony Espy (awe) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image Status in Canonical System Image: In Progress Status in lxc-android-config package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Invalid Status in phablet-tools package in Ubuntu: Invalid Bug description: STEPS: 1. run sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu rc-test 2. run ubuntu-emulator-run rc-test EXPECTED: Expected I expect there to be a mock sim installed and a network connection ACTUAL: You get the message from the wizard saying there is no sim installed and from the running setup you can not connect to the network. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1587808] Re: Ubuntu-emulator no network on latest image
So... a long time ago, when Ubuntu Touch was first being developed, we hit a bug with certain rild implementations that would configure the routing table when a data call was established, and this caused problems with NM's routing logic. The workaround was the creation of a NM dispatcher script called 02default_route_workaround, which runs the following command when triggered: ip route flush proto boot This clears any pre-existing routes, and let's NM be the master of the routing table. As you can imagine, this doesn't play well with externally managed devices which may have created default routes. I confirmed that this script was the culprit by adding a logger statement to log when the script gets called to syslog. By dumping the script args ( $1 == interface, $2 == status ), I determined that the script was being called with 'interface=none' and 'status=hostname'. I compared NM 0.9.10x to the 1.2.2, and turns out there's a difference in how the hostname is set. In 0.9.10x, setting the hostname is handled by one of the settings plugins. On an Ubuntu system this is either ifupdown or the keyfile settings plugins, neither of which trigger the dispatcher scripts. In NM 1.2.2, setting the hostname is no longer handled by the settings plugins, and is now instead handled by the core NMPolicy class. The static function settings_set_hostname_cb additionally triggers a call to nm_dispatcher_call with action=hostname. This fix is to modify 02default_route_workaround to prevent the route flush from occurring if 'status=hostname'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image Status in Canonical System Image: In Progress Status in lxc-android-config package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Invalid Status in phablet-tools package in Ubuntu: Invalid Bug description: STEPS: 1. run sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu rc-test 2. run ubuntu-emulator-run rc-test EXPECTED: Expected I expect there to be a mock sim installed and a network connection ACTUAL: You get the message from the wizard saying there is no sim installed and from the running setup you can not connect to the network. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1587808] Re: Ubuntu-emulator no network on latest image
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Tony Espy (awe) ** Changed in: phablet-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: network-manager (Ubuntu) Status: New => In Progress ** Changed in: network-manager (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: In Progress Status in phablet-tools package in Ubuntu: Invalid Bug description: STEPS: 1. run sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu rc-test 2. run ubuntu-emulator-run rc-test EXPECTED: Expected I expect there to be a mock sim installed and a network connection ACTUAL: You get the message from the wizard saying there is no sim installed and from the running setup you can not connect to the network. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1597681] Re: [CTA] Enable WAPI support
** Changed in: network-manager (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1597681 Title: [CTA] Enable WAPI support Status in Canonical System Image: In Progress Status in indicator-network package in Ubuntu: In Progress Status in network-manager package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: The phone does not currently support WAPI [1] It should do so. As part of this, support for the SMS4 [2] cipher is also required. [1] https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure [2]: https://en.wikipedia.org/wiki/SMS4 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589489] Re: cannot connect to known Wi-Fi after OTA-11
I just updated bug #1593686 ( WPA-PSK limit introduced in OTA11 ) with the root cause which confirms Pete's theory about timeouts. That said, *if* a user had successfully connected to an AP prior to the update to OTA11. This *shouldn't* have caused issues, as the psk would already have been present in the connection file, and it should've just worked. If further problems are reported, checking the length of the user's passphrase should be suggested. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589489 Title: cannot connect to known Wi-Fi after OTA-11 Status in Canonical System Image: New Status in network-manager package in Ubuntu: Confirmed Bug description: We're receiving many customer cases where after updating to OTA-11 they cannot connect to their known or saved Wi-FI AP's. The most common behaviour is that M10 ask indefinitely for password when it is supoused to be saved previously. I guess this is about network manager that has been updated in OTA-11 What we are asking the customer for: 1º Forget the network through the UI Settings>Wi-Fi and connect to it again as if was the first time. 2º Try to connect another Wi-Fi AP not saved previously 3º Factory data reset(but we haven't recommend it yet) Please let us know which logs do you need and we'll try to reproduce it with our units. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1589489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11
I just confirmed that this is a regression is caused by the final deprecation of dbus-glib in NM 1.2x, and it's replacement by gdbus. As part of this work, the code which requests secrets from a secret-agent, now uses code generated from the introspection XML to make the actual DBus method call. As this generated function doesn't have a parameter to allow the client to specify a timeout, the default ( ~25s ) gets used. This contrasts to the old code which explicitly specified a 120s timeout as a parameter to dbus_g_proxy_begin_call_with_timeout(). So, if the user types the passphrase ( or 64-char hex key ) in < ~25s, the connection should work. The maximum length passphrase ( repeating blocks of '1234567890' ) is ~40 characters before the timeout makes it impossible to type anything longer. An upstream bug had been reported and is currently in-progress: https://bugzilla.gnome.org/show_bug.cgi?id=767321 Currently the only workaround for this is to manually update the system connection file for the AP with the psk and restart the device. It then should be possible to tap the access point in the WiFi list, and as long as the passphrase is correct in the connection file, NM should reconnect to the network automatically when available. You can accomplish this by stopping NM on the device and editing the connection file directly, or copying the connection file from the device, editing, and pushing it back ( via adb ). System connection files are found in the directory /etc/NetworkManager/system-connections. I've verified with a krillin running OTA11 that passphrases up to 63 characters work correctly once they've been pre-populated in a connection file. I haven't yet verified a 64-character hex key, but will make sure this is tested as well before we release the final fix. ** Bug watch added: GNOME Bug Tracker #767321 https://bugzilla.gnome.org/show_bug.cgi?id=767321 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1593686 Title: Wi-Fi passphrase limit introduced in OTA-11 Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS 12.4-25d.JA2) stopped working, possibly due to the length of the WPA pass-phrase, which was 29 characters long. The pass-phrase requirement is from 8 to 63 characters. After reducing the pass- phrase to 14 (and sometimes 15) characters connectivity is restored. Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both 802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot connect. The pass-phrase length requirement on both radios is 18 to 128 characters. In both cases the Cisco APs do not log any event. Prior to OTA 11 connectivity worked normally on OTA 10.1 OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11
** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed => Invalid ** Changed in: canonical-devices-system-image Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1593686 Title: Wi-Fi passphrase limit introduced in OTA-11 Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS 12.4-25d.JA2) stopped working, possibly due to the length of the WPA pass-phrase, which was 29 characters long. The pass-phrase requirement is from 8 to 63 characters. After reducing the pass- phrase to 14 (and sometimes 15) characters connectivity is restored. Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both 802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot connect. The pass-phrase length requirement on both radios is 18 to 128 characters. In both cases the Cisco APs do not log any event. Prior to OTA 11 connectivity worked normally on OTA 10.1 OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected
@Andrea Can you provide the info requested on comment #25 too? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: [touch] Internet connection stops working while WiFi is still connected Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: In Progress Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: I don't have a recipe, but here's what usually happens on my phone 1) I connect to the office WiFi (Canonical's HQ, BlueFin office) 2) Use browser, perform random google searches to check internet is working 3) After a while (sometimes I put the phone to sleep, sometimes I checked the Updates from system settings a few times), I go back to the browser, and it starts returning "Network Error". NM, as you can see from the logs, says WiFi is "connected" 4) At this point I use Terminal app and discover that "ping 8.8.8.8" is working correctly, "ping google.com" immediately returns "unkown host", i.e. it doesn't seem to be waiting for a timeout, it returns pretty fast. There are no related crash files in /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected
@Andrea There are two tests I'd like you to run for me. First, let's verify the baseline by flashing OTA10 ( pre-NM 1.1.93 landing ) on a spare krillin, and then set the WiFi connection to the opposite as earlier suggested, this time setting ipv4.method to ignore. This will validate that IPv6 connections were actually working ( vs. just not causing DNS to fail ), even though the kernels lack support for IPv6 peer addresses ( which NM 1.2x always uses when adding IPv6 addresses, and which in turn always fail ). Second, there are three cases currently that I can see where NM adds IPv6 addresses ( note, there are more possible, but these are the most common when method=auto ): - NM always configures an IPv6 Link Local address with the peer set to the "Any" address ( all zeros or :: ); the code states that a LL address is always added for any method other than "ignore" - a VPN configuration specifies an IPv6 address ( in this case, our VPN always sets the peer with the interface identifier part of the address set to ::1/64 ) - an address is received via RDP ( router discovery protocol ); this is the case that happens when you associate to an AP that supports IPv6 and method=auto As I can't reproduce the last case ( my ISP doesn't support IPv6 yet ), it would be great if you could run NetworkManager in the foreground with an env var specified which triggers netlink debug messages. This will let me see what peer_address is being set when you connect to the work AP. If you want to send me these traces privately, that might be best. Please use a recent rc-proposed image. Here are the steps: 1. From system-settings::wifi, "forget" the access point 2. adb into the phone, and start an interactive sudo session: # sudo -i 3. Stop NM # stop network-manager 4. Run the script command to capture output: # script nm-nl.out 5. Start NetworkManager in the foreground like this: # NLCB=debug /usr/sbin/NetworkManager -n -d --log-level=debug --log- domains=ip6,wifi,vpn 6. From the indicator, connect to the AP 7. Leave the connection up and NM running for 5-10m 8. Kill NM via Ctl-C 9. Exit the script via Ctl-D 10. Grab the script output and send it to me direct, or put on a fileshare Please let me know if you have any questions, or want to discuss before you try any of this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: [touch] Internet connection stops working while WiFi is still connected Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: In Progress Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: I don't have a recipe, but here's what usually happens on my phone 1) I connect to the office WiFi (Canonical's HQ, BlueFin office) 2) Use browser, perform random google searches to check internet is working 3) After a while (sometimes I put the phone to sleep, sometimes I checked the Updates from system settings a few times), I go back to the browser, and it starts returning "Network Error". NM, as you can see from the logs, says WiFi is "connected" 4) At this point I use Terminal app and discover that "ping 8.8.8.8" is working correctly, "ping google.com" immediately returns "unkown host", i.e. it doesn't seem to be waiting for a timeout, it returns pretty fast. There are no related crash files in /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565717] Re: No connection after returning from area without coverage
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1565717
Title:
No connection after returning from area without coverage
Status in Canonical System Image:
In Progress
Status in network-manager package in Ubuntu:
Fix Committed
Bug description:
After moving in an out of my own "faraday cage" an ubuntu phone, NM
got into an state where *both* WiFi and cellular data were
disconnected and NM was not able to recover.
* This still happens with network-manager 1.1.93-0ubuntu1~vivid3, in
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 336
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-05-17 09:19:51
version version: 336
version ubuntu: 20160517
version device: 20160329-a9bacdb
version custom: 20160505-975-38-9
Originally reported for:
NM version:
network-manager 0.9.10.0-4ubuntu15.1.11
root@ubuntu-phablet:/home/phablet# system-image-cli -i
current build number: 298
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-03-30 16:58:21
version version: 298
version ubuntu: 20160330
version device: 20160323-1467d3c
version custom: 20160324--36-54-vivid
phablet@ubuntu-phablet:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ril_0gsm connecting (prepare) /214050030479893/context1
wlan0wifi disconnected --
ril_1gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
ip6tnl0 unknown unmanaged --
sit0 unknown unmanaged --
tunl0unknown unmanaged --
phablet@ubuntu-phablet:~$ nmcli c
NAME UUID TYPE
DEVICE
WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
/234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
/214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
/214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
/214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
Settings = { Gateway=10.50.83.25
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
Name = Pepephone
Type = internet
AccessPointName = gprs.pepephone.com
Active = 1
Protocol = ip
AuthenticationMethod = chap
Password =
Preferred = 0
Username =
IPv6.Settings = { }
[ /ril_0/context2 ]
Name = MMS Pepephone
Type = mms
Active = 0
Settings = { }
MessageCenter = http://www.pepephone.com
MessageProxy = 10.138.255.43:8080
Preferred = 0
Password =
AccessPointName = gprs.pepephone.com
Protocol = ip
AuthenticationMethod = chap
Username =
IPv6.Settings = { }
phablet@ubuntu-phablet:~$ ifconfig
ccmni0Link encap:Ethernet HWaddr 46:23:7c:fb:73:cb
inet addr:10.50.83.25 Mask:255.0.0.0
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:603432 (603.4 KB) TX bytes:193513 (193.5 KB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11189 errors:0 dropped:0 overruns:0 frame:0
TX packets:11189 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1733281 (1.7 MB) TX bytes:1733281 (1.7 MB)
wlan0 Link encap:Ethernet HWaddr b8:64:91:47:21:b6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3184 errors:0 dropped:0 overruns:0 frame:0
TX packets:1626 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:308130 (308.1 KB) TX bytes:172906 (172.9 KB)
phablet@ubuntu-phablet:~$
[Desktop-packages] [Bug 1579098] Re: [touch] Mobile data connection drops, and doesn't automatically reconnect
** Changed in: network-manager (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579098 Title: [touch] Mobile data connection drops, and doesn't automatically reconnect Status in Canonical System Image: In Progress Status in network-manager package in Ubuntu: Fix Committed Bug description: Krillin, rc-proposed, r325 In the last couple of weeks it often happened that the mobile data connection dropped without reconnecting afterwards. I often find my device without mobile data connection without apparent reason. Switching mobile data connection Off and back On from settings restores the connection. I don't have any useful additional info to provide, unfortunately. Please let me know if you need log/cmd output in particular. phablet@ubuntu-phablet:~$ nmcli d status DEVICE TYPE STATE CONNECTION ril_1gsm disconnected -- wlan0wifi disconnected -- ril_0gsm unavailable -- ifb0 ifb unmanaged -- ifb1 ifb unmanaged -- ip6tnl0 ip6tnlunmanaged -- sit0 iptunnel unmanaged -- lo loopback unmanaged -- tunl0unknown unmanaged -- Syslog since last time mobile data was connected: http://pastebin.ubuntu.com/16259803/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1594938] Re: [arale] Hotspot activation doesn't always work
** Attachment added: "Screenshot of Hotspot setup dialog" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594938/+attachment/4688157/+files/hotspot-spinning.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1594938 Title: [arale] Hotspot activation doesn't always work Status in Canonical System Image: New Status in network-manager package in Ubuntu: New Bug description: Although the hotspot logic was vastly improved in OTA11, there are still intermittent issues with enabling hotspot on arale. On a freshly flashed phone running rc-proposed / 356, when I first attempt to setup a hotspot, when I click the "Start" button, the spinner shows up and the hotspot never actually starts ( see attached screenshot ). I was then able to cancel the dialog and enable hotspot via the toggle switch. The correct icon was shown on the panel, and the hotspot was visible from other devices. Note, the only change I made to the configuration was to change the default password to "12345678" ( the minimum length WPA-PSK passphrase ). Here's my image details: current build number: 356 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2016-06-21 14:39:34 version version: 356 version ubuntu: 20160621 version device: 20160526-af18709 version custom: 20160504-975-19-6 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1594938] Re: [arale] Hotspot activation doesn't always work
** Attachment added: "indicator-network log file from arale after start failed" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594938/+attachment/4688158/+files/indicator-network.log ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1594938 Title: [arale] Hotspot activation doesn't always work Status in Canonical System Image: New Status in network-manager package in Ubuntu: New Bug description: Although the hotspot logic was vastly improved in OTA11, there are still intermittent issues with enabling hotspot on arale. On a freshly flashed phone running rc-proposed / 356, when I first attempt to setup a hotspot, when I click the "Start" button, the spinner shows up and the hotspot never actually starts ( see attached screenshot ). I was then able to cancel the dialog and enable hotspot via the toggle switch. The correct icon was shown on the panel, and the hotspot was visible from other devices. Note, the only change I made to the configuration was to change the default password to "12345678" ( the minimum length WPA-PSK passphrase ). Here's my image details: current build number: 356 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2016-06-21 14:39:34 version version: 356 version ubuntu: 20160621 version device: 20160526-af18709 version custom: 20160504-975-19-6 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1594938] [NEW] [arale] Hotspot activation doesn't always work
Public bug reported: Although the hotspot logic was vastly improved in OTA11, there are still intermittent issues with enabling hotspot on arale. On a freshly flashed phone running rc-proposed / 356, when I first attempt to setup a hotspot, when I click the "Start" button, the spinner shows up and the hotspot never actually starts ( see attached screenshot ). I was then able to cancel the dialog and enable hotspot via the toggle switch. The correct icon was shown on the panel, and the hotspot was visible from other devices. Note, the only change I made to the configuration was to change the default password to "12345678" ( the minimum length WPA-PSK passphrase ). Here's my image details: current build number: 356 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2016-06-21 14:39:34 version version: 356 version ubuntu: 20160621 version device: 20160526-af18709 version custom: 20160504-975-19-6 ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1594938 Title: [arale] Hotspot activation doesn't always work Status in Canonical System Image: New Status in network-manager package in Ubuntu: New Bug description: Although the hotspot logic was vastly improved in OTA11, there are still intermittent issues with enabling hotspot on arale. On a freshly flashed phone running rc-proposed / 356, when I first attempt to setup a hotspot, when I click the "Start" button, the spinner shows up and the hotspot never actually starts ( see attached screenshot ). I was then able to cancel the dialog and enable hotspot via the toggle switch. The correct icon was shown on the panel, and the hotspot was visible from other devices. Note, the only change I made to the configuration was to change the default password to "12345678" ( the minimum length WPA-PSK passphrase ). Here's my image details: current build number: 356 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2016-06-21 14:39:34 version version: 356 version ubuntu: 20160621 version device: 20160526-af18709 version custom: 20160504-975-19-6 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579098] Re: [touch] Mobile data connection drops, and doesn't automatically reconnect
** Changed in: network-manager (Ubuntu) Status: Confirmed => In Progress ** Changed in: canonical-devices-system-image Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579098 Title: [touch] Mobile data connection drops, and doesn't automatically reconnect Status in Canonical System Image: In Progress Status in network-manager package in Ubuntu: In Progress Bug description: Krillin, rc-proposed, r325 In the last couple of weeks it often happened that the mobile data connection dropped without reconnecting afterwards. I often find my device without mobile data connection without apparent reason. Switching mobile data connection Off and back On from settings restores the connection. I don't have any useful additional info to provide, unfortunately. Please let me know if you need log/cmd output in particular. phablet@ubuntu-phablet:~$ nmcli d status DEVICE TYPE STATE CONNECTION ril_1gsm disconnected -- wlan0wifi disconnected -- ril_0gsm unavailable -- ifb0 ifb unmanaged -- ifb1 ifb unmanaged -- ip6tnl0 ip6tnlunmanaged -- sit0 iptunnel unmanaged -- lo loopback unmanaged -- tunl0unknown unmanaged -- Syslog since last time mobile data was connected: http://pastebin.ubuntu.com/16259803/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected
** Changed in: network-manager (Ubuntu) Status: Incomplete => In Progress ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Tony Espy (awe) ** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: [touch] Internet connection stops working while WiFi is still connected Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: In Progress Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: I don't have a recipe, but here's what usually happens on my phone 1) I connect to the office WiFi (Canonical's HQ, BlueFin office) 2) Use browser, perform random google searches to check internet is working 3) After a while (sometimes I put the phone to sleep, sometimes I checked the Updates from system settings a few times), I go back to the browser, and it starts returning "Network Error". NM, as you can see from the logs, says WiFi is "connected" 4) At this point I use Terminal app and discover that "ping 8.8.8.8" is working correctly, "ping google.com" immediately returns "unkown host", i.e. it doesn't seem to be waiting for a timeout, it returns pretty fast. There are no related crash files in /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565717] Re: No connection after returning from area without coverage
OK, so there are two low-level problems:
1. InProgress error returned by SetProperty('Active',true) call to ofono
for a gprs-context.
Alfonso's first syslog shows that this can happen, but I'm not sure
exactly how to reproduce. NM would've had to start activation, then
Attached bounced down and back up again, without ofono canceling the
context activation. The next time NM tried to activate, in theory it'd
be returned InProgress.
Right now, NMModemOfono::stage1_prepare_done() always emits a failed
MODEM_PREPARE_RESULT for any error returned by ofono in response to the
SetProperty call.
The fix is to check explicitly for error == InProgress, and just return
without emitting a result ( this is the same thing that happens if no
error is returned ).
2. The context in question is already active.
This can be reproduced by killing NetworkManager, when it restarts, it
gets stuck in the Prepare stage.
This is because ofono doesn't send an error if SetProperty('Active',
true) would have no effect on the property's value ( ie. if it's already
true ). Furthermore, as the context 'Settings' property is already
populated, context_property_changed() is never invoked for the
'Settings', so a MODEM_PREPARE_RESULT is never sent, true or false, so
the device is stuck in PREPARE state.
The fix involves the following changes to NMModemOfono:
do_context_activate() should check the cached value of 'Active', and if
true, should call a new function called process_context_settings(),
which should be based on the current context_property_changed(). This
will result in a PREPARE_RESULT being generated, and thus the device
should no longer get stuck in PREPARE state.
In theory this should work, as NM should just deal with any EEXISTS
errors when it tries to re-configure the IP address, routing table
entries, and DNS nameservers. It this *doesn't* just work, then we may
need some upstream assistance.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1565717
Title:
No connection after returning from area without coverage
Status in Canonical System Image:
Confirmed
Status in network-manager package in Ubuntu:
In Progress
Bug description:
After moving in an out of my own "faraday cage" an ubuntu phone, NM
got into an state where *both* WiFi and cellular data were
disconnected and NM was not able to recover.
* This still happens with network-manager 1.1.93-0ubuntu1~vivid3, in
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 336
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-05-17 09:19:51
version version: 336
version ubuntu: 20160517
version device: 20160329-a9bacdb
version custom: 20160505-975-38-9
Originally reported for:
NM version:
network-manager 0.9.10.0-4ubuntu15.1.11
root@ubuntu-phablet:/home/phablet# system-image-cli -i
current build number: 298
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-03-30 16:58:21
version version: 298
version ubuntu: 20160330
version device: 20160323-1467d3c
version custom: 20160324--36-54-vivid
phablet@ubuntu-phablet:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ril_0gsm connecting (prepare) /214050030479893/context1
wlan0wifi disconnected --
ril_1gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
ip6tnl0 unknown unmanaged --
sit0 unknown unmanaged --
tunl0unknown unmanaged --
phablet@ubuntu-phablet:~$ nmcli c
NAME UUID TYPE
DEVICE
WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
/234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
/214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
/214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
/214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
Settings = { Gateway=10.50.83.25
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
Name = Pepephone
Type = internet
AccessPointName = gprs.pepephone.com
Active
[Desktop-packages] [Bug 1565717] Re: No connection after returning from area without coverage
@Pat
The reason I asked was that two of the three scenarios listed by Alfonso
in the bug involved a crash or restart of NetworkManager, and the
resulting state was that the mobile data connection gets stuck trying to
activate an already active ( or activating ) connection.
I wasn't sure if he was able to reproduce this exact scenario with the
faraday scenario. Looking at his syslog in comment #1, I see that it
did end up in the state. I think it's just harder a smaller window to
hit ( ie. the signal loss has to line up timing-wise with the activation
attempt ).
I added comments to bug #1579098 re: the fact that I can reproduce it,
and have a pending fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1565717
Title:
No connection after returning from area without coverage
Status in Canonical System Image:
Confirmed
Status in network-manager package in Ubuntu:
In Progress
Bug description:
After moving in an out of my own "faraday cage" an ubuntu phone, NM
got into an state where *both* WiFi and cellular data were
disconnected and NM was not able to recover.
* This still happens with network-manager 1.1.93-0ubuntu1~vivid3, in
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 336
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-05-17 09:19:51
version version: 336
version ubuntu: 20160517
version device: 20160329-a9bacdb
version custom: 20160505-975-38-9
Originally reported for:
NM version:
network-manager 0.9.10.0-4ubuntu15.1.11
root@ubuntu-phablet:/home/phablet# system-image-cli -i
current build number: 298
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-03-30 16:58:21
version version: 298
version ubuntu: 20160330
version device: 20160323-1467d3c
version custom: 20160324--36-54-vivid
phablet@ubuntu-phablet:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ril_0gsm connecting (prepare) /214050030479893/context1
wlan0wifi disconnected --
ril_1gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
ip6tnl0 unknown unmanaged --
sit0 unknown unmanaged --
tunl0unknown unmanaged --
phablet@ubuntu-phablet:~$ nmcli c
NAME UUID TYPE
DEVICE
WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
/234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
/214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
/214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
/214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
Settings = { Gateway=10.50.83.25
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
Name = Pepephone
Type = internet
AccessPointName = gprs.pepephone.com
Active = 1
Protocol = ip
AuthenticationMethod = chap
Password =
Preferred = 0
Username =
IPv6.Settings = { }
[ /ril_0/context2 ]
Name = MMS Pepephone
Type = mms
Active = 0
Settings = { }
MessageCenter = http://www.pepephone.com
MessageProxy = 10.138.255.43:8080
Preferred = 0
Password =
AccessPointName = gprs.pepephone.com
Protocol = ip
AuthenticationMethod = chap
Username =
IPv6.Settings = { }
phablet@ubuntu-phablet:~$ ifconfig
ccmni0Link encap:Ethernet HWaddr 46:23:7c:fb:73:cb
inet addr:10.50.83.25 Mask:255.0.0.0
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:603432 (603.4 KB) TX bytes:193513 (193.5 KB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11189 errors:0
[Desktop-packages] [Bug 1579098] Re: [touch] Mobile data connection drops, and doesn't automatically reconnect
I'm able to reproduce this on arale ( rc-proposed, 334 ) by either toggling cellular technology ( 2/3g -> 2g only, and back ), or by putting the device into a faraday cage. This is partially a regression in 1.1.93 ( we dropped a related patch ), and partially a day-one problem. I have what looks to be a promising fix, but would like to discuss with upstream before I land it in the silo. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579098 Title: [touch] Mobile data connection drops, and doesn't automatically reconnect Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Krillin, rc-proposed, r325 In the last couple of weeks it often happened that the mobile data connection dropped without reconnecting afterwards. I often find my device without mobile data connection without apparent reason. Switching mobile data connection Off and back On from settings restores the connection. I don't have any useful additional info to provide, unfortunately. Please let me know if you need log/cmd output in particular. phablet@ubuntu-phablet:~$ nmcli d status DEVICE TYPE STATE CONNECTION ril_1gsm disconnected -- wlan0wifi disconnected -- ril_0gsm unavailable -- ifb0 ifb unmanaged -- ifb1 ifb unmanaged -- ip6tnl0 ip6tnlunmanaged -- sit0 iptunnel unmanaged -- lo loopback unmanaged -- tunl0unknown unmanaged -- Syslog since last time mobile data was connected: http://pastebin.ubuntu.com/16259803/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected
@Andrea Can you try adding the following setting to the NetworkManager connection file for "Canonical-2.4GHz-g" in /etc/NetworkManager/system- connections: [ipv6] method=ignore "[ipv6]" should already be there, so just add "method=ignore", and remove any other settings under "ipv6". Restart the device once you've updated the connection file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: [touch] Internet connection stops working while WiFi is still connected Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: I don't have a recipe, but here's what usually happens on my phone 1) I connect to the office WiFi (Canonical's HQ, BlueFin office) 2) Use browser, perform random google searches to check internet is working 3) After a while (sometimes I put the phone to sleep, sometimes I checked the Updates from system settings a few times), I go back to the browser, and it starts returning "Network Error". NM, as you can see from the logs, says WiFi is "connected" 4) At this point I use Terminal app and discover that "ping 8.8.8.8" is working correctly, "ping google.com" immediately returns "unkown host", i.e. it doesn't seem to be waiting for a timeout, it returns pretty fast. There are no related crash files in /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected
So from @Andrea's latest pastebin: - NM shows both modem and wlan0 as connected - syslog shows one DHCP renewal period - a do-add-ip4-address error is logged, however the IP address is still configured ( ip addr show confirms this ); need to investigate whether the error log message is correct, and possible adjust the text of the message - dnsmasq has four nameservers configured ( wlan0: ipv4 & ipv6; modem: two ipv4 ) - the internet is reachable, as 8.8.8.8 can be pinged - DNS lookups fail ( ping google.com responds with 'unknown host' ) - the DHCP lease interval appears to be just shy of 10m ( 571s ) - the problem seems to occur after the lease renewal - the device may have been asleep between the time the WiFi connection was working and the failure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: [touch] Internet connection stops working while WiFi is still connected Status in Canonical System Image: New Status in network-manager package in Ubuntu: Incomplete Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: I don't have a recipe, but here's what usually happens on my phone 1) I connect to the office WiFi (Canonical's HQ, BlueFin office) 2) Use browser, perform random google searches to check internet is working 3) After a while (sometimes I put the phone to sleep, sometimes I checked the Updates from system settings a few times), I go back to the browser, and it starts returning "Network Error". NM, as you can see from the logs, says WiFi is "connected" 4) At this point I use Terminal app and discover that "ping 8.8.8.8" is working correctly, "ping google.com" immediately returns "unkown host", i.e. it doesn't seem to be waiting for a timeout, it returns pretty fast. There are no related crash files in /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565717] Re: No connection after returning from area without coverage
@Alfsonso
One more note, although comment #2 isn't a valid scenario, it does
trigger the same behavior.
The root cause of the bug is that the current NM wwan plugin doesn't
properly handle already activated contexts.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1565717
Title:
No connection after returning from area without coverage
Status in Canonical System Image:
Confirmed
Status in network-manager package in Ubuntu:
In Progress
Bug description:
After moving in an out of my own "faraday cage" an ubuntu phone, NM
got into an state where *both* WiFi and cellular data were
disconnected and NM was not able to recover.
* This still happens with network-manager 1.1.93-0ubuntu1~vivid3, in
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 336
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-05-17 09:19:51
version version: 336
version ubuntu: 20160517
version device: 20160329-a9bacdb
version custom: 20160505-975-38-9
Originally reported for:
NM version:
network-manager 0.9.10.0-4ubuntu15.1.11
root@ubuntu-phablet:/home/phablet# system-image-cli -i
current build number: 298
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-03-30 16:58:21
version version: 298
version ubuntu: 20160330
version device: 20160323-1467d3c
version custom: 20160324--36-54-vivid
phablet@ubuntu-phablet:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ril_0gsm connecting (prepare) /214050030479893/context1
wlan0wifi disconnected --
ril_1gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
ip6tnl0 unknown unmanaged --
sit0 unknown unmanaged --
tunl0unknown unmanaged --
phablet@ubuntu-phablet:~$ nmcli c
NAME UUID TYPE
DEVICE
WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
/234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
/214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
/214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
/214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
Settings = { Gateway=10.50.83.25
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
Name = Pepephone
Type = internet
AccessPointName = gprs.pepephone.com
Active = 1
Protocol = ip
AuthenticationMethod = chap
Password =
Preferred = 0
Username =
IPv6.Settings = { }
[ /ril_0/context2 ]
Name = MMS Pepephone
Type = mms
Active = 0
Settings = { }
MessageCenter = http://www.pepephone.com
MessageProxy = 10.138.255.43:8080
Preferred = 0
Password =
AccessPointName = gprs.pepephone.com
Protocol = ip
AuthenticationMethod = chap
Username =
IPv6.Settings = { }
phablet@ubuntu-phablet:~$ ifconfig
ccmni0Link encap:Ethernet HWaddr 46:23:7c:fb:73:cb
inet addr:10.50.83.25 Mask:255.0.0.0
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:603432 (603.4 KB) TX bytes:193513 (193.5 KB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11189 errors:0 dropped:0 overruns:0 frame:0
TX packets:11189 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1733281 (1.7 MB) TX bytes:1733281 (1.7 MB)
wlan0 Link encap:Ethernet HWaddr b8:64:91:47:21:b6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3184 errors:0 dropped:0 overruns:0
[Desktop-packages] [Bug 1565717] Re: No connection after returning from area without coverage
@Alfonso
The scenario in comment #2 isn't valid. That said, I am able to
reproduce by killing NetworkManager, so I agree this is a valid bug that
needs to be fixed.
@Pat
As Alfonso pointed out, your problem is different, as there's no active
context, nor does NetworkManager appear stuck. Could you please file a
new bug, and if possible nail down the exact steps to reproduce? As
described, it sounds like an indicator bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1565717
Title:
No connection after returning from area without coverage
Status in Canonical System Image:
Confirmed
Status in network-manager package in Ubuntu:
In Progress
Bug description:
After moving in an out of my own "faraday cage" an ubuntu phone, NM
got into an state where *both* WiFi and cellular data were
disconnected and NM was not able to recover.
* This still happens with network-manager 1.1.93-0ubuntu1~vivid3, in
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 336
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-05-17 09:19:51
version version: 336
version ubuntu: 20160517
version device: 20160329-a9bacdb
version custom: 20160505-975-38-9
Originally reported for:
NM version:
network-manager 0.9.10.0-4ubuntu15.1.11
root@ubuntu-phablet:/home/phablet# system-image-cli -i
current build number: 298
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-03-30 16:58:21
version version: 298
version ubuntu: 20160330
version device: 20160323-1467d3c
version custom: 20160324--36-54-vivid
phablet@ubuntu-phablet:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ril_0gsm connecting (prepare) /214050030479893/context1
wlan0wifi disconnected --
ril_1gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
ip6tnl0 unknown unmanaged --
sit0 unknown unmanaged --
tunl0unknown unmanaged --
phablet@ubuntu-phablet:~$ nmcli c
NAME UUID TYPE
DEVICE
WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
/234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
/214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
/214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
/214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
Settings = { Gateway=10.50.83.25
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
Name = Pepephone
Type = internet
AccessPointName = gprs.pepephone.com
Active = 1
Protocol = ip
AuthenticationMethod = chap
Password =
Preferred = 0
Username =
IPv6.Settings = { }
[ /ril_0/context2 ]
Name = MMS Pepephone
Type = mms
Active = 0
Settings = { }
MessageCenter = http://www.pepephone.com
MessageProxy = 10.138.255.43:8080
Preferred = 0
Password =
AccessPointName = gprs.pepephone.com
Protocol = ip
AuthenticationMethod = chap
Username =
IPv6.Settings = { }
phablet@ubuntu-phablet:~$ ifconfig
ccmni0Link encap:Ethernet HWaddr 46:23:7c:fb:73:cb
inet addr:10.50.83.25 Mask:255.0.0.0
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:603432 (603.4 KB) TX bytes:193513 (193.5 KB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11189 errors:0 dropped:0 overruns:0 frame:0
TX packets:11189 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1733281 (1.7 MB) TX bytes:1733281 (1.7 MB)
wlan0 Link encap:Ethernet HWaddr
[Desktop-packages] [Bug 1565717] Re: No connection after returning from area without coverage
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1565717
Title:
No connection after returning from area without coverage
Status in Canonical System Image:
Confirmed
Status in network-manager package in Ubuntu:
In Progress
Bug description:
After moving in an out of my own "faraday cage" an ubuntu phone, NM
got into an state where *both* WiFi and cellular data were
disconnected and NM was not able to recover.
* This still happens with network-manager 1.1.93-0ubuntu1~vivid3, in
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 336
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-05-17 09:19:51
version version: 336
version ubuntu: 20160517
version device: 20160329-a9bacdb
version custom: 20160505-975-38-9
Originally reported for:
NM version:
network-manager 0.9.10.0-4ubuntu15.1.11
root@ubuntu-phablet:/home/phablet# system-image-cli -i
current build number: 298
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-03-30 16:58:21
version version: 298
version ubuntu: 20160330
version device: 20160323-1467d3c
version custom: 20160324--36-54-vivid
phablet@ubuntu-phablet:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ril_0gsm connecting (prepare) /214050030479893/context1
wlan0wifi disconnected --
ril_1gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
ip6tnl0 unknown unmanaged --
sit0 unknown unmanaged --
tunl0unknown unmanaged --
phablet@ubuntu-phablet:~$ nmcli c
NAME UUID TYPE
DEVICE
WLAN_1609 fe9b17ad-88fa-43b7-bcab-8fbc1985ce42
802-11-wireless --
Wireless 98ff5b6f-b0d9-471a-b867-8a7be51e12c2
802-11-wireless --
Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089
802-11-wireless --
/234304107917083/context1 1f192cdc-ccea-2dc3-fa13-619ed3053828 gsm
--
/214321010036211/context1 0992421f-2369-0765-ceaa-ba2a3091e111 gsm
--
/214050030479893/context1 d30e4f19-9d00-ab1f-ab43-6d9c1b628556 gsm
ril_0
/214019301737411/context1 88b28978-e2fc-6336-8665-b0ae78d321ae gsm
--
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
Settings = { Gateway=10.50.83.25
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
Name = Pepephone
Type = internet
AccessPointName = gprs.pepephone.com
Active = 1
Protocol = ip
AuthenticationMethod = chap
Password =
Preferred = 0
Username =
IPv6.Settings = { }
[ /ril_0/context2 ]
Name = MMS Pepephone
Type = mms
Active = 0
Settings = { }
MessageCenter = http://www.pepephone.com
MessageProxy = 10.138.255.43:8080
Preferred = 0
Password =
AccessPointName = gprs.pepephone.com
Protocol = ip
AuthenticationMethod = chap
Username =
IPv6.Settings = { }
phablet@ubuntu-phablet:~$ ifconfig
ccmni0Link encap:Ethernet HWaddr 46:23:7c:fb:73:cb
inet addr:10.50.83.25 Mask:255.0.0.0
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:603432 (603.4 KB) TX bytes:193513 (193.5 KB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11189 errors:0 dropped:0 overruns:0 frame:0
TX packets:11189 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1733281 (1.7 MB) TX bytes:1733281 (1.7 MB)
wlan0 Link encap:Ethernet HWaddr b8:64:91:47:21:b6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3184 errors:0 dropped:0 overruns:0 frame:0
TX packets:1626 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
[Desktop-packages] [Bug 1580146] Re: Internet connection stops working while WiFi is still connected
@Andrea Let's try and work together to get the description of the bug ( including steps to reproduce ) accurate. The initial description was network "stops working" when WiFi is "still connected". This implies the network was actually connected and working before the bug occurred, true? It'd also be nice if we could quantify how long it takes for the network to stop working. Your steps to reproduce in comment #9 state you see a network error the first time you open the browser. So it sounds like you never had a working internet connection this time around. Sounds like two different scenarios? Also, I'm not sure what you mean by "doublecheck that the bug is active using terminal"? If you're running commands to see if the network is active, then please describe what commands you used. Is it possible to attach the full syslog from your device today? Re: access points. Everytime NetworkManager starts up, it reads all of those connection files ( checkout /etc/NetworkManager/system-connections sometime if you're interested ). Whenever WiFi is activated and NM has to decide which access point to associate with, it iterates through it's list of connections for every device. Ideally, there'd be an easy way to 'forget all', but there isn't at the moment. This was just a suggestion that could make things work a little better on your phone, take it or leave it. Re: results; are you only back in the office next Wed ( May 18 )? Re: problems with mobile data ( comment # 3); did you review bug #1533508 yet and/or file a separate bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected Status in network-manager package in Ubuntu: Incomplete Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: Not sure yet... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580146] Re: Internet connection stops working while WiFi is still connected
@Andrea One last thing... did you check for crash files? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected Status in network-manager package in Ubuntu: Incomplete Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: Not sure yet... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580146] Re: Internet connection stops working while WiFi is still connected
@Andrea Re: comment #3, please review bug #1533508, to see if your hitting the same. If not, please file a new bug and include output from /usr/share/ofono/scripts/list-modems and list-contexts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected Status in network-manager package in Ubuntu: Incomplete Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: Not sure yet... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580146] Re: Internet connection stops working while WiFi is still connected
@Andrea Finally, you might also want to consider "forgetting" some of the saved access points on your device. NetworkManager shows a seriously long list of WiFi connections. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected Status in network-manager package in Ubuntu: Incomplete Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: Not sure yet... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580146] Re: Internet connection stops working while WiFi is still connected
@Andrea Let's keep this bug specific to the original problem described. Does this problem only occur at the office? Can you reproduce it reliably? If so, how long after you initially connect does it take to manifest itself? >From what you provided in your initial pastebin, both the indicator and NetworkManager show wlan0 connected to the office access point. You also stated that you could ping 8.8.8.8, but that 'ping google.com' returned 'unknown host'. The new version of NM now logs the IPv4 details when an IP address is assigned and/or renewed. One possibility here is that lease renewal is not working properly. So, if/when this problem happens again, please provide the following: 1) the entire syslog 2) the output of 'iw add show wlan0' 3) the output of 'ip route' If you again can ping IPv4 addresses on the internet, but can't resolve hostnames, then let's checkout the dnsmasq configuration. To do this, run the following command: $ sudo kill -SIGUSR1 `pidof dnsmasq` This causes dnsmasq to write its current configured nameservers to the syslog, so after sending the signal, grep for "dnsmasq" in syslog and look for the lines like these: May 12 19:55:35 ubuntu-phablet dnsmasq[2048]: server 192.168.1.1#53: queries sent 19, retried or failed 0 Also, in the future, it's better to include requested information ( output from commands, syslog, ... ) directly in comments or attachments vs. using pastebin. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected Status in network-manager package in Ubuntu: Incomplete Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: Not sure yet... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580146] Re: Internet connection stops working while WiFi is still connected
** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected Status in network-manager package in Ubuntu: Incomplete Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: Not sure yet... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579915] Re: network-manager 1.2 uses more power
** Changed in: network-manager (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power Status in Canonical System Image: Fix Committed Status in network-manager package in Ubuntu: Fix Released Bug description: On krillin and arale, power use went up significantly in new builds starting on May 4. So far, I have results for: * krillin rc-proposed 324 and 325 * arale rc-proposed 316 and 317 When the radios are off, results are unchanged. However, power went up in two common cases -- standby with all radios enabled, and screen-on with radios enabled. * krillin standby: ~8mA -> ~80mA * arale standby: ~35mA -> ~79mA * krillin screen-on: ~177mA -> ~215mA * arale screen-on: ~305mA -> ~353mA Quite a few things landed in that build, but some of the top suspects are: * network-manager got updated to 1.2 * indicator-network got a cell data switch * USS got "fixes to sleep/idle settings" * ubuntu-push got a fix related to network-manager * libhybris got partial support for wireless display * account-polld got a new calendar plugin Full list: http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog This change cuts typical standby time anywhere from 50% to 90%, so it probably should be fixed before release. However, tests suggest that simply turning off wifi returns the phone to a nice low standby power -- about 6mA for both devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579915] Re: network-manager 1.2 uses more power
Two things I noticed while testing the powersave fix from silo-77: 1) On mako ( rc-proposed / 434 ), iwconfig doesn't report anything at all for powersave. This may be a driver limitation. 2) On frieza ( rc-proposed / 101 ), the powersave period is set to 0, which may be a less than ideal value. This should be investigated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power Status in Canonical System Image: In Progress Status in network-manager package in Ubuntu: In Progress Bug description: On krillin and arale, power use went up significantly in new builds starting on May 4. So far, I have results for: * krillin rc-proposed 324 and 325 * arale rc-proposed 316 and 317 When the radios are off, results are unchanged. However, power went up in two common cases -- standby with all radios enabled, and screen-on with radios enabled. * krillin standby: ~8mA -> ~80mA * arale standby: ~35mA -> ~79mA * krillin screen-on: ~177mA -> ~215mA * arale screen-on: ~305mA -> ~353mA Quite a few things landed in that build, but some of the top suspects are: * network-manager got updated to 1.2 * indicator-network got a cell data switch * USS got "fixes to sleep/idle settings" * ubuntu-push got a fix related to network-manager * libhybris got partial support for wireless display * account-polld got a new calendar plugin Full list: http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog This change cuts typical standby time anywhere from 50% to 90%, so it probably should be fixed before release. However, tests suggest that simply turning off wifi returns the phone to a nice low standby power -- about 6mA for both devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579915] Re: network-manager 1.2 uses more power
I've confirmed that the default powersave patch included in xenial is wrong, as it patches libnm-util which is deprecated, as opposed to patching the new libnm0. I've update the version of NM in the silo for VPN with an updated patch which restores WiFi powersave by default. https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-077/+packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: On krillin and arale, power use went up significantly in new builds starting on May 4. So far, I have results for: * krillin rc-proposed 324 and 325 * arale rc-proposed 316 and 317 When the radios are off, results are unchanged. However, power went up in two common cases -- standby with all radios enabled, and screen-on with radios enabled. * krillin standby: ~8mA -> ~80mA * arale standby: ~35mA -> ~79mA * krillin screen-on: ~177mA -> ~215mA * arale screen-on: ~305mA -> ~353mA Quite a few things landed in that build, but some of the top suspects are: * network-manager got updated to 1.2 * indicator-network got a cell data switch * USS got "fixes to sleep/idle settings" * ubuntu-push got a fix related to network-manager * libhybris got partial support for wireless display * account-polld got a new calendar plugin Full list: http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog This change cuts typical standby time anywhere from 50% to 90%, so it probably should be fixed before release. However, tests suggest that simply turning off wifi returns the phone to a nice low standby power -- about 6mA for both devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1557026] Re: Network Manager sets powersave off by default in xenial
Note, it looks like the problem is that the original patch fixes up the libnm-util version of nm-settings-wireless.c which has been deprecated. Instead the libnm-core version of nm-settings-wireless.c needs to be updated. I'm testing this now for a touch build and will report back here if it works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1557026 Title: Network Manager sets powersave off by default in xenial Status in network-manager package in Ubuntu: Confirmed Bug description: Nwetwork Manager sets Power Management:off in iwconfig by default. It can be changed per connection by adding powersave=1. In 14.04 powersave was set on by default and could be disabled per connection. That seemed to be reasonable. If the default has been changed for some reason, it is better to make a NM global setting. It is not handy to change every connection manually, and most users will not be able to do it. After upgrade to 16.04 power consumption will increase. It is also funny that pm-tools set powersave on, but NM reverts this setting. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.0.4-0ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 14 18:41:38 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-29 (13 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.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.125 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-03-12 (1 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-03-13T01:40:30.748775 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Voxnet eafa9e18-fa85-4d9a-a705-6a3e97a45fbc /org/freedesktop/NetworkManager/ActiveConnection/1 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- 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/1557026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580146] Re: Internet connection stops working while WiFi is still connected
To be clear from discussions with Andrea, the network is accessible, but it appears that DNS isn't working correctly. He's able to ping an IPv4 address, but trying to ping a hostname results in an immediate'unknown host' being displayed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected Status in network-manager package in Ubuntu: New Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: Not sure yet... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1557026] Re: Network Manager sets powersave off by default in xenial
So NM 1.1.93-0ubuntu1 includes the patch default_powersave_on.patch,
which is pretty simple, it just modifies the NMSettingWireless code to
default powersave to 1:
===
--- a/libnm-util/nm-setting-wireless.c
+++ b/libnm-util/nm-setting-wireless.c
@@ -675,7 +675,7 @@ nm_setting_wireless_get_hidden (NMSettin
guint32
nm_setting_wireless_get_powersave (NMSettingWireless *setting)
{
- g_return_val_if_fail (NM_IS_SETTING_WIRELESS (setting), 0);
+ g_return_val_if_fail (NM_IS_SETTING_WIRELESS (setting), 1);
return NM_SETTING_WIRELESS_GET_PRIVATE (setting)->powersave;
}
@@ -885,6 +885,9 @@ verify (NMSetting *setting, GSList *all_
static void
nm_setting_wireless_init (NMSettingWireless *setting)
{
+ NMSettingWirelessPrivate *priv = NM_SETTING_WIRELESS_GET_PRIVATE
(setting);
+
+ priv->powersave = 1;
}
static void
@@ -1283,7 +1286,7 @@ nm_setting_wireless_class_init (NMSettin
g_object_class_install_property
(object_class, PROP_POWERSAVE,
g_param_spec_uint (NM_SETTING_WIRELESS_POWERSAVE, "", "",
- 0, G_MAXUINT32, 0,
+ 0, G_MAXUINT32, 1,
G_PARAM_READWRITE |
G_PARAM_STATIC_STRINGS));
}
...unfortunately, the NM1.2 treats powersave=1 as IGNORE:
/**
* NMSettingWirelessPowersave:
* @NM_SETTING_WIRELESS_POWERSAVE_DEFAULT: use the default value
* @NM_SETTING_WIRELESS_POWERSAVE_IGNORE: don't touch existing setting
* @NM_SETTING_WIRELESS_POWERSAVE_DISABLE: disable powersave
* @NM_SETTING_WIRELESS_POWERSAVE_ENABLE: enable powersave
*
* These flags indicate whether wireless powersave must be enabled.
**/
typedef enum {
NM_SETTING_WIRELESS_POWERSAVE_DEFAULT = 0,
NM_SETTING_WIRELESS_POWERSAVE_IGNORE= 1,
NM_SETTING_WIRELESS_POWERSAVE_DISABLE = 2,
NM_SETTING_WIRELESS_POWERSAVE_ENABLE= 3,
_NM_SETTING_WIRELESS_POWERSAVE_NUM, /*< skip >*/
NM_SETTING_WIRELESS_POWERSAVE_LAST =
_NM_SETTING_WIRELESS_POWERSAVE_NUM - 1, /*< skip >*/
} NMSettingWirelessPowersave;
...and the code in NMDeviceWiFi will only enable powersave if the value
returned from NMSettingWireless is 3:
if (powersave == NM_SETTING_WIRELESS_POWERSAVE_IGNORE)
return;
nm_platform_wifi_set_powersave (NM_PLATFORM_GET,
nm_device_get_ifindex (device),
powersave ==
NM_SETTING_WIRELESS_POWERSAVE_ENABLE);
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1557026
Title:
Network Manager sets powersave off by default in xenial
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Nwetwork Manager sets Power Management:off in iwconfig by default.
It can be changed per connection by adding powersave=1.
In 14.04 powersave was set on by default and could be disabled per connection.
That seemed to be reasonable.
If the default has been changed for some reason, it is better to make a NM
global setting.
It is not handy to change every connection manually, and most users will not
be able to do it.
After upgrade to 16.04 power consumption will increase.
It is also funny that pm-tools set powersave on, but NM reverts this
setting.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.0.4-0ubuntu10
ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1579915] Re: network-manager 1.2 uses more power
@Amr Thanks for the pointer. I just added a comment to bug #1557026 regarding the xenial powersave regression, and it applies to Touch as well. I'm working on an updated patch for Touch, and then will see about SRU'ing for xenial as soon as possible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: On krillin and arale, power use went up significantly in new builds starting on May 4. So far, I have results for: * krillin rc-proposed 324 and 325 * arale rc-proposed 316 and 317 When the radios are off, results are unchanged. However, power went up in two common cases -- standby with all radios enabled, and screen-on with radios enabled. * krillin standby: ~8mA -> ~80mA * arale standby: ~35mA -> ~79mA * krillin screen-on: ~177mA -> ~215mA * arale screen-on: ~305mA -> ~353mA Quite a few things landed in that build, but some of the top suspects are: * network-manager got updated to 1.2 * indicator-network got a cell data switch * USS got "fixes to sleep/idle settings" * ubuntu-push got a fix related to network-manager * libhybris got partial support for wireless display * account-polld got a new calendar plugin Full list: http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog This change cuts typical standby time anywhere from 50% to 90%, so it probably should be fixed before release. However, tests suggest that simply turning off wifi returns the phone to a nice low standby power -- about 6mA for both devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579915] Re: network-manager 1.2 uses more power
Just flashed OTA10 and 'iwconfig wlan0' when associated to an AP shows: Power Management period:2 phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 32 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: On krillin and arale, power use went up significantly in new builds starting on May 4. So far, I have results for: * krillin rc-proposed 324 and 325 * arale rc-proposed 316 and 317 When the radios are off, results are unchanged. However, power went up in two common cases -- standby with all radios enabled, and screen-on with radios enabled. * krillin standby: ~8mA -> ~80mA * arale standby: ~35mA -> ~79mA * krillin screen-on: ~177mA -> ~215mA * arale screen-on: ~305mA -> ~353mA Quite a few things landed in that build, but some of the top suspects are: * network-manager got updated to 1.2 * indicator-network got a cell data switch * USS got "fixes to sleep/idle settings" * ubuntu-push got a fix related to network-manager * libhybris got partial support for wireless display * account-polld got a new calendar plugin Full list: http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog This change cuts typical standby time anywhere from 50% to 90%, so it probably should be fixed before release. However, tests suggest that simply turning off wifi returns the phone to a nice low standby power -- about 6mA for both devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579915] Re: network-manager 1.2 uses more power
@Amr Yes, this could be related to bug #1557026. I checked, and we're including default_powersave_on.patch, however it doesn't appear to be working properly in NM 1.1.93. I just confirmed on krillin ( rc-proposed / 325 ) that even though the device is associated to an AP, iwconfig show 'Power Management:off'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: On krillin and arale, power use went up significantly in new builds starting on May 4. So far, I have results for: * krillin rc-proposed 324 and 325 * arale rc-proposed 316 and 317 When the radios are off, results are unchanged. However, power went up in two common cases -- standby with all radios enabled, and screen-on with radios enabled. * krillin standby: ~8mA -> ~80mA * arale standby: ~35mA -> ~79mA * krillin screen-on: ~177mA -> ~215mA * arale screen-on: ~305mA -> ~353mA Quite a few things landed in that build, but some of the top suspects are: * network-manager got updated to 1.2 * indicator-network got a cell data switch * USS got "fixes to sleep/idle settings" * ubuntu-push got a fix related to network-manager * libhybris got partial support for wireless display * account-polld got a new calendar plugin Full list: http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog This change cuts typical standby time anywhere from 50% to 90%, so it probably should be fixed before release. However, tests suggest that simply turning off wifi returns the phone to a nice low standby power -- about 6mA for both devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579915] Re: network-manager 1.2 uses more power
@Selene Are the devices associated to WiFi access points when the testing is performed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: On krillin and arale, power use went up significantly in new builds starting on May 4. So far, I have results for: * krillin rc-proposed 324 and 325 * arale rc-proposed 316 and 317 When the radios are off, results are unchanged. However, power went up in two common cases -- standby with all radios enabled, and screen-on with radios enabled. * krillin standby: ~8mA -> ~80mA * arale standby: ~35mA -> ~79mA * krillin screen-on: ~177mA -> ~215mA * arale screen-on: ~305mA -> ~353mA Quite a few things landed in that build, but some of the top suspects are: * network-manager got updated to 1.2 * indicator-network got a cell data switch * USS got "fixes to sleep/idle settings" * ubuntu-push got a fix related to network-manager * libhybris got partial support for wireless display * account-polld got a new calendar plugin Full list: http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog This change cuts typical standby time anywhere from 50% to 90%, so it probably should be fixed before release. However, tests suggest that simply turning off wifi returns the phone to a nice low standby power -- about 6mA for both devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579825] Re: IP Address not displayed for wifi access points
@Ken I see the same thing on krillin running rc-proposed / #320. That said, looks like we made a poor choice of properties to use as 'IP4Address' was marked as deprecated as far back as NM 0.9: https://developer.gnome.org/NetworkManager/0.9/spec.html#org.freedesktop.NetworkManager.Device Looks that choice has now bitten us, and the property is no longer being populated on purpose. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579825 Title: IP Address not displayed for wifi access points Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: latest rc-proposed build 319 Open system settings expand the connected access point by pressing right arrow expected results: ip address is displayed actual results: ip address is not displayed, just a label "IP Address" with no value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1579825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579825] Re: IP Address not displayed for wifi access points
I see this on mako running stable / #30 plus the a test version of NetworkManager 1.1.93 that I'm using for the VPN bug #1579222. When I go to the access point details page in system settings, I also see the following message logged to the upstart log file application-legacy- ubuntu-system-settings.log: 2016-05-09 12:36:50,542 - WARNING - Got invalid serialized mime data. Ignoring it. When I go back to the main WiFi settings page, I also alot of the following log messages: 2016-05-09 12:34:24,080 - WARNING - file:///usr/share/ubuntu/settings/system/qml- plugins/wifi/PageComponent.qml:80: TypeError: Cannot read property of null -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1579825 Title: IP Address not displayed for wifi access points Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: latest rc-proposed build 319 Open system settings expand the connected access point by pressing right arrow expected results: ip address is displayed actual results: ip address is not displayed, just a label "IP Address" with no value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1579825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1537913] Re: Active APN is not selected
@Jonas
Nope. NM is responsible for monitoring the 'Preferred' properties of
all the APN/gprs_contexts for a particular SIM *and* enforcing that the
first APN/context found with 'Preferred=true' is activated. NM never
changes the value of 'Preferred'.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1537913
Title:
Active APN is not selected
Status in Canonical System Image:
In Progress
Status in network-manager package in Ubuntu:
New
Status in ubuntu-system-settings package in Ubuntu:
In Progress
Bug description:
The APN panel shows 3 APNs but the active APN is not selected in the UI
MX4 running rc-proposed 230
A krillin running ota 8.5 shows a selected APN
The settings log contains this when viewing the page
2016-01-25 16:06:34,484 - WARNING -
file:///usr/share/ubuntu/settings/system/qml-plugins/cellular/apn_manager.js:50:
Error: Unknown context type
You can see ATT Phone should be selected
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Password =
IPv6.Settings = { }
Settings = { }
Protocol = ip
AccessPointName = nxtgenphone
Type = internet
AuthenticationMethod = chap
MessageProxy = proxy.mobile.att.net:80
Name = ATT Nextgenphone
Username =
Active = 0
Preferred = 0
MessageCenter = http://mmsc.mobile.att.net
[ /ril_0/context2 ]
Password =
IPv6.Settings = { }
Settings = { Gateway=10.244.204.71 Method=static
Address=10.244.204.71 Proxy=172.26.39.1 Interface=ccmni0 ProxyPort=80
DomainNameServers=172.26.38.1,172.26.38.2, Netmask=255.255.255.0 }
Protocol = ip
AccessPointName = phone
Type = internet
AuthenticationMethod = chap
MessageProxy = proxy.mobile.att.net:80
Name = ATT Phone
Username =
Active = 1
Preferred = 0
MessageCenter = http://mmsc.mobile.att.net
[ /ril_0/context3 ]
Password =
IPv6.Settings = { }
Settings = { }
Protocol = ip
AccessPointName = wap.cingular
Type = internet
AuthenticationMethod = chap
MessageProxy = wireless.cingular.com
Name = ATT WAP
Username =
Active = 0
Preferred = 0
MessageCenter = http://mmsc.cingular.com/
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537913/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1569674] Re: [Kubuntu] Fail to connect to wifi after a recent update
@Avishay Can you try removing the 'gateway-ping-timeout' line from one of your connections and retry? From the error you originally reported, it looks like the Plasma networking code is mangling this value and NM complains... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1569674 Title: [Kubuntu] Fail to connect to wifi after a recent update Status in network-manager package in Ubuntu: Confirmed Bug description: I installed the recent updates in the Update Manager and after rebooting I wasn't able to connect to my wifi network anymore. It attempts to connect to the network and fails with the following error message: Failed to update connection [network name] connection.gateway-ping-timeout: can not set property: value "46730064" of type 'guint' is invalid or out of range for property 'gateway-ping-timeout' of type 'guint' I am able to use wired connection. 1. release: Description:Ubuntu Xenial Xerus (development branch) Release:16.04 2. network-manager version: network-manager: Installed: 1.1.93-0ubuntu3 Candidate: 1.1.93-0ubuntu3 Version table: *** 1.1.93-0ubuntu3 500 500 http://il.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected the machine to connect to wifi as always 4. it failed to connect with the above error message ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 13 06:37:27 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-01 (11 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) IpRoute: default via 10.100.102.1 dev enp0s31f6 proto static metric 100 10.100.102.0/24 dev enp0s31f6 proto kernel scope link src 10.100.102.5 metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-04-12T22:28:14.870844 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s31f6 ethernet connected/org/freedesktop/NetworkManager/Devices/0 Wired connection 1 d956dc0d-4de6-4f45-8869-a3703d8d0d28 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp4s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- 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/ubuntu/+source/network-manager/+bug/1569674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1569674] Re: [Kubuntu] Fail to connect to wifi after a recent update
One other note, I tried installing Kubuntu, but wasn't able to do so with today's daily image. This makes debugging a bit difficult... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1569674 Title: [Kubuntu] Fail to connect to wifi after a recent update Status in network-manager package in Ubuntu: Confirmed Bug description: I installed the recent updates in the Update Manager and after rebooting I wasn't able to connect to my wifi network anymore. It attempts to connect to the network and fails with the following error message: Failed to update connection [network name] connection.gateway-ping-timeout: can not set property: value "46730064" of type 'guint' is invalid or out of range for property 'gateway-ping-timeout' of type 'guint' I am able to use wired connection. 1. release: Description:Ubuntu Xenial Xerus (development branch) Release:16.04 2. network-manager version: network-manager: Installed: 1.1.93-0ubuntu3 Candidate: 1.1.93-0ubuntu3 Version table: *** 1.1.93-0ubuntu3 500 500 http://il.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected the machine to connect to wifi as always 4. it failed to connect with the above error message ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 13 06:37:27 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-01 (11 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) IpRoute: default via 10.100.102.1 dev enp0s31f6 proto static metric 100 10.100.102.0/24 dev enp0s31f6 proto kernel scope link src 10.100.102.5 metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-04-12T22:28:14.870844 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s31f6 ethernet connected/org/freedesktop/NetworkManager/Devices/0 Wired connection 1 d956dc0d-4de6-4f45-8869-a3703d8d0d28 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp4s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- 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/ubuntu/+source/network-manager/+bug/1569674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1569674] Re: [Kubuntu] Fail to connect to wifi after a recent update
@Avishay Were you connected to WiFi before you rebooted, or were you trying to connect to a network from the network menu for the first time? Does the failure occur for *any* networks you're trying to connect to via WiFi? I don't have Kubuntu installed on any of my machines, but I was able to bring up Kubuntu with today's daily install/liveCD and could connect to my home WiFi network ( WPA2-PSK ). Could you take a look to see if there's a connection file for the AP you're trying to connect to in /etc/NetworkManager/system-connections? If so, could you attach to the bug ( after stripping any private data in the file )? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1569674 Title: [Kubuntu] Fail to connect to wifi after a recent update Status in network-manager package in Ubuntu: Confirmed Bug description: I installed the recent updates in the Update Manager and after rebooting I wasn't able to connect to my wifi network anymore. It attempts to connect to the network and fails with the following error message: Failed to update connection [network name] connection.gateway-ping-timeout: can not set property: value "46730064" of type 'guint' is invalid or out of range for property 'gateway-ping-timeout' of type 'guint' I am able to use wired connection. 1. release: Description:Ubuntu Xenial Xerus (development branch) Release:16.04 2. network-manager version: network-manager: Installed: 1.1.93-0ubuntu3 Candidate: 1.1.93-0ubuntu3 Version table: *** 1.1.93-0ubuntu3 500 500 http://il.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected the machine to connect to wifi as always 4. it failed to connect with the above error message ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 13 06:37:27 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-01 (11 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) IpRoute: default via 10.100.102.1 dev enp0s31f6 proto static metric 100 10.100.102.0/24 dev enp0s31f6 proto kernel scope link src 10.100.102.5 metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-04-12T22:28:14.870844 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s31f6 ethernet connected/org/freedesktop/NetworkManager/Devices/0 Wired connection 1 d956dc0d-4de6-4f45-8869-a3703d8d0d28 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp4s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- 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/ubuntu/+source/network-manager/+bug/1569674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1569674] Re: [Kubuntu] Fail to connect to wifi after a recent update
** Summary changed: - Fail to connect to wifi after a recent update + [Kubuntu] Fail to connect to wifi after a recent update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1569674 Title: [Kubuntu] Fail to connect to wifi after a recent update Status in network-manager package in Ubuntu: Confirmed Bug description: I installed the recent updates in the Update Manager and after rebooting I wasn't able to connect to my wifi network anymore. It attempts to connect to the network and fails with the following error message: Failed to update connection [network name] connection.gateway-ping-timeout: can not set property: value "46730064" of type 'guint' is invalid or out of range for property 'gateway-ping-timeout' of type 'guint' I am able to use wired connection. 1. release: Description:Ubuntu Xenial Xerus (development branch) Release:16.04 2. network-manager version: network-manager: Installed: 1.1.93-0ubuntu3 Candidate: 1.1.93-0ubuntu3 Version table: *** 1.1.93-0ubuntu3 500 500 http://il.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected the machine to connect to wifi as always 4. it failed to connect with the above error message ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 13 06:37:27 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-01 (11 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) IpRoute: default via 10.100.102.1 dev enp0s31f6 proto static metric 100 10.100.102.0/24 dev enp0s31f6 proto kernel scope link src 10.100.102.5 metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-04-12T22:28:14.870844 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s31f6 ethernet connected/org/freedesktop/NetworkManager/Devices/0 Wired connection 1 d956dc0d-4de6-4f45-8869-a3703d8d0d28 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp4s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- 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/ubuntu/+source/network-manager/+bug/1569674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1567069] Re: Wrong APN selected so MMS stopped working
Re-tested krillin with stable #27 ( OTA-8 ), and got the exact same behavior. Also went much further back to stable #21 ( almost a year-to- the-date ) and same behavior, ATT WAP is chosen yet again. The only difference between our devices is that you have a non-working T-Mobile SIM present, and I don't, but that really should make no difference in the ordering of NM's connection attempts for a single SIM/modem. The contexts are read from ofono in order ( context1, context2, context3 ), and then NM always seems to work it's way through the list in reverse order ( ie. it always tries context3 aka ATT WAP first ). It could be that ATT WAP was always failing to connect for you, thus you were always ending up with context2 ( ATT Phone ) as the working APN, and that for some reason ATT WAP now works? No idea, but the NM still appears to be working the same across multiple versions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1567069 Title: Wrong APN selected so MMS stopped working Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: On two phones connected to AT, got recent rc-proposed updates, at some point between 3/30 and 4/6 the phone started to select the wrong APN, one which did not support MMS only internet. These phones have worked with MMS reliably for over a year. Rebooting the phone does not fix it. One phone has been just getting updates for a year the other I had flashed last week. Explicitly selecting the correct preferred APN makes them work again. My concern is something changed in the logic or database on the device to change the behavior. Krillin rc-proposed r306 Arale rc-proposed r299 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1567069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1567069] Re: Wrong APN selected so MMS stopped working
** Changed in: network-manager (Ubuntu) Status: New => Incomplete ** Changed in: ofono (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1567069 Title: Wrong APN selected so MMS stopped working Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: On two phones connected to AT, got recent rc-proposed updates, at some point between 3/30 and 4/6 the phone started to select the wrong APN, one which did not support MMS only internet. These phones have worked with MMS reliably for over a year. Rebooting the phone does not fix it. One phone has been just getting updates for a year the other I had flashed last week. Explicitly selecting the correct preferred APN makes them work again. My concern is something changed in the logic or database on the device to change the behavior. Krillin rc-proposed r306 Arale rc-proposed r299 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1567069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta
OK, strike the last bit about nameservers being added vs. replaced. I was the one who misunderstood how the VPN IPv4v6 dialogs work, and thus wasn't finding the "User this connection only for the resources on this network" checkbox. Once I did, the VPN DNS works as expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1552424 Title: [FFE] NetworkManager 1.2-beta Status in network-manager package in Ubuntu: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Status in network-manager-iodine package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-vpnc package in Ubuntu: Confirmed Bug description: We really should update NetworkManager to 1.2 (or some other updated stable release) for the LTS, this will allow us to better deal with any bugs that might come up post-release. This new release will also much improve interop with LXC, which has recently been an issue. Other FFEs will be opened for NM VPN plugins and for NetworkManager- applet. NetworkManager-1.2 Overview of changes since NetworkManager-1.0 This is a new stable release of NetworkManager. Notable changes include: * Added an option to enable use of random MAC addresses for Wi-Fi access point scanning (defaults to disabled). Controlled with 'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key in ifcfg files). * Wi-Fi scanning now utilizes wpa_supplicant's AP list. * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg files. * Added support for creation of more types of software devices: tun & tap, macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6). * The software devices (bond, bridge, vlan, team, ...) can now be stacked arbitrarily. The nmcli interface for creating master-slave relationships has been significantly improved by the use of 'master' argument to all link types. * RFC7217 stable privacy addressing is now used by default to protect from address-based host tracking. The IPv6 addressing mode is configured with IPV6_ADDR_GEN_MODE key in ifcfg files. * Improved route management code to avoid clashes between conflicting routes in multiple connections. * Refactored platform code resulting in more robust interface to platform, less overhead and reduced memory footprint. * Improved interoperability with other network management tools. The externally created software devices are not managed until they're activated. * The Device instances now exist for all software connections and the platform devices are now only created when the device is activated. This makes it possible for connections with device of same name not to clash unless they're activated concurrently. The links are now not unnecessarily present unless the connection is active, avoiding pollution of the link namespace. * NetworkManager now correctly manages connectivity in namespace-based containers such as LXC and Docker. * Support for configuring ethernet Wake-On-Lan has been added. * Added LLDP listener functionality and related CLI client commands. Enabled via LLDP option in ifcfg files. * CLI secret agent has been extended with support for VPN secrets. * The command line client now utilizes colors for its output. * The command line client now sorts the devices and properties for better clarity. * Numerous improvements to Bash command completion for nmcli. * NetworkManager relies on less external libraries. The use of dbus-glib has been replaced with gio's native D-Bus support and libnl-route is no longer used. * Dependency on avahi-autoipd has been dropped. Native IPv4 link-local addressing configuration based on systemd network library is now used instead. * Hostname is now managed via systemd-hostnamed on systemd-based systems. * Management of resolv.conf management can be changed at runtime, private resolv.conf is always written in /run. * NetworkManager can now write DNS options to resolv.conf. * Updated version of systemd network library used for internal DHCP and IPv4 link-local support. * Support for event logging via audit subsystem has been added. * Support for native logging via systemd-journald has been added taking advantage of its structured logging. * Live reconfiguration of IP configuration after changing the settings without reactivation of the device with "nmcli device reapply" command and via
[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta
I've re-based Mathieu's branch on rc1: lp:~awe/network-manager/update-1.2 I've pushed a version to my PPA: https://launchpad.net/~awe/+archive/ubuntu/ppa The original issue ( no DNS ) seen with the Canonical VPN seems to have been resolved, although the behavior seems to be slightly different than 1.0.4x( wily ) which appears to add the VPN DNS server vs. replace the existing nameservers. Mathieu says this is by design, however I don't feel like its totally understood yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1552424 Title: [FFE] NetworkManager 1.2-beta Status in network-manager package in Ubuntu: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Status in network-manager-iodine package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-vpnc package in Ubuntu: Confirmed Bug description: We really should update NetworkManager to 1.2 (or some other updated stable release) for the LTS, this will allow us to better deal with any bugs that might come up post-release. This new release will also much improve interop with LXC, which has recently been an issue. Other FFEs will be opened for NM VPN plugins and for NetworkManager- applet. NetworkManager-1.2 Overview of changes since NetworkManager-1.0 This is a new stable release of NetworkManager. Notable changes include: * Added an option to enable use of random MAC addresses for Wi-Fi access point scanning (defaults to disabled). Controlled with 'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key in ifcfg files). * Wi-Fi scanning now utilizes wpa_supplicant's AP list. * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg files. * Added support for creation of more types of software devices: tun & tap, macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6). * The software devices (bond, bridge, vlan, team, ...) can now be stacked arbitrarily. The nmcli interface for creating master-slave relationships has been significantly improved by the use of 'master' argument to all link types. * RFC7217 stable privacy addressing is now used by default to protect from address-based host tracking. The IPv6 addressing mode is configured with IPV6_ADDR_GEN_MODE key in ifcfg files. * Improved route management code to avoid clashes between conflicting routes in multiple connections. * Refactored platform code resulting in more robust interface to platform, less overhead and reduced memory footprint. * Improved interoperability with other network management tools. The externally created software devices are not managed until they're activated. * The Device instances now exist for all software connections and the platform devices are now only created when the device is activated. This makes it possible for connections with device of same name not to clash unless they're activated concurrently. The links are now not unnecessarily present unless the connection is active, avoiding pollution of the link namespace. * NetworkManager now correctly manages connectivity in namespace-based containers such as LXC and Docker. * Support for configuring ethernet Wake-On-Lan has been added. * Added LLDP listener functionality and related CLI client commands. Enabled via LLDP option in ifcfg files. * CLI secret agent has been extended with support for VPN secrets. * The command line client now utilizes colors for its output. * The command line client now sorts the devices and properties for better clarity. * Numerous improvements to Bash command completion for nmcli. * NetworkManager relies on less external libraries. The use of dbus-glib has been replaced with gio's native D-Bus support and libnl-route is no longer used. * Dependency on avahi-autoipd has been dropped. Native IPv4 link-local addressing configuration based on systemd network library is now used instead. * Hostname is now managed via systemd-hostnamed on systemd-based systems. * Management of resolv.conf management can be changed at runtime, private resolv.conf is always written in /run. * NetworkManager can now write DNS options to resolv.conf. * Updated version of systemd network library used for internal DHCP and IPv4 link-local support. * Support for event logging via audit subsystem has been added. * Support for native logging via systemd-journald has been added taking
[Desktop-packages] [Bug 1567069] Re: Wrong APN selected so MMS stopped working
Just tested with krillin ( rc/bq-aquaris.en #48 ) plus a single AT SIM. Made sure to clear all of the 'Preferred' flags and rebooted. To do this, as root: # stop network-manager # stop ofono # cd /var/lib/ofono// # vi gprs ( change any 'Preferred=true' -> 'Preferred=false' ) # reboot I see in the log that NM finds the three contexts in order, and then tries context3 first always. I rebooted twice and the same thing always happens: 17:16:48 NetworkManager: SCPlugin-Ofono: found internet context 'ATT Nextgenphone' (context1) 17:16:48 NetworkManager: SCPlugin-Ofono: update_connection_setting_from_context: name:ATT Nextgenphone, path:context1, id:/310410833791757/context1, uuid: 71c1fc6d-6992-1120-b348-990f150dae3d 17:16:48 NetworkManager: SCPlugin-Ofono: found internet context 'ATT Phone' (context2) 17:16:48 NetworkManager: SCPlugin-Ofono: update_connection_setting_from_context: name:ATT Phone, path:context2, id:/310410833791757/context2, uuid: fe79bba6-614c-401c-d83b-1e8f52153ed0 17:16:48 NetworkManager: SCPlugin-Ofono: found internet context 'ATT WAP' (context3) 17:16:48 NetworkManager: SCPlugin-Ofono: update_connection_setting_from_context: name:ATT WAP, path:context3, id:/310410833791757/context3, uuid: 499fc259-e7ce-9ecc-bc73-8a4f40d888b6 17:16:48 NetworkManager: SCPlugin-Ofono: found internet context 'T-Mobile GPRS' (context2) 17:16:48 NetworkManager: SCPlugin-Ofono: update_connection_setting_from_context: name:T-Mobile GPRS, path:context2, id:/310260006686790/context2, uuid: 0fc0650f-0763-ee7d-f968-936a08469368 17:17:34 NetworkManager: Auto-activating connection '/310410833791757/context3'. 17:17:34 NetworkManager: Activation (ril_0) starting connection '/310410833791757/context3' 17:17:34 NetworkManager: (/ril_0): activating context /ril_0/context3 It shouldn't be too hard to re-flash a previous rc prior to 48 to see if this is a regression caused by OTA10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1567069 Title: Wrong APN selected so MMS stopped working Status in network-manager package in Ubuntu: New Status in ofono package in Ubuntu: New Bug description: On two phones connected to AT, got recent rc-proposed updates, at some point between 3/30 and 4/6 the phone started to select the wrong APN, one which did not support MMS only internet. These phones have worked with MMS reliably for over a year. Rebooting the phone does not fix it. One phone has been just getting updates for a year the other I had flashed last week. Explicitly selecting the correct preferred APN makes them work again. My concern is something changed in the logic or database on the device to change the behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1567069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta
NM 1.1.93 ( 1.2-rc1 ) was just released. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1552424 Title: [FFE] NetworkManager 1.2-beta Status in network-manager package in Ubuntu: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Status in network-manager-iodine package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-vpnc package in Ubuntu: Confirmed Bug description: We really should update NetworkManager to 1.2 (or some other updated stable release) for the LTS, this will allow us to better deal with any bugs that might come up post-release. This new release will also much improve interop with LXC, which has recently been an issue. Other FFEs will be opened for NM VPN plugins and for NetworkManager- applet. NetworkManager-1.2 Overview of changes since NetworkManager-1.0 This is a new stable release of NetworkManager. Notable changes include: * Added an option to enable use of random MAC addresses for Wi-Fi access point scanning (defaults to disabled). Controlled with 'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key in ifcfg files). * Wi-Fi scanning now utilizes wpa_supplicant's AP list. * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg files. * Added support for creation of more types of software devices: tun & tap, macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6). * The software devices (bond, bridge, vlan, team, ...) can now be stacked arbitrarily. The nmcli interface for creating master-slave relationships has been significantly improved by the use of 'master' argument to all link types. * RFC7217 stable privacy addressing is now used by default to protect from address-based host tracking. The IPv6 addressing mode is configured with IPV6_ADDR_GEN_MODE key in ifcfg files. * Improved route management code to avoid clashes between conflicting routes in multiple connections. * Refactored platform code resulting in more robust interface to platform, less overhead and reduced memory footprint. * Improved interoperability with other network management tools. The externally created software devices are not managed until they're activated. * The Device instances now exist for all software connections and the platform devices are now only created when the device is activated. This makes it possible for connections with device of same name not to clash unless they're activated concurrently. The links are now not unnecessarily present unless the connection is active, avoiding pollution of the link namespace. * NetworkManager now correctly manages connectivity in namespace-based containers such as LXC and Docker. * Support for configuring ethernet Wake-On-Lan has been added. * Added LLDP listener functionality and related CLI client commands. Enabled via LLDP option in ifcfg files. * CLI secret agent has been extended with support for VPN secrets. * The command line client now utilizes colors for its output. * The command line client now sorts the devices and properties for better clarity. * Numerous improvements to Bash command completion for nmcli. * NetworkManager relies on less external libraries. The use of dbus-glib has been replaced with gio's native D-Bus support and libnl-route is no longer used. * Dependency on avahi-autoipd has been dropped. Native IPv4 link-local addressing configuration based on systemd network library is now used instead. * Hostname is now managed via systemd-hostnamed on systemd-based systems. * Management of resolv.conf management can be changed at runtime, private resolv.conf is always written in /run. * NetworkManager can now write DNS options to resolv.conf. * Updated version of systemd network library used for internal DHCP and IPv4 link-local support. * Support for event logging via audit subsystem has been added. * Support for native logging via systemd-journald has been added taking advantage of its structured logging. * Live reconfiguration of IP configuration after changing the settings without reactivation of the device with "nmcli device reapply" command and via D-Bus API. * The API for VPN plugins now supports multiple simultaneous connections. Most popular VPN plugins have been updated to support this functionality. * The libnm library now provides API to access VPN service
[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta
The openvpn failure is actually a symptom of a larger problem which can
affect *any* DNS server ( ie. not just servers associated with a VPN )
that includes a domain. The updated gdbus patch mentioned in the
previous comment adds the DBus parameters to the dnsmasq SetServersEx
method in the wrong order when a domain is specified, domains are
actually supposed to come *after* the IP address of a nameserver:
+static void
+add_dnsmasq_nameserver (NMDnsDnsmasq *self,
+GVariantBuilder *servers,
+const char *ip,
+const char *domain)
+{
+ g_return_if_fail (ip);
+
+ _LOGD ("adding nameserver '%s' for domain '%s'",
+ ip, domain);
+
+ g_variant_builder_open (servers, G_VARIANT_TYPE ("as"));
+
+ if (domain)
+ g_variant_builder_add (servers, "s", domain);
+ g_variant_builder_add (servers, "s", ip);
+
+ g_variant_builder_close (servers);
+}
Fixing is just a matter of moving the "if (domain)" statement to after
the g_variant_build_add call for the servers.
See the following page for a description of the dnsmasq DBus interface:
http://www.thekelleys.org.uk/dnsmasq/docs/DBus-interface
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1552424
Title:
[FFE] NetworkManager 1.2-beta
Status in network-manager package in Ubuntu:
Confirmed
Status in network-manager-applet package in Ubuntu:
Confirmed
Status in network-manager-iodine package in Ubuntu:
Confirmed
Status in network-manager-openconnect package in Ubuntu:
Confirmed
Status in network-manager-openvpn package in Ubuntu:
Confirmed
Status in network-manager-pptp package in Ubuntu:
Confirmed
Status in network-manager-vpnc package in Ubuntu:
Confirmed
Bug description:
We really should update NetworkManager to 1.2 (or some other updated
stable release) for the LTS, this will allow us to better deal with
any bugs that might come up post-release.
This new release will also much improve interop with LXC, which has
recently been an issue.
Other FFEs will be opened for NM VPN plugins and for NetworkManager-
applet.
NetworkManager-1.2
Overview of changes since NetworkManager-1.0
This is a new stable release of NetworkManager. Notable changes
include:
* Added an option to enable use of random MAC addresses for Wi-Fi access
point scanning (defaults to disabled). Controlled with
'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key
in
ifcfg files).
* Wi-Fi scanning now utilizes wpa_supplicant's AP list.
* Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg
files.
* Added support for creation of more types of software devices: tun & tap,
macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6).
* The software devices (bond, bridge, vlan, team, ...) can now be stacked
arbitrarily. The nmcli interface for creating master-slave relationships
has been significantly improved by the use of 'master' argument to
all link types.
* RFC7217 stable privacy addressing is now used by default to protect from
address-based host tracking. The IPv6 addressing mode is configured with
IPV6_ADDR_GEN_MODE key in ifcfg files.
* Improved route management code to avoid clashes between conflicting
routes in multiple connections.
* Refactored platform code resulting in more robust interface to platform,
less overhead and reduced memory footprint.
* Improved interoperability with other network management tools. The
externally created software devices are not managed until they're
activated.
* The Device instances now exist for all software connections and the platform
devices are now only created when the device is activated. This makes it
possible for connections with device of same name not to clash unless
they're activated concurrently. The links are now not unnecessarily
present
unless the connection is active, avoiding pollution of the link namespace.
* NetworkManager now correctly manages connectivity in namespace-based
containers such as LXC and Docker.
* Support for configuring ethernet Wake-On-Lan has been added.
* Added LLDP listener functionality and related CLI client commands. Enabled
via
LLDP option in ifcfg files.
* CLI secret agent has been extended with support for VPN secrets.
* The command line client now utilizes colors for its output.
* The command line client now sorts the devices and properties for better
clarity.
* Numerous improvements to Bash command completion for nmcli.
* NetworkManager relies on less external libraries. The use of dbus-glib
has been replaced
[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta
The openvpn failure to setup DNS is due to an error returned to the DBus call to dnsmasq: dnsmasq update failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid IP address: 'buildd': bad address So, pretty sure this is a bug in the patch [1] that adds DBus support to dnsmasq, and that the domain and IP address are getting mixed up. [1] 0001-dns-use-DBus-to-make-dnsmasq-nameserver-changes.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1552424 Title: [FFE] NetworkManager 1.2-beta Status in network-manager package in Ubuntu: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Status in network-manager-iodine package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-vpnc package in Ubuntu: Confirmed Bug description: We really should update NetworkManager to 1.2 (or some other updated stable release) for the LTS, this will allow us to better deal with any bugs that might come up post-release. This new release will also much improve interop with LXC, which has recently been an issue. Other FFEs will be opened for NM VPN plugins and for NetworkManager- applet. NetworkManager-1.2 Overview of changes since NetworkManager-1.0 This is a new stable release of NetworkManager. Notable changes include: * Added an option to enable use of random MAC addresses for Wi-Fi access point scanning (defaults to disabled). Controlled with 'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key in ifcfg files). * Wi-Fi scanning now utilizes wpa_supplicant's AP list. * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg files. * Added support for creation of more types of software devices: tun & tap, macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6). * The software devices (bond, bridge, vlan, team, ...) can now be stacked arbitrarily. The nmcli interface for creating master-slave relationships has been significantly improved by the use of 'master' argument to all link types. * RFC7217 stable privacy addressing is now used by default to protect from address-based host tracking. The IPv6 addressing mode is configured with IPV6_ADDR_GEN_MODE key in ifcfg files. * Improved route management code to avoid clashes between conflicting routes in multiple connections. * Refactored platform code resulting in more robust interface to platform, less overhead and reduced memory footprint. * Improved interoperability with other network management tools. The externally created software devices are not managed until they're activated. * The Device instances now exist for all software connections and the platform devices are now only created when the device is activated. This makes it possible for connections with device of same name not to clash unless they're activated concurrently. The links are now not unnecessarily present unless the connection is active, avoiding pollution of the link namespace. * NetworkManager now correctly manages connectivity in namespace-based containers such as LXC and Docker. * Support for configuring ethernet Wake-On-Lan has been added. * Added LLDP listener functionality and related CLI client commands. Enabled via LLDP option in ifcfg files. * CLI secret agent has been extended with support for VPN secrets. * The command line client now utilizes colors for its output. * The command line client now sorts the devices and properties for better clarity. * Numerous improvements to Bash command completion for nmcli. * NetworkManager relies on less external libraries. The use of dbus-glib has been replaced with gio's native D-Bus support and libnl-route is no longer used. * Dependency on avahi-autoipd has been dropped. Native IPv4 link-local addressing configuration based on systemd network library is now used instead. * Hostname is now managed via systemd-hostnamed on systemd-based systems. * Management of resolv.conf management can be changed at runtime, private resolv.conf is always written in /run. * NetworkManager can now write DNS options to resolv.conf. * Updated version of systemd network library used for internal DHCP and IPv4 link-local support. * Support for event logging via audit subsystem has been added. * Support for native logging via systemd-journald has been added taking advantage of its structured logging. * Live reconfiguration of IP
[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta
@Bryan Thanks for the reply. I actually did a fresh xenial install on my Thinkpad 410s this afternoon, installed the packages from Mathieu's PPA, and then configured the Canonical VPN. I'm able to start it, but once active, I'm not also not able to access the network. This is most likely a bug in the updated dnsmasq code as after the VPN is started, dnsmasq is left without any DNS servers configured ( you can check this by sending SIGUSR1 to dnsmasq and checking the syslog output ). Also, Mathieu mentioned that when the VPN is activated, the WiFi icon shown by the applet is incorrect. I see just the small lock, and no signal bars. This is probably due to a path issue with the icons in the applet. No applet crashes on my end. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1552424 Title: [FFE] NetworkManager 1.2-beta Status in network-manager package in Ubuntu: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Status in network-manager-iodine package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-vpnc package in Ubuntu: Confirmed Bug description: We really should update NetworkManager to 1.2 (or some other updated stable release) for the LTS, this will allow us to better deal with any bugs that might come up post-release. This new release will also much improve interop with LXC, which has recently been an issue. Other FFEs will be opened for NM VPN plugins and for NetworkManager- applet. NetworkManager-1.2 Overview of changes since NetworkManager-1.0 This is a new stable release of NetworkManager. Notable changes include: * Added an option to enable use of random MAC addresses for Wi-Fi access point scanning (defaults to disabled). Controlled with 'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key in ifcfg files). * Wi-Fi scanning now utilizes wpa_supplicant's AP list. * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg files. * Added support for creation of more types of software devices: tun & tap, macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6). * The software devices (bond, bridge, vlan, team, ...) can now be stacked arbitrarily. The nmcli interface for creating master-slave relationships has been significantly improved by the use of 'master' argument to all link types. * RFC7217 stable privacy addressing is now used by default to protect from address-based host tracking. The IPv6 addressing mode is configured with IPV6_ADDR_GEN_MODE key in ifcfg files. * Improved route management code to avoid clashes between conflicting routes in multiple connections. * Refactored platform code resulting in more robust interface to platform, less overhead and reduced memory footprint. * Improved interoperability with other network management tools. The externally created software devices are not managed until they're activated. * The Device instances now exist for all software connections and the platform devices are now only created when the device is activated. This makes it possible for connections with device of same name not to clash unless they're activated concurrently. The links are now not unnecessarily present unless the connection is active, avoiding pollution of the link namespace. * NetworkManager now correctly manages connectivity in namespace-based containers such as LXC and Docker. * Support for configuring ethernet Wake-On-Lan has been added. * Added LLDP listener functionality and related CLI client commands. Enabled via LLDP option in ifcfg files. * CLI secret agent has been extended with support for VPN secrets. * The command line client now utilizes colors for its output. * The command line client now sorts the devices and properties for better clarity. * Numerous improvements to Bash command completion for nmcli. * NetworkManager relies on less external libraries. The use of dbus-glib has been replaced with gio's native D-Bus support and libnl-route is no longer used. * Dependency on avahi-autoipd has been dropped. Native IPv4 link-local addressing configuration based on systemd network library is now used instead. * Hostname is now managed via systemd-hostnamed on systemd-based systems. * Management of resolv.conf management can be changed at runtime, private resolv.conf is always written in /run. * NetworkManager can now write DNS options to
[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta
@Bryan Thanks for the test results. Let's not open any new bugs for now, as Mathieu was able to reproduce the Canonical VPN issue and noticed that the problem is probably related to the dnsmasq DBus changes that were made as part of the upgrade to NM1.2. I'll take a look at this later today and see if I can reproduce. Regarding the applet crash, could you add a backtrace to the bug for us? I'll also see if I can reproduce. Finally, in discussing with Mathieu, one other issue exists with the applet icons when VPN is enabled. This is probably due to an icon path mismatch. As @Amr mentioned in comment #14, 1.1.92 ( beta3) was released last week. I'm currently testing this version for Touch. The final release of NM1.2 is expected to land this week. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1552424 Title: [FFE] NetworkManager 1.2-beta Status in network-manager package in Ubuntu: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Status in network-manager-iodine package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-vpnc package in Ubuntu: Confirmed Bug description: We really should update NetworkManager to 1.2 (or some other updated stable release) for the LTS, this will allow us to better deal with any bugs that might come up post-release. This new release will also much improve interop with LXC, which has recently been an issue. Other FFEs will be opened for NM VPN plugins and for NetworkManager- applet. NetworkManager-1.2 Overview of changes since NetworkManager-1.0 This is a new stable release of NetworkManager. Notable changes include: * Added an option to enable use of random MAC addresses for Wi-Fi access point scanning (defaults to disabled). Controlled with 'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key in ifcfg files). * Wi-Fi scanning now utilizes wpa_supplicant's AP list. * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg files. * Added support for creation of more types of software devices: tun & tap, macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6). * The software devices (bond, bridge, vlan, team, ...) can now be stacked arbitrarily. The nmcli interface for creating master-slave relationships has been significantly improved by the use of 'master' argument to all link types. * RFC7217 stable privacy addressing is now used by default to protect from address-based host tracking. The IPv6 addressing mode is configured with IPV6_ADDR_GEN_MODE key in ifcfg files. * Improved route management code to avoid clashes between conflicting routes in multiple connections. * Refactored platform code resulting in more robust interface to platform, less overhead and reduced memory footprint. * Improved interoperability with other network management tools. The externally created software devices are not managed until they're activated. * The Device instances now exist for all software connections and the platform devices are now only created when the device is activated. This makes it possible for connections with device of same name not to clash unless they're activated concurrently. The links are now not unnecessarily present unless the connection is active, avoiding pollution of the link namespace. * NetworkManager now correctly manages connectivity in namespace-based containers such as LXC and Docker. * Support for configuring ethernet Wake-On-Lan has been added. * Added LLDP listener functionality and related CLI client commands. Enabled via LLDP option in ifcfg files. * CLI secret agent has been extended with support for VPN secrets. * The command line client now utilizes colors for its output. * The command line client now sorts the devices and properties for better clarity. * Numerous improvements to Bash command completion for nmcli. * NetworkManager relies on less external libraries. The use of dbus-glib has been replaced with gio's native D-Bus support and libnl-route is no longer used. * Dependency on avahi-autoipd has been dropped. Native IPv4 link-local addressing configuration based on systemd network library is now used instead. * Hostname is now managed via systemd-hostnamed on systemd-based systems. * Management of resolv.conf management can be changed at runtime, private resolv.conf is always written in /run. * NetworkManager can now
[Desktop-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi
It should be noted that we just landed a new version of NetworkManager into rc-proposed ( 0.9.10.0-4ubuntu15.1.10 ) which fixed a couple of race conditions that existed in the interactions between NM and wpa_supplicant that could potentially cause the phone to stop scanning on WiFi after a disconnect occurs. That said, for now I think it best to keep this bug open, until wider testing shows whether or not issues still exist. Finally, an ongoing effort is happening to re-base Touch on NetworkManager 1.2, which includes a significant re-working of NM's WiFi logic. As this gets closer to reality/landing, I will make sure to comment on this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi
@Julia Thanks for the testing report! So when you say, "you gave it 10/15 minutes of time to reconnect on its own". I assume during this time you were assuming that the device would re-connect automatically when the screen was off? Then you say you woke the phone, and it was offline until you started to interact with the network menu. Can you give us a rough idea of how long it was between when you woke the phone, and it connected? My experience have show that it's usually somewhere between 30s and 2m to connect. Finally, the original bug describes a situation where after the phone is woken, it will *never* re-connect to an available access point it's previously been connected to. @ Pete Regarding passive network scanning... no, none of the sort happens, in fact we have no code at all in our network stack that integrates with our power management framework on touch devices. At some point, the screen turns off, which given the right conditions causes powerd to notify the kernel that it's allowed to sleep. When this happens ( ie. the kernel decides to suspend given no more wake locks ), there's no notification to wpa_supplicant or NetworkManager, and in some cases we've seen this "pulling of the rug" approach actually prevent some devices from suspending. Enabling passive scanning during suspend is something that could be accomplished automatically by the driver, or enabled by wpa_supplicant before suspend, however without some knowledge of the system power/suspend mechanism, neither wpa_supplicant or NM can do this today. Making such a thing work, also would require deeper technical cooperation from the ODM and/or IHV. Note, we also should seriously consider a new system settings for WiFi that allows a user to specify whether or not WiFi is to attempt to keep a connection going when the system goes to suspend. I would argue that our current situation is a bit ambiguous ( ie. WiFi remains on, but at some point when the device suspends, it does disconnect ). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
@Jean-Baptiste This was reported quite awhile back. Is this behavior still reproducible with OTA9? ** Changed in: network-manager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1478319 Title: Wifi doesn't reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Incomplete 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1489154] Re: NetworkManager does not start / fails to start
@Vincent, @Yanik, Please refer to comments #8 and #11. This is not a bug and has been closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1489154 Title: NetworkManager does not start / fails to start Status in One Hundred Papercuts: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: Yesterday i did the upgrade to version 1.0.4 of NetworkManger. Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash report. This also fails cause the start of the NetworkManger fails after booting. Trying manually to start with ~$ sudo systemctl start NetworkManager leads that the icon comes up, disappears, comes up, disappears for 3, 4 times and then it's gone forever. ~$ journalctl -xe Aug 26 22:02:34 Wily NetworkManager[1578]: monitoring ifupdown state file '/run/network/ifstate'. Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVxlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVethFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMTunFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMMacvlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMInfinibandFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMGreFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMEthernetFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBridgeFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBondFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMAtmManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWifiFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBluezManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWwanFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so) Aug 26 22:02:34 Wily NetworkManager[1578]: WiFi enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WWAN enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WiMAX enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: Networking is enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): new Ethernet device (carrier: ON, driver: 'e1000', ifindex: 2) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Aug 26 22:02:34 Wily NetworkManager[1578]: keyfile: add connection in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,"Kabelnetzwerkverbindung 1") Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): created default wired connection 'Kabelnetzwerkverbindung 1' Aug 26 22:02:34 Wily NetworkManager[1578]: urfkill disappeared from the bus Aug 26 22:02:34 Wily NetworkManager[1578]: wpa_supplicant running Aug 26 22:02:34 Wily NetworkManager[1578]: ModemManager available in the bus Aug 26 22:02:34 Wily NetworkManager[1578]: ofono is now available Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemAdded' is invalid for instance Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemRemoved' is invalid for instan Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Aug 26 22:02:34 Wily kernel: NetworkManager[1578]: segfault at c ip b6f4b97a sp bffb4890 error 4 in libglib-2.0.so.0.4504.0[b6ec8000+127000] Aug 26 22:02:34 Wily systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV Aug 26 22:02:34 Wily systemd[1]:
[Desktop-packages] [Bug 1536195] Re: Can't receive calls and sms while Hotspot is active
@Matthew That's correct. The E4.5 is not able to use data on one SIM and voice on the other SIM simultaneously. This is a limitation of a dual-standby modem design. That said, if the phone is registered on one of it's SIMs using 3G or greater, it *can* use data and voice simultaneously on the *same* SIM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1536195 Title: Can't receive calls and sms while Hotspot is active Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in ofono package in Ubuntu: Invalid Bug description: Using 2 Sim Cards Sim 1 for using telephone calls (Provider: Telering (Austria)) Sim 2 for using mobile internet (Provider: 3 AT; this Sim is a Data-Only Sim) While activating Hotspot (using/sharing the internet using Sim 2) I cant receive any calls (number from Sim 1) or SMS. When calling me the caller always get a message from tel-provider: "The customer is currently not accessible...", it seems like the phone switched of. But I can make calls during the phone is in "Hotspot"-mode without problems. Calls and SMS are related to SIM 1 Data is related to Sim 2 (is running in 2G/3G mode) After ending Hotspot I am not reachable at all. I have to reboot (sometimes twice) to be accessible again. -- Using bq Aquarius E4.5 Ubuntu Edition with Ubuntu 15.04 OTA-8.5 20151210 Phone is runing as it was delivered, no developer mode - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1536195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 615239] Re: Every Wi-Fi disconnection is treated as an authentication error
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/615239 Title: Every Wi-Fi disconnection is treated as an authentication error Status in Canonical System Image: New Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager I'm using lucid, with the 0.8-0ubuntu3, in a laptop, and is incredible that the nm-applet couldn't diagnostic why the wireless connection was lost and only trow the password prompt when I've lost the signal. nm-applet should see the kern.log or dmesg to react at signal lost. For example, when the kernel try 3 times probe the AP and don't get response nm-applet say The pc are far away from the access point and can not be connected. Please, move close to the access point or try another more near. And by the way, when the authentication fails, or the association. --- Architecture: i386 CRDA: Error: [Errno 2] No existe el archivo o directorio CheckboxSubmission: ee8ebec101005ce57a9c3355b36ca8a7 CheckboxSystem: edda5d4f616ca792bf437989cb597002 DistroRelease: Ubuntu 10.04 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) IpRoute: 172.16.254.0/24 dev wlan1 proto kernel scope link src 172.16.254.5 metric 2 169.254.0.0/16 dev wlan1 scope link metric 1000 default via 172.16.254.200 dev wlan1 proto static Keyfiles: Error: [Errno 2] No existe el archivo o directorio Package: network-manager 0.8-0ubuntu3 PackageArchitecture: i386 ProcEnviron: PATH=(custom, no user) LANG=es_DO.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: lucid Uname: Linux 2.6.32-24-generic i686 UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/615239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1536195] Re: Can't receive calls and sms while Hotspot is active
We could, although the problem is actually related to any data usage, not just hotspot... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1536195 Title: Can't receive calls and sms while Hotspot is active Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in ofono package in Ubuntu: Invalid Bug description: Using 2 Sim Cards Sim 1 for using telephone calls (Provider: Telering (Austria)) Sim 2 for using mobile internet (Provider: 3 AT; this Sim is a Data-Only Sim) While activating Hotspot (using/sharing the internet using Sim 2) I cant receive any calls (number from Sim 1) or SMS. When calling me the caller always get a message from tel-provider: "The customer is currently not accessible...", it seems like the phone switched of. But I can make calls during the phone is in "Hotspot"-mode without problems. Calls and SMS are related to SIM 1 Data is related to Sim 2 (is running in 2G/3G mode) After ending Hotspot I am not reachable at all. I have to reboot (sometimes twice) to be accessible again. -- Using bq Aquarius E4.5 Ubuntu Edition with Ubuntu 15.04 OTA-8.5 20151210 Phone is runing as it was delivered, no developer mode - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1536195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1536195] Re: Can't receive calls and sms while Hotspot is active
@tuxboson Your welcome... the semantics of dual-SIM modems are tricky, and frankly this isn't fully discussed in the phone's user manual. That said, I ended up fixing one of our telephony test plans, as there was simple note about dual-standy modems that didn't give a full description either! Re: changing your request to a question. Do you mean changing the status of the bug? I'm updating all of the tasks to Invalid along with this comment, so I think that's what you meant? ** Changed in: ofono (Ubuntu) Status: Incomplete => Invalid ** Changed in: network-manager (Ubuntu) Status: Incomplete => Invalid ** Changed in: indicator-network (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1536195 Title: Can't receive calls and sms while Hotspot is active Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in ofono package in Ubuntu: Invalid Bug description: Using 2 Sim Cards Sim 1 for using telephone calls (Provider: Telering (Austria)) Sim 2 for using mobile internet (Provider: 3 AT; this Sim is a Data-Only Sim) While activating Hotspot (using/sharing the internet using Sim 2) I cant receive any calls (number from Sim 1) or SMS. When calling me the caller always get a message from tel-provider: "The customer is currently not accessible...", it seems like the phone switched of. But I can make calls during the phone is in "Hotspot"-mode without problems. Calls and SMS are related to SIM 1 Data is related to Sim 2 (is running in 2G/3G mode) After ending Hotspot I am not reachable at all. I have to reboot (sometimes twice) to be accessible again. -- Using bq Aquarius E4.5 Ubuntu Edition with Ubuntu 15.04 OTA-8.5 20151210 Phone is runing as it was delivered, no developer mode - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1536195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
@Jean-Baptiste Do you end up with the same network-menu as shown in screenshot included with comment #1? The network icon shown on the menu indicates that WiFi is off, and no mobile data connection. If you can reproduce again, can you please include the output of these commands: % /usr/share/ofono/scripts/list-modems -p % nmcli d Also can you please attach the syslog too? ** Changed in: network-manager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1533508 Title: Mobile data doesn't automatically connect after leaving wifi Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. The attached screenshot shows the network 4G data is available but doesn't connect as shown in the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1536195] Re: Can't receive calls and sms while Hotspot is active
@tuxboson The modem in the BQ Aquaris E4.5 is dual-standby, which means it's not able to use both SIMs simultaneously. If you're using one of the SIMs for data, and data is actually being transferred on the connection, incoming calls will be blocked on the other SIM. As you discovered, you can make an outgoing call on the other SIM, but when you do so, the data connection on the first SIM will be quiesced ( ie. temporarily suspended ) while the call is active. These scenarios can easily be tested without hotspot by just running a ping command from the terminal app. Regarding hotspot usage, do you have one or more clients connected to the phone when incoming calls are failing? Also you mention being unreachable after ending hotspot. How long did you wait to determine that you needed to reboot? There is a slight delay when data traffic is stopped, until incoming calls are receivable again, although I can't as yet quantify this delay. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1536195 Title: Can't receive calls and sms while Hotspot is active Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: Using 2 Sim Cards Sim 1 for using telephone calls (Provider: Telering (Austria)) Sim 2 for using mobile internet (Provider: 3 AT; this Sim is a Data-Only Sim) While activating Hotspot (using/sharing the internet using Sim 2) I cant receive any calls (number from Sim 1) or SMS. When calling me the caller always get a message from tel-provider: "The customer is currently not accessible...", it seems like the phone switched of. But I can make calls during the phone is in "Hotspot"-mode without problems. Calls and SMS are related to SIM 1 Data is related to Sim 2 (is running in 2G/3G mode) After ending Hotspot I am not reachable at all. I have to reboot (sometimes twice) to be accessible again. -- Using bq Aquarius E4.5 Ubuntu Edition with Ubuntu 15.04 OTA-8.5 20151210 Phone is runing as it was delivered, no developer mode - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1536195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1533508] Re: Mobile data doesn't automatically connect after leaving wifi
@Dubstar_04 Can you please let us know what device you're using? Also, in addition to the information requested in comment #4, could you please include details about what software you're running on the device? Please either grab a screenshot of Settings::About This Phone::OS, or the output from the command 'system-image-cli -i'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1533508 Title: Mobile data doesn't automatically connect after leaving wifi Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: The mobile data doesn't automatically connect when leaving wifi. Expected Behavior: - Leave wifi - Mobile data connects automatically Observed Behavior: - Leave wifi - Mobile data is available but user interaction is required to connect. The device requires a reboot or airplane mode to be cycled before a connection is made. The attached screenshot shows the network 4G data is available but doesn't connect as shown in the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1536195] Re: Can't receive calls and sms while Hotspot is active
** Changed in: ofono (Ubuntu) Status: New => Incomplete ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1536195 Title: Can't receive calls and sms while Hotspot is active Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: Using 2 Sim Cards Sim 1 for using telephone calls (Provider: Telering (Austria)) Sim 2 for using mobile internet (Provider: 3 AT; this Sim is a Data-Only Sim) While activating Hotspot (using/sharing the internet using Sim 2) I cant receive any calls (number from Sim 1) or SMS. When calling me the caller always get a message from tel-provider: "The customer is currently not accessible...", it seems like the phone switched of. But I can make calls during the phone is in "Hotspot"-mode without problems. Calls and SMS are related to SIM 1 Data is related to Sim 2 (is running in 2G/3G mode) After ending Hotspot I am not reachable at all. I have to reboot (sometimes twice) to be accessible again. -- Using bq Aquarius E4.5 Ubuntu Edition with Ubuntu 15.04 OTA-8.5 20151210 Phone is runing as it was delivered, no developer mode - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1536195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1534552] Re: Phone: Connection to registered wifi network takes too long
@Michael Does the WiFi re-connect delay and/or failure occur in both places? When it actually does connect, is the delay the same in both places? Is the delay *always* ~9m??? Is "eduroam" one of the APs you're actually using at work or home? I ask, as I notice that the security settings indicate that WiFi Enterprise grade authentication is configured. I also noticed that the ESSID:"" is not configured for any security at all. Is this also one of the APs you're using? Also, with respect to listing access points that are known by the system, there are two commands that are more applicable: $ nmcli d wifi list This command shows NetworkManager's current list of available APs. $ sudo wpa_cli scan_results This command shows wpa_supplicant's current list of available APs. Could you please also attach the syslog from your phone? Finally, have you installed any non-store software on the phone? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1534552 Title: Phone: Connection to registered wifi network takes too long Status in network-manager package in Ubuntu: Incomplete Bug description: I am using my Ubuntu Phone at home and at work via wifi. The connection to the registered wifi networks takes too long (several minutes) or fails completely. Even when I turn off wifi off and on again, it takes minutes too reconnect. At home the phone sometimes displays wifi networks, that only exists at work and vice versa. Device: Aquaris E 4.5 OS: 15.04 OTA 8.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1534552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1512831] Re: Flight mode: Wi-Fi re-enabled upon reboot
@Pete
Flight mode persistence is actually handled by urfkill.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1512831
Title:
Flight mode: Wi-Fi re-enabled upon reboot
Status in indicator-network package in Ubuntu:
Invalid
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
One arale r152 rc-proposed, finding that under flight mode Wi-Fi can
be re-enabled upon reboot, will attach a screenie ("boite_LeSage" is
my home router access point).
TEST CASE:
1. Enable flight mode, verify that flight mode is indicated, Wi-Fi switch is
off.
2. Reboot phone.
EXPECTED:
Flight mode engaged, Wi-Fi disabled.
ACTUAL:
Flight mode engaged, Wi-Fi enabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1512831/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1512831] Re: Flight mode: Wi-Fi re-enabled upon reboot
@Allan
Can you please re-test with a current image?
I just tried this on my arale ( rc-proposed/meizu.en #216 ) which was
updated two days ago. I can't recreate.
I verified that WiFi was enabled, then enabled FlightMode, verifying
that WiFi had been disabled before rebooting.
I ran this scenario five times in a row, and each time after the device
booted, FlightMode was enabled, and WiFi still disabled.
I even tried one time with WiFi disabled, before enabling FlightMode,
with no difference.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Allan LeSage (allanlesage)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1512831
Title:
Flight mode: Wi-Fi re-enabled upon reboot
Status in indicator-network package in Ubuntu:
Invalid
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
One arale r152 rc-proposed, finding that under flight mode Wi-Fi can
be re-enabled upon reboot, will attach a screenie ("boite_LeSage" is
my home router access point).
TEST CASE:
1. Enable flight mode, verify that flight mode is indicated, Wi-Fi switch is
off.
2. Reboot phone.
EXPECTED:
Flight mode engaged, Wi-Fi disabled.
ACTUAL:
Flight mode engaged, Wi-Fi enabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1512831/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270189] Re: Ubuntu Touch devices are using cellular DNS servers over wifi connection
@Lorn It was designed this way in order to make the switching from WiFi back to the mobile data connection fast. Re-working this fundamental design decision IMHOP would be a significant amount of work, and it's not like our current queue of NM related is empty... I think in the short term if we're able to dedicate cycles to this bug, the best approach would be to re-work how DNS is handled when WiFi is enabled and mobile data is active. My gut tells me that instead of just adding the new DNS servers when WiFi is enabled, that we remove the existing name servers, then re-add them *after* the WiFi nameservers. Also, I'm not sure that mobile data is needed for downloading HERE/AGPS data, this is something we'd need to discuss with tvoss. That said, it *is* required for MMS to work properly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1270189 Title: Ubuntu Touch devices are using cellular DNS servers over wifi connection Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: New Bug description: On my Nexus 4, build 121 with TMobile, when I am on wifi, I correctly get a 192.168 ip and DNS entries for this network (on wlan0) -- fine. When I am in range of cellular data, I get an ip address from TMobile and am given DNS entries that aren't on the same network as the TMobile ip address (on rmnet_usb0). The problem is, the DNS entries from TMobile are preferred over the ones from the wifi network such that while wlan0 is correctly setup as the default route, DNS queries are being made to the TMobile DNS servers over wlan0 because there are no explicit routes to these servers. This is problematic because the remote DNS server may not respond to queries coming from out of network or site policy may disallow the use of foreign DNS servers-- both of which result in slow (or possibly failing) DNS queries since the cellular DNS is checked first. Also, where it did work, these queries could incur charges when the user is intending to use only wifi. In the case of (at least) TMobile, this could be a security concern because the well-known TMobile DNS servers are on the private '10.' network, which opens the possibility for a rogue DNS server to be on the private wifi network with this ip address. This could be fixed in (at least) four ways: 1) when on wifi, don't merge the DNS servers on cellular networks at all which forces the device to use the ones available on the site (wlan0). This is guaranteed to not incur changes 2) when on wifi, merge the DNS server from the cellular network, but add them after the ones on the wifi network. This will try the site's DNS first and only if they fail, fallback to the cellular DNS. This may incur charges under certain circumstances 3) add an explicit route to the cellular DNS servers through rmnet_usb0. This will bypass the site DNS with all queries going through cellular DNS. This will incur charges and would make the device unable to resolve site-local names. 4) same as '2', but also add explicit routes for the cellular name servers. This should only incur charges if wifi DNS fails I think '3' is out. '2' and '4' seems most intuitive (with '4' perhaps most correct). '1' seems also ok. # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.x.1 0.0.0.0 UG0 0 0 wlan0 100.152.35.128 0.0.0.0 255.255.255.252 U 0 0 0 rmnet_usb0 192.168.x.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Auto-activating connection '/310260575949457/context1'. Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) starting connection '/310260575949457/context1' Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) scheduled... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) started... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) complete. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): IPv4 static configuration: Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:address 100.152.35.130/30 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.177.0.34 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.168.183.116 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5
[Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
** Changed in: qtbase-opensource-src (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: qtbase-opensource-src (Ubuntu) Status: Fix Released => Fix Committed ** Also affects: qtbase-opensource-src (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu RTM) Status: New => Fix Released ** Changed in: qtbase-opensource-src (Ubuntu RTM) Assignee: (unassigned) => Tony Espy (awe) ** Changed in: qtbase-opensource-src (Ubuntu RTM) Importance: Undecided => High ** Changed in: qtbase-opensource-src (Ubuntu) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/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: In Progress Status in network-manager package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Triaged 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
@Selene Just wanted to confirm that we don't need any more investigation re: your comment #131 ( I think that may be the largest comment # I've seen in a LP bug ), as your latest update to bug #1524133 indicated that you'd isolated the problem to a SIM with an expired data plan? @Timo We should probably close this bug out when OTA8.5 is released, and then push another update to the PPA that contains the updated patch with the desktop crash fix ( bug #1523975 ). I've attached yet another of the version of the patch which just includes the additional wiredDevice NULL check from Lorn's latest patch. @Lorn Thanks again for all the help. Again, once the OTA8.5 update has been released, we can focus on transitioning to the connectivity API based bearer plugin for our next update. ** Patch added: "yet another update to our bearer-mgmt networkmanager patch" https://bugs.launchpad.net/ubuntu-rtm/+source/dbus-cpp/+bug/1480877/+attachment/4533428/+files/net-bearer-nm-disconnect-ap-signals7.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices Status in Canonical System Image: Fix Committed Status in Unity 8: New Status in dbus-cpp package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Fix Committed 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 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
So the latest changes in Lorn's signals6 patch can be summarized as: 1) remove QNetworkManagerEngine::requestUpdate (), which is a public method which can trigger a WiFi scan request to NM. This method doesn't appear to be called internally by the bearer plugin, so if we think extra WiFi scans are the culprit, there must have been an change to one of our Qt applications which is calling this method. Also as this method wasn't added in the original patch, it's presence can't really be considered a regression. Has anyone attempted to determine if we *are* scanning more often? This could be done manually by running wpa_cli ( as root ), and watching for the frequency of scan events output. It can also be accomplished by looking at the wpa_suppl and/or NM log messages in syslog. And finally, you could also just monitor DBus looking for ScanDone signals from NM. NOTE - I'm pretty sure this patch won't compile unless this method is also removed from qnetworkmanagerengine.h too, but I haven't tried to build it myself... 2) check that wiredDevice pointer is valid before using it to call a method This is the crasher fix when USS/Qt from the PPA gets installed on a desktop. Looks fine to me. 3) remove most of the logic from the engine's parseConnection() method. This method takes a connection path, and creates a private configuration object, and then based upon the underlying device type, may modify the private configuration instance in a device-specific way before returning it to the caller. The device-specific logic in some cases could have side-effects, such as modifying the global accessPointConfigurations hash table and/or the configuredAccessPoint map. Again, this chnage looks reasonable to remove, however I don't see how it could have any impact on power. This code only runs during initialization where all existing system connections are loaded, and whenever a new system connection is added ( ie. a user connects to a new AP or APN ). I'm not sure whether we want to include this the last change if we want to keep the delta as small as possible? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices Status in Canonical System Image: Fix Committed Status in Unity 8: New Status in dbus-cpp package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Fix Committed 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 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
