[Touch-packages] [Bug 2040108] Re: error "contains an invalid sample specification."
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/2040108 Title: error "contains an invalid sample specification." Status in pulseaudio package in Ubuntu: Expired Bug description: After upgrade network audio stop working. On the client side in log i see: "CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series' contains an invalid sample specification." Microphone sink work, but playback not. I tried as client ubuntu 23.04 and 23.10, so I suppose issue in zeroconf-publish Just specifying env PULSE_SERVER play sound fine. Also will be great if zeroconf-publish can filter what to export, at least disable microphone. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio-module-zeroconf 1:16.1+dfsg1-2ubuntu4 Uname: Linux 6.2.16-060216-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vova 1822 F wireplumber /dev/snd/controlC2: vova 1822 F wireplumber /dev/snd/controlC1: vova 1822 F wireplumber /dev/snd/seq:vova 1820 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 22 17:04:30 2023 InstallationDate: Installed on 2023-04-01 (204 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230401) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to mantic on 2023-10-15 (7 days ago) dmi.bios.date: 08/09/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FEb dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS ELITE V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFEb:bd08/09/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSELITEV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSELITEV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS ELITE V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2040108/+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 2043929] Re: package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: подпроцесс из пакета initramfs-tools установлен сценарий post-installation возвратил код ошибки 1
[Expired for initramfs-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2043929 Title: package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: подпроцесс из пакета initramfs-tools установлен сценарий post- installation возвратил код ошибки 1 Status in initramfs-tools package in Ubuntu: Expired Bug description: relevant dpkg terminal log: update-initramfs: Generating /boot/initrd.img-5.19.0-38-generic /usr/sbin/mkinitramfs: 494: zstd: Exec format error E: mkinitramfs failure zstd -q -1 -T0 126 update-initramfs: failed for /boot/initrd.img-5.19.0-38-generic with 1. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Nov 19 19:59:30 2023 DpkgHistoryLog: Start-Date: 2023-11-19 19:58:49 Commandline: /usr/bin/unattended-upgrade Upgrade: avahi-utils:amd64 (0.8-5ubuntu5, 0.8-5ubuntu5.1), libavahi-common-data:amd64 (0.8-5ubuntu5, 0.8-5ubuntu5.1), libavahi-common-data:i386 (0.8-5ubuntu5, 0.8-5ubuntu5.1), libavahi-core7:amd64 (0.8-5ubuntu5, 0.8-5ubuntu5.1), avahi-daemon:amd64 (0.8-5ubuntu5, 0.8-5ubuntu5.1), libavahi-ui-gtk3-0:amd64 (0.8-5ubuntu5, 0.8-5ubuntu5.1), libavahi-common3:amd64 (0.8-5ubuntu5, 0.8-5ubuntu5.1), libavahi-common3:i386 (0.8-5ubuntu5, 0.8-5ubuntu5.1), libavahi-glib1:amd64 (0.8-5ubuntu5, 0.8-5ubuntu5.1), libavahi-client3:amd64 (0.8-5ubuntu5, 0.8-5ubuntu5.1), libavahi-client3:i386 (0.8-5ubuntu5, 0.8-5ubuntu5.1) ErrorMessage: подпроцесс из пакета initramfs-tools установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2023-04-06 (227 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: подпроцесс из пакета initramfs-tools установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2043929/+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 2049960] [NEW] polkitd.postinst script refers to non-existent /usr/libexec/polkitd
Public bug reported: I am seeing this on Ubuntu noble with polkitd 123-3. After debootstrap'ing a minimal system, I run # apt-get install linux-generic which pulls in polkitd as a dependency. In the output, I see the following: Setting up polkitd (123-3) ... Creating group 'polkitd' with GID 994. Creating user 'polkitd' (polkit) with UID 994 and GID 994. Running in chroot, ignoring request. * Reloading system message bus config... Failed to open connection to "system" message bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory invoke-rc.d: initscript dbus, action "reload" failed. start-stop-daemon: unable to stat /usr/libexec/polkitd (No such file or directory) There is indeed no file there: # ls -l /usr/libexec/polkitd ls: cannot access '/usr/libexec/polkitd': No such file or directory The binary appears to be installed at /usr/lib/polkit-1/polkitd . ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2049960 Title: polkitd.postinst script refers to non-existent /usr/libexec/polkitd Status in policykit-1 package in Ubuntu: New Bug description: I am seeing this on Ubuntu noble with polkitd 123-3. After debootstrap'ing a minimal system, I run # apt-get install linux-generic which pulls in polkitd as a dependency. In the output, I see the following: Setting up polkitd (123-3) ... Creating group 'polkitd' with GID 994. Creating user 'polkitd' (polkit) with UID 994 and GID 994. Running in chroot, ignoring request. * Reloading system message bus config... Failed to open connection to "system" message bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory invoke-rc.d: initscript dbus, action "reload" failed. start-stop-daemon: unable to stat /usr/libexec/polkitd (No such file or directory) There is indeed no file there: # ls -l /usr/libexec/polkitd ls: cannot access '/usr/libexec/polkitd': No such file or directory The binary appears to be installed at /usr/lib/polkit-1/polkitd . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2049960/+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 2049318] Re: [SRU] free(): double free detected in tcache 2
Hello Jo, or anyone else affected, Accepted iptables into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iptables/1.8.7-1ubuntu5.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: iptables (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2049318 Title: [SRU] free(): double free detected in tcache 2 Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Jammy: Fix Committed Bug description: [ Impact ] iptables is unable to list the iptables rules or save the iptables rules if a nftables ruleset is defined which iptables does not recognize. [ Test Plan ] 1. Simple test plan based on upstream test case: sudo nft -f - < rules.txt * Convert the rule to nftables ruleset - sudo iptables-nft-restore < rules.txt * List the nftables ruleset - sudo nft list ruleset * Also confirm that iptables can list the old rule - sudo iptables -L * Now add another nftables rule (this rule is taken from upstream test case) sudo nft -f -
[Touch-packages] [Bug 2049958] [NEW] package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/bluetooth/obexd' before installing new version: Input/output
Public bug reported:
bug found during software update launched from bootable usb
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez-obexd 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckMismatches: ./casper/minimal.squashfs
CasperMD5CheckResult: fail
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
Date: Sat Jan 20 00:18:32 2024
DuplicateSignature:
package:bluez-obexd:5.68-0ubuntu1
Unpacking bluez-obexd (5.68-0ubuntu1.1) over (5.68-0ubuntu1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-MsVzUs/045-bluez-obexd_5.68-0ubuntu1.1_amd64.deb
(--unpack):
unable to make backup link of './usr/lib/bluetooth/obexd' before installing
new version: Input/output error
ErrorMessage: unable to make backup link of './usr/lib/bluetooth/obexd' before
installing new version: Input/output error
InterestingModules: rfcomm bnep btusb bluetooth
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent
layerfs-path=minimal.standard.live.squashfs --- quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.22.0ubuntu1
apt 2.7.3
SourcePackage: bluez
Title: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to
make backup link of './usr/lib/bluetooth/obexd' before installing new version:
Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2018
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 306
dmi.board.asset.tag: Default string
dmi.board.name: GL553VW
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.:bvr306:bd09/26/2018:br5.6:svnASUSTeKCOMPUTERINC.:pnGL553VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
dmi.product.family: GL
dmi.product.name: GL553VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: D0:57:7B:12:13:2F ACL MTU: 1021:5 SCO MTU: 96:6
UP RUNNING
RX bytes:1345 acl:0 sco:0 events:90 errors:0
TX bytes:3835 acl:0 sco:0 commands:90 errors:0
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package mantic need-duplicate-check
--
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/2049958
Title:
package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to
make backup link of './usr/lib/bluetooth/obexd' before installing new
version: Input/output error
Status in bluez package in Ubuntu:
New
Bug description:
bug found during software update launched from bootable usb
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez-obexd 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckMismatches: ./casper/minimal.squashfs
CasperMD5CheckResult: fail
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
Date: Sat Jan 20 00:18:32 2024
DuplicateSignature:
package:bluez-obexd:5.68-0ubuntu1
Unpacking bluez-obexd (5.68-0ubuntu1.1) over (5.68-0ubuntu1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-MsVzUs/045-bluez-obexd_5.68-0ubuntu1.1_amd64.deb
(--unpack):
unable to make backup link of './usr/lib/bluetooth/obexd' before installing
new version: Input/output error
ErrorMessage: unable to make backup link of './usr/lib/bluetooth/obexd'
before installing new version: Input/output error
InterestingModules: rfcomm bnep btusb bluetooth
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent
layerfs-path=minimal.standard.live.squashfs --- quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.22.0ubuntu1
apt 2.7.3
SourcePackage: bluez
Title: package bluez-obexd 5.68-0ubuntu1 failed to
[Touch-packages] [Bug 2042587] Re: jammy's version breaks existing dhcp scripts with relay
Hello Timo, or anyone else affected, Accepted dnsmasq into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dnsmasq/2.86-1.1ubuntu0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: dnsmasq (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Fix Committed Bug description: [ Impact ] When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. This was fixed in 2.87, therefore making only jammy carry an affected package. [ Test Plan ] To easily test this on a single machine, a test script is being provided to setup networking and dnsmasq configuration. # Launch a jammy VM lxc launch ubuntu-daily:jammy j-dnsmasq-2042587 --vm # open a root shell in that VM. All subsequent commands must be executed as root in that VM lxc shell j-dnsmasq-2042587 # download test script wget https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5738174/+files/setup- and-server.sh # make it executable chmod +x setup-and-server.sh # install dnsmasq. Ignore the postinst error (because systemd-resolved is also running and there is a port conflict) apt update && apt install dnsmasq -y # run the setup script. It will configure things and start dnsmasq ready to be tested ./setup-and-server.sh # in another root session inside the vm (so run "lxc shell j-dnsmasq-2042587" in another terminal), run the proposed commands from the setup script (and press ctrl-c after the result is shown): No DHCP relay: ip netns exec client dhclient -d -v p2 The setup script should log an IP that is not a relay. For example: dnsmasq-dhcp: DHCPDISCOVER(p1) aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPOFFER(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587 ### IP = 192.168.47.150 ### With DHCP relay set to 192.168.47.9, IP should NOT be that address: ip netns exec client dhclient -d -v p2 -g 192.168.47.9 With the affected dnsmasq package, we will see an error: dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587 ### IP = 192.168.47.9 TEST FAILED ### The error is that the obtained IP is that of the dhcp relay (provided via the -g option). With the fixed dnsmasq package, "TEST FAILED" must not appear, and the IP should not be that of the provided dhcp relay. [ Where problems could occur ] If the fix is incorrect, it would mean the dhcp-script would get an incorrect IP again, or perhaps we could have crashes in dnsmasq when dealing with buffers and pointers if the dhcp-script option is in use. This fix was committed upstream a few months after the bug was introduced, so it took a while to be noticed. [ Other Info ] Not at this time. [ Original description ] When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The
[Touch-packages] [Bug 2045570] Re: dnsmasq crash when no servers in resolv.conf
Hello Alfred, or anyone else affected, Accepted dnsmasq into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dnsmasq/2.86-1.1ubuntu0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: dnsmasq (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2045570 Title: dnsmasq crash when no servers in resolv.conf Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Fix Committed Bug description: [ Impact ] dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the file is updated. When that happens and for some reason there were no "nameserver" declarations in the updated file, dnsmasq can crash. Here is a log of a reproducer: $ dig +short @127.0.0.1 ubuntu.com ;; communications error to 127.0.0.1#53: timed out ;; communications error to 127.0.0.1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ;; no servers could be reached We can see the startup, then when resolv.conf is read again and no nameservers were found, and the crash: Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: started, version 2.86 cachesize 150 Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: DNS service limited to local subnets Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: reading /etc/resolv.conf Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: using nameserver 10.0.100.1#53 Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: read /etc/hosts - 7 addresses Jan 03 13:57:13 j-dnsmasq-2045570 systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Jan 03 13:58:01 j-dnsmasq-2045570 dnsmasq[1507]: no servers found in /etc/resolv.conf, will retry Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with result 'core-dump'. dnsmasq has provisions for this situation, we can see that in the 13:58:01 message where it says it will retry, but due to this bug, it crashes instead. The problem was introduced[1] in version 2.86, and fixed in 2.87, so only jammy is affected. 1. https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=d290630d31f4517ab26392d00753d1397f9a4114;hp=d2ad5dc073aaacaf22b117f16106282a73586803 The commit message says: """ This problem was introduced in 2.86. """ And indeed, I wasn't able to crash 2.80 shipped in focal. [ Test Plan ] It might take a few tries to reproduce the bug, but here is the general outline. Also keep in mind that it's important to use a DNS name that isn't cached already by a previous query. # Create a jammy lxd container lxc launch ubuntu-daily:jammy j-dnsmasq-2045570 # Enter the container lxc shell j-dnsmasq-2045570 # From now on, all commands should be executed in the container. # Install dnsmasq, and disable systemd-resolved apt update && apt install -y dnsmasq # Disable systemd-resolved, and start dnsmasq systemctl disable --now systemd-resolved systemctl enable --now dnsmasq # In one terminal inside the container, watch the dnsmasq logs: journalctl -u dnsmasq.service -f # In another terminal, remove /etc/resolv.conf and create a new one, empty rm /etc/resolv.conf echo "nameserver 1.1.1.1" > /etc/resolv.conf # restart dnsmasq systemctl restart dnsmasq.service # Perform a dns query dig @127.0.0.1 +short linux.com # Comment the
[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
Hello Gil, or anyone else affected, Accepted openssl into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Kinetic: Won't Fix Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of three bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] S/MIME signature can fail silently The commit by upstream propagates the return code of some functions rather than ignore it. [Test plan] This issue is not very simple to reproduce because "openssl cms" cannot be used to do so. This has to be done with the openssl API instead. At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. [Where problems could occur] At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/pull/18876 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate
Hello bugproxy, or anyone else affected, Accepted openssl into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Jammy) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2023545 Title: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate Status in Ubuntu on IBM z Systems: In Progress Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of three bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] Openssl using an engine dumps core upon certificate creation; other operations are probably affected too. Overall, engines are likely mostly unusable. [Test plan] - An openssl engine is req. to test the fix. - A z13 / LinuxONE LPAR or z/VM guest is needed, with attached APQN. - Check with 'lszcrypt -V' the availability (online) of the hw crypto resources. - Install the needed package that allows to exploit the hw crypto resources: sudo apt-get install libica-utils libica? openssl-ibmca - And copy a working sample openssf.cnf file: sudo cp /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample /etc/ssl/openssl.cnf - Verify if the 'openssl engine' lists an ibmca engine, in addition to the dynamic engine: (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support <=== - try to create a new certificate, using this cmd-line: openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' - The above command must not lead to a 'Segmentation fault (core dumped)', rather than create a proper certificate file. Also watch /var/log/syslog / journalctl for more details. - The issue is fixed in openssl 3.0.8 which landed in lunar. [Where problems could occur] I don't pretend to understand the lifecycle of providers in openssl3 but the patch is simple and has been widely tested by now, including on ubuntu. Thus, I see little chance an unexpected problem would occur with it. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/issues/18578 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy- sru-0001-Release-the-drbg-in-the-global-default-context- befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' ---Problem Description--- OpenSSL with ibmca engine configured dumps core when creating a new certificate. # openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support # openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' Segmentation fault (core dumped) # journalctl Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b ilc:2 in libc.so.6[3ffae08+1ca000] Jun 07 13:06:08 SYSTEM kernel: Failing address: TEID: 0800 Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user ASCE. Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024 Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded Not tainted 5.15.0-73-generic #80-Ubuntu Jun 07
[Touch-packages] [Bug 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
Hello Adrien, or anyone else affected, Accepted openssl into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2033422 Title: openssl: backport to jammy "clear method store / query cache confusion" Status in openssl package in Ubuntu: New Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [ATTENTION] This SRU contains THREE changes which are listed in the section below. [Meta] This bug is part of a series of three bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses three issues with Jammy's openssl version: - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections (this one) The SRU information has been added to the three bug reports and I am attaching the debdiff here only for all three. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). I have also pushed the code to git (without any attempt to make it git-ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . To test, follow these steps: - run "time python3 main.py" # using the aforementioned main.py script - apt install -t jammy-proposed libssl3 - run "time python3 main.py" - compare the runtimes for the two main.py runs You can run this on x86_64, Raspberry Pi 4 or any machine, and get a very large speed-up in all cases. The improvements are not architecture-dependant. Using this changeset, I get the following numbers for ten runs on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used
[Touch-packages] [Bug 2040011] Re: [SRU] Ensure supported codenames are accurate
** Changed in: vim (Ubuntu Mantic) Status: In Progress => Incomplete ** Changed in: vim (Ubuntu Jammy) Status: In Progress => Incomplete ** Changed in: vim (Ubuntu Focal) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2040011 Title: [SRU] Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Released Status in vim source package in Focal: Incomplete Status in vim source package in Jammy: Incomplete Status in vim source package in Lunar: Won't Fix Status in vim source package in Mantic: Incomplete Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "noble") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+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 2041396] Re: gdb 12.1 generates SIGILL on armhf
> The where problems could occur section says "it is possible that this
fix may break ARM64 execution". How was it verified that this is not
broken?
I believe this could be verified by running the GDB tests inside the Rust
testing suite.
Should I queue an autopkgtest against rustc for GDB in this case?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Fix Released
Status in gdb package in Ubuntu:
Fix Released
Status in gdb source package in Jammy:
Incomplete
Bug description:
[ Impact ]
* GDB 12.1 introduced a regression where it will break program execution
when the program contains mixed ARM code and THUMB code.
* Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.
[ Test Plan ]
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands ...
```
b 3
r
c
```
(you can save the contents above to a file and run GDB using `gdb -x
script ./repro`)
... you will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
[ Where problems could occur ]
* GDB is a complex software. As the patch suggests, it may break other use
cases (like single-stepping) entirely.
* Since this is an ARM-only patch, it's unlikely to affect other CPU
architectures. However, it is possible that this fix may break ARM64 execution.
[ Other Info ]
* This bug has been fixed in GDB 13, but the fix was never backported to GDB
12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+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 2041396] Re: gdb 12.1 generates SIGILL on armhf
The where problems could occur section says "it is possible that this
fix may break ARM64 execution". How was it verified that this is not
broken?
** Changed in: gdb (Ubuntu Jammy)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Fix Released
Status in gdb package in Ubuntu:
Fix Released
Status in gdb source package in Jammy:
Incomplete
Bug description:
[ Impact ]
* GDB 12.1 introduced a regression where it will break program execution
when the program contains mixed ARM code and THUMB code.
* Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.
[ Test Plan ]
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands ...
```
b 3
r
c
```
(you can save the contents above to a file and run GDB using `gdb -x
script ./repro`)
... you will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
[ Where problems could occur ]
* GDB is a complex software. As the patch suggests, it may break other use
cases (like single-stepping) entirely.
* Since this is an ARM-only patch, it's unlikely to affect other CPU
architectures. However, it is possible that this fix may break ARM64 execution.
[ Other Info ]
* This bug has been fixed in GDB 13, but the fix was never backported to GDB
12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+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 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration Status in gtk+3.0 package in Ubuntu: Incomplete Status in lxqt-session package in Ubuntu: Fix Released Bug description: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg- divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
I updated the tasks on this bug after having verified what has LXC_DEVEL set to 1, so we should be good now in terms of affected releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Jammy: Confirmed Status in lxc source package in Mantic: Confirmed Status in lxc source package in Noble: Confirmed Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
In fact, the same but updated note was already on https://documentation.ubuntu.com/lxd/en/latest/installing/#install-lxd- from-source where it mentions that it affects 22.04 onward while the one you dug up says 23.04/23.10 are not affected ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Jammy: Confirmed Status in lxc source package in Mantic: Confirmed Status in lxc source package in Noble: Confirmed Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2046526] Re: pam_access Configuration Treats TTY Names as Hostnames
** Changed in: pam (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2046526 Title: pam_access Configuration Treats TTY Names as Hostnames Status in pam package in Ubuntu: Confirmed Bug description: Comments in PAM service files at /etc/pam.d/* suggest a line to uncomment to configure complicated authorization rules using pam_access (which in turn is configured by /etc/security/access.conf): /etc/pam.d/sshd: # Uncomment and edit /etc/security/access.conf if you need to set complex # access limits that are hard to express in sshd_config. # account required pam_access.so /etc/pam.d/login: # Uncomment and edit /etc/security/access.conf if you need to # set access limits. # (Replaces /etc/login.access file) # account required pam_access.so Comments in /etc/security/access.conf indicate the origin in this file can be a TTY or domain name: # The third field should be a list of one or more tty names (for # non-networked logins), host names, domain names (begin with "."), I wanted to configure a user on my server, 'localadmin', who can only log in on the console and not via any network service and tried to achieve this using pam_access as follows: I uncommented the default ‘account required pam_access.so’ lines in /etc/pam.d/sshd and /etc/pam.d/login. I add the following in /etc/security/access.conf intending to allow user 'localadmin' to only log in on the console: +:localadmin:tty1 -:localadmin:ALL This seems to work. Login via SSH fails and succeeds on the console, as expected. However, /var/log/auth.log suspiciously indicates it is treating tty1 as a hostname during the failed SSH attempt: Dec 15 01:28:12 server sshd[5868]: pam_access(sshd:account): cannot resolve hostname "tty1" Dec 15 01:28:12 server sshd[5868]: pam_access(sshd:account): access denied for user `localadmin' from `10.0.0.101' It is confirmed to be doing DNS lookups for 'tty1' in the search domain during the login attempt: admin@server:~$ resolvectl status eth0 ... DNS Servers: 10.0.0.2 DNS Domain: example.com admin@server:~$ sudo tcpdump -i eth0 -n port 53 01:28:12.100348 IP 10.0.0.42.44968 > 10.0.0.2.53: 21558+ [1au] A? tty1.example.com. (45) 01:28:12.100666 IP 10.0.0.42.44669 > 10.0.0.2.53: 40453+ [1au] ? tty1.example.com. (45) 01:28:12.103027 IP 10.0.0.2.53 > 10.0.0.42.44968: 21558 NXDomain* 0/1/1 (95) 01:28:12.103027 IP 10.0.0.2.53 > 10.0.0.42.44669: 40453 NXDomain* 0/1/1 (95) I configured my DNS service to resolve hostname 'tty1' to the IP address the SSH connection originates from: admin@server:~$ dig +short tty1.example.com 10.0.0.101 SSH access is then unexpectedly allowed: user@clienthost:~$ ip -4 a show dev eth0 inet 10.0.0.101/24 ... user@clienthost:~$ ssh localadmin@10.0.0.42 localadmin@10.0.0.42's password: localadmin@server:~$ I think the local origins should be completely separated from network origins in /etc/security/access.conf somehow (maybe with separate access.conf files used for local and network PAM services). Other requested bug report info: root@server:~# lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 root@server:~# apt-cache policy pam N: Unable to locate package pam root@server:~# apt-cache policy libpam-modules libpam-modules: Installed: 1.4.0-11ubuntu2.3 Candidate: 1.4.0-11ubuntu2.3 Version table: *** 1.4.0-11ubuntu2.3 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1.4.0-11ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2046526/+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 2047595] Re: sound control panel security
** Package changed: ubuntu-meta (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2047595 Title: sound control panel security Status in gnome-shell package in Ubuntu: New Bug description: The controls in the upper right hand corner, which consist of WiFi Bar, Sound Bar, and Battery Bar icons are unlocked when the machine is locked. This will enable anyone, who has physical access to the machine to change, disable or rearrange any settings available in this interface; 1. WiFi-- add or remove access points, disconnect WiFi, change power modes, styles, keyboard, etc. Power Modes. 2. Sounds, disable or modify sounds, lighting settings 3. Change or modify battery schemes. Power off machines, or sleep / Hibernate machine, etc. lsb_release -rd Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2047595/+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 2046633] Re: Don't include 'nmcli -f all con' output in bug report (for privacy)
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046633
Title:
Don't include 'nmcli -f all con' output in bug report (for privacy)
Status in network-manager package in Ubuntu:
New
Bug description:
The apport bug reporting hooks for this package
(/usr/share/apport/package/hooks/source_network-manager{,-applet}.py)
include the output of `nmcli -f all con`. This lists all wifi SSIDs
that the user has ever connected to, and the date of last connection.
I think this is a privacy problem, as it tends to reveal the user's
recent whereabouts, and it's posted publicly on launchpad. (Imagine
for instance an entry for "LoveMotelGuestWifi" at a time when the user
had said they were at the office...)
It is disclosed to the user before the report is sent, but only if
they think to expand that item in the "Send / Don't send" dialog
(which is not descriptively labeled), and there is no way to opt out
of it. You can delete it manually from launchpad afterward, which is
what I am going to do with this bug report, but I doubt most people
would know to do that.
This info should probably not be included at all, or if it is, it
should be sanitized. Also, it might be a good idea to purge launchpad
of all such files.
(Marking this as "security" in case you consider this kind of a
privacy leak to be something the security team should handle. If not,
feel free to demote it to an ordinary bug.)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sat Dec 16 14:38:45 2023
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-06-03 (1657 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
default via 192.168.1.13 dev enxa0cec8c4f782 proto dhcp src 192.168.1.60
metric 100
169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.1.0/24 dev enxa0cec8c4f782 proto kernel scope link src 192.168.1.60
metric 100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: network-manager
UpgradeStatus: Upgraded to mantic on 2023-12-14 (3 days ago)
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2020-08-04T11:07:36.415303
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.44.2 connected started full enabled enabled
enabled missing enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046633/+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 2047595] Re: sound control panel security
What desktop environment are you using? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2047595 Title: sound control panel security Status in gnome-shell package in Ubuntu: New Bug description: The controls in the upper right hand corner, which consist of WiFi Bar, Sound Bar, and Battery Bar icons are unlocked when the machine is locked. This will enable anyone, who has physical access to the machine to change, disable or rearrange any settings available in this interface; 1. WiFi-- add or remove access points, disconnect WiFi, change power modes, styles, keyboard, etc. Power Modes. 2. Sounds, disable or modify sounds, lighting settings 3. Change or modify battery schemes. Power off machines, or sleep / Hibernate machine, etc. lsb_release -rd Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2047595/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
Food for thought for an SRU, here is an example of an upstream that noted[1] this problem: NOTE: If you use the `liblxc-dev` package and get compile time errors when building the `go-lxc` module, ensure that the value for `LXC_DEVEL` is `0` for your `liblxc` build. To check that, look at `/usr/include/lxc/version.h`. If the `LXC_DEVEL` value is `1`, replace it with `0` to work around the problem. It's a packaging bug, and we are aware of it for Ubuntu 22.04/22.10. Ubuntu 23.04/23.10 does not have this problem. 1. https://sources.debian.org/src/incus/0.4-1/doc/installing.md/?hl=192#L191 ** Changed in: lxc (Ubuntu Mantic) Status: New => Confirmed ** Changed in: lxc (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Jammy: Confirmed Status in lxc source package in Mantic: Confirmed Status in lxc source package in Noble: Confirmed Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2049239] Re: package linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049239 Title: package linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: i occured this when i on terminal i can't provide more details because i don't know much ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 12 19:20:00 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2023-10-28 (76 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: initramfs-tools Title: package linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049239/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
I imported your noble debdiff and pushed to this branch: https://code.launchpad.net/~ahasenack/ubuntu/+source/lxc/+git/lxc/+ref/noble- lxc-drop-devel-2039873 If you run "git ubuntu clone lxc; cd lxc; git ubuntu remote add ahasenack; git checkout noble-lxc-drop-devel-2039873" you should have a local copy. Or if using just git, not git-ubuntu, follow the instructions from the URL above. Regarding the new d/t/build dep8 test: """ d/t/control: Tests: build Restrictions: allow-stderr superficial d/t/build: #!/bin/sh # autopkgtest check: very basic checks to ensure that LXC package is in a good shape set -eux # ensure that LXC_DEVEL is 0 grep "LXC_DEVEL" meson.build | grep 0 """ a) being marked as superficial won't block a migration if it fails (IIRC: at least, it's definitely not a hard error). And we do want this to "stop the line" if it fails, right? b) it's checking something from the source code, which could be later changed via d/rules during build. What I mean is that this is not the place users will get the value of LXC_DEVEL from. We should be checking the include file that gets installed on the user's system, either via grep, or preferably a small C program that includes that version.h file and checks the value of LXC_DEVEL. c) A DEP8 test is awesome, thanks for that. But it might too close to a release for such a check. Imagine an SRU gets sponsored, then reviewed, then accepted, and then we get the DEP8 result that says "oops, LXC_DEVEL=1 is leaking again". How about also checking it during package build? I won't block the upload on this, though, but it would be good to have I think, even if later. What are your thoughts on (a) and (b)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Jammy: New Status in lxc source package in Mantic: New Status in lxc source package in Noble: Confirmed Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
** Also affects: lxc (Ubuntu Noble) Importance: Undecided Status: Confirmed ** Also affects: lxc (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Jammy: New Status in lxc source package in Mantic: New Status in lxc source package in Noble: Confirmed Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 1958019]
Canonical occasionally breaks sound compatibility between kernel release (but I yet to figure out why). However, the XanMod kernel quite rarely breaks Lenovo sound compatibility, thus I suggest you give that kernel a whirl: https://xanmod.org/ (It's quite easy to install and remove if needed). -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
Probably time to bisect and then report back to Cirrus Logic. On 1/18/24 16:53, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #806 from Howard Chu (h...@highlandsun.com) --- > (In reply to Cameron Berkenpas from comment #805) >> I believe support for the 16ACHg6 was added quite a ways back. > Yes, it was added in 5.18. It is broken in 6.x. That's why I still only run > 5.19 on my machine. The comment below says it actually stopped working in > 6.6. > I can't confirm that it worked in any earlier 6.x kernels, I had no luck with > it. >> On 1/18/24 05:36, bugzilla-dae...@kernel.org wrote: >>> --- Comment #804 from shenanig...@duck.com --- >>> (In reply to Howard Chu from comment #791) (In reply to Miggy from comment #790) > It seems the sound no longer works for the legion 7 16achg6 on kernel >> 6.6. > It's been working great for the last year on all kernels, but 6.6 just > doesn't work. > > I'm not sure if anyone else is having similar issues? Manjaro Linux here. I had no luck with sound on Ubuntu's 6.2 either. I dropped back to 5.19 to get sound working again. >>> I have been lurking on this thread for a while. This thread has been up and >>> still active since 2020, I don't even know where / which suggestions I need >>> to >>> start following. >>> >>> I have 16ACHg6 too, (Alsa says that) it's running Realtek ALC287. I have a >>> fresh install of Ubuntu 22.04 with kernel 6.5.0-14-generic, I have updated >> my >>> BIOS and internal speakers hasn't been working at all since the first day. >>> External speakers (headphone, Bluetooth speakers) work just fine though. >>> Still >>> no luck with 16ACHg6 then ? >>> -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to Cameron Berkenpas from comment #805) > I believe support for the 16ACHg6 was added quite a ways back. Yes, it was added in 5.18. It is broken in 6.x. That's why I still only run 5.19 on my machine. The comment below says it actually stopped working in 6.6. I can't confirm that it worked in any earlier 6.x kernels, I had no luck with it. > > On 1/18/24 05:36, bugzilla-dae...@kernel.org wrote: > > --- Comment #804 from shenanig...@duck.com --- > > (In reply to Howard Chu from comment #791) > >> (In reply to Miggy from comment #790) > >>> It seems the sound no longer works for the legion 7 16achg6 on kernel > 6.6. > >>> It's been working great for the last year on all kernels, but 6.6 just > >>> doesn't work. > >>> > >>> I'm not sure if anyone else is having similar issues? Manjaro Linux here. > >> I had no luck with sound on Ubuntu's 6.2 either. I dropped back to 5.19 to > >> get sound working again. > > I have been lurking on this thread for a while. This thread has been up and > > still active since 2020, I don't even know where / which suggestions I need > > to > > start following. > > > > I have 16ACHg6 too, (Alsa says that) it's running Realtek ALC287. I have a > > fresh install of Ubuntu 22.04 with kernel 6.5.0-14-generic, I have updated > my > > BIOS and internal speakers hasn't been working at all since the first day. > > External speakers (headphone, Bluetooth speakers) work just fine though. > > Still > > no luck with 16ACHg6 then ? > > -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
I believe support for the 16ACHg6 was added quite a ways back. On 1/18/24 05:36, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > shenanig...@duck.com changed: > > What|Removed |Added > > CC||shenanig...@duck.com > > --- Comment #804 from shenanig...@duck.com --- > (In reply to Howard Chu from comment #791) >> (In reply to Miggy from comment #790) >>> It seems the sound no longer works for the legion 7 16achg6 on kernel 6.6. >>> It's been working great for the last year on all kernels, but 6.6 just >>> doesn't work. >>> >>> I'm not sure if anyone else is having similar issues? Manjaro Linux here. >> I had no luck with sound on Ubuntu's 6.2 either. I dropped back to 5.19 to >> get sound working again. > I have been lurking on this thread for a while. This thread has been up and > still active since 2020, I don't even know where / which suggestions I need > to > start following. > > I have 16ACHg6 too, (Alsa says that) it's running Realtek ALC287. I have a > fresh install of Ubuntu 22.04 with kernel 6.5.0-14-generic, I have updated my > BIOS and internal speakers hasn't been working at all since the first day. > External speakers (headphone, Bluetooth speakers) work just fine though. > Still > no luck with 16ACHg6 then ? > -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to Howard Chu from comment #791) > (In reply to Miggy from comment #790) > > It seems the sound no longer works for the legion 7 16achg6 on kernel 6.6. > > It's been working great for the last year on all kernels, but 6.6 just > > doesn't work. > > > > I'm not sure if anyone else is having similar issues? Manjaro Linux here. > > I had no luck with sound on Ubuntu's 6.2 either. I dropped back to 5.19 to > get sound working again. I have been lurking on this thread for a while. This thread has been up and still active since 2020, I don't even know where / which suggestions I need to start following. I have 16ACHg6 too, (Alsa says that) it's running Realtek ALC287. I have a fresh install of Ubuntu 22.04 with kernel 6.5.0-14-generic, I have updated my BIOS and internal speakers hasn't been working at all since the first day. External speakers (headphone, Bluetooth speakers) work just fine though. Still no luck with 16ACHg6 then ? -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2040011] Re: [SRU] Ensure supported codenames are accurate
please fix the header to have the required SRU information -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2040011 Title: [SRU] Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Released Status in vim source package in Focal: In Progress Status in vim source package in Jammy: In Progress Status in vim source package in Lunar: Won't Fix Status in vim source package in Mantic: In Progress Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "noble") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+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 2047450] Please test proposed package
Hello dann, or anyone else affected, Accepted coreutils into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/coreutils/8.32-4.1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2047450 Title: tail emits no output for sysfs files when using large page kernels Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: Fix Committed Status in coreutils source package in Lunar: Won't Fix Status in coreutils source package in Mantic: Fix Committed Status in coreutils source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional -64k flavors). When booted on 64K kernels, tail emits no output when tailing a sysfs file. The difference in behavior can be a source for bugs in scripts that use tail, and general user confusion. [Test Plan] The upstream fix includes a test case that tails the /sys/kernel/profiling file, if it exists. That case would fail with an unfixed coreutils package as shown below: = When booted on a 4K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling 0 = When booted on a 64K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling ubuntu@gunyolk:~$ Since the upstream test cases are executed at build time, the existing tests and this new test will be used to regression test behavior. This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We should also do a manual verification on arm64 w/ the 64K kernel since that case is not covered by our builders. [Where Problems Could Occur] The biggest risk for a regression I see is due to the side-effect of the fix now allocating a dynamic buffer instead of the stack. An error in logic there could cause a crash or a memory leak in scenarios undetected during testing. I used valgrind when developing the fix to derisk the memory leak scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+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 2047450] Re: tail emits no output for sysfs files when using large page kernels
Hello dann, or anyone else affected, Accepted coreutils into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/coreutils/9.1-1ubuntu2.23.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: coreutils (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: coreutils (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2047450 Title: tail emits no output for sysfs files when using large page kernels Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: Fix Committed Status in coreutils source package in Lunar: Won't Fix Status in coreutils source package in Mantic: Fix Committed Status in coreutils source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional -64k flavors). When booted on 64K kernels, tail emits no output when tailing a sysfs file. The difference in behavior can be a source for bugs in scripts that use tail, and general user confusion. [Test Plan] The upstream fix includes a test case that tails the /sys/kernel/profiling file, if it exists. That case would fail with an unfixed coreutils package as shown below: = When booted on a 4K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling 0 = When booted on a 64K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling ubuntu@gunyolk:~$ Since the upstream test cases are executed at build time, the existing tests and this new test will be used to regression test behavior. This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We should also do a manual verification on arm64 w/ the 64K kernel since that case is not covered by our builders. [Where Problems Could Occur] The biggest risk for a regression I see is due to the side-effect of the fix now allocating a dynamic buffer instead of the stack. An error in logic there could cause a crash or a memory leak in scenarios undetected during testing. I used valgrind when developing the fix to derisk the memory leak scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+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 2031841] Re: initramfs-tools and dracut install different sets of kernel modules
For the record, these commits refer to this bug: Filter net kernel modules by symbol regexp from dracut https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-tools/commit/?id=55a7cf12c037ccd14a0241aa8cab085f6f8590d8 Filter block kernel modules by symbol regex from dracut https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-tools/commit/?id=7ef0f4f446abe98434dcd2410247f95b0983 Install all usb/typec kernel modules https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-tools/commit/?id=aa8821f6ad59d9ce8f8cacddc5f8ae7e41178b71 Do not install ARM/RISCV specific modules on other architectures https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-tools/commit/?id=2df78bbb143884b9601a32608e12e43d40ccb0b0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2031841 Title: initramfs-tools and dracut install different sets of kernel modules Status in initramfs-tools package in Ubuntu: Fix Released Bug description: initramfs-tools and dracut install different sets of kernel modules. Either these modules are not needed for booting or are missing in the other project. dracut-install can filter modules by symbol (--mod-filter-symbol) to select modules more fine-grain. Harmonize the set of modules. Adopt the install rules from dracut to get rid of modules that are shipped in initramfs-tools, but not in dracut. Following kernel modules will be kept since they are mentioned in the initramfs-tools code: * via hidden_dep_add_modules: psmouse mlx5_ib mlx4_ib * via framebuffer hook: =drivers/gpu vga16fb =drivers/char/agp * explicit in auto_add_modules: extcon-usb-gpio extcon-usbc-cros-ec cros_ec_spi * via hw_random in auto_add_modules: =drivers/char/hw_random * via fb in auto_add_modules: pwm-cros-ec pwm_bl * ignored difference for now: =drivers/mmc * via virtual in auto_add_modules: hv_utils * not analyzed yet: mhi_ep mhi mhi_pci_generic i2c-mux i2c-mux-gpio i2c-mux-ltc4306 i2c-mux-mlxcpld i2c-mux-pca9541 i2c-mux-pca954x i2c-mux-reg c67x00 Following modules will be removed from initramfs-tools with this change, but are in dracut (pulled in as dependency): intel_pmc_bxt kempld-core rave-sp retu-mfd nandcore bch If that change removed too much, we need to add it back and also report that to dracut to add it there as well. Test setup: mantic schroot with linux 6.3.0-7-generic and following packages: linux-image-generic,zstd,busybox-initramfs,cryptsetup- initramfs,isc-dhcp-client,kbd,lvm2,mdadm,ntfs-3g,plymouth,plymouth- theme-spinner,initramfs-tools,dracut-core,dracut-config- generic,dcracut-network initramfs generation with dracut: dracut --regenerate-all --force -q --add-drivers "=drivers/char/agp hv_utils =drivers/mmc pwm-cros-ec pwm_bl mlx4_ib extcon-usb-gpio extcon-usbc-cros-ec cros_ec_spi =drivers/gpu vga16fb psmouse mlx5_ib =drivers/char/hw_random" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2031841/+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 2049540] Re: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
What is the problem here? Is there any proof that these modules are needed? These four commit refer to bug #2031841 and cause the difference: Filter net kernel modules by symbol regexp from dracut https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-tools/commit/?id=55a7cf12c037ccd14a0241aa8cab085f6f8590d8 Filter block kernel modules by symbol regex from dracut https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-tools/commit/?id=7ef0f4f446abe98434dcd2410247f95b0983 Install all usb/typec kernel modules https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-tools/commit/?id=aa8821f6ad59d9ce8f8cacddc5f8ae7e41178b71 Do not install ARM/RISCV specific modules on other architectures https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-tools/commit/?id=2df78bbb143884b9601a32608e12e43d40ccb0b0 Using symbol regexes will be more fine-grained than including whole directories. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: Triaged Status in initramfs-tools source package in Noble: Triaged Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
Thanks a lot for these, so we're good on AMD platforms. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2049885] [NEW] Merge console-setup (1.223) from Debian
Public bug reported: In Debian console-setup (1.223) is available. It should be merged into Noble. ** Affects: console-setup (Ubuntu) Importance: Undecided Assignee: Heinrich Schuchardt (xypron) Status: New ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) => Heinrich Schuchardt (xypron) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2049885 Title: Merge console-setup (1.223) from Debian Status in console-setup package in Ubuntu: New Bug description: In Debian console-setup (1.223) is available. It should be merged into Noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2049885/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
** Changed in: glibc (Ubuntu) Importance: Undecided => Critical ** Changed in: glibc (Ubuntu) Status: New => Triaged ** Changed in: glibc (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot Status in glibc package in Ubuntu: Triaged Status in pango1.0 package in Ubuntu: New Bug description: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 4 /fontsets/mono # End of fontsets tests --- stderr --- (test program exited with status code 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
I'm currently focused on cataloguing failures, but I'll try to investigate it if nobody has picked it up by then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot Status in glibc package in Ubuntu: New Status in pango1.0 package in Ubuntu: New Bug description: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 4 /fontsets/mono # End of fontsets tests --- stderr --- (test program exited with status code 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2049881] [NEW] pango1.0: FTBFS against glibc 2.39 snapshot
Public bug reported: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH2 2024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH2 2024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH2 2024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH2 2024-01-19 11:25:39.234546069 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 4 /fontsets/mono # End of fontsets tests --- stderr --- (test program exited with status code 1) ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: test-rebuild-glibc-noble ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot Status in glibc package in Ubuntu: New Status in pango1.0 package in Ubuntu: New Bug description: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH22024-01-19
[Touch-packages] [Bug 1568726] Re: iconv stdio buffering
** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu) Status: New => Triaged ** Changed in: glibc (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1568726 Title: iconv stdio buffering Status in eglibc package in Ubuntu: Triaged Status in glibc package in Ubuntu: Triaged Bug description: Tool "iconv" suffers from the stdio buffering problem described here: https://stackoverflow.com/questions/14472179/how-do-i-perform-a- streaming-character-conversion Basically, when piping to iconv in an interactive session, output stutters. Tool "stdbuf" does not help. From the page above: "But it looks like iconv is managing the buffering internally itself - it's nothing to do with the Linux pipe buffer." Solutions are described in this page: http://www.pixelbeat.org/programming/stdio_buffering/ iconv should have a command-line switch to help. From the page above: "Note tail's stdout buffer would also have this problem, but tail -f calls fflush on the stdout stream when new data is received to alleviate this (as do tcpdump -l, grep --line-buffered and sed --unbuffered for example)." [known workaround] Use `recode` instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1568726/+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 1974056] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2024-01-19 05:42 EDT--- @xnox, @Boris, are there any updates on this? -- 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/1974056 Title: iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 fails on s390x Status in iptables: Unknown Status in Ubuntu on IBM z Systems: In Progress Status in iptables package in Ubuntu: New Bug description: In Ubuntu, we execute the full iptables shell testcases across all architectures. They seem to all pass everywhere, however iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless- bitwise_0 is currently failing on s390x like so: command17FAIL stderr: W: [FAILED] ././testcases/nft- only/0009-needless-bitwise_0: expected 0 but got 1 i wonder if there is some endian bug, as this is currently Ubuntu's only big-endian architecture. this can be reproduced with: pull-lp-source iptables cd iptables-1.8.7/ chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0 cd iptables/tests/shell sudo ./run-tests.sh --host To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1974056/+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 1982693] Re: USB-Audio device UMC204HD disappears after suspend
I have in the meantime switched to a new PC and this problem doesn't occur any more. Sorry I cannot be of help. -- 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/1982693 Title: USB-Audio device UMC204HD disappears after suspend Status in alsa-driver package in Ubuntu: New Bug description: Coming back from sleep, Behringer UMC204HD is not in the list of devices in Settings > Sound. It comes back if I unplug and plug back in. I tried with/without a USB hub in between, I tried setting "usbcore.autosuspend=-1". No help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 15:04:57 2022 InstallationDate: Installed on 2022-04-21 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U192k successful Symptom_Card: HD Webcam C525 - HD Webcam C525 Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [USB-Audio - UMC204HD 192k, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.H0 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VH (MS-7996) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.H0:bd06/16/2018:br5.12:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VH(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7996 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1982693/+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 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12
Merged version uploaded which should unblock the autopkgtest. ** Changed in: python-oslo.versionedobjects (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2049369 Title: autopkg tests ignored for migration of python3-defaults adding 3.12 Status in cython package in Ubuntu: New Status in cython-legacy package in Ubuntu: New Status in ipykernel package in Ubuntu: New Status in ironic-python-agent package in Ubuntu: New Status in jupyter-client package in Ubuntu: New Status in numpy package in Ubuntu: New Status in python-memory-profiler package in Ubuntu: New Status in python-oslo.versionedobjects package in Ubuntu: Fix Committed Status in python-urllib3 package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in rich package in Ubuntu: New Status in sphinx-autoapi package in Ubuntu: New Status in vcr.py package in Ubuntu: New Status in cython package in Debian: Unknown Status in cython-legacy package in Debian: New Status in ipykernel package in Debian: New Status in jupyter-client package in Debian: New Status in numpy package in Debian: New Status in python-memory-profiler package in Debian: New Status in python-urllib3 package in Debian: New Status in rich package in Debian: Confirmed Status in sphinx-autoapi package in Debian: Unknown Status in vcr.py package in Debian: Unknown Bug description: autopkg tests ignored for migration of python3-defaults adding 3.12: These are the autopkg tests for packages, which we'll ignore for the initial migration of python3-defaults adding 3.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12
The oslo.versionedobjects autopkgtests appear to be broken in Debian (but working in the 0ubuntu1 version we had before); I'll untangle this and upload a merged version to fix this. ** Changed in: python-oslo.versionedobjects (Ubuntu) Importance: Undecided => High ** Changed in: python-oslo.versionedobjects (Ubuntu) Status: New => In Progress ** Changed in: python-oslo.versionedobjects (Ubuntu) Assignee: (unassigned) => James Page (james-page) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2049369 Title: autopkg tests ignored for migration of python3-defaults adding 3.12 Status in cython package in Ubuntu: New Status in cython-legacy package in Ubuntu: New Status in ipykernel package in Ubuntu: New Status in ironic-python-agent package in Ubuntu: New Status in jupyter-client package in Ubuntu: New Status in numpy package in Ubuntu: New Status in python-memory-profiler package in Ubuntu: New Status in python-oslo.versionedobjects package in Ubuntu: In Progress Status in python-urllib3 package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in rich package in Ubuntu: New Status in sphinx-autoapi package in Ubuntu: New Status in vcr.py package in Ubuntu: New Status in cython package in Debian: Unknown Status in cython-legacy package in Debian: New Status in ipykernel package in Debian: New Status in jupyter-client package in Debian: New Status in numpy package in Debian: New Status in python-memory-profiler package in Debian: New Status in python-urllib3 package in Debian: New Status in rich package in Debian: Confirmed Status in sphinx-autoapi package in Debian: Unknown Status in vcr.py package in Debian: Unknown Bug description: autopkg tests ignored for migration of python3-defaults adding 3.12: These are the autopkg tests for packages, which we'll ignore for the initial migration of python3-defaults adding 3.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x
The last two autopkgtest runs in the infrastructure are green despite
the trigger and they both show:
258s Unpacking wpasupplicant (2:2.10-21) ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite often fails with "systemd units changed without reload" on
s390x
Status in netplan:
Invalid
Status in netplan.io package in Ubuntu:
Triaged
Status in wpa package in Ubuntu:
New
Bug description:
The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
often fails with
AssertionError: systemd units changed without reload
Looking at the history of autopkgtest runs, it looks like that the
error does not always occur during execution of a specific test. I've
seen occurrences of this error during the following test-cases:
test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL
Example [1]:
781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
781s --
781s Traceback (most recent call last):
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line
189, in test_dhcp6
781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in
generate_and_settle
781s self.fail('systemd units changed without reload')
781s AssertionError: systemd units changed without reload
[1] https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2048388/+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
