[Touch-packages] [Bug 2046116] Re: bluetooth device connected but not recognised as output device
Hi Mark,thanks for your help, I am not technical expert but I don't think it is because of my headset since it is relatively new device and, the other thing is that I was using this Bluetooth devices(headset, sound bar) without any problem but this problem started couple of weeks ago, so my initial thought was it was because of an OS update,so I created this bug report.From my observation I would say , it might be related to pulseaudio, because the first thing I recognized was that pulseaudio was not starting automatically at the start, then when i started it, it recognizes Bluetooth devices but they are not listed in Settings->Sound->Output, so there is no sound output from the headset.I have tried your suggested solution but no change, also tried some solutions suggested on the web. @:~/Desktop/TradeWeb/tradestats$ sudo hcitool info F4:4E:FD:00:5A:65 Requesting information ... BD Address: F4:4E:FD:00:5A:65 OUI Company: Actions Semiconductor Co.,Ltd.(Cayman Islands) (F4-4E-FD) Device Name: Srhythm NC25 LMP Version: 5.0 (0x9) LMP Subversion: 0x201 Manufacturer: Actions (Zhuhai) Technology Co., Limited (992) Features page 0: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 -- 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/2046116 Title: bluetooth device connected but not recognised as output device Status in bluez package in Ubuntu: New Bug description: bluetooth device connected but not recognised as output device ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:28:00 2023 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81EK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2018 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 7QCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 530-14IKB dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB: dmi.product.family: YOGA 530-14IKB dmi.product.name: 81EK dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB dmi.product.version: Lenovo YOGA 530-14IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 0C:54:15:91:FA:4F ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:83770 acl:295 sco:0 events:4208 errors:0 TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046116/+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 2046367] Re: AlphaSSL SHA256 G4 Intermediate Certificate missing
Hey Andrey, thanks; I think they've almost got it right -- the Qualys TLS compliance tool says the chain is in the wrong order so it might not work everywhere, but certainly it'll work better than just Ubuntu adding one intermediate: https://www.ssllabs.com/ssltest/analyze.html?d=smsc.kz Thanks ** Changed in: ca-certificates (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/2046367 Title: AlphaSSL SHA256 G4 Intermediate Certificate missing Status in ca-certificates package in Ubuntu: Won't Fix Bug description: Please add AlphaSSL SHA256 G4 Intermediate Certificate into ca- certificates. https://support.globalsign.com/ca-certificates/intermediate- certificates/alphassl-intermediate-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2046367/+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 m from comment #792) > I'm on 6.6.4 on a Lenovo Yoga S940-14IIL > > cat /sys/class/sound/hwC1D0/subsystem_id 0x17aa3819 > > Same subsystem_id as for Lenovo 13s Gen2 ITL > (https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_realtek. > c#L10193) > > Sound works, but it is high-pitched since the base is missing. The C940 also has alc298 and tas2770. Please try this: sudo nano /etc/modprobe.d/alsa-base.conf add this line: options snd-hda-intel model=17aa:3818 save: ctrl+o ctrl+x sudo reboot -- 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 2046495] [NEW] test-execute fails in LXD with failure in exec-privatenetwork-yes-privatemounts-yes.service
Public bug reported: This is in v255. This log snippet is taken from a local autopkgtest build: exec-privatenetwork-yes-privatemounts-yes.service: Will spawn child (service_enter_start): /bin/sh exec-privatenetwork-yes-privatemounts-yes.service: Failed to set 'trusted.invocation_id' xattr on control group /system.slice/test-execute-48e27182b3724b7.scope/99d288e6f11f869e/system.slice/exec-privatenetwork-yes-privatemounts-yes.service, ignoring: Operation not permitted exec-privatenetwork-yes-privatemounts-yes.service: Failed to remove 'trusted.delegate' xattr flag on control group /system.slice/test-execute-48e27182b3724b7.scope/99d288e6f11f869e/system.slice/exec-privatenetwork-yes-privatemounts-yes.service, ignoring: Operation not permitted exec-privatenetwork-yes-privatemounts-yes.service: Failed to remove 'trusted.survive_final_kill_signal' xattr flag on control group /system.slice/test-execute-48e27182b3724b7.scope/99d288e6f11f869e/system.slice/exec-privatenetwork-yes-privatemounts-yes.service, ignoring: Operation not permitted exec-privatenetwork-yes-privatemounts-yes.service: Passing 0 fds to service exec-privatenetwork-yes-privatemounts-yes.service: About to execute: /bin/sh -x -c "! ip link show dummy-test-exec" Serializing sd-executor-state to memfd. exec-privatenetwork-yes-privatemounts-yes.service: Forked /bin/sh as 5092 Closing set fd 21 (socket:[116840]) Closing set fd 19 (socket:[113527]) Closing set fd 20 (socket:[116839]) exec-privatenetwork-yes-privatemounts-yes.service: Changed dead -> start Received SIGCHLD from PID 5092 (sh). Child 5092 (sh) died (code=exited, status=0/SUCCESS) exec-privatenetwork-yes-privatemounts-yes.service: Child 5092 belongs to exec-privatenetwork-yes-privatemounts-yes.service. exec-privatenetwork-yes-privatemounts-yes.service: Main process exited, code=exited, status=0/SUCCESS (success) exec-privatenetwork-yes-privatemounts-yes.service: Running next main command for state start. exec-privatenetwork-yes-privatemounts-yes.service: Will spawn child (service_run_next_main): /bin/sh exec-privatenetwork-yes-privatemounts-yes.service: Passing 0 fds to service exec-privatenetwork-yes-privatemounts-yes.service: About to execute: /bin/sh -x -c "test ! -e /proc/sys/net/ipv4/conf/dummy-test-exec" Serializing sd-executor-state to memfd. exec-privatenetwork-yes-privatemounts-yes.service: Forked /bin/sh as 5094 Closing set fd 21 (socket:[116840]) Closing set fd 19 (socket:[113527]) Closing set fd 20 (socket:[116839]) Received SIGCHLD from PID 5094 (sh). Child 5094 (sh) died (code=exited, status=0/SUCCESS) exec-privatenetwork-yes-privatemounts-yes.service: Child 5094 belongs to exec-privatenetwork-yes-privatemounts-yes.service. exec-privatenetwork-yes-privatemounts-yes.service: Main process exited, code=exited, status=0/SUCCESS (success) exec-privatenetwork-yes-privatemounts-yes.service: Running next main command for state start. exec-privatenetwork-yes-privatemounts-yes.service: Will spawn child (service_run_next_main): /bin/sh exec-privatenetwork-yes-privatemounts-yes.service: Passing 0 fds to service exec-privatenetwork-yes-privatemounts-yes.service: About to execute: /bin/sh -x -c "test ! -e /sys/class/net/dummy-test-exec" Serializing sd-executor-state to memfd. exec-privatenetwork-yes-privatemounts-yes.service: Forked /bin/sh as 5095 Closing set fd 21 (socket:[116840]) Closing set fd 19 (socket:[113527]) Closing set fd 20 (socket:[116839]) exec-privatenetwork-yes-privatemounts-yes.service: Control group is empty. Received SIGCHLD from PID 5095 (sh). Child 5095 (sh) died (code=exited, status=1/FAILURE) exec-privatenetwork-yes-privatemounts-yes.service: Child 5095 belongs to exec-privatenetwork-yes-privatemounts-yes.service. exec-privatenetwork-yes-privatemounts-yes.service: Main process exited, code=exited, status=1/FAILURE exec-privatenetwork-yes-privatemounts-yes.service: Failed with result 'exit-code'. exec-privatenetwork-yes-privatemounts-yes.service: Service will not restart (restart setting) exec-privatenetwork-yes-privatemounts-yes.service: Changed start -> failed exec-privatenetwork-yes-privatemounts-yes.service: Unit entered failed state. exec-privatenetwork-yes-privatemounts-yes.service: Consumed 27ms CPU time. src/test/test-execute.c:1109:test_exec_privatenetwork: exec-privatenetwork-yes-privatemounts-yes.service: can_unshare=yes: exit status 1, expected 0 (test-execute-root) terminated by signal ABRT. Assertion 'r >= 0' failed at src/test/test-execute.c:1330, function prepare_ns(). Aborting. ** Affects: systemd (Ubuntu) Importance: High Assignee: Nick Rosbrook (enr0n) Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2046495 Title:
[Touch-packages] [Bug 2046498] [NEW] test-execute fails in LXD with failure in exec-networknamespacepath-privatemounts-no.service
Public bug reported: This is in v255. This log snippet is taken from a local autopkgtest build: exec-networknamespacepath-privatemounts-no.service: Child 4580 belongs to exec-networknamespacepath-privatemounts-no.service. exec-networknamespacepath-privatemounts-no.service: Main process exited, code=exited, status=0/SUCCESS (success) exec-networknamespacepath-privatemounts-no.service: Running next main command for state start. exec-networknamespacepath-privatemounts-no.service: Will spawn child (service_run_next_main): /bin/sh exec-networknamespacepath-privatemounts-no.service: Passing 0 fds to service exec-networknamespacepath-privatemounts-no.service: About to execute: /bin/sh -x -c "ip link show dummy-test-ns" Serializing sd-executor-state to memfd. exec-networknamespacepath-privatemounts-no.service: Forked /bin/sh as 4581 Closing set fd 19 (socket:[109908]) Closing set fd 21 (socket:[51]) Closing set fd 20 (socket:[50]) Received SIGCHLD from PID 4581 (sh). Child 4581 (sh) died (code=exited, status=1/FAILURE) exec-networknamespacepath-privatemounts-no.service: Child 4581 belongs to exec-networknamespacepath-privatemounts-no.service. exec-networknamespacepath-privatemounts-no.service: Main process exited, code=exited, status=1/FAILURE exec-networknamespacepath-privatemounts-no.service: Failed with result 'exit-code'. exec-networknamespacepath-privatemounts-no.service: Service will not restart (restart setting) exec-networknamespacepath-privatemounts-no.service: Changed start -> failed exec-networknamespacepath-privatemounts-no.service: Unit entered failed state. exec-networknamespacepath-privatemounts-no.service: Consumed 23ms CPU time. src/test/test-execute.c:1124:test_exec_networknamespacepath: exec-networknamespacepath-privatemounts-no.service: can_unshare=no: exit status 1, expected 0 (test-execute-without-unshare) terminated by signal ABRT. Assertion 'r >= 0' failed at src/test/test-execute.c:1330, function prepare_ns(). Aborting. ** Affects: systemd (Ubuntu) Importance: High Assignee: Nick Rosbrook (enr0n) Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2046498 Title: test-execute fails in LXD with failure in exec-networknamespacepath- privatemounts-no.service Status in systemd package in Ubuntu: New Bug description: This is in v255. This log snippet is taken from a local autopkgtest build: exec-networknamespacepath-privatemounts-no.service: Child 4580 belongs to exec-networknamespacepath-privatemounts-no.service. exec-networknamespacepath-privatemounts-no.service: Main process exited, code=exited, status=0/SUCCESS (success) exec-networknamespacepath-privatemounts-no.service: Running next main command for state start. exec-networknamespacepath-privatemounts-no.service: Will spawn child (service_run_next_main): /bin/sh exec-networknamespacepath-privatemounts-no.service: Passing 0 fds to service exec-networknamespacepath-privatemounts-no.service: About to execute: /bin/sh -x -c "ip link show dummy-test-ns" Serializing sd-executor-state to memfd. exec-networknamespacepath-privatemounts-no.service: Forked /bin/sh as 4581 Closing set fd 19 (socket:[109908]) Closing set fd 21 (socket:[51]) Closing set fd 20 (socket:[50]) Received SIGCHLD from PID 4581 (sh). Child 4581 (sh) died (code=exited, status=1/FAILURE) exec-networknamespacepath-privatemounts-no.service: Child 4581 belongs to exec-networknamespacepath-privatemounts-no.service. exec-networknamespacepath-privatemounts-no.service: Main process exited, code=exited, status=1/FAILURE exec-networknamespacepath-privatemounts-no.service: Failed with result 'exit-code'. exec-networknamespacepath-privatemounts-no.service: Service will not restart (restart setting) exec-networknamespacepath-privatemounts-no.service: Changed start -> failed exec-networknamespacepath-privatemounts-no.service: Unit entered failed state. exec-networknamespacepath-privatemounts-no.service: Consumed 23ms CPU time. src/test/test-execute.c:1124:test_exec_networknamespacepath: exec-networknamespacepath-privatemounts-no.service: can_unshare=no: exit status 1, expected 0 (test-execute-without-unshare) terminated by signal ABRT. Assertion 'r >= 0' failed at src/test/test-execute.c:1330, function prepare_ns(). Aborting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046498/+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 2046367] Re: AlphaSSL SHA256 G4 Intermediate Certificate missing
There were problems with the site https://smsc.kz, we wrote to technical support, they uploaded a full bundle of certificates to solve the problem with the lack of an intermediate CA -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/2046367 Title: AlphaSSL SHA256 G4 Intermediate Certificate missing Status in ca-certificates package in Ubuntu: Incomplete Bug description: Please add AlphaSSL SHA256 G4 Intermediate Certificate into ca- certificates. https://support.globalsign.com/ca-certificates/intermediate- certificates/alphassl-intermediate-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2046367/+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 2046336] Re: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
** Changed in: klibc (Debian) Importance: Undecided => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2046336 Title: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs Status in klibc package in Ubuntu: New Status in klibc package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1055694: Package: initramfs-tools Version: 0.142 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating coreutils from 9.1-1 to 9.4-1+b1 the following lines appear when running update-initramfs -u: cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cat' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cpio' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dd' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dmesg' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/false' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/gunzip' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/kill' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ln' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ls' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkdir' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkfifo' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mknod' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mv' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/nuke' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/readlink' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/resume' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sh' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sleep' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sync' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/true' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/umount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/uname' The lines seem to be a cosmetic issue only, but I cannot be entirely sure. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-3-amd64 -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.0-4-amd64 root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro preempt=full quiet -- /proc/filesystems btrfs fuseblk vfat -- lsmod Module Size Used by tcp_diag 12288 0 inet_diag 28672 1 tcp_diag vboxnetadp 28672 0 vboxnetflt 40960 0 vboxdrv 716800 2 vboxnetadp,vboxnetflt nvme_fabrics 32768 0 ccm20480 9 rfcomm102400 16 snd_seq_dummy 12288 0 snd_hrtimer12288 1 snd_seq 114688 7 snd_seq_dummy qrtr 57344 4 cmac 12288 3 algif_hash 12288 1 algif_skcipher 12288 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 36864 2 zstd 12288 12 zram 40960 2 zsmalloc 36864 1 zram btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb intel_rapl_msr 20480 0 btintel57344 1 btusb intel_rapl_common 36864 1 intel_rapl_msr btmtk 12288 1 btusb binfmt_misc28672 1 bluetooth1126400 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm edac_mce_amd 40960 0 kvm_amd 184320 0 iwlmvm589824 0 kvm 1359872 1 kvm_amd mac80211 1392640 1 iwlmvm sha3_generic 16384 1 jitterentropy_rng 20480 1 snd_hda_codec_realtek 192512 1 irqbypass 12288 1 kvm snd_hda_codec_generic 114688 1 snd_hda_codec_realtek ledtrig_audio 12288 1 snd_hda_codec_generic snd_hda_codec_hdmi 90112 1 libarc412288 1 mac80211 ghash_clmulni_intel16384 0 sha512_ssse3 53248 1 snd_hda_intel 61440 4 sha512_generic 16384 1 sha512_ssse3 snd_usb_audio 417792 3 ctr12288 3 snd_intel_dspcfg 32768 1 snd_hda_intel snd_usbmidi_lib49152 1 snd_usb_audio snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg drbg 49152 1 snd_rawmidi53248 1 snd_usbmidi_lib aesni_intel 360448 10 ansi_cprng 12288 0 iwlwifi 544768 1 iwlmvm snd_hda_codec 225280 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek crypto_simd
[Touch-packages] [Bug 2046488] [NEW] test-execute fails on arhmf because of exec-basic.service
Public bug reported: This was observed during a PPA autopkgtest[1] while prepping v255 for Ubuntu. Here is the relevant part from that log: 2158s [31mFAIL: test-execute[0m 2158s Bus n/a: changing state UNSET → OPENING 2158s sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... 2158s Bus n/a: changing state OPENING → AUTHENTICATING 2158s Bus n/a: changing state AUTHENTICATING → HELLO 2158s Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a 2158s Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a 2158s Got message type=method_return sender=org.freedesktop.DBus destination=:1.18 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a 2158s Bus n/a: changing state HELLO → RUNNING 2158s Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a 2158s Got message type=method_return sender=:1.2 destination=:1.18 path=n/a interface=n/a member=n/a cookie=1667 reply_cookie=3 signature=o error-name=n/a error-message=n/a 2158s Got message type=signal sender=org.freedesktop.DBus destination=:1.18 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a 2158s Got message type=method_return sender=org.freedesktop.DBus destination=:1.18 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a 2158s Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. 2158s Got message type=signal sender=:1.2 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=1674 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a 2158s Got result done/Success for job test-execute-28edb5b6cd3eae1c.scope 2158s Bus n/a: changing state RUNNING → CLOSED 2158s Found cgroup2 on /sys/fs/cgroup/unified, unified hierarchy for systemd controller 2158s /* test_run_tests_unprivileged */ 2158s Successfully forked off '(test-execute-unprivileged)' as PID 1662. 2158s PR_SET_MM_ARG_START failed: Operation not permitted 2158s Changing mount flags / (MS_RDONLY|MS_REMOUNT|MS_BIND "")... 2158s Changing mount propagation / (MS_REC|MS_SHARED "") 2158s Mounting tmpfs (tmpfs) on /run/test-execute-unit-dir (MS_NOSUID|MS_NODEV "")... 2158s Reading /usr/lib/systemd/tests/unit-tests/systemd-runtest.env failed: No such file or directory 2158s Mounting tmpfs (tmpfs) on /dev/shm (MS_NOSUID|MS_NODEV "")... 2158s Mounting tmpfs (tmpfs) on /root (MS_NOSUID|MS_NODEV "")... 2158s Mounting tmpfs (tmpfs) on /tmp (MS_NOSUID|MS_NODEV "")... 2158s Mounting tmpfs (tmpfs) on /var/tmp (MS_NOSUID|MS_NODEV "")... 2158s Mounting tmpfs (tmpfs) on /var/lib (MS_NOSUID|MS_NODEV "")... 2158s Mounting tmpfs (tmpfs) on /run/credstore (MS_NOSUID|MS_NODEV "mode=")... 2158s Mounting tmpfs (tmpfs) on /run/credstore.encrypted (MS_NOSUID|MS_NODEV "mode=")... 2158s Found cgroup2 on /sys/fs/cgroup/unified, unified hierarchy for systemd controller 2158s Unified cgroup hierarchy is located at /sys/fs/cgroup/unified/system.slice/test-execute-28edb5b6cd3eae1c.scope/b8fc9c86c5b12c35. Controllers are on legacy hierarchies. 2158s bpf-firewall: Can't load kernel CGROUP SKB BPF program, BPF firewalling is not supported: Operation not permitted 2158s Can't load kernel CGROUP DEVICE BPF program, BPF device control is not supported: Operation not permitted 2158s Controller 'cpu' supported: yes 2158s Controller 'cpuacct' supported: yes 2158s Controller 'cpuset' supported: no 2158s Controller 'io' supported: no 2158s Controller 'blkio' supported: yes 2158s Controller 'memory' supported: yes 2158s Controller 'devices' supported: yes 2158s Controller 'pids' supported: yes 2158s Controller 'bpf-firewall' supported: no 2158s Controller 'bpf-devices' supported: no 2158s Controller 'bpf-foreign' supported: no 2158s Controller 'bpf-socket-bind' supported: no 2158s Controller 'bpf-restrict-network-interfaces' supported: no 2158s Failed to establish memory pressure event source, ignoring: Permission denied 2158s Using systemd-executor binary from '/usr/lib/systemd/systemd-executor'. 2158s Looking for unit files in (higher priority first): 2158s /run/test-execute-unit-dir 2158s /tmp/fake-xdg-runtime-5nI2PG/systemd/user 2158s Found container virtualization lxc. 2158s Unit
[Touch-packages] [Bug 2036253] Re: FTBFS: missing strl* symbols fail the build
** Description changed: [ Impact ] Currently, the build of the heimdal package against glibc 2.38 is not possible due to the fact that strlcat and strlcpy were added to glibc in version 2.38 and heimdal no longer defines its internal version. We need this fix to build heimdal package successfully. [ Test plan ] Build the package in a ppa to check the error is gone and that the package builds successfully. # Install the package and check it works ok #0.Prepare a VM or Container. i.e: # lxc launch ubuntu-daily:mantic Mheimdal #1. Install heimtools from heimdal-clients # apt update && apt upgrade -y # apt install -y heimdal-clients #1.1 Check the libraries are installed well # dpkg -l libroken19-heimdal | grep ii # dpkg -l libkafs0-heimdal | grep ii #1.2 Check that the command is not broken (you get a Usage: : heimtools [--version] [--help] command ..) # heimtools --help - #2. Install aklog from src:aftools, openafs-krb5 binay. With this, we test the 2 libraries - that depends on ROKEN symbols we touched in this SRU. A rebuild of aftools against the - new heimdal package is needed for this to be successfull. + #2. Install aklog from src:aftools, openafs-krb5 binary package. A rebuild of + aftools against the new heimdal package is needed for this to be + successfull. # apt install -y openafs-krb5 - #2.1 Check tht the command is not broken (you don't get a - aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0) + #2.1 Check that the command is not broken (you don't get a + aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version + HEIMDAL_ROKEN_1.0) # aklog --help [ Where problems could occur ] - I tried to get a complete list of libraries and binaries that use the symbols affected in this fix - (inside and outside the ones provided by src:hiemdal itself), but, I don't know if there are other - third-party pieces of software outside the archive that depends on these libraries. - If that if the case, when executing, the affected binary will no run an a messge like this can appear: + I tried to get a complete list of libraries and binaries that use the + symbols affected in this fix (inside and outside the ones provided by + src:hiemdal itself), but, I don't know if there are other third-party + pieces of software outside the archive that depends on these libraries. + + If that if the case, when executing, the affected binary will no run and + a message like this can appear: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0 Could be a disruption in the way the heimdal suite works? Unlikely, but there is always room for it. - It should be fine since the symbols, in this case, are available to all heimdal-dependants libraries in - the build. This case could arise if a mix of heimdal libraries (provided by two different versions of - src:heimdal) are installed, but this is what the 'Breaks:' that was added in the d/control wants to avoid. + It should be fine since the symbols, in this case, are available to all heimdal-dependants libraries in the build. This case could arise if a mix of heimdal libraries (provided by two different versions of src:heimdal) are installed, but this is what the 'Breaks:' that was added in the d/control wants to avoid. [ Other Info ] A rebuild of the openafs package against this new version of the libraries provided by this heimdal package is needed. (bug 2046441). [ Original Description ] See ubuntu-devel thread[1] and mantic rebuild report[2]. dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match completely debian/libkafs0-heimdal.symbols --- debian/libkafs0-heimdal.symbols (libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64) +++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 + @@ -12,7 +12,7 @@ _kafs_get_cred@Base 1.4.0+git20110226 _kafs_realm_of_cell@Base 1.4.0+git20110226 _kafs_resolve_debug@Base 1.4.0+git20110226 - _kafs_strlcpy@Base 1.4.0+git20110226 +#MISSING: 7.8.git20221117.28daf24+dfsg-3ubuntu1# _kafs_strlcpy@Base 1.4.0+git20110226 k_afs_cell_of_file@Base 1.4.0+git20110226 k_hasafs@Base 1.4.0+git20110226 k_hasafs_recheck@Base 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:18: override_dh_makeshlibs] Error 25 This one might need a fix similar to the krb5 one[3]. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042784.html 2. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html#ubuntu-server-team 3. https://launchpad.net/ubuntu/+source/krb5/1.20.1-3ubuntu1 -- You received this bug notification
[Touch-packages] [Bug 2046485] [NEW] intel 3000 hd graphics not working
Public bug reported:
when i try this command
sudo apt-get install xserver-xorg-video-intel
i get this
xserver-xorg-video-intel is already the newest version
(2:2.99.917+git20210115-1).
i have intel 3000 hd graphics built-in in my laptop.
but my screen is too bright and i am getting 3rd class video quality in
youtube in browser, i checked videos in 720p, 1080p, but same issue.
when i check some videos in my laptop, that are in good quality
downloaded from internet. issue is same.
i have no issue in windows 7, 10.
but only i have issue is in Linux mint, and Lubuntu
Lubuntu 22.04 LTS
Lubuntu 22.04.3 LTS JAMMY JELLYFISH RELEASE AMD 20230807
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
CasperVersion: 1.470.2
CompositorRunning: None
CurrentDesktop: LXQt
Date: Thu Dec 14 23:55:58 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family
Integrated Graphics Controller [103c:1658]
LiveMediaBuild: Lubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcKernelCmdLine: fsck.mode=skip noprompt boot=casper
floppy.allowed_drive_mask=0 ignore_uuid --
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2011
dmi.bios.release: 15.27
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1B
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1658
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 10.31
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 16.49
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:br15.27:efr16.49:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058C11244720001620100:rvnHewlett-Packard:rn1658:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:skuA3X35UA#ABA:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.sku: A3X35UA#ABA
dmi.product.version: 058C11244720001620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2046485
Title:
intel 3000 hd graphics not working
Status in xorg package in Ubuntu:
New
Bug description:
when i try this command
sudo apt-get install xserver-xorg-video-intel
i get this
xserver-xorg-video-intel is already the newest version
(2:2.99.917+git20210115-1).
i have intel 3000 hd graphics built-in in my laptop.
but my screen is too bright and i am getting 3rd class video quality
in youtube in browser, i checked videos in 720p, 1080p, but same
issue.
when i check some videos in my laptop, that are in good quality
downloaded from internet. issue is same.
i have no issue in windows 7, 10.
but only i have issue is in Linux mint, and Lubuntu
Lubuntu 22.04 LTS
Lubuntu 22.04.3 LTS JAMMY JELLYFISH RELEASE AMD 20230807
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
CasperVersion: 1.470.2
CompositorRunning: None
CurrentDesktop: LXQt
Date: Thu Dec 14 23:55:58 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family
Integrated Graphics Controller [103c:1658]
LiveMediaBuild:
[Touch-packages] [Bug 2046486] [NEW] units with SetCredential= fail in LXD containers
Public bug reported: To demonstrate this, in an unprivileged LXD container, create the following unit (taken from the systemd test suite): $ cat > /etc/systemd/system/exec-set-credential.service << EOF # SPDX-License-Identifier: LGPL-2.1-or-later [Unit] Description=Test for SetCredential= [Service] ExecStart=/bin/sh -x -c 'test "$$(cat %d/test-execute.set-credential)" = "hoge"' ExecStartPost=/bin/sh -x -c 'test "$$(cat %d/test-execute.set-credential)" = "hoge"' ExecStop=/bin/sh -x -c 'test "$$(cat %d/test-execute.set-credential)" = "hoge"' ExecStopPost=/bin/sh -x -c 'test "$$(cat %d/test-execute.set-credential)" = "hoge"' Type=oneshot SetCredential=test-execute.set-credential:hoge EOF $ systemctl daemon-reload $ systemctl start exec-set-credential.service Job for exec-set-credential.service failed because the control process exited with error code. See "systemctl status exec-set-credential.service" and "journalctl -xeu exec-set-credential.service" for details. With debug logs enabled, we see: $ journalctl -u exec-set-credential.service -b --no-pager Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Trying to enqueue job exec-set-credential.service/start/replace Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Installed new job exec-set-credential.service/start as 2740 Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Enqueued job exec-set-credential.service/start as 2740 Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Will spawn child (service_enter_start): /bin/sh Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Failed to set 'trusted.invocation_id' xattr on control group /system.slice/exec-set-credential.service, ignoring: Operation not permitted Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Failed to remove 'trusted.delegate' xattr flag on control group /system.slice/exec-set-credential.service, ignoring: Operation not permitted Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Failed to remove 'trusted.survive_final_kill_signal' xattr flag on control group /system.slice/exec-set-credential.service, ignoring: Operation not permitted Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Passing 0 fds to service Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: About to execute: /bin/sh -x -c "test \"1031(cat /run/credentials/exec-set-credential.service/test-execute.set-credential)\" = \"hoge\"" Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Forked /bin/sh as 2183 Dec 14 19:24:24 noble (sh)[2183]: PR_SET_MM_ARG_START failed: Operation not permitted Dec 14 19:24:24 noble (sh)[2183]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy Dec 14 19:24:24 noble (sh)[2183]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Changed dead -> start Dec 14 19:24:24 noble systemd[1]: Starting exec-set-credential.service - Test for SetCredential=... Dec 14 19:24:24 noble (sh)[2183]: Successfully forked off '(sd-mkdcreds)' as PID 2184. Dec 14 19:24:24 noble (sd-[2184]: Changing mount propagation /dev (MS_REC|MS_SLAVE "") Dec 14 19:24:24 noble (sd-[2184]: Mounting ramfs (ramfs) on /dev/shm (MS_NOSUID|MS_NODEV|MS_NOEXEC|MS_NOSYMFOLLOW "mode=0700")... Dec 14 19:24:24 noble (sd-[2184]: Changing mount flags /dev/shm (MS_RDONLY|MS_NOSUID|MS_NODEV|MS_NOEXEC|MS_REMOUNT|MS_NOSYMFOLLOW|MS_BIND "")... Dec 14 19:24:24 noble (sd-[2184]: Failed to mount n/a (type n/a) on /dev/shm (MS_RDONLY|MS_NOSUID|MS_NODEV|MS_NOEXEC|MS_REMOUNT|MS_NOSYMFOLLOW|MS_BIND ""): Permission denied Dec 14 19:24:24 noble (sh)[2183]: (sd-mkdcreds) failed with exit status 1. Dec 14 19:24:24 noble (sh)[2183]: exec-set-credential.service: Failed to set up credentials: Protocol error Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Child 2183 belongs to exec-set-credential.service. Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Main process exited, code=exited, status=243/CREDENTIALS Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Will spawn child (service_enter_stop_post): /bin/sh Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: About to execute: /bin/sh -x -c "test \"1031(cat /run/credentials/exec-set-credential.service/test-execute.set-credential)\" = \"hoge\"" Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Forked /bin/sh as 2186 Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Changed start -> stop-post Dec 14 19:24:24 noble (sh)[2186]: PR_SET_MM_ARG_START failed: Operation not permitted Dec 14 19:24:24 noble (sh)[2186]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy Dec 14 19:24:24 noble (sh)[2186]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy Dec 14 19:24:24 noble sh[2186]: + test 1031(cat /run/credentials/exec-set-credential.service/test-execute.set-credential) = hoge Dec 14 19:24:24 noble
[Touch-packages] [Bug 2045033] Re: Merge rsyslog 8.2312.0-1 from Debian
Unsubscribing sponsors, since there are merge conflicts. ** Merge proposal linked: https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/457541 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2045033 Title: Merge rsyslog 8.2312.0-1 from Debian Status in rsyslog package in Ubuntu: New Bug description: Debian has released rsyslog 8.2310.0-4. Merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2045033/+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 2046477] [NEW] Enable unprivileged user namespace restrictions by default
Public bug reported:
As per https://discourse.ubuntu.com/t/spec-unprivileged-user-namespace-
restrictions-via-apparmor-in-ubuntu-23-10/37626, unprivileged user
namespace restrictions for Ubuntu 23.10 are to be enabled by default via
a sysctl.d conf file in apparmor, and for that to happen, the
restrictions need to be enabled for 24.04
When the unprivileged user namespace restrictions are enabled, various
applications within and outside the Ubuntu archive fail to function, as
they use unprivileged user namespaces as part of their normal operation.
A search of the Ubuntu archive for the 23.10 release was performed
looking for all applications that make legitimate use of the
CLONE_NEWUSER argument, the details of which can be seen in
https://docs.google.com/spreadsheets/d/1MOPVoTW0BROF1TxYqoWeJ3c6w2xKElI4w-VjdCG0m9s/edit#gid=2102562502
For each package identified in that list, an investigation was made to
determine if the application actually used this as an unprivileged user,
and if so which of the binaries within the package were affected.
The full investigation can be seen in
https://warthogs.atlassian.net/browse/SEC-1898 (which is unfortunately
private) but is summarised to the following list of Ubuntu source
packages, as well as some out-of-archive applications that are known to
use unprivileged user namespaces.
For each of these binaries, an apparmor profile is required so that the
binary can be granted use of unprivileged user namespaces - an example
profile for the ch-run binary within the charliecloud package is shown:
$ cat /etc/apparmor.d/ch-run
abi ,
include
profile ch-run /usr/bin/ch-run flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists
}
However, in a few select cases, it has been decided not to ship an apparmor
profile, since this would effectively allow this mitigation to be bypassed. In
particular, the unshare and setns binaries within the util-linux package are
installed on every Ubuntu system, and allow an unprivileged user the ability to
launch an arbitrary application within a new user namespace. Any malicious
application then that wished to exploit an unprivileged user namespace to
conduct an attack on the kernel would simply need to spawn itself via `unshare
-U` or similar to be granted this permission. Therefore, due to the ubiquitous
nature of the unshare (and setns) binaries, profiles are not planned to be
provided for these by default.
Similarly, the bwrap binary within bubblewrap is also installed by default on
Ubuntu Desktop 24.04 and can also be used to launch arbitrary binaries within a
new user namespace and so no profile is planned to be provided for this either.
In Bug 2035315 new apparmor profiles were added to the apparmor package
for various applications which require unprivileged user namespaces,
using a new unconfined profile mode. They were also added in the
AppArmor upstream project.
As well as enabling the sysctl via the sysctl.d conf file, it is
proposed to add logic into the apparmor.service systemd unit to check
that the kernel supports the unconfined profile mode and that it is
enabled - and if not then to force disable the userns restrictions
sysctl via the following logic:
userns_restricted=$(sysctl -n kernel.apparmor_restrict_unprivileged_userns)
unconfined_userns=$([ -f
/sys/kernel/security/apparmor/features/policy/unconfined_restrictions/userns ]
&& cat
/sys/kernel/security/apparmor/features/policy/unconfined_restrictions/userns ||
echo 0)
if [ -n "$userns_restricted" ] && [ "$userns_restricted" -eq 1 ]; then
if [ "$unconfined_userns" -eq 0 ]; then
# userns restrictions rely on unconfined userns to be supported
echo "disabling unprivileged userns restrictions since unconfined userns is
not supported / enabled"
sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
fi
fi
This allows a local admin to disable the sysctl via the regular sysctl.d
conf approach, but to also make sure we don't inadvertently enable it
when it is not supported by the kernel.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2046477
Title:
Enable unprivileged user namespace restrictions by default
Status in apparmor package in Ubuntu:
New
Bug description:
As per https://discourse.ubuntu.com/t/spec-unprivileged-user-
namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626,
unprivileged user namespace restrictions for Ubuntu 23.10 are to be
enabled by default via a sysctl.d conf file in apparmor, and for that
to happen, the restrictions need to be enabled for 24.04
When the unprivileged user namespace restrictions are enabled, various
applications within and outside the Ubuntu archive fail to function,
as they use unprivileged user
[Touch-packages] [Bug 2046474] [NEW] Ubuntu-bug in terminal few errors
Public bug reported:
Ubuntu-bug in terminal few errors
ubuntu-bug -w
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none
bind,ro 0 0): cannot open directory "/var/lib": permission denied
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0):
cannot open directory "/var/lib": permission denied
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none
bind,ro 0 0): cannot open directory "/var/lib": permission denied
Gtk-Message: 18:43:25.874: Failed to load module "window-decorations-gtk-module"
Gtk-Message: 18:43:25.874: Failed to load module "colorreload-gtk-module"
kng@kng-300E5EV-300E4EV-270E5EV-270E4EV:~$ ATTENTION: default value of option
mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[ERROR glean_core] Error setting metrics feature config: Json(Error("EOF while
parsing a value", line: 1, column: 0))
ALSA lib conf.c:4120:(snd_config_update_r) Cannot access file
/usr/share/alsa/alsa.conf
ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ default
[Parent 10803, IPC I/O Parent] WARNING: process 11194 exited on signal 9: file
/build/firefox/parts/firefox/build/ipc/chromium/src/base/process_util_posix.cc:266
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.5
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: unknown
CrashReports:
640:1000:125:10103500:2023-12-14 16:45:11.104133895 +0200:2023-12-14
16:45:07.048100891 +0200:/var/crash/_usr_bin_kwin_x11.1000.crash
640:1000:125:7629821:2023-12-14 15:37:52.752158527 +0200:2023-12-14
15:37:50.912875521 +0200:/var/crash/_usr_bin_dolphin.1000.crash
CurrentDesktop: KDE
Date: Thu Dec 14 19:16:42 2023
InstallationDate: Installed on 2021-03-10 (1009 days ago)
InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to jammy on 2023-05-08 (220 days ago)
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2046474
Title:
Ubuntu-bug in terminal few errors
Status in apport package in Ubuntu:
New
Bug description:
Ubuntu-bug in terminal few errors
ubuntu-bug -w
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none
bind,ro 0 0): cannot open directory "/var/lib": permission denied
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0):
cannot open directory "/var/lib": permission denied
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none
bind,ro 0 0): cannot open directory "/var/lib": permission denied
Gtk-Message: 18:43:25.874: Failed to load module
"window-decorations-gtk-module"
Gtk-Message: 18:43:25.874: Failed to load module "colorreload-gtk-module"
kng@kng-300E5EV-300E4EV-270E5EV-270E4EV:~$ ATTENTION: default value of option
mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[ERROR glean_core] Error setting metrics feature config: Json(Error("EOF
while parsing a value", line: 1, column: 0))
ALSA lib conf.c:4120:(snd_config_update_r) Cannot access file
/usr/share/alsa/alsa.conf
ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ default
[Parent 10803, IPC I/O Parent] WARNING: process 11194 exited on signal 9:
file
/build/firefox/parts/firefox/build/ipc/chromium/src/base/process_util_posix.cc:266
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.5
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: unknown
CrashReports:
640:1000:125:10103500:2023-12-14 16:45:11.104133895 +0200:2023-12-14
16:45:07.048100891 +0200:/var/crash/_usr_bin_kwin_x11.1000.crash
[Touch-packages] [Bug 2046356] Re: Update URL for Support information in MOTD message
Dropping the foundations-todo task as we expect debdiffs to sponsor to be provided by Lucas. I expect the patch pilot program to handle this quickly, but please do fill out the SRU template in the bug description. ** Tags removed: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: New Status in base-files source package in Xenial: New Status in base-files source package in Bionic: New Status in base-files source package in Focal: New Status in base-files source package in Jammy: New Status in base-files source package in Mantic: New Status in base-files source package in Noble: New Bug description: On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+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 2046356] Re: Update URL for Support information in MOTD message
** Tags removed: rls-nn-incoming ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: New Status in base-files source package in Xenial: New Status in base-files source package in Bionic: New Status in base-files source package in Focal: New Status in base-files source package in Jammy: New Status in base-files source package in Mantic: New Status in base-files source package in Noble: New Bug description: On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+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 2046336] Re: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
** Changed in: klibc (Ubuntu) Assignee: (unassigned) => Skia (hyask) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2046336 Title: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs Status in klibc package in Ubuntu: New Status in klibc package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1055694: Package: initramfs-tools Version: 0.142 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating coreutils from 9.1-1 to 9.4-1+b1 the following lines appear when running update-initramfs -u: cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cat' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cpio' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dd' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dmesg' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/false' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/gunzip' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/kill' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ln' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ls' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkdir' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkfifo' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mknod' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mv' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/nuke' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/readlink' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/resume' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sh' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sleep' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sync' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/true' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/umount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/uname' The lines seem to be a cosmetic issue only, but I cannot be entirely sure. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-3-amd64 -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.0-4-amd64 root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro preempt=full quiet -- /proc/filesystems btrfs fuseblk vfat -- lsmod Module Size Used by tcp_diag 12288 0 inet_diag 28672 1 tcp_diag vboxnetadp 28672 0 vboxnetflt 40960 0 vboxdrv 716800 2 vboxnetadp,vboxnetflt nvme_fabrics 32768 0 ccm20480 9 rfcomm102400 16 snd_seq_dummy 12288 0 snd_hrtimer12288 1 snd_seq 114688 7 snd_seq_dummy qrtr 57344 4 cmac 12288 3 algif_hash 12288 1 algif_skcipher 12288 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 36864 2 zstd 12288 12 zram 40960 2 zsmalloc 36864 1 zram btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb intel_rapl_msr 20480 0 btintel57344 1 btusb intel_rapl_common 36864 1 intel_rapl_msr btmtk 12288 1 btusb binfmt_misc28672 1 bluetooth1126400 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm edac_mce_amd 40960 0 kvm_amd 184320 0 iwlmvm589824 0 kvm 1359872 1 kvm_amd mac80211 1392640 1 iwlmvm sha3_generic 16384 1 jitterentropy_rng 20480 1 snd_hda_codec_realtek 192512 1 irqbypass 12288 1 kvm snd_hda_codec_generic 114688 1 snd_hda_codec_realtek ledtrig_audio 12288 1 snd_hda_codec_generic snd_hda_codec_hdmi 90112 1 libarc412288 1 mac80211 ghash_clmulni_intel16384 0 sha512_ssse3 53248 1 snd_hda_intel 61440 4 sha512_generic 16384 1 sha512_ssse3 snd_usb_audio 417792 3 ctr12288 3 snd_intel_dspcfg 32768 1 snd_hda_intel snd_usbmidi_lib49152 1 snd_usb_audio snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg drbg 49152 1 snd_rawmidi53248 1 snd_usbmidi_lib aesni_intel 360448 10 ansi_cprng 12288 0 iwlwifi 544768 1 iwlmvm snd_hda_codec 225280 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
[Touch-packages] [Bug 2046459] Re: systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting in boot failure
We are planning on shipping the generator again in the systemd package, though it will remain disabled by default. ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2046459 Title: systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting in boot failure Status in systemd package in Ubuntu: Triaged Bug description: I have my system set up to rely on GPT auto generator together with Discoverable Partitions Specification (DPS). After upgrading my system the gpt generator is no longer included resulting in boot failure. I have been able to workaround this by setting up the mounts in fstab but that is unsatisfactory. Furthermore I work on an embedded device which uses Ubuntu as a base and relies on the GPT auto generator. In this case it is not possible for me to switch back to an old fstab file as we rely on some autodiscovery possible only with DPS. Even though it is not used by the default installation, I kindly request to revert a366279a84730e92ed734710560ea833709f359d. Even though the default does not require it does not mean that no one else does. Also the generator binary fairly small at a few dozen KB so not much is gained from omitting it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046459/+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 2036253] Re: FTBFS: missing strl* symbols fail the build
Testing the rebuilding of openafs for the possible-not-SRU (but at least
is resulting in a lot of polishing for Noble :), because openafs tools
is FTBFS in Noble for other causes [1] ), getting the list of binaries
(not only shared libraries):
for d in $(apt-cache rdepends libroken19-heimdal | cut -d':' -f2 |
xargs); do for b in $(apt-file list ${d} | grep bin | cut -d' ' -f2); do
objdump -T ${b}| grep ROKEN | grep strlc && echo ${b} && echo ${d} &&
apt-cache show ${d} | grep ^Source ; done; done
So, needed action:
* those have to be added to the Breaks.
* hitting an unmet dependencies when installing openafs-krb5, because the
Depends: ${shlibs:Depends}, ${misc:Depends} is converted on Depends:
libroken19-heimdal (= 1.8.10-1ubuntu2.1) but that version number is from
openafs version, not from heimdal: need to check if that comes from the
following change in symbols file (it looks like it, to me):
- libroken.so.19 #PACKAGE# #MINVER#
+ libroken.so.19 #PACKAGE# (= ${binary:Version})
[1] https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/2033754 , and
unsuccessful build on ppa [2]
[2]
https://launchpad.net/~mirespace/+archive/ubuntu/heimdal-ftbfs-lp2036253/+sourcepub/15537670/+listing-archive-extra
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/2036253
Title:
FTBFS: missing strl* symbols fail the build
Status in heimdal package in Ubuntu:
Fix Released
Status in heimdal source package in Mantic:
Fix Committed
Status in heimdal source package in Noble:
Fix Released
Status in heimdal package in Debian:
New
Bug description:
[ Impact ]
Currently, the build of the heimdal package against glibc 2.38 is not
possible due to
the fact that strlcat and strlcpy were added to glibc in version 2.38 and
heimdal no longer defines its internal version.
We need this fix to build heimdal package successfully.
[ Test plan ]
Build the package in a ppa to check the error is gone and that the
package builds successfully.
# Install the package and check it works ok
#0.Prepare a VM or Container. i.e:
# lxc launch ubuntu-daily:mantic Mheimdal
#1. Install heimtools from heimdal-clients
# apt update && apt upgrade -y
# apt install -y heimdal-clients
#1.1 Check the libraries are installed well
# dpkg -l libroken19-heimdal | grep ii
# dpkg -l libkafs0-heimdal | grep ii
#1.2 Check that the command is not broken (you get a
Usage: : heimtools [--version] [--help] command ..)
# heimtools --help
#2. Install aklog from src:aftools, openafs-krb5 binay. With this, we test
the 2 libraries
that depends on ROKEN symbols we touched in this SRU. A rebuild of
aftools against the
new heimdal package is needed for this to be successfull.
# apt install -y openafs-krb5
#2.1 Check tht the command is not broken (you don't get a
aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version
HEIMDAL_ROKEN_1.0)
# aklog --help
[ Where problems could occur ]
I tried to get a complete list of libraries and binaries that use the symbols
affected in this fix
(inside and outside the ones provided by src:hiemdal itself), but, I don't
know if there are other
third-party pieces of software outside the archive that depends on these
libraries.
If that if the case, when executing, the affected binary will no run an a
messge like this can appear:
undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0
Could be a disruption in the way the heimdal suite works? Unlikely, but there
is always room for it.
It should be fine since the symbols, in this case, are available to all
heimdal-dependants libraries in
the build. This case could arise if a mix of heimdal libraries (provided by
two different versions of
src:heimdal) are installed, but this is what the 'Breaks:' that was added in
the d/control wants to avoid.
[ Other Info ]
A rebuild of the openafs package against this new version of the libraries
provided by this heimdal package is needed.
(bug 2046441).
[ Original Description ]
See ubuntu-devel thread[1] and mantic rebuild report[2].
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't
match completely debian/libkafs0-heimdal.symbols
--- debian/libkafs0-heimdal.symbols
(libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64)
+++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 +
@@ -12,7 +12,7 @@
_kafs_get_cred@Base 1.4.0+git20110226
_kafs_realm_of_cell@Base 1.4.0+git20110226
_kafs_resolve_debug@Base 1.4.0+git20110226
- _kafs_strlcpy@Base 1.4.0+git20110226
+#MISSING: 7.8.git20221117.28daf24+dfsg-3ubuntu1# _kafs_strlcpy@Base
1.4.0+git20110226
k_afs_cell_of_file@Base
[Touch-packages] [Bug 2046459] [NEW] systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting in boot failure
Public bug reported: I have my system set up to rely on GPT auto generator together with Discoverable Partitions Specification (DPS). After upgrading my system the gpt generator is no longer included resulting in boot failure. I have been able to workaround this by setting up the mounts in fstab but that is unsatisfactory. Furthermore I work on an embedded device which uses Ubuntu as a base and relies on the GPT auto generator. In this case it is not possible for me to switch back to an old fstab file as we rely on some autodiscovery possible only with DPS. Even though it is not used by the default installation, I kindly request to revert a366279a84730e92ed734710560ea833709f359d. Even though the default does not require it does not mean that no one else does. Also the generator binary fairly small at a few dozen KB so not much is gained from omitting it. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: regression -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2046459 Title: systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting in boot failure Status in systemd package in Ubuntu: New Bug description: I have my system set up to rely on GPT auto generator together with Discoverable Partitions Specification (DPS). After upgrading my system the gpt generator is no longer included resulting in boot failure. I have been able to workaround this by setting up the mounts in fstab but that is unsatisfactory. Furthermore I work on an embedded device which uses Ubuntu as a base and relies on the GPT auto generator. In this case it is not possible for me to switch back to an old fstab file as we rely on some autodiscovery possible only with DPS. Even though it is not used by the default installation, I kindly request to revert a366279a84730e92ed734710560ea833709f359d. Even though the default does not require it does not mean that no one else does. Also the generator binary fairly small at a few dozen KB so not much is gained from omitting it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046459/+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 2045033] Re: Merge rsyslog 8.2312.0-1 from Debian
rsyslog_8.2312.0-1ubuntu1 is building in ppa:xypron/merge-from-debian. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2045033 Title: Merge rsyslog 8.2312.0-1 from Debian Status in rsyslog package in Ubuntu: New Bug description: Debian has released rsyslog 8.2310.0-4. Merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2045033/+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 2045033] Re: Merge rsyslog 8.2312.0-1 from Debian
Merge request created: https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/457541 ** Changed in: rsyslog (Ubuntu) Assignee: Heinrich Schuchardt (xypron) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2045033 Title: Merge rsyslog 8.2312.0-1 from Debian Status in rsyslog package in Ubuntu: New Bug description: Debian has released rsyslog 8.2310.0-4. Merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2045033/+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
Ok, I have tried to do that but get stuck and have a few questions about the process. >In this case, the commits in the repo would be based on debian/sid rather than ubuntu/noble-devel. This >would ensure we incorporate the changes Debian has placed on top of lxc, as well as our own (and means in >future we can follow the git-ubuntu merge process for this package). Does this mean that I have to drop our (ubuntu-specific) changelog file and just replace it with the changelog file from the debian source package? Even more, do I need to take only source code from debian source package or packaging metadata too (debian/ directory)? I can see two options: 1. take debian/sid source package, unpack, add Ubuntu-specific patches, add a changelog entry, add transition packages entries to the debian/control file. In this case we loosing all the changelog from Ubuntu LXC package. 2. take debian/sid source package, unpack, drop debian/ directory and replace it with the debian/ directory from the Ubuntu package from ubuntu/noble-devel, ... Which option is a correct and preferred one? -- 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 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 2045033] Re: Merge rsyslog 8.2312.0-1 from Debian
Upstream release 8.2312.0 introduced a double free bug: https://github.com/rsyslog/rsyslog/issues/5294 A patch has been suggested: https://github.com/rgerhards/rsyslog/commit/c7c16b935c4b3fb740eacbd5dbb043f5cd457acd ** Bug watch added: github.com/rsyslog/rsyslog/issues #5294 https://github.com/rsyslog/rsyslog/issues/5294 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2045033 Title: Merge rsyslog 8.2312.0-1 from Debian Status in rsyslog package in Ubuntu: New Bug description: Debian has released rsyslog 8.2310.0-4. Merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2045033/+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 2036253] Re: FTBFS: missing strl* symbols fail the build
** Description changed: [ Impact ] Currently, the build of the heimdal package against glibc 2.38 is not possible due to the fact that strlcat and strlcpy were added to glibc in version 2.38 and heimdal no longer defines its internal version. We need this fix to build heimdal package successfully. - [ Test plan ] Build the package in a ppa to check the error is gone and that the package builds successfully. # Install the package and check it works ok #0.Prepare a VM or Container. i.e: # lxc launch ubuntu-daily:mantic Mheimdal #1. Install heimtools from heimdal-clients # apt update && apt upgrade -y # apt install -y heimdal-clients #1.1 Check the libraries are installed well # dpkg -l libroken19-heimdal | grep ii # dpkg -l libkafs0-heimdal | grep ii #1.2 Check that the command is not broken (you get a - Usage: : heimtools [--version] [--help] command ..) + Usage: : heimtools [--version] [--help] command ..) # heimtools --help #2. Install aklog from src:aftools, openafs-krb5 binay. With this, we test the 2 libraries - that depends on ROKEN symbols we touched in this SRU. A rebuild of aftools against the - new heimdal package is needed for this to be successfull. + that depends on ROKEN symbols we touched in this SRU. A rebuild of aftools against the + new heimdal package is needed for this to be successfull. # apt install -y openafs-krb5 #2.1 Check tht the command is not broken (you don't get a - aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0) - #aklog --help + aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0) + # aklog --help [ Where problems could occur ] I tried to get a complete list of libraries and binaries that use the symbols affected in this fix (inside and outside the ones provided by src:hiemdal itself), but, I don't know if there are other third-party pieces of software outside the archive that depends on these libraries. If that if the case, when executing, the affected binary will no run an a messge like this can appear: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0 Could be a disruption in the way the heimdal suite works? Unlikely, but there is always room for it. It should be fine since the symbols, in this case, are available to all heimdal-dependants libraries in the build. This case could arise if a mix of heimdal libraries (provided by two different versions of src:heimdal) are installed, but this is what the 'Breaks:' that was added in the d/control wants to avoid. [ Other Info ] A rebuild of the openafs package against this new version of the libraries provided by this heimdal package is needed. (bug 2046441). [ Original Description ] See ubuntu-devel thread[1] and mantic rebuild report[2]. dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match completely debian/libkafs0-heimdal.symbols --- debian/libkafs0-heimdal.symbols (libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64) +++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 + @@ -12,7 +12,7 @@ _kafs_get_cred@Base 1.4.0+git20110226 _kafs_realm_of_cell@Base 1.4.0+git20110226 _kafs_resolve_debug@Base 1.4.0+git20110226 - _kafs_strlcpy@Base 1.4.0+git20110226 +#MISSING: 7.8.git20221117.28daf24+dfsg-3ubuntu1# _kafs_strlcpy@Base 1.4.0+git20110226 k_afs_cell_of_file@Base 1.4.0+git20110226 k_hasafs@Base 1.4.0+git20110226 k_hasafs_recheck@Base 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:18: override_dh_makeshlibs] Error 25 This one might need a fix similar to the krb5 one[3]. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042784.html 2. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html#ubuntu-server-team 3. https://launchpad.net/ubuntu/+source/krb5/1.20.1-3ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2036253 Title: FTBFS: missing strl* symbols fail the build Status in heimdal package in Ubuntu: Fix Released Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Released Status in heimdal package in Debian: New Bug description: [ Impact ] Currently, the build of the heimdal package against glibc 2.38 is not possible due to the fact that strlcat and strlcpy were added to glibc in version 2.38 and heimdal no longer defines its internal version. We need this fix to build heimdal package successfully. [ Test plan ]
[Touch-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
Same thing happening with Lenovo Legion Pro 7 Gen 6 The sound with the integrated sound card has disappeared, however it's working over HDMI and Bluetooth. Here's alsa-info output: http://alsa-project.org/db/?f=b90325c4bf477327de3bceb39c0af9be569ebbaf -- 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/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+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 2046336] Re: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
Test is passing [1] with `klibc` 2.0.13-2ubuntu1~ppa2 from this PPA: https://launchpad.net/~hyask/+archive/ubuntu/klibc-2046336 [1]: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-hyask-klibc-2046336/noble/amd64/i/initramfs-tools/20231214_120611_9a9f6@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2046336 Title: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs Status in klibc package in Ubuntu: New Status in klibc package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1055694: Package: initramfs-tools Version: 0.142 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating coreutils from 9.1-1 to 9.4-1+b1 the following lines appear when running update-initramfs -u: cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cat' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cpio' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dd' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dmesg' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/false' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/gunzip' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/kill' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ln' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ls' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkdir' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkfifo' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mknod' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mv' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/nuke' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/readlink' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/resume' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sh' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sleep' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sync' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/true' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/umount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/uname' The lines seem to be a cosmetic issue only, but I cannot be entirely sure. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-3-amd64 -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.0-4-amd64 root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro preempt=full quiet -- /proc/filesystems btrfs fuseblk vfat -- lsmod Module Size Used by tcp_diag 12288 0 inet_diag 28672 1 tcp_diag vboxnetadp 28672 0 vboxnetflt 40960 0 vboxdrv 716800 2 vboxnetadp,vboxnetflt nvme_fabrics 32768 0 ccm20480 9 rfcomm102400 16 snd_seq_dummy 12288 0 snd_hrtimer12288 1 snd_seq 114688 7 snd_seq_dummy qrtr 57344 4 cmac 12288 3 algif_hash 12288 1 algif_skcipher 12288 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 36864 2 zstd 12288 12 zram 40960 2 zsmalloc 36864 1 zram btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb intel_rapl_msr 20480 0 btintel57344 1 btusb intel_rapl_common 36864 1 intel_rapl_msr btmtk 12288 1 btusb binfmt_misc28672 1 bluetooth1126400 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm edac_mce_amd 40960 0 kvm_amd 184320 0 iwlmvm589824 0 kvm 1359872 1 kvm_amd mac80211 1392640 1 iwlmvm sha3_generic 16384 1 jitterentropy_rng 20480 1 snd_hda_codec_realtek 192512 1 irqbypass 12288 1 kvm snd_hda_codec_generic 114688 1 snd_hda_codec_realtek ledtrig_audio 12288 1 snd_hda_codec_generic snd_hda_codec_hdmi 90112 1 libarc412288 1 mac80211 ghash_clmulni_intel16384 0 sha512_ssse3 53248 1 snd_hda_intel 61440 4 sha512_generic 16384 1 sha512_ssse3 snd_usb_audio 417792 3 ctr12288 3 snd_intel_dspcfg 32768 1 snd_hda_intel snd_usbmidi_lib49152 1 snd_usb_audio snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg drbg 49152 1 snd_rawmidi53248 1 snd_usbmidi_lib aesni_intel
[Touch-packages] [Bug 2036253] Re: FTBFS: missing strl* symbols fail the build
** Description changed: - [SRU - Template WIP] + [ Impact ] + + Currently, the build of the heimdal package against glibc 2.38 is not possible due to + the fact that strlcat and strlcpy were added to glibc in version 2.38 and heimdal no longer defines its internal version. + + We need this fix to build heimdal package successfully. + + + [ Test plan ] + + Build the package in a ppa to check the error is gone and that the + package builds successfully. + + # Install the package and check it works ok + + #0.Prepare a VM or Container. i.e: + # lxc launch ubuntu-daily:mantic Mheimdal + + #1. Install heimtools from heimdal-clients + # apt update && apt upgrade -y + # apt install -y heimdal-clients + + #1.1 Check the libraries are installed well + # dpkg -l libroken19-heimdal | grep ii + # dpkg -l libkafs0-heimdal | grep ii + + #1.2 Check that the command is not broken (you get a + Usage: : heimtools [--version] [--help] command ..) + # heimtools --help + + #2. Install aklog from src:aftools, openafs-krb5 binay. With this, we test the 2 libraries + that depends on ROKEN symbols we touched in this SRU. A rebuild of aftools against the + new heimdal package is needed for this to be successfull. + # apt install -y openafs-krb5 + + #2.1 Check tht the command is not broken (you don't get a + aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0) + #aklog --help + + [ Where problems could occur ] + + I tried to get a complete list of libraries and binaries that use the symbols affected in this fix + (inside and outside the ones provided by src:hiemdal itself), but, I don't know if there are other + third-party pieces of software outside the archive that depends on these libraries. + If that if the case, when executing, the affected binary will no run an a messge like this can appear: + + undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0 + + Could be a disruption in the way the heimdal suite works? Unlikely, but there is always room for it. + It should be fine since the symbols, in this case, are available to all heimdal-dependants libraries in + the build. This case could arise if a mix of heimdal libraries (provided by two different versions of + src:heimdal) are installed, but this is what the 'Breaks:' that was added in the d/control wants to avoid. + + [ Other Info ] + A rebuild of the openafs package against this new version of the libraries provided by this heimdal package is needed. + (bug 2046441). + + [ Original Description ] + See ubuntu-devel thread[1] and mantic rebuild report[2]. dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match completely debian/libkafs0-heimdal.symbols --- debian/libkafs0-heimdal.symbols (libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64) +++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 + @@ -12,7 +12,7 @@ _kafs_get_cred@Base 1.4.0+git20110226 _kafs_realm_of_cell@Base 1.4.0+git20110226 _kafs_resolve_debug@Base 1.4.0+git20110226 - _kafs_strlcpy@Base 1.4.0+git20110226 +#MISSING: 7.8.git20221117.28daf24+dfsg-3ubuntu1# _kafs_strlcpy@Base 1.4.0+git20110226 k_afs_cell_of_file@Base 1.4.0+git20110226 k_hasafs@Base 1.4.0+git20110226 k_hasafs_recheck@Base 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:18: override_dh_makeshlibs] Error 25 This one might need a fix similar to the krb5 one[3]. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042784.html 2. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html#ubuntu-server-team 3. https://launchpad.net/ubuntu/+source/krb5/1.20.1-3ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2036253 Title: FTBFS: missing strl* symbols fail the build Status in heimdal package in Ubuntu: Fix Released Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Released Status in heimdal package in Debian: New Bug description: [ Impact ] Currently, the build of the heimdal package against glibc 2.38 is not possible due to the fact that strlcat and strlcpy were added to glibc in version 2.38 and heimdal no longer defines its internal version. We need this fix to build heimdal package successfully. [ Test plan ] Build the package in a ppa to check the error is gone and that the package builds successfully. # Install the package and check it works ok #0.Prepare a VM or Container. i.e: # lxc launch ubuntu-daily:mantic Mheimdal #1. Install heimtools from heimdal-clients # apt update && apt upgrade -y
[Touch-packages] [Bug 2046389] Re: FTBFS if bash-completion is installed at build time
This bug was fixed in the package p11-kit - 0.25.3-2ubuntu2
---
p11-kit (0.25.3-2ubuntu2) noble; urgency=medium
* d/not-installed: fix FTBFS if bash-completion present (LP: #2046389)
p11-kit (0.25.3-2ubuntu1) noble; urgency=medium
* Merge with Debian unstable. Remaining changes:
- d/rules: disable LTO due to FTBFS (LP 2032576)
p11-kit (0.25.3-2) unstable; urgency=medium
* Upload to unstable.
p11-kit (0.25.3-1) experimental; urgency=medium
* New upstream version.
p11-kit (0.25.2-1) experimental; urgency=medium
* New upstream version.
+ Update copyright file.
* Add lintian override for source-is-missing false positive.
p11-kit (0.25.1-1) experimental; urgency=low
* New upstream version.
+ Unfuzz 40_getpeereid_from_libbsd.diff and 36_enable_locale.diff.
+ Drop patches previously pulled from upstream GIT.
+ Use cme ("cme update dpkg-copyright") with helper files to manage
copyright info.
+ Update symbol file.
+ Add b-d on python3.
p11-kit (0.25.0-5) unstable; urgency=medium
* Add support for nodoc buildprofile. (Patch by Samuel Thibault, modified to
avoid dh-exec.) Closes: #1053327
* Drop ancient override for dh_missing in debian/rules (originally added to
*enable* it, when it was not yet run by default.)
-- Dan Bungert Wed, 13 Dec 2023
17:49:26 -0700
** Changed in: p11-kit (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/2046389
Title:
FTBFS if bash-completion is installed at build time
Status in p11-kit package in Ubuntu:
Fix Released
Bug description:
p11-kit will FTBFS if bash-completion happens to be installed on the
system building p11-kit.
The failure is raised by dh_missing:
dh_missing
dh_missing: warning: usr/share/bash-completion/completions/p11-kit exists in
debian/tmp but is not installed to anywhere (related file:
"debian/tmp/usr/bin/p11-kit")
dh_missing: warning: usr/share/bash-completion/completions/trust exists in
debian/tmp but is not installed to anywhere (related file:
"debian/tmp/usr/bin/trust")
dh_missing: error: missing files, aborting
full sample log:
https://launchpadlibrarian.net/702524075/buildlog_ubuntu-noble-amd64.p11-kit_0.25.3-2ubuntu1_BUILDING.txt.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/2046389/+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 2046436] Re: Ubuntu won't boot after enabling jumbo packets on network device
Hi, If you press ESC when the splash screen shows up, do you see the console? We need to know where it's getting stuck to better understand the problem. If you manage to see the console during boot, can you describe what you see? -- 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/2046436 Title: Ubuntu won't boot after enabling jumbo packets on network device Status in network-manager package in Ubuntu: New Bug description: Ubuntu Desktop 23.10 Asrock IMB-X1714 main board, with Intel I226V and I226LM ethernet controllers network-manager 1.44.2-1ubuntu1.2 When enabling jumbo packets on a wired network device by setting MTU to 9000, Ubuntu will not boot anymore. The Ubuntu splash screen, with rotating wheel, appears, at a lower resolution than ordinary, but freezes after a few seconds. I can only revert this by disabling the ethernet devices in BIOS. After that Ubuntu will boot normally. I can then manually edit the .yaml configuration files in /etc/netplan to disable jumbo packets again. 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 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 11:04:19 2023 IfupdownConfig: InstallationDate: Installed on 2023-12-13 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.208 metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.208 metric 100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled missing enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046436/+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 2022927] Re: Busybox mount fails to mount Snaps
** Changed in: busybox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2022927 Title: Busybox mount fails to mount Snaps Status in busybox package in Ubuntu: Incomplete Bug description: Snapd tries to mount squashfs Snaps with non-standard mount flags like "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to userspace programs that a given mount should not be shown in a list of mounted partitions/filesystems. Busybox does not support these flags, and so fails with "Invalid argument". $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test mount: mounting test on /tmp/test failed: Invalid argument These flags can likely be be safely ignored, as they don't actually affect the functionality of the mount. This goes for all mount options starting with "x-", as these generally denote non-standard mount option "extensions". I've created a patch against Busybox which adds an optional configuration item to ignore all mount options beginning with "x-". An additional verbose option has also been added to enable the ability to report that the mount flags have been ignored, rather than silently ignoring them. This is a requirement for a customer project, where we are limited to using Busybox (due to coreutils' GPL-3.0 licence) but would also require using Snaps like checkbox for testing and verification. This was posted on the Busybox mailing list a few months ago (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html) but patch acceptance there seems to take quite a long time, and we need this for the customer. A PPA containing the patched Busybox version is available on the project's Launchpad team: https://launchpad.net/~nemos- team/+archive/ubuntu/ppa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+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 2046436] [NEW] Ubuntu won't boot after enabling jumbo packets on network device
Public bug reported: Ubuntu Desktop 23.10 Asrock IMB-X1714 main board, with Intel I226V and I226LM ethernet controllers network-manager 1.44.2-1ubuntu1.2 When enabling jumbo packets on a wired network device by setting MTU to 9000, Ubuntu will not boot anymore. The Ubuntu splash screen, with rotating wheel, appears, at a lower resolution than ordinary, but freezes after a few seconds. I can only revert this by disabling the ethernet devices in BIOS. After that Ubuntu will boot normally. I can then manually edit the .yaml configuration files in /etc/netplan to disable jumbo packets again. 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 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 11:04:19 2023 IfupdownConfig: InstallationDate: Installed on 2023-12-13 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.208 metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.208 metric 100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled missing enabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2046436 Title: Ubuntu won't boot after enabling jumbo packets on network device Status in network-manager package in Ubuntu: New Bug description: Ubuntu Desktop 23.10 Asrock IMB-X1714 main board, with Intel I226V and I226LM ethernet controllers network-manager 1.44.2-1ubuntu1.2 When enabling jumbo packets on a wired network device by setting MTU to 9000, Ubuntu will not boot anymore. The Ubuntu splash screen, with rotating wheel, appears, at a lower resolution than ordinary, but freezes after a few seconds. I can only revert this by disabling the ethernet devices in BIOS. After that Ubuntu will boot normally. I can then manually edit the .yaml configuration files in /etc/netplan to disable jumbo packets again. 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 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 11:04:19 2023 IfupdownConfig: InstallationDate: Installed on 2023-12-13 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.208 metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.208 metric 100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled missing enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046436/+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 2022927] Re: Busybox mount fails to mount Snaps
I agree that this patch should be shipped but if upstream doesn't accept it we also would have no way to drop it again without breaking users, so this seems risky. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2022927 Title: Busybox mount fails to mount Snaps Status in busybox package in Ubuntu: New Bug description: Snapd tries to mount squashfs Snaps with non-standard mount flags like "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to userspace programs that a given mount should not be shown in a list of mounted partitions/filesystems. Busybox does not support these flags, and so fails with "Invalid argument". $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test mount: mounting test on /tmp/test failed: Invalid argument These flags can likely be be safely ignored, as they don't actually affect the functionality of the mount. This goes for all mount options starting with "x-", as these generally denote non-standard mount option "extensions". I've created a patch against Busybox which adds an optional configuration item to ignore all mount options beginning with "x-". An additional verbose option has also been added to enable the ability to report that the mount flags have been ignored, rather than silently ignoring them. This is a requirement for a customer project, where we are limited to using Busybox (due to coreutils' GPL-3.0 licence) but would also require using Snaps like checkbox for testing and verification. This was posted on the Busybox mailing list a few months ago (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html) but patch acceptance there seems to take quite a long time, and we need this for the customer. A PPA containing the patched Busybox version is available on the project's Launchpad team: https://launchpad.net/~nemos- team/+archive/ubuntu/ppa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+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
