[Touch-packages] [Bug 1908259] Re: TEST-36-NUMAPOLICY fails with qemu 5.2
Upstream CI as well as local autopkgtest runs confirm that the new systemd test code will make the new qemu pass. # Formerly failing $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries -o systemd-vs-qemu5.2 --apt-upgrade --apt-pocket=proposed=src:qemu --setup-commands="add-apt-repository ppa:ci-trg ... autopkgtest [17:09:01]: test upstream: ---] upstream PASS autopkgtest [17:09:02]: test upstream: - - - - - - - - - - results - - - - - - - - - - autopkgtest [17:09:03]: summary upstream PASS qemu-system-x86_64: terminating on signal 15 from pid 1783557 (/usr/bin/python3) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908259 Title: TEST-36-NUMAPOLICY fails with qemu 5.2 Status in systemd: Unknown Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Hi, this test now fails as seen on ppc here https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/s/systemd/20201214_224336_8b0d8@/log.gz + /bin/qemu-system-ppc64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinux-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.qFc3xq/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=hvc0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' E: QEMU failed with exit code 1 qemu-system-ppc64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) Reproducible in LP infra with systemd 246.6-5ubuntu1 and qemu 5.2 On other architectures this test is just skipped and ppc happened to complete faster so I saw it earlier. The same happens on amd64 + /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.8Hqpmk/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) E: QEMU failed with exit code 1 Isolated this to a test without systemd: $ apt install linux-image-generic qemu-system-x86 $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' Upgrading to 5.2 makes this: $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) The numa spec is indeed a bit short -numa node,nodeid=0 If I change this to -numa node,mem=512M,nodeid=0 It would work, but that kind of specification is forbidden >=5.1 Parameter -numa node,mem is not supported by this machine type Use -numa node,memdev instead You'd need also something like -M pc-i440fx-5.0 which isn't anything the test wants to set in stone I guess. Instead using memdev works: -object memory-backend-ram,id=mem0,size=512M -numa node,memdev=mem0,nodeid=0 This works fine and is in qemu since quite some time. Properly documented since 2.12 but actually available since 2.1 (2014) The argument for this test is in test/TEST-36-NUMAPOLICY/test.sh QEMU_OPTIONS="-numa node,nodeid=0" Fixing that to a new form should help. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1908259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908259] Re: TEST-36-NUMAPOLICY fails with qemu 5.2
https://github.com/systemd/systemd/pull/17987 was accepted upstream. I assume with the amount of dependencies that systemd has there is no easy "just apply this and upload" that will make anyone happy :-/ But now that everything seems ready I wanted to ask the package maintainer (who usually has a plan on coming uploads already) when we could get this applied? ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908259 Title: TEST-36-NUMAPOLICY fails with qemu 5.2 Status in systemd: Unknown Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Hi, this test now fails as seen on ppc here https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/s/systemd/20201214_224336_8b0d8@/log.gz + /bin/qemu-system-ppc64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinux-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.qFc3xq/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=hvc0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' E: QEMU failed with exit code 1 qemu-system-ppc64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) Reproducible in LP infra with systemd 246.6-5ubuntu1 and qemu 5.2 On other architectures this test is just skipped and ppc happened to complete faster so I saw it earlier. The same happens on amd64 + /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.8Hqpmk/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) E: QEMU failed with exit code 1 Isolated this to a test without systemd: $ apt install linux-image-generic qemu-system-x86 $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' Upgrading to 5.2 makes this: $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) The numa spec is indeed a bit short -numa node,nodeid=0 If I change this to -numa node,mem=512M,nodeid=0 It would work, but that kind of specification is forbidden >=5.1 Parameter -numa node,mem is not supported by this machine type Use -numa node,memdev instead You'd need also something like -M pc-i440fx-5.0 which isn't anything the test wants to set in stone I guess. Instead using memdev works: -object memory-backend-ram,id=mem0,size=512M -numa node,memdev=mem0,nodeid=0 This works fine and is in qemu since quite some time. Properly documented since 2.12 but actually available since 2.1 (2014) The argument for this test is in test/TEST-36-NUMAPOLICY/test.sh QEMU_OPTIONS="-numa node,nodeid=0" Fixing that to a new form should help. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1908259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1907306] Re: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1907306 Title: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: In Progress Bug description: [impact] networkd dhcpv4 client never attempts more than 2 renew and 2 rebind [test case] configure an interface to use dhcpv4; acquire a dhcpv4 address, then stop the dhcpv4 server, and wait for the networkd client to perform its renewals and rebinds before expiring the lease using a 20 minute lease time as an example (all times are approximate due to RFC-mandated random 'fuzz' time of -1 to +1 sec): the current behavior would be to sent renew requests at: 10:00 13:45 and then rebind requests at: 17:30 18:45 then the lease would expire at 20:00 the correct/new behavior should be renew requests at: 10:00 13:45 15:37 16:37 and then rebind requests at: 17:30 18:45 19:45 and then lease expiration at 20:00. longer lease times would increase the number of retransmissions. [regression potential] any regression would likely result in problems receiving and/or maintaining a dhcpv4 address [scope] this is needed in b/f/g/h. this was fixed upstream in: https://github.com/systemd/systemd/pull/17908 that was just added, so this is not fixed in any ubuntu release yet. technically, this is needed in x as well, however I don't plan to backport to x since 1) it reaches ESM soon and 2) the default network management tool in x is ifupdown, not systemd-networkd. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1907306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
** Description changed: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 3) Recompile SSSD completely to use libcrypto as backend [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. - Then the tool might fail if the card certificate is not added to the ca- - certificates.crt, but this is outside the scope of the test case. + Then: + 1) If you previously configured SSSD match rules and/or CA certificates: + - You should still get your certificate public key printed as output + - Configured login with smartcard should continue working - What it matters is that the card is found. + 2) If SSSD was not configured to do smartcard authentication: + - p11_child may fail if the card certificate was not previously added to + the trusted DB, but this is outside of this test case. + - What it matters is that the card is found. [ Regression potential ] While the change may involve quite different code paths when it comes to security features, I think we trust OpenSSL enough to be an acceptable crypto backend for PKCS#11 operations. Behavior should not change, also assuming that upstream dropped NSS support completely in latest release [3], keeping the same functionalities. As per a further review of this by xnox [4], we can safely assume that SSSD does not use libcrypto for operations where its behavior should differ from NSS. As it's needed only
[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/sssd/+git/sssd/+merge/395411 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 3) Recompile SSSD completely to use libcrypto as backend [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. Then the tool might fail if the card certificate is not added to the ca-certificates.crt, but this is outside the scope of the test case. What it matters is that the card is found. [ Regression potential ] While the change may involve quite different code paths when it comes to security features, I think we trust OpenSSL enough to be an acceptable crypto backend for PKCS#11 operations. Behavior should not change, also assuming that upstream dropped NSS support completely in latest release [3], keeping the same functionalities. As per a further review of this by xnox [4], we can safely assume that SSSD does not use libcrypto for operations where its
[Touch-packages] [Bug 1872824] Re: Can't upgrade console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package ke
I got stuck in this situation as well, and I was able to manually "unstick" things like this: ```sudo apt install -f -y console-setup-linux keyboard-configuration console-setup systemd libpam-systemd``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1872824 Title: Can't upgrade console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console- setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5 Status in console-setup package in Ubuntu: Confirmed Bug description: Upgrade path from 16.04 to 20.04 fails. console-setup-linux_1.194ubuntu3_all.deb tries to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5. I have reproduced this bug on bare metal and WSL. Log: Unpacking console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5) ... dpkg: error processing archive /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb (--unpack): trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../keyboard-configuration_1.194ubuntu3_all.deb ... Unpacking keyboard-configuration (1.194ubuntu3) over (1.108ubuntu15.5) ... Preparing to unpack .../busybox-initramfs_1%3a1.30.1-4ubuntu6_amd64.deb ... Unpacking busybox-initramfs (1:1.30.1-4ubuntu6) over (1:1.22.0-15ubuntu1.4) ... Preparing to unpack .../initramfs-tools-bin_0.136ubuntu6_amd64.deb ... Unpacking initramfs-tools-bin (0.136ubuntu6) over (0.122ubuntu8.16) ... Preparing to unpack .../cpio_2.13+dfsg-2_amd64.deb ... Unpacking cpio (2.13+dfsg-2) over (2.11+dfsg-5ubuntu1.1) ... Preparing to unpack .../liblz4-1_1.9.2-2_amd64.deb ... Unpacking liblz4-1:amd64 (1.9.2-2) over (0.0~r131-2ubuntu2) ... Processing triggers for libc-bin (2.31-0ubuntu7) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.27) ... Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1872824/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/sssd/+git/sssd/+merge/395410 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 3) Recompile SSSD completely to use libcrypto as backend [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. Then the tool might fail if the card certificate is not added to the ca-certificates.crt, but this is outside the scope of the test case. What it matters is that the card is found. [ Regression potential ] While the change may involve quite different code paths when it comes to security features, I think we trust OpenSSL enough to be an acceptable crypto backend for PKCS#11 operations. Behavior should not change, also assuming that upstream dropped NSS support completely in latest release [3], keeping the same functionalities. As per a further review of this by xnox [4], we can safely assume that SSSD does not use libcrypto for operations where its
[Touch-packages] [Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression
To anyone following this bug: As we get ready to re-release the new adcli package which implements the --use-ldaps flag, if you are happy to spend a few moments testing the new package, I would really appreciate it. I really don't want to cause another regression again. You can install the new adcli package in -proposed like so: Enable -proposed by running the following command to make a new sources.list.d entry: 1) cat << EOF | sudo tee /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed main universe EOF 2) sudo apt update 3) sudo apt install adcli 4) sudo apt-cache policy adcli | grep Installed Installed: 0.8.2-1ubuntu1.2 5) sudo apt-cache policy libsasl2-modules-gssapi-mit | grep Installed Installed: 2.1.27~101-g0780600+dfsg-3ubuntu2.3 6) sudo rm /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list 7) sudo apt update >From there, join your domain like normal, and if you like, try out other adcli or realm commands to ensure they work. Let me know how the new adcli package in -proposed goes. In my testing, it fixes the regression, and works as intended. To Jason Alavaliant, thanks! I really appreciate the help testing. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1906627 Title: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression Status in adcli package in Ubuntu: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in adcli source package in Bionic: Fix Committed Status in cyrus-sasl2 source package in Bionic: Fix Committed Bug description: [Impact] A recent release of adcli 0.8.2-1ubuntu1 to bionic-updates caused a regression for some users when attempting to join a Active Directory realm. adcli introduced a default behaviour change, moving from GSS- API to GSS-SPNEGO as the default channel encryption algorithm. adcli uses the GSS-SPNEGO implementation from libsasl2-modules-gssapi- mit, a part of cyrus-sasl2. The implementation seems to have some compatibility issues with particular configurations of Active Directory on recent Windows Server systems. Particularly, adcli sends a ldap query to the domain controller, which responds with a tcp ack, but never returns a ldap response. The connection just hangs at this point and no more traffic is sent. You can see it on the packet trace below: https://paste.ubuntu.com/p/WRnnRMGBPm/ On Focal, where the implementation of GSS-SPNEGO is working, we see a full exchange, and adcli works as expected: https://paste.ubuntu.com/p/8668pJrr2m/ The fix is to not assume use of confidentiality and integrity modes, and instead use the flags negotiated by GSS-API during the initial handshake, as required by Microsoft's implementation. [Testcase] You will need to set up a Windows Server 2019 system, install and configure Active Directory and enable LDAP extensions and configure LDAPS and import the AD SSL certificate to the Ubuntu client. Create some users in Active Directory. On the Ubuntu client, set up /etc/hosts with the hostname of the Windows Server machine, if your system isn't configured for AD DNS. From there, install adcli 0.8.2-1 from -release. $ sudo apt install adcli Set up a packet trace with tcpdump: $ sudo tcpdump -i any port '(389 or 3268 or 636 or 3269)' Next, join the AD realm using the normal GSS-API: # adcli join --verbose -U Administrator --domain WIN- SB6JAS7PH22.testing.local --domain-controller WIN- SB6JAS7PH22.testing.local --domain-realm TESTING.LOCAL You will be prompted for Administrator's passowrd. The output should look like the below: https://paste.ubuntu.com/p/NWHGQn746D/ Next, enable -proposed, and install adcli 0.8.2-1ubuntu1 which caused the regression. Repeat the above steps. Now you should see the connection hang. https://paste.ubuntu.com/p/WRnnRMGBPm/ Finally, install the fixed cyrus-sasl2 package from -proposed https://launchpad.net/~mruffell/+archive/ubuntu/lp1906627-test $ sudo apt-get update $ sudo apt install libsasl2-2 libsasl2-modules libsasl2-modules-db libsasl2-modules-gssapi-mit Repeat the steps. GSS-SPNEGO should be working as intended, and you should get output like below: https://paste.ubuntu.com/p/W5cJNGvCsx/ [Where problems could occur] Since we are changing the implementation of GSS-SPNEGO, and cyrus- sasl2 is the library which provides it, we can potentially break any package which depends on libsasl2-modules-gssapi-mit for GSS-SPNEGO. $ apt rdepends libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-mit Reverse Depends: |Suggests: ldap-utils Depends: adcli Conflicts: libsasl2-modules-gssapi-heimdal
[Touch-packages] [Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression
Performing verification for Bionic Firstly, I installed adcli and libsasl2-modules-gssapi-mit from -updates: adcli 0.8.2-1 libsasl2-modules-gssapi-mit 2.1.27~101-g0780600+dfsg-3ubuntu2.1 >From there, I joined a Active Directory realm: https://paste.ubuntu.com/p/zJhvpRzktk/ Next, I enabled -proposed and installed the fixed cyrus-sasl2 and adcli packages: https://paste.ubuntu.com/p/cRrbkjjFmw/ We see that installing adcli 0.8.2-1ubuntu1.2 automatically pulls in the fixed cyrus-sasl2 2.1.27~101-g0780600+dfsg-3ubuntu2.3 packages because of the depends we set. Next, I joined a Active Directory realm, using the same commands as previous, i.e. not using the new --use-ldaps flag, but instead, falling back to GSS-API and the new GSS-SPNEGO changes: https://paste.ubuntu.com/p/WdKYxxDBQm/ The join succeeds, and does not get stuck. This shows that the implementation of GSS-SPNEGO is now compatible with Active Directory, and that the new adcli package is using the new implementation. Looking at the packet trace, we see the full 30 or so packets exchanged, which matches the expect count. https://paste.ubuntu.com/p/k9njh3jYHh/ With these changes, the adcli and cyrus-sasl2 packages in -proposed can join realms in the same ways that the initial packages in -updates can. These changes fix the recent adcli regression. Happy to mark verified. ** Tags removed: regression-update verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1906627 Title: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression Status in adcli package in Ubuntu: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in adcli source package in Bionic: Fix Committed Status in cyrus-sasl2 source package in Bionic: Fix Committed Bug description: [Impact] A recent release of adcli 0.8.2-1ubuntu1 to bionic-updates caused a regression for some users when attempting to join a Active Directory realm. adcli introduced a default behaviour change, moving from GSS- API to GSS-SPNEGO as the default channel encryption algorithm. adcli uses the GSS-SPNEGO implementation from libsasl2-modules-gssapi- mit, a part of cyrus-sasl2. The implementation seems to have some compatibility issues with particular configurations of Active Directory on recent Windows Server systems. Particularly, adcli sends a ldap query to the domain controller, which responds with a tcp ack, but never returns a ldap response. The connection just hangs at this point and no more traffic is sent. You can see it on the packet trace below: https://paste.ubuntu.com/p/WRnnRMGBPm/ On Focal, where the implementation of GSS-SPNEGO is working, we see a full exchange, and adcli works as expected: https://paste.ubuntu.com/p/8668pJrr2m/ The fix is to not assume use of confidentiality and integrity modes, and instead use the flags negotiated by GSS-API during the initial handshake, as required by Microsoft's implementation. [Testcase] You will need to set up a Windows Server 2019 system, install and configure Active Directory and enable LDAP extensions and configure LDAPS and import the AD SSL certificate to the Ubuntu client. Create some users in Active Directory. On the Ubuntu client, set up /etc/hosts with the hostname of the Windows Server machine, if your system isn't configured for AD DNS. From there, install adcli 0.8.2-1 from -release. $ sudo apt install adcli Set up a packet trace with tcpdump: $ sudo tcpdump -i any port '(389 or 3268 or 636 or 3269)' Next, join the AD realm using the normal GSS-API: # adcli join --verbose -U Administrator --domain WIN- SB6JAS7PH22.testing.local --domain-controller WIN- SB6JAS7PH22.testing.local --domain-realm TESTING.LOCAL You will be prompted for Administrator's passowrd. The output should look like the below: https://paste.ubuntu.com/p/NWHGQn746D/ Next, enable -proposed, and install adcli 0.8.2-1ubuntu1 which caused the regression. Repeat the above steps. Now you should see the connection hang. https://paste.ubuntu.com/p/WRnnRMGBPm/ Finally, install the fixed cyrus-sasl2 package from -proposed https://launchpad.net/~mruffell/+archive/ubuntu/lp1906627-test $ sudo apt-get update $ sudo apt install libsasl2-2 libsasl2-modules libsasl2-modules-db libsasl2-modules-gssapi-mit Repeat the steps. GSS-SPNEGO should be working as intended, and you should get output like below: https://paste.ubuntu.com/p/W5cJNGvCsx/ [Where problems could occur] Since we are changing the implementation of GSS-SPNEGO, and cyrus- sasl2 is the library which provides it, we can potentially break any package which depends on libsasl2-modules-gssapi-mit for
[Touch-packages] [Bug 1908314] Re: Flicking screen on intel card
I'm guessing this would be bug 1896091, but to be sure please attach a photo or video of the problem. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908314 Title: Flicking screen on intel card Status in Ubuntu: Incomplete Bug description: Flicking screen on intel card ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 22:46:01 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a0] InstallationDate: Installed on 2020-12-10 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Latitude 7480 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=UUID=2d2eba82-dddc-469c-8508-b0cc7269226b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2020 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 00F6D3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd07/26/2020:br1.19:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7480 dmi.product.sku: 07A0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1908314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908273] Re: Software stopped working
The only relevant error I can see is a crash in your graphics driver is affecting some Python app: [681600.192682] python3.8[1480136]: segfault at 24 ip 7fbbd34a3c14 sp 7ffc3c62aef0 error 6 in iris_dri.so[7fbbd2a72000+d49000] [681600.192702] Code: 2b 7e 30 01 c7 81 ff ff ff 00 00 0f 87 9d 17 00 00 48 01 c8 48 89 46 38 48 85 c9 0f 84 10 06 00 00 83 ea 01 81 ca 00 00 09 78 <89> 11 48 8d 51 04 45 85 ff 74 76 41 8d 47 ff 48 8d 4c c1 0c 0f 1f Please try: 1. Launching the affected apps from a Terminal window then copy and paste any errors you see here. 2. Check for crash reports using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908273 Title: Software stopped working Status in mesa package in Ubuntu: Incomplete Bug description: After update to Ubuntu 20.04.1 LTS some of my software stopped working, all of it is visualization software: VMD, Discovery Studio, PyMOL, Gmolden, Avogadro. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 14:41:52 2020 DistUpgraded: 2020-11-21 20:16:19,197 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Wykonanie procesu potomnego „./xorg_fix_proprietary.py” (Nie ma takiego pliku ani katalogu) się nie powiodło (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8537] InstallationDate: Installed on 2020-05-20 (208 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 0408:5373 Quanta Computer, Inc. HP HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-21 (23 days ago) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8537 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD0097RK4 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 440 G6 dmi.product.sku: 5PQ09EA#AKD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908265] Re: bad heating
I can't see any explanation for such a problem in the attached files. Please run 'top' in a Terminal window and tell us what processes are using the most CPU. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908265 Title: bad heating Status in Ubuntu: Incomplete Bug description: i had dell pre-installed ubuntu, but i had erase it. now i am facing heating issues ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 17:59:23 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08c8] InstallationDate: Installed on 2020-12-11 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Bus 001 Device 002: ID 27c6:5301 Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-124-generic root=UUID=4f0e25d7-2cd2-474f-9088-9df1ffccd1ce ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0H40C6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:svnDellInc.:pnVostro3480:pvr:rvnDellInc.:rn0H40C6:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3480 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1908265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906600] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444020/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device
[Touch-packages] [Bug 1906600] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444021/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820]
[Touch-packages] [Bug 1906600] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444029/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820]
[Touch-packages] [Bug 1906600] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444028/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:
[Touch-packages] [Bug 1906600] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444031/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820]
[Touch-packages] [Bug 1906600] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444030/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:
[Touch-packages] [Bug 1906600] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444027/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:
[Touch-packages] [Bug 1906600] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444026/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:
[Touch-packages] [Bug 1906600] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444025/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:
[Touch-packages] [Bug 1906600] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444024/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:
[Touch-packages] [Bug 1906600] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444023/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:
[Touch-packages] [Bug 1906600] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444022/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820]
[Touch-packages] [Bug 1906600] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444018/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device
[Touch-packages] [Bug 1906600] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444017/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820]
[Touch-packages] [Bug 1906600] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444019/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820]
[Touch-packages] [Bug 1906600] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444016/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:
[Touch-packages] [Bug 1906600] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444015/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device
[Touch-packages] [Bug 1906600] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444014/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820]
[Touch-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
If I have done this correctly, and that is truly questionable, I just installed one of the generic kernels from https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.10-rc6/amd64/ then restarted the PC and was connected for 8 - 10 minutes, but then the connection dropped again. I had installed: linux- modules-5.10.0-051000rc6-generic_5.10.0-051000rc6.202011291930_amd64.deb. Here is what it shows I am running: bryan@bryan-HP-Notebook:~$ uname -r 5.4.0-58-generic I will run the apport again to upload immediately after posting this message. As always, I thank you for your help. Cheers! ** Description changed: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01
[Touch-packages] [Bug 1908312] Re: [Echo-NHH, playback] fails after a while (stutter)
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1908312 Title: [Echo-NHH, playback] fails after a while (stutter) Status in alsa-driver package in Ubuntu: New Bug description: Bluetooth playback suffers from intermittent stutters. Happens on multiple bluetooth speakers (I tested it).Apparently this is a known problem because there is a whole thread about it on Reddit, which seems a bit ridiculous this has been an issue for 9 or 10 years and hasn't been resolved yet because bluetooth speakers are so common now. Playback improved somewhat when auto-mute is disabled via alsmixer (but ONLY when the system is active. If screensaver engages to shut down the screens, the stutters begin shortly thereafter.Prior to disabling auto-mute, the system would intermittently stutter regardless of whether screen saver/power saver modes were active. Am using Ubuntu 20.10 (had the same issue under the prior version of ubuntu too). Software center version is 3.38.1. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j 1726 F pulseaudio /dev/snd/controlC1: j 1726 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 15:35:16 2020 InstallationDate: Installed on 2020-05-21 (208 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Echo-NHH Symptom_Type: Sound works for a while, then breaks Title: [Echo-NHH, playback] fails after a while UpgradeStatus: Upgraded to groovy on 2020-10-28 (48 days ago) dmi.bios.date: 01/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd01/11/2013:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1908312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908312] [NEW] [Echo-NHH, playback] fails after a while (stutter)
You have been subscribed to a public bug: Bluetooth playback suffers from intermittent stutters. Happens on multiple bluetooth speakers (I tested it).Apparently this is a known problem because there is a whole thread about it on Reddit, which seems a bit ridiculous this has been an issue for 9 or 10 years and hasn't been resolved yet because bluetooth speakers are so common now. Playback improved somewhat when auto-mute is disabled via alsmixer (but ONLY when the system is active. If screensaver engages to shut down the screens, the stutters begin shortly thereafter.Prior to disabling auto-mute, the system would intermittently stutter regardless of whether screen saver/power saver modes were active. Am using Ubuntu 20.10 (had the same issue under the prior version of ubuntu too). Software center version is 3.38.1. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j 1726 F pulseaudio /dev/snd/controlC1: j 1726 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 15:35:16 2020 InstallationDate: Installed on 2020-05-21 (208 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Echo-NHH Symptom_Type: Sound works for a while, then breaks Title: [Echo-NHH, playback] fails after a while UpgradeStatus: Upgraded to groovy on 2020-10-28 (48 days ago) dmi.bios.date: 01/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd01/11/2013:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- [Echo-NHH, playback] fails after a while (stutter) https://bugs.launchpad.net/bugs/1908312 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908314] [NEW] Flicking screen on intel card
Public bug reported: Flicking screen on intel card ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 22:46:01 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a0] InstallationDate: Installed on 2020-12-10 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Latitude 7480 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=UUID=2d2eba82-dddc-469c-8508-b0cc7269226b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2020 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 00F6D3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd07/26/2020:br1.19:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7480 dmi.product.sku: 07A0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908314 Title: Flicking screen on intel card Status in xorg package in Ubuntu: New Bug description: Flicking screen on intel card ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 22:46:01 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a0] InstallationDate: Installed on 2020-12-10 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Latitude 7480 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=UUID=2d2eba82-dddc-469c-8508-b0cc7269226b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2020 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 00F6D3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd07/26/2020:br1.19:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7480 dmi.product.sku: 07A0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1908314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1907306] Re: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind
** Merge proposal linked: https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/395398 ** Merge proposal linked: https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/395399 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1907306 Title: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: In Progress Bug description: [impact] networkd dhcpv4 client never attempts more than 2 renew and 2 rebind [test case] configure an interface to use dhcpv4; acquire a dhcpv4 address, then stop the dhcpv4 server, and wait for the networkd client to perform its renewals and rebinds before expiring the lease using a 20 minute lease time as an example (all times are approximate due to RFC-mandated random 'fuzz' time of -1 to +1 sec): the current behavior would be to sent renew requests at: 10:00 13:45 and then rebind requests at: 17:30 18:45 then the lease would expire at 20:00 the correct/new behavior should be renew requests at: 10:00 13:45 15:37 16:37 and then rebind requests at: 17:30 18:45 19:45 and then lease expiration at 20:00. longer lease times would increase the number of retransmissions. [regression potential] any regression would likely result in problems receiving and/or maintaining a dhcpv4 address [scope] this is needed in b/f/g/h. this was fixed upstream in: https://github.com/systemd/systemd/pull/17908 that was just added, so this is not fixed in any ubuntu release yet. technically, this is needed in x as well, however I don't plan to backport to x since 1) it reaches ESM soon and 2) the default network management tool in x is ifupdown, not systemd-networkd. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1907306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1907306] Re: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind
** Description changed: [impact] networkd dhcpv4 client never attempts more than 2 renew and 2 rebind [test case] configure an interface to use dhcpv4; acquire a dhcpv4 address, then stop the dhcpv4 server, and wait for the networkd client to perform its renewals and rebinds before expiring the lease + using a 20 minute lease time as an example (all times are approximate + due to RFC-mandated random 'fuzz' time of -1 to +1 sec): + + the current behavior would be to sent renew requests at: + + 10:00 + 13:45 + + and then rebind requests at: + + 17:30 + 18:45 + + then the lease would expire at 20:00 + + the correct/new behavior should be renew requests at: + + 10:00 + 13:45 + 15:37 + 16:37 + + and then rebind requests at: + + 17:30 + 18:45 + 19:45 + + and then lease expiration at 20:00. + + longer lease times would increase the number of retransmissions. + [regression potential] any regression would likely result in problems receiving and/or maintaining a dhcpv4 address [scope] - this is in progress upstream, and would need to be applied to all - releases + this is needed in b/f/g/h. + + this was fixed upstream in: + https://github.com/systemd/systemd/pull/17908 + + that was just added, so this is not fixed in any ubuntu release yet. + + technically, this is needed in x as well, however I don't plan to + backport to x since 1) it reaches ESM soon and 2) the default network + management tool in x is ifupdown, not systemd-networkd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1907306 Title: networkd dhcpv4 client never attempts more than 2 renew and 2 rebind Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: In Progress Bug description: [impact] networkd dhcpv4 client never attempts more than 2 renew and 2 rebind [test case] configure an interface to use dhcpv4; acquire a dhcpv4 address, then stop the dhcpv4 server, and wait for the networkd client to perform its renewals and rebinds before expiring the lease using a 20 minute lease time as an example (all times are approximate due to RFC-mandated random 'fuzz' time of -1 to +1 sec): the current behavior would be to sent renew requests at: 10:00 13:45 and then rebind requests at: 17:30 18:45 then the lease would expire at 20:00 the correct/new behavior should be renew requests at: 10:00 13:45 15:37 16:37 and then rebind requests at: 17:30 18:45 19:45 and then lease expiration at 20:00. longer lease times would increase the number of retransmissions. [regression potential] any regression would likely result in problems receiving and/or maintaining a dhcpv4 address [scope] this is needed in b/f/g/h. this was fixed upstream in: https://github.com/systemd/systemd/pull/17908 that was just added, so this is not fixed in any ubuntu release yet. technically, this is needed in x as well, however I don't plan to backport to x since 1) it reaches ESM soon and 2) the default network management tool in x is ifupdown, not systemd-networkd. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1907306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
Thank you for all of your help! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908140 Title: Bond DHCP fails on Ubuntu Server 20.04 netplan Status in systemd package in Ubuntu: Incomplete Bug description: I recently installed Ubuntu Server 20.04 to replace an ESXi server. During the installation, I configured a bonded interface for two ethernet interfaces. I configured the bond on my ZyXel GS1900-8 as a static LAG. During the setup process, the link came up successfully and was leased an IP via DHCP. All subsequent boots have failed to acquire an IP address for the bonded interface. Sometimes, if I allow dhcp4 on the enslaved interfaces, and run sudo dhclient -r && sudo dhclient, the enslaved interfaces will be leased an IP address _and_ the bond will get an IP address. I know this is not proper as dhclient and systemd-networkd do not mix. Also, I would like to configure this as a LACP bond instead. I have enabled LACP on the switch with priority 65535 and "IP/MAC address" load balancing algorithm, switched the LAG from static to LACP, and altered netplan to use the 802.3ad bond mode. Please let me know what, if anything, I'm doing wrong here. I've looked around at as many netplan DHCP bond posts here as I could find to no avail. See below for configuration files and command outputs. I cannot give you the output of `lsb_release -rd` as the package is not installed and there's no connection to install it. $ cat /etc/netplan/00-bond.yaml network: version: 2 renderer: networkd ethernets: eth0: dhcp4: false eth1: dhcp4: false bonds: bond0: dhcp4: true interfaces: - eth0 - eth1 parameters: mode: 802.3ad $ sudo journalctl -b -u systemd-networkd Dec 14 08:06:47 lore systemd[1]: Starting Network Service... Dec 14 08:06:47 lore systemd-networkd[852]: bond0: netdev ready Dec 14 08:06:47 lore systemd-networkd[852]: Enumeration completed. Dec 14 08:06:47 lore systemd[1]: Started Network Service. Dec 14 08:06:47 lore systemd-networkd[852]: bond0: IPv6 successfully enabled Dec 14 08:06:47 lore systemd-networkd[852]: bond0: Link UP Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: docker0: Link UP $ sudo ip a lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred lft forever inet6 ::1/128 scope host valid_lft forever preferred lft forever eno1: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:46 brd ff:ff:ff:ff:ff:ff eno2: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:47 brd ff:ff:ff:ff:ff:ff eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a2 brd ff:ff:ff:ff:ff:ff eth1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a3 brd ff:ff:ff:ff:ff:ff bond0: mtu 1500 qdisk noqueue state DOWN group default qlen 1000 link/ether 52:8b:2c:cc:a0:15 brd ff:ff:ff:ff:ff:ff docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:26:1c:1b:39 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker 0 valid_lft forever preferred_lft forever $ cat /run/systemd/network/10-netplan-bond0.netdev [NetDev] Name=bond0 Kind=bond [Bond] Mode=802.3ad $ cat /run/systemd/network/10-netplan-bond0.network [Match] Name=bond0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 ConfigureWithoutCarrier=yes [DHCP] RouteMetric=100 UseMTU=true $ cat /run/systemd/network/10-netplan-eth0.network [Match] Name=eth0 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /run/systemd/network/10-netplan-eth1.network [Match] Name=eth1 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: down MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 802.3ad info LACP rate: slow Min links: 0 Aggregator selection policy
[Touch-packages] [Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
The BIOS update does indeed fix the type interface number issue. This ticket can be marked as a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578141 and closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908140 Title: Bond DHCP fails on Ubuntu Server 20.04 netplan Status in systemd package in Ubuntu: Incomplete Bug description: I recently installed Ubuntu Server 20.04 to replace an ESXi server. During the installation, I configured a bonded interface for two ethernet interfaces. I configured the bond on my ZyXel GS1900-8 as a static LAG. During the setup process, the link came up successfully and was leased an IP via DHCP. All subsequent boots have failed to acquire an IP address for the bonded interface. Sometimes, if I allow dhcp4 on the enslaved interfaces, and run sudo dhclient -r && sudo dhclient, the enslaved interfaces will be leased an IP address _and_ the bond will get an IP address. I know this is not proper as dhclient and systemd-networkd do not mix. Also, I would like to configure this as a LACP bond instead. I have enabled LACP on the switch with priority 65535 and "IP/MAC address" load balancing algorithm, switched the LAG from static to LACP, and altered netplan to use the 802.3ad bond mode. Please let me know what, if anything, I'm doing wrong here. I've looked around at as many netplan DHCP bond posts here as I could find to no avail. See below for configuration files and command outputs. I cannot give you the output of `lsb_release -rd` as the package is not installed and there's no connection to install it. $ cat /etc/netplan/00-bond.yaml network: version: 2 renderer: networkd ethernets: eth0: dhcp4: false eth1: dhcp4: false bonds: bond0: dhcp4: true interfaces: - eth0 - eth1 parameters: mode: 802.3ad $ sudo journalctl -b -u systemd-networkd Dec 14 08:06:47 lore systemd[1]: Starting Network Service... Dec 14 08:06:47 lore systemd-networkd[852]: bond0: netdev ready Dec 14 08:06:47 lore systemd-networkd[852]: Enumeration completed. Dec 14 08:06:47 lore systemd[1]: Started Network Service. Dec 14 08:06:47 lore systemd-networkd[852]: bond0: IPv6 successfully enabled Dec 14 08:06:47 lore systemd-networkd[852]: bond0: Link UP Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: docker0: Link UP $ sudo ip a lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred lft forever inet6 ::1/128 scope host valid_lft forever preferred lft forever eno1: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:46 brd ff:ff:ff:ff:ff:ff eno2: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:47 brd ff:ff:ff:ff:ff:ff eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a2 brd ff:ff:ff:ff:ff:ff eth1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a3 brd ff:ff:ff:ff:ff:ff bond0: mtu 1500 qdisk noqueue state DOWN group default qlen 1000 link/ether 52:8b:2c:cc:a0:15 brd ff:ff:ff:ff:ff:ff docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:26:1c:1b:39 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker 0 valid_lft forever preferred_lft forever $ cat /run/systemd/network/10-netplan-bond0.netdev [NetDev] Name=bond0 Kind=bond [Bond] Mode=802.3ad $ cat /run/systemd/network/10-netplan-bond0.network [Match] Name=bond0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 ConfigureWithoutCarrier=yes [DHCP] RouteMetric=100 UseMTU=true $ cat /run/systemd/network/10-netplan-eth0.network [Match] Name=eth0 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /run/systemd/network/10-netplan-eth1.network [Match] Name=eth1 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: down MII Polling Interval (ms): 100 Up
[Touch-packages] [Bug 1899262] Update Released
The verification of the Stable Release Update for wpa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Bionic: Fix Released Bug description: * Impact One of the distro patch is incorrect and create issues when trying to query dbus properties * Test Case $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1/Interfaces/1 org.freedesktop.DBus.Properties.GetAll string:fi.w1.wpa_supplicant1.Interface shouldn't error out (the /1 reflect the interface number and could be a different value, check with d-feet if needed) * Regression potential The fixes is in the dbus interface, check that communication with desktop clients (indicator, applet, settings) still works correctly, returning expected informations on the signal, etc - dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties
This bug was fixed in the package wpa - 2:2.6-15ubuntu2.6 --- wpa (2:2.6-15ubuntu2.6) bionic; urgency=medium * debian/patches/fix-dbus-getall-request.patch: - update to a fixed version of the patch to not error out when not in AP mode, thanks Michael Nazzareno Trimarchi (lp: #1899262) -- Sebastien Bacher Wed, 11 Nov 2020 10:50:58 +0100 ** Changed in: wpa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Bionic: Fix Released Bug description: * Impact One of the distro patch is incorrect and create issues when trying to query dbus properties * Test Case $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1/Interfaces/1 org.freedesktop.DBus.Properties.GetAll string:fi.w1.wpa_supplicant1.Interface shouldn't error out (the /1 reflect the interface number and could be a different value, check with d-feet if needed) * Regression potential The fixes is in the dbus interface, check that communication with desktop clients (indicator, applet, settings) still works correctly, returning expected informations on the signal, etc - dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908136] Re: no_proxy=::1 is not honored by curl in Bionic and earlier versions
Maybe it was just a coincidence, but those regressions disappeared immediately when reverting the ::1 addition: LP: #1907959 https://autopkgtest.ubuntu.com/packages/s/samtools/bionic/amd64 LP: #1907955 https://autopkgtest.ubuntu.com/packages/r/ruby2.5/bionic/amd64 Since you are around would you be so kind and address @laney's more than wone yeare old comments in the following MR so the cowboy deployed can be dropped and does not make extra work for @laney to land fixes? https://code.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/376587 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1908136 Title: no_proxy=::1 is not honored by curl in Bionic and earlier versions Status in Auto Package Testing: New Status in curl package in Ubuntu: Fix Released Status in curl source package in Xenial: New Status in curl source package in Bionic: New Status in curl source package in Focal: Fix Released Bug description: Bionic: env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Could not resolve proxy: foo * Closing connection 0 curl: (5) Could not resolve proxy: foo Focal: $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Uses proxy env variable no_proxy == '::1' * Trying ::1:80... * TCP_NODELAY set * Immediate connect fail for ::1: Network is unreachable * Closing connection 0 curl: (7) Couldn't connect to server To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
The audio simply disappeared, because the sound card, when the voltage was reduced, reset, causing the kernel to recognize it as card 0 or card 1, different from the settings. Then the sound was gone. After testing the input source, the voltage of 3.3 V and 5 V was below normal (around 3.28 V and 5.08 V) causing the card to not work properly. After repairing the power supply, the voltage of 3.3 V and 5 V is around 3.32 V and 5.13 V. On the outside, the power supply appears to be of good quality, but inside it has few output capacitors. ** Changed in: alsa-driver (Ubuntu) Status: New => Opinion ** Changed in: alsa-driver (Ubuntu) Status: Opinion => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size
[Touch-packages] [Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
There's a BIOS update available for my board. I'll install this and hopefully I won't need a SW fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908140 Title: Bond DHCP fails on Ubuntu Server 20.04 netplan Status in systemd package in Ubuntu: Incomplete Bug description: I recently installed Ubuntu Server 20.04 to replace an ESXi server. During the installation, I configured a bonded interface for two ethernet interfaces. I configured the bond on my ZyXel GS1900-8 as a static LAG. During the setup process, the link came up successfully and was leased an IP via DHCP. All subsequent boots have failed to acquire an IP address for the bonded interface. Sometimes, if I allow dhcp4 on the enslaved interfaces, and run sudo dhclient -r && sudo dhclient, the enslaved interfaces will be leased an IP address _and_ the bond will get an IP address. I know this is not proper as dhclient and systemd-networkd do not mix. Also, I would like to configure this as a LACP bond instead. I have enabled LACP on the switch with priority 65535 and "IP/MAC address" load balancing algorithm, switched the LAG from static to LACP, and altered netplan to use the 802.3ad bond mode. Please let me know what, if anything, I'm doing wrong here. I've looked around at as many netplan DHCP bond posts here as I could find to no avail. See below for configuration files and command outputs. I cannot give you the output of `lsb_release -rd` as the package is not installed and there's no connection to install it. $ cat /etc/netplan/00-bond.yaml network: version: 2 renderer: networkd ethernets: eth0: dhcp4: false eth1: dhcp4: false bonds: bond0: dhcp4: true interfaces: - eth0 - eth1 parameters: mode: 802.3ad $ sudo journalctl -b -u systemd-networkd Dec 14 08:06:47 lore systemd[1]: Starting Network Service... Dec 14 08:06:47 lore systemd-networkd[852]: bond0: netdev ready Dec 14 08:06:47 lore systemd-networkd[852]: Enumeration completed. Dec 14 08:06:47 lore systemd[1]: Started Network Service. Dec 14 08:06:47 lore systemd-networkd[852]: bond0: IPv6 successfully enabled Dec 14 08:06:47 lore systemd-networkd[852]: bond0: Link UP Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: docker0: Link UP $ sudo ip a lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred lft forever inet6 ::1/128 scope host valid_lft forever preferred lft forever eno1: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:46 brd ff:ff:ff:ff:ff:ff eno2: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:47 brd ff:ff:ff:ff:ff:ff eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a2 brd ff:ff:ff:ff:ff:ff eth1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a3 brd ff:ff:ff:ff:ff:ff bond0: mtu 1500 qdisk noqueue state DOWN group default qlen 1000 link/ether 52:8b:2c:cc:a0:15 brd ff:ff:ff:ff:ff:ff docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:26:1c:1b:39 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker 0 valid_lft forever preferred_lft forever $ cat /run/systemd/network/10-netplan-bond0.netdev [NetDev] Name=bond0 Kind=bond [Bond] Mode=802.3ad $ cat /run/systemd/network/10-netplan-bond0.network [Match] Name=bond0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 ConfigureWithoutCarrier=yes [DHCP] RouteMetric=100 UseMTU=true $ cat /run/systemd/network/10-netplan-eth0.network [Match] Name=eth0 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /run/systemd/network/10-netplan-eth1.network [Match] Name=eth1 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: down MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 802.3ad info
[Touch-packages] [Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
I thought this could be related to https://bugzilla.kernel.org/show_bug.cgi?id=199813. Indeed dmidecode -t 41 shows there are two interfaces for type interface 1 and two for 2. ** Bug watch added: Linux Kernel Bug Tracker #199813 https://bugzilla.kernel.org/show_bug.cgi?id=199813 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908140 Title: Bond DHCP fails on Ubuntu Server 20.04 netplan Status in systemd package in Ubuntu: Incomplete Bug description: I recently installed Ubuntu Server 20.04 to replace an ESXi server. During the installation, I configured a bonded interface for two ethernet interfaces. I configured the bond on my ZyXel GS1900-8 as a static LAG. During the setup process, the link came up successfully and was leased an IP via DHCP. All subsequent boots have failed to acquire an IP address for the bonded interface. Sometimes, if I allow dhcp4 on the enslaved interfaces, and run sudo dhclient -r && sudo dhclient, the enslaved interfaces will be leased an IP address _and_ the bond will get an IP address. I know this is not proper as dhclient and systemd-networkd do not mix. Also, I would like to configure this as a LACP bond instead. I have enabled LACP on the switch with priority 65535 and "IP/MAC address" load balancing algorithm, switched the LAG from static to LACP, and altered netplan to use the 802.3ad bond mode. Please let me know what, if anything, I'm doing wrong here. I've looked around at as many netplan DHCP bond posts here as I could find to no avail. See below for configuration files and command outputs. I cannot give you the output of `lsb_release -rd` as the package is not installed and there's no connection to install it. $ cat /etc/netplan/00-bond.yaml network: version: 2 renderer: networkd ethernets: eth0: dhcp4: false eth1: dhcp4: false bonds: bond0: dhcp4: true interfaces: - eth0 - eth1 parameters: mode: 802.3ad $ sudo journalctl -b -u systemd-networkd Dec 14 08:06:47 lore systemd[1]: Starting Network Service... Dec 14 08:06:47 lore systemd-networkd[852]: bond0: netdev ready Dec 14 08:06:47 lore systemd-networkd[852]: Enumeration completed. Dec 14 08:06:47 lore systemd[1]: Started Network Service. Dec 14 08:06:47 lore systemd-networkd[852]: bond0: IPv6 successfully enabled Dec 14 08:06:47 lore systemd-networkd[852]: bond0: Link UP Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: docker0: Link UP $ sudo ip a lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred lft forever inet6 ::1/128 scope host valid_lft forever preferred lft forever eno1: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:46 brd ff:ff:ff:ff:ff:ff eno2: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:47 brd ff:ff:ff:ff:ff:ff eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a2 brd ff:ff:ff:ff:ff:ff eth1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a3 brd ff:ff:ff:ff:ff:ff bond0: mtu 1500 qdisk noqueue state DOWN group default qlen 1000 link/ether 52:8b:2c:cc:a0:15 brd ff:ff:ff:ff:ff:ff docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:26:1c:1b:39 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker 0 valid_lft forever preferred_lft forever $ cat /run/systemd/network/10-netplan-bond0.netdev [NetDev] Name=bond0 Kind=bond [Bond] Mode=802.3ad $ cat /run/systemd/network/10-netplan-bond0.network [Match] Name=bond0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 ConfigureWithoutCarrier=yes [DHCP] RouteMetric=100 UseMTU=true $ cat /run/systemd/network/10-netplan-eth0.network [Match] Name=eth0 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /run/systemd/network/10-netplan-eth1.network [Match] Name=eth1 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link
[Touch-packages] [Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
> your bonded links are down; nothing will happen until they are brought
up.
Yes, I figured as such. I've already tried to bring up eth0, eth1, and
bond0 via ip, ifup, and ifconfig to no success.
> your pasted log appears incomplete since i see no output for eth0 or
eth1; please paste or attach your entire log.
This is the entire log since reboot. If I look at the journal from
previous boots, there are mentions of eth0 and eth1, as well as eno1 and
eno2.
$ networkctl list
IDX LINKTYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eno1etheroff unmanaged
3 eno2etheroff unmanaged
4 eth0etheroff pending
5 eth1etheroff pending
6 bond0 bond no-carrier configured
7 docker0 bridge no-carrier unmanaged
After doing ip link set dev {eth0,eth1} up, they change from off to
degraded in networkctl list. Attempting the same on bond0 afterward does
nothing.
$ networkctl status -n 40
* State: no carrier
Address: 172.17.0.1 on docker0
Dec 14 21:29:44 lore systemd[1]: Starting Network Service...
Dec 14 21:29:44 lore systemd-networkd[852]: bond0: netdev ready
Dec 14 21:29:44 lore systemd-networkd[852]: Enumeration completed.
Dec 14 21:29:44 lore systemd[1]: Started Network Service.
Dec 14 21:29:44 lore systemd-networkd[852]: bond0: IPv6 successfully enabled
Dec 14 21:29:44 lore systemd-networkd[852]: bond0: Link UP
Dec 14 21:31:44 lore systemd[1]: systemd-networkd-wait-online.service: Main
process exited, code=exited, status=1/FAILURE
Dec 14 21:31:44 lore systemd[1]: systemd-networkd-wait-online.service: Failed
with result 'exit-code'.
Dec 14 21:31:44 lore systemd[1]: Failed to start Wait for Network to be
Configured.
Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link
'7' we don't know about, ignoring.
Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link
'7' we don't know about, ignoring.
Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link
'7' we don't know about, ignoring.
Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link
'7' we don't know about, ignoring.
Dec 14 21:31:50 lore systemd-networkd[852]: docker0: Link UP
Dec 15 18:13:43 lore systemd-networkd[856]: eth1: Link IP
Dec 15 18:13:45 lore systemd-networkd[856]: eth0: Ganied carrier
Dec 15 18:13:47 lore systemd-networkd[856]: eth0: Gained IPv6LL
Dec 15 18:13:47 lore systemd-networkd[856]: eth1: Ganied carrier
Dec 15 18:13:48 lore systemd-networkd[856]: eth1: Gained IPv6LL
Dec 15 18:15:13 lore systemd-networkd[856]: bond0: Link DOWN
Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Link DOWN
Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Lost carrier
Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Link DOWN
Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Lost carrer
All of the lines from today (Dec 15) correspond to my attempts to bring
interfaces up as mentioned above, then bringing them back down after it
failed.
> networkctl status bond0 eth0 eth1
* 4: eth0
Link File: n/a
Network File: n/a
Status: off (pending)
HW Address: 0c:c4:7a:c6:c6:a2 (Super Micro Computer, Inc.)
MTU: 1500 (min: 68, max: 9710)
Queue Length (Tx/Rx): 64/64
Auto negotiaition: yes
Speed: n/a
Port: tp
Dec 14 21:29:42 lore systemd-udevd[588]: eth0: Failed to rename network
interface 4 from 'eth0' to 'eno1': File exists
Dec 14 21:29:42 lore systemd-udevd[588]: eth0: Failed to process device,
ignoring: File exists
Dec 15 18:13:45 lore systemd-networkd[856]: eth0: Ganied carrier
Dec 15 18:13:47 lore systemd-networkd[856]: eth0: Gained IPv6LL
Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Link DOWN
Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Lost carrier
* 5: eth1
Link File: n/a
Network File: n/a
Status: off (pending)
HW Address: 0c:c4:7a:c6:c6:a2 (Super Micro Computer, Inc.)
MTU: 1500 (min: 68, max: 9710)
Queue Length (Tx/Rx): 64/64
Auto negotiaition: yes
Speed: n/a
Port: tp
Dec 14 21:29:42 lore systemd-udevd[588]: eth1: Failed to rename network
interface 5 from 'eth1' to 'eno2': File exists
Dec 14 21:29:42 lore systemd-udevd[588]: eth1: Failed to process device,
ignoring: File exists
Dec 15 18:13:43 lore systemd-networkd[856]: eth1: Link IP
Dec 15 18:13:47 lore systemd-networkd[856]: eth1: Ganied carrier
Dec 15 18:13:48 lore systemd-networkd[856]: eth1: Gained IPv6LL
Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Link DOWN
Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Lost carrer
* 6: bond0
Link File: /usr/lib/systemd/network/99-default.link
Network File: /run/systemd/network/10-netplan-bond0.network
Type: bond
State: off (configured)
Driver: bonding
[Touch-packages] [Bug 1901789] Re: Release upgrade 20.04 -> 20.10 removed input method from ibus
This bug was fixed in the package ibus - 1.5.23-2 --- ibus (1.5.23-2) unstable; urgency=medium * Team upload * debian/patches/Warn-deprecated-IBus-XKB-engines-w-dialog.patch: - Show a warning dialog when a deprecated engine name from ibus < 1.5.23 is configured (LP: #1901789). * Bump Standards-Version to 4.5.1 -- Gunnar Hjalmarsson Mon, 14 Dec 2020 13:09:45 +0100 ** Changed in: ibus (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1901789 Title: Release upgrade 20.04 -> 20.10 removed input method from ibus Status in ibus: New Status in ibus package in Ubuntu: Fix Released Bug description: What happened: === I'm using iBus as input "method" with - Japanese (Anthy) // primary - German set up. I upgraded from ubuntu 20.04 to 20.10. EXPECTED: No changes regarding input. ACTUAL: German input method was removed lsb_release -rd === Description: Ubuntu 20.10 Release: 20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.12 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Oct 28 11:10:04 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to groovy on 2020-10-24 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1901789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted
This bug was fixed in the package coreutils - 8.32-4ubuntu2 --- coreutils (8.32-4ubuntu2) hirsute; urgency=medium * d/p/treat-devtmpfs-and-squashfs-as-dummy-filesystems.patch: - Extend default filesystem exlusion to fuse.portal (LP: #1905623) -- Julian Andres Klode Sat, 05 Dec 2020 21:55:44 +0100 ** Changed in: coreutils (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in coreutils package in Ubuntu: Fix Released Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797002] Re: Bluetooth audio skips while the settings dialog is open
Hello, Thank you for looking at this issue. If source code propagate downstream, then I think it would be a good idea to come up with a system that propagates bug reports upstream. If that effort is underway I will consider registering on arbitrary other bug trackers in the meantime as a stopgap solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: Bluetooth audio skips while the settings dialog is open Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908136] Re: no_proxy=::1 is not honored by curl in Bionic and earlier versions
While there is a curl bug here that older versions do not honor ipv6 addresses in no_proxy, there's no information here that explains why you think this caused a *regression* in autopkgtests. Tests attempting to use the http proxy to connect to ::1 will fail with or without adding ::1 to no_proxy. So how does having it listed in no_proxy cause a regression? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1908136 Title: no_proxy=::1 is not honored by curl in Bionic and earlier versions Status in Auto Package Testing: New Status in curl package in Ubuntu: Fix Released Status in curl source package in Xenial: New Status in curl source package in Bionic: New Status in curl source package in Focal: Fix Released Bug description: Bionic: env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Could not resolve proxy: foo * Closing connection 0 curl: (5) Could not resolve proxy: foo Focal: $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Uses proxy env variable no_proxy == '::1' * Trying ::1:80... * TCP_NODELAY set * Immediate connect fail for ::1: Network is unreachable * Closing connection 0 curl: (7) Couldn't connect to server To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908273] Re: Software stopped working
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908273 Title: Software stopped working Status in xorg package in Ubuntu: New Bug description: After update to Ubuntu 20.04.1 LTS some of my software stopped working, all of it is visualization software: VMD, Discovery Studio, PyMOL, Gmolden, Avogadro. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 14:41:52 2020 DistUpgraded: 2020-11-21 20:16:19,197 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Wykonanie procesu potomnego „./xorg_fix_proprietary.py” (Nie ma takiego pliku ani katalogu) się nie powiodło (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8537] InstallationDate: Installed on 2020-05-20 (208 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 0408:5373 Quanta Computer, Inc. HP HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-21 (23 days ago) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8537 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD0097RK4 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 440 G6 dmi.product.sku: 5PQ09EA#AKD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1908273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908273] [NEW] Software stopped working
You have been subscribed to a public bug: After update to Ubuntu 20.04.1 LTS some of my software stopped working, all of it is visualization software: VMD, Discovery Studio, PyMOL, Gmolden, Avogadro. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 14:41:52 2020 DistUpgraded: 2020-11-21 20:16:19,197 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Wykonanie procesu potomnego „./xorg_fix_proprietary.py” (Nie ma takiego pliku ani katalogu) się nie powiodło (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8537] InstallationDate: Installed on 2020-05-20 (208 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 0408:5373 Quanta Computer, Inc. HP HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-21 (23 days ago) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8537 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD0097RK4 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 440 G6 dmi.product.sku: 5PQ09EA#AKD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Software stopped working https://bugs.launchpad.net/bugs/1908273 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
> please paste or attach your entire log if that *is* your entire log, then please include the output of: $ networkctl list $ networkctl status $ networkctl status bond0 eth0 eth1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908140 Title: Bond DHCP fails on Ubuntu Server 20.04 netplan Status in systemd package in Ubuntu: Incomplete Bug description: I recently installed Ubuntu Server 20.04 to replace an ESXi server. During the installation, I configured a bonded interface for two ethernet interfaces. I configured the bond on my ZyXel GS1900-8 as a static LAG. During the setup process, the link came up successfully and was leased an IP via DHCP. All subsequent boots have failed to acquire an IP address for the bonded interface. Sometimes, if I allow dhcp4 on the enslaved interfaces, and run sudo dhclient -r && sudo dhclient, the enslaved interfaces will be leased an IP address _and_ the bond will get an IP address. I know this is not proper as dhclient and systemd-networkd do not mix. Also, I would like to configure this as a LACP bond instead. I have enabled LACP on the switch with priority 65535 and "IP/MAC address" load balancing algorithm, switched the LAG from static to LACP, and altered netplan to use the 802.3ad bond mode. Please let me know what, if anything, I'm doing wrong here. I've looked around at as many netplan DHCP bond posts here as I could find to no avail. See below for configuration files and command outputs. I cannot give you the output of `lsb_release -rd` as the package is not installed and there's no connection to install it. $ cat /etc/netplan/00-bond.yaml network: version: 2 renderer: networkd ethernets: eth0: dhcp4: false eth1: dhcp4: false bonds: bond0: dhcp4: true interfaces: - eth0 - eth1 parameters: mode: 802.3ad $ sudo journalctl -b -u systemd-networkd Dec 14 08:06:47 lore systemd[1]: Starting Network Service... Dec 14 08:06:47 lore systemd-networkd[852]: bond0: netdev ready Dec 14 08:06:47 lore systemd-networkd[852]: Enumeration completed. Dec 14 08:06:47 lore systemd[1]: Started Network Service. Dec 14 08:06:47 lore systemd-networkd[852]: bond0: IPv6 successfully enabled Dec 14 08:06:47 lore systemd-networkd[852]: bond0: Link UP Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: docker0: Link UP $ sudo ip a lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred lft forever inet6 ::1/128 scope host valid_lft forever preferred lft forever eno1: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:46 brd ff:ff:ff:ff:ff:ff eno2: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:47 brd ff:ff:ff:ff:ff:ff eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a2 brd ff:ff:ff:ff:ff:ff eth1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a3 brd ff:ff:ff:ff:ff:ff bond0: mtu 1500 qdisk noqueue state DOWN group default qlen 1000 link/ether 52:8b:2c:cc:a0:15 brd ff:ff:ff:ff:ff:ff docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:26:1c:1b:39 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker 0 valid_lft forever preferred_lft forever $ cat /run/systemd/network/10-netplan-bond0.netdev [NetDev] Name=bond0 Kind=bond [Bond] Mode=802.3ad $ cat /run/systemd/network/10-netplan-bond0.network [Match] Name=bond0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 ConfigureWithoutCarrier=yes [DHCP] RouteMetric=100 UseMTU=true $ cat /run/systemd/network/10-netplan-eth0.network [Match] Name=eth0 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /run/systemd/network/10-netplan-eth1.network [Match] Name=eth1 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: down MII Polling Interval (ms): 100 Up
[Touch-packages] [Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
> eth0: mtu 1500 qdisc noop state DOWN group default qlen > 1000 > eth1: mtu 1500 qdisc noop state DOWN group default qlen > 1000 your bonded links are down; nothing will happen until they are brought up. > $ sudo journalctl -b -u systemd-networkd ... your pasted log appears incomplete since i see no output for eth0 or eth1; please paste or attach your entire log. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908140 Title: Bond DHCP fails on Ubuntu Server 20.04 netplan Status in systemd package in Ubuntu: Incomplete Bug description: I recently installed Ubuntu Server 20.04 to replace an ESXi server. During the installation, I configured a bonded interface for two ethernet interfaces. I configured the bond on my ZyXel GS1900-8 as a static LAG. During the setup process, the link came up successfully and was leased an IP via DHCP. All subsequent boots have failed to acquire an IP address for the bonded interface. Sometimes, if I allow dhcp4 on the enslaved interfaces, and run sudo dhclient -r && sudo dhclient, the enslaved interfaces will be leased an IP address _and_ the bond will get an IP address. I know this is not proper as dhclient and systemd-networkd do not mix. Also, I would like to configure this as a LACP bond instead. I have enabled LACP on the switch with priority 65535 and "IP/MAC address" load balancing algorithm, switched the LAG from static to LACP, and altered netplan to use the 802.3ad bond mode. Please let me know what, if anything, I'm doing wrong here. I've looked around at as many netplan DHCP bond posts here as I could find to no avail. See below for configuration files and command outputs. I cannot give you the output of `lsb_release -rd` as the package is not installed and there's no connection to install it. $ cat /etc/netplan/00-bond.yaml network: version: 2 renderer: networkd ethernets: eth0: dhcp4: false eth1: dhcp4: false bonds: bond0: dhcp4: true interfaces: - eth0 - eth1 parameters: mode: 802.3ad $ sudo journalctl -b -u systemd-networkd Dec 14 08:06:47 lore systemd[1]: Starting Network Service... Dec 14 08:06:47 lore systemd-networkd[852]: bond0: netdev ready Dec 14 08:06:47 lore systemd-networkd[852]: Enumeration completed. Dec 14 08:06:47 lore systemd[1]: Started Network Service. Dec 14 08:06:47 lore systemd-networkd[852]: bond0: IPv6 successfully enabled Dec 14 08:06:47 lore systemd-networkd[852]: bond0: Link UP Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: docker0: Link UP $ sudo ip a lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred lft forever inet6 ::1/128 scope host valid_lft forever preferred lft forever eno1: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:46 brd ff:ff:ff:ff:ff:ff eno2: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:47 brd ff:ff:ff:ff:ff:ff eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a2 brd ff:ff:ff:ff:ff:ff eth1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a3 brd ff:ff:ff:ff:ff:ff bond0: mtu 1500 qdisk noqueue state DOWN group default qlen 1000 link/ether 52:8b:2c:cc:a0:15 brd ff:ff:ff:ff:ff:ff docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:26:1c:1b:39 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker 0 valid_lft forever preferred_lft forever $ cat /run/systemd/network/10-netplan-bond0.netdev [NetDev] Name=bond0 Kind=bond [Bond] Mode=802.3ad $ cat /run/systemd/network/10-netplan-bond0.network [Match] Name=bond0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 ConfigureWithoutCarrier=yes [DHCP] RouteMetric=100 UseMTU=true $ cat /run/systemd/network/10-netplan-eth0.network [Match] Name=eth0 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /run/systemd/network/10-netplan-eth1.network [Match] Name=eth1 [Network]
[Touch-packages] [Bug 1885755] Re: test-cap-list fails with Linux 5.8 due to new capabilities
*** This bug is a duplicate of bug 1905044 *** https://bugs.launchpad.net/bugs/1905044 > Can we also push the fix to Xenial not needed in x ** This bug has been marked a duplicate of bug 1905044 systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1885755 Title: test-cap-list fails with Linux 5.8 due to new capabilities Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: == test-cap-list === Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at src/test/test-cap-list.c:60, function test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) This seems to be a result of new capabilities added in 5.8. systemd builds an array to convert capability numbers to strings, and these new capabilities are not in its array, so the test bombs out when trying to look up the string for a capability it doesn't know about. Rebuilding systemd using headers from Linux 5.8 should fix this issue. Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200630_155538_0c63d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200630_162720_b3e1b@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200630_140417_c5bdb@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903222] Re: Systemd throws error with unknown capabilities
*** This bug is a duplicate of bug 1905044 *** https://bugs.launchpad.net/bugs/1905044 ** This bug is no longer a duplicate of bug 1885755 test-cap-list fails with Linux 5.8 due to new capabilities ** This bug has been marked a duplicate of bug 1905044 systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1903222 Title: Systemd throws error with unknown capabilities Status in HWE Next: New Status in systemd package in Ubuntu: New Bug description: The Kernel v5.8 introduces a new capability (CAP_BPF), which is not supported by Systemd v237 as shipped in bionic. Systemd added a patch to handle unknown capabilities that makes it so it does not error with Kernels with new capabilities: https://github.com/systemd/systemd/pull/16420 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1903222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905245] Re: "Failed to parse bus message: Invalid argument" with Linux 5.8
** Description changed: [impact] newer kernels introduced a new capability, and existing systemd doesn't have the name mapping for the new cap (since the mapping table is generated at systemd compile time), so it fails when trying to map the capability to a user-facing name, which causes failure when running commands like 'systemctl show' [test case] install a focal system, and install the 5.8 (or newer) kernel, e.g. from linux-generic-hwe-20.04-edge, and reboot into the new kernel. Find any service that does not specify its CapabilityBoundingSet; e.g. 'apparmor', and run systemctl show on it: ubuntu@lp1905245-f:~$ systemctl show -p CapabilityBoundingSet apparmor Failed to parse bus message: Invalid argument the command should correctly show the value, e.g.: $ systemctl show -p CapabilityBoundingSet apparmor CapabilityBoundingSet=cap_chown cap_dac_override ...etc... [regression potential] a regression would likely occur while systemd is parsing or printing or otherwise handling kernel capabilities. A regression could happen when running systemd commands, such as systemctl, or when pid1 is managing services. [scope] - this is needed only in focal (and possibly bionic). + this is needed only in b and f. This is fixed upstream by PR 16424: https://github.com/systemd/systemd/pull/16424 which was first included in v246, so this is already fixed in groovy and later. - this was introduced externally from systemd, with the new capability in the kernel, so this fix technically is needed in x/b/f. However, x is unlikely to get a new kernel capability during the rest of its life cycle. - For b, unless a kernel is added that includes a new capability, this patch is not needed. + Though b is unlikely to have the 5.8 kernel backported directly during + its remaining lifetime, this bug is reproducable when running a b + container on a host system with the 5.8 kernel, so this is needed for b. + + This bug was introduced upstream with commit + dd1f5bd0aa584c5e5e10fddc735155c3501eb21e which was first included in + v235, so this bug does not exist in x. [original description] When I run `systemctl show myservice.service`, I get the following error message: Failed to parse bus message: Invalid argument systemd version: 245.4-4ubuntu3.3 linux version: 5.8.0-29-generic #31~20.04.1-Ubuntu (From linux-generic-hwe-20.04-edge) This is a bug that has been fixed in Debian. See https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=964926 Please can we port the fix to the ubuntu 20.04 version. ** Description changed: [impact] newer kernels introduced a new capability, and existing systemd doesn't have the name mapping for the new cap (since the mapping table is generated at systemd compile time), so it fails when trying to map the capability to a user-facing name, which causes failure when running commands like 'systemctl show' [test case] install a focal system, and install the 5.8 (or newer) kernel, e.g. from linux-generic-hwe-20.04-edge, and reboot into the new kernel. Find any service that does not specify its CapabilityBoundingSet; e.g. 'apparmor', and run systemctl show on it: ubuntu@lp1905245-f:~$ systemctl show -p CapabilityBoundingSet apparmor Failed to parse bus message: Invalid argument the command should correctly show the value, e.g.: $ systemctl show -p CapabilityBoundingSet apparmor CapabilityBoundingSet=cap_chown cap_dac_override ...etc... [regression potential] a regression would likely occur while systemd is parsing or printing or otherwise handling kernel capabilities. A regression could happen when running systemd commands, such as systemctl, or when pid1 is managing services. [scope] - this is needed only in b and f. + this is needed only in focal (and possibly bionic). This is fixed upstream by PR 16424: https://github.com/systemd/systemd/pull/16424 which was first included in v246, so this is already fixed in groovy and later. - Though b is unlikely to have the 5.8 kernel backported directly during - its remaining lifetime, this bug is reproducable when running a b - container on a host system with the 5.8 kernel, so this is needed for b. + this was introduced externally from systemd, with the new capability in the kernel, so this fix technically is needed in x/b/f. However, x is unlikely to get a new kernel capability during the rest of its life cycle. + For b, unless a kernel is added that includes a new capability, this patch is not needed. - This bug was introduced upstream with commit - dd1f5bd0aa584c5e5e10fddc735155c3501eb21e which was first included in - v235, so this bug does not exist in x. + [other info] + + there is a testcase-only related bug 1905044 [original description] When I run `systemctl show myservice.service`, I get the following error message:
[Touch-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Bionic: Fix Committed Bug description: * Impact One of the distro patch is incorrect and create issues when trying to query dbus properties * Test Case $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1/Interfaces/1 org.freedesktop.DBus.Properties.GetAll string:fi.w1.wpa_supplicant1.Interface shouldn't error out (the /1 reflect the interface number and could be a different value, check with d-feet if needed) * Regression potential The fixes is in the dbus interface, check that communication with desktop clients (indicator, applet, settings) still works correctly, returning expected informations on the signal, etc - dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
** Changed in: systemd (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1905044 Title: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: Fix Committed Bug description: [impact] autopkgtest failure when running with 5.8 kernel, if systemd is built with earlier kernel (e.g. 5.4) [test case] see autopkgtest results, e.g. links in original description below [regression potential] as this only fixes a test case, any regression would likely result in an incorrectly passing, or incorrectly failing, test. [scope] this is needed for b/f/g/h. this bug was introduced by upstream commit 23cc81e7c22 which first added testing for 'invalid' cap numbers, but incorrectly using capability_list_length() instead of cap_last_cap(). That commit was first included in v236, so this bug does not exist before Bionic. this is fixed upstream by commit ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in v247, so this is needed for h and earlier. Also note that even though the 5.8 kernel is not planned to be released for Bionic, this test also runs at build time, and since the LP build farm builds inside chroots, if the build farm ever moved up to Focal with a 5.8 kernel, the build of systemd for Bionic would start failing (since it would still be building using the older kernel headers, inside the chroot), so this does need to be fixed in Bionic systemd as well. [other info] there is a non-test bug related to this in bug 1905245 [original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz The failing testcases are: - root-unittests Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) - upstream TEST-24-UNIT-TESTS: --- test-cap-list begin --- Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. --- test-cap-list end --- Both seem to be failing with the same assertion. These tests are successful on Focal with linux 5.4, therefore they would regress when upgrading the kernel from 5.4 to 5.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800836] Re: systemd-networkd doesn't process IPv6 RA properly
possibly needs upstream commit https://github.com/systemd/systemd/commit/f02ba163891bab73a80332b4599a9d73083cb6c2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1800836 Title: systemd-networkd doesn't process IPv6 RA properly Status in systemd package in Ubuntu: Confirmed Bug description: The gateways/firewalls in our DC are highly available and when there is a failover their IPv6 VIP (fe80::1) moves from the master to the backup one. We found that only our Bionic VMs behind those gateways had issues after a failover. Those Bionic VMs were all running systemd-networkd (from netplan) and before the failover they had: $ ip -6 route ... default via fe80::1 dev eth0 proto ra metric 1024 pref medium But after a failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 And after another failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 nexthop via fe80::210:18ff:fe77:b558 dev eth0 weight 1 This is problematic as those then use fe80::210:18ff:fe77:b558%$IFACE as their default gateway even when this gateway is unavailable: $ ip -6 route get :: :: from :: via fe80::210:18ff:fe77:b558 dev eth0 proto ra src fe80::a800:ff:fe51:8c37 metric 1024 pref medium We concluded it was a systemd-networkd bug after checking that the following combinations were NOT affected: 1) Xenial+4.4 kernel 2) Xenial+4.15 kernel 3) Bionic+ifupdown Additional information: $ apt-cache policy systemd systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 31 08:47:28 2018 Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=43b7ee2e-2ab1-4505-8e0b-d9fe0563a034 ro console=ttyS0 net.ifnames=0 vsyscall=none kaslr nmi_watchdog=0 possible_cpus=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
@rbalint, fyi since this is a testcase-only fix, I just pushed to the hirsute repo, assuming you wouldn't mind. https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d55c6f8186cb2cb73f61d6ff5b2e0ded82ef265c ** Description changed: [impact] - autopkgtest failure when running with 5.8 kernel + autopkgtest failure when running with 5.8 kernel, if systemd is built + with earlier kernel (e.g. 5.4) [test case] see autopkgtest results, e.g. links in original description below [regression potential] as this only fixes a test case, any regression would likely result in an incorrectly passing, or incorrectly failing, test. [scope] this is needed for b/f/g/h. this bug was introduced by upstream commit 23cc81e7c22 which first added testing for 'invalid' cap numbers, but incorrectly using capability_list_length() instead of cap_last_cap(). That commit was first included in v236, so this bug does not existing before Bionic. this is fixed upstream by commit ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in v247, so this is needed for h and earlier. Also note that even though the 5.8 kernel is not planned to be released for Bionic, this test also runs at build time, and since the LP build farm builds inside chroots, if the build farm ever moved up to Focal with a 5.8 kernel, the build of systemd for Bionic would start failing, so this does need to be fixed in Bionic systemd as well. [other info] there is a non-test bug related to this in bug 1905245 [original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz The failing testcases are: - root-unittests Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) - upstream TEST-24-UNIT-TESTS: --- test-cap-list begin --- Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. --- test-cap-list end --- Both seem to be failing with the same assertion. These tests are successful on Focal with linux 5.4, therefore they would regress when upgrading the kernel from 5.4 to 5.8. ** Description changed: [impact] autopkgtest failure when running with 5.8 kernel, if systemd is built with earlier kernel (e.g. 5.4) [test case] see autopkgtest results, e.g. links in original description below [regression potential] as this only fixes a test case, any regression would likely result in an incorrectly passing, or incorrectly failing, test. [scope] this is needed for b/f/g/h. this bug was introduced by upstream commit 23cc81e7c22 which first added testing for 'invalid' cap numbers, but incorrectly using capability_list_length() instead of cap_last_cap(). That commit was - first included in v236, so this bug does not existing before Bionic. + first included in v236, so this bug does not exist before Bionic. this is fixed upstream by commit ebc815cd1c647faa934a446ceea91ff4bc9dffa4, which was first included in v247, so this is needed for h and earlier. Also note that even though the 5.8 kernel is not planned to be released for Bionic, this test also runs at build time, and since the LP build farm builds inside chroots, if the build farm ever moved up to Focal with a 5.8 kernel, the build of systemd for Bionic would start failing, so this does need to be fixed in Bionic systemd as well. [other info] there is a non-test bug related to this in bug 1905245 [original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x:
[Touch-packages] [Bug 1907886] Re: avinfo is missing
Thanks, upstream doesn't install that utility and they seem to consider it experimentl, fedora is including it in their binary though, we could probably do the same for Ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1907886 Title: avinfo is missing Status in bluez package in Ubuntu: Triaged Bug description: The "avinfo" command line tools available in bluez/tools (https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools) is not available in the package. The package bluez-tools (https://packages.ubuntu.com/groovy/bluez- tools) seems to map another project external to bluez (https://github.com/khvzak/bluez-tools) and not the "tools" folder of bluez. "avinfo" is used for example in order to check which codecs are supported by a headphone set (see https://github.com/EHfive /pulseaudio-modules-bt/issues/31#issuecomment-462717049). Maybe have "bluez-tools" map the "tools" folder of bluez, and move the other project to another package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1907886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908239] Re: package libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is dif
rm -rf /usr/share/doc/libjpeg-turbo8/changelog.Debian.gz then apt --fix-broken install i had succes with that ** Changed in: libjpeg-turbo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1908239 Title: package libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg- turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:i386 Status in libjpeg-turbo package in Ubuntu: Confirmed Bug description: I WILL INSTALL WINE, BUT ERROR Errors were encountered while processing: /var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 15 16:25:00 2020 ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:i386 InstallationDate: Installed on 2020-09-23 (82 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1908239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
** Changed in: pulseaudio (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: pulseaudio (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Committed Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
** Changed in: pulseaudio (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Committed Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1907882] Re: paprefs does not find modules
The issue is a paprefs one though and reported upstream
https://gitlab.freedesktop.org/pulseaudio/paprefs/-/issues/7
** Bug watch added: gitlab.freedesktop.org/pulseaudio/paprefs/-/issues #7
https://gitlab.freedesktop.org/pulseaudio/paprefs/-/issues/7
** Package changed: pulseaudio (Ubuntu) => paprefs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1907882
Title:
paprefs does not find modules
Status in paprefs package in Ubuntu:
Fix Released
Bug description:
on ubuntu 20.10 paprefs does not find modules, as it uses a hardcoded path.
workaround:
cd /usr/lib
sudo ln -s pulse-13.99.2 pulse-13.99
see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531251
strace paprefs 2>&1 |grep /lib/pulse
access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) =
-1 ENOENT (No such file or directory)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/paprefs/+bug/1907882/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908265] [NEW] bad heating
Public bug reported: i had dell pre-installed ubuntu, but i had erase it. now i am facing heating issues ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 17:59:23 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08c8] InstallationDate: Installed on 2020-12-11 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Bus 001 Device 002: ID 27c6:5301 Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-124-generic root=UUID=4f0e25d7-2cd2-474f-9088-9df1ffccd1ce ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0H40C6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:svnDellInc.:pnVostro3480:pvr:rvnDellInc.:rn0H40C6:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3480 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908265 Title: bad heating Status in xorg package in Ubuntu: New Bug description: i had dell pre-installed ubuntu, but i had erase it. now i am facing heating issues ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 17:59:23 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08c8] InstallationDate: Installed on 2020-12-11 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Bus 001 Device 002: ID 27c6:5301 Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-124-generic root=UUID=4f0e25d7-2cd2-474f-9088-9df1ffccd1ce ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0H40C6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:svnDellInc.:pnVostro3480:pvr:rvnDellInc.:rn0H40C6:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3480 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8
[Touch-packages] [Bug 1907882] Re: paprefs does not find modules
Thank you for your bug report. Indeed that's buggy in focal as well.
That has been fixed in the stable version in hirsute now
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Low
** Changed in: pulseaudio (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1907882
Title:
paprefs does not find modules
Status in pulseaudio package in Ubuntu:
Fix Released
Bug description:
on ubuntu 20.10 paprefs does not find modules, as it uses a hardcoded path.
workaround:
cd /usr/lib
sudo ln -s pulse-13.99.2 pulse-13.99
see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531251
strace paprefs 2>&1 |grep /lib/pulse
access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) =
-1 ENOENT (No such file or directory)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1907882/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908136] Re: no_proxy=::1 is not honored by curl in Bionic and earlier versions
** Tags added: rls-bb-incoming rls-x-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1908136 Title: no_proxy=::1 is not honored by curl in Bionic and earlier versions Status in Auto Package Testing: New Status in curl package in Ubuntu: Fix Released Status in curl source package in Xenial: New Status in curl source package in Bionic: New Status in curl source package in Focal: Fix Released Bug description: Bionic: env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Could not resolve proxy: foo * Closing connection 0 curl: (5) Could not resolve proxy: foo Focal: $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Uses proxy env variable no_proxy == '::1' * Trying ::1:80... * TCP_NODELAY set * Immediate connect fail for ::1: Network is unreachable * Closing connection 0 curl: (7) Couldn't connect to server To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908259] Re: TEST-36-NUMAPOLICY fails with qemu 5.2
Tests are somewhat blocked by PPA being under maintenance. But I have filed the issue upstream for discussion and to trigger their CI. Issue => https://github.com/systemd/systemd/issues/17986 PR => https://github.com/systemd/systemd/pull/17987 ** Bug watch added: github.com/systemd/systemd/issues #17986 https://github.com/systemd/systemd/issues/17986 ** Also affects: systemd via https://github.com/systemd/systemd/issues/17986 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908259 Title: TEST-36-NUMAPOLICY fails with qemu 5.2 Status in systemd: Unknown Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Hi, this test now fails as seen on ppc here https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/s/systemd/20201214_224336_8b0d8@/log.gz + /bin/qemu-system-ppc64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinux-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.qFc3xq/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=hvc0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' E: QEMU failed with exit code 1 qemu-system-ppc64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) Reproducible in LP infra with systemd 246.6-5ubuntu1 and qemu 5.2 On other architectures this test is just skipped and ppc happened to complete faster so I saw it earlier. The same happens on amd64 + /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.8Hqpmk/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) E: QEMU failed with exit code 1 Isolated this to a test without systemd: $ apt install linux-image-generic qemu-system-x86 $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' Upgrading to 5.2 makes this: $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) The numa spec is indeed a bit short -numa node,nodeid=0 If I change this to -numa node,mem=512M,nodeid=0 It would work, but that kind of specification is forbidden >=5.1 Parameter -numa node,mem is not supported by this machine type Use -numa node,memdev instead You'd need also something like -M pc-i440fx-5.0 which isn't anything the test wants to set in stone I guess. Instead using memdev works: -object memory-backend-ram,id=mem0,size=512M -numa node,memdev=mem0,nodeid=0 This works fine and is in qemu since quite some time. Properly documented since 2.12 but actually available since 2.1 (2014) The argument for this test is in test/TEST-36-NUMAPOLICY/test.sh QEMU_OPTIONS="-numa node,nodeid=0" Fixing that to a new form should help. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1908259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908259] Re: TEST-36-NUMAPOLICY fails with qemu 5.2
Added qemu task for update-excuse tag to be resolved. I have a fix prepared that is building/testing right now. If successful I'll open an upstream issue for it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908259 Title: TEST-36-NUMAPOLICY fails with qemu 5.2 Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Hi, this test now fails as seen on ppc here https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/s/systemd/20201214_224336_8b0d8@/log.gz + /bin/qemu-system-ppc64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinux-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.qFc3xq/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=hvc0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' E: QEMU failed with exit code 1 qemu-system-ppc64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) Reproducible in LP infra with systemd 246.6-5ubuntu1 and qemu 5.2 On other architectures this test is just skipped and ppc happened to complete faster so I saw it earlier. The same happens on amd64 + /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.8Hqpmk/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) E: QEMU failed with exit code 1 Isolated this to a test without systemd: $ apt install linux-image-generic qemu-system-x86 $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' Upgrading to 5.2 makes this: $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) The numa spec is indeed a bit short -numa node,nodeid=0 If I change this to -numa node,mem=512M,nodeid=0 It would work, but that kind of specification is forbidden >=5.1 Parameter -numa node,mem is not supported by this machine type Use -numa node,memdev instead You'd need also something like -M pc-i440fx-5.0 which isn't anything the test wants to set in stone I guess. Instead using memdev works: -object memory-backend-ram,id=mem0,size=512M -numa node,memdev=mem0,nodeid=0 This works fine and is in qemu since quite some time. Properly documented since 2.12 but actually available since 2.1 (2014) The argument for this test is in test/TEST-36-NUMAPOLICY/test.sh QEMU_OPTIONS="-numa node,nodeid=0" Fixing that to a new form should help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1908259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1883798] Re: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different f
i had succes with that -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1883798 Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg- turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 Status in libjpeg-turbo package in Ubuntu: Confirmed Bug description: not install file !!! packettracer ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libjpeg-turbo8 2.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 AptOrdering: libjpeg-turbo8:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 17 03:37:01 2020 DpkgTerminalLog: Preparing to unpack .../libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb ... Unpacking libjpeg-turbo8:amd64 (2.0.3-0ubuntu1.20.04.1) over (2.0.3-0ubuntu1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1883798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1883798] Re: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different f
rm -rf /usr/share/doc/libjpeg-turbo8/changelog.Debian.gz then apt --fix-broken install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1883798 Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg- turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 Status in libjpeg-turbo package in Ubuntu: Confirmed Bug description: not install file !!! packettracer ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libjpeg-turbo8 2.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 AptOrdering: libjpeg-turbo8:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 17 03:37:01 2020 DpkgTerminalLog: Preparing to unpack .../libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb ... Unpacking libjpeg-turbo8:amd64 (2.0.3-0ubuntu1.20.04.1) over (2.0.3-0ubuntu1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1883798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908259] [NEW] TEST-36-NUMAPOLICY fails with qemu 5.2
Public bug reported: Hi, this test now fails as seen on ppc here https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/s/systemd/20201214_224336_8b0d8@/log.gz + /bin/qemu-system-ppc64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinux-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.qFc3xq/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=hvc0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' E: QEMU failed with exit code 1 qemu-system-ppc64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) Reproducible in LP infra with systemd 246.6-5ubuntu1 and qemu 5.2 On other architectures this test is just skipped and ppc happened to complete faster so I saw it earlier. The same happens on amd64 + /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.8Hqpmk/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) E: QEMU failed with exit code 1 Isolated this to a test without systemd: $ apt install linux-image-generic qemu-system-x86 $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' Upgrading to 5.2 makes this: $ /bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinuz-5.8.0-25-generic -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append 'console=ttyS0 selinux=0' qemu-system-x86_64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) The numa spec is indeed a bit short -numa node,nodeid=0 If I change this to -numa node,mem=512M,nodeid=0 It would work, but that kind of specification is forbidden >=5.1 Parameter -numa node,mem is not supported by this machine type Use -numa node,memdev instead You'd need also something like -M pc-i440fx-5.0 which isn't anything the test wants to set in stone I guess. Instead using memdev works: -object memory-backend-ram,id=mem0,size=512M -numa node,memdev=mem0,nodeid=0 This works fine and is in qemu since quite some time. Properly documented since 2.12 but actually available since 2.1 (2014) The argument for this test is in test/TEST-36-NUMAPOLICY/test.sh QEMU_OPTIONS="-numa node,nodeid=0" Fixing that to a new form should help. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1908259 Title: TEST-36-NUMAPOLICY fails with qemu 5.2 Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Hi, this test now fails as seen on ppc here https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/s/systemd/20201214_224336_8b0d8@/log.gz + /bin/qemu-system-ppc64 -smp 1 -net none -m 512M -nographic -vga none -kernel /boot/vmlinux-5.8.0-25-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.qFc3xq/default.img -numa node,nodeid=0 -initrd /boot/initrd.img-5.8.0-25-generic -append ' root=/dev/sda1 rw raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=hvc0 selinux=0 SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-36.units:/usr/lib/systemd/tests/testdata/units: systemd.unit=testsuite.target systemd.wants=testsuite-36.service systemd.wants=end.service ' E: QEMU failed with exit code 1 qemu-system-ppc64: total memory for NUMA nodes (0x0) should equal RAM size (0x2000) Reproducible in LP infra with systemd 246.6-5ubuntu1 and qemu 5.2 On other architectures this test is just skipped and ppc happened to complete faster so I saw it earlier. The same happens on amd64 + /bin/qemu-system-x86_64 -smp
[Touch-packages] [Bug 1908241] [NEW] README.sysctl refers to "service procps reload", which no longer works
Public bug reported:
/etc/sysctl.d/README.sysctl states:
After making any changes, please run "service procps reload" (or, from
a Debian package maintainer script "deb-systemd-invoke restart procps.service").
However, "service procps reload" no longer works:
$ sudo service procps reload
Usage: /etc/init.d/procps {start|stop|status|restart|try-restart|force-reload}
It looks like the correct command should be "service procps force-
reload"?
Local versions:
Ubuntu 20.04.1 LTS
procps 2:3.3.16-1ubuntu2
** Affects: procps (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal groovy
** Summary changed:
- sysctl.d/README refers to "service procps reload", which no longer works
+ README.sysctl refers to "service procps reload", which no longer works
** Tags added: focal
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1908241
Title:
README.sysctl refers to "service procps reload", which no longer works
Status in procps package in Ubuntu:
New
Bug description:
/etc/sysctl.d/README.sysctl states:
After making any changes, please run "service procps reload" (or, from
a Debian package maintainer script "deb-systemd-invoke restart
procps.service").
However, "service procps reload" no longer works:
$ sudo service procps reload
Usage: /etc/init.d/procps {start|stop|status|restart|try-restart|force-reload}
It looks like the correct command should be "service procps force-
reload"?
Local versions:
Ubuntu 20.04.1 LTS
procps 2:3.3.16-1ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1908241/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908153] Re: [Alienware 15 R4, Realtek ALC3266, Black Headphone Out or internal speakers] Underruns, dropouts or crackling sound
reassigning to linux if the issue started with a kernel update ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1908153 Title: [Alienware 15 R4, Realtek ALC3266, Black Headphone Out or internal speakers] Underruns, dropouts or crackling sound Status in linux package in Ubuntu: New Bug description: With this latest update (Linux 5.4.0-58), the sound is now crackling. Feels like DMA buffer underruns, but I'm not sure. Not seeing a significant CPU load that might have aggravated it, nor am I seeing any complaints in syslog or kern.log. Restarting pulseaudio and running alsa force-reload had no effect. These sound issues started with the same update that caused the ath10k_pci driver to become extremely unreliable (filed as bug 1908106). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ddt 22891 F pulseaudio /dev/snd/controlC0: ddt 22891 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 14:55:14 2020 InstallationDate: Installed on 2020-03-23 (266 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Dec 14 07:32:47 ddtlap dbus-daemon[859]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=124 pid=1157 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Dec 14 08:11:14 ddtlap pulseaudio[1157]: Failed to create sink input: sink is suspended. Dec 14 08:12:19 ddtlap pulseaudio[1157]: Failed to create sink input: sink is suspended. Dec 14 08:13:47 ddtlap dbus-daemon[859]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.70" (uid=1000 pid=1553 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.3" (uid=0 pid=855 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Alienware 15 R4, Realtek ALC3266, Black Headphone Out, Left] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to focal on 2020-05-12 (216 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 15 R4 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware15R4:pvr1.7.0:rvnAlienware:rnAlienware15R4:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 15 R4 dmi.product.sku: 0876 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846334] Re: cupsd assert failure: free(): invalid pointer
Could someone try if the hirsute version fixes their issue? ** Changed in: cups (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1846334 Title: cupsd assert failure: free(): invalid pointer Status in cups package in Ubuntu: Fix Committed Bug description: Just running in the background, no user action (printing) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: free(): invalid pointer Date: Tue Oct 1 19:41:35 2019 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-09 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: letter PpdFiles: HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at malloc.c:5332 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
** Changed in: network-manager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-dev-wlo1): supplicant management interface state:
[Touch-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4
Could you switch to a vt after getting the issue and do 'journalctl -b 0 > journal' and add the journal file to the bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1849886 Title: lightdm does not work on eoan on raspberry pi 4 Status in lightdm package in Ubuntu: Incomplete Bug description: if you follow the directions on https://wiki.ubuntu.com/ARM/RaspberryPi sudo apt-get install xubuntu-desktop about 20% thru the installation it will ask which window manager you want (using dpkg-reconfigure). if you select lightdm, you will only get a blank greeter screen after you reboot. using sudo dpkg-reconfigure gdm3 resets this to gdm3 and after a reboot, everything is fine. this was done on a clean armhf eoan install on a 4gb raspberry pi 4B. I have done the install several times. This bug is repeatable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1849886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908051] Re: error: Argument 7: Cannot convert from `void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
you should at least specify the valac version you are using
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1908051
Title:
error: Argument 7: Cannot convert from `void
Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
Status in libunity package in Ubuntu:
Incomplete
Bug description:
make returns:
unity-protocol.vapi:242.4-242.43: warning: DBus methods are recommended to
throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void set_view_type (uint
view_type) throws GLib.IOError;
unity-launcher.vala:61.5-61.42: warning: DBus methods are recommended to
throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public HashTable query ()
^^
unity-scope-channel.vala:312.33-312.50: error: Argument 7: Cannot convert
from `void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
(GLib.DBusConnection, string, string, string, string, GLib.Variant)' to `void
GLib.DBusSignalCallback (GLib.DBusConnection, string?, string, string, string,
GLib.Variant)'
DBusSignalFlags.NONE, this.owner_changed);
^^
unity-scope-channel.vala:269.9-269.52: warning: Access to possible `null'.
Perform a check or use an unsafe cast.
(transfer_model as DiffModel).commit_changes ();
unity-synchronizer.vala:93.5-93.18: warning: `GLib.HashTable.add' has been
deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:434.7-434.28: warning:
`GLib.HashTable.add' has been deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:606.7-606.72: warning: Access to possible
`null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByField).map_subscope_categories
(scope_id, proxy.categories_model);
^^
unity-aggregator-scope-private.vala:1308.7-1308.66: warning: Access to
possible `null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByScope).add_scope_mapping (owner,
scope_id);
unity-aggregator-scope-private.vala:1352.7-1352.66: warning: Access to
possible `null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByScope).add_scope_mapping (owner,
master_scope_id);
unity-scope-loader.vala:41.49-41.69: warning: `GLib.ModuleFlags.BIND_LAZY'
has been deprecated since vala-0.46. Use LAZY
unity-sound-menu-mpris.vala:475.5-475.27: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void raise() throws IOError{
^^^
unity-sound-menu-mpris.vala:580.5-580.32: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void play_pause() throws IOError
unity-sound-menu-mpris.vala:585.5-585.26: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void next() throws IOError
^^
unity-sound-menu-mpris.vala:590.5-590.30: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void previous() throws IOError
^^
unity-sound-menu-mpris.vala:709.5-709.39: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void activate_playlist (ObjectPath playlist_id) throws
IOError
^^^
unity-sound-menu-mpris.vala:714.5-714.48: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async PlaylistDetails[] get_playlists (uint32 index,
unity-sound-menu-mpris.vala:407.5-407.55: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void EnableTrackSpecificItems (ObjectPath
object_path, string desktop_id) throws IOError;
^^^
unity-sound-menu-mpris.vala:408.5-408.56: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void EnablePlayerSpecificItems (ObjectPath
object_path, string desktop_id) throws IOError;
[Touch-packages] [Bug 1908051] Re: error: Argument 7: Cannot convert from `void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.
At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Please also ensure that you include the release and flavour of Ubuntu
that you are using.
Thank you!
** Changed in: libunity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1908051
Title:
error: Argument 7: Cannot convert from `void
Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
Status in libunity package in Ubuntu:
Incomplete
Bug description:
make returns:
unity-protocol.vapi:242.4-242.43: warning: DBus methods are recommended to
throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void set_view_type (uint
view_type) throws GLib.IOError;
unity-launcher.vala:61.5-61.42: warning: DBus methods are recommended to
throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public HashTable query ()
^^
unity-scope-channel.vala:312.33-312.50: error: Argument 7: Cannot convert
from `void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
(GLib.DBusConnection, string, string, string, string, GLib.Variant)' to `void
GLib.DBusSignalCallback (GLib.DBusConnection, string?, string, string, string,
GLib.Variant)'
DBusSignalFlags.NONE, this.owner_changed);
^^
unity-scope-channel.vala:269.9-269.52: warning: Access to possible `null'.
Perform a check or use an unsafe cast.
(transfer_model as DiffModel).commit_changes ();
unity-synchronizer.vala:93.5-93.18: warning: `GLib.HashTable.add' has been
deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:434.7-434.28: warning:
`GLib.HashTable.add' has been deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:606.7-606.72: warning: Access to possible
`null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByField).map_subscope_categories
(scope_id, proxy.categories_model);
^^
unity-aggregator-scope-private.vala:1308.7-1308.66: warning: Access to
possible `null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByScope).add_scope_mapping (owner,
scope_id);
unity-aggregator-scope-private.vala:1352.7-1352.66: warning: Access to
possible `null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByScope).add_scope_mapping (owner,
master_scope_id);
unity-scope-loader.vala:41.49-41.69: warning: `GLib.ModuleFlags.BIND_LAZY'
has been deprecated since vala-0.46. Use LAZY
unity-sound-menu-mpris.vala:475.5-475.27: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void raise() throws IOError{
^^^
unity-sound-menu-mpris.vala:580.5-580.32: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void play_pause() throws IOError
unity-sound-menu-mpris.vala:585.5-585.26: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void next() throws IOError
^^
unity-sound-menu-mpris.vala:590.5-590.30: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void previous() throws IOError
^^
unity-sound-menu-mpris.vala:709.5-709.39: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void activate_playlist (ObjectPath playlist_id) throws
IOError
^^^
unity-sound-menu-mpris.vala:714.5-714.48: warning: DBus methods are
[Touch-packages] [Bug 1908239] [NEW] package libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is d
Public bug reported: I WILL INSTALL WINE, BUT ERROR Errors were encountered while processing: /var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 15 16:25:00 2020 ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:i386 InstallationDate: Installed on 2020-09-23 (82 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libjpeg-turbo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1908239 Title: package libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg- turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:i386 Status in libjpeg-turbo package in Ubuntu: New Bug description: I WILL INSTALL WINE, BUT ERROR Errors were encountered while processing: /var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 15 16:25:00 2020 ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:i386 InstallationDate: Installed on 2020-09-23 (82 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8 2.0.3-0ubuntu1.20.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1908239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797002] Re: Bluetooth audio skips while the settings dialog is open
Yeah OK... Anyone experiencing this bug please also report it to BlueZ upstream: https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers=Bluetooth and then tell us the new bug ID. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: Bluetooth audio skips while the settings dialog is open Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797002] Re: Bluetooth audio skips while the settings dialog is open
Unsure if that's something settings could change though, it's probably due to the panel triggering bluetooth discovery automatically -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: Bluetooth audio skips while the settings dialog is open Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797002] Re: Bluetooth audio skips while the settings dialog is open
Can anyone experiencing this bug please report it upstream? https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues And then tell us the new issue ID. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: Bluetooth audio skips while the settings dialog is open Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
** Description changed: - this bug is for tracking purpose. + [Impact] + On the Dell AIO machines, there is no internal mic, after plugging a + headset, users expect the headset-mic or headphone-mic could be selected + automatically. But with the current rule, the headset-mic/headphone-mic will + not be selected automatically and even users manually select them, they will + not show up in the gnome sound setting, and users could not record sound by + headset-mic/headphone-mic. + + [Fix] + backport a patch from pulseaudio mergerequest, the patch is going to be + merged to pulseaudio 14.1. This patch could be backported to hirsute without + any change, but need to be changed if backport it to groovy and focal. + + [Test] + On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic + is selected automatically, use the headset-mic to record the sound, the sound could + be recorded and the sound quality is good. + + [Where problems could occur] + This patch could change the policy of audio device switching, it will not + affect all audio devices, but only the devices which has AVAIL_UNKNOWN available + status, that means it has possibility to introduce the regression on headphone-mic + , headset-mic, internal mic and internal speaker's switching since they all has + AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device + will not switch to internl mic automatically or after unplug the headphone, the + output device will not switch to internal speaker automatically. But this possibility + is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. ** Description changed: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected - automatically. But with the current rule, the headset-mic/headphone-mic will - not be selected automatically and even users manually select them, they will - not show up in the gnome sound setting, and users could not record sound by - headset-mic/headphone-mic. + automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be - merged to pulseaudio 14.1. This patch could be backported to hirsute without - any change, but need to be changed if backport it to groovy and focal. + merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] - On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic - is selected automatically, use the headset-mic to record the sound, the sound could - be recorded and the sound quality is good. + On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not - affect all audio devices, but only the devices which has AVAIL_UNKNOWN available - status, that means it has possibility to introduce the regression on headphone-mic - , headset-mic, internal mic and internal speaker's switching since they all has - AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device - will not switch to internl mic automatically or after unplug the headphone, the - output device will not switch to internal speaker automatically. But this possibility - is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. + affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy:
[Touch-packages] [Bug 1908167] Re: pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
This is the debdiff for focal, thx. ** Patch added: "pulseaudio_13.99.1-1ubuntu3.9.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908167/+attachment/5443772/+files/pulseaudio_13.99.1-1ubuntu3.9.debdiff ** Summary changed: - pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic + [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: In Progress Status in pulseaudio source package in Hirsute: In Progress Bug description: this bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908167] Re: pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
This is the debdiff for groovy, thx. ** Patch added: "pulseaudio_13.99.2-1ubuntu2.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908167/+attachment/5443771/+files/pulseaudio_13.99.2-1ubuntu2.2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: In Progress Status in pulseaudio source package in Hirsute: In Progress Bug description: this bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908167] Re: pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
This is the debdiff for hirsute, thx. ** Patch added: "pulseaudio_14.0-1ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908167/+attachment/5443770/+files/pulseaudio_14.0-1ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: In Progress Status in pulseaudio source package in Hirsute: In Progress Bug description: this bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
