[Touch-packages] [Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
** Description changed: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - - mksbuild - - pbuilder whatever chroot management tool it has + - mk-sbuild + - pbuilder-dist $release create - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr - [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. -- 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/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: In Progress Status in debootstrap source package in Jammy: Fix Committed Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mk-sbuild - pbuilder-dist $release create - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: systemd (Ubuntu) Status: Won't Fix => In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: systemd (Ubuntu) Importance: Low => Medium -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1914409] Re: fsck integration is not flicker free
** Tags removed: flickerfree ** Tags added: flickerfreeboot -- 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/1914409 Title: fsck integration is not flicker free Status in systemd package in Ubuntu: New Bug description: Install Ubuntu desktop, with full disk LUKS encryption, on an UEFI system. On boot, ESP & rootfs will have fsck started. This flickers briefly that fsck are in progress, although most of the time both the ESP and rootfs fsck finish/exit instantly. It would be nice delaying to show fsck progress in plymouth until it takes a substantial amount of time and/or if there is progress about it. I.e. ideally it should not be shown if it takes less than a second to complete (or some other very quick threshold). As there is not enough to time to show the message that the fsck is in progress, for the human to read it, before the message is dissmissed again. One can see this as a flickerfree boot effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914409/+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-2 from Debian
** Changed in: rsyslog Status: Confirmed => Fix Released -- 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-2 from Debian Status in Rsyslog: Fix Released Status in rsyslog package in Ubuntu: Fix Released Bug description: Debian has released rsyslog 8.2310.0-4. Merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/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 2055176] Re: Apps crash out when switching windows and using VMWare Horizon
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2055176
Title:
Apps crash out when switching windows and using VMWare Horizon
Status in Ubuntu:
Incomplete
Bug description:
When using VMWare Horizon and quickly switching windows (alt-tab), the
Horizon app and other apps crashes (such as spotify (snap?) and zoom
(native deb)). I can see a Segmentation Fault error in syslog. I have
tried the last four versions of VMWare Horizon and have the same
results. This was never a problem with 23.10.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 27 14:50:55 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Dell WhiskeyLake-U GT2 [UHD Graphics 620] [1028:08e0]
InstallationDate: Installed on 2024-02-03 (24 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic
root=UUID=5f7a0ef6-50b2-480b-b0f3-1aed4dbdbd57 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2023
dmi.bios.release: 1.28
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.28.0
dmi.board.name: 0PYRY5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: NAB612163
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.28.0:bd11/03/2023:br1.28:svnDellInc.:pnLatitude7300:pvr:rvnDellInc.:rn0PYRY5:rvrA00:cvnDellInc.:ct10:cvr:sku08E0:
dmi.product.family: Latitude
dmi.product.name: Latitude 7300
dmi.product.sku: 08E0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2055176/+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 2055153] Re: Xorg freeze
Thanks for the bug report. Each time you experience a failed boot followed by a successful boot please run: journalctl -b-1 > failedboot.txt And each time you experience a slow boot please run: journalctl -b0 > slowboot.txt and attach the resulting text files here. ** Summary changed: - Xorg freeze + Boots slowly or not at all when NVIDIA driver is installed ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535 (Ubuntu) ** Also affects: nvidia-graphics-drivers-545 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags added: nvidia ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-545 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2055153 Title: Boots slowly or not at all when NVIDIA driver is installed Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-535 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-545 package in Ubuntu: Incomplete Bug description: I have booting related issue everytime I install NVIDIA-driver on Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would either (1) boot fine (25% of the time) (2) boot takes long time(about 2 min) (50% of the time) (3) boot fails (25% of the time) This symptom disappears when I uninstall NVIDIA driver so I'm pretty sure it is related to NVIDIA driver but I don't know how to fix it. For case (2) (boot takes long time), black screen with '/dev/nvme0n1p6: clean, *** files, *** blocks' hang for a long time. For case (3) (boot fails), blackscreen with 'iwlwifi : invalid buffer destination' 'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND' 'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error (AE_NOT_FOUND)' 'Bluetooth: hci0: Malformed MSFT vendor event: 0x02' 'INFO: task plymouthd: *** blocked for more than *** seconds' '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message' 'INFO: task gpu-manager: *** blocked for more than *** seconds' '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message' This screen appears and doesn't boot or blackscreen with cursor appears and doesn't boot. It happens quite randomly and it really is frustrating and want to resolve this issue. I've tried various things but it didn't work out. Here are some things I tried - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt install' - Installing different driver version(525, 535, 545) - trying boot-repair program - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot fails) - tried various kernel version with various Ubuntu version (my laptop is very new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly tried 22.04) However none of them seemed to resolve the problem I am facing. It showed different symptoms time-to-time but mostly all of them were boot-related. I am using a dualboot with windows I am kind of lost and kindly ask for help. Here are some of the specification that would be helpful Laptop: lenovo legion pro 7 16irx8h $ uname -a Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux $ lspci 00:00.0 Host bridge: Intel Corporation Device a702 (rev 01) 00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01) 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD Graphics (rev 04) 00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant (rev 01) 00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 01) 00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog and Telemetry (rev 01) 00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 Gb/s) XHCI Host Controller (rev 11) 00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11) 00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi (rev 11) 00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C Host Controller #0 (rev 11) 00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C Host Controller #1 (rev 11) 00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C Host Controller #2 (rev 11) 00:16.0 Communication controller: Intel
[Touch-packages] [Bug 2052399] Re: kbd is not built for i386
i386 is not supported as a standalone architecture in Ubuntu. ** Changed in: kbd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2052399 Title: kbd is not built for i386 Status in kbd package in Ubuntu: Won't Fix Bug description: kbd is not built for i386 which leads to Bug #1463840 dpkg: dependency problems prevent configuration of console-setup-linux: console-setup-linux depends on kbd (>= 0.99-12) | console-tools (>= 1:0.2.3-16); however: Package kbd is not installed. Package console-tools is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2052399/+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 2018996] Re: whoopsie uses 100% CPU indefinitely on chrome crash file
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: whoopsie (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/2018996 Title: whoopsie uses 100% CPU indefinitely on chrome crash file Status in whoopsie package in Ubuntu: Confirmed Bug description: $@ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 $@ apt-cache policy whoopsie whoopsie: Installed: 0.2.77 Candidate: 0.2.77 Version table: *** 0.2.77 500 500 http://jp.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status TL;DR whoopsie will happily consume 100% for hours in what seems like a pretty futile attempt to deal with massive crash files. It should be more aware of what is a realistic crash to upload. This has happened a couple of times today, so I searched, found https://askubuntu.com/questions/1245078/woopsie-upload-all-process- consumes-cpu-100/1296481#1296481 which suggested looking in /var/crash/ where I found $@ ls -lh /var/crash/ total 8.3G -rw-r- 1 fergal whoopsie 8.3G May 8 23:03 _opt_google_chrome_chrome.1000.crash I don't know what whoopsie was doing but I doubt that was ever going to be productive and I cannot have a service that is going to occasionally use 100% CPU for hours. Here's what `top` had to say before I killed it 94802 root 20 0 11.7g 11.3g 58624 R 100.0 36.6 108:11.76 whoopsie-upload So it had been trying for 108 minutes and was using 11G of RAM. I would love to enable crash reporting but this is unacceptable. I've deleted the crash file and uninstalled whoopsie. I'll happily reinstall it if it gains some safeguards against this kind of thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2018996/+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 2054924] Re: color emoji are broken with fontconfig 2.15
** Changed in: fontconfig (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2054924 Title: color emoji are broken with fontconfig 2.15 Status in Fontconfig: Fix Released Status in fontconfig package in Ubuntu: Triaged Status in fonts-noto-color-emoji package in Ubuntu: Triaged Status in fontconfig package in Debian: Confirmed Bug description: The Noto Color Emoji font is no longer used to show emoji. Many emoji no longer show and the few that do are not in color. To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 2026757] Related fix merged to ironic (master)
Reviewed: https://review.opendev.org/c/openstack/ironic/+/888121 Committed: https://opendev.org/openstack/ironic/commit/27f53debb6800d9552510d44957b4d7d6292eaf5 Submitter: "Zuul (22348)" Branch:master commit 27f53debb6800d9552510d44957b4d7d6292eaf5 Author: yatinkarel Date: Tue Jul 11 14:44:06 2023 +0530 ci: Source install dnsmasq-2.87 dnsmasq-2.86 shipped in Ubuntu jammy has a known issue[1] which is fixed in dnsmasq-2.87 but it's not yet released with Ubuntu jammy. Until fixed version is available in Ubuntu jammy let's use source install instead of using a older version from Ubuntu focal. [1] https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q3/016562.html Update from Julia: Pushing forward the source fix again as ubuntu removed the prior path we were using as a focal package and replaced it with a package which is demonstrating the same basic issue. Related-Bug: #2026757 Change-Id: I7ffcd167fc1e3a8c1192d766743bb5620d85ef35 -- 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/2026757 Title: dnsmasq on Ubuntu Jammy crashes on neutron-dhcp-agent updates Status in Ironic: Triaged Status in neutron: New Status in dnsmasq package in Ubuntu: Invalid Status in dnsmasq source package in Jammy: Incomplete Status in dnsmasq source package in Kinetic: Won't Fix Status in dnsmasq source package in Lunar: Invalid Status in dnsmasq source package in Mantic: Invalid Bug description: The Ironic project's CI has been having major blocking issues moving to utilizing Ubuntu Jammy and with some investigation we were able to isolate the issues down to the dhcp updates causing dnsmasq to crash on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds similar to an issue known about to the dnsmasq maintainers, where dnsmasq would crash with updates occurring due to configuration refresh[0]. This resulted in us upgrading dnsmasq to the version which ships with Ubuntu Lunar. Which was no better. Dnsmasq still crashed upon record updates for addresses and ports getting configuration added/changed/removed. We later downgraded to the version of dnsmasq shipped in Ubuntu Focal, and dnsmasq stopped crashing and appeared stable enough to utilize for CI purposes. ** Kernel log from Ubuntu Jammy Package ** [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000] [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000] [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000] [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000] [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000] [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000] [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000] [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a **
[Touch-packages] [Bug 2055105] Re: please merge cron 3.0pl1-184 from debian unstable
piuparts install/upgrade/purge test (pass) ** Attachment added: "piutest-cron.log.gz" https://bugs.launchpad.net/ubuntu/+source/cron/+bug/2055105/+attachment/5749964/+files/piutest-cron.log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/2055105 Title: please merge cron 3.0pl1-184 from debian unstable Status in cron package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/2055105/+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 2054924] Re: color emoji are broken with fontconfig 2.15
** Changed in: fontconfig (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2054924 Title: color emoji are broken with fontconfig 2.15 Status in Fontconfig: Fix Released Status in fontconfig package in Ubuntu: Confirmed Status in fonts-noto-color-emoji package in Ubuntu: Triaged Status in fontconfig package in Debian: Confirmed Bug description: The Noto Color Emoji font is no longer used to show emoji. Many emoji no longer show and the few that do are not in color. To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 2055233] [NEW] [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] No sound at all
Public bug reported: sound work if rechanging to Analog Stereo Duplex. but after sound file finish it broken again ! ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu6 ProcVersionSignature: Ubuntu 6.6.0-14.14.1-lowlatency 6.6.3 Uname: Linux 6.6.0-14-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Feb 28 02:39:07 2024 InstallationDate: Installed on 2024-01-12 (46 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240112) MachineType: MSI MS-7850 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative successful Symptom_Card: CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus] (SB1570 SB Audigy Fx) - HDA Creative Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2055233 Title: [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: sound work if rechanging to Analog Stereo Duplex. but after sound file finish it broken again ! ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu6 ProcVersionSignature: Ubuntu 6.6.0-14.14.1-lowlatency 6.6.3 Uname: Linux 6.6.0-14-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Feb 28 02:39:07 2024 InstallationDate: Installed on 2024-01-12 (46 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240112) MachineType: MSI MS-7850 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative successful Symptom_Card: CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus] (SB1570 SB Audigy Fx) - HDA Creative Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7850, Creative Sound Blaster Z, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2055233/+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 2026757] Related fix proposed to ironic (stable/2023.2)
Related fix proposed to branch: stable/2023.2 Review: https://review.opendev.org/c/openstack/ironic/+/910444 -- 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/2026757 Title: dnsmasq on Ubuntu Jammy crashes on neutron-dhcp-agent updates Status in Ironic: Triaged Status in neutron: New Status in dnsmasq package in Ubuntu: Invalid Status in dnsmasq source package in Jammy: Incomplete Status in dnsmasq source package in Kinetic: Won't Fix Status in dnsmasq source package in Lunar: Invalid Status in dnsmasq source package in Mantic: Invalid Bug description: The Ironic project's CI has been having major blocking issues moving to utilizing Ubuntu Jammy and with some investigation we were able to isolate the issues down to the dhcp updates causing dnsmasq to crash on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds similar to an issue known about to the dnsmasq maintainers, where dnsmasq would crash with updates occurring due to configuration refresh[0]. This resulted in us upgrading dnsmasq to the version which ships with Ubuntu Lunar. Which was no better. Dnsmasq still crashed upon record updates for addresses and ports getting configuration added/changed/removed. We later downgraded to the version of dnsmasq shipped in Ubuntu Focal, and dnsmasq stopped crashing and appeared stable enough to utilize for CI purposes. ** Kernel log from Ubuntu Jammy Package ** [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000] [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000] [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000] [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000] [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000] [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000] [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000] [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a ** Kernel log entries from Ubuntu Lunar package ** [234724.842339] dnsmasq[409843]: segfault at fffd ip 7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000] [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [234784.918116] dnsmasq[410019]: segfault at fffd ip 7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000] [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [235022.163339] dnsmasq[410151]: segfault at fffd ip 7f21dd37f47e sp 7fff9bf416d0 error 5 in libc.so.6[7f21dd302000+195000]
[Touch-packages] [Bug 2055200] Re: tests-in-lxd is broken with latest autopkgtest version
Uploaded the fix to noble. ** Changed in: systemd (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2055200 Title: tests-in-lxd is broken with latest autopkgtest version Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Jammy: Triaged Status in systemd source package in Mantic: Won't Fix Bug description: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+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 2055200] Re: tests-in-lxd is broken with latest autopkgtest version
** Tags added: systemd-sru-next -- 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/2055200 Title: tests-in-lxd is broken with latest autopkgtest version Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Mantic: Won't Fix Bug description: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+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 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
This bug still exists on Ubuntu 23.10. HP Elitebook 840 G1. inxi -Fxz System: Kernel: 6.5.0-21-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME v: 45.2 Distro: Ubuntu 23.10 (Mantic Minotaur) Machine: Type: Laptop System: Hewlett-Packard product: HP EliteBook 840 G1 v: A3009DD10303 serial: Mobo: Hewlett-Packard model: 198F v: KBC Version 15.59 serial: BIOS: Hewlett-Packard v: L71 Ver. 01.46 date: 07/20/2018 Battery: ID-1: BAT0 charge: 42.8 Wh (94.7%) condition: 45.2/45.2 Wh (100.0%) volts: 13.0 min: 11.4 model: Hewlett-Packard Primary status: charging CPU: Info: dual core model: Intel Core i5-4300U bits: 64 type: MT MCP arch: Haswell rev: 1 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 2622 high: 2708 min/max: 800/2900 cores: 1: 2594 2: 2594 3: 2594 4: 2708 bogomips: 19952 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-7.5 bus-ID: 00:02.0 Device-2: Cheng Uei Precision Industry (Foxlink) HP HD Webcam driver: uvcvideo type: USB bus-ID: 2-7:3 Display: wayland server: X.Org v: 1.23.2 with: Xwayland v: 23.2.0 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1280x720~60Hz API: OpenGL v: 4.6 Mesa 23.2.1-1ubuntu3.1 renderer: Mesa Intel HD Graphics 4400 (HSW GT2) direct-render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard 8 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 API: ALSA v: k6.5.0-21-generic status: kernel-api Server-1: PipeWire v: 0.3.79 status: active Network: Device-1: Intel Ethernet I218-LM vendor: Hewlett-Packard driver: e1000e v: kernel port: 3080 bus-ID: 00:19.0 IF: enp0s25 state: down mac: Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel bus-ID: 02:00.0 IF: wlo1 state: up mac: IF-ID-1: docker0 state: down mac: Bluetooth: Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB bus-ID: 2-3.2:4 Report: hciconfig ID: hci0 rfk-id: 0 state: up address: bt-v: 4.0 lmp-v: 6 Drives: Local Storage: total: 119.24 GiB used: 72.01 GiB (60.4%) ID-1: /dev/sda vendor: Samsung model: MZ7PC128HAFU-000H1 size: 119.24 GiB Partition: ID-1: / size: 116.52 GiB used: 72.01 GiB (61.8%) fs: ext4 dev: /dev/sda4 Swap: ID-1: swap-1 type: file size: 4 GiB used: 127.2 MiB (3.1%) file: /swap.img Sensors: System Temperatures: cpu: 47.0 C mobo: N/A Fan Speeds (rpm): N/A Info: Processes: 268 Uptime: 2h 29m Memory: total: 8 GiB available: 7.65 GiB used: 5.26 GiB (68.8%) Init: systemd target: graphical (5) Compilers: gcc: 13.2.0 Packages: 2038 Shell: Bash v: 5.2.15 inxi: 3.3.29 -- 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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Expired Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16]
[Touch-packages] [Bug 2055200] Re: tests-in-lxd is broken with latest autopkgtest version
** Summary changed: - tests-in-lxd is broken on Jammy with latest autopkgtest version + tests-in-lxd is broken with latest autopkgtest version ** Also affects: systemd (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Mantic) Status: New => Won't Fix ** Changed in: systemd (Ubuntu Jammy) Status: New => Triaged ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/2055200 Title: tests-in-lxd is broken with latest autopkgtest version Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Mantic: Won't Fix Bug description: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+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 2055124] Re: WiFi adapter cannot get IP configuration from Netgear orbi RBR20
** Package changed: ubuntu => network-manager (Ubuntu) -- 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/2055124 Title: WiFi adapter cannot get IP configuration from Netgear orbi RBR20 Status in network-manager package in Ubuntu: New Bug description: Since a recent Ubuntu update (~6 weeks ago), my laptop cannot connect anymore to my Netgear Orbi RBR20 WiFi access point. The wifi connection is still working fine with my Android smartphone set as a WiFi access point. My other devices can connect successfully to the Orbi RBR20: printers, smartphones, TV, tablets, desktop, Sonos, Netatmo... Expected: - Get an IP address from the Netgear Orbi RBR20. Happened instead: - No IP address obtained, stuck with no WiFi connectivity. ThinkPad X13 Gen2 with Ubuntu 22.04.4 LTS: -- fred@ThinkPad:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename:jammy Mediatek WiFi adapter: -- *-network description: Interface réseau sans fil produit: MT7921 802.11ax PCI Express Wireless Network Adapter fabricant: MEDIATEK Corp. identifiant matériel: 0 information bus: pci@:03:00.0 nom logique: wlp3s0 nom logique: /dev/fb0 version: 00 numéro de série: 74:97:79:8a:36:e7 bits: 64 bits horloge: 33MHz fonctionnalités: pciexpress msi pm bus_master cap_list ethernet physical wireless fb configuration : broadcast=yes depth=32 driver=mt7921e driverversion=6.5.0-15-generic firmware=01-20220209150915 latency=0 link=yes mode=1920x1200 multicast=yes visual=truecolor wireless=IEEE 802.11 xres=1920 yres=1200 ressources : mémoireE/S:40-3f mémoireE/S:40-3f mémoireE/S:40-3f irq:87 mémoire:47020-4702f mémoire:47030-470303fff mémoire:470304000-470304fff No power saving: [connection] wifi.powersave = 2 Cannot obtain IP configuration: --- DEVICE TYPE STATE CONNECTION wlp3s0 wifi connexion (obtention de la configuration IP) ORBIchamprond Device association looks OK: [241460.865152] wlp3s0: authenticate with c2:a5:11:2f:00:c1 [241460.883343] wlp3s0: send auth to c2:a5:11:2f:00:c1 (try 1/3) [241460.886001] wlp3s0: authenticated [241460.887489] wlp3s0: associate with c2:a5:11:2f:00:c1 (try 1/3) [241460.991496] wlp3s0: associate with c2:a5:11:2f:00:c1 (try 2/3) [241461.016131] wlp3s0: RX AssocResp from c2:a5:11:2f:00:c1 (capab=0x1511 status=0 aid=1) [241461.046179] wlp3s0: associated RBR20 firmware version: v2.7.3.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055124/+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 2055124] [NEW] WiFi adapter cannot get IP configuration from Netgear orbi RBR20
You have been subscribed to a public bug: Since a recent Ubuntu update (~6 weeks ago), my laptop cannot connect anymore to my Netgear Orbi RBR20 WiFi access point. The wifi connection is still working fine with my Android smartphone set as a WiFi access point. My other devices can connect successfully to the Orbi RBR20: printers, smartphones, TV, tablets, desktop, Sonos, Netatmo... Expected: - Get an IP address from the Netgear Orbi RBR20. Happened instead: - No IP address obtained, stuck with no WiFi connectivity. ThinkPad X13 Gen2 with Ubuntu 22.04.4 LTS: -- fred@ThinkPad:~$ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy Mediatek WiFi adapter: -- *-network description: Interface réseau sans fil produit: MT7921 802.11ax PCI Express Wireless Network Adapter fabricant: MEDIATEK Corp. identifiant matériel: 0 information bus: pci@:03:00.0 nom logique: wlp3s0 nom logique: /dev/fb0 version: 00 numéro de série: 74:97:79:8a:36:e7 bits: 64 bits horloge: 33MHz fonctionnalités: pciexpress msi pm bus_master cap_list ethernet physical wireless fb configuration : broadcast=yes depth=32 driver=mt7921e driverversion=6.5.0-15-generic firmware=01-20220209150915 latency=0 link=yes mode=1920x1200 multicast=yes visual=truecolor wireless=IEEE 802.11 xres=1920 yres=1200 ressources : mémoireE/S:40-3f mémoireE/S:40-3f mémoireE/S:40-3f irq:87 mémoire:47020-4702f mémoire:47030-470303fff mémoire:470304000-470304fff No power saving: [connection] wifi.powersave = 2 Cannot obtain IP configuration: --- DEVICE TYPE STATE CONNECTION wlp3s0 wifi connexion (obtention de la configuration IP) ORBIchamprond Device association looks OK: [241460.865152] wlp3s0: authenticate with c2:a5:11:2f:00:c1 [241460.883343] wlp3s0: send auth to c2:a5:11:2f:00:c1 (try 1/3) [241460.886001] wlp3s0: authenticated [241460.887489] wlp3s0: associate with c2:a5:11:2f:00:c1 (try 1/3) [241460.991496] wlp3s0: associate with c2:a5:11:2f:00:c1 (try 2/3) [241461.016131] wlp3s0: RX AssocResp from c2:a5:11:2f:00:c1 (capab=0x1511 status=0 aid=1) [241461.046179] wlp3s0: associated RBR20 firmware version: v2.7.3.22 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment wifi -- WiFi adapter cannot get IP configuration from Netgear orbi RBR20 https://bugs.launchpad.net/bugs/2055124 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager 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 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
With the updated context, I think the proposal looks reasonable and would be comfortable sponsoring the upload. I suggest first waiting for the lvm2 merge to migrate, just to rule out issues on that front. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Noble: Confirmed Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is a problem when software like systemd via libcryptsetup try to open a volume, and get an unrecognizable error out of it. With the fix in libdm and libcryptsetup, there is a clear ENOKEY returned when a key is missing and activation fails for that reason. This allows systemd (and other applications) to make the right decision depending on the failure case. Without this, the same generic error is returned in any case. For more details, see: https://gitlab.com/cryptsetup/cryptsetup/-/issues/841 libcryptsetup 2.7.0, now available in debian stable, and systemd v255, shipped in Noble, make use of this error code. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+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 2055180] Re: coreutils 9.4-3ubuntu1 FTBFS
** Changed in: coreutils (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2055180 Title: coreutils 9.4-3ubuntu1 FTBFS Status in coreutils package in Ubuntu: Fix Committed Bug description: The recent upload FTBFS due to a build-time test failure[1]: FAIL: tests/cp/cp-i === --- err4 2024-02-26 18:03:34.566066156 + +++ err_skip 2024-02-26 18:03:34.554065852 + @@ -1 +1 @@ -cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead +cp: not replacing 'd' FAIL tests/cp/cp-i.sh (exit status: 1) This appears related to a new Debian patch that we pulled in with the merge. [1] https://launchpadlibrarian.net/716215295/buildlog_ubuntu-noble- amd64.coreutils_9.4-3ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2055180/+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 2055180] Re: coreutils 9.4-3ubuntu1 FTBFS
** Changed in: coreutils (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2055180 Title: coreutils 9.4-3ubuntu1 FTBFS Status in coreutils package in Ubuntu: In Progress Bug description: The recent upload FTBFS due to a build-time test failure[1]: FAIL: tests/cp/cp-i === --- err4 2024-02-26 18:03:34.566066156 + +++ err_skip 2024-02-26 18:03:34.554065852 + @@ -1 +1 @@ -cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead +cp: not replacing 'd' FAIL tests/cp/cp-i.sh (exit status: 1) This appears related to a new Debian patch that we pulled in with the merge. [1] https://launchpadlibrarian.net/716215295/buildlog_ubuntu-noble- amd64.coreutils_9.4-3ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2055180/+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 2055146] Re: Upgrade from Jammy to Noble breaks
This bug was fixed in the package dash - 0.5.12-6ubuntu4 --- dash (0.5.12-6ubuntu4) noble; urgency=medium * Update the link targets for /usr, fixing postinst (LP: #2055146) -- Julian Andres Klode Tue, 27 Feb 2024 12:29:41 +0100 ** Changed in: dash (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2055146 Title: Upgrade from Jammy to Noble breaks Status in dash package in Ubuntu: Fix Released Bug description: Hello there! Upgrading `dash` from Jammy to Noble is broken. Here is a quick reproducer: ``` podman pull ubuntu:jammy podman run -it --rm ubuntu:jammy sed -i 's/jammy/noble/' /etc/apt/sources.list apt update apt full-upgrade ``` This should end up with this error: ``` Setting up dash (0.5.12-6ubuntu3) ... Removing 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash' Removing 'diversion of /bin/sh to /bin/sh.distrib by dash' This should never be reached dpkg: error processing package dash (--configure): installed dash package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dash E: Sub-process /usr/bin/dpkg returned an error code (1) ``` As `dash` is pre-installed on almost every kind of Ubuntu, this breaks any upgrade from Jammy to Noble in practice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2055146/+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 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
** Merge proposal linked: https://code.launchpad.net/~bluca/ubuntu/+source/lvm2/+git/lvm2/+merge/461372 ** Merge proposal unlinked: https://code.launchpad.net/~bluca/ubuntu/+source/lvm2/+git/lvm2/+merge/460984 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Noble: Confirmed Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is a problem when software like systemd via libcryptsetup try to open a volume, and get an unrecognizable error out of it. With the fix in libdm and libcryptsetup, there is a clear ENOKEY returned when a key is missing and activation fails for that reason. This allows systemd (and other applications) to make the right decision depending on the failure case. Without this, the same generic error is returned in any case. For more details, see: https://gitlab.com/cryptsetup/cryptsetup/-/issues/841 libcryptsetup 2.7.0, now available in debian stable, and systemd v255, shipped in Noble, make use of this error code. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+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 2055200] [NEW] tests-in-lxd is broken on Jammy with latest autopkgtest version
Public bug reported: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "tests-in-lxd.debdiff" https://bugs.launchpad.net/bugs/2055200/+attachment/5749847/+files/tests-in-lxd.debdiff ** Description changed: - With autopkgtest 5.32 being SRU'd to Jammy, `tests-in-lxd` breaks + With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. + + [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 -- 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/2055200 Title: tests-in-lxd is broken on Jammy with latest autopkgtest version Status in systemd package in Ubuntu: New Bug description: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Changed in: angelfish (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2054924] Re: color emoji are broken with fontconfig 2.15
** Changed in: fontconfig (Debian) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2054924 Title: color emoji are broken with fontconfig 2.15 Status in Fontconfig: Fix Released Status in fontconfig package in Ubuntu: Triaged Status in fonts-noto-color-emoji package in Ubuntu: Triaged Status in fontconfig package in Debian: Confirmed Bug description: The Noto Color Emoji font is no longer used to show emoji. Many emoji no longer show and the few that do are not in color. To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
** Description changed: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. + + This is a problem when software like systemd via libcryptsetup try to + open a volume, and get an unrecognizable error out of it. With the fix + in libdm and libcryptsetup, there is a clear ENOKEY returned when a key + is missing and activation fails for that reason. This allows systemd + (and other applications) to make the right decision depending on the + failure case. Without this, the same generic error is returned in any + case. + + For more details, see: + + https://gitlab.com/cryptsetup/cryptsetup/-/issues/841 + + libcryptsetup 2.7.0, now available in debian stable, and systemd v255, + shipped in Noble, make use of this error code. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Noble: Confirmed Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is a problem when software like systemd via libcryptsetup try to open a volume, and get an unrecognizable error out of it. With the fix in libdm and libcryptsetup, there is a clear ENOKEY returned when a key is missing and activation fails for that reason. This allows systemd (and other applications) to make the right decision depending on the failure case. Without this, the same generic error is returned in any case. For more details, see: https://gitlab.com/cryptsetup/cryptsetup/-/issues/841 libcryptsetup 2.7.0, now available in debian stable, and systemd v255, shipped in Noble, make use of this error code. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+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 2055194] [NEW] Invalid version: 'None' when re-installing/upgrading python-apt using pip when wheel module installed
Public bug reported:
[ Impact ]
* It is not possible to upgrade or re-install python-apt using pip from
the git+ssh://git.launchpad.net/ubuntu/+source/python-apt git repo if
already installed and if wheel installed too.
* On initial install it also is assigned version `0.0.0` which is
incorrect
* This applies to the Mantic, Jammy and earlier versions. It has been
fixed in Noble
[ Test Plan ]
* Attempt re-install of python-apt
[ Where problems could occur ]
* Being unable to install python-apt
* Being unable to upgrade python-apt
* Being unable to re-install python-apt
[ Other Info ]
* This been resolved upstream @ https://salsa.debian.org/apt-
team/python-apt/-/commit/765772fad2d3611b952b6ad416c6b765739a902a and in
`2.4.y` branch @ https://salsa.debian.org/apt-team/python-
apt/-/tree/2.4.y?ref_type=heads
* You can workaround this too by setting environment variable
`DEBVER=2.4.11`
* Reproducer
```
❯ python3 -m venv venv
❯ source venv/bin/activate
❯ python3 -m pip list
PackageVersion
-- ---
pip23.2
setuptools 68.1.2
❯ python3 -m pip install --upgrade
git+ssh://git.launchpad.net/ubuntu/+source/python-apt@ubuntu/jammy-updates
Collecting
git+ssh://git.launchpad.net/ubuntu/+source/python-apt@ubuntu/jammy-updates
Cloning ssh://git.launchpad.net/ubuntu/+source/python-apt (to revision
ubuntu/jammy-updates) to ./pip-req-build-t7t8vnsu
Running command git clone --filter=blob:none --quiet
ssh://git.launchpad.net/ubuntu/+source/python-apt /tmp/pip-req-build-t7t8vnsu
warning: filtering not recognized by server, ignoring
warning: filtering not recognized by server, ignoring
Running command git checkout -b ubuntu/jammy-updates --track
origin/ubuntu/jammy-updates
Switched to a new branch 'ubuntu/jammy-updates'
branch 'ubuntu/jammy-updates' set up to track 'origin/ubuntu/jammy-updates'.
Resolved ssh://git.launchpad.net/ubuntu/+source/python-apt to commit
f043e6bd4d2842d6693d48e0c68c7a63bd3be9ac
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: python-apt
Building wheel for python-apt (pyproject.toml) ... done
Created wheel for python-apt:
filename=python_apt-0.0.0-cp311-cp311-linux_x86_64.whl size=1808770
sha256=472ff7d9bcdad50912dc42499d68bc5e958b9843c355c157ccf920021728c205
Stored in directory:
/tmp/pip-ephem-wheel-cache-nyc3gs5x/wheels/c7/db/d7/21a72eaa5719ab3ab1ca242d5d0e08aca4aa67eaddb3c9b8fa
Successfully built python-apt
Installing collected packages: python-apt
Successfully installed python-apt-0.0.0
❯ python3 -m pip list
PackageVersion
-- ---
pip23.2
python-apt 0.0.0
setuptools 68.1.2
# install wheel
❯ python3 -m pip install wheel
Collecting wheel
Obtaining dependency information for wheel from
https://files.pythonhosted.org/packages/c7/c3/55076fc728723ef927521abaa1955213d094933dc36d4a2008d5101e1af5/wheel-0.42.0-py3-none-any.whl.metadata
Using cached wheel-0.42.0-py3-none-any.whl.metadata (2.2 kB)
Using cached wheel-0.42.0-py3-none-any.whl (65 kB)
Installing collected packages: wheel
Successfully installed wheel-0.42.0
❯ python3 -m pip list
PackageVersion
-- ---
pip23.2
python-apt 0.0.0
setuptools 68.1.2
wheel 0.42.0
# Now try re-install
❯ python3 -m pip install --upgrade
git+ssh://git.launchpad.net/ubuntu/+source/python-apt@ubuntu/jammy-updates
Collecting
git+ssh://git.launchpad.net/ubuntu/+source/python-apt@ubuntu/jammy-updates
Cloning ssh://git.launchpad.net/ubuntu/+source/python-apt (to revision
ubuntu/jammy-updates) to ./pip-req-build-lk856i6s
Running command git clone --filter=blob:none --quiet
ssh://git.launchpad.net/ubuntu/+source/python-apt /tmp/pip-req-build-lk856i6s
warning: filtering not recognized by server, ignoring
warning: filtering not recognized by server, ignoring
Running command git checkout -b ubuntu/jammy-updates --track
origin/ubuntu/jammy-updates
Switched to a new branch 'ubuntu/jammy-updates'
branch 'ubuntu/jammy-updates' set up to track 'origin/ubuntu/jammy-updates'.
Resolved ssh://git.launchpad.net/ubuntu/+source/python-apt to commit
f043e6bd4d2842d6693d48e0c68c7a63bd3be9ac
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [34 lines of output]
Traceback (most recent call last):
File
"/tmp/venv/lib/python3.11/site-packages/setuptools/_normalization.py", line 59,
in safe_version
return str(packaging.version.Version(v))
File
"/tmp/venv/lib/python3.11/site-packages/setuptools/_vendor/packaging/version.py",
line 198, in __init__
raise InvalidVersion(f"Invalid version: '{version}'")
setuptools.extern.packaging.version.InvalidVersion: Invalid version:
'None'
During handling of the above exception,
[Touch-packages] [Bug 2055195] [NEW] KUbuntu ships an outdated version that breaks Google
Public bug reported: Adding an account gets stuck. Calendars won't update. https://bugs.kde.org/show_bug.cgi?id=420280 describes the details. Apparently installing a library convered from Fedora solves this. ** Affects: signon-ui (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/2055195 Title: KUbuntu ships an outdated version that breaks Google Status in signon-ui package in Ubuntu: New Bug description: Adding an account gets stuck. Calendars won't update. https://bugs.kde.org/show_bug.cgi?id=420280 describes the details. Apparently installing a library convered from Fedora solves this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/2055195/+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 2055193] [NEW] [FFe] APT 24.04 crypto policy update
Public bug reported:
I don't know if this will land before the feature freeze but I'm filing
this in any case:
Our goal for 24.04 is to reject 1024-bit RSA repository signing keys.
Work is ongoing in Launchpad to allow dual-signing PPAs and then resign
all PPAs with a 4096-bit key.
This needs the following changes:
1) The gnupg upstream commit for https://dev.gnupg.org/T6946 needs to be
backported. This is applying fine and in the package already, but the test
suite fails with issues that look weirdly unrelated.
2) APT needs to learn to pass the argument if supported
3) APT needs to learn to interpret the output
4) APT possibly may have to learn to issue warnings instead of errors for weak
keys and pass the URL to the gpgv method to allow 1024-bit RSA keys over TLS
connections, in case there are unforeseen issues with the PPA migration.
Signing key policy: We would like to adopt a signing key policy of
rsa>2048,ed25519,ed448
As a result we would like to reject
- RSA keys below 2048 bits
- DSA keys
- Unsafe ECC keys:
- NIST P-{256,384,521}
- Brainpool P-{256,384,512}
- secp256k1
Notes:
- DSA keys are not possible to use anymore due to the deprecation of SHA1 that
happened years ago
- NIST and Brainpool and secp256k1 are not very popular,
https://safecurves.cr.yp.to/ lists all of them as unsafe. It is believed they
have backdoors. Some FIPS customers may prefer them over Ed25519 and Ed448 as
they have been approved longer, so it's possible fips support packages could
reenable them by setting the correct apt.conf setting in a snippet.
Timing wrt feature freeze and launchpad changes:
Launchpad changes won't be landing before feature freeze and it will
take some more weeks to resign the repositories, hence we need to do
uploads after FF to enable the error by default even if we ship the
functionality before it.
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Affects: gnupg (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
I don't know if this will land before the feature freeze but I'm filing
this in any case:
Our goal for 24.04 is to reject 1024-bit RSA repository signing keys.
Work is ongoing in Launchpad to allow dual-signing PPAs and then resign
all PPAs with a 4096-bit key.
This needs the following changes:
- 1) The gnupg upstream commit for https://dev.gnupg.org/T6946 needs to be
backported
+ 1) The gnupg upstream commit for https://dev.gnupg.org/T6946 needs to be
backported. This is applying fine and in the package already, but the test
suite fails with issues that look weirdly unrelated.
2) APT needs to learn to pass the argument if supported
3) APT needs to learn to interpret the output
4) APT possibly may have to learn to issue warnings instead of errors for
weak keys and pass the URL to the gpgv method to allow 1024-bit RSA keys over
TLS connections, in case there are unforeseen issues with the PPA migration.
-
Signing key policy: We would like to adopt a signing key policy of
rsa>2048,ed25519,ed448
As a result we would like to reject
- RSA keys below 2048 bits
- DSA keys
- Unsafe ECC keys:
- - NIST P-{256,384,521}
- - Brainpool P-{256,384,512}
- - secp256k1
+ - NIST P-{256,384,521}
+ - Brainpool P-{256,384,512}
+ - secp256k1
Notes:
- DSA keys are not possible to use anymore due to the deprecation of SHA1
that happened years ago
- NIST and Brainpool and secp256k1 are not very popular,
https://safecurves.cr.yp.to/ lists all of them as unsafe. It is believed they
have backdoors. Some FIPS customers may prefer them over Ed25519 and Ed448 as
they have been approved longer, so it's possible fips support packages could
reenable them by setting the correct apt.conf setting in a snippet.
** Also affects: gnupg (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
I don't know if this will land before the feature freeze but I'm filing
this in any case:
Our goal for 24.04 is to reject 1024-bit RSA repository signing keys.
Work is ongoing in Launchpad to allow dual-signing PPAs and then resign
all PPAs with a 4096-bit key.
This needs the following changes:
1) The gnupg upstream commit for https://dev.gnupg.org/T6946 needs to be
backported. This is applying fine and in the package already, but the test
suite fails with issues that look weirdly unrelated.
2) APT needs to learn to pass the argument if supported
3) APT needs to learn to interpret the output
4) APT possibly may have to learn to issue warnings instead of errors for
weak keys and pass the URL to the gpgv method to allow 1024-bit RSA keys over
TLS connections, in case there are unforeseen issues with the PPA migration.
Signing key policy: We would like to adopt a signing key policy of
rsa>2048,ed25519,ed448
As a result we would like to reject
- RSA keys below 2048 bits
- DSA keys
- Unsafe ECC keys:
[Touch-packages] [Bug 2055055] Re: unmkinitramfs: wrong and unneeded count= in a dd call
https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/92 -- 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/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call Status in initramfs-tools package in Ubuntu: Triaged Bug description: Speaking about this line in unmkinitramfs: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: 77312 7200768 78615040 A combo of dd+head could be used intead to skip and count respectively: 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | head -c$((end - start)) | Or even tail+head: 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) | To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+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 2054683] Re: Please merge lvm2 2.03.16-3 from Debian unstable.
Uploaded and accepted: == OK: lvm2_2.03.16.orig.tar.xz OK: lvm2_2.03.16-3ubuntu1.debian.tar.xz OK: lvm2_2.03.16-3ubuntu1.dsc -> Component: main Section: admin ** Changed in: lvm2 (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/2054683 Title: Please merge lvm2 2.03.16-3 from Debian unstable. Status in lvm2 package in Ubuntu: In Progress Bug description: Please merge lvm2 2.03.16-3 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+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 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
I just sponsored lvm2 2.03.16-3ubuntu1 which should fix the FTBFS. On including libdm-propagate-ioctl-errors-back-to-caller.patch: I am not sure this bug is important enough to grant that. The patch may apply cleanly to 2.03.16, but still it comes from 2.03.23, which is not a trivial change in the upstream codebase. I can see that better error messages on ENOKEY will result in an overall better UX, however most commits in an upstream devel repo will somehow improve something, still we try to rely on releases as cut by upstream when possible, for the many reasons I certainly don't have to tell you about. :-) However: I may have missed the point here, and maybe the current UX is both (1) terrible, or at least quite bad (2) affecting many users, and not only users with an niche disk encryption configuration. If you think this is the case, can you please update the bug and elaborate a bit more on it? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Noble: Confirmed Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+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 2054683] Re: Please merge lvm2 2.03.16-3 from Debian unstable.
** Changed in: lvm2 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/2054683 Title: Please merge lvm2 2.03.16-3 from Debian unstable. Status in lvm2 package in Ubuntu: In Progress Bug description: Please merge lvm2 2.03.16-3 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+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 2055180] [NEW] coreutils 9.4-3ubuntu1 FTBFS
Public bug reported: The recent upload FTBFS due to a build-time test failure[1]: FAIL: tests/cp/cp-i === --- err42024-02-26 18:03:34.566066156 + +++ err_skip2024-02-26 18:03:34.554065852 + @@ -1 +1 @@ -cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead +cp: not replacing 'd' FAIL tests/cp/cp-i.sh (exit status: 1) This appears related to a new Debian patch that we pulled in with the merge. [1] https://launchpadlibrarian.net/716215295/buildlog_ubuntu-noble- amd64.coreutils_9.4-3ubuntu1_BUILDING.txt.gz ** Affects: coreutils (Ubuntu) Importance: High Assignee: Nick Rosbrook (enr0n) Status: Confirmed ** Tags: update-excuse ** Changed in: coreutils (Ubuntu) Importance: Undecided => High ** Changed in: coreutils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2055180 Title: coreutils 9.4-3ubuntu1 FTBFS Status in coreutils package in Ubuntu: Confirmed Bug description: The recent upload FTBFS due to a build-time test failure[1]: FAIL: tests/cp/cp-i === --- err4 2024-02-26 18:03:34.566066156 + +++ err_skip 2024-02-26 18:03:34.554065852 + @@ -1 +1 @@ -cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead +cp: not replacing 'd' FAIL tests/cp/cp-i.sh (exit status: 1) This appears related to a new Debian patch that we pulled in with the merge. [1] https://launchpadlibrarian.net/716215295/buildlog_ubuntu-noble- amd64.coreutils_9.4-3ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2055180/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
This bug was fixed in the package kubuntu-meta - 1.443 --- kubuntu-meta (1.443) noble; urgency=medium * Update update to check for germinate. Ref: (LP: #2017786) -- Scarlett Moore Tue, 27 Feb 2024 05:02:36 -0700 ** Changed in: kubuntu-meta (Ubuntu) Status: New => 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/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: Won't Fix Status in kubuntu-meta package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: Won't Fix Status in xubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2055176] [NEW] Apps crash out when switching windows and using VMWare Horizon
Public bug reported:
When using VMWare Horizon and quickly switching windows (alt-tab), the
Horizon app and other apps crashes (such as spotify (snap?) and zoom
(native deb)). I can see a Segmentation Fault error in syslog. I have
tried the last four versions of VMWare Horizon and have the same
results. This was never a problem with 23.10.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 27 14:50:55 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Dell WhiskeyLake-U GT2 [UHD Graphics 620] [1028:08e0]
InstallationDate: Installed on 2024-02-03 (24 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic
root=UUID=5f7a0ef6-50b2-480b-b0f3-1aed4dbdbd57 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2023
dmi.bios.release: 1.28
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.28.0
dmi.board.name: 0PYRY5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: NAB612163
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.28.0:bd11/03/2023:br1.28:svnDellInc.:pnLatitude7300:pvr:rvnDellInc.:rn0PYRY5:rvrA00:cvnDellInc.:ct10:cvr:sku08E0:
dmi.product.family: Latitude
dmi.product.name: Latitude 7300
dmi.product.sku: 08E0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu wayland-session
--
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/2055176
Title:
Apps crash out when switching windows and using VMWare Horizon
Status in xorg package in Ubuntu:
New
Bug description:
When using VMWare Horizon and quickly switching windows (alt-tab), the
Horizon app and other apps crashes (such as spotify (snap?) and zoom
(native deb)). I can see a Segmentation Fault error in syslog. I have
tried the last four versions of VMWare Horizon and have the same
results. This was never a problem with 23.10.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 27 14:50:55 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Dell WhiskeyLake-U GT2 [UHD Graphics 620] [1028:08e0]
InstallationDate: Installed on 2024-02-03 (24 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic
root=UUID=5f7a0ef6-50b2-480b-b0f3-1aed4dbdbd57 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2023
dmi.bios.release: 1.28
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.28.0
dmi.board.name: 0PYRY5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: NAB612163
dmi.chassis.type: 10
[Touch-packages] [Bug 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA
https://ubuntu.com/security/notices/USN-6663-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2054090 Title: Implicit rejection of PKCS#1 v1.5 RSA Status in openssl package in Ubuntu: New Status in openssl source package in Trusty: New Status in openssl source package in Xenial: New Status in openssl source package in Bionic: Fix Released Status in openssl source package in Focal: Fix Released Status in openssl source package in Jammy: Fix Released Status in openssl source package in Mantic: Fix Released Status in openssl source package in Noble: New Bug description: OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random output instead of an exception when detecting wrong padding (https://github.com/openssl/openssl/pull/13817). There are available backports already: * 3.0 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit- rejection.patch?ref_type=heads * 1.1.1 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit- rejection.patch?ref_type=heads This change is needed to fix CVE-2023-50782. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2055055] Re: unmkinitramfs: wrong and unneeded count= in a dd call
> The count_bytes solution looks better to me The updated patch is attached. I've just checked: all the *_bytes flags were introduced to dd in the same commit https://github.com/coreutils/coreutils/commit/140eca15c4a3d3213629a048cc307fde0d094738, so it is safe to throw in count_bytes in the mix. > I see four dd calls in unmkinitramfs. Can you check those as well? The other dd calls are good: - 2x of bs=1 kind - the last one is "dump from X till the end" utilizing skip_bytes for X, which is correct > Debian is affected as well. If you can spare the time, please submit your patch Will do when they activate my just created account on salsa ** Patch added: "Add count_bytes iflag" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+attachment/5749755/+files/dd-count-2.patch -- 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/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call Status in initramfs-tools package in Ubuntu: Triaged Bug description: Speaking about this line in unmkinitramfs: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: 77312 7200768 78615040 A combo of dd+head could be used intead to skip and count respectively: 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | head -c$((end - start)) | Or even tail+head: 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) | To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
The attachment "mysuperpatch.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] -- 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/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: Won't Fix Status in kubuntu-meta package in Ubuntu: New Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: Won't Fix Status in xubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2055153] [NEW] Xorg freeze
Public bug reported: I have booting related issue everytime I install NVIDIA-driver on Ubuntu 22.04 So the main problem is everytime I boot, Ubuntu would either (1) boot fine (25% of the time) (2) boot takes long time(about 2 min) (50% of the time) (3) boot fails (25% of the time) This symptom disappears when I uninstall NVIDIA driver so I'm pretty sure it is related to NVIDIA driver but I don't know how to fix it. For case (2) (boot takes long time), black screen with '/dev/nvme0n1p6: clean, *** files, *** blocks' hang for a long time. For case (3) (boot fails), blackscreen with 'iwlwifi : invalid buffer destination' 'ACPI BIOS Error (bug): could not resolve symbol [\_TZ.ETMD], AE NOT_FOUND' 'ACPI Error: Aborting method \_SB.IETM._OSC due to previos error (AE_NOT_FOUND)' 'Bluetooth: hci0: Malformed MSFT vendor event: 0x02' 'INFO: task plymouthd: *** blocked for more than *** seconds' '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message' 'INFO: task gpu-manager: *** blocked for more than *** seconds' '"echo 0 > /prc/sys/kernel/hung_task_timeout_secs" disables this message' This screen appears and doesn't boot or blackscreen with cursor appears and doesn't boot. It happens quite randomly and it really is frustrating and want to resolve this issue. I've tried various things but it didn't work out. Here are some things I tried - deleting and reinstalling NVIDIA driver with 'purge, autoremove, apt install' - Installing different driver version(525, 535, 545) - trying boot-repair program - disabling nouveau by modifying /etc/modprobe.d/blacklist.conf - 'nomodeset' by modifying /etc/default/grub (made it worse.. all boot fails) - tried various kernel version with various Ubuntu version (my laptop is very new device so 20.04 had issues with touchpad, wifi, etc, therefore I mainly tried 22.04) However none of them seemed to resolve the problem I am facing. It showed different symptoms time-to-time but mostly all of them were boot- related. I am using a dualboot with windows I am kind of lost and kindly ask for help. Here are some of the specification that would be helpful Laptop: lenovo legion pro 7 16irx8h $ uname -a Linux alvin-Legion-Pro-7-16IRX8H 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux $ lspci 00:00.0 Host bridge: Intel Corporation Device a702 (rev 01) 00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01) 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD Graphics (rev 04) 00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant (rev 01) 00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 01) 00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog and Telemetry (rev 01) 00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 Gb/s) XHCI Host Controller (rev 11) 00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11) 00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi (rev 11) 00:15.0 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C Host Controller #0 (rev 11) 00:15.1 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C Host Controller #1 (rev 11) 00:15.2 Serial bus controller: Intel Corporation Raptor Lake Serial IO I2C Host Controller #2 (rev 11) 00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 (rev 11) 00:19.0 Serial bus controller: Intel Corporation Device 7a7c (rev 11) 00:19.1 Serial bus controller: Intel Corporation Device 7a7d (rev 11) 00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 (rev 11) 00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 (rev 11) 00:1b.5 PCI bridge: Intel Corporation Device 7a45 (rev 11) 00:1d.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #9 (rev 11) 00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11) 00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio Controller (rev 11) 00:1f.4 SMBus: Intel Corporation Raptor Lake-S PCH SMBus Controller (rev 11) 00:1f.5 Serial bus controller: Intel Corporation Raptor Lake SPI (flash) Controller (rev 11) 01:00.0 VGA compatible controller: NVIDIA Corporation AD104M [GeForce RTX 4080 Max-Q / Mobile] (rev a1) 01:00.1 Audio device: NVIDIA Corporation Device 22bc (rev a1) 06:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO 07:00.0 PCI bridge: Intel Corporation Device 1133 (rev 02) 08:00.0 PCI bridge: Intel Corporation Device 1133 (rev 02) 08:01.0 PCI bridge: Intel Corporation Device 1133 (rev 02) 08:02.0 PCI bridge: Intel Corporation Device 1133 (rev 02) 08:03.0 PCI bridge: Intel Corporation Device 1133 (rev 02) 09:00.0 USB controller: Intel Corporation Device 1134 3d:00.0 USB controller: Intel Corporation
[Touch-packages] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
I have opted for the check without the version check. Will be uploaded shortly. -- 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/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: Won't Fix Status in kubuntu-meta package in Ubuntu: New Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: Won't Fix Status in xubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2055146] Re: Upgrade from Jammy to Noble breaks
** Tags removed: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2055146 Title: Upgrade from Jammy to Noble breaks Status in dash package in Ubuntu: Fix Committed Bug description: Hello there! Upgrading `dash` from Jammy to Noble is broken. Here is a quick reproducer: ``` podman pull ubuntu:jammy podman run -it --rm ubuntu:jammy sed -i 's/jammy/noble/' /etc/apt/sources.list apt update apt full-upgrade ``` This should end up with this error: ``` Setting up dash (0.5.12-6ubuntu3) ... Removing 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash' Removing 'diversion of /bin/sh to /bin/sh.distrib by dash' This should never be reached dpkg: error processing package dash (--configure): installed dash package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dash E: Sub-process /usr/bin/dpkg returned an error code (1) ``` As `dash` is pre-installed on almost every kind of Ubuntu, this breaks any upgrade from Jammy to Noble in practice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2055146/+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 2055146] Re: Upgrade from Jammy to Noble breaks
** Changed in: dash (Ubuntu) Status: New => In Progress ** Changed in: dash (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2055146 Title: Upgrade from Jammy to Noble breaks Status in dash package in Ubuntu: Fix Committed Bug description: Hello there! Upgrading `dash` from Jammy to Noble is broken. Here is a quick reproducer: ``` podman pull ubuntu:jammy podman run -it --rm ubuntu:jammy sed -i 's/jammy/noble/' /etc/apt/sources.list apt update apt full-upgrade ``` This should end up with this error: ``` Setting up dash (0.5.12-6ubuntu3) ... Removing 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash' Removing 'diversion of /bin/sh to /bin/sh.distrib by dash' This should never be reached dpkg: error processing package dash (--configure): installed dash package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dash E: Sub-process /usr/bin/dpkg returned an error code (1) ``` As `dash` is pre-installed on almost every kind of Ubuntu, this breaks any upgrade from Jammy to Noble in practice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2055146/+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 2055148] [NEW] NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan
Public bug reported: From: https://discourse.ubuntu.com/t/blog-netplan-developer- diaries/35932/11 Hi all, NetworkManager connections with an explicit DoT (DNS over TLS) configuration are not supported with Netplan, but NetworkManager does feed back the DoT DNS info with server address and Server Name Indication (SNI) in the form server_address#SNI, e.g. 1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a result, subsequent Netplan config applications fail because DNS servers don’t have the expected dotted decimal (IPv4) or colon’ed hex (IPv6) form. ``` nmcli> describe ipv4.dns === [dns] === [NM property description] Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved. ``` ** Affects: netplan Importance: Undecided Status: New ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: netplan-everywhere ** Also affects: netplan Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: 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/2055148 Title: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan Status in netplan: New Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: From: https://discourse.ubuntu.com/t/blog-netplan-developer- diaries/35932/11 Hi all, NetworkManager connections with an explicit DoT (DNS over TLS) configuration are not supported with Netplan, but NetworkManager does feed back the DoT DNS info with server address and Server Name Indication (SNI) in the form server_address#SNI, e.g. 1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a result, subsequent Netplan config applications fail because DNS servers don’t have the expected dotted decimal (IPv4) or colon’ed hex (IPv6) form. ``` nmcli> describe ipv4.dns === [dns] === [NM property description] Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2055148/+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 2055065] Re: Please merge kbd 2.6.4-2 (main) from Debian unstable
** Description changed: - TODO + debian: + kbd| 2.0.4-4 | oldoldstable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x + kbd| 2.3.0-3 | oldstable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x + kbd| 2.5.1-1 | stable | source + kbd| 2.5.1-1+b1| stable | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x + kbd| 2.6.4-2 | testing| source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x + kbd| 2.6.4-2 | unstable | source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x + kbd| 2.6.4-2 | unstable-debug | source + ubuntu: + kbd | 1.15.5-1ubuntu1 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el + kbd | 1.15.5-1ubuntu4 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x + kbd | 1.15.5-1ubuntu5 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x + kbd | 2.0.4-2ubuntu1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x + kbd | 2.0.4-4ubuntu2 | focal | source, amd64, arm64, armhf, ppc64el, riscv64, s390x + kbd | 2.3.0-3ubuntu4 | jammy | source, amd64, arm64, armhf, ppc64el, riscv64, s390x + kbd | 2.3.0-3ubuntu4.22.04 | jammy-updates | source, amd64, arm64, armhf, ppc64el, riscv64, s390x + kbd | 2.5.1-1ubuntu1 | mantic | source, amd64, arm64, armhf, ppc64el, riscv64, s390x + kbd | 2.5.1-1ubuntu1 | noble | source, amd64, arm64, armhf, ppc64el, riscv64, s390x ** Changed in: kbd (Ubuntu) Status: New => In Progress ** Changed in: kbd (Ubuntu) Assignee: (unassigned) => Olivier Gayot (ogayot) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2055065 Title: Please merge kbd 2.6.4-2 (main) from Debian unstable Status in kbd package in Ubuntu: In Progress Bug description: debian: kbd| 2.0.4-4 | oldoldstable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x kbd| 2.3.0-3 | oldstable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x kbd| 2.5.1-1 | stable | source kbd| 2.5.1-1+b1| stable | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x kbd| 2.6.4-2 | testing| source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x kbd| 2.6.4-2 | unstable | source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x kbd| 2.6.4-2 | unstable-debug | source ubuntu: kbd | 1.15.5-1ubuntu1 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el kbd | 1.15.5-1ubuntu4 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x kbd | 1.15.5-1ubuntu5 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x kbd | 2.0.4-2ubuntu1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x kbd | 2.0.4-4ubuntu2 | focal | source, amd64, arm64, armhf, ppc64el, riscv64, s390x kbd | 2.3.0-3ubuntu4 | jammy | source, amd64, arm64, armhf, ppc64el, riscv64, s390x kbd | 2.3.0-3ubuntu4.22.04 | jammy-updates | source, amd64, arm64, armhf, ppc64el, riscv64, s390x kbd | 2.5.1-1ubuntu1 | mantic | source, amd64, arm64, armhf, ppc64el, riscv64, s390x kbd | 2.5.1-1ubuntu1 | noble | source, amd64, arm64, armhf, ppc64el, riscv64, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2055065/+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 2055146] [NEW] Upgrade from Jammy to Noble breaks
Public bug reported: Hello there! Upgrading `dash` from Jammy to Noble is broken. Here is a quick reproducer: ``` podman pull ubuntu:jammy podman run -it --rm ubuntu:jammy sed -i 's/jammy/noble/' /etc/apt/sources.list apt update apt full-upgrade ``` This should end up with this error: ``` Setting up dash (0.5.12-6ubuntu3) ... Removing 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash' Removing 'diversion of /bin/sh to /bin/sh.distrib by dash' This should never be reached dpkg: error processing package dash (--configure): installed dash package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dash E: Sub-process /usr/bin/dpkg returned an error code (1) ``` As `dash` is pre-installed on almost every kind of Ubuntu, this breaks any upgrade from Jammy to Noble in practice. ** Affects: dash (Ubuntu) Importance: Undecided Status: New ** Tags: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2055146 Title: Upgrade from Jammy to Noble breaks Status in dash package in Ubuntu: New Bug description: Hello there! Upgrading `dash` from Jammy to Noble is broken. Here is a quick reproducer: ``` podman pull ubuntu:jammy podman run -it --rm ubuntu:jammy sed -i 's/jammy/noble/' /etc/apt/sources.list apt update apt full-upgrade ``` This should end up with this error: ``` Setting up dash (0.5.12-6ubuntu3) ... Removing 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash' Removing 'diversion of /bin/sh to /bin/sh.distrib by dash' This should never be reached dpkg: error processing package dash (--configure): installed dash package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dash E: Sub-process /usr/bin/dpkg returned an error code (1) ``` As `dash` is pre-installed on almost every kind of Ubuntu, this breaks any upgrade from Jammy to Noble in practice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2055146/+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 2055065] Re: Please merge kbd 2.6.4-2 (main) from Debian unstable
** Merge proposal linked: https://code.launchpad.net/~ogayot/ubuntu/+source/kbd/+git/kbd/+merge/461345 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2055065 Title: Please merge kbd 2.6.4-2 (main) from Debian unstable Status in kbd package in Ubuntu: New Bug description: TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2055065/+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 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA
Bionic released in ESM Infra, version 1.1.1-1ubuntu2.1~18.04.23+esm5 ** Changed in: openssl (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2054090 Title: Implicit rejection of PKCS#1 v1.5 RSA Status in openssl package in Ubuntu: New Status in openssl source package in Trusty: New Status in openssl source package in Xenial: New Status in openssl source package in Bionic: Fix Released Status in openssl source package in Focal: Fix Released Status in openssl source package in Jammy: Fix Released Status in openssl source package in Mantic: Fix Released Status in openssl source package in Noble: New Bug description: OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random output instead of an exception when detecting wrong padding (https://github.com/openssl/openssl/pull/13817). There are available backports already: * 3.0 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit- rejection.patch?ref_type=heads * 1.1.1 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit- rejection.patch?ref_type=heads This change is needed to fix CVE-2023-50782. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2055055] Re: unmkinitramfs: wrong and unneeded count= in a dd call
Thank you for taking the time to report this bug and contributing to Ubuntu. The count_bytes solution looks better to me. I see four dd calls in unmkinitramfs. Can you check those as well? Debian is affected as well. If you can spare the time, please submit your patch to https://salsa.debian.org/kernel-team/initramfs- tools/-/merge_requests as well. ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Triaged -- 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/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call Status in initramfs-tools package in Ubuntu: Triaged Bug description: Speaking about this line in unmkinitramfs: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: 77312 7200768 78615040 A combo of dd+head could be used intead to skip and count respectively: 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | head -c$((end - start)) | Or even tail+head: 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) | To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+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 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA
This bug was fixed in the package openssl - 3.0.2-0ubuntu1.15 --- openssl (3.0.2-0ubuntu1.15) jammy-security; urgency=medium * SECURITY UPDATE: Implicit rejection for RSA PKCS#1 (LP: #2054090) - debian/patches/openssl-pkcs1-implicit-rejection.patch: Return deterministic random output instead of an error in case there is a padding error in crypto/cms/cms_env.c, crypto/evp/ctrl_params_translate.c, crypto/pkcs7/pk7_doit.c, crypto/rsa/rsa_ossl.c, crypto/rsa/rsa_pk1.c, crypto/rsa/rsa_pmeth.c, doc/man1/openssl-pkeyutl.pod.in, doc/man1/openssl-rsautl.pod.in, doc/man3/EVP_PKEY_CTX_ctrl.pod, doc/man3/EVP_PKEY_decrypt.pod, doc/man3/RSA_padding_add_PKCS1_type_1.pod, doc/man3/RSA_public_encrypt.pod, doc/man7/provider-asym_cipher.pod, include/crypto/rsa.h, include/openssl/core_names.h, include/openssl/rsa.h, providers/implementations/asymciphers/rsa_enc.c and test/recipes/30-test_evp_data/evppkey_rsa_common.txt. -- David Fernandez Gonzalez Fri, 16 Feb 2024 09:51:30 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2054090 Title: Implicit rejection of PKCS#1 v1.5 RSA Status in openssl package in Ubuntu: New Status in openssl source package in Trusty: New Status in openssl source package in Xenial: New Status in openssl source package in Bionic: New Status in openssl source package in Focal: Fix Released Status in openssl source package in Jammy: Fix Released Status in openssl source package in Mantic: Fix Released Status in openssl source package in Noble: New Bug description: OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random output instead of an exception when detecting wrong padding (https://github.com/openssl/openssl/pull/13817). There are available backports already: * 3.0 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit- rejection.patch?ref_type=heads * 1.1.1 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit- rejection.patch?ref_type=heads This change is needed to fix CVE-2023-50782. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA
This bug was fixed in the package openssl - 1.1.1f-1ubuntu2.22 --- openssl (1.1.1f-1ubuntu2.22) focal-security; urgency=medium * SECURITY UPDATE: Implicit rejection for RSA PKCS#1 (LP: #2054090) - debian/patches/openssl-1.1.1-pkcs1-implicit-rejection.patch: Return deterministic random output instead of an error in case there is a padding error in crypto/cms/cms_env.c, crypto/pkcs7/pk7_doit.c, crypto/rsa/rsa_local.h, crypto/rsa/rsa_ossl.c, crypto/rsa/rsa_pk1.c, crypto/rsa/rsa_pmeth.c, doc/man1/pkeyutl.pod, doc/man1/rsautl.pod, doc/man3/EVP_PKEY_CTX_ctrl.pod, doc/man3/EVP_PKEY_decrypt.pod, doc/man3/RSA_padding_add_PKCS1_type_1.pod, doc/man3/RSA_public_encrypt.pod, include/openssl/rsa.h and test/recipes/30-test_evp_data/evppkey.txt. -- David Fernandez Gonzalez Fri, 16 Feb 2024 16:41:31 +0100 ** Changed in: openssl (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2054090 Title: Implicit rejection of PKCS#1 v1.5 RSA Status in openssl package in Ubuntu: New Status in openssl source package in Trusty: New Status in openssl source package in Xenial: New Status in openssl source package in Bionic: New Status in openssl source package in Focal: Fix Released Status in openssl source package in Jammy: Fix Released Status in openssl source package in Mantic: Fix Released Status in openssl source package in Noble: New Bug description: OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random output instead of an exception when detecting wrong padding (https://github.com/openssl/openssl/pull/13817). There are available backports already: * 3.0 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit- rejection.patch?ref_type=heads * 1.1.1 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit- rejection.patch?ref_type=heads This change is needed to fix CVE-2023-50782. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA
This bug was fixed in the package openssl - 3.0.10-1ubuntu2.3 --- openssl (3.0.10-1ubuntu2.3) mantic-security; urgency=medium * SECURITY UPDATE: Implicit rejection for RSA PKCS#1 (LP: #2054090) - debian/patches/openssl-pkcs1-implicit-rejection.patch: Return deterministic random output instead of an error in case there is a padding error in crypto/cms/cms_env.c, crypto/evp/ctrl_params_translate.c, crypto/pkcs7/pk7_doit.c, crypto/rsa/rsa_ossl.c, crypto/rsa/rsa_pk1.c, crypto/rsa/rsa_pmeth.c, doc/man1/openssl-pkeyutl.pod.in, doc/man1/openssl-rsautl.pod.in, doc/man3/EVP_PKEY_CTX_ctrl.pod, doc/man3/EVP_PKEY_decrypt.pod, doc/man3/RSA_padding_add_PKCS1_type_1.pod, doc/man3/RSA_public_encrypt.pod, doc/man7/provider-asym_cipher.pod, include/crypto/rsa.h, include/openssl/core_names.h, include/openssl/rsa.h, providers/implementations/asymciphers/rsa_enc.c and test/recipes/30-test_evp_data/evppkey_rsa_common.txt. -- David Fernandez Gonzalez Wed, 21 Feb 2024 11:45:39 +0100 ** Changed in: openssl (Ubuntu Mantic) Status: New => Fix Released ** Changed in: openssl (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2054090 Title: Implicit rejection of PKCS#1 v1.5 RSA Status in openssl package in Ubuntu: New Status in openssl source package in Trusty: New Status in openssl source package in Xenial: New Status in openssl source package in Bionic: New Status in openssl source package in Focal: Fix Released Status in openssl source package in Jammy: Fix Released Status in openssl source package in Mantic: Fix Released Status in openssl source package in Noble: New Bug description: OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random output instead of an exception when detecting wrong padding (https://github.com/openssl/openssl/pull/13817). There are available backports already: * 3.0 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit- rejection.patch?ref_type=heads * 1.1.1 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit- rejection.patch?ref_type=heads This change is needed to fix CVE-2023-50782. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2055065] Re: Please merge kbd 2.6.4-2 (main) from Debian unstable
** Changed in: kbd (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2055065 Title: Please merge kbd 2.6.4-2 (main) from Debian unstable Status in kbd package in Ubuntu: New Bug description: TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2055065/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
We had a mitigation for this in glibc but the latest change from simply denying the unshare() call to allowing it but then denying anything requiring capabilities *presumably* broke the glibc test suite again. I'm only basing this from looking at the test logs, as I'm temporarily unable to run autopkgtests locally and am lacking the time to fix it. 2 classes of errors: 2770s FAIL: stdlib/tst-system 2770s original exit status 1 2770s error: test-container.c:1136: could not create a private mount namespace That one is clearly userns-related, as it's due to a failing mount() call right after unshare() 2770s FAIL: sunrpc/tst-svc_register 2770s original exit status 1 2770s error: xwrite.c:32: write of 12 bytes failed after 0: Operation not permitted 2770s error: 1 test failures I can't tell for sure what this one is about since this is your basic write() call and I don't have a stack trace at hand, but the EPERM would suggest that it's related. I think a first fix would be to amend the test script to disable the userns restriction entirely for the duration of the tests (using 'needs- sudo'), while I'll still need to patch the test suite eventually to handle this new failure mode gracefully and simply ignore the tests, akin to https://sourceware.org/pipermail/libc- alpha/2024-February/154754.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2052739] Re: tzdata 2024a release
Verified successful autopkgtest on https://autopkgtest.ubuntu.com/packages/tzdata: mantic: * amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/t/tzdata/20240223_012444_0f113@/log.gz * arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/arm64/t/tzdata/20240223_001555_7ca29@/log.gz * armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/armhf/t/tzdata/20240223_023357_ee94e@/log.gz * ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/ppc64el/t/tzdata/20240223_001617_0822f@/log.gz * s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/s390x/t/tzdata/20240223_014437_7f723@/log.gz jammy: * amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/t/tzdata/20240223_001452_bda5d@/log.gz * arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/t/tzdata/20240222_232655_62fd6@/log.gz * armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/armhf/t/tzdata/20240222_235619_bdf0b@/log.gz * ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/t/tzdata/20240222_232100_67fd5@/log.gz * s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/t/tzdata/20240223_000331_11f77@/log.gz focal: * amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/t/tzdata/20240223_001845_45d0c@/log.gz * arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/t/tzdata/20240222_235449_caab5@/log.gz * armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/t/tzdata/20240222_235714_29cd7@/log.gz * ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/t/tzdata/20240222_231755_6a4ad@/log.gz * s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/t/tzdata/20240222_233135_dc0df@/log.gz ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-focal verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2052739 Title: tzdata 2024a release Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] The 2024a release contains the following changes: * Kazakhstan unifies on UTC+5 beginning 2024-03-01. * Palestine springs forward a week later after Ramadan. * zic no longer pretends to support indefinite-past DST. * localtime no longer mishandles Ciudad Juárez in 2422. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024a * python-icu: test_2024a (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2052405] Re: Translation error in policykit-1 package
update the suggested translation text as 2024-01-17. thank you for reporting the outdated translation typo. fixed translation list : * https://translations.launchpad.net/ubuntu/jammy/+source/policykit-1/+pots/polkit-1/ko/7/+translate * https://translations.launchpad.net/ubuntu/jammy/+source/policykit-1/+pots/polkit-1/ko/8/+translate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2052405 Title: Translation error in policykit-1 package Status in Ubuntu Translations: New Status in language-support-translations-ko package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Bug description: policykit-1 package have translation error. https://translations.launchpad.net/ubuntu/jammy/+source/policykit-1/+pots/polkit-1/ko/+translate `$(program)'을(를) 관리자 권한으로 실행려면 인증이 필요합니다. -> `$(program)'을(를) 관리자 권한으로 실행하려면 인증이 필요합니다. `$(program)'을(를) $(user) 계정으로 실행려면 인증이 필요합니다. -> `$(program)'을(를) $(user) 계정으로 실행하려면 인증이 필요합니다. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/2052405/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
I can confirm ajgreeny's message. Installed in a QEMU/KVM VM and got a working GUI after reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: Invalid Status in lightdm package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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
