[Touch-packages] [Bug 1883793] Re: systemd-resolved leaks mDNS queries to DNS
Finished my investigation. Guess it is not a bug after all, rather — I would say — a matter of extremely dispersed documentation plus very unfriendly behavior from the ISP. The situation is that even if you put mdns_minimal in front of other entries in hosts in nsswitch, mdns /is not queried/ if the DNS declares SOA for the "local" domain. Mine does. This is the reason why I was getting the impression of systemd-resolved passing queries to DNS even when it should not have. It was actually nss_mdns to let it do so. The fact that for some time my isp has directed all dns queries to its own nameserver even when another one was selected did not help in verifying the behavior with a dns not declaring SOA for local. Yet, this aspect of the linux mdns implementation should be documented with much better emphasis, or even better, there should be a way to make mdns_minimal report/log what it is doing. Currently, you find mention of the mdns "handover" to dns for local only looking at the very end of /usr/share/doc/libnss-mdns/README.md.gz where the heuristics is explained. Because heuristics /can go wrong/, the item should IMHO be given much better emphasis. For instance, I suggest that ubuntu ships with a man page for nss_mdns and nss_mdns_minimal. ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Package changed: systemd (Ubuntu) => nss-mdns (Ubuntu) -- 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/1883793 Title: systemd-resolved leaks mDNS queries to DNS Status in nss-mdns package in Ubuntu: Invalid Bug description: On a freshly installed ubuntu focal machine, access to local machines advertised via mDNS is now broken. This is a regression wrt eoan where it used to work. Trying to ping something like .local invariably results in pinging 40.68.249.35 because systemd-resolved passes the query to the DNS even if .local is reserved for multicast DNS and for some reasons .local seems to resolve to 40.68.249.35. This happens even if the avahi daemon is up and running. Stopping systemd-resolved makes the mDNS resolution work as expected. Not only this breaks standard workflows, but it also means that anyone pretending to be 40.68.249.35 on the network could probably impersonate any local host. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 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 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jun 16 23:43:22 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (121 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-23 (24 days ago) dmi.bios.date: 10/02/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-mdns/+bug/1883793/+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 1904192] Re: ebtables can not rename just created chain
This bug was fixed in the package iptables - 1.8.5-3ubuntu4 --- iptables (1.8.5-3ubuntu4) hirsute; urgency=medium * Fix regression in ebtables when renaming a chain (LP: #1904192) - d/p/9004-ebtables-fix-for-broken-chain-rename.patch: Backport patch from upstream to fix improper use of errno to indicate failure when renaming an existing chain. -- Alex Murray Wed, 18 Nov 2020 11:36:27 +1030 ** Changed in: iptables (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 iptables in Ubuntu. https://bugs.launchpad.net/bugs/1904192 Title: ebtables can not rename just created chain Status in iptables: Unknown Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Groovy: In Progress Status in iptables package in Debian: Unknown Status in iptables package in Fedora: Fix Committed Bug description: [SRU] * Changes that went into 1.8.5 ave broken the errno handling. In particular loading extensions. Due to that it has become impossible to rename rules. * Upstream has created a fix and this backports that change to Ubuntu => http://git.netfilter.org/iptables/commit/?id=55b7c71dce7144f4dc0297c17abf0f04879ee247 [Test Case] * # ebtables -t nat -N foo # ebtables -t nat -E foo bar ebtables v1.8.5 (nf_tables): Chain 'foo' doesn't exists * with the fix the above command sequence works [Where problems could occur] * The change moved code from nft_chain_user_rename to do_commandeb and therefore in theory any ebtables/xtables subcommand could be affected. Yet what it does is just resetting the error code in a better place, so while it "could" affect every subcommand it should (tm) not do so. [Other Info] * n/a --- Hi, I have an issue with ebtables that affects libvirt. While initially found in hirsute I had to realize this is broken in Groovy and even Bionic (might be a different reason back then) as well right now. But working in Focal (witch matches my memory of it being good before [1]). I was isolating the commands that libvirt runs (identical between Focal and Hirsute) to find a simplified trigger. Gladly I found one that leaves libvirt and other components out of the equation. The following works on focal, but fails on the other releases. Note: I checked which tool is in use and in both cases it is xtables-nft-multi. /usr/sbin/ebtables -> /etc/alternatives/ebtables* /etc/alternatives/ebtables -> /usr/sbin/ebtables-nft* /usr/sbin/ebtables-nft -> xtables-nft-multi* So I converted the libvirt issued commands into xtables-nft-multi just to be sure in case a system to compare has other alternatives set. Focal (Good): /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -N testrule3 /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -E testrule3 testrule3-renamed Groovy/Hirsute (Fail): /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -N testrule3 /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -E testrule3 testrule3-renamed ebtables v1.8.5 (nf_tables): Chain 'testrule3' doesn't exists Try `ebtables -h' or 'ebtables --help' for more information. What might be the root cause for this? -- Old test instructions -- As I said I was tracking a fail in libvirt so the test instructions initially were around that: # the following us done as 2nd level guest (to not mess with the host, # but works on bare metal jst as much) uvt-kvm create --host-passthrough --memory 2048 --cpu 4 --disk 16 --password=ubuntu hirsute-kvm release=hirsute arch=amd64 label=daily # On guest then sudo apt update sudo apt install uvtool uvtool-libvirt uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=hirsute uvt-kvm create --disk 5 --machine-type ubuntu --password=ubuntu hirsute-2nd-lvm release=hirsute arch=amd64 label=daily uvt-kvm wait hirsute-2nd-lvm virsh shutdown hirsute-2nd-lvm virsh edit hirsute-2nd-lvm # add this to the network virsh start hirsute-2nd-lvm error: Failed to start domain hirsute-2nd-nwfilter error: internal error: applyDHCPOnlyRules failed - spoofing not protected! FYI: Get helpful log details with these in /etc/libvirt/libvirtd.conf log_filters="1:util.firewall" log_outputs="1:syslog:libvirtd" -- -- [1]: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1758037 To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1904192/+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 1303316] Re: Digital S/PDIF output is not present in 5.1 mode
** Tags removed: trusty ** Tags added: groovy ** Tags removed: precise ** Changed in: pulseaudio (Ubuntu) Status: Won't Fix => New -- 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/1303316 Title: Digital S/PDIF output is not present in 5.1 mode Status in pulseaudio package in Ubuntu: New Bug description: I have the sound connected through digital S / PDIF Sound works properly selecting stereo, but can not get it to work using 5.1 When I select stereo sound, appears on the tab below to phonon spdif output option. When I select Output 5.1, that option does not appear. I imagine the error will also occur selecting 7.1 Deputy screenshots. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: phonon 4:4.7.0really4.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Apr 6 13:12:42 2014 InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: phonon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303316/+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 1905346] [NEW] USB devices, Headphones drives. And others like webcam not detected, as well as failing to powerdown
Public bug reported: https://askubuntu.com/questions/1294526/unbunti-20-04-01-kernal-5-4-0-54 -generic-amd-3700-u-issue-of-not-shutting-down-a this is explanation of main issue, I feel the usb headphones and drives not being detected is a symptom. Also webcam is not detected as well, and sound won't work at all sometimes. Meaning that it is started off random and rebooting would fix, but over last month the problem has gotten worse to happen multiple times a day. to where the problem is not more normal state. booting into recovery mode seems to do nothing. it's not hardware as windows 10 is dual booted on my machine (asus zenbook um433d ryzen 7 3700U AMD) works fine, I've reinstalled ubuntu which first install had similar problems everything is fine first month then problems start happening. It happened similarly here. running usb version to test older version of unbuntu like 20.10 and 18.04 off usb stick sound and web cam work. However not sure if this indicative of initial problem or not. But computer will not come out of suspend in any version. The problem is getting worse and I haven't found any real solution other than upgrade the kernal because, or try a different distro. Please help and let me know if I can provide additional data to aid in this problem. My background is in Science, IT, and now entering web development. Thank you, Topher Judd gnrforl...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: topher 2392 F pulseaudio /dev/snd/controlC0: topher 2392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 09:00:55 2020 InstallationDate: Installed on 2020-10-03 (51 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434DA_UM433DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434DA_UM433DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1905346 Title: USB devices, Headphones drives. And others like webcam not detected, as well as failing to powerdown Status in alsa-driver package in Ubuntu: New Bug description: https://askubuntu.com/questions/1294526/unbunti-20-04-01-kernal-5-4-0-54 -generic-amd-3700-u-issue-of-not-shutting-down-a this is explanation of main issue, I feel the usb headphones and drives not being detected is a symptom. Also webcam is not detected as well, and sound won't work at all sometimes. Meaning that it is started off random and rebooting would fix, but over last month the problem has gotten worse to happen multiple times a day. to where the problem is not more normal state. booting into recovery mode seems to do nothing. it's not hardware as windows 10 is dual booted on my machine (asus zenbook um433d ryzen 7 3700U AMD) works fine, I've reinstalled ubuntu which first install had similar problems everything is fine first month then problems start happening. It happened similarly here. running usb version to test older version of unbuntu like 20.10 and 18.04 off usb stick sound and web cam work. However not sure if this indicative of initial problem or not. But computer will not come out of suspend in any version. The problem is getting worse and I haven't found any real solution other than upgrade the kernal because, or try a different distro. Please help and let me know if I can provide additional data to aid in this problem. My background is in Science, IT, and now entering web development. Thank you, Topher Judd gnrforl...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64
[Touch-packages] [Bug 1905285] Re: socket-activated sshd breaks on concurrent connections
Hello Marcin, the Description section of
https://www.freedesktop.org/software/systemd/man/systemd.unit.html gives
information on how to modify configurations without having them undone
by future updates; the systemctl edit command automates the process of
using these local modifications.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1905285
Title:
socket-activated sshd breaks on concurrent connections
Status in openssh package in Ubuntu:
New
Bug description:
This is mostly the same issue as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=934663.
With the default configuration of openssh-server and systemd, sshd
will complain and crash when multiple connections are made and
terminated in a quick succession, e.g. with `ssh-keyscan`. It results
in the following errors in /var/log/auth.log:
```
Nov 22 20:53:34 {host} sshd[14567]: Unable to negotiate with {client} port
41460: no matching host key type found. Their offer:
sk-ecdsa-sha2-nistp...@openssh.com [preauth]
Nov 22 20:53:34 {host} sshd[14570]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:34 {host} sshd[14569]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:34 {host} sshd[14568]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:34 {host} sshd[14566]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:47 {host} sshd[14584]: Connection closed by {client} port 59312
[preauth]
Nov 22 20:53:47 {host} sshd[14586]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
Nov 22 20:53:48 {host} sshd[14585]: fatal: chroot("/run/sshd"): No such file
or directory [preauth]
```
as well as e.g. missing responses in ssh-keyscan:
```
$ ssh-keyscan -vvv {host}
debug2: fd 3 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 2
debug2: fd 4 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 4
debug2: fd 5 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 8
debug2: fd 6 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 32
debug2: fd 7 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 64
debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.1 pat OpenSSH* compat 0x0400
# {host}:22 SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.1
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms:
curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256
debug2: host key algorithms: sk-ecdsa-sha2-nistp...@openssh.com
debug2: ciphers ctos:
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
debug2: ciphers stoc:
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
debug2: MACs ctos:
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc:
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,z...@openssh.com
debug2: compression stoc: none,z...@openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms:
curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms:
rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos:
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
debug2: ciphers stoc:
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
debug2: MACs ctos:
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc:
[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Thanks @hui.wang. Upgrading to Groovy didn't fix the issue for me with an AX200 card, but installing rtl8821ce-dkms made it work great. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
Same bug seen on Ubuntu Bionic 18.04.5 LTS with Lenovo P53. In my case, the bug seen when attempting a domain login in ubuntu. About 75% of the time, the login hangs for several minutes, then the screen turns black, and returns to the greater. Once in a while, the user is able to login. The workaround of removing the at-spi2-core package effectively stops the crashes -- but this removes also other functionalities. For example, nautilus is removed. Is there a patch available, or did anyone report the bug upstream yet ? Logs of the error : Nov 20 15:44:47 HOSTNAME gnome-session[5658]: gnome-session-binary[5658]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Nov 20 15:44:47 HOSTNAME gnome-session[5658]: gnome-session-binary[5658]: CRITICAL: We failed, but the fail whale is dead. Sorry Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: Unrecoverable failure in required component org.gnome.Shell.desktop Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: CRITICAL: We failed, but the fail whale is dead. Sorry Nov 20 15:44:47 HOSTNAME at-spi-bus-launcher[5774]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" Nov 20 15:44:47 HOSTNAME at-spi-bus-launcher[5774]: after 21 requests (21 known processed) with 0 events remaining. ** Tags added: cpe-onsite -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend Status in at-spi2-core package in Ubuntu: Confirmed Bug description: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+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
** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress -- 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/1905245 Title: "Failed to parse bus message: Invalid argument" with Linux 5.8 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: In Progress Bug description: [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 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. [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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905245/+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 1905167] Re: htop shows 100% usage of systemd-udevd
** Attachment added: "udev2.perf" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1905167/+attachment/5437314/+files/udev2.perf -- 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/1905167 Title: htop shows 100% usage of systemd-udevd Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I'm attaching a perf profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 13:57:47 2020 InstallationDate: Installed on 2020-02-08 (287 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/dnscrypt-proxy.service → /etc/systemd/system/dnscrypt-proxy.service.d/override.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1905167/+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 1905167] Re: htop shows 100% usage of systemd-udevd
Okay, so i installed manually through terminal nvidia-drivers-455, which removed the old 450 and installed itself, then i rebooted. After reboot now htop doesn't show 100% constant of systemd-udevd, but shows between 20% to 80%, the medium looks like 50% CPU usage. In Journalctl there is constant nagging: ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 236 ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s). ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: NVRM: This can occur when a driver such as: NVRM: nouveau, rivafb, nvidiafb or rivatv NVRM: was loaded and obtained ownership of the NVIDIA device(s). ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: NVRM: Try unloading the conflicting kernel module (and/or NVRM: reconfigure your kernel without the conflicting NVRM: driver(s)), then try loading the NVIDIA kernel module NVRM: again. ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: NVRM: No NVIDIA devices probed. ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 236 ное 23 23:48:22 lyubomir-Aspire-A515-51G systemd-udevd[709]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. ное 23 23:48:22 lyubomir-Aspire-A515-51G systemd[1]: nvidia-persistenced.service: Start request repeated too quickly. ное 23 23:48:22 lyubomir-Aspire-A515-51G systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. ное 23 23:48:22 lyubomir-Aspire-A515-51G systemd[1]: Failed to start NVIDIA Persistence Daemon. ное 23 23:48:22 lyubomir-Aspire-A515-51G boinc[2398]: No protocol specified ное 23 23:48:22 lyubomir-Aspire-A515-51G boinc[2398]: No protocol specified ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 236 ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s). ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: NVRM: This can occur when a driver such as: NVRM: nouveau, rivafb, nvidiafb or rivatv NVRM: was loaded and obtained ownership of the NVIDIA device(s). ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: NVRM: Try unloading the conflicting kernel module (and/or NVRM: reconfigure your kernel without the conflicting NVRM: driver(s)), then try loading the NVIDIA kernel module NVRM: again. ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: NVRM: No NVIDIA devices probed. ное 23 23:48:22 lyubomir-Aspire-A515-51G kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 236 ное 23 23:48:22 lyubomir-Aspire-A515-51G systemd-udevd[709]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. -- 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/1905167 Title: htop shows 100% usage of systemd-udevd Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I'm attaching a perf profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 13:57:47 2020 InstallationDate: Installed on 2020-02-08 (287 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/dnscrypt-proxy.service → /etc/systemd/system/dnscrypt-proxy.service.d/override.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor:
[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, so it fails when trying to map - the capability to a user-facing name, which causes failure when running + 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] - TBD + 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 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. [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. -- 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/1905245 Title: "Failed to parse bus message: Invalid argument" with Linux 5.8 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: New Bug description: [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 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. [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. To manage notifications about
[Touch-packages] [Bug 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
likely same as bug 1905245 -- 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: Invalid Status in systemd source package in Focal: Confirmed Bug 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 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, 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] + + TBD + + [scope] + + 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. + + 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. + + [original description] + When I run `systemctl show myservice.service`, I get the following error message: -Failed to parse bus message: Invalid argument + 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. ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) 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/1905245 Title: "Failed to parse bus message: Invalid argument" with Linux 5.8 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: New Bug description: [impact] newer kernels introduced a new capability, and existing systemd doesn't have the name mapping for the new cap, 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] TBD [scope] 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. 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. [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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905245/+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
** Tags added: rls-bb-incoming rls-ff-incoming -- 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/1905245 Title: "Failed to parse bus message: Invalid argument" with Linux 5.8 Status in systemd package in Ubuntu: New Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905245/+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
https://github.com/systemd/systemd/pull/16424 -- 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/1905245 Title: "Failed to parse bus message: Invalid argument" with Linux 5.8 Status in systemd package in Ubuntu: New Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905245/+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 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)
** Description changed: - Apport popped up saying whoopsie had crashed (I assume during a previous - crash report upload?) + [Impact] + whoopsie is crashing somewhat regularly. There are a couple of crashes in the Error Tracker which look similar: - ProblemType: Crash - DistroRelease: Ubuntu 20.10 + https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd + https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98 + + As of yet (2020-11-22) neither crash is happening with whoopsie version + 0.2.73. + + + Apport popped up saying whoopsie had crashed (I assume during a previous crash report upload?) + + ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AssertionMessage: double free or corruption (fasttop) CasperMD5CheckResult: skip CrashCounter: 1 Date: Fri Oct 9 08:08:56 2020 ExecutablePath: /usr/bin/whoopsie InstallationDate: Installed on 2019-11-18 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/whoopsie -f ProcEnviron: - LANG=en_AU.UTF-8 - LANGUAGE=en_AU:en - PATH=(custom, no user) + LANG=en_AU.UTF-8 + LANGUAGE=en_AU:en + PATH=(custom, no user) RelatedPackageVersions: apport-noui N/A - Signal: 6 - SourcePackage: whoopsie + Signal: 6SourcePackage: whoopsie StacktraceTop: - __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 - malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption (fasttop)") at malloc.c:5389 - _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at malloc.c:4298 - () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 + malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption (fasttop)") at malloc.c:5389 + _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at malloc.c:4298 + () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: whoopsie assert failure: double free or corruption (fasttop) UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago) UserGroups: N/A separator: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1899100 Title: whoopsie assert failure: double free or corruption (fasttop) Status in whoopsie package in Ubuntu: Fix Released Bug description: [Impact] whoopsie is crashing somewhat regularly. There are a couple of crashes in the Error Tracker which look similar: https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98 As of yet (2020-11-22) neither crash is happening with whoopsie version 0.2.73. Apport popped up saying whoopsie had crashed (I assume during a previous crash report upload?) ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AssertionMessage: double free or corruption (fasttop) CasperMD5CheckResult: skip CrashCounter: 1 Date: Fri Oct 9 08:08:56 2020 ExecutablePath: /usr/bin/whoopsie InstallationDate: Installed on 2019-11-18 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/whoopsie -f ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) RelatedPackageVersions: apport-noui N/A Signal: 6SourcePackage: whoopsie StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption (fasttop)") at malloc.c:5389 _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at malloc.c:4298 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: whoopsie assert failure: double free or corruption (fasttop) UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1899100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1905167] Re: htop shows 100% usage of systemd-udevd
If you stopped mid-upgrade, I'd suggest finishing the package upgrade and reboot. If you still have problems with fully/correctly upgraded packages you will need to provide more logs; the journal for systemd- udevd is a good place to start. -- 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/1905167 Title: htop shows 100% usage of systemd-udevd Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I'm attaching a perf profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 13:57:47 2020 InstallationDate: Installed on 2020-02-08 (287 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/dnscrypt-proxy.service → /etc/systemd/system/dnscrypt-proxy.service.d/override.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1905167/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
2.1.12 will be landing in hirsute tomorrow-ish, once it syncs from Debian unstable. This fixes _this_ bug, namely immediate configuration of _foreign_ architecture packages, by disabling the code that forces them to be configured together with their native architecture siblings. It does _not_ fix other instances that look like this bug where the package failing to be configured immediately is a native architecture package, nor does it fix issues where disabling immediate configuration causes the ordering to fail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: Triaged Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
As requested by the uploader, I will be dropping apt 2.1.11 from groovy- proposed. It will be superseeded by a newer version in the nearest future. ** Changed in: apt (Ubuntu Groovy) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: Triaged Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl
[Touch-packages] [Bug 1905167] Re: htop shows 100% usage of systemd-udevd
I have not installed any unofficial ppa or manual drivers. The only ones that are supposed to be installed are the official binary nvidia drivers. However, i remember that recently through "Software & Updates -> Additional drivers" i clicked a newer version (455, IIRC), it showed a progress bar, but i decided that i'll take many MBs and i' currently on metered connection, so i clicked "Revert" or "Cancel" or something like that. Then i clicked "Close". I only have these packages installed: libnvidia-cfg1-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] libnvidia-common-450/focal-updates,focal-updates,now 450.80.02-0ubuntu0.20.04.2 all [installed] libnvidia-compute-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] libnvidia-compute-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 i386 [installed,automatic] libnvidia-decode-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] libnvidia-decode-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 i386 [installed] libnvidia-encode-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] libnvidia-encode-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 i386 [installed] libnvidia-extra-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] libnvidia-fbc1-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] libnvidia-fbc1-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 i386 [installed] libnvidia-gl-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] libnvidia-gl-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 i386 [installed] libnvidia-ifr1-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] libnvidia-ifr1-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 i386 [installed] nvidia-compute-utils-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] nvidia-dkms-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] nvidia-kernel-common-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] nvidia-kernel-source-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] nvidia-prime/focal,focal,now 0.8.14 all [installed] nvidia-settings/focal-updates,now 440.82-0ubuntu0.20.04.1 amd64 [installed] nvidia-utils-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] xserver-xorg-video-nvidia-450/focal-updates,now 450.80.02-0ubuntu0.20.04.2 amd64 [installed] -- 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/1905167 Title: htop shows 100% usage of systemd-udevd Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I'm attaching a perf profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 13:57:47 2020 InstallationDate: Installed on 2020-02-08 (287 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/dnscrypt-proxy.service → /etc/systemd/system/dnscrypt-proxy.service.d/override.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1905167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
We do not have a fix for this yet. ** Changed in: apt (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Committed Status in apt source package in Bionic: Triaged Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Fix Committed Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date:
[Touch-packages] [Bug 1905167] Re: htop shows 100% usage of systemd-udevd
Your problem appears to be with the nvidia driver and/or service(s), not with systemd; do you have any 3rd-party nvidia packages or tools installed, or are you using the official ubuntu-provided nvidia packages? ** Also affects: nvidia-graphics-drivers-455 (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1905167 Title: htop shows 100% usage of systemd-udevd Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I'm attaching a perf profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 13:57:47 2020 InstallationDate: Installed on 2020-02-08 (287 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/dnscrypt-proxy.service → /etc/systemd/system/dnscrypt-proxy.service.d/override.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1905167/+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 1903814] for 18.04
--- Comment on attachment From i...@de.ibm.com 2020-11-23 11:20 EDT--- The attached patch applies cleanly to binutils-2_30 tag and binutils_2.30-21ubuntu1~18.04.4ubuntu1. ** Attachment added: "for 18.04" https://bugs.launchpad.net/bugs/1903814/+attachment/5437266/+files/patch-binutils-2_30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1903814 Title: [binutils] Prevent GOT access rewrite for certain symbols Status in Ubuntu on IBM z Systems: Triaged Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Bionic: New Status in binutils package in Debian: New Bug description: Please backport the following bugfix into Ubuntu LTS: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e6213e09ed0e Some relevant historic links: Debian bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961736 glibc bugreport: https://sourceware.org/bugzilla/show_bug.cgi?id=18960 In s390 kernel context, this bug manifests itself as random errors and infinite loops, so it's fairly severe. These are the current versions of binutils: Package binutils xenial (16.04LTS) (devel): GNU assembler, linker and binary utilities 2.26.1-1ubuntu1~16.04.8 [security]: amd64 i386 2.26-8ubuntu2 [ports]: arm64 armhf powerpc ppc64el s390x xenial-updates (devel): GNU assembler, linker and binary utilities 2.26.1-1ubuntu1~16.04.8: amd64 arm64 armhf i386 powerpc ppc64el s390x bionic (18.04LTS) (devel): GNU assembler, linker and binary utilities 2.30-21ubuntu1~18.04.4 [security]: amd64 i386 2.30-15ubuntu1 [ports]: arm64 armhf ppc64el s390x bionic-updates (devel): GNU assembler, linker and binary utilities 2.30-21ubuntu1~18.04.4: amd64 arm64 armhf i386 ppc64el s390x focal (20.04LTS) (devel): GNU assembler, linker and binary utilities 2.34-6ubuntu1: amd64 arm64 armhf i386 ppc64el s390x groovy (devel): GNU assembler, linker and binary utilities 2.35.1-1ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The patch applies fine to 2.26 and 2.30 (except for tests, but we don't need them). We don't need it on 2.32+. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+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 1886854] Re: Race in load-module snap policy check in classic confinement
This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.11 --- pulseaudio (1:11.1-1ubuntu7.11) bionic-security; urgency=medium * SECURITY UPDATE: don't rely on SCM_CREDENTIALS to detect snap confined clients (LP: #1895928) - d/p/0409-pa-client-peer-credentials.patch: drop patch - d/p/0409-fix-arg-parsing-after-async-hook.patch: remains of old 0409 patch not related to pa_creds. - d/p/0410-pa-client-peer-apparmor-label.patch: new patch, records AppArmor label in pa_client struct for native connections using aa_getpeercon. - d/p/0702-add-snappy-policy-module.patch: use the AppArmor label in the pa_client rather than looking it up via the process ID from SCM_CREDENTIALS. - CVE-2020-16123 * Don't block classic snaps from module loading/unloading (LP: #1886854) - d/p/0702-add-snappy-policy-module.patch: replace deny_to_snaps_hook with a version that allows classic snaps. -- James Henstridge Tue, 22 Sep 2020 12:30:20 +0800 -- 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: Fix Released Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes the following run the snap to fail again. EXPECTED
[Touch-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.8 --- pulseaudio (1:13.99.1-1ubuntu3.8) focal-security; urgency=medium * SECURITY UPDATE: don't rely on SCM_CREDENTIALS to detect snap confined clients (LP: #1895928) - d/p/0409-pa-client-peer-credentials.patch: drop patch - d/p/0409-fix-arg-parsing-after-async-hook.patch: remains of old 0409 patch not related to pa_creds. - d/p/0410-pa-client-peer-apparmor-label.patch: new patch, records AppArmor label in pa_client struct for native connections using aa_getpeercon. - d/p/0702-add-snappy-policy-module.patch: use the AppArmor label in the pa_client rather than looking it up via the process ID from SCM_CREDENTIALS. - CVE-2020-16123 * Don't block classic snaps from module loading/unloading (LP: #1886854) - d/p/0702-add-snappy-policy-module.patch: replace deny_to_snaps_hook with a version that allows classic snaps. -- James Henstridge Thu, 15 Oct 2020 17:23:31 -0400 ** 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: Fix Released Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting
[Touch-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement
This bug was fixed in the package pulseaudio - 1:13.99.2-1ubuntu2.1 --- pulseaudio (1:13.99.2-1ubuntu2.1) groovy-security; urgency=medium * SECURITY UPDATE: don't rely on SCM_CREDENTIALS to detect snap confined clients (LP: #1895928) - d/p/0409-pa-client-peer-credentials.patch: drop patch - d/p/0409-fix-arg-parsing-after-async-hook.patch: remains of old 0409 patch not related to pa_creds. - d/p/0410-pa-client-peer-apparmor-label.patch: new patch, records AppArmor label in pa_client struct for native connections using aa_getpeercon. - d/p/0702-add-snappy-policy-module.patch: use the AppArmor label in the pa_client rather than looking it up via the process ID from SCM_CREDENTIALS. - CVE-2020-16123 * Don't block classic snaps from module loading/unloading (LP: #1886854) - d/p/0702-add-snappy-policy-module.patch: replace deny_to_snaps_hook with a version that allows classic snaps. -- James Henstridge Thu, 05 Nov 2020 16:46:59 -0500 ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16123 ** 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: Fix Released Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work
[Touch-packages] [Bug 1905167] Re: htop shows 100% usage of systemd-udevd
Today it again does this, but this time immediately after i SIGKILL the process it again resumes with 100% CPU. -- 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/1905167 Title: htop shows 100% usage of systemd-udevd Status in systemd package in Ubuntu: New Bug description: I'm attaching a perf profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 13:57:47 2020 InstallationDate: Installed on 2020-02-08 (287 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/dnscrypt-proxy.service → /etc/systemd/system/dnscrypt-proxy.service.d/override.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905167/+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 1904549] Re: MTU is not set on vlan interface
I can't reproduce it, on a VM with similar config the vlan does get the
right mtu. can you provide your systemd-networkd journal log? Is there a
specific environment (e.g. specific cloud) this fails in?
** 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/1904549
Title:
MTU is not set on vlan interface
Status in netplan:
New
Status in netplan.io package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Hello,
Upon changing the following configuration, adding the MTU lines, I
ended up with the VLAN interfaces still in MTU 1500 after a `netplan
generate && netplan apply`
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
# uname -a
Linux il3-fw2 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
# dpkg -l netplan.io
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionArchitecture Description
+++-==-==--===
ii netplan.io 0.100-0ubuntu4~20.04.2 amd64YAML network
configuration abstraction for various backends
==
# This is the network config written by 'subiquity'
network:
ethernets:
ens10f0: {}
ens10f1: {}
ens10f2: {}
ens10f3: {}
ens1f0: {}
ens1f1: {}
bonds:
bond-oam:
interfaces: [ens10f0, ens10f1]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
mtu: 9000
bond-manlan:
interfaces: [ens10f2, ens10f3]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
bond-core:
interfaces: [ens1f0, ens1f1]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
mtu: 9000
vlans:
vlan3001:
id: 3001
link: bond-manlan
addresses: [ "10.130.1.3/24" ]
vlan3002:
id: 3002
link: bond-manlan
addresses: [ "10.130.2.3/24" ]
vlan3003:
id: 3003
link: bond-manlan
addresses: [ "10.130.3.3/24" ]
vlan3054:
id: 3054
link: bond-core
addresses: [ "10.130.56.3/24" ]
mtu: 9000
vlan3065:
id: 3065
link: bond-oam
addresses: [ "10.130.63.3/24" ]
mtu: 9000
version: 2
==
And here is the result after the `netplan apply`
===
# netstat -in
Kernel Interface table
Iface MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR
Flg
bond-cor 9000 19448696 0 0 0 6858767 0 1 0
BMmRU
bond-man 1500 7981199 0 1 0 1755800 0 2 0
BMmRU
bond-oam 9000 6236232 0 0 0 4488877 0 1 0
BMmU
ens10f0 9000 3961100 0 0 0 2271891 0 0 0
BMsU
ens10f1 9000 2288169 0 0 0 2218120 0 0 0
BMsU
ens10f2 1500 2506083 0 0 0 1226075 0 0 0
BMsRU
ens10f3 1500 5475116 0 0 0529725 0 0 0
BMsRU
ens1f09000 9513761 0 0 0 3970465 0 0 0
BMsRU
ens1f19000 9934935 0 0 0 2888302 0 0 0
BMsRU
lo 6553621336 0 0 0
[Touch-packages] [Bug 1905285] [NEW] socket-activated sshd breaks on concurrent connections
Public bug reported:
This is mostly the same issue as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=934663.
With the default configuration of openssh-server and systemd, sshd will
complain and crash when multiple connections are made and terminated in
a quick succession, e.g. with `ssh-keyscan`. It results in the following
errors in /var/log/auth.log:
```
Nov 22 20:53:34 {host} sshd[14567]: Unable to negotiate with {client} port
41460: no matching host key type found. Their offer:
sk-ecdsa-sha2-nistp...@openssh.com [preauth]
Nov 22 20:53:34 {host} sshd[14570]: fatal: chroot("/run/sshd"): No such file or
directory [preauth]
Nov 22 20:53:34 {host} sshd[14569]: fatal: chroot("/run/sshd"): No such file or
directory [preauth]
Nov 22 20:53:34 {host} sshd[14568]: fatal: chroot("/run/sshd"): No such file or
directory [preauth]
Nov 22 20:53:34 {host} sshd[14566]: fatal: chroot("/run/sshd"): No such file or
directory [preauth]
Nov 22 20:53:47 {host} sshd[14584]: Connection closed by {client} port 59312
[preauth]
Nov 22 20:53:47 {host} sshd[14586]: fatal: chroot("/run/sshd"): No such file or
directory [preauth]
Nov 22 20:53:48 {host} sshd[14585]: fatal: chroot("/run/sshd"): No such file or
directory [preauth]
```
as well as e.g. missing responses in ssh-keyscan:
```
$ ssh-keyscan -vvv {host}
debug2: fd 3 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 2
debug2: fd 4 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 4
debug2: fd 5 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 8
debug2: fd 6 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 32
debug2: fd 7 setting O_NONBLOCK
debug3: conalloc: oname {host} kt 64
debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.1 pat OpenSSH* compat 0x0400
# {host}:22 SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.1
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms:
curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256
debug2: host key algorithms: sk-ecdsa-sha2-nistp...@openssh.com
debug2: ciphers ctos:
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
debug2: ciphers stoc:
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
debug2: MACs ctos:
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc:
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,z...@openssh.com
debug2: compression stoc: none,z...@openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms:
curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms:
rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos:
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
debug2: ciphers stoc:
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
debug2: MACs ctos:
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc:
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,z...@openssh.com
debug2: compression stoc: none,z...@openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: (no match)
debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.1 pat OpenSSH* compat 0x0400
# {host}:22 SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.1
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.1 pat OpenSSH* compat 0x0400
# {host}:22 SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.1
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT
[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot
I also have this Bug on "Raspbian GNU/Linux 10 (buster)". I solved it with the following changes: -Before=network.target +After=network.target -ExecStart=/lib/ufw/ufw-init start quiet +ExecStart=/usr/sbin/ufw --force enable -ExecStop=/lib/ufw/ufw-init stop +ExecStop=/usr/sbin/ufw --force disable I had to change the start and stop commands, without it sometimes doesn't work. I Tested this changes with 25 reboots without any problems. @Maintainers: Please publish this (or another) fix as soon as possible in the repositories because this is a major security vulnerability. I also suggest to request a CVE number. Best regards Fabian Fröhlich -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot Status in ufw: Invalid Status in ufw package in Ubuntu: Invalid Status in ufw source package in Xenial: Invalid Status in ufw source package in Bionic: Invalid Status in ufw source package in Cosmic: Invalid Status in ufw source package in Disco: Invalid Bug description: Whenever I boot into 17.10 ufw is always inactive, even though /etc/ufw/ufw.conf has this: # Set to yes to start on boot. If setting this remotely, be sure to add a rule # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp' ENABLED=yes ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ufw 0.35-5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 13:56:40 2017 InstallationDate: Installed on 2015-04-01 (936 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170 To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+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 1904549] Re: MTU is not set on vlan interface
Hello,
I don't need it on bond-manlan for sure (MTU 1500 on this one and its VLANs),
but I read in several place that setting MTU on the bond would also set it on
interface members.
And that indeed worked correctly.
As I said, I think the issue is definitely more in the udevd/networkd
part (remind me of the azure issue seen in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902960) because
the /run/systemd/network files were correct after the netplan apply.
--
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/1904549
Title:
MTU is not set on vlan interface
Status in netplan:
New
Status in netplan.io package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
Hello,
Upon changing the following configuration, adding the MTU lines, I
ended up with the VLAN interfaces still in MTU 1500 after a `netplan
generate && netplan apply`
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
# uname -a
Linux il3-fw2 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
# dpkg -l netplan.io
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionArchitecture Description
+++-==-==--===
ii netplan.io 0.100-0ubuntu4~20.04.2 amd64YAML network
configuration abstraction for various backends
==
# This is the network config written by 'subiquity'
network:
ethernets:
ens10f0: {}
ens10f1: {}
ens10f2: {}
ens10f3: {}
ens1f0: {}
ens1f1: {}
bonds:
bond-oam:
interfaces: [ens10f0, ens10f1]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
mtu: 9000
bond-manlan:
interfaces: [ens10f2, ens10f3]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
bond-core:
interfaces: [ens1f0, ens1f1]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
mtu: 9000
vlans:
vlan3001:
id: 3001
link: bond-manlan
addresses: [ "10.130.1.3/24" ]
vlan3002:
id: 3002
link: bond-manlan
addresses: [ "10.130.2.3/24" ]
vlan3003:
id: 3003
link: bond-manlan
addresses: [ "10.130.3.3/24" ]
vlan3054:
id: 3054
link: bond-core
addresses: [ "10.130.56.3/24" ]
mtu: 9000
vlan3065:
id: 3065
link: bond-oam
addresses: [ "10.130.63.3/24" ]
mtu: 9000
version: 2
==
And here is the result after the `netplan apply`
===
# netstat -in
Kernel Interface table
Iface MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR
Flg
bond-cor 9000 19448696 0 0 0 6858767 0 1 0
BMmRU
bond-man 1500 7981199 0 1 0 1755800 0 2 0
BMmRU
bond-oam 9000 6236232 0 0 0 4488877 0 1 0
BMmU
ens10f0 9000 3961100 0 0 0 2271891 0 0 0
BMsU
ens10f1 9000 2288169 0 0 0 2218120 0 0 0
BMsU
ens10f2 1500 2506083 0 0 0 1226075 0 0 0
BMsRU
ens10f3 1500 5475116 0 0 0529725 0 0 0
BMsRU
ens1f09000 9513761 0 0 0 3970465 0 0 0
BMsRU
ens1f19000 9934935 0 0 0 2888302 0
[Touch-packages] [Bug 1901609] Re: signond causes qprocess crash
** Description changed: - I'm reporting this bug upstream from where I found it, since I've - learned that the signond package in KDE Neon is sourced from Ubuntu - focal. + [Impact] + + Without the patch users are unable to add google accounts because signond crashes. + This prevents users from using KDE's online accounts feature for google. + The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. + + [Test Case] + + - in a plasma session + - install kio-gdrive + - run `systemsettings5 kcm_kaccounts` + - add a new account + - click on google + - wait for login window to appear + - signond shouldn't be crashing + + [Where problems could occur] + + Cannot think of any. It simply adds type info to the objects. Also + upstream has rtti disabled for months and I'm not aware of any problems. + + [Other Info] + + This is a fairly grave issue as far as user experience is concerned. + + + + + + I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) - Expected behaviour: + Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. - Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 ** Also affects: signon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: signon (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: signon (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: New Status in signon source package in Focal: New Status in signon source package in Groovy: New Status in signon source package in Hirsute: New Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to:
[Touch-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive
The fix is quite offtopic, but for this special case it should be a solution: the date of the pictures should be also preserved in the EXIF-Data. You can read the exif-data of the files and set the timestamp from this data. I used another tool under windows for this so far, but exiftool should do the job: Excerpt from the help-message: exiftool "-FileModifyDatehttps://bugs.launchpad.net/bugs/1872504 Title: date modified is wrong for files on an exfat formatted drive Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: When using exfat formatted drives (e.g. my camera card) with focal fossa any access causes the date modified to be set, even when it would not normally be set, and it is set a month into the future. Installing exfat-fuse and exfat-utils results in the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 17:27:30 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
what is release version fr this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Triaged Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Fix Committed Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed
[Touch-packages] [Bug 1905245] Re: "Failed to parse bus message: Invalid argument" with Linux 5.8
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1905245 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/1905245 Title: "Failed to parse bus message: Invalid argument" with Linux 5.8 Status in systemd package in Ubuntu: New Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905245/+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 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu5.1 --- alsa-ucm-conf (1.2.2-1ubuntu5.1) groovy; urgency=medium * d/p/0001-sof-hda-dsp-add-initial-kcontrol-values.patch * d/p/0002-sof-hda-dsp-make-the-boot-init-optional-for-all-cont.patch * d/p/0003-sof-hda-dsp-Set-Master-Playback-Switch-on-in-the-Boo.patch * d/p/0004-sof-hda-dsp-Increase-the-speaker-output-volume-in-th.patch Unmute the master playback switch and increase the init output volume, otherwise the playback will be muted after freshly install the OS if the machine uses ucm to configure the audio mixers, and the init playback output volume is too low after freshly install the OS. (LP: #1901922) -- Hui Wang Mon, 09 Nov 2020 03:59:02 + ** Changed in: alsa-lib (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in ALSA Libraries: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago)
[Touch-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu2.2 --- alsa-lib (1.2.2-2.1ubuntu2.2) focal; urgency=medium * d/p/0001-ucm-handle-correctly-Linked-configuration.patch - If the sound card is Linked in the ucm, don't return error in the check_empty_configuration(). So far the AMD Ryzen machines with acp sound card need this fix, otherwise the pulseaudio will fail to load ucm on those machines and the whole audio can't work. (LP: #1901922) -- Hui Wang Mon, 09 Nov 2020 14:53:11 +0800 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in ALSA Libraries: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag:
[Touch-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
This bug was fixed in the package alsa-lib - 1.2.3.2-1ubuntu3.1 --- alsa-lib (1.2.3.2-1ubuntu3.1) groovy; urgency=medium * d/p/0001-ucm-handle-correctly-Linked-configuration.patch - If the sound card is Linked in the ucm, don't return error in the check_empty_configuration(). So far the AMD Ryzen machines with acp sound card need this fix, otherwise the pulseaudio will fail to load ucm on those machines and the whole audio can't work. (LP: #1901922) -- Hui Wang Mon, 09 Nov 2020 06:26:27 + ** Changed in: alsa-lib (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in ALSA Libraries: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No
[Touch-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.5 --- alsa-ucm-conf (1.2.2-1ubuntu0.5) focal; urgency=medium * d/p/0001-sof-hda-dsp-add-initial-kcontrol-values.patch * d/p/0002-sof-hda-dsp-make-the-boot-init-optional-for-all-cont.patch * d/p/0003-sof-hda-dsp-Set-Master-Playback-Switch-on-in-the-Boo.patch * d/p/0004-sof-hda-dsp-Increase-the-speaker-output-volume-in-th.patch Unmute the master playback switch and increase the init output volume, otherwise, the playback will be muted after freshly install the OS if the machine uses ucm to configure the audio mixers, and the init playback output volume is too low after freshly install the OS. (LP: #1901922) -- Hui Wang Mon, 09 Nov 2020 12:06:50 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in ALSA Libraries: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days
[Touch-packages] [Bug 1901922] Update Released
The verification of the Stable Release Update for alsa-lib 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 alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in ALSA Libraries: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO
[Touch-packages] [Bug 1904549] Re: MTU is not set on vlan interface
this could be udevd/networkd bug which both fiddle with mtu.
--
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/1904549
Title:
MTU is not set on vlan interface
Status in netplan:
New
Status in netplan.io package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
Hello,
Upon changing the following configuration, adding the MTU lines, I
ended up with the VLAN interfaces still in MTU 1500 after a `netplan
generate && netplan apply`
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
# uname -a
Linux il3-fw2 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
# dpkg -l netplan.io
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionArchitecture Description
+++-==-==--===
ii netplan.io 0.100-0ubuntu4~20.04.2 amd64YAML network
configuration abstraction for various backends
==
# This is the network config written by 'subiquity'
network:
ethernets:
ens10f0: {}
ens10f1: {}
ens10f2: {}
ens10f3: {}
ens1f0: {}
ens1f1: {}
bonds:
bond-oam:
interfaces: [ens10f0, ens10f1]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
mtu: 9000
bond-manlan:
interfaces: [ens10f2, ens10f3]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
bond-core:
interfaces: [ens1f0, ens1f1]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
mtu: 9000
vlans:
vlan3001:
id: 3001
link: bond-manlan
addresses: [ "10.130.1.3/24" ]
vlan3002:
id: 3002
link: bond-manlan
addresses: [ "10.130.2.3/24" ]
vlan3003:
id: 3003
link: bond-manlan
addresses: [ "10.130.3.3/24" ]
vlan3054:
id: 3054
link: bond-core
addresses: [ "10.130.56.3/24" ]
mtu: 9000
vlan3065:
id: 3065
link: bond-oam
addresses: [ "10.130.63.3/24" ]
mtu: 9000
version: 2
==
And here is the result after the `netplan apply`
===
# netstat -in
Kernel Interface table
Iface MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR
Flg
bond-cor 9000 19448696 0 0 0 6858767 0 1 0
BMmRU
bond-man 1500 7981199 0 1 0 1755800 0 2 0
BMmRU
bond-oam 9000 6236232 0 0 0 4488877 0 1 0
BMmU
ens10f0 9000 3961100 0 0 0 2271891 0 0 0
BMsU
ens10f1 9000 2288169 0 0 0 2218120 0 0 0
BMsU
ens10f2 1500 2506083 0 0 0 1226075 0 0 0
BMsRU
ens10f3 1500 5475116 0 0 0529725 0 0 0
BMsRU
ens1f09000 9513761 0 0 0 3970465 0 0 0
BMsRU
ens1f19000 9934935 0 0 0 2888302 0 0 0
BMsRU
lo 6553621336 0 0 0 21336 0 0 0
LRU
vlan3001 1500 1952436 0 0 0
[Touch-packages] [Bug 1904549] Re: MTU is not set on vlan interface
I wonder if you need more mtu settings on:
* ens10f2
* ens10f3
* bond-manlan
I don't think that MTU is allowed to be higher on a vlan, than on bond-
man, than on physical interfaces. Why did you not set mtu: 9000 on bond-
manlan?
however that does not explain how come the vlans on top of bond-core / bond-oam
are not 9000.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/1904549
Title:
MTU is not set on vlan interface
Status in netplan:
New
Status in netplan.io package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
Hello,
Upon changing the following configuration, adding the MTU lines, I
ended up with the VLAN interfaces still in MTU 1500 after a `netplan
generate && netplan apply`
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
# uname -a
Linux il3-fw2 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
# dpkg -l netplan.io
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionArchitecture Description
+++-==-==--===
ii netplan.io 0.100-0ubuntu4~20.04.2 amd64YAML network
configuration abstraction for various backends
==
# This is the network config written by 'subiquity'
network:
ethernets:
ens10f0: {}
ens10f1: {}
ens10f2: {}
ens10f3: {}
ens1f0: {}
ens1f1: {}
bonds:
bond-oam:
interfaces: [ens10f0, ens10f1]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
mtu: 9000
bond-manlan:
interfaces: [ens10f2, ens10f3]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
bond-core:
interfaces: [ens1f0, ens1f1]
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 100
lacp-rate: fast
mtu: 9000
vlans:
vlan3001:
id: 3001
link: bond-manlan
addresses: [ "10.130.1.3/24" ]
vlan3002:
id: 3002
link: bond-manlan
addresses: [ "10.130.2.3/24" ]
vlan3003:
id: 3003
link: bond-manlan
addresses: [ "10.130.3.3/24" ]
vlan3054:
id: 3054
link: bond-core
addresses: [ "10.130.56.3/24" ]
mtu: 9000
vlan3065:
id: 3065
link: bond-oam
addresses: [ "10.130.63.3/24" ]
mtu: 9000
version: 2
==
And here is the result after the `netplan apply`
===
# netstat -in
Kernel Interface table
Iface MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR
Flg
bond-cor 9000 19448696 0 0 0 6858767 0 1 0
BMmRU
bond-man 1500 7981199 0 1 0 1755800 0 2 0
BMmRU
bond-oam 9000 6236232 0 0 0 4488877 0 1 0
BMmU
ens10f0 9000 3961100 0 0 0 2271891 0 0 0
BMsU
ens10f1 9000 2288169 0 0 0 2218120 0 0 0
BMsU
ens10f2 1500 2506083 0 0 0 1226075 0 0 0
BMsRU
ens10f3 1500 5475116 0 0 0529725 0 0 0
BMsRU
ens1f09000 9513761 0 0 0 3970465 0 0 0
BMsRU
ens1f19000 9934935 0 0 0
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
This bug was fixed in the package bluez - 5.55-0ubuntu1.1 --- bluez (5.55-0ubuntu1.1) groovy; urgency=medium * Added patches from the Raspberry Pi Foundation - d/p/raspi-bcm43xx-load-firmware.patch - d/p/raspi-bcm43xx-3wire.patch - d/p/raspi-cypress-305-bdaddr.patch * These patches fix Bluetooth operation on the Pi 400 (LP: #1903048) -- Dave Jones Thu, 05 Nov 2020 13:39:07 + ** Changed in: bluez (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1903048] Update Released
The verification of the Stable Release Update for bluez 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Releasing this a day earlier to get the update shipped to users ASAP. -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1303316] Re: Digital S/PDIF output is not present in 5.1 mode
Missing option is SPDIF Digital 5.1 -- 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/1303316 Title: Digital S/PDIF output is not present in 5.1 mode Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have the sound connected through digital S / PDIF Sound works properly selecting stereo, but can not get it to work using 5.1 When I select stereo sound, appears on the tab below to phonon spdif output option. When I select Output 5.1, that option does not appear. I imagine the error will also occur selecting 7.1 Deputy screenshots. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: phonon 4:4.7.0really4.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Apr 6 13:12:42 2014 InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: phonon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303316/+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 1303316] Re: Digital S/PDIF output is not present in 5.1 mode
The same mistake in gorilla. ** Attachment added: "4.jpeg" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303316/+attachment/5437227/+files/4.jpeg -- 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/1303316 Title: Digital S/PDIF output is not present in 5.1 mode Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have the sound connected through digital S / PDIF Sound works properly selecting stereo, but can not get it to work using 5.1 When I select stereo sound, appears on the tab below to phonon spdif output option. When I select Output 5.1, that option does not appear. I imagine the error will also occur selecting 7.1 Deputy screenshots. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: phonon 4:4.7.0really4.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Apr 6 13:12:42 2014 InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: phonon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303316/+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 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied
However, the service still couldn't create a PID-file after a reboot. So
I tweaked a little bit longer.
It turns out that the isc-dhcp-server is started before the temporary
filesystem "/run".
The lines "Wants=local-fs.target", "After=local-fs.target" and "sleep 3 ; \"
solves that.
Security by apparmor requires the creation of the PID-file in
"/{,var/}run/{,dhcp-server/}dhcpd{,6}.pid rw,". The lines
"if [ ! -d /run/dhcp-server ]; then mkdir -p /run/dhcp-server; fi; \"
"chown root:dhcpd /run/dhcp-server; \"
"chmod ug=rwx,o=rx /run/dhcp-server; \"
"sleep 1; \"
enables this.
This tweaking resulted in the following "/etc/systemd/system/isc-dhcp-
server.services" file.
[Unit]
Description=ISC DHCP IPv4 server
Documentation=man:dhcpd(8)
Wants=network-online.target
Wants=local-fs.target
After=network-online.target
After=local-fs.target
After=time-sync.target
ConditionPathExists=/etc/default/isc-dhcp-server
ConditionPathIsMountPoint=/run
ConditionPathExists=|/etc/ltsp/dhcpd.conf
ConditionPathExists=|/etc/dhcp/dhcpd.conf
[Service]
EnvironmentFile=/etc/default/isc-dhcp-server
RuntimeDirectory=dhcp-server
# The leases files need to be root:dhcpd even when dropping privileges
ExecStart=/bin/sh -ec '\
sleep 3 ; \
CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \
if [ ! -d /run/dhcp-server ]; then mkdir -p /run/dhcp-server; fi; \
chown root:dhcpd /run/dhcp-server; \
chmod ug=rwx,o=rx /run/dhcp-server; \
sleep 1; \
if [ ! "$DHCPDv4_PID" ] ; then DHCPDv4_PID=/run/dhcp-server/dhcpd.pid; fi; \
[ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \
chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \
chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \
exec dhcpd -user dhcpd -group dhcpd -f -4 -pf $DHCPDv4_PID -cf $CONFIG_FILE
$INTERFACESv4'
[Install]
WantedBy=multi-user.target
==
I hope this helps. Any suggestion to improve this service-file is
appreciated :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1448657
Title:
isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid:
Permission denied
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
Just upgraded from 14-10 to 15-04, and now see the following in
syslog:
Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400
audit(1430045408.725:8): apparmor="DENIED" operation="capable"
profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1 capname="dac_ove
rride"
Apr 26 10:50:08 server sh[8619]: Can't create PID file
/run/dhcp-server/dhcpd.pid: Permission denied.
Description:Ubuntu 15.04
Release:15.04
isc-dhcp-server:
Installed: 4.3.1-5ubuntu2
--- 8x -
# cat /etc/default/isc-dhcp-server
# Defaults for isc-dhcp-server initscript
# sourced by /etc/init.d/isc-dhcp-server
# installed at /etc/default/isc-dhcp-server by the maintainer scripts
#
# This is a POSIX shell fragment
#
# Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
#DHCPD_CONF=/etc/dhcp/dhcpd.conf
# Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
#DHCPD_PID=/var/run/dhcpd.pid
# Additional options to start dhcpd with.
# Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
#OPTIONS=""
# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACES=""
--- 8x -
# ls -la /var/run
lrwxrwxrwx 1 root root 4 Oct 24 2013 /var/run -> /run
# ls -la /run/dhcp-server/
total 0
drwxr-xr-x 2 dhcpd dhcpd 40 Apr 26 10:59 .
drwxr-xr-x 34 root root 1060 Apr 26 11:33 ..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+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 1905080] Re: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV
Reassigning to the kernel since the upstream PulseAudio bug was closed as such. ** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1032 Importance: Unknown Status: Unknown ** Package changed: pulseaudio (Ubuntu) => linux (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/1905080 Title: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV Status in PulseAudio: Unknown Status in linux package in Ubuntu: Incomplete Bug description: Before the upgrade the HDMI 4 digital stereo output was chosen automatically for my nvidia GF card and was usable by the players immediately after turning the TV on. After the upgrade I have to switch the profile from Disabled to HDMI4 each time I turn the TV on. It doesn't get stored properly. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1905080/+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 1905261] [NEW] Openssl ignores order from /etc/nsswitch.conf
Public bug reported:
I'm issuing command like below:
openssl s_client -connect subdomain.domain.example.com
I have following nsswitch.confg defined:
'''
$ cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat systemd
group: compat systemd
shadow: compat
hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return]
dns myhostname
networks: files
protocols: db files
services: db files
ethers: db files
rpc:db files
netgroup: nis
'''
For host resolution /etc/hosts file should take precedence. But it doesn't work
that way and when I have some unresolvable name it tries to connect to DNS
ignoring local hosts file. The order can be clearly visible in strace:
'''openat(AT_FDCWD, "/usr/lib/ssl/ct_log_list.cnf", O_RDONLY) = -1 ENOENT (No
such file or directory)
openat(AT_FDCWD, "/usr/lib/ssl/cert.pem", O_RDONLY) = -1 ENOENT (No such file
or directory)
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1
ENOENT (No such file or directory)
close(5)= 0
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1
ENOENT (No such file or directory)
close(5)= 0
openat(AT_FDCWD, "/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=560, ...}) = 0
read(5, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 560
read(5, "", 4096) = 0
close(5)= 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
openat(AT_FDCWD, "/etc/host.conf", O_RDONLY|O_CLOEXEC) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=93, ...}) = 0
read(5, "# The \"order\" line is only used "..., 4096) = 93
read(5, "", 4096) = 0
close(5)= 0
futex(0x7f3d2d2b5ba4, FUTEX_WAKE_PRIVATE, 2147483647) = 0
openat(AT_FDCWD, "/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
read(5, "# Generated by NetworkManager\nse"..., 4096) = 64
read(5, "", 4096) = 0
close(5)= 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=335124, ...}) = 0
mmap(NULL, 335124, PROT_READ, MAP_PRIVATE, 5, 0) = 0x7f3d2de05000
close(5)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libnss_files.so.2", O_RDONLY|O_CLOEXEC)
= 5
read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P#\0\0\0\0\0\0"..., 832)
= 832
fstat(5, {st_mode=S_IFREG|0644, st_size=47568, ...}) = 0
mmap(NULL, 2168632, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) =
0x7f3d2cab
mprotect(0x7f3d2cabb000, 2093056, PROT_NONE) = 0
mmap(0x7f3d2ccba000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0xa000) = 0x7f3d2ccba000
mmap(0x7f3d2ccbc000, 22328, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3d2ccbc000
close(5)= 0
mprotect(0x7f3d2ccba000, 4096, PROT_READ) = 0
munmap(0x7f3d2de05000, 335124) = 0
openat(AT_FDCWD, "/etc/hosts", O_RDONLY|O_CLOEXEC) = 5
'''
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: openssl 1.1.1-1ubuntu2.1~18.04.6
ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18
Uname: Linux 4.15.0-124-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
Date: Mon Nov 23 10:49:41 2020
InstallationDate: Installed on 2015-05-08 (2026 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=pl_PL.UTF-8
SHELL=/bin/bash
SourcePackage: openssl
UpgradeStatus: Upgraded to bionic on 2018-08-26 (819 days ago)
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1905261
Title:
Openssl ignores order from /etc/nsswitch.conf
Status in openssl package in Ubuntu:
New
Bug description:
I'm issuing command like below:
openssl s_client -connect subdomain.domain.example.com
I have following nsswitch.confg defined:
'''
$ cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages
[Touch-packages] [Bug 1905080] Re: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV
I started some investigation with the pulseaudio upstream and the issue is caused by the fact only the currently selected profile receives updates of the the plugged/available state since PA13 and that conflicts with the feature of switching the unavailable profiles away. They never get back from the Off state. -- 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/1905080 Title: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV Status in pulseaudio package in Ubuntu: Incomplete Bug description: Before the upgrade the HDMI 4 digital stereo output was chosen automatically for my nvidia GF card and was usable by the players immediately after turning the TV on. After the upgrade I have to switch the profile from Disabled to HDMI4 each time I turn the TV on. It doesn't get stored properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905080/+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 1905080] Re: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV
Hello. Like mentioned in #1905078, I don't have the apport package installed and don't plan to do so due to various reasons. Right now I'm working with PA downgraded from 1:13.99.1-1ubuntu3.7 to 1:11.1-1ubuntu7.10 that doesn't exhibit such problems. -- 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/1905080 Title: After upgrading from Ubuntu 18 to 20 pulseaudio starts with HDMI output disabled and doesn't turn on when I turn on the TV Status in pulseaudio package in Ubuntu: Incomplete Bug description: Before the upgrade the HDMI 4 digital stereo output was chosen automatically for my nvidia GF card and was usable by the players immediately after turning the TV on. After the upgrade I have to switch the profile from Disabled to HDMI4 each time I turn the TV on. It doesn't get stored properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905080/+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 1905085] Re: Error when I type sudo in the terminal.Also I get an error when I am requested to authentycate do not show the line for the password and instead shows an error messa
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Package changed: evince (Ubuntu) => sudo (Ubuntu) ** Changed in: sudo (Ubuntu) Importance: Undecided => Low ** Changed in: sudo (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1905085 Title: Error when I type sudo in the terminal.Also I get an error when I am requested to authentycate do not show the line for the password and instead shows an error message Status in sudo package in Ubuntu: Invalid Bug description: mt@mt-MS-7728:/usr/lib/sudo$ sudo chmod -R u=rw sudoers.so sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins mt@mt-MS-7728:/usr/lib/sudo$ chmod -R u=rw sudoers.so chmod: changing permissions of 'sudoers.so': Operation not permitted mt@mt-MS-7728:/usr/lib/sudo$ pkexec chmod go-w /usr/lib/sudo/sudoers.so Error executing command as another user: Request dismissed mt@mt-MS-7728:/usr/lib/sudo$ mount -o remount,rw / mount: only root can use "--options" option mt@mt-MS-7728:/usr/lib/sudo$ mount --options remount,rw / mount: only root can use "--options" option mt@mt-MS-7728:/usr/lib/sudo$ chmod 644 /usr/lib/sudo/sudoers.so chmod: changing permissions of '/usr/lib/sudo/sudoers.so': Operation not permitted mt@mt-MS-7728:/usr/lib/sudo$ chown root:root /usr/lib/sudo/sudoers.so chown: changing ownership of '/usr/lib/sudo/sudoers.so': Operation not permitted mt@mt-MS-7728:/usr/lib/sudo$ cd .. mt@mt-MS-7728:/usr/lib$ cd policykit-1 mt@mt-MS-7728:/usr/lib/policykit-1$ ls -l total 32 -rwxrwxrwx 1 root root 14328 mar 27 2019 polkit-agent-helper-1 -rwxrwxrwx 1 root root 14552 mar 27 2019 polkitd mt@mt-MS-7728:/usr/lib/policykit-1$ sudo chmod -R u=rw polkit-agent-helper-1 sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins mt@mt-MS-7728:/usr/lib/policykit-1$ chmod -R u=rw polkit-agent-helper-1 chmod: changing permissions of 'polkit-agent-helper-1': Operation not permitted mt@mt-MS-7728:/usr/lib/policykit-1$ Ubuntu 18.04.5 LTSmt@mt-MS-7728:/$ xprop WM_CLASS WM_CLASS(STRING) = "gnome-terminal-server", "Gnome-terminal" mt@mt-MS-7728:/$ locate -b "\gnome-terminal-server" /usr/lib/gnome-terminal/gnome-terminal-server mt@mt-MS-7728:/ I expected it to work normal giving me root access to the commands. It gave me an error message that says"sudoers.so"must be writeable only by the user and actually it is set up to be read and write for all,that was my mistake when I ran a chmod 777 for the whole lib directory since then sudo does not work and now when I try to chmod without sudo it says,permission denied and when I try with sudo it gives me the error,so it is a circle I can not get out of.Another problem I have,probably,from the same origin,is the authentication label that do not show the line where the password should be inserted and instead it shows an error message that says something about the /usr/lib/policykit being restored to its original state.Well this is all I have to say ,for the moment. Thanks.Please see if you can help me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 20:48:22 2020 InstallationDate: Installed on 2020-11-16 (4 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1905085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1905106] Re: wifi cannot find any network
Thank you for your bug report, that seems rather a driver or kernel issue. Could you give some details on the hardware configuration you are using and the wifi device? ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1905106 Title: wifi cannot find any network Status in linux package in Ubuntu: Incomplete Bug description: I tried to use this command to try to solve the problem, but it didn't work: sudo service network manager and tried to update the system and restart the machine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 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.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 21:07:52 2020 InstallationDate: Installed on 2020-11-18 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.42.129 dev usb0 proto dhcp metric 100 169.254.0.0/16 dev usb0 scope link metric 1000 192.168.42.0/24 dev usb0 proto kernel scope link src 192.168.42.163 metric 100 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905106/+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 1905085] [NEW] Error when I type sudo in the terminal.Also I get an error when I am requested to authentycate do not show the line for the password and instead shows an error mes
You have been subscribed to a public bug: mt@mt-MS-7728:/usr/lib/sudo$ sudo chmod -R u=rw sudoers.so sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins mt@mt-MS-7728:/usr/lib/sudo$ chmod -R u=rw sudoers.so chmod: changing permissions of 'sudoers.so': Operation not permitted mt@mt-MS-7728:/usr/lib/sudo$ pkexec chmod go-w /usr/lib/sudo/sudoers.so Error executing command as another user: Request dismissed mt@mt-MS-7728:/usr/lib/sudo$ mount -o remount,rw / mount: only root can use "--options" option mt@mt-MS-7728:/usr/lib/sudo$ mount --options remount,rw / mount: only root can use "--options" option mt@mt-MS-7728:/usr/lib/sudo$ chmod 644 /usr/lib/sudo/sudoers.so chmod: changing permissions of '/usr/lib/sudo/sudoers.so': Operation not permitted mt@mt-MS-7728:/usr/lib/sudo$ chown root:root /usr/lib/sudo/sudoers.so chown: changing ownership of '/usr/lib/sudo/sudoers.so': Operation not permitted mt@mt-MS-7728:/usr/lib/sudo$ cd .. mt@mt-MS-7728:/usr/lib$ cd policykit-1 mt@mt-MS-7728:/usr/lib/policykit-1$ ls -l total 32 -rwxrwxrwx 1 root root 14328 mar 27 2019 polkit-agent-helper-1 -rwxrwxrwx 1 root root 14552 mar 27 2019 polkitd mt@mt-MS-7728:/usr/lib/policykit-1$ sudo chmod -R u=rw polkit-agent-helper-1 sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner sudo: fatal error, unable to load plugins mt@mt-MS-7728:/usr/lib/policykit-1$ chmod -R u=rw polkit-agent-helper-1 chmod: changing permissions of 'polkit-agent-helper-1': Operation not permitted mt@mt-MS-7728:/usr/lib/policykit-1$ Ubuntu 18.04.5 LTSmt@mt-MS-7728:/$ xprop WM_CLASS WM_CLASS(STRING) = "gnome-terminal-server", "Gnome-terminal" mt@mt-MS-7728:/$ locate -b "\gnome-terminal-server" /usr/lib/gnome-terminal/gnome-terminal-server mt@mt-MS-7728:/ I expected it to work normal giving me root access to the commands. It gave me an error message that says"sudoers.so"must be writeable only by the user and actually it is set up to be read and write for all,that was my mistake when I ran a chmod 777 for the whole lib directory since then sudo does not work and now when I try to chmod without sudo it says,permission denied and when I try with sudo it gives me the error,so it is a circle I can not get out of.Another problem I have,probably,from the same origin,is the authentication label that do not show the line where the password should be inserted and instead it shows an error message that says something about the /usr/lib/policykit being restored to its original state.Well this is all I have to say ,for the moment. Thanks.Please see if you can help me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 20:48:22 2020 InstallationDate: Installed on 2020-11-16 (4 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sudo (Ubuntu) Importance: Low Status: Invalid ** Tags: amd64 apport-bug bionic -- Error when I type sudo in the terminal.Also I get an error when I am requested to authentycate do not show the line for the password and instead shows an error message https://bugs.launchpad.net/bugs/1905085 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo 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 1903966] Re: Loading keymaps via udev is not reliable, please use upstream rule
https://bugs.launchpad.net/ubuntu/+source/v4l-utils/1.20.0-2 ** Changed in: v4l-utils (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1903966 Title: Loading keymaps via udev is not reliable, please use upstream rule Status in v4l-utils package in Ubuntu: Fix Committed Status in v4l-utils package in Debian: Unknown Bug description: Dear Maintainer, the udev rule installed from debian/ir-keytable.udev is not guaranteed to be run at the appropriate moment during bootup which can cause the remote not to be configured according to the settings in /etc/rc_maps.cfg. This seems to occur more often with newer kernel versions. Please use the upstream version (https://git.linuxtv.org/v4l-utils.git/tree/utils/keytable/70-infrared.rules) instead. This commit message explains the need for this change: https://git.linuxtv.org/v4l-utils.git/commit/utils/keytable/70-infrared.rules?id=e440918467868a5f3e7f73f54ef2cbd85d68f3f1 Description:Ubuntu 20.04.1 LTS Release:20.04 ir-keytable version: 1.18.0-2build1 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1903966/+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] [NEW] "Failed to parse bus message: Invalid argument" with Linux 5.8
Public bug reported: 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. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1905245 Title: "Failed to parse bus message: Invalid argument" with Linux 5.8 Status in systemd package in Ubuntu: New Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905245/+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
