[Touch-packages] [Bug 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
I have tried that Grzegorz - Thulium suggested but it doesn't work for
me.
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in Linux Firmware:
New
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2037906/+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
Normally, intermediate certificates are supposed to be included by the leaf certificate owners in their chain of certificates to their roots. It is unusual for intermediate certificates to be included in the CA bundle. GlobalSign has instructions for many applications on their website: https://support.globalsign.com/ssl/ssl-certificates- installation I suspect whatever you're problem you're trying to solve would be better solved by a site administrator rather than us. What problem are you trying to solve? Why is including intermediate certificates in our CA bundle the right answer for solving the problem? Thanks ** Changed in: ca-certificates (Ubuntu) Status: New => Incomplete -- 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 2046389] Re: FTBFS if bash-completion is installed at build time
** Changed in: p11-kit (Ubuntu) Status: New => Fix Committed -- 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 Committed 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 2046389] Re: FTBFS if bash-completion is installed at build time
** Changed in: p11-kit (Ubuntu) Assignee: (unassigned) => Dan Bungert (dbungert) -- 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: New 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 2046389] [NEW] FTBFS if bash-completion is installed at build time
Public bug reported: 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 ** Affects: p11-kit (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 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 -- 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: New 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 2045250] Re: pam_lastlog doesn't handle localtime_r related errors properly
I'm uncomfortable with the idea of printing nothing when the routines
fail.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2045250
Title:
pam_lastlog doesn't handle localtime_r related errors properly
Status in Ubuntu on IBM z Systems:
New
Status in pam package in Ubuntu:
New
Status in pam package in Fedora:
Fix Released
Bug description:
The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to
noble) are affected by
https://bugzilla.redhat.com/show_bug.cgi?id=2012871
Customers report a command going through PAM crashing for a given user.
A potential follow on issue can be that no ssh remote connections to an
affected server are possible anymore, esp. painful with headless systems (was
reported on a different distro).
This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
with tm = localtime_r(...) that can be NULL and needs to be handled.
There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
314- ll_time = last_login.ll_time;
315: if ((tm = localtime_r (_time, _buf)) != NULL) {
316- strftime (the_time, sizeof (the_time),
317- /* TRANSLATORS: "strftime options for date of last
login" */
--
574-
575- lf_time = utuser.ut_tv.tv_sec;
576: tm = localtime_r (_time, _buf);
577- strftime (the_time, sizeof (the_time),
578- /* TRANSLATORS: "strftime options for date of last login" */
Case 1 (line 315) is properly handled, but not case 2 (line 576).
The second case got fixed by:
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c
This fix should be included in Ubuntu (and Debian).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2045250/+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 1735002] Re: Allow configuring Wi-Fi MAC Randomization feature from GUI
** Changed in: gnome-control-center Status: Unknown => New -- 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/1735002 Title: Allow configuring Wi-Fi MAC Randomization feature from GUI Status in gnome-control-center: New Status in NetworkManager: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: Recent versions of NetworkManager have a feature enabled by default to use a random MAC address when scanning for available Wi-Fi networks for privacy. My understanding is that the spoofed MAC address is not used when actually connecting to a network. This feature was disabled in Ubuntu 17.10 because it broke scanning with some Wi-Fi drivers. My understanding is that there is a bug in some drivers when attempting to change the MAC address. See LP: #1681513. The bug might not be as big of an issue with the latest version of NetworkManager because 1) There are helpful commits like this (it was not backported to 17.04): https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=46d53e1 2) It is also possible now to selectively disable Wi-Fi MAC Randomization for specific drivers. https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b869d9 However, I'm really hesitant to re-enable this feature as long as A) we don't know for sure which drivers are affected, B) and more importantly, there is no GUI way to turn the feature on or off. Asking users to edit config files isn't very nice. The MAC Address Randomization feature is really nice (Windows 10 has a similar feature) but I think we need a GUI on/off switch in Settings > Wi-Fi or Settings > Privacy. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1735002/+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 1735002] Re: Allow configuring Wi-Fi MAC Randomization feature from GUI
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #743 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/743 ** Changed in: gnome-control-center Importance: Wishlist => Unknown ** Changed in: gnome-control-center Status: Confirmed => Unknown ** Changed in: gnome-control-center Remote watch: GNOME Bug Tracker #781295 => gitlab.gnome.org/GNOME/gnome-control-center/-/issues #743 -- 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/1735002 Title: Allow configuring Wi-Fi MAC Randomization feature from GUI Status in gnome-control-center: Unknown Status in NetworkManager: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: Recent versions of NetworkManager have a feature enabled by default to use a random MAC address when scanning for available Wi-Fi networks for privacy. My understanding is that the spoofed MAC address is not used when actually connecting to a network. This feature was disabled in Ubuntu 17.10 because it broke scanning with some Wi-Fi drivers. My understanding is that there is a bug in some drivers when attempting to change the MAC address. See LP: #1681513. The bug might not be as big of an issue with the latest version of NetworkManager because 1) There are helpful commits like this (it was not backported to 17.04): https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=46d53e1 2) It is also possible now to selectively disable Wi-Fi MAC Randomization for specific drivers. https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b869d9 However, I'm really hesitant to re-enable this feature as long as A) we don't know for sure which drivers are affected, B) and more importantly, there is no GUI way to turn the feature on or off. Asking users to edit config files isn't very nice. The MAC Address Randomization feature is really nice (Windows 10 has a similar feature) but I think we need a GUI on/off switch in Settings > Wi-Fi or Settings > Privacy. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1735002/+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 2046365] Re: package linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
I received the same error message but this was not immediately after a system update - I updated with the auto updater about 24 hours prior. The error message was the result of sudo apt-get update && sudo apt upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2046365 Title: package linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After normal, auto update of system. Got an alert that there is software to be updated and I proceed. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Dec 13 19:17:21 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2023-08-17 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2046365/+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 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
Thanks @onestory-studio, that's a very good idea. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: Triaged Status in software-properties source package in Mantic: Confirmed Bug description: Test Case - From Ubuntu 23.10: sudo apt install hello sudo add-apt-repository ppa:jbicha/temp sudo apt upgrade apt policy hello sudo ppa-purge ppa:jbicha/temp apt policy hello reveals that the PPA version of hello is still installed Also /etc/apt/sources.list.d/jbicha-ubuntu-temp-mantic.sources is still present and active What Should Happen -- ppa-purge should disable the PPA and reinstall any PPA packages with the version apt currently sees. Background -- add-apt-repository creates deb822 sources lists, starting in Ubuntu 23.10 https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by- default/29333 Other Info -- add-apt-repository has a --remove option But it does not do the reinstall part which is important Honestly, that feature is so important, I suggest that add-apt-repository take over the functionality of ppa-purge so that we always get the ppa-purge behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761/+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 2046365] Re: package linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2046365 Title: package linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After normal, auto update of system. Got an alert that there is software to be updated and I proceed. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Dec 13 19:17:21 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2023-08-17 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2046365/+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]
For add info about the laptop Legion S7 16ARHA7 ( https://psref.lenovo.com/Detail/Legion/Legion_S7_16ARHA7?M=82UG0029SP ) cat /sys/class/sound/hwC1D0/subsystem_id 0xaa0100 Alsainfo in the comment 700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
I'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. -- 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 2036253] Re: FTBFS: missing strl* symbols fail the build
This bug was fixed in the package heimdal -
7.8.git20221117.28daf24+dfsg-3ubuntu2
---
heimdal (7.8.git20221117.28daf24+dfsg-3ubuntu2) noble; urgency=medium
* d/lib{kafs0,roken19}-heimdal.symbols:
- _{kafs,rk}_strl{cat,cpy} are made optional symbols, since they
are not needed when built against glibc 2.38 (LP: #2036253).
- Make symbol dependencies on libroken19-heimdal and libkafs0-heimdal
strict to avoid future symbol skew.
* d/control: Declare Breaks: against older packages using these symbols.
-- Miriam España Acebal Wed, 29 Nov 2023
12:55:12 +0100
** Changed in: heimdal (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
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:
[SRU - Template WIP]
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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 1956127] Re: xorg metapackage requires xorg-docs-core
*** This bug is a duplicate of bug 1956126 *** https://bugs.launchpad.net/bugs/1956126 ** Description changed: - xorg, a required dependency of ubuntu-desktop and ubuntu-desktop-minimal - requires the package xorg-docs-core. Currently Ubuntu 22.04 Jammy - defaults to Wayland. These docs are ancient and now most people won't - even be using X11, much less this documentation. Why is x11-docs-core - going to be required in April of 2022? + xorg requires the package xorg-docs-core. Wayland is the default. Why is + documentation required for something that isn't the default? ** Tags added: noble -- 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/1956127 Title: xorg metapackage requires xorg-docs-core Status in xorg package in Ubuntu: New Bug description: xorg requires the package xorg-docs-core. Wayland is the default. Why is documentation required for something that isn't the default? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1956127/+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 2046375] Re: gdb-dbgsym missing from jammy-updates
** Package changed: ubuntu => gdb (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2046375 Title: gdb-dbgsym missing from jammy-updates Status in gdb package in Ubuntu: New Bug description: gdb is in http://archive.ubuntu.com/ubuntu/dists/jammy- updates/main/binary-amd64/Packages.gz: Package: gdb Architecture: amd64 Version: 12.1-0ubuntu1~22.04 But gdb-dbgsym is not in http://ddebs.ubuntu.com/dists/jammy- updates/main/binary-amd64/Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2046375/+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 2046375] [NEW] gdb-dbgsym missing from jammy-updates
You have been subscribed to a public bug: gdb is in http://archive.ubuntu.com/ubuntu/dists/jammy- updates/main/binary-amd64/Packages.gz: Package: gdb Architecture: amd64 Version: 12.1-0ubuntu1~22.04 But gdb-dbgsym is not in http://ddebs.ubuntu.com/dists/jammy- updates/main/binary-amd64/Packages ** Affects: gdb (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- gdb-dbgsym missing from jammy-updates https://bugs.launchpad.net/bugs/2046375 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036253] Re: FTBFS: missing strl* symbols fail the build
While preparing SRU paperwork and test cases, checking that binaries using those symbols work ok ( beyond the installation and the built that was OK), I found problems like this: root@Nheimdal:~# aklog --help aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0 so a rebuild against this heimdal libraries of the binaries that uses those symbols is needed. ** Tags removed: block-proposed -- 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 Committed Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Committed Status in heimdal package in Debian: New Bug description: [SRU - Template WIP] 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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
** Tags added: block-proposed ** Description changed: + [SRU - Template WIP] + 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_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 + 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 Committed Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Committed Status in heimdal package in Debian: New Bug description: [SRU - Template WIP] 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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 2044127] Re: ubuntu-but does not accept "program" paramater as documented in --help
Thanks for helping me - yes, that clarifies it. Maybe exactly the sentence you write here to explain it to me would be good to have in the --help and man page? Closer to the root, to me, these things that are referred to as "symptom" are more an "area of occurence" where the symptoms appear. For example, a symptom to me would be "broken and distorted sound" - not "sound". I assume that it's not an option / easy to rename this completely, at least it's not just a documentation rephrasing and needs changes in many places. But maybe it's something that could be taken in consideration for sometime in the future. -- 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/2044127 Title: ubuntu-but does not accept "program" paramater as documented in --help Status in apport package in Ubuntu: New Bug description: ubuntu-bug --help says $ ubuntu-bug --help usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash file] which suggest I can type a symptom after "ubuntu-bug" that I want to report. But doing something like: $ ubuntu-bug "Ubuntu Software tells me at every boot that it installed important OS update 'UEFI dbx'" only results in the error: dpkg-query: no packages found matching Ubuntu The man page of ubuntu-bug states that the symptoms are asked for when I run "ubuntu-bug" without parameters. So the --help output is wrong or the program is lacking some fallback if the message given as sysmptom is neither a pid, nor a package name nor a program path nor a crash file, the given parameter must be accepted as a symptom description. Probably the easiest part to solve that is to remove the nonworking symptom parameter from the --help output as long as that is not working. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-1015.15-lowlatency 6.2.16 Uname: Linux 6.2.0-1015-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 14:31:49 2023 InstallationDate: Installed on 2023-08-21 (92 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: Upgraded to mantic on 2023-11-05 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2044127/+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
Hi Isaac, I see your ping at http://lists.busybox.net/pipermail/busybox/2023-July/090414.html got no replies yet :( Have you tried contacting upstream through other means such as filing a bug in their bug tracker (https://bugs.busybox.net/) ? As mentioned above, it would be nice to understand how we should deal with this potential delta in the future. > Resubscribing ubuntu-sponsors as I've had no response from the mailing list In this case, I suppose replying to Christian's request: > - a good explanation why you think that wouldn't lock us in into hard to maintain delta and issues to users is still pending. Also, the debdiff should be updated to target noble and rebased on 1:1.36.1-6ubuntu1 which is the version in noble-proposed ATM. -- 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
[Touch-packages] [Bug 2046367] [NEW] AlphaSSL SHA256 G4 Intermediate Certificate missing
Public bug reported: Please add AlphaSSL SHA256 G4 Intermediate Certificate into ca- certificates. https://support.globalsign.com/ca-certificates/intermediate- certificates/alphassl-intermediate-certificates ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New -- 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: New 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 2033139] Re: ubuntu-desktop{-minimal} still depending on ghostscript-x package
https://launchpad.net/ubuntu/+source/ubuntu-meta/1.526
** Changed in: ubuntu-meta (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: ghostscript (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2033139
Title:
ubuntu-desktop{-minimal} still depending on ghostscript-x package
Status in ghostscript package in Ubuntu:
Fix Released
Status in ubuntu-meta package in Ubuntu:
Fix Released
Bug description:
The packages ubuntu-desktop and ubuntu-desktop-minimal still depend on
package ghostscript-x, but it's a dummy package that just points for the
package ghostscript.
So the idea is to change the dependency so the dummy package ghostscript-x
can be removed safely.
Description: Ubuntu Mantic Minotaur (development branch)
Release: 23.10
Packages version: 1.516
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/2033139/+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 2046365] [NEW] package linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: After normal, auto update of system. Got an alert that there is software to be updated and I proceed. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Dec 13 19:17:21 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2023-08-17 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2046365 Title: package linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: After normal, auto update of system. Got an alert that there is software to be updated and I proceed. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Dec 13 19:17:21 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2023-08-17 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2046365/+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
Thanks, Aleksandr. I am unsubscribing ubuntu-sponsors until https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/comments/21 is addressed. Please subscribe it back here when it is done. -- 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 2033139] Re: ubuntu-desktop{-minimal} still depending on ghostscript-x package
ghostscript-x was deleted in Noble. It shows as a dependency in ubuntu-desktop
and ubuntu-desktop-minimal packaging.
https://packages.ubuntu.com/noble/ubuntu-desktop-minimal
ghostscript-x wasn't deleted in Mantic.
https://packages.ubuntu.com/mantic/ghostscript-x
** Tags added: noble ubuntu-meta
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2033139
Title:
ubuntu-desktop{-minimal} still depending on ghostscript-x package
Status in ghostscript package in Ubuntu:
Confirmed
Status in ubuntu-meta package in Ubuntu:
Confirmed
Bug description:
The packages ubuntu-desktop and ubuntu-desktop-minimal still depend on
package ghostscript-x, but it's a dummy package that just points for the
package ghostscript.
So the idea is to change the dependency so the dummy package ghostscript-x
can be removed safely.
Description: Ubuntu Mantic Minotaur (development branch)
Release: 23.10
Packages version: 1.516
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/2033139/+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 added: rls-nn-incoming -- 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 2046116] Re: bluetooth device connected but not recognised as output device
hi @werdem o/ What bluetooth device are you using? Your version of BlueZ has a security patch for vulnerability CVE-2023-45866 which disables support for certain legacy bluetooth devices. If your device does not support Classic Bonding, you can re-enable it by setting `ClassicBondedOnly=false` in `/etc/bluetooth/input.conf`, and then running `systemctl restart bluetooth`. More info in https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/comments/6 Please let me know if that enables your device. Keep in mind that enabling legacy devices enables the exploit. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866 -- 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 2042587] Re: jammy's version breaks existing dhcp scripts with relay
** Changed in: dnsmasq (Ubuntu Jammy) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: dnsmasq (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: New Status in dnsmasq source package in Jammy: Triaged Bug description: When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Thank you for the clarification! I'll remove the regression-update tag then, since this is the intended behaviour of the security update, so it shouldn't count towards regression statistics. ** Tags removed: regression-update -- 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/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2039104] Please test proposed package
Hello Steve, or anyone else affected, Accepted ubuntu-settings into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- settings/23.10.5.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Mantic: Fix Committed Bug description: [SRU Justification] In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). [Test case] No testing is planned beyond any autopkgtests which may be none (the package itself doesn't have any). This should not be released to -updates on its own, but should be staged in -proposed so any future SRUs needed don't fail to copy due to out-of-date packages. [Where problems may occur] It is unlikely but possible that the removal of the raspi binary package from this source package will have inadvertently modified the contents of the other remaining binary packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
> It is unlikely but possible that the removal of the raspi binary package from this source package will have inadvertently modified the contents of the other remaining binary packages. It might be worth running a binary debdiff for SRU verification then, against the binary packages built in proposed, to ensure that the change only contains what we expect? ** Changed in: ubuntu-settings (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Mantic: Fix Committed Bug description: [SRU Justification] In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). [Test case] No testing is planned beyond any autopkgtests which may be none (the package itself doesn't have any). This should not be released to -updates on its own, but should be staged in -proposed so any future SRUs needed don't fail to copy due to out-of-date packages. [Where problems may occur] It is unlikely but possible that the removal of the raspi binary package from this source package will have inadvertently modified the contents of the other remaining binary packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Hello all o/ This is intentional. And easy to reverse. The patch for CVE-2023-45866 works as intended and is not a regression. https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/profiles/input?id=25a471a83e02e1effb15d5a488b3f0085eaeb675 If ClassicBondedOnly is not enforced, a nearby attacker can create a HID (like a keyboard and mouse) on the victims PC when bluetooth is discoverable. An HID can be used as a keyloggers or, of course, give direct control of the session. The CVE reporter has discussed this further on https://github.com/skysafe/reblog/tree/main/cve-2023-45866 And a talk and PoC release is forthcoming. Fortunately, it is easy to enable legacy devices by setting `ClassicBondedOnly=false` in `/etc/bluetooth/input.conf`, and then running `systemctl restart bluetooth`. I ver ified that a PS3 controller works well after this :) All other distros *should* be fixing this CVE. I would love it if bloggers in the Linux gaming sphere could raise awareness about this CVE and share how to enable legacy bluetooth device support. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866 ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: bluez (Ubuntu) Assignee: Nishit Majithia (0xnishit) => Mark Esler (eslerm) -- 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/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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] [NEW] Update URL for Support information in MOTD message
Public bug reported: 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 ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Focal) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Xenial) Importance: Undecided Status: New ** Summary changed: - Update URL for Support information for MOTD message + Update URL for Support information in MOTD message -- 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 2045033] Re: Merge rsyslog 8.2312.0-1 from Debian
Debian has released rsyslog 8.2312.0-1 -- 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
Miriam, please adapt the bug description to follow the SRU bug template https://wiki.ubuntu.com/StableReleaseUpdates -- 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 Committed Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Committed Status in heimdal package in Debian: New Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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
Resubscribing ubuntu-sponsors as I've had no response from the mailing list -- 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
[Touch-packages] [Bug 2036253] Re: FTBFS: missing strl* symbols fail the build
both sponsored after some nitpicks changed -- 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 Committed Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Committed Status in heimdal package in Debian: New Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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
** Changed in: heimdal (Ubuntu Noble) Status: In Progress => Fix Committed ** Changed in: heimdal (Ubuntu Mantic) Status: New => Fix Committed -- 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 Committed Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Committed Status in heimdal package in Debian: New Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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 2040384] Re: Merge heimdal from Debian unstable for noble
** Changed in: heimdal (Ubuntu)
Status: New => Fix Released
--
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/2040384
Title:
Merge heimdal from Debian unstable for noble
Status in heimdal package in Ubuntu:
Fix Released
Bug description:
Upstream: tbd
Debian: 7.8.git20221117.28daf24+dfsg-3
Ubuntu: 7.8.git20221117.28daf24+dfsg-3ubuntu1
Debian does new releases regularly, so it's likely there will be newer
versions available before FF that we can pick up if this merge is done
later in the cycle.
If it turns out this needs a sync rather than a merge, please change
the tag 'needs-merge' to 'needs-sync', and (optionally) update the
title as desired.
### New Debian Changes ###
heimdal (7.8.git20221117.28daf24+dfsg-3) unstable; urgency=medium
* Fix random 'Ticket expired' and 'Clock skew too great' errors by setting
kdc_offset correctly. Closes: #1039992.
-- Brian May Tue, 04 Jul 2023 10:09:56 +1000
heimdal (7.8.git20221117.28daf24+dfsg-2) unstable; urgency=medium
* Fix incorrect license of Debian files.
* Fix deprecated dependancies.
* gsskrb5: fix accidental logic inversions (CVE-2022-45142)
(Closes: #1030849) - change applied from NMU version
7.8.git20221117.28daf24+dfsg-1.1
* Add ro.po file. Closes: #1031897.
-- Brian May Sat, 25 Feb 2023 09:32:57 +1100
heimdal (7.8.git20221117.28daf24+dfsg-1) unstable; urgency=medium
* New upstream release.
-- Brian May Sat, 10 Dec 2022 16:29:20 +1100
heimdal (7.8.git20221115.a6cf945+dfsg-3) unstable; urgency=medium
* Source-only upload to enable migration to testingi (2nd attempt).
-- Brian May Sun, 04 Dec 2022 09:56:06 +1100
heimdal (7.8.git20221115.a6cf945+dfsg-2) unstable; urgency=medium
* Source-only upload to enable migration to testing.
-- Brian May Sun, 04 Dec 2022 09:09:44 +1100
heimdal (7.8.git20221115.a6cf945+dfsg-1) unstable; urgency=medium
* New upstream version.
* Numerous security fixes (Closes: #1024187).
* asn1: Invalid free in ASN.1 codec (CVE-2022-44640)
* krb5: PAC parse integer overflows (CVE-2022-42898)
* gsskrb5: Use constant-time memcmp() for arcfour unwrap (CVE-2022-3437)
* gsskrb5: Use constant-time memcmp() in unwrap_des3() (CVE-2022-3437)
* gsskrb5: Don't pass NULL pointers to memcpy() in DES unwrap
(CVE-2022-3437)
* gsskrb5: Avoid undefined behaviour in _gssapi_verify_pad()
(CVE-2022-3437)
* gsskrb5: Check the result of _gsskrb5_get_mech() (CVE-2022-3437)
* gsskrb5: Check buffer length against overflow for DES{,3} unwrap
(CVE-2022-3437)
* gsskrb5: Check for overflow in _gsskrb5_get_mech() (CVE-2022-3437)
* gsskrb5: Pass correct length to _gssapi_verify_pad() (CVE-2022-3437)
* libhx509: Fix denial of service vulnerability (CVE-2022-41916)
* spnego: send_reject when no mech selected (CVE-2021-44758)
* Fix regression in _krb5_get_int64 on 32 bit systems.
https://github.com/heimdal/heimdal/pull/1025
* Increment soname for libroken.
* Increment soname for libhcrypto.
* Remove legacy shared library version requirements.
* Add symbols to libkadm5srv8.
-- Brian May Sun, 27 Nov 2022 10:44:26 +1100
heimdal (7.7.0+dfsg-6) unstable; urgency=medium
* Retry deleting dangling windc.so again. Closes: #857215.
* Create /var/lib/heimdal-kdc/m-key not /var/lib/heimdal-kdc/heimdal.mkey.
Closes: #964008.
* Disable use of -rpath in krb5-config.heimdal. Closes: #868840.
-- Brian May Mon, 05 Sep 2022 08:35:33 +1000
heimdal (7.7.0+dfsg-5) unstable; urgency=medium
* Fix missing closefrom symbol. Closes: #1016884, #1017244.
* Fix spelling of dependency in changelog.
* Fix override_dh_fixperms typo, use 700 for /var/lib/heimdal-kdc/
* Remove default --parallel from dh call.
* Remove unused debian/upstream/signing-key.asc key.
* Fix Multi-Arch headers. heimdal-multidev is not co-installable, so
heimdal-dev cannot be co-installable either.
-- Brian May Fri, 02 Sep 2022 07:59:59 +1000
heimdal (7.7.0+dfsg-4) unstable; urgency=medium
* Delete dependency on install-info. Closes: #1013735.
* Non-maintainer upload.
* Reduce Build-Depends: (Closes: #980531)
+ Drop unused libhesiod-dev.
+ Drop unused libperl4-corelibs-perl as cf/make-proto.pl no longer uses
it.
+ Drop unused libx11-dev, libxau-dev, libxt-dev, ss-dev, and
x11proto-core-dev.
+ Clean generated C tables to actually rebuild them using python3.
-- Brian May Mon, 27 Jun 2022 10:36:10 +1000
heimdal (7.7.0+dfsg-3) unstable; urgency=high
### Old Ubuntu Delta ###
heimdal (7.8.git20221117.28daf24+dfsg-3ubuntu1) mantic; urgency=medium
* Merge from Debian unstable. Remaining changes:
- d/rules: Disable lto,
[Touch-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
Excellent, thanks Danilo for the super fast fix! ⭐
--
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/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 addresses
Status in netplan.io package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Invalid
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
"2001::1"]. Notably the addresses do *not* have a netmask, neither in
the original config nor that update. Unfortunately that update cannot
be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config
for the IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is
not added on this call. The netplan backend should do that (not
second-guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch
it together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2046158/+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
** Changed in: heimdal (Ubuntu Mantic) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- 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: In Progress Status in heimdal source package in Mantic: New Status in heimdal source package in Noble: In Progress Status in heimdal package in Debian: New Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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
** Also affects: heimdal (Ubuntu Noble) Importance: Undecided Assignee: Miriam España Acebal (mirespace) Status: In Progress ** Also affects: heimdal (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2036253 Title: FTBFS: missing strl* symbols fail the build Status in heimdal package in Ubuntu: In Progress Status in heimdal source package in Mantic: New Status in heimdal source package in Noble: In Progress Status in heimdal package in Debian: New Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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
** Summary changed: - Merge rsyslog 8.2310.0-2 from Debian + Merge rsyslog 8.2312.0-1 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 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
Hi Martin, thanks so much for your bug report.
I can confirm it's a problem in libnetplan. I created a small fix for it
https://github.com/canonical/netplan/pull/428
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
** Changed in: netplan.io (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 addresses
Status in netplan.io package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Invalid
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
"2001::1"]. Notably the addresses do *not* have a netmask, neither in
the original config nor that update. Unfortunately that update cannot
be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config
for the IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is
not added on this call. The netplan backend should do that (not
second-guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch
it together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.2
To manage notifications about this bug go to:
[Touch-packages] [Bug 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable
Fixed. ** Description changed: [Impact] When working with ubuntu core or ubuntu core desktop, neither */etc/default/locale* nor */etc/default/keyboard* are modifiable, so it's not possible to set the global keyboard or the global language. This is required to allow to set the GDM language, and the default one during installation. The first half of the solution is to create the folder */etc/writable/default*, and make soft-links from */etc/default/locale* to */etc/writable/default/locale* and from */etc/default/keyboard* to */etc/writable/default/keyboard*, just like it is already being done with */etc/hostname*, */etc/issue*, */etc/localtime*, */etc/motd* and , */etc/timezone*. This solution, unfortunately, isn't complete. Although any application that just reads the files will work, not all of the applications that write to them will; specifically the systemd utilities that set the contents for those files, because they don't open the file directly; instead, they create first the new file in the same folder than the old one, fill its contents, and only then delete the old one and rename the new one. To solve this, systemd in Ubuntu already has several patches that detect if a file is a soft-link, in which case it replaces the old path with the destination one. Currently I have in place a patch for Ubuntu Core Desktop that implements both changes for both */etc/default/locale* and */etc/default/keyboard*. [Test plan] - Using *localectl set-lang LANG="xx_YY.UTF-8"* should change the locale - to the specified one. Also, *localectl* should return the current - locale. + Using *sudo localectl set-lang LANG="xx_YY.UTF-8"* in an Ubuntu Core or + Ubuntu Core Desktop admin terminal must change the locale to the + specified one, which can be checked by reading the */etc/default/locale* + file. Also, *localectl* must return the new locale. [Where problems could occur] In general, applications just read the content of the file and use the DBus interface to set the locale, so only those applications that modify by themselves the */etc/default/keyboard* and/or */etc/default/locale* would present a problem, in which case they would require specific patches. Anyway, those applications neither would work with the current state (with those files in a read-only filesystem). [Other info] For Noble, this will be addressed when we merge systemd v255 from Debian. This is only needed on core, so we don't need to fix for Mantic or Lunar. ** Changed in: systemd (Ubuntu Jammy) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2035122 Title: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable Status in systemd package in Ubuntu: New Status in systemd source package in Jammy: New Status in systemd source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Bug description: [Impact] When working with ubuntu core or ubuntu core desktop, neither */etc/default/locale* nor */etc/default/keyboard* are modifiable, so it's not possible to set the global keyboard or the global language. This is required to allow to set the GDM language, and the default one during installation. The first half of the solution is to create the folder */etc/writable/default*, and make soft-links from */etc/default/locale* to */etc/writable/default/locale* and from */etc/default/keyboard* to */etc/writable/default/keyboard*, just like it is already being done with */etc/hostname*, */etc/issue*, */etc/localtime*, */etc/motd* and , */etc/timezone*. This solution, unfortunately, isn't complete. Although any application that just reads the files will work, not all of the applications that write to them will; specifically the systemd utilities that set the contents for those files, because they don't open the file directly; instead, they create first the new file in the same folder than the old one, fill its contents, and only then delete the old one and rename the new one. To solve this, systemd in Ubuntu already has several patches that detect if a file is a soft-link, in which case it replaces the old path with the destination one. Currently I have in place a patch for Ubuntu Core Desktop that implements both changes for both */etc/default/locale* and */etc/default/keyboard*. [Test plan] Using *sudo localectl set-lang LANG="xx_YY.UTF-8"* in an Ubuntu Core or Ubuntu Core Desktop admin terminal must change the locale to the specified one, which can be checked by reading the */etc/default/locale* file. Also, *localectl* must return the new locale. [Where problems could occur] In general, applications just read the content of the file and use the DBus interface to set the locale, so
[Touch-packages] [Bug 2046336] Re: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
Here is a Merge Request with a possible patch: https://salsa.debian.org/kernel-team/klibc/-/merge_requests/12 -- 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
[Touch-packages] [Bug 2036253] Re: FTBFS: missing strl* symbols fail the build
Mmm... checking Steve's patch, he is including all the binaries packages from/inside krb5 with affected libraries (It makes sense, as a library is using a symbol from other, no matter who is the parent src...). I let myself be carried away by the comment on the heimdal's Debian bug that coincides mainly with the results on my previous comment. I drop the 'grep -v heimdal' and I'll use the resulting list then. -- 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: In Progress Status in heimdal package in Debian: New Bug 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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] [NEW] initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
Public bug reported: 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_simd16384 1 aesni_intel cryptd 28672 3 crypto_simd,ghash_clmulni_intel ecdh_generic 16384 2 bluetooth rapl 20480 0 ecc45056 1 ecdh_generic snd_seq_device 16384 2 snd_seq,snd_rawmidi crc16 12288 1 bluetooth snd_hda_core 147456 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek mc 94208 1 snd_usb_audio wmi_bmof 12288 0 snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec gigabyte_wmi 12288 0 sg 45056 0
[Touch-packages] [Bug 2036253] Re: FTBFS: missing strl* symbols fail the build
Checking if outside the package these symbols are being used by other
shared libraries:
* For libkafs0-heimdal: None
libroken19-heimdal: /usr/lib/x86_64-linux-gnu/libroken.so.19.0.0
root@Nheimdal:~# for s in $(for p in $(apt-cache rdepends libkafs0-heimdal |
grep -v heimdal | cut -d':' -f2 | xargs); do for l in $(apt-file list ${p} |
grep '.so' | grep lib | cut -d':' -f2| xargs); do readlink -f ${l} ; done; done
| sort -u); do nm -D ${s} | grep strlc && apt-file search ${s}; done
root@Nheimdal:~#
* For libroken19-heimdal: libafsauthent2 and libafsrpc2, both form
src:openafs
root@Nheimdal:~# for s in $(for p in $(apt-cache rdepends libroken19-heimdal |
grep -v heimdal | cut -d':' -f2 | xargs); do for l in $(apt-file list ${p} |
grep '.so' | grep lib | cut -d':' -f2| xargs); do readlink -f ${l} ; done; done
| sort -u); do nm -D ${s} | grep strlc && apt-file search ${s}; done
U rk_strlcat@HEIMDAL_ROKEN_1.0
U rk_strlcpy@HEIMDAL_ROKEN_1.0
libafsauthent2: /usr/lib/libafsauthent.so.2.0.0
U rk_strlcat@HEIMDAL_ROKEN_1.0
U rk_strlcpy@HEIMDAL_ROKEN_1.0
libafsrpc2: /usr/lib/libafsrpc.so.2.0.0
I will follow the same approach that in [1], for krb5.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043184#30
P.S. Sorry for the ugly and no-efficient inline bash, but for the
purpose of the fixing I think is OK, and I promise I'll do a pretty
script after Xmas (in case that doesn't exist yet, which I couldn't
say). for sure).
** Bug watch added: Debian Bug tracker #1043184
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043184
--
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:
In Progress
Status in heimdal package in Debian:
New
Bug 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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
