[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407928 Title: [phone] Does not auto-switch to available, known WiFi To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
I've confirmed with the original customer that this indeed *is* working as expected. As such, I'm updating the status on both tasks to 'Invalid'. ** Changed in: rsyslog (Ubuntu) Status: Incomplete => Invalid ** Changed in: snappy Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
** Changed in: rsyslog (Ubuntu) Status: New => Incomplete ** Changed in: snappy Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
I just updated the status to Incomplete for both bug tasks, as I may have been too confident in the original bug description given to me by the customer. The logrotate script as written is not meant to "restart" rsyslogd. Looking at the man page, the HUP signal (as sent by the /usr/lib/rsyslog /rsyslog-rotate script on postrotate) is meant to trigger rsyslogd to close all open files. My testing shows that this does seem to be working OK on both 16.04 classic and Core 16. I suspect that the problem may be due the way the customer is integrating with rsyslogd, and that this in turn might be why rsyslogd is holding on to the deleted files. I'm going to leave this bug open until we can determine the actual root cause, because as mentioned in the bug description, this can lead to a device running out of storage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464745] Re: logrotate file fails on all but sysvinit
This bug no longer exists in Ubuntu 16.04, as the rsyslog rotate script (inherited from the Debian package) handles both systemd and sysvinit based systems: $ more /usr/lib/rsyslog/rsyslog-rotate #!/bin/sh if [ -d /run/systemd/system ]; then systemctl kill -s HUP rsyslog.service else invoke-rc.d rsyslog rotate > /dev/null fi As such, I'm updating the status on this to Invalid. ** Changed in: rsyslog (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464745 Title: logrotate file fails on all but sysvinit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1464745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
@ogra If the component in question was removed and/or deprecated and no longer used in the current development release, then the policy shouldn't apply. In this case I don't think it would be much of a stretch to get a waiver for this. That said, as I'm pretty sure this bug is specific to Core, so fixing the issue in the core snap directly is probably the better approach. We can't just leave things "as is", as this bug can lead to Core devices running out of storage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
@ogra This is a bug in the core[16] snap. I'm not sure why we'd even consider SRU'ing to UC18 or UC20. On both of the those systems, core wouldn't be the booting snap, so any fix would be a no-op. Possible ways to fix include: - releasing an rsyslog SRU for 16.04, but as Michael points out this could impact classic OR - patch rsyslog in the core snap to do the right thing I'll spend more time on this as soon as I have some more cycles and will try to determine the exact cause of the restart failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868894] [NEW] [uc18] docker overlayfs* seems broken
Public bug reported: A customer recently reported that 'sudo docker run hello-world' fails on a pi3 or pi4 running UC18. Looking at the journal, the failure appears to be caused by an apparmor denial related docker's overlay2 storage driver. I've tried both the unified and the Pi3 specific UC18 images and both fail with the same error. The same command works fine on other devices running UC18 (I've tested multipass+macOS, and dragonboard), and also works on a Pi3b running our standard UC16 image. Here are the details from the UC18 image. $ snap list core16-2.43.3 8691stablecanonical✓ core core18 202001241673stablecanonical✓ base docker 18.09.9 427 stablecanonical✓ - pi 18-127 18-pi canonical✓ gadget pi-kernel 5.3.0-1019.21~18.04.1 104 18-pi canonical✓ kernel snapd 2.43.3 6438stablecanonical✓ snapd And here's the apparmor denial: Mar 24 19:38:55 localhost sudo[3095]: awe : TTY=pts/0 ; PWD=/home/awe ; USER=root ; COMMAND=/snap/bin/docker run hello-world Mar 24 19:39:02 localhost audit[2932]: AVC apparmor="DENIED" operation="open" profile="snap.docker.dockerd" name="/system-data/var/snap/docker/common/var-lib-docker/overlay2/afce643d5ac2c31f46b8c867c35abea776166c6da199fab370c30af17d314fd7-init/diff/.dockerenv" pid=2932 comm="dockerd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 I've been told this may end up being something that gets worked around in snapd, however as this looks like a regression, I'm erring on the side of caution and filing this bug anyways. Please let me know if there's anything else I can provide. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868894 Title: [uc18] docker overlayfs* seems broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1868894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836396] Re: Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues
snappy-hwe-snaps is a project used to track work related to system stack snaps published by Canonical. Your bug most likely has to do with the bluez (or related) Debian package from the Ubuntu archive. ** Project changed: snappy-hwe-snaps => bluez ** Project changed: bluez => bluez (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836396 Title: Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1836396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831519] Re: Battery percentage not displayed for Lenovo IdeaPad S145 running on Peppermint Linux 10.
This project is meant for tracking bugs and source code related to system stack snaps (bluez, modem-manager, ... ) published by Canonical. Please use a bug tracker for Peppermint Linux. ** Project changed: snappy-hwe-snaps => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831519 Title: Battery percentage not displayed for Lenovo IdeaPad S145 running on Peppermint Linux 10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1831519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls
@Alfonso What's the use case for calling 'netplan apply' in this scenario? Is NM the configured as the netplan renderer? Is there ever a case where "systemd-networkd-resolvconf-update.service" can call resolvconf even though NM is the renderer from the start (i.e. there's no transition from networkd to NM)? I've always contended that mixing two network management services on the same device was asking for trouble... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825194 Title: resolvconf is racy, which leads to broken resolv.conf in parallel calls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762672] Re: TPM intermittently fails after cold-boot
I just ran an additional five cycles of the testing described in my previous comment with no failures. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM intermittently fails after cold-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762672] Re: TPM intermittently fails after cold-boot
Tested the latest OEM kernel from -proposed on a Dell Edge Gateway 3000 running Ubuntu Server 18.04 LTS: # rmadison linux-image-oem | grep bionic-proposed linux-image-oem | 4.15.0.1035.40 | bionic-proposed | amd64 # dpkg -l | grep linux-image-oem ii linux-image-oem 4.15.0.1035.40 amd64OEM Linux kernel image Cold booted (x5) the system and instead of seeing "TPM error (2314)...selftest" messages, I see the following (expected) messages: Mar 28 18:35:01 1K5JB02 kernel: ACPI: TPM2 0x76D537C8 34 (v03 Tpm2Tabl 0001 AMI ) Mar 28 18:35:01 1K5JB02 kernel: tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) Mar 28 18:35:01 1K5JB02 kernel: tpm tpm0: A TPM error (2314) occurred attempting the self test Verified that the TPM is operational by running tpm2_listpcrs (version 3.1.3 built from source) using the in-kernel resource manager: admin@1K5JB02:~$ sudo -i root@1K5JB02:~# export LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH root@1K5JB02:~# export TPM2TOOLS_TCTI_NAME=device TPM2TOOLS_DEVICE_FILE=/dev/tpmrm0 root@1K5JB02:~# tpm2_startup --clear root@1K5JB02:~# tpm2_listpcrs Bank/Algorithm: TPM_ALG_SHA1(0x0004) PCR_00: 51 3f 1d 55 df 26 29 a2 42 ac 0b bf ae 7d 76 54 ef 91 24 d3 . . . ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM intermittently fails after cold-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762672] Re: TPM intermittently fails after cold-boot
@Tyler So it looks like we landed this just in time for the new SRU cycle, which means we're looking at a tentative release to proposed on Mar 25. Does that sound right? If so, I may check with Anthony to see if there's a possibility that linux-oem could possibly re-spin and release earlier... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM intermittently fails after cold-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762672] Re: TPM intermittently fails after cold-boot
@Khaled Just curious as to why this is now FixCommitted? Has Tyler's back-port landed in git for the next OEM and/or mainline kernel SRU release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM intermittently fails after cold-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762672] Re: TPM intermittently fails after cold-boot
** Description changed: - [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) - [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest - [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest - [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest - [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest - [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest - [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest - [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest - [3.423100] tpm tpm0: TPM self test failed - [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) + [Impact] + On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold boots. The problem seems to be that the TPM gets into a state where the partial self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to completion), but instead returns TPM_RC_TESTING (meaning some tests are still running in the background). A reboot can sometimes restore TPM functionality. + + This bug was originally reported on a Dell XPS 13, but has also recently + been reported on a Dell Edge Gateway 3000. + + The bug has been confirmed to be fixed in the current development + release (19.04/Cosmic). + + [Test Case] + Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop or Server and grep for the following error log message: + + "tpm tpm0: A TPM error (2314) occurred continue selftest" + + Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools + should produce errors. + + As this bug is due to a race condition, ideally this test case would be + run multiple times (20+ cold boots). + + Once the patch is installed the following error message may still be + present in the syslog, however attempts to use the TPM should work: + + "tpm tpm0: A TPM error (2314) occurred attempting the self test" + + [Regression Potential] + The chance of regression is low, as this patch was written by a well respected kernel developer with deep TPM experience. The patch is also being cherry-picked from the upstream stable and LTS kernels, and as mentioned, has already landed in Disco. + + [Original Description] + After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently fail on cold boot. The following log messages could be observed in syslog: + + [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) + [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest + [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest + [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest + [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest + [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest + [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest + [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest + [3.423100] tpm tpm0: TPM self test failed + [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) Discussion https://lkml.org/lkml/2017/12/6/284 Fix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6 - - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: linux-image-generic 4.15.0.13.14 - ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 - Uname: Linux 4.15.0-13-generic x86_64 - ApportVersion: 2.20.9-0ubuntu2 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: baz2268 F pulseaudio - CurrentDesktop: XFCE - Date: Tue Apr 10 11:41:57 2018 - EcryptfsInUse: Yes - HibernationDevice: RESUME=/dev/mapper/cryptswap1 - InstallationDate: Installed on 2018-03-01 (39 days ago) - InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301) - MachineType: Dell Inc. XPS 13 9360 - ProcFB: 0 inteldrmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1 - RelatedPackageVersions: - linux-restricted-modules-4.15.0-13-generic N/A - linux-backports-modules-4.15.0-13-generic N/A - linux-firmware 1.173 - SourcePackage: linux - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 01/25/2018 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: 2.5.1 - dmi.board.name: 02PG84 - dmi.board.vendor: Dell Inc. - dmi.board.version: A00 - dmi.chassis.type: 9 - dmi.chassis.vendor: Dell Inc. - dmi.modalias: dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr: - dmi.product.family: XPS - dmi.product.name: XPS 13 9360 - dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of
[Bug 1762672] Re: TPM intermittently fails after cold-boot
** Summary changed: - TPM on Dell XPS 13 stopped working after upgrade to 18.04 + TPM intermittently fails after cold-boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM intermittently fails after cold-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762672] Re: TPM on Dell XPS 13 stopped working after upgrade to 18.04
I've run 10 cold boots on the gateway mentioned in my previous comment, and in each case after issuing a tpm2_startup clear command, I've been able to query the NVLIST of the TPM. So the back-ported patch appears to be working as advertised. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM on Dell XPS 13 stopped working after upgrade to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762672] Re: TPM on Dell XPS 13 stopped working after upgrade to 18.04
@Tyler I've tested your kernel on a Dell Edge Gateway 3000 which was showing the same TPM selftest log messages as originally described in this bug. When cold-booted with your kernel I only see the following messages now: 14:57:44 [0.00] ACPI: TPM2 0x76D537C8 34 (v03 Tpm2Tabl 0001 AMI ) 14:57:44 [2.703384] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) 14:57:44 [2.714914] tpm tpm0: A TPM error (2314) occurred attempting the self test I was able to verify that the TPM is operational by running the following tpm2-tools commands: $ sudo tpm2_startup -T device --clear $ tpm2_nvlist (produces valid output) Note - in this case, the system is using the in-kernel resource manager, which it appears doesn't initialize the TPM, hence the need for using tpm2_startup to initialize the TPM. The version of tpm2-tools used is 2.1.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762672 Title: TPM on Dell XPS 13 stopped working after upgrade to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798384] Re: Grub allows to load unsigned kernel even BIOS enabled secure boot
Note it's possible to use grub2 configuration directives to lock down privileged operations (such as access to the shell). The 'superusers' and 'password*' directives can be used to require user auth before certain operations. It even looks like it's possible to completely disable these privileged operations by setting 'superusers' to an empty string. For more information see: https://www.gnu.org/software/grub/manual/grub/grub.html#Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798384 Title: Grub allows to load unsigned kernel even BIOS enabled secure boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1798384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781597 Title: [SRU] WoWLAN settings are not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791814] Re: The core snap was renamed to system in the 2.35 release
And after reverting core back to 2.34.1, it's reported as:
{
"snap": "core",
"slot": "optical-drive",
"interface": "optical-drive",
"label": ""
},
So yes, this looks like a valid bug. Also looks like "label:" was
dropped?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791814
Title:
[2.35.1] /v2/interfaces returns "system" instead of "core" as owning
snap of core interface slots
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1791814/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791814] Re: The core snap was renamed to system in the 2.35 release
I *think* (I don't have a pre-2.35 core snap at hand) the issue is that
the 'snap' attribute of the core interfaces as reported by snapd's
/v2/interfaces endpoint used to be set to "core", whereas with 2.35 it's
reported as "system". Here's a fragment of the JSON returned by this
endpoint for the optical-drive slot:
{
"snap": "system",
"slot": "optical-drive",
"interface": "optical-drive"
},
You can see this by running the following command:
$ curl --unix-socket /run/snapd.socket http:/v2/interfaces | jq
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791814
Title:
[2.35.1] /v2/interfaces returns "system" instead of "core" as owning
snap of core interface slots
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1791814/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791814] Re: The core snap was renamed to system in the 2.35 release
Sorry, the version of core that I reverted back to was 16-2.34.3 (5145), not 2.34.1. ** Summary changed: - The core snap was renamed to system in the 2.35 release + [2.35.1] /v2/interfaces returns "system" instead of "core" as owning snap of core interface slots -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791814 Title: [2.35.1] /v2/interfaces returns "system" instead of "core" as owning snap of core interface slots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1791814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771463] Re: [18.04 Server] Dependencies to be updated for EDM Support
The bug was accidentally reported against the wrong project. ** Changed in: ubuntu Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771463 Title: [18.04 Server] Dependencies to be updated for EDM Support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1771463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771463] Re: [18.04 Server] Dependencies to be updated for EDM Support
I just changed the status of this bug to Incomplete, and will follow up with the bug reporter as there's insufficient detail in the description, and most likely a misunderstanding of how Ubuntu dependencies work. ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771463 Title: [18.04 Server] Dependencies to be updated for EDM Support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1771463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392012 Title: [MIR] libteam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libteam/+bug/1392012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724537] Re: The revert features is not revert completed.
The description needs some more detail. >From what I've read, the bug is: 1) Install a new kernel snap from candidate channel which has known bugs 2) Verify that the bugs are reproducible 3) Revert the kernel snap back to the stable version 4) Re-test to ensure known bugs are not reproducible Expected result: Known bugs associated with new kernel snap aren't reproducible Actual result: Known bugs associated with new kernel snap are reproducible Does that sound correct? ** Changed in: snapd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724537 Title: The revert features is not revert completed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1724537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055068 Title: Guest user can use arbitrary MAC addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1055068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055068 Title: Guest user can use arbitrary MAC addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1055068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1023277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639754] Re: Ethernet devices have higher metric than wlan or wwan ones
As this has been fixed in netplan, I'm changing the status of the HWE task to Invalid. If this is incorrect, or there's something else we need to do in the NM snap, then feel free to re-open. ** Changed in: snappy-hwe-snaps Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639754 Title: Ethernet devices have higher metric than wlan or wwan ones To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-hwe-snaps/+bug/1639754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1478319 Title: Wifi doesn't reconnect to AP if it uses the same SSID than another AP To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634540] [NEW] Configuring a static IP address generates a netplan file without a gateway
Public bug reported: Configuring a static IP address for an ethernet device on an Ubuntu Core 16 system generates a netplan file without a gateway specified, thus the console-conf WaitDefaultRouteTask eventually times out. Here's the netplan file generated: network: ethernets: eth0: addresses: - 10.155.114.58/21 eth1: addresses: [] version: 2 Steps to reproduce: 1. Run console conf 2. Select ethernet interface 3. Configure a static IP address Subnet: 10.155.112.0/21 Address: 10.155.114.58 Gateway: 10.155.112.1 Expected Results: System come online with specified static IP address and gateway. Actual Results: Console-conf time out error is displayed. ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634540 Title: Configuring a static IP address generates a netplan file without a gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1634540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688286] Re: [MIR] ofono
Ah, thanks for the clarification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688286 Title: [MIR] ofono To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/688286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688286] Re: [MIR] ofono
@Michael Didn't quite catch that last bit about ofono-scripts. Care to elaborate? Is this something we should fix in our next landing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688286 Title: [MIR] ofono To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/688286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688286] Re: [MIR] ofono
** Changed in: ofono (Ubuntu) Importance: Undecided => Critical ** Changed in: ofono (Ubuntu) Status: Incomplete => In Progress ** Description changed: - Binary package hint: ofono + [Availability] + * Available in universe - I have reviewed the package and it meets the requirements for main - inclusion. It is a build dependency for geoclue, which is needed for - indicator-datetime. + [Rationale] + * This package is used on production device running Ubuntu Touch. Although it's no longer a hard dependency for Unity8, it's desirable to move it into main. + + [Security] + * A security review was performed prior to the Unity8 dendency fix. No know security issues at this time. + + [Quality Assurance] + * This package has unit tests, and new unit tests were added primarily to test the rilmodem driver, as part of Ubuntu Touch development. This package currently lacks autopkgtests. It does however include a binary ofono-scripts package with ~100 Python based test tools which are used for manual testing and debugging of Touch devices. Automated testing is possible via the ofono-phonesim package, but was not a priority due to a focus on the rilmodem driver testing on real hardware. This code has been heavily tested by Engineering and QA during the lifetime of Ubuntu Touch. + + [Dependencies] + All dependencies are already in main ( I'd like independent verification of this by a core-dev ). + + [Standards Compliance] + ( ) + + [Maintenance] + This package is maintained by Canonical and actively in use on the phone images. + + [Background] + This package is used to control one or more modems for data, sms, and/or voice. On Ubuntu Touch it is configured to use a builtin ofono modem driver called rilmodem, with which it controls a native or containerized rild daemon from an AOSP BSP. oFono may also be used with one of a variety of builtin plugins which talk directly to a modem thru a serial port or other device, using a native protocol such as the Hayes command set ( eg. AT Commands ). It was originally a joint project between Intel and Nokia and was used as part of MeeGo. It still is under active development by Intel, and thus is well supported upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688286 Title: [MIR] ofono To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/688286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551823 Title: PPTP connection does not work and dies after 2 minutes (on the phone) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616048] Re: Create interface for ofono
This certainly makes sense, but given our current plans, this isn't a high-priority interface in the short term. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616048 Title: Create interface for ofono To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1616048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614626] Re: [MIR] tone-generator
By "team bug subscriber", do you mean a team subscribed in Launchpad for this bug? I'll discuss with my manager, but can't necessarily volunteer my current team for this without his approval. As for whether or not this is a fork. Yes, it's a fork, and no there's been no need to collaborate with Jolla as the code is stable, and hasn't been touched since the package was created. >From the initial bzr revision: revno: 1 committer: Tony Espy <e...@canonical.com> branch nick: trunk timestamp: Wed 2014-07-30 15:52:39 -0400 message: Inital version of tone-generator daemon. Forked from: https://github.com/nemomobile/tone-generator --- If you checkout the link, the project's been mothballed, as it now redirects to: https://github.com/nemomobile-graveyard/tone-generator This is pretty simple bit of software, and at the time there weren't any alternatives... Replacing it would at minimum require an investigation task. An alternative would be to unwind unity8's dependency on this package, as it's not clear to me that a unity8 install really requires this package, as it's purpose is quite-specific to touch devices that include voice modems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614626 Title: [MIR] tone-generator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tone-generator/+bug/1614626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614626] [NEW] [MIR] tone-generator
Public bug reported: [Availability] * Available in universe [Rationale] * This package is required by unity8 [Security] * No known security issues at this time. It has been reviewed by security in the past for use on the phone. [Quality assurance] * This package has no unit tests or autopkgtests. It does include several shell scripts which use dbus-send to test the notification and dial tones. Automated testing of this package is difficult, as it requires a human being to verify that the tones are audible. [Dependencies] Most dependencies are already in main with the exception of the following: * telephony-service (bug #1613490) [Standards compliance] * This package uses autotools and adheres to FHS and Debian policy. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images. [Background] * This package is used to generate dial-tone (DTMF) or notification sounds. It provides a DBus API which clients use to start and stop generation of these sounds ( similar to the way MIDI works: note on/off ). It was written by Nokia, and was bundled as part of Moblin/MeeGo, and has also been more recently used by by Jolla for Sailfish OS. ** Affects: tone-generator (Ubuntu) Importance: Undecided Assignee: Michael Terry (mterry) Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614626 Title: [MIR] tone-generator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tone-generator/+bug/1614626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592696] Re: snaps don't work with encrypted home: failed to create user data directory. errmsg: Permission denied
Installing the proposed packages worked for me, albeit with an extra hoop of running a snap app as sudo first to get around the permission problem. After the installing, I did: % sudo snap install hello % hello mkdir: cannot create directory ‘/home/espy/snap/hello’: Permission denied % sudo /snap/bin/hello Hello, world! % hello Hello world! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592696 Title: snaps don't work with encrypted home: failed to create user data directory. errmsg: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1592696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598181] Re: No network showing from the dialer app even though phone calls are possible
A quick look at the list-modems output shows the following for the NetworkRegistration interface for SIM1: [ org.ofono.NetworkRegistration ] Mode = auto Strength = 100 Name = Technology = umts Status = registered LocationAreaCode = 20498 CellId = 15168848 Perhaps the lack of an operator "Name" is causing the dialer-app to show "No Network"? ** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Also affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598181 Title: No network showing from the dialer app even though phone calls are possible To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587808] Re: Ubuntu-emulator no network on latest image
@Dave Did you ever confirm my results per my last request in comment #11? It's looking more and more like I was mistaken, and that NM 1.2 may indeed be the culprit. I re-tested the emulator with the latest rc ( #27 ), and dropped a "manual" network-manager.override file in /etc/init. When I start the emulator, eth0 is properly configured as the default route, and networking is OK. If I then manually start network-manager, the default route disappears. It looks like there's code in NMDefaultRouteManager to remove pre-existing default routes, however the code does have logic to check if the route device is known, and only deletes it in certain circumstances. Unfortunately, there's little to no logging of this code path. I'll add some debug logs to the version of NM in silo 005, and re-test tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587808] Re: Ubuntu-emulator no network on latest image
@Pat Is there a new rc available then? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587808] Re: Ubuntu-emulator no network on latest image
By default, ubuntu-emulator creates an /etc/network/interfaces file with the following contents: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 10.0.2.15 netmask 255.255.255.0 gateway 10.0.2.2 dns-nameservers 10.0.2.3 iface eth1 inet manual iface eth2 inet manual iface eth3 inet manual iface eth4 inet manual iface eth5 inet manual These interfaces are processed individually by the init script network- interface, and as eth0 is the only 'auto' interface, ifupdown will attempt to configure it. My guess is that some system-level change in r20 introduces a race condition which prevents ifupdown from properly configuring the default route for eth0. If the network-interface jobs is restarted, the default route is properly configured, and the browser is able to access the network. That said, this doesn't resolve the problem with scopes not starting... Here's the syntax for re-starting the interface: # restart network-interface INTERFACE=eth0 Note, I've also tested the latest emulator rc ( #27 ) and confirmed that the restart works there as well. I also verified that I get the same system-settings failure ( eg. white screen after launching system- settings ) that @Dave described in comment #13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597681 Title: [CTA] Enable WAPI support To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599943] Re: Zombie outgoing call that can't be hung up
** Description changed: I dialed a number that happened to call me at the exact same moment - I received the call and completed it, but the outgoing call remains in a zombie state, can't be hung up and I can't make any other calls: $ /usr/share/ofono/scripts/hangup-call /ril_1/voicecall02 $ /usr/share/ofono/scripts/hangup-all $ /usr/share/ofono/scripts/list-calls [ /ril_1 ] [ /ril_1/voicecall02 ] LineIdentification = +48.. RemoteMultiparty = 0 RemoteHeld = 0 State = dialing Name = Emergency = 0 Multiparty = 0 [ /ril_0 ] + This bug was reported on a turbo running rc-proposed/127. The phone had + a single valid SIM card inserted in the second slot (/ril_1). + ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ofono 1.17.bzr6914+15.04.20160413.1-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.100-user-01769-g42b9fe3 aarch64 ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Thu Jul 7 19:49:32 2016 InstallationDate: Installed on 2016-07-07 (0 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160707-020304) SourcePackage: ofono UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599943 Title: Zombie outgoing call that can't be hung up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1599943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589489 Title: cannot connect to known Wi-Fi after OTA-11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1589489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593686 Title: Wi-Fi passphrase limit introduced in OTA-11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593686 Title: Wi-Fi passphrase limit introduced in OTA-11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: [touch] Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: [touch] Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588127] Re: Phone abandons incoming call
** Changed in: ofono (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588127 Title: Phone abandons incoming call To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565717 Title: No connection after returning from area without coverage To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579098 Title: [touch] Mobile data connection drops, and doesn't automatically reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594938 Title: [arale] Hotspot activation doesn't always work To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594938 Title: [arale] Hotspot activation doesn't always work To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594938 Title: [arale] Hotspot activation doesn't always work To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection
@Simon Pretty sure my results reported in comment #11 were using the silo, so 5.37 doesn't resolve the problem. I just re-tested on arale ( rc-proposed, 350 ) and still see the same behavior on the initial connect of the headset. Unfortunately, I can't seem to get the headset to work at all now with the latest rc-proposed image. I'll retry on krillin later today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1527354 Title: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587808] Re: Ubuntu-emulator no network on latest image
I created an emulator instance using revision 19. I verified indeed that it's running NM , per comment #8. The indicator shows that airplane mode is active, although urfill isn't running ( /usr/share/urfkill/scripts/flight-mode throws an error ). When I run 'nmcli d', I see that ril_0 ( the modem ) is unavailable, and then I see a number of ethernet devices listed, all which are reported as "unmanaged". This means NM isn't managing the devices. In the case of the emulator, 'eth0' is configured in /etc/network/interfaces like this: auto eth0 iface eth0 inet static address 10.0.2.15 netmask 255.255.255.0 gateway 10.0.2.2 dns-nameservers 10.0.2.3 To confirm that NM really doesn't effect the default networking in the emulator, I dropped an upstart override containing "manual" into /etc/init, and re-started the emulator. I re-started, confirmed NM was longer running, and then used wget to pull down a webpage ( slashdot.org ). Next I created an emulator using the latest rc image ( #23 ), and after swiping down in the OOB/How-To-Swipe app, I get a white screen, and the apps scope is never displayed, nor does the launcher appear when dragging from the left. I re-created an emulator using revision 20, with the same effect. If I kill the instance, and restart, after entering the device PIN, I again just get a white screen. phablet-screenshot isn't able to grab an image either... The last thing I see on the console is: [4.994175] systemd-logind[606]: Failed to start user service: Unknown unit: user@0.service * Setting up X socket directories...[ OK ] /lib/init/init-d-script: 12: /etc/rc2.d/S02whoopsie: -c: not found basename: missing operand Try 'basename --help' for more information. * Starting virtual private network daemon(s)... [ 10.583711] systemd-logind[606]: Failed to start user service: Unknown unit: user@32011.service sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glTexParameterf:1786 error 0x500 sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glTexParameterf:1786 error 0x500 I see these same errors with revision 19, so they don't seem to be the cause of the networking and/or unity errors. @Dave Could you try to disable NM startup per my instructions above and see if you get the same results? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579098 Title: [touch] Mobile data connection drops, and doesn't automatically reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587808] Re: Ubuntu-emulator no network on latest image
Any chance you can fire up an old emulator image and prove this? Again, although there is a modem emulation included in the emulator image ( it's part of qemu ), it's not sufficient for us to run a full ofono/rilmodem against. AFAIK, there's no special trigger to configure ofono phonesim on the emulator either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587808] Re: Ubuntu-emulator no network on latest image
We've never really had any kind of working mobile data support in the emulator. There was an effort a long time ago to try and make this work for CI testing of ofono, but as it was estimated to be a major under- taking, we abandoned it. It should be possible to use the ofono phonesim package to do some testing of the telephony related components, however again this isn't something that would be configured by default either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587808] Re: Ubuntu-emulator no network on latest image
** Changed in: phablet-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587808 Title: Ubuntu-emulator no network on latest image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: [touch] Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565717
Title:
No connection after returning from area without coverage
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565717/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565717 Title: No connection after returning from area without coverage To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: [touch] Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: [touch] Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565717 Title: No connection after returning from area without coverage To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565717 Title: No connection after returning from area without coverage To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565717 Title: No connection after returning from area without coverage To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557026 Title: Network Manager sets powersave off by default in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1557026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: Internet connection stops working while WiFi is still connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1580146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557026
Title:
Network Manager sets powersave off by default in xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1557026/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
