[Touch-packages] [Bug 2103888] Re: Please remove lomiri and qtmir from plucky-proposed
Hey, thanks for explaining the background so well - we all have been there at the uncertainty if all will be ready to make a particular switch. We didn't switch to MIR 2.20 as you say and it is too late to try. Hence I'm unsure on mir (at first). It is not that we'd remove an unintended 2.20, what I see right now is https://launchpad.net/ubuntu/+source/mir/2.14.1-8 which fails to build on arm64 but otherwise is happy. Yet in detail it seems that is a switch to clang which was further completed towards 2.20 - ok to keep that stable and remove the -proposed as requested. And due to that the other two are just forever build-dep wait on 2.20. We usually do not remove those that are just and only b-dep waiting (which we expect to resolve) while there is no newer version to sync. The reason for that is that the BD-wait would auto resolve once the new dependency is available. In this case i see that qtmir already went 0.8.0~git20250316.401819c-1 -> 0.8.0~git20250319.5ab362a-1 so that will auto-sync and be happy. For lomiri I still see 0.3.0-5 in Debian and Ubuntu. Unless if there is a stronger reason for it (yes I know we clean up towards the release and I like that) I'd keep lomiri around. If there is a reason I miss tell us about it. ./remove-package -m "LP: #2103888, depend on MIR 2.20 scheduled for 25.10, new versions to auto-sync exist" -s plucky-proposed mir qtmir Removing packages from plucky-proposed: mir 2.14.1-8 in plucky libmiral-dev 3.9.0.2.14.1-8 in plucky amd64 libmiral-dev 3.9.0.2.14.1-8 in plucky armhf libmiral-dev 3.9.0.2.14.1-8 in plucky ppc64el libmiral-dev 3.9.0.2.14.1-8 in plucky riscv64 libmiral-dev 3.9.0.2.14.1-8 in plucky s390x libmiral5t64 3.9.0.2.14.1-8 in plucky amd64 libmiral5t64 3.9.0.2.14.1-8 in plucky armhf libmiral5t64 3.9.0.2.14.1-8 in plucky ppc64el libmiral5t64 3.9.0.2.14.1-8 in plucky riscv64 libmiral5t64 3.9.0.2.14.1-8 in plucky s390x libmircommon-dev 2.14.1-8 in plucky amd64 libmircommon-dev 2.14.1-8 in plucky armhf libmircommon-dev 2.14.1-8 in plucky ppc64el libmircommon-dev 2.14.1-8 in plucky riscv64 libmircommon-dev 2.14.1-8 in plucky s390x libmircommon9t64 2.14.1-8 in plucky amd64 libmircommon9t64 2.14.1-8 in plucky armhf libmircommon9t64 2.14.1-8 in plucky ppc64el libmircommon9t64 2.14.1-8 in plucky riscv64 libmircommon9t64 2.14.1-8 in plucky s390x libmircookie-dev 2.14.1-8 in plucky amd64 libmircookie-dev 2.14.1-8 in plucky armhf libmircookie-dev 2.14.1-8 in plucky ppc64el libmircookie-dev 2.14.1-8 in plucky riscv64 libmircookie-dev 2.14.1-8 in plucky s390x libmircookie2t64 2.14.1-8 in plucky amd64 libmircookie2t64 2.14.1-8 in plucky armhf libmircookie2t64 2.14.1-8 in plucky ppc64el libmircookie2t64 2.14.1-8 in plucky riscv64 libmircookie2t64 2.14.1-8 in plucky s390x libmircore-dev 2.14.1-8 in plucky amd64 libmircore-dev 2.14.1-8 in plucky armhf libmircore-dev 2.14.1-8 in plucky ppc64el libmircore-dev 2.14.1-8 in plucky riscv64 libmircore-dev 2.14.1-8 in plucky s390x libmircore2t64 2.14.1-8 in plucky amd64 libmircore2t64 2.14.1-8 in plucky armhf libmircore2t64 2.14.1-8 in plucky ppc64el libmircore2t64 2.14.1-8 in plucky riscv64 libmircore2t64 2.14.1-8 in plucky s390x libmiroil-dev 2.14.1-8 in plucky amd64 libmiroil-dev 2.14.1-8 in plucky armhf libmiroil-dev 2.14.1-8 in plucky ppc64el libmiroil-dev 2.14.1-8 in plucky riscv64 libmiroil-dev 2.14.1-8 in plucky s390x libmiroil3t64 2.14.1-8 in plucky amd64 libmiroil3t64 2.14.1-8 in plucky armhf libmiroil3t64 2.14.1-8 in plucky ppc64el libmiroil3t64 2.14.1-8 in plucky riscv64 libmiroil3t64 2.14.1-8 in plucky s390x libmirplatform-dev 2.14.1-8 in plucky amd64 libmirplatform-dev 2.14.1-8 in plucky armhf libmirplatform-dev 2.14.1-8 in plucky ppc64el libmirplatform-dev 2.14.1-8 in plucky riscv64 libmirplatform-dev 2.14.1-8 in plucky s390x libmirplatform26t64 2.14.1-8 in plucky amd64 libmirplatform26t64 2.14.1-8 in plucky armhf libmirplatform26t64 2.14.1-8 in plucky ppc64el libmirplatform26t64 2.14.1-8 in plucky riscv64 libmirplatform26t64 2.14.1-8 in plucky s390x
[Touch-packages] [Bug 2101817] Re: gnome-shell crashed with SIGSEGV in drisw_init_screen() from driCreateNewScreen3() from dri2_create_screen() from dri2_initialize_device() from dri2_initialize()
I'm not really sure if this is Critical or just High. It depends on how many machines are affected. The function prefix suggests software rendering so maybe it's just some VMs? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2101817 Title: gnome-shell crashed with SIGSEGV in drisw_init_screen() from driCreateNewScreen3() from dri2_create_screen() from dri2_initialize_device() from dri2_initialize() Status in Mesa: New Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 48~beta-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/29b4464c85e6349b307fd74e2fd50e3e047fbe64 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2101817/+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 2092666] Re: package polkitd 124-2ubuntu1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
Same problem here do-release-upgrading from jammy to noble -- 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/2092666 Title: package polkitd 124-2ubuntu1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: Confirmed Bug description: = Welcome to Ubuntu 24.04 LTS 'Noble Numbat' = The Ubuntu team is proud to announce Ubuntu 24.04 LTS 'Noble Numbat'. To see what's new in this release, visit: https://wiki.ubuntu.com/NobleNumbat/ReleaseNotes Ubuntu is a Linux distribution for your desktop or server, with a fast and easy install, regular releases, a tight selection of excellent applications installed by default, and almost any other software you can imagine available through the network. We hope you enjoy Ubuntu. == Feedback and Helping == If you would like to help shape Ubuntu, take a look at the list of ways you can participate at http://www.ubuntu.com/community/participate/ Your comments, bug reports, patches and suggestions will help ensure that our next release is the best release of Ubuntu ever. If you feel that you have found a bug please read: http://help.ubuntu.com/community/ReportingBugs Then report bugs using apport in Ubuntu. For example: ubuntu-bug linux will open a bug report in Launchpad regarding the linux package. If you have a question, or if you think you may have found a bug but aren't sure, first try asking on the #ubuntu or #ubuntu-bugs IRC channels on Libera.Chat, on the Ubuntu Users mailing list, or on the Ubuntu forums: http://help.ubuntu.com/community/InternetRelayChat http://lists.ubuntu.com/mailman/listinfo/ubuntu-users http://www.ubuntuforums.org/ == More Information == You can find out more about Ubuntu on our website, IRC channel and wiki. If you're new to Ubuntu, please visit: http://www.ubuntu.com/ To sign up for future Ubuntu announcements, please subscribe to Ubuntu's very low volume announcement list at: http://lists.ubuntu.com/mailman/listinfo/ubuntu-announce Continue [yN] y Get:1 Upgrade tool signature [833 B] Get:2 Upgrade tool [1,277 kB] Fetched 1,278 kB in 0s (0 B/s) authenticate 'noble.tar.gz' against 'noble.tar.gz.gpg' extracting 'noble.tar.gz' dpkg: dependency problems prevent configuration of ubuntu-server: ubuntu-server depends on software-properties-common; however: Package software-properties-common is not configured yet. dpkg: error processing package ubuntu-server (--configure): dependency problems - leaving unconfigured Processing triggers for linux-image-6.8.0-51-generic (6.8.0-51.52) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.8.0-51-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/polkitd.0.crash' /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.8.0-51-generic Found initrd image: /boot/initrd.img-6.8.0-51-generic Found linux image: /boot/vmlinuz-5.15.0-130-generic Found initrd image: /boot/initrd.img-5.15.0-130-generic Found linux image: /boot/vmlinuz-5.15.0-127-generic Found initrd image: /boot/initrd.img-5.15.0-127-generic Found linux image: /boot/vmlinuz-5.15.0-126-generic Found initrd image: /boot/initrd.img-5.15.0-126-generic Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done Processing triggers for ca-certificates (20240203) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for initramfs-tools (0.142ubuntu25.4) ... update-initramfs: Generating /boot/initrd.img-6.8.0-51-generic Processing triggers for mariadb-server (1:10.11.8-0ubuntu0.24.04.1) ... Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.10+dfsg-3ubuntu3.1) ... Errors were encountered while processing: polkitd pkexec packagekit modemmanager policykit-1 packagekit-tools software-properties-common ubuntu-server needrestart is being skipped since dpkg has failed packages have been installed but needrestart is suspended packages have been installed but needrestart is suspended Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 24.04 Package: polkitd 124-2ubuntu1 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 2060082] Re: Dublin timezone cause systemd cpu high
I'm not sure about the proposed fix, but: * Dublin is probably not the only timezone impacted. * We should probably try to reproduce that and confirm the bug on Jammy, but also check Noble, just to be sure. ** Tags added: rls-jj-incoming ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2060082 Title: Dublin timezone cause systemd cpu high Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Jammy: New Bug description: Systemd version(249) in Jammy Jellyfish is too old, When using the Dublin time zone for daylight saving time switching，the CPU usage will suddenly increase to 100% starting from 2024-03-31 00:00:00 and last for 1 hour, but return to normal at 2024-03-31 02:00:00. plz backport the bugfix to v249 or update 255 version in Jammy Jellyfish to fix it. thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2060082/+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 2106111] Re: Black text highlighting in google chrome after latest update
The problem was resolved after switching theme in google chrome from GTK to QT and then to classic ** Summary changed: - Black text highlighting after + Black text highlighting in google chrome after latest update -- 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/2106111 Title: Black text highlighting in google chrome after latest update Status in Ubuntu: Opinion Bug description: Selecting text makes it invisible after latest ubuntu 22.04 update ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-57.59~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 3 10:12:22 2025 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:a7a1] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0c05] InstallationDate: Installed on 2024-07-03 (273 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: Dell Inc. Latitude 5540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-57-generic root=UUID=18e80cce-8d0e-4696-944e-e17a23c9554d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2023 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 031CD3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd11/07/2023:br1.8:efr1.8:svnDellInc.:pnLatitude5540:pvr:rvnDellInc.:rn031CD3:rvrA00:cvnDellInc.:ct10:cvr:sku0C05: dmi.product.family: Latitude dmi.product.name: Latitude 5540 dmi.product.sku: 0C05 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.13 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2106111/+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 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
Correction: The webkit2gtk patch got dropped shortly before Oracular was released. But conveniently around the same time, Mesa started working. So that's the real fix we wanted anyway. ** Also affects: mesa (Ubuntu Plucky) Importance: High Status: Won't Fix ** Also affects: webkit2gtk (Ubuntu Plucky) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: Fix Released ** Changed in: mesa (Ubuntu Oracular) Status: Won't Fix => Fix Released ** Changed in: mesa (Ubuntu Plucky) Status: Won't Fix => Fix Released ** Changed in: webkit2gtk (Ubuntu Oracular) Status: Fix Released => Won't Fix ** Changed in: webkit2gtk (Ubuntu Plucky) Status: Fix Released => Won't Fix ** Changed in: webkit2gtk (Ubuntu Oracular) Milestone: ubuntu-24.10 => None ** Changed in: webkit2gtk (Ubuntu Plucky) Milestone: ubuntu-24.10 => None ** Changed in: webkit2gtk (Ubuntu Oracular) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: webkit2gtk (Ubuntu Plucky) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: webkit2gtk (Ubuntu) Milestone: ubuntu-24.10 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile Status in Mesa: New Status in mesa package in Ubuntu: Won't Fix Status in webkit2gtk package in Ubuntu: Fix Released Status in mesa source package in Noble: Won't Fix Status in webkit2gtk source package in Noble: Fix Released Status in mesa source package in Oracular: Fix Released Status in webkit2gtk source package in Oracular: Won't Fix Status in mesa source package in Plucky: Fix Released Status in webkit2gtk source package in Plucky: Won't Fix Bug description: [ Impact ] webkit2gtk apps crash immediately with SIGSEGV on Raspberry Pi in Xorg sessions. Including the installer, yelp and MiniBrowser. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash. [ Where problems could occur ] Anywhere in webkit2gtk apps such as the OEM installer, Help app (yelp). [ Original description ] MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 2092363] Re: Missing (but referenced) SOF firmware in pc-kernel – No Audio
As mentioned previously, missing firmware isn't the only problem. Other main blockers are adding kernel modules (for example VirtualBox') and fwupd not working. Am I right in understanding this as FDE/TPM won't really be supported "properly" for a good while yet and that people like myself relying on this should seek other alternatives until it's more mature? Meanwhile/alternatively: are there any workarounds like rolling one's own kernel snap with the necessary additions? Are there any guides available on doing that properly (especially related to getting the signing part done properly for Secure Boot to work)? Any way of contributing to solving this permanently BTW – sponsoring someone or doing actual work. Are these features (firmware component snaps, and similar for kernel modules) tracked somewhere? Lastly – is it possible to use FDE with TPM without using the snap kernel? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2092363 Title: Missing (but referenced) SOF firmware in pc-kernel – No Audio Status in canonical-kernel-snaps: Confirmed Status in pc-kernel-snap: Invalid Status in apt package in Ubuntu: Invalid Status in boot-managed-by-snapd package in Ubuntu: Invalid Status in firmware-sof package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: I am encountering an issue with the pc-kernel snap on my HP EliteBook 840 G11 laptop running Ubuntu 24.04.1 LTS with the new TPM+FDE feature. Despite testing multiple kernel channels, the system fails to detect any audio devices. However, when booting into a live session of Ubuntu 24.04.1 LTS, audio functions as expected. This suggests the issue may be related to the pc-kernel snap. Right now I'm on channel 24/stable (version: 6.8.0-50.51), but I have tried 24-hwe/stable and 24.10/stable as well. For reference, I have first tried to seek help in the support section over at Ubuntu Discourse, and I was encouraged to file a bug report here against the linux package on Discourse: https://discourse.ubuntu.com/t/no-audio-device-detected-on-hp-elitebook-840-14-g11-running-ubuntu-24-04/51498/7 Details: OS: Ubuntu 24.04.1 LTS Setup: TPM-backed Full Disk Encryption (FDE) using pc-kernel snap Kernel Channels Tried: 24-hwe/stable, 24/stable, 24.10/stable Issue: aplay -l reports "no sound card found"; only "Dummy output" is listed in Audio settings. Observation: Audio works correctly in a live session of Ubuntu 24.04.1 LTS. Listing audio devices: $ aplay -l aplay: device_list:277: no soundcards found... Relevant lspci Output: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Meteor Lake-P HD Audio Controller [8086:7e28] (rev 20) Subsystem: Hewlett-Packard Company Meteor Lake-P HD Audio Controller [103c:8c26] Kernel driver in use: sof-audio-pci-intel-mtl Kernel modules: snd_hda_intel, snd_sof_pci_intel_mtl Additional Notes: Could the issue be related to missing kernel drivers or modules, such as firmware-sof-signed? Reference: https://packages.ubuntu.com/noble/firmware-sof-signed Please let me know if additional details, logs, or steps are required. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-50-generic (not installed) ProcVersionSignature: Ubuntu 6.8.0-50.51-generic 6.8.12 Uname: Linux 6.8.0-50-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:kihen 3216 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 22 20:09:17 2024 MachineType: HP HP EliteBook 840 14 inch G11 Notebook PC ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb 1 i915drmfb ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-50-generic N/A linux-backports-modules-6.8.0-50-generic N/A linux-firmwareN/A SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 06/20/2024 dmi.bios.release: 2.6 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.02.06 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.43.50 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.67 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.02.06:bd06/20/2024:br2.6:efr2.67:svnHP:pnHPEliteBook84014inchG11NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.43.50:cvnHP:ct10:cvr:sku8M4W7AV: dmi.prod
[Touch-packages] [Bug 2083017] Re: network-manager changed path to nm-dhcp-helper, apparmor need update
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
** Changed in: isc-dhcp (Ubuntu)
Status: Confirmed => Invalid
--
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/2083017
Title:
network-manager changed path to nm-dhcp-helper, apparmor need update
Status in apparmor package in Ubuntu:
Confirmed
Status in isc-dhcp package in Ubuntu:
Invalid
Bug description:
From the Debian Bug report logs - #1055067
isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper,
apparmor need update
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055067
The problem causes the DHCP fail to receive the IP with this error in
the dmesg command:
[ 1037.911083] audit: type=1400 audit(1727430402.572:1355):
apparmor="DENIED" operation="exec" class="file"
profile="/{,usr/}sbin/dhclient" name="/usr/libexec/nm-dhcp-helper"
pid=6763 comm="dhclient" requested_mask="x" denied_mask="x" fsuid=0
ouid=0
The /etc/apparmor.d/sbin.dhclient file needs to be updated to include
the /usr/libexec/nm-dhcp-helper (instead of
/usr/lib/NetworkManager/nm-dhcp-helper). Just in case, to solve it, I
duplicated the definitions for the NetworkManager/nm-dhcp-helper.
FILE: /etc/apparmor.d/sbin.dhclient
# Support the new executable helper from NetworkManager.
/usr/lib/NetworkManager/nm-dhcp-helper Pxrm,
signal (receive) peer=/usr/lib/NetworkManager/nm-dhcp-helper,
/usr/libexec/nm-dhcp-helper Pxrm,
signal (receive) peer=/usr/libexec/nm-dhcp-helper,
/usr/lib/NetworkManager/nm-dhcp-helper {
#include
#include
/usr/lib/NetworkManager/nm-dhcp-helper mr,
/run/NetworkManager/private-dhcp rw,
signal (send) peer=/sbin/dhclient,
/var/lib/NetworkManager/*lease r,
signal (receive) peer=/usr/sbin/NetworkManager,
ptrace (readby) peer=/usr/sbin/NetworkManager,
network inet dgram,
network inet6 dgram,
}
/usr/libexec/nm-dhcp-helper {
#include
#include
/usr/libexec/nm-dhcp-helper mr,
/run/NetworkManager/private-dhcp rw,
signal (send) peer=/sbin/dhclient,
/var/lib/NetworkManager/*lease r,
signal (receive) peer=/usr/sbin/NetworkManager,
ptrace (readby) peer=/usr/sbin/NetworkManager,
network inet dgram,
network inet6 dgram,
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2083017/+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 2104920] Re: Installing libsdl2-dev:i386 purges important system files
Attached is a solver log. Note that I ran this on a machine with UBUNTY 24.04.01 (not the same machine as the one with 24.04.02 (as that one is now fixed using the workaround proposed earlier). Both 24.04.01 and 24.04.02 exhibit the same problem though. Thank you, have a nice day! ** Attachment added: "solver_log.tar.xz" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2104920/+attachment/5869380/+files/solver_log.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2104920 Title: Installing libsdl2-dev:i386 purges important system files Status in apt package in Ubuntu: Incomplete Status in libsdl2 package in Ubuntu: Invalid Bug description: The command: sudo apt install libsdl2-dev:i386 (on a 64bit ubuntu system) leads to the following being uninstalled: apport apport-core-dump-handler apport-gtk aptdaemon cloud-init command-not-found gdm3 gnome-control-center gnome-shell gnome-shell-extension-appindicator gnome-shell-extension-desktop-icons-ng gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-tiling-assistant gnome-terminal hplip ibus ibus-table ibus-table-cangjie-big ibus-table-cangjie3 ibus-table-cangjie5 language-selector-common language-selector-gnome memtest86+ nautilus-extension-gnome-terminal netplan.io network-manager network-manager-config-connectivity-ubuntu network-manager-gnome network-manager-openvpn network-manager-openvpn-gnome network-manager-pptp network-manager-pptp-gnome networkd-dispatcher nvidia-settings orca os-prober power-profiles-daemon python3-apport python3-aptdaemon python3-aptdaemon.gtk3widgets python3-brlapi python3-cairo python3-cffi-backend python3-commandnotfound python3-cryptography python3-cups python3-cupshelpers python3-dbus python3-distupgrade python3-gdbm python3-gi python3-ibus-1.0 python3-jinja2 python3-jsonschema python3-launchpadlib python3-lazr.restfulclient python3-markupsafe python3-netifaces python3-netplan python3-oauthlib python3-pil python3-pyrsistent python3-software-properties python3-sss python3-systemd python3-update-manager python3-yaml screen-resolution-extra software-properties-common software-properties-gtk sssd sssd-ad sssd-ad-common sssd-common sssd-ipa sssd-krb5 sssd-krb5-common sssd-ldap sssd-proxy system-config-printer-common system-config-printer-udev ubuntu-advantage-desktop-daemon ubuntu-desktop-minimal ubuntu-minimal ubuntu-pro-client ubuntu-pro-client-l10n ubuntu-release-upgrader-core ubuntu-release-upgrader-gtk ubuntu-session unattended-upgrades update-manager update-manager-core update-notifier update-notifier-common xorg xserver-xorg ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libsdl2-dev:i386 (not installed) ProcVersionSignature: Ubuntu 6.11.0-21.21~24.04.1-generic 6.11.11 Uname: Linux 6.11.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 28 14:25:55 2025 InstallationDate: Installed on 2025-03-28 (0 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) ProcEnviron: LANG=sv_SE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: libsdl2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2104920/+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 2106133] Re: Gnome Papers "Sign Digitally" Feature Fails Due to AppArmor Restrictions
Hi, John!
Gnome Papers fails to access my hardware token (a Giesecke & Devrient
GmbH StarSign CUT S USB device) due to an AppArmor denial. The error
message I see is:
Apr 02 23:31:26 desktop kernel: audit: type=1400
audit(1743647486.460:13357): apparmor="DENIED" operation="open"
class="file" profile="/usr/bin/papers" name="/sys/devices/pci:00/0>
As a result, the signing functionality in Gnome Papers doesn't work. From what
I understand, Gnome Papers attempts to access various hardware devices
(including smart cards, TPMs, and USB tokens like mine) because it needs to
request the device password to sign documents.
I think different hardware tokens may have different paths in
/sys/devices/, which is why the application may need to scan this tree.
--
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/2106133
Title:
Gnome Papers "Sign Digitally" Feature Fails Due to AppArmor
Restrictions
Status in AppArmor:
New
Status in apparmor package in Ubuntu:
New
Status in papers package in Ubuntu:
New
Bug description:
Description:
I am unable to digitally sign PDF documents in Gnome Papers using my hardware
device "Giesecke & Devrient GmbH StarSign CUT S" with a certificate. The
signing process fails due to AppArmor blocking access to necessary directories.
Affected Directories:
AppArmor restricts Gnome Papers from accessing the following paths:
~/.pki/nssdb
/sys/devices/
Steps to Reproduce:
1. Open Gnome Papers.
2. Attempt to sign a PDF using the "Sign Digitally" feature with a hardware
security device.
3. The signing process fails due to restricted access.
Workaround:
Manually editing the AppArmor profile resolves the issue:
Open the file "/etc/apparmor.d/usr.bin.papers" and add the following lines:
owner @{HOME}/.pki/** lrk,
/sys/devices/** r,
/run/pcscd/pcscd.comm rw,
Reload AppArmor:
sudo systemctl restart apparmor
Expected Behavior:
Gnome Papers should be able to access the necessary directories and sign PDFs
using the hardware device without requiring manual AppArmor modifications.
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: apparmor 4.1.0~beta5-0ubuntu12
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 3 10:50:21 2025
InstallationDate: Installed on 2025-04-02 (1 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Beta amd64 (20250326.6)
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.14.0-13-generic
root=UUID=e5c8dae6-79c1-4a2a-aa55-7a53dcc8a41b ro quiet splash pcie_aspm=off
nvme_core.default_ps_max_latency_us=0
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
vt.handoff=7
SourcePackage: apparmor
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2106133/+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 2018703] Re: Design or scour output flaws exist in many Humanity icons.
** Changed in: humanity-icon-theme (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2018703 Title: Design or scour output flaws exist in many Humanity icons. Status in humanity-icon-theme package in Ubuntu: Incomplete Bug description: The following icons have flaws consistent with SVG XML post-processing flaws. Humanity/actions/16/mail-mark-read.svg Humanity/actions/16/mail-read.svg Humanity/actions/16/mail-replied.svg Humanity/actions/22/media-seek-backward.svg Humanity/actions/22/media-seek-forward.svg Humanity/actions/22/sleep.svg Humanity/actions/24/media-seek-backward.svg Humanity/actions/24/media-seek-forward.svg Humanity/actions/24/sleep.svg Humanity/actions/48/go-bottom.svg Humanity/apps/22/gnome-session-hibernate.svg Humanity/apps/24/gnome-inhibit-applet.svg Humanity/apps/24/gnome-session-hibernate.svg Humanity/apps/24/ooo-impress.svg Humanity/apps/32/gnome-session-hibernate.svg Humanity/apps/48/gdm-setup.svg Humanity/apps/48/gnome-inhibit-applet.svg Humanity/apps/48/tsclient.svg Humanity/apps/48/wmtweaks.svg Humanity/categories/24/applications-other.svg Humanity/categories/24/preferences-other.svg Humanity/categories/32/applications-graphics.svg Humanity/devices/16/computer.svg Humanity/devices/22/computer.svg Humanity/devices/24/computer.svg Humanity/devices/48/gnome-dev-disc-dvdr.svg Humanity/mimes/48/text-x-java-source.svg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/2018703/+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 2106133] Re: Gnome Papers "Sign Digitally" Feature Fails Due to AppArmor Restrictions
Is gnome papers looking for a smart key or similar device, the tpm?
Giving it full access to the /sys/devices/ tree is certainly more than
it needs.
--
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/2106133
Title:
Gnome Papers "Sign Digitally" Feature Fails Due to AppArmor
Restrictions
Status in AppArmor:
New
Status in apparmor package in Ubuntu:
New
Status in papers package in Ubuntu:
New
Bug description:
Description:
I am unable to digitally sign PDF documents in Gnome Papers using my hardware
device "Giesecke & Devrient GmbH StarSign CUT S" with a certificate. The
signing process fails due to AppArmor blocking access to necessary directories.
Affected Directories:
AppArmor restricts Gnome Papers from accessing the following paths:
~/.pki/nssdb
/sys/devices/
Steps to Reproduce:
1. Open Gnome Papers.
2. Attempt to sign a PDF using the "Sign Digitally" feature with a hardware
security device.
3. The signing process fails due to restricted access.
Workaround:
Manually editing the AppArmor profile resolves the issue:
Open the file "/etc/apparmor.d/usr.bin.papers" and add the following lines:
owner @{HOME}/.pki/** lrk,
/sys/devices/** r,
/run/pcscd/pcscd.comm rw,
Reload AppArmor:
sudo systemctl restart apparmor
Expected Behavior:
Gnome Papers should be able to access the necessary directories and sign PDFs
using the hardware device without requiring manual AppArmor modifications.
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: apparmor 4.1.0~beta5-0ubuntu12
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 3 10:50:21 2025
InstallationDate: Installed on 2025-04-02 (1 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Beta amd64 (20250326.6)
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.14.0-13-generic
root=UUID=e5c8dae6-79c1-4a2a-aa55-7a53dcc8a41b ro quiet splash pcie_aspm=off
nvme_core.default_ps_max_latency_us=0
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
vt.handoff=7
SourcePackage: apparmor
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2106133/+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 2092232] Re: unable to deploy Plucky Puffin due to AppArmor lsblk denials
** Summary changed: - not able to deploy Plucky Puffin + unable to deploy Plucky Puffin due to AppArmor lsblk denials -- 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/2092232 Title: unable to deploy Plucky Puffin due to AppArmor lsblk denials Status in MAAS: Invalid Status in The Ubuntu-power-systems project: Confirmed Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Describe the bug: Deployment fails on Power9 and Power10 nodes when trying with Ubuntu 25.04/Plucky Puffin Actual behavior (what actually happened?): ``` Thu, 19 Dec. 2024 17:38:22 Marking node failed - Node operation 'Deploying' timed out after 30 minutes. Thu, 19 Dec. 2024 17:38:22 Node changed status - From 'Deploying' to 'Failed deployment' Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-keys_to_console with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-power_state_change with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-install_hotplug with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-ssh_authkey_fingerprints with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-final_message with frequency always Thu, 19 Dec. 2024 17:08:06 Rebooting ``` Looking its console, it seems deployment has finished quickly: ``` -END SSH HOST KEY KEYS- [ 29.557514] cloud-init[755]: Cloud-init v. 24.4-0ubuntu1 finished at Thu, 19 Dec 2024 17:10:00 +. Datasource DataSourceNone. Up 29.55 seconds [ 29.557942] cloud-init[755]: 2024-12-19 17:10:00,978 - cc_final_message.py[WARNING]: Used fallback datasource ... [ 29.563198] cloud-init[755]: +[SHA256]-+ Ubuntu Plucky Puffin (development branch) ubuntu hvc0 ubuntu login: ubuntu login: ``` but either way MAAS deployment fails. MAAS version: 3.5.2 Additional context: a) I'm able to deploy the same system, via MAAS, when trying with Jammy/Noble/Oracular b) Also able to deploy with Plucky Puffin .ISO image (also on the same system - P10rain-LPAR09). To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2092232/+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 2106177] [NEW] aa-notify's default configuration breaks the userns restriction by suggesting capabilities addition to unprivileged_userns
Public bug reported: The default configuration of aa-notify does not have any filtering on the notifications that it pops up, resulting in notifications that suggest adding capabilities to unprivileged_userns, circumventing and breaking the AppArmor userns restrictions. Since Plucky is very close to release, we will unfortunately have to go for a less invasive bugfix patch by adding filtering to the default config that filters out such notifications. However, this has lingering issues in that user configs that override the system config may result in such notifications appearing again. In the longer run, we will want to update aa-notify to fix this instead of depending on certain config values to be set. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2106177 Title: aa-notify's default configuration breaks the userns restriction by suggesting capabilities addition to unprivileged_userns Status in apparmor package in Ubuntu: New Bug description: The default configuration of aa-notify does not have any filtering on the notifications that it pops up, resulting in notifications that suggest adding capabilities to unprivileged_userns, circumventing and breaking the AppArmor userns restrictions. Since Plucky is very close to release, we will unfortunately have to go for a less invasive bugfix patch by adding filtering to the default config that filters out such notifications. However, this has lingering issues in that user configs that override the system config may result in such notifications appearing again. In the longer run, we will want to update aa-notify to fix this instead of depending on certain config values to be set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2106177/+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 2104316] Re: 25.04 beta TPMFDE: first boot failure
> - UKIs don't work with mem attribute protocol + secure boot enabled, this is likely due to systemd's borked hooking of the SEC ARCH 2 protocol pointer, which i assume is in protected memory... This makes sense because other systems boot after all. Is this "borked hooking" only in newer systemds? (because Noble TPM FDE installs apparently work with plucky ovmf) > I think we should get rid of the mem attribute protocol in ubuntu's edk2 until these are fixed. You marked the edk2 task as invalid, but this sounds like you think we should make a change to edk2? (even if it's not a bug in edk2, per se) -- 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/2104316 Title: 25.04 beta TPMFDE: first boot failure Status in Gadget snap for Personal Computers using Intel or AMD processors: New Status in Ubuntu: New Status in edk2 package in Ubuntu: Invalid Status in grub2 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 25.04 beta hybrid TPMFDE: first boot failure Using virt-manager, creating a VM, adjusting the firmware for UEFI (.ms), and adding a TPM (default settings), the resulting system appears to install but fails on first boot. The screen shows TianoCore along with BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... If I repeat this test with ubuntu 24.04.2 boot makes it boots as expected, showing this prior to continuing to the desktop: BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... /EndEntire /EndEntire On 24.04.2, if I hit escape during the /EndEntire bit, I can see the Grub menu offering the "Run Ubuntu Core" option, which never seems to work on the 25.04 beta install. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-pc/+bug/2104316/+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 2106133] Re: Gnome Papers "Sign Digitally" Feature Fails Due to AppArmor Restrictions
These are the messages in the journalctl:
Apr 02 23:23:23 desktop kernel: audit: type=1400 audit(1743647003.486:12599):
apparmor="DENIED" operation="file_lock" class="file" profile="/usr/bin/papers"
name="/home/cristiano/.pki/nssdb/cert9.db" pid=811514 comm="papers"
requested_mask="k" denied_mask="k" fsuid=1000 ouid=1000
Apr 02 23:25:37 desktop kernel: audit: type=1400
audit(1743647137.429:12896): apparmor="DENIED" operation="file_lock"
class="file" profile="/usr/bin/papers" name="/home/cristiano/.pki>
Apr 02 23:31:26 desktop kernel: audit: type=1400
audit(1743647486.460:13357): apparmor="DENIED" operation="open"
class="file" profile="/usr/bin/papers" name="/sys/devices/pci:00/0>
Apr 02 23:33:49 desktop kernel: audit: type=1400 audit(1743647629.944:13632):
apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/papers"
name="/run/pcscd/pcscd.comm">
My workaround to fix this issue is to edit the file
"/etc/apparmor.d/usr.bin.papers" and add the following lines:
owner @{HOME}/.pki/** lrk,
/sys/devices/** r,
/run/pcscd/pcscd.comm rw,
--
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/2106133
Title:
Gnome Papers "Sign Digitally" Feature Fails Due to AppArmor
Restrictions
Status in AppArmor:
New
Status in apparmor package in Ubuntu:
New
Status in papers package in Ubuntu:
New
Bug description:
Description:
I am unable to digitally sign PDF documents in Gnome Papers using my hardware
device "Giesecke & Devrient GmbH StarSign CUT S" with a certificate. The
signing process fails due to AppArmor blocking access to necessary directories.
Affected Directories:
AppArmor restricts Gnome Papers from accessing the following paths:
~/.pki/nssdb
/sys/devices/
Steps to Reproduce:
1. Open Gnome Papers.
2. Attempt to sign a PDF using the "Sign Digitally" feature with a hardware
security device.
3. The signing process fails due to restricted access.
Workaround:
Manually editing the AppArmor profile resolves the issue:
Open the file "/etc/apparmor.d/usr.bin.papers" and add the following lines:
owner @{HOME}/.pki/** lrk,
/sys/devices/** r,
/run/pcscd/pcscd.comm rw,
Reload AppArmor:
sudo systemctl restart apparmor
Expected Behavior:
Gnome Papers should be able to access the necessary directories and sign PDFs
using the hardware device without requiring manual AppArmor modifications.
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: apparmor 4.1.0~beta5-0ubuntu12
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 3 10:50:21 2025
InstallationDate: Installed on 2025-04-02 (1 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Beta amd64 (20250326.6)
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.14.0-13-generic
root=UUID=e5c8dae6-79c1-4a2a-aa55-7a53dcc8a41b ro quiet splash pcie_aspm=off
nvme_core.default_ps_max_latency_us=0
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
vt.handoff=7
SourcePackage: apparmor
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2106133/+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 2083017] Re: network-manager changed path to nm-dhcp-helper, apparmor need update
24.10 for me.
--
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/2083017
Title:
network-manager changed path to nm-dhcp-helper, apparmor need update
Status in apparmor package in Ubuntu:
Incomplete
Status in isc-dhcp package in Ubuntu:
Invalid
Bug description:
From the Debian Bug report logs - #1055067
isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper,
apparmor need update
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055067
The problem causes the DHCP fail to receive the IP with this error in
the dmesg command:
[ 1037.911083] audit: type=1400 audit(1727430402.572:1355):
apparmor="DENIED" operation="exec" class="file"
profile="/{,usr/}sbin/dhclient" name="/usr/libexec/nm-dhcp-helper"
pid=6763 comm="dhclient" requested_mask="x" denied_mask="x" fsuid=0
ouid=0
The /etc/apparmor.d/sbin.dhclient file needs to be updated to include
the /usr/libexec/nm-dhcp-helper (instead of
/usr/lib/NetworkManager/nm-dhcp-helper). Just in case, to solve it, I
duplicated the definitions for the NetworkManager/nm-dhcp-helper.
FILE: /etc/apparmor.d/sbin.dhclient
# Support the new executable helper from NetworkManager.
/usr/lib/NetworkManager/nm-dhcp-helper Pxrm,
signal (receive) peer=/usr/lib/NetworkManager/nm-dhcp-helper,
/usr/libexec/nm-dhcp-helper Pxrm,
signal (receive) peer=/usr/libexec/nm-dhcp-helper,
/usr/lib/NetworkManager/nm-dhcp-helper {
#include
#include
/usr/lib/NetworkManager/nm-dhcp-helper mr,
/run/NetworkManager/private-dhcp rw,
signal (send) peer=/sbin/dhclient,
/var/lib/NetworkManager/*lease r,
signal (receive) peer=/usr/sbin/NetworkManager,
ptrace (readby) peer=/usr/sbin/NetworkManager,
network inet dgram,
network inet6 dgram,
}
/usr/libexec/nm-dhcp-helper {
#include
#include
/usr/libexec/nm-dhcp-helper mr,
/run/NetworkManager/private-dhcp rw,
signal (send) peer=/sbin/dhclient,
/var/lib/NetworkManager/*lease r,
signal (receive) peer=/usr/sbin/NetworkManager,
ptrace (readby) peer=/usr/sbin/NetworkManager,
network inet dgram,
network inet6 dgram,
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2083017/+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 2061176] Re: [HP Envy x360 2-in-1 Laptop 16-ac0xxx, Realtek ALC245, Speaker, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2061176 Title: [HP Envy x360 2-in-1 Laptop 16-ac0xxx, Realtek ALC245, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: The speakers won't work on the new HP envy 360. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aknen 1487 F pulseaudio /dev/snd/pcmC0D6c: aknen 1487 F...m pulseaudio /dev/snd/pcmC0D0p: aknen 1487 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 14:34:46 2024 InstallationDate: Installed on 2024-04-10 (2 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aknen 1487 F pulseaudio /dev/snd/pcmC0D6c: aknen 1487 F...m pulseaudio /dev/snd/pcmC0D0p: aknen 1487 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Envy x360 2-in-1 Laptop 16-ac0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/05/2024 dmi.bios.release: 15.1 dmi.bios.vendor: Insyde dmi.bios.version: F.01 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8C66 dmi.board.vendor: HP dmi.board.version: 01.22 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnInsyde:bvrF.01:bd01/05/2024:br15.1:efr1.22:svnHP:pnHPEnvyx3602-in-1Laptop16-ac0xxx:pvrType1ProductConfigId:rvnHP:rn8C66:rvr01.22:cvnHP:ct31:cvrChassisVersion:sku9S1R5UA#ABA: dmi.product.family: 103C_5335M8 HP ENVY dmi.product.name: HP Envy x360 2-in-1 Laptop 16-ac0xxx dmi.product.sku: 9S1R5UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-04-12T14:25:11.869752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2061176/+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 2104316] Re: 25.04 beta TPMFDE: first boot failure
Two possible causes: - UKIs don't work with mem attribute protocol + secure boot enabled, this is likely due to systemd's borked hooking of the SEC ARCH 2 protocol pointer, which i assume is in protected memory... - grub page faults when running chainloader on kernel.efi , or linux + boot on kernel.efi, the exact cause of this is unclear right now. but probably because systemd-stub incorrectly marks itself as NX_COMPAT despite not being so. Both of these things need to be investigated. I think we should get rid of the mem attribute protocol in ubuntu's edk2 until these are fixed. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu) Assignee: (unassigned) => Mate Kukri (mkukri) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Mate Kukri (mkukri) -- 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/2104316 Title: 25.04 beta TPMFDE: first boot failure Status in Gadget snap for Personal Computers using Intel or AMD processors: New Status in Ubuntu: New Status in edk2 package in Ubuntu: New Status in grub2 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: 25.04 beta hybrid TPMFDE: first boot failure Using virt-manager, creating a VM, adjusting the firmware for UEFI (.ms), and adding a TPM (default settings), the resulting system appears to install but fails on first boot. The screen shows TianoCore along with BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... If I repeat this test with ubuntu 24.04.2 boot makes it boots as expected, showing this prior to continuing to the desktop: BdsDxe: loading Booot0003... BdsDxe: starting Booot0003... /EndEntire /EndEntire On 24.04.2, if I hit escape during the /EndEntire bit, I can see the Grub menu offering the "Run Ubuntu Core" option, which never seems to work on the 25.04 beta install. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-pc/+bug/2104316/+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 2106115] Re: Expose IFLA_VXLAN_FAN_MAP version via sysctl/proc
** Changed in: linux (Ubuntu Plucky) Status: New => In Progress ** Changed in: linux (Ubuntu Plucky) Assignee: (unassigned) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/2106115 Title: Expose IFLA_VXLAN_FAN_MAP version via sysctl/proc Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in iproute2 source package in Plucky: New Status in linux source package in Plucky: In Progress Bug description: [Impact] Expose the IFLA_VXLAN_FAN_MAP constant via /proc and systcl, allowing user space (e.g. iproute2) to consume it at run-time [Fix] Apply the attached patch and rebuild the kernel [How to test] $ sudo modprobe vxlan $ sudo sysctl -a | grep -i vxlan net.fan.IFLA_VXLAN_FAN_MAP = 34 net.fan.vxlan = 4 $ cat /proc/sys/net/fan/IFLA_VXLAN_FAN_MAP 34 [Regression potential] None, we are adding a new /proc / sysctl entry and no sw depends on it ATM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2106115/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
** Tags removed: mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 2103839] Re: timedatectl set-timezone does not update /etc/timezone, leaving system with inconsistent time zone setting
Thanks, all, for taking the time to look into my bug report. Since I don't control the application that first caused me to notice this bug, and I can't stop it from preferring /etc/timezone over other time zone sources, I will implement the given workaround on my servers. Thank you for providing an official workaround and stance on the issue. -- 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/2103839 Title: timedatectl set-timezone does not update /etc/timezone, leaving system with inconsistent time zone setting Status in systemd package in Ubuntu: Won't Fix Status in systemd source package in Noble: Won't Fix Status in systemd source package in Oracular: Won't Fix Bug description: [WORKAROUND FOR AFFECTED USERS] /etc/timezone will be dropped entirely in Ubuntu 25.10. Please update affected applications to use /etc/localtime instead of /etc/timezone. Please see [1], and more specifically [2], if you need to keep /etc/timezone up-to-date on Ubuntu 24.04 LTS. [1] https://discourse.ubuntu.com/t/how-to-change-the-time-zone-in-ubuntu-using-the-command-line/35307 [2] https://discourse.ubuntu.com/t/how-to-change-the-time-zone-in-ubuntu-using-the-command-line/35307/2 [Original Description] In Ubuntu 24.04 server, setting the system time zone via systemd's timedatectl fails to update the contents of /etc/timezone. In previous LTS server releases, timedatectl updated this file without any issue, so this is new faulty behavior. Because there are several different ways to query for the system's time zone (e.g., timedatectl, /etc/localtime, /etc/timezone), this bug leaves the system time zone in an inconsistent state, with the answer depending on the query method. For example, I discovered this bug when installing the latest version of Jenkins on Ubuntu 24.04, where Jenkins insisted my server was on UTC even though timedatectl would report back "America/Chicago". It turned out that Jenkins was reading the system time zone from /etc/timezone, which had never been updated after I set the timezone via timedatectl. I don't know for certain, but I believe that /etc/timezone is a common way for Java-based applications to read the system time zone. I think there has been talk of removing /etc/timezone entirely from Debian, since it could be considered redundant, which may be why timedatectl has changed its behavior here. I would be fine with that solution except for the fact that when I delete /etc/timezone on Ubuntu 24.04, it keeps getting recreated. I believe whenever the tzdata package is updated, that regenerates /etc/timezone, and a "dpkg-reconfigure tzdata" certainly does. If nothing else, there is an inconsistency in Ubuntu 24.04 between the behavior of timedatectl and the behavior of tzdata, and this inconsistent behavior can lead to an inconsistent time zone setting. Steps to reproduce the bug: ``` $ timedatectl show --property=Timezone Timezone=America/New_York $ ls -la /etc/localtime lrwxrwxrwx 1 root root 36 Mar 21 21:46 /etc/localtime -> /usr/share/zoneinfo/America/New_York $ cat /etc/timezone America/New_York $ sudo timedatectl set-timezone 'America/Chicago' $ timedatectl show --property=Timezone Timezone=America/Chicago $ ls -la /etc/localtime lrwxrwxrwx 1 root root 35 Mar 21 20:51 /etc/localtime -> /usr/share/zoneinfo/America/Chicago $ cat /etc/timezone America/New_York $ sudo dpkg-reconfigure --frontend noninteractive tzdata 2> /dev/null $ cat /etc/timezone America/Chicago ``` ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.5 ProcVersionSignature: Ubuntu 6.8.0-55.57-generic 6.8.12 Uname: Linux 6.8.0-55-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 21 18:20:28 2025 InstallationDate: Installed on 2025-02-11 (38 days ago) InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware7,1 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-55-generic root=UUID=d1d2bd07-2fa1-4f46-b54e-6b249e25a778 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.16707776.B64.2008070230 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvn
[Touch-packages] [Bug 2103839] Re: timedatectl set-timezone does not update /etc/timezone, leaving system with inconsistent time zone setting
** Description changed: + [WORKAROUND FOR AFFECTED USERS] + + /etc/timezone will be dropped entirely in Ubuntu 25.10. Please update + affected applications to use /etc/localtime instead of /etc/timezone. + + Please see [1], and more specifically [2], if you need to keep + /etc/timezone up-to-date on Ubuntu 24.04 LTS. + + [1] https://discourse.ubuntu.com/t/how-to-change-the-time-zone-in-ubuntu-using-the-command-line/35307 + [2] https://discourse.ubuntu.com/t/how-to-change-the-time-zone-in-ubuntu-using-the-command-line/35307/2 + + + [Original Description] + In Ubuntu 24.04 server, setting the system time zone via systemd's timedatectl fails to update the contents of /etc/timezone. In previous LTS server releases, timedatectl updated this file without any issue, so this is new faulty behavior. Because there are several different ways to query for the system's time zone (e.g., timedatectl, /etc/localtime, /etc/timezone), this bug leaves the system time zone in an inconsistent state, with the answer depending on the query method. For example, I discovered this bug when installing the latest version of Jenkins on Ubuntu 24.04, where Jenkins insisted my server was on UTC even though timedatectl would report back "America/Chicago". It turned out that Jenkins was reading the system time zone from /etc/timezone, which had never been updated after I set the timezone via timedatectl. I don't know for certain, but I believe that /etc/timezone is a common way for Java-based applications to read the system time zone. I think there has been talk of removing /etc/timezone entirely from Debian, since it could be considered redundant, which may be why timedatectl has changed its behavior here. I would be fine with that solution except for the fact that when I delete /etc/timezone on Ubuntu 24.04, it keeps getting recreated. I believe whenever the tzdata package is updated, that regenerates /etc/timezone, and a "dpkg- reconfigure tzdata" certainly does. If nothing else, there is an inconsistency in Ubuntu 24.04 between the behavior of timedatectl and the behavior of tzdata, and this inconsistent behavior can lead to an inconsistent time zone setting. - Steps to reproduce the bug: ``` $ timedatectl show --property=Timezone Timezone=America/New_York $ ls -la /etc/localtime lrwxrwxrwx 1 root root 36 Mar 21 21:46 /etc/localtime -> /usr/share/zoneinfo/America/New_York $ cat /etc/timezone America/New_York $ sudo timedatectl set-timezone 'America/Chicago' $ timedatectl show --property=Timezone Timezone=America/Chicago $ ls -la /etc/localtime lrwxrwxrwx 1 root root 35 Mar 21 20:51 /etc/localtime -> /usr/share/zoneinfo/America/Chicago $ cat /etc/timezone America/New_York $ sudo dpkg-reconfigure --frontend noninteractive tzdata 2> /dev/null $ cat /etc/timezone America/Chicago ``` ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.5 ProcVersionSignature: Ubuntu 6.8.0-55.57-generic 6.8.12 Uname: Linux 6.8.0-55-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 21 18:20:28 2025 InstallationDate: Installed on 2025-02-11 (38 days ago) InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: - + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware7,1 ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-55-generic root=UUID=d1d2bd07-2fa1-4f46-b54e-6b249e25a778 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.16707776.B64.2008070230 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.16707776.B64.2008070230:bd08/07/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Changed in: systemd (Ubuntu) Status: New => Won't Fix ** Changed in: systemd (Ubuntu Noble) Status: New => Won't Fix ** Changed in: systemd (Ubuntu Oracular) Status: New => Won't Fix -- 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/2103839 Title: timedatectl s
[Touch-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** No longer affects: gtk4 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 2106017] Re: Network manager still adds default ipv6 route despite setting to ignore it
** Tags added: server-triage-discuss -- 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/2106017 Title: Network manager still adds default ipv6 route despite setting to ignore it Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: This is my VPN connection. I set not to add DNS resolving (ipv6.ignore-auto-dns: "true") and default route for ipv6 (ipv6.never- default: "true") Yet after connection it still set the default route via tun0 These routes I get: 2a00:1398:300:14::/64 dev tun0 proto kernel metric 50 pref medium 2000::/3 via 2a00:1398:300:14::1 dev tun0 proto static metric 50 pref medium For instance $ dig en.wikipedia.org +short dyna.wikimedia.org. 2a02:ec80:300:ed1a::1 $ sudo ip -6 r get 2a02:ec80:300:ed1a::1 2a02:ec80:300:ed1a::1 from :: via 2a00:1398:300:14::1 dev tun0 proto static src 2a00:1398:300:14::1080 metric 50 pref medium Maybe I don't understand something here. But the above subnets does not cover en.wikipedia.org ipv6 . $ sudo cat /etc/netplan/90-NM-6be5abbb-c998-4f66-9752-e2d10a6c13b4.yaml network: version: 2 nm-devices: NM-6be5abbb-c998-4f66-9752-e2d10a6c13b4: renderer: NetworkManager networkmanager: uuid: "6be5abbb-c998-4f66-9752-e2d10a6c13b4" name: "CENSORED" passthrough: connection.type: "vpn" connection.timestamp: "1743602165" vpn.ca: "/home/mastier/.cert/CENSORED.pem" vpn.connect-timeout: "5" vpn.connection-type: "password" vpn.dev: "tun" vpn.password-flags: "1" vpn.remote: "CENSORED:1194:udp" vpn.tls-version-min: "1.3" vpn.username: "CENSORED" vpn.verify-x509-name: "name:CENSORED" vpn.service-type: "org.freedesktop.NetworkManager.openvpn" ipv4.method: "auto" ipv4.never-default: "true" ipv6.addr-gen-mode: "default" ipv6.ignore-auto-dns: "true" ipv6.method: "auto" ipv6.never-default: "true" proxy._: "" $ apt-cache policy network-manager network-manager: Installed: 1.46.0-1ubuntu2.2 Candidate: 1.46.0-1ubuntu2.2 Version table: *** 1.46.0-1ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.46.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages $ apt-cache policy network-manager-openvpn network-manager-openvpn: Installed: 1.10.2-4build2 Candidate: 1.10.2-4build2 Version table: *** 1.10.2-4build2 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy netplan.io netplan.io: Installed: 1.1.1-1~ubuntu24.04.1 Candidate: 1.1.1-1~ubuntu24.04.1 Version table: *** 1.1.1-1~ubuntu24.04.1 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0-2ubuntu1.2 500 500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages 1.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2106017/+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 2092232] Re: unable to deploy Plucky Puffin due to AppArmor lsblk denials
Many thanks for checking it Jacopo. The issue mentioned on comment #9, is only happening with virtualized nodes, qemu/kvm and PowerVM LPARs. We're able to get the proper lsblk output when running from a Power9 bare metal with Plucky (upgraded from Oracular -> Plucky)**. But regarding the original bug description - Plucky still fails to deploy via MAAS on arm64 and amd64, same as mentioned on comment #3 - I was rechecking it, able to deploy 4 nodes with Oracular and they all fail when trying to deploy Plucky with: Thu, 03 Apr. 2025 18:57:21 Marking node failed - Node operation 'Deploying' timed out after 30 minutes. ... Thu, 03 Apr. 2025 18:24:48 Node installation - 'cloudinit' running config-ssh_authkey_fingerprints with frequency once-per-instance Thu, 03 Apr. 2025 18:24:48 Rebooting ** `lsblk` output from P9 bare metal: patricia@p9bm-b:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:00 1.8T 0 disk ├─sda1 8:108M 0 part ├─sda2 8:202G 0 part /boot └─sda3 8:30 1.8T 0 part └─ubuntu--vg-ubuntu--lv 252:00 100G 0 lvm / sr011:01 1.5G 0 rom (There's also an issue installing Plucky (.ISO) on Power9 bare metal: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2104297 , but this is a separate issue). -- 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/2092232 Title: unable to deploy Plucky Puffin due to AppArmor lsblk denials Status in MAAS: Invalid Status in The Ubuntu-power-systems project: Confirmed Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Describe the bug: Deployment fails on Power9 and Power10 nodes when trying with Ubuntu 25.04/Plucky Puffin Actual behavior (what actually happened?): ``` Thu, 19 Dec. 2024 17:38:22 Marking node failed - Node operation 'Deploying' timed out after 30 minutes. Thu, 19 Dec. 2024 17:38:22 Node changed status - From 'Deploying' to 'Failed deployment' Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-keys_to_console with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-power_state_change with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-install_hotplug with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-ssh_authkey_fingerprints with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-final_message with frequency always Thu, 19 Dec. 2024 17:08:06 Rebooting ``` Looking its console, it seems deployment has finished quickly: ``` -END SSH HOST KEY KEYS- [ 29.557514] cloud-init[755]: Cloud-init v. 24.4-0ubuntu1 finished at Thu, 19 Dec 2024 17:10:00 +. Datasource DataSourceNone. Up 29.55 seconds [ 29.557942] cloud-init[755]: 2024-12-19 17:10:00,978 - cc_final_message.py[WARNING]: Used fallback datasource ... [ 29.563198] cloud-init[755]: +[SHA256]-+ Ubuntu Plucky Puffin (development branch) ubuntu hvc0 ubuntu login: ubuntu login: ``` but either way MAAS deployment fails. MAAS version: 3.5.2 Additional context: a) I'm able to deploy the same system, via MAAS, when trying with Jammy/Noble/Oracular b) Also able to deploy with Plucky Puffin .ISO image (also on the same system - P10rain-LPAR09). To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2092232/+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 2103839] Re: timedatectl set-timezone does not update /etc/timezone, leaving system with inconsistent time zone setting
I wrote https://discourse.ubuntu.com/t/how-to-change-the-time-zone-in- ubuntu-using-the-command-line/35307 some time ago. The plan for the 25.10 release is to drop /etc/timezone completely. -- 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/2103839 Title: timedatectl set-timezone does not update /etc/timezone, leaving system with inconsistent time zone setting Status in systemd package in Ubuntu: New Status in systemd source package in Noble: New Status in systemd source package in Oracular: New Bug description: In Ubuntu 24.04 server, setting the system time zone via systemd's timedatectl fails to update the contents of /etc/timezone. In previous LTS server releases, timedatectl updated this file without any issue, so this is new faulty behavior. Because there are several different ways to query for the system's time zone (e.g., timedatectl, /etc/localtime, /etc/timezone), this bug leaves the system time zone in an inconsistent state, with the answer depending on the query method. For example, I discovered this bug when installing the latest version of Jenkins on Ubuntu 24.04, where Jenkins insisted my server was on UTC even though timedatectl would report back "America/Chicago". It turned out that Jenkins was reading the system time zone from /etc/timezone, which had never been updated after I set the timezone via timedatectl. I don't know for certain, but I believe that /etc/timezone is a common way for Java-based applications to read the system time zone. I think there has been talk of removing /etc/timezone entirely from Debian, since it could be considered redundant, which may be why timedatectl has changed its behavior here. I would be fine with that solution except for the fact that when I delete /etc/timezone on Ubuntu 24.04, it keeps getting recreated. I believe whenever the tzdata package is updated, that regenerates /etc/timezone, and a "dpkg-reconfigure tzdata" certainly does. If nothing else, there is an inconsistency in Ubuntu 24.04 between the behavior of timedatectl and the behavior of tzdata, and this inconsistent behavior can lead to an inconsistent time zone setting. Steps to reproduce the bug: ``` $ timedatectl show --property=Timezone Timezone=America/New_York $ ls -la /etc/localtime lrwxrwxrwx 1 root root 36 Mar 21 21:46 /etc/localtime -> /usr/share/zoneinfo/America/New_York $ cat /etc/timezone America/New_York $ sudo timedatectl set-timezone 'America/Chicago' $ timedatectl show --property=Timezone Timezone=America/Chicago $ ls -la /etc/localtime lrwxrwxrwx 1 root root 35 Mar 21 20:51 /etc/localtime -> /usr/share/zoneinfo/America/Chicago $ cat /etc/timezone America/New_York $ sudo dpkg-reconfigure --frontend noninteractive tzdata 2> /dev/null $ cat /etc/timezone America/Chicago ``` ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.5 ProcVersionSignature: Ubuntu 6.8.0-55.57-generic 6.8.12 Uname: Linux 6.8.0-55-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 21 18:20:28 2025 InstallationDate: Installed on 2025-02-11 (38 days ago) InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware7,1 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-55-generic root=UUID=d1d2bd07-2fa1-4f46-b54e-6b249e25a778 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.16707776.B64.2008070230 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.16707776.B64.2008070230:bd08/07/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2103839/+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 2092232] Re: unable to deploy Plucky Puffin due to AppArmor lsblk denials
@patricia that one should be fixed by https://bugs.launchpad.net/maas/+bug/2104530 . The hotfix will be rolled out to TOR3 tomorrow. -- 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/2092232 Title: unable to deploy Plucky Puffin due to AppArmor lsblk denials Status in MAAS: Invalid Status in The Ubuntu-power-systems project: Confirmed Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Describe the bug: Deployment fails on Power9 and Power10 nodes when trying with Ubuntu 25.04/Plucky Puffin Actual behavior (what actually happened?): ``` Thu, 19 Dec. 2024 17:38:22 Marking node failed - Node operation 'Deploying' timed out after 30 minutes. Thu, 19 Dec. 2024 17:38:22 Node changed status - From 'Deploying' to 'Failed deployment' Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-keys_to_console with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-power_state_change with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-install_hotplug with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-ssh_authkey_fingerprints with frequency once-per-instance Thu, 19 Dec. 2024 17:08:06 Node installation - 'cloudinit' running config-final_message with frequency always Thu, 19 Dec. 2024 17:08:06 Rebooting ``` Looking its console, it seems deployment has finished quickly: ``` -END SSH HOST KEY KEYS- [ 29.557514] cloud-init[755]: Cloud-init v. 24.4-0ubuntu1 finished at Thu, 19 Dec 2024 17:10:00 +. Datasource DataSourceNone. Up 29.55 seconds [ 29.557942] cloud-init[755]: 2024-12-19 17:10:00,978 - cc_final_message.py[WARNING]: Used fallback datasource ... [ 29.563198] cloud-init[755]: +[SHA256]-+ Ubuntu Plucky Puffin (development branch) ubuntu hvc0 ubuntu login: ubuntu login: ``` but either way MAAS deployment fails. MAAS version: 3.5.2 Additional context: a) I'm able to deploy the same system, via MAAS, when trying with Jammy/Noble/Oracular b) Also able to deploy with Plucky Puffin .ISO image (also on the same system - P10rain-LPAR09). To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2092232/+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 2103839] Re: timedatectl set-timezone does not update /etc/timezone, leaving system with inconsistent time zone setting
After looking at this further, I think this is the best we can do for noble. Among other things, the reason the downstream patch that supported /etc/timezone in systemd was dropped is that it was difficult to keep correct as the locations in the codebase which referenced /etc/localtime grew/changed. While other components may use /etc/timezone, that file is owned by tzdata, and so that package is responsible for updating the contents. I think pointing to this[1] discourse post, and in particular this[2] comment, is the best way to document the expected behavior. [1] https://discourse.ubuntu.com/t/how-to-change-the-time-zone-in-ubuntu-using-the-command-line/35307 [2] https://discourse.ubuntu.com/t/how-to-change-the-time-zone-in-ubuntu-using-the-command-line/35307/2 -- 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/2103839 Title: timedatectl set-timezone does not update /etc/timezone, leaving system with inconsistent time zone setting Status in systemd package in Ubuntu: New Status in systemd source package in Noble: New Status in systemd source package in Oracular: New Bug description: In Ubuntu 24.04 server, setting the system time zone via systemd's timedatectl fails to update the contents of /etc/timezone. In previous LTS server releases, timedatectl updated this file without any issue, so this is new faulty behavior. Because there are several different ways to query for the system's time zone (e.g., timedatectl, /etc/localtime, /etc/timezone), this bug leaves the system time zone in an inconsistent state, with the answer depending on the query method. For example, I discovered this bug when installing the latest version of Jenkins on Ubuntu 24.04, where Jenkins insisted my server was on UTC even though timedatectl would report back "America/Chicago". It turned out that Jenkins was reading the system time zone from /etc/timezone, which had never been updated after I set the timezone via timedatectl. I don't know for certain, but I believe that /etc/timezone is a common way for Java-based applications to read the system time zone. I think there has been talk of removing /etc/timezone entirely from Debian, since it could be considered redundant, which may be why timedatectl has changed its behavior here. I would be fine with that solution except for the fact that when I delete /etc/timezone on Ubuntu 24.04, it keeps getting recreated. I believe whenever the tzdata package is updated, that regenerates /etc/timezone, and a "dpkg-reconfigure tzdata" certainly does. If nothing else, there is an inconsistency in Ubuntu 24.04 between the behavior of timedatectl and the behavior of tzdata, and this inconsistent behavior can lead to an inconsistent time zone setting. Steps to reproduce the bug: ``` $ timedatectl show --property=Timezone Timezone=America/New_York $ ls -la /etc/localtime lrwxrwxrwx 1 root root 36 Mar 21 21:46 /etc/localtime -> /usr/share/zoneinfo/America/New_York $ cat /etc/timezone America/New_York $ sudo timedatectl set-timezone 'America/Chicago' $ timedatectl show --property=Timezone Timezone=America/Chicago $ ls -la /etc/localtime lrwxrwxrwx 1 root root 35 Mar 21 20:51 /etc/localtime -> /usr/share/zoneinfo/America/Chicago $ cat /etc/timezone America/New_York $ sudo dpkg-reconfigure --frontend noninteractive tzdata 2> /dev/null $ cat /etc/timezone America/Chicago ``` ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.5 ProcVersionSignature: Ubuntu 6.8.0-55.57-generic 6.8.12 Uname: Linux 6.8.0-55-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 21 18:20:28 2025 InstallationDate: Installed on 2025-02-11 (38 days ago) InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware7,1 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-55-generic root=UUID=d1d2bd07-2fa1-4f46-b54e-6b249e25a778 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.16707776.B64.2008070230 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.16707776.B64.2008070230:bd08/07/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporati
[Touch-packages] [Bug 2035050] Re: gsettings-ubuntu-schemas is a recommended dependency of ubuntu-desktop metapackages
** Tags removed: mantic ** Tags added: plucky -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-ubuntu-touch- schemas in Ubuntu. https://bugs.launchpad.net/bugs/2035050 Title: gsettings-ubuntu-schemas is a recommended dependency of ubuntu-desktop metapackages Status in GSettings Ubuntu touch schemas: New Status in gsettings-ubuntu-touch-schemas package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: The mostly empty entries have remained the same since Jammy. Most or all of the settings seem not functional or invalid on a the standard installation with Gnome. /usr/share/glib-2.0/schemas/com.canonical.unity.desktop.gschema.xml /usr/share/glib-2.0/schemas/com.ubuntu.notifications.hub.gschema.xml /usr/share/glib-2.0/schemas/com.ubuntu.notifications.settings.gschema.xml /usr/share/glib-2.0/schemas/com.ubuntu.phone.gschema.xml /usr/share/glib-2.0/schemas/com.ubuntu.sound.gschema.xml /usr/share/glib-2.0/schemas/com.ubuntu.touch.network.gschema.xml /usr/share/glib-2.0/schemas/com.ubuntu.touch.sound.gschema.xml /usr/share/glib-2.0/schemas/com.ubuntu.touch.system.gschema.xml /usr/share/glib-2.0/schemas/com.ubuntu.user-interface.gschema.xml To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-ubuntu-touch-schemas/+bug/2035050/+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 2061176] Re: [HP Envy x360 2-in-1 Laptop 16-ac0xxx, Realtek ALC245, Speaker, Internal] No sound at all
GNU nano 7.2 hardware-info.txt 00:00.0 Host bridge: Intel Corporation Alder Lake Host and DRAM Controller (rev 06) Subsystem: Hewlett-Packard Company Alder Lake Host and DRAM Controller Flags: bus master, fast devsel, latency 0, IOMMU group 2 Capabilities: Kernel driver in use: igen6_edac Kernel modules: igen6_edac 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-UP4 GT2 [Iris Xe Graphics] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Alder Lake-UP4 GT2 [Iris Xe Graphics] Flags: bus master, fast devsel, latency 0, IRQ 213, IOMMU group 1 Memory at 603d00 (64-bit, non-prefetchable) [size=16M] Memory at 40 (64-bit, prefetchable) [size=256M] I/O ports at 3000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915, xe 00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 06) Subsystem: Hewlett-Packard Company Alder Lake Innovation Platform Framework Processor Participant Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 3 Memory at 603e14 (64-bit, non-prefetchable) [size=128K] Capabilities: Kernel driver in use: proc_thermal_pci Kernel modules: processor_thermal_device_pci 00:05.0 Multimedia controller: Intel Corporation Alder Lake Imaging Signal Processor (rev 06) Subsystem: Hewlett-Packard Company Alder Lake Imaging Signal Processor Flags: bus master, fast devsel, latency 0, IRQ 255, IOMMU group 0 Memory at 603c00 (64-bit, non-prefetchable) [size=16M] Capabilities: Kernel modules: intel_ipu6, intel_ipu6_psys, intel_ipu6_isys 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 06) (prog-if 00 [Normal decode]) Subsystem: Hewlett-Packard Company 12th Gen Core Processor PCI Express x4 Controller Flags: bus master, fast devsel, latency 0, IRQ 123, IOMMU group 4 Bus: primary=00, secondary=01, subordinate=29, sec-latency=0 I/O behind bridge: [disabled] [16-bit] Memory behind bridge: 6e00-7a1f [size=194M] [32-bit] Prefetchable memory behind bridge: 60-601bff [size=448M] [32-bit] Capabilities: Kernel driver in use: pcieport 00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 06) (prog-if 00 [Normal decode]) Subsystem: Hewlett-Packard Company Alder Lake-P Thunderbolt 4 PCI Express Root Port Flags: bus master, fast devsel, latency 0, IRQ 124, IOMMU group 5 Bus: primary=00, secondary=2a, subordinate=52, sec-latency=0 I/O behind bridge: 4000-4fff [size=4K] [16-bit] Memory behind bridge: 6000-6c1f [size=194M] [32-bit] Prefetchable memory behind bridge: 602000-603bff [size=448M] [32-bit] Capabilities: Kernel driver in use: pcieport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2061176 Title: [HP Envy x360 2-in-1 Laptop 16-ac0xxx, Realtek ALC245, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: The speakers won't work on the new HP envy 360. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aknen 1487 F pulseaudio /dev/snd/pcmC0D6c: aknen 1487 F...m pulseaudio /dev/snd/pcmC0D0p: aknen 1487 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 14:34:46 2024 InstallationDate: Installed on 2024-04-10 (2 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aknen 1487 F pulseaudio /dev/snd/pcmC0D6c: aknen 1487 F...m pulseaudio /dev/snd/pcmC0D0p: aknen 1487 F...m pulseaudio Symptom_J
[Touch-packages] [Bug 2033165] Re: 310 empty dirs created by hicolor-icon-theme
** Changed in: hicolor-icon-theme (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2033165 Title: 310 empty dirs created by hicolor-icon-theme Status in hicolor-icon-theme package in Ubuntu: Incomplete Bug description: 310 empty dirs created by hicolor-icon-theme 0.17-2 in Mantic. 0.17-2 was first published 2018-03-19 11:33:46 UTC for Bionic. find /usr/share/icons/hicolor/ -type d -empty && find /usr/share/icons/hicolor/ -type d -empty | grep -c '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/2033165/+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 2103945] Re: Qt 6.8.3 in Ubuntu 25.04
This bug was fixed in the package nvidia-cuda-toolkit - 12.2.2-2build1 --- nvidia-cuda-toolkit (12.2.2-2build1) plucky; urgency=medium * No-change rebuild for Qt 6.8.3 (LP: #2103945). -- Simon Quigley Sat, 29 Mar 2025 15:06:25 -0500 ** Changed in: qt6-5compat (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 gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2103945 Title: Qt 6.8.3 in Ubuntu 25.04 Status in calibre package in Ubuntu: Fix Committed Status in copyq package in Ubuntu: Fix Committed Status in digikam package in Ubuntu: Fix Released Status in dolphin package in Ubuntu: Fix Committed Status in dtk6log package in Ubuntu: Fix Committed Status in elisa-player package in Ubuntu: Fix Released Status in fcitx-qt5 package in Ubuntu: Fix Committed Status in fcitx5-qt package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gammaray package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gwenview package in Ubuntu: Fix Committed Status in haruna package in Ubuntu: Fix Committed Status in itinerary package in Ubuntu: Fix Released Status in kaidan package in Ubuntu: Fix Released Status in kasts package in Ubuntu: Fix Committed Status in kate package in Ubuntu: Fix Committed Status in kde-cli-tools package in Ubuntu: Fix Released Status in kde-spectacle package in Ubuntu: Fix Released Status in kdeconnect package in Ubuntu: Fix Released Status in kf6-kcmutils package in Ubuntu: Fix Released Status in kf6-kcolorscheme package in Ubuntu: Fix Released Status in kf6-kconfigwidgets package in Ubuntu: Fix Committed Status in kf6-kdbusaddons package in Ubuntu: Fix Released Status in kf6-kglobalaccel package in Ubuntu: Fix Committed Status in kf6-kiconthemes package in Ubuntu: Fix Released Status in kf6-kio package in Ubuntu: Fix Released Status in kf6-kirigami package in Ubuntu: Fix Released Status in kf6-kjobwidgets package in Ubuntu: Fix Released Status in kf6-kwindowsystem package in Ubuntu: Fix Committed Status in kf6-kxmlgui package in Ubuntu: Fix Committed Status in kf6-qqc2-desktop-style package in Ubuntu: Fix Committed Status in kglobalacceld package in Ubuntu: Fix Committed Status in kinfocenter package in Ubuntu: Fix Committed Status in kirigami-addons package in Ubuntu: Fix Released Status in koko package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Committed Status in kontactinterface package in Ubuntu: Fix Released Status in kosmindoormap package in Ubuntu: Fix Committed Status in kquickimageeditor package in Ubuntu: Fix Released Status in krfb package in Ubuntu: Fix Released Status in kruler package in Ubuntu: Fix Committed Status in kscreen package in Ubuntu: Fix Committed Status in kscreenlocker package in Ubuntu: Fix Released Status in kwayland package in Ubuntu: Fix Committed Status in kwin package in Ubuntu: Fix Committed Status in layer-shell-qt package in Ubuntu: Fix Released Status in libfm-qt package in Ubuntu: Fix Released Status in libkscreen package in Ubuntu: Fix Released Status in libqtxdg package in Ubuntu: Fix Released Status in lxqt-qtplugin package in Ubuntu: Fix Released Status in nheko package in Ubuntu: Fix Committed Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in okular package in Ubuntu: Fix Released Status in oxygen package in Ubuntu: Fix Released Status in photoqt package in Ubuntu: Fix Committed Status in plasma-desktop package in Ubuntu: Fix Committed Status in plasma-integration package in Ubuntu: Fix Committed Status in plasma-mobile package in Ubuntu: Fix Released Status in plasma-workspace package in Ubuntu: Fix Committed Status in plasma5support package in Ubuntu: Fix Released Status in powerdevil package in Ubuntu: Fix Committed Status in pyqt6 package in Ubuntu: Fix Released Status in pyside6 package in Ubuntu: Fix Committed Status in qcoro package in Ubuntu: Fix Committed Status in qgnomeplatform package in Ubuntu: Fix Released Status in qt6-3d package in Ubuntu: Fix Released Status in qt6-5compat package in Ubuntu: Fix Released Status in qt6-base package in Ubuntu: Fix Released Status in qt6-charts package in Ubuntu: Fix Released Status in qt6-connectivity package in Ubuntu: Fix Released Status in qt6-datavis3d package in Ubuntu: Fix Released Status in qt6-declarative package in Ubuntu: Fix Committed Status in qt6-graphs package in Ubuntu: Fix Committed Status in qt6-grpc package in Ubuntu: Fix Committed Status in qt6-httpserver package in Ubuntu: Fix Committed Status in qt6-imageformats package in Ubuntu: Fix Committed Status in qt6-languageserver package in Ubuntu: Fix Released Status in qt6-location package in Ubuntu: Fix
[Touch-packages] [Bug 2103916] Re: Please remove libsynthesis from Ubuntu
(main)mwhudson@orcrist:~/src/ubuntu/ubuntu-archive-tools$ ./remove-package -m "Remove packages that transitively depende on pcre3 (LP: #2103916)" -s plucky lomiri-sync-monitor libsynthesis Removing packages from plucky: lomiri-sync-monitor 0.6.0-4 in plucky lomiri-sync-monitor 0.6.0-4 in plucky amd64 lomiri-sync-monitor 0.6.0-4 in plucky arm64 lomiri-sync-monitor 0.6.0-4 in plucky armhf lomiri-sync-monitor 0.6.0-4 in plucky ppc64el lomiri-sync-monitor 0.6.0-4 in plucky riscv64 lomiri-sync-monitor 0.6.0-4 in plucky s390x lomiri-sync-monitor-helper 0.6.0-4 in plucky amd64 lomiri-sync-monitor-helper 0.6.0-4 in plucky arm64 lomiri-sync-monitor-helper 0.6.0-4 in plucky armhf lomiri-sync-monitor-helper 0.6.0-4 in plucky ppc64el lomiri-sync-monitor-helper 0.6.0-4 in plucky riscv64 lomiri-sync-monitor-helper 0.6.0-4 in plucky s390x lomiri-sync-monitor-loa 0.6.0-4 in plucky amd64 lomiri-sync-monitor-loa 0.6.0-4 in plucky arm64 lomiri-sync-monitor-loa 0.6.0-4 in plucky armhf lomiri-sync-monitor-loa 0.6.0-4 in plucky i386 lomiri-sync-monitor-loa 0.6.0-4 in plucky ppc64el lomiri-sync-monitor-loa 0.6.0-4 in plucky riscv64 lomiri-sync-monitor-loa 0.6.0-4 in plucky s390x qml-module-lomiri-syncmonitor 0.6.0-4 in plucky amd64 qml-module-lomiri-syncmonitor 0.6.0-4 in plucky arm64 qml-module-lomiri-syncmonitor 0.6.0-4 in plucky armhf qml-module-lomiri-syncmonitor 0.6.0-4 in plucky ppc64el qml-module-lomiri-syncmonitor 0.6.0-4 in plucky riscv64 qml-module-lomiri-syncmonitor 0.6.0-4 in plucky s390x libsynthesis 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky libsmltk0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky amd64 libsmltk0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky arm64 libsmltk0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky armhf libsmltk0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky ppc64el libsmltk0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky riscv64 libsmltk0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky s390x libsynthesis-dev 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky amd64 libsynthesis-dev 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky arm64 libsynthesis-dev 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky armhf libsynthesis-dev 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky ppc64el libsynthesis-dev 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky riscv64 libsynthesis-dev 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky s390x libsynthesis0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky amd64 libsynthesis0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky arm64 libsynthesis0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky armhf libsynthesis0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky ppc64el libsynthesis0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky riscv64 libsynthesis0t64 3.4.0.47.5+syncevolution-1.5.3-1.2build1 in plucky s390x Comment: Remove packages that transitively depende on pcre3 (LP: #2103916) Remove [y|N]? y 2 packages successfully removed. ** Changed in: libsynthesis (Ubuntu) Status: New => Fix Released ** Changed in: lomiri-sync-monitor (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsynthesis in Ubuntu. https://bugs.launchpad.net/bugs/2103916 Title: Please remove libsynthesis from Ubuntu Status in libsynthesis package in Ubuntu: Fix Released Status in lomiri-sync-monitor package in Ubuntu: Fix Released Status in syncevolution package in Ubuntu: Fix Released Status in libsynthesis package in Debian: Confirmed Bug description: Please remove libsynthesis from Ubuntu since it's blocking the removal of pcre3. libsynthesis has been removed from Debian Testing but not Debian Unstable yet. If it is fixed in Debian, it can auto-sync back to Ubuntu. We also need to remove syncevolution and lomiri-sync-monitor. $ reverse-depends src:libsynthesis Reverse-Depends === * libsyncevolution0 [amd64 arm64 armhf ppc64el riscv64 s390x] * libsyncevolution0 [amd64 arm64 armhf ppc64el riscv64 s390x] * syncevolution-common (for libsynthesis0t64) $ reverse-depends -b src:libsynthesis Reverse-Build-Depends ===
[Touch-packages] [Bug 2103945] Re: Qt 6.8.3 in Ubuntu 25.04
This bug was fixed in the package qt6-serialbus - 6.8.3-0ubuntu1 --- qt6-serialbus (6.8.3-0ubuntu1) plucky; urgency=medium * New upstream release (LP: #2103945). -- Simon Quigley Thu, 27 Mar 2025 22:26:18 -0500 ** Changed in: qt6-websockets (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 gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2103945 Title: Qt 6.8.3 in Ubuntu 25.04 Status in calibre package in Ubuntu: Fix Committed Status in copyq package in Ubuntu: Fix Committed Status in digikam package in Ubuntu: Fix Released Status in dolphin package in Ubuntu: Fix Committed Status in dtk6log package in Ubuntu: Fix Committed Status in elisa-player package in Ubuntu: Fix Committed Status in fcitx-qt5 package in Ubuntu: Fix Committed Status in fcitx5-qt package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gammaray package in Ubuntu: Fix Committed Status in gst-plugins-good1.0 package in Ubuntu: Fix Committed Status in gwenview package in Ubuntu: Fix Committed Status in haruna package in Ubuntu: Fix Committed Status in itinerary package in Ubuntu: Fix Committed Status in kaidan package in Ubuntu: Fix Committed Status in kasts package in Ubuntu: Fix Committed Status in kate package in Ubuntu: Fix Committed Status in kde-cli-tools package in Ubuntu: Fix Released Status in kde-spectacle package in Ubuntu: Fix Released Status in kdeconnect package in Ubuntu: Fix Released Status in kf6-kcmutils package in Ubuntu: Fix Released Status in kf6-kcolorscheme package in Ubuntu: Fix Released Status in kf6-kconfigwidgets package in Ubuntu: Fix Committed Status in kf6-kdbusaddons package in Ubuntu: Fix Released Status in kf6-kglobalaccel package in Ubuntu: Fix Committed Status in kf6-kiconthemes package in Ubuntu: Fix Committed Status in kf6-kio package in Ubuntu: Fix Released Status in kf6-kirigami package in Ubuntu: Fix Committed Status in kf6-kjobwidgets package in Ubuntu: Fix Committed Status in kf6-kwindowsystem package in Ubuntu: Fix Committed Status in kf6-kxmlgui package in Ubuntu: Fix Committed Status in kf6-qqc2-desktop-style package in Ubuntu: Fix Committed Status in kglobalacceld package in Ubuntu: Fix Committed Status in kinfocenter package in Ubuntu: Fix Committed Status in kirigami-addons package in Ubuntu: Fix Released Status in koko package in Ubuntu: Fix Committed Status in konqueror package in Ubuntu: Fix Committed Status in kontactinterface package in Ubuntu: Fix Released Status in kosmindoormap package in Ubuntu: Fix Committed Status in kquickimageeditor package in Ubuntu: Fix Committed Status in krfb package in Ubuntu: Fix Committed Status in kruler package in Ubuntu: Fix Committed Status in kscreen package in Ubuntu: Fix Committed Status in kscreenlocker package in Ubuntu: Fix Committed Status in kwayland package in Ubuntu: Fix Committed Status in kwin package in Ubuntu: Fix Committed Status in layer-shell-qt package in Ubuntu: Fix Committed Status in libfm-qt package in Ubuntu: Fix Committed Status in libkscreen package in Ubuntu: Fix Committed Status in libqtxdg package in Ubuntu: Fix Committed Status in lxqt-qtplugin package in Ubuntu: Fix Committed Status in nheko package in Ubuntu: Fix Committed Status in nvidia-cuda-toolkit package in Ubuntu: Fix Committed Status in okular package in Ubuntu: Fix Released Status in oxygen package in Ubuntu: Fix Committed Status in photoqt package in Ubuntu: Fix Committed Status in plasma-desktop package in Ubuntu: Fix Committed Status in plasma-integration package in Ubuntu: Fix Committed Status in plasma-mobile package in Ubuntu: Fix Released Status in plasma-workspace package in Ubuntu: Fix Committed Status in plasma5support package in Ubuntu: Fix Committed Status in powerdevil package in Ubuntu: Fix Committed Status in pyqt6 package in Ubuntu: Fix Released Status in pyside6 package in Ubuntu: Fix Committed Status in qcoro package in Ubuntu: Fix Committed Status in qgnomeplatform package in Ubuntu: Fix Released Status in qt6-3d package in Ubuntu: Fix Committed Status in qt6-5compat package in Ubuntu: Fix Committed Status in qt6-base package in Ubuntu: Fix Released Status in qt6-charts package in Ubuntu: Fix Committed Status in qt6-connectivity package in Ubuntu: Fix Committed Status in qt6-datavis3d package in Ubuntu: Fix Released Status in qt6-declarative package in Ubuntu: Fix Committed Status in qt6-graphs package in Ubuntu: Fix Committed Status in qt6-grpc package in Ubuntu: Fix Committed Status in qt6-httpserver package in Ubuntu: Fix Committed Status in qt6-imageformats package in Ubuntu: Fix Committed Status in qt6-languageserver package in Ubuntu: Fix Released Status in qt6-location package in Ubuntu:
[Touch-packages] [Bug 2106174] [NEW] aa-notify's userns_special_profiles default missing unprivileged_userns
Public bug reported: Both the unconfined profile and unprivileged_userns are part of the default notify.conf's userns_special_profiles, so the default fallback when no configurations are present should also match this default. ** Affects: apparmor (Ubuntu) Importance: Undecided Assignee: Ryan Lee (rlee287) Status: New ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Ryan Lee (rlee287) -- 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/2106174 Title: aa-notify's userns_special_profiles default missing unprivileged_userns Status in apparmor package in Ubuntu: New Bug description: Both the unconfined profile and unprivileged_userns are part of the default notify.conf's userns_special_profiles, so the default fallback when no configurations are present should also match this default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2106174/+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 2105985] [NEW] Issue with enabling harware acceleration support on Ubuntu 24[RISCV64]
You have been subscribed to a public bug: We are currently working on enabling GNOME (Wayland) to run on top of a Imagination GPU hardware accelerator for RISCV64. Initially, we tested this on Ubuntu 22.04 LTS, but after receiving suggestions from the GNOME forum, we decided to switch to Ubuntu 24.04 LTS. Since upgrading, we’ve noticed significant improvements, and GNOME is running more smoothly than expected. However, the graphics configuration still shows “Software Rendering” instead of utilising hardware acceleration. Despite configuring the Imagination GPU, we are unable to enable hardware acceleration for GNOME, which is impacting 3D rendering performance. Please find the below EGL logs details for Imagination GPU as below: OpenGL ES profile vendor: Imagination Technologies OpenGL ES profile renderer: PowerVR Rogue GE8300 OpenGL ES profile version: OpenGL ES 3.2 OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: After several attempts and experiments running GPU computing tests, such as OpenCL tests on the Imagination GPU, an issue arises when attempting to execute 3D programs[opengles], as they are being executed on the CPU instead of the imagination GPU. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) Uname: Linux 5.10.41 riscv64 ApportVersion: 2.28.1-0ubuntu3.5 Architecture: riscv64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 2 09:12:29 2025 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Medium Status: Triaged ** Tags: apport-bug noble riscv64 wayland-session -- Issue with enabling harware acceleration support on Ubuntu 24[RISCV64] https://bugs.launchpad.net/bugs/2105985 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa 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 2105985] Re: Issue with enabling harware acceleration support on Ubuntu 24[RISCV64]
Thanks. The main issue seems to be our build of Mesa is missing the imagination/pvr driver (even though we do have the source code). Jan 06 06:29:32 Ubuntu-riscv64 gnome-shell[1389]: Added device '/dev/dri/card0' (NB2) using atomic mode setting. Jan 06 06:29:32 Ubuntu-riscv64 gnome-shell[1389]: libEGL warning: MESA-LOADER: egl: failed to open pvr: driver not built! Jan 06 06:29:32 Ubuntu-riscv64 gnome-shell[1389]: Added device '/dev/dri/card1' (pvr) using non-atomic mode setting. Jan 06 06:29:32 Ubuntu-riscv64 gnome-shell[1389]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated Jan 06 06:29:32 Ubuntu-riscv64 gnome-shell[1389]: Created gbm renderer for '/dev/dri/card0' Jan 06 06:29:32 Ubuntu-riscv64 gnome-shell[1389]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated Jan 06 06:29:32 Ubuntu-riscv64 gnome-shell[1389]: Created gbm renderer for '/dev/dri/card1' Jan 06 06:29:32 Ubuntu-riscv64 gnome-shell[1389]: Integrated GPU /dev/dri/card0 selected as primary There is a secondary issue though, in that two different graphics cards are detected. So if you had any displays connected to 'pvr' instead of 'NB2' those displays would take the slow path of copying between GPUs (assuming they are compatible with each other at all). ** Package changed: mutter (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Status: Incomplete => Triaged ** Tags added: riscv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2105985 Title: Issue with enabling harware acceleration support on Ubuntu 24[RISCV64] Status in linux-riscv package in Ubuntu: New Status in mesa package in Ubuntu: Triaged Bug description: We are currently working on enabling GNOME (Wayland) to run on top of a Imagination GPU hardware accelerator for RISCV64. Initially, we tested this on Ubuntu 22.04 LTS, but after receiving suggestions from the GNOME forum, we decided to switch to Ubuntu 24.04 LTS. Since upgrading, we’ve noticed significant improvements, and GNOME is running more smoothly than expected. However, the graphics configuration still shows “Software Rendering” instead of utilising hardware acceleration. Despite configuring the Imagination GPU, we are unable to enable hardware acceleration for GNOME, which is impacting 3D rendering performance. Please find the below EGL logs details for Imagination GPU as below: OpenGL ES profile vendor: Imagination Technologies OpenGL ES profile renderer: PowerVR Rogue GE8300 OpenGL ES profile version: OpenGL ES 3.2 OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: After several attempts and experiments running GPU computing tests, such as OpenCL tests on the Imagination GPU, an issue arises when attempting to execute 3D programs[opengles], as they are being executed on the CPU instead of the imagination GPU. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) Uname: Linux 5.10.41 riscv64 ApportVersion: 2.28.1-0ubuntu3.5 Architecture: riscv64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 2 09:12:29 2025 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2105985/+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 2105985] Re: Issue with enabling harware acceleration support on Ubuntu 24[RISCV64]
Also the information provided so far is showing both your kernel and Mesa are older than what is in Ubuntu 24.04. Although journal.txt suggests a newer version of Mesa is now installed, it does not match eglinfo-all.txt so please run the commands in comment #2 again on Ubuntu 24.04. What is the kernel version you are now using? ** Also affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-riscv (Ubuntu) Status: New => Incomplete ** Changed in: mesa (Ubuntu) Status: Triaged => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2105985 Title: Issue with enabling harware acceleration support on Ubuntu 24[RISCV64] Status in linux package in Ubuntu: Incomplete Status in linux-riscv package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: We are currently working on enabling GNOME (Wayland) to run on top of a Imagination GPU hardware accelerator for RISCV64. Initially, we tested this on Ubuntu 22.04 LTS, but after receiving suggestions from the GNOME forum, we decided to switch to Ubuntu 24.04 LTS. Since upgrading, we’ve noticed significant improvements, and GNOME is running more smoothly than expected. However, the graphics configuration still shows “Software Rendering” instead of utilising hardware acceleration. Despite configuring the Imagination GPU, we are unable to enable hardware acceleration for GNOME, which is impacting 3D rendering performance. Please find the below EGL logs details for Imagination GPU as below: OpenGL ES profile vendor: Imagination Technologies OpenGL ES profile renderer: PowerVR Rogue GE8300 OpenGL ES profile version: OpenGL ES 3.2 OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: After several attempts and experiments running GPU computing tests, such as OpenCL tests on the Imagination GPU, an issue arises when attempting to execute 3D programs[opengles], as they are being executed on the CPU instead of the imagination GPU. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) Uname: Linux 5.10.41 riscv64 ApportVersion: 2.28.1-0ubuntu3.5 Architecture: riscv64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 2 09:12:29 2025 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2105985/+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 2060082] Re: Dublin timezone cause systemd cpu high
I took a bit of time to try to reproduce, without success. Here were my steps: $ lxc launch ubuntu:jammy --vm jammy Launching jammy $ lxc exec jammy bash root@jammy:~# apt update && apt install -y atop ... root@jammy:~# systemctl stop systemd-timesyncd root@jammy:~# timedatectl set-timezone Europe/Dublin root@jammy:~# timedatectl set-time "2024-03-30 23:59:50" In another terminal before messing with the time: $ lxc exec jammy htop I did not see init eating 100% CPU, the machine remained mostly idle. Could you please provide more details on how to reproduce the bug? ** Changed in: systemd (Ubuntu Jammy) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Tags removed: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2060082 Title: Dublin timezone cause systemd cpu high Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Bug description: Systemd version(249) in Jammy Jellyfish is too old, When using the Dublin time zone for daylight saving time switching，the CPU usage will suddenly increase to 100% starting from 2024-03-31 00:00:00 and last for 1 hour, but return to normal at 2024-03-31 02:00:00. plz backport the bugfix to v249 or update 255 version in Jammy Jellyfish to fix it. thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2060082/+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 2099944] Re: Please remove packages from plucky-proposed that need libselinux 3.8
Removing packages from plucky-proposed: refpolicy 2:2.20250213-2 in plucky Comment: Requires libselinux 3.8 which isn't in Plucky (lp: #2099944) Remove [y|N]? y 1 package successfully removed. ** Changed in: refpolicy (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/2099944 Title: Please remove packages from plucky-proposed that need libselinux 3.8 Status in libselinux package in Ubuntu: Invalid Status in libsepol package in Ubuntu: Fix Released Status in mcstrans package in Ubuntu: Fix Released Status in policycoreutils package in Ubuntu: Fix Released Status in refpolicy package in Ubuntu: Fix Released Status in restorecond package in Ubuntu: Fix Released Status in secilc package in Ubuntu: Fix Released Status in selinux-dbus package in Ubuntu: Fix Released Status in selinux-gui package in Ubuntu: Fix Released Status in selinux-python package in Ubuntu: Fix Released Status in semodule-utils package in Ubuntu: Fix Released Bug description: Several packages in plucky-proposed are currently dependency wait on the following: libselinux1-dev (>= 3.8), libsemanage-dev (>= 3.8) Security Team, could you please clarify your plans re: the libselinux version intended for Plucky? If you plan to ship 3.8, could you please file an FFE? If you don't plan to ship 3.8, could you please ask for removal of these packages from the plucky-proposed pocket? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/2099944/+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 2099944] Re: Please remove packages from plucky-proposed that need libselinux 3.8
Removing packages from plucky-proposed: mcstrans 3.8-1 in plucky Comment: Requires libselinux 3.8 which isn't in Plucky (lp: #2099944) Remove [y|N]? y 1 package successfully removed. ** Changed in: mcstrans (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/2099944 Title: Please remove packages from plucky-proposed that need libselinux 3.8 Status in libselinux package in Ubuntu: Invalid Status in libsepol package in Ubuntu: Fix Released Status in mcstrans package in Ubuntu: Fix Released Status in policycoreutils package in Ubuntu: Fix Released Status in refpolicy package in Ubuntu: Fix Released Status in restorecond package in Ubuntu: Fix Released Status in secilc package in Ubuntu: Fix Released Status in selinux-dbus package in Ubuntu: Fix Released Status in selinux-gui package in Ubuntu: Fix Released Status in selinux-python package in Ubuntu: Fix Released Status in semodule-utils package in Ubuntu: Fix Released Bug description: Several packages in plucky-proposed are currently dependency wait on the following: libselinux1-dev (>= 3.8), libsemanage-dev (>= 3.8) Security Team, could you please clarify your plans re: the libselinux version intended for Plucky? If you plan to ship 3.8, could you please file an FFE? If you don't plan to ship 3.8, could you please ask for removal of these packages from the plucky-proposed pocket? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/2099944/+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 2106126] Re: Mesa 25.0.3
Fab, thanks Timo. Please land this as soon as you _realistically_ can, that is, after B-D wait, et al. ** Changed in: mesa (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2106126 Title: Mesa 25.0.3 Status in mesa package in Ubuntu: Triaged Bug description: A new bugfix release is available. Mesa 25.0.3 Release Notes / 2025-04-02 == Mesa 25.0.3 is a bug fix release which fixes bugs found since the 25.0.2 release. New features - None Bug fixes - - [RADV][RDNA3][Phoenix3][APU] NARAKA: BLADEPOINT (1203220) gpu hang reproducible (ice/water regression mesa 24.1 bisected SAMPLE_MASK_TRACKER_WATERMARK=15) random (maybe other apps/games) - GPU hangs running Octopath Traveler II with 780M - GPU crash on Radeon 780M with Tales of Arise - brw: Hit unreachable nir_op_fsign case that brw_nir_lower_fsign missed - The Last of Us - shadows flickering on gfx1201 without nohiz flag - anv: Dark pattern overlayed on objects in Eve Online DX11 mode on BMG - Mesa 25 removes VA-API encoding for R9 390 - Video stuttering / anv: extend implicit fencing support - anv, bmg: Visual issues in AC Origins, Odyssey and Fenyx Rising when dxvk doesn't export PointSize - [ANV][LNL] - A Game About Digging A Hole (3244220) - Title throws an assertion failure on launch. - anv/video: Timestamps are exposed in video encode queue, but it crashes - Getting a crash with manually built llvmpipe (OpenGL) - [RadeonSI] Blender assetshelf icons are borken in mesa >= 25.0.0 - radeonsi regression after 24.3.4 - misc OpenGL CTS failures - glBindVertexBuffer regression due to ID reuse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2106126/+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 2106126] [NEW] Mesa 25.0.3
Public bug reported: A new bugfix release is available. Mesa 25.0.3 Release Notes / 2025-04-02 == Mesa 25.0.3 is a bug fix release which fixes bugs found since the 25.0.2 release. New features - None Bug fixes - - [RADV][RDNA3][Phoenix3][APU] NARAKA: BLADEPOINT (1203220) gpu hang reproducible (ice/water regression mesa 24.1 bisected SAMPLE_MASK_TRACKER_WATERMARK=15) random (maybe other apps/games) - GPU hangs running Octopath Traveler II with 780M - GPU crash on Radeon 780M with Tales of Arise - brw: Hit unreachable nir_op_fsign case that brw_nir_lower_fsign missed - The Last of Us - shadows flickering on gfx1201 without nohiz flag - anv: Dark pattern overlayed on objects in Eve Online DX11 mode on BMG - Mesa 25 removes VA-API encoding for R9 390 - Video stuttering / anv: extend implicit fencing support - anv, bmg: Visual issues in AC Origins, Odyssey and Fenyx Rising when dxvk doesn't export PointSize - [ANV][LNL] - A Game About Digging A Hole (3244220) - Title throws an assertion failure on launch. - anv/video: Timestamps are exposed in video encode queue, but it crashes - Getting a crash with manually built llvmpipe (OpenGL) - [RadeonSI] Blender assetshelf icons are borken in mesa >= 25.0.0 - radeonsi regression after 24.3.4 - misc OpenGL CTS failures - glBindVertexBuffer regression due to ID reuse ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2106126 Title: Mesa 25.0.3 Status in mesa package in Ubuntu: New Bug description: A new bugfix release is available. Mesa 25.0.3 Release Notes / 2025-04-02 == Mesa 25.0.3 is a bug fix release which fixes bugs found since the 25.0.2 release. New features - None Bug fixes - - [RADV][RDNA3][Phoenix3][APU] NARAKA: BLADEPOINT (1203220) gpu hang reproducible (ice/water regression mesa 24.1 bisected SAMPLE_MASK_TRACKER_WATERMARK=15) random (maybe other apps/games) - GPU hangs running Octopath Traveler II with 780M - GPU crash on Radeon 780M with Tales of Arise - brw: Hit unreachable nir_op_fsign case that brw_nir_lower_fsign missed - The Last of Us - shadows flickering on gfx1201 without nohiz flag - anv: Dark pattern overlayed on objects in Eve Online DX11 mode on BMG - Mesa 25 removes VA-API encoding for R9 390 - Video stuttering / anv: extend implicit fencing support - anv, bmg: Visual issues in AC Origins, Odyssey and Fenyx Rising when dxvk doesn't export PointSize - [ANV][LNL] - A Game About Digging A Hole (3244220) - Title throws an assertion failure on launch. - anv/video: Timestamps are exposed in video encode queue, but it crashes - Getting a crash with manually built llvmpipe (OpenGL) - [RadeonSI] Blender assetshelf icons are borken in mesa >= 25.0.0 - radeonsi regression after 24.3.4 - misc OpenGL CTS failures - glBindVertexBuffer regression due to ID reuse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2106126/+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 2103601] Re: 25.0.1 breaks gdm on panfrost
I've pushed 25.0.3 to ppa:canonical-x/x-staging, please give that a go once it's built. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2103601 Title: 25.0.1 breaks gdm on panfrost Status in mesa package in Ubuntu: Confirmed Bug description: Summary === At boot gdm shows an entirely black screen with some weird screen artifacts. The mouse still works. After experimenting a bit I found that logging in blindly works and only wayland seems to be affected. Changing the gdm config to wayland=false makes it render properly. The problem appeared after a recent update to mesa 25.04. Downgrading everything manually resolves the problem. Downgrading only libgl1-mesa-dri did not help. Other Debian users seem to be affected too, see https://github.com/hexdump0815/imagebuilder/issues/314 Hardware Device: Asus Chromebook CM14 SOC: mt8186 GPU: Mali-G52 r1 (Panfrost) Packages libegl-mesa0/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] libgl1-mesa-dri/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] libglx-mesa0/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] mesa-libgallium/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] mesa-va-drivers/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] mesa-vdpau-drivers/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] mesa-vulkan-drivers/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] Happy to collect more info or run tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2103601/+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 2099990] Re: lsusb fails due to apparmor
Hi, Installed plucky yesterday , and had the same problem, i was looking for aa-compalin command to set complain mode to lsusb but command was not installed (strange because other aa- was ok) but at last i had a manual look in the apparmor.d folder and i saw lsub and lsusb.save ! Looking inside the two configs i saw that the lsusb.save file was containing the complain option and in the lsusb no. so deleted lsusb and renamed the lsusb.save to lsusb. Solved the problem. Maybe installing the new version of apparmor created a new lsusb profile and old profile renamed as .save thanks for your suggestions anyway -- 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/200 Title: lsusb fails due to apparmor Status in apparmor package in Ubuntu: Fix Released Bug description: With apparmor 4.1.0~beta5-0ubuntu5 on a RISC-V Microchip Icicle Kit I see that the kernel discovers USB: [ +0.008662] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.007425] usb 1-1: Product: Ultra [ +0.003688] usb 1-1: Manufacturer: SanDisk [ +0.004245] usb 1-1: SerialNumber: 010187b422912d2f128c699458cec5c82b7af2ece2713972b09d1de68f741b2afecb66a842d0ff9957008a558107452c91e7 [ +0.011662] usb-storage 1-1:1.0: USB Mass Storage device detected [ +0.012149] scsi host0: usb-storage 1-1:1.0 [ +0.011826] usbcore: registered new interface driver usb-storage [ +0.035775] usbcore: registered new interface driver uas But lsusb shows not device. Looking as journalctl shows that apparmor is blocking: Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:207): apparmor="DENIED" operation="capable" class="cap" profile="lsusb" pid=1510 comm="lsusb" capability=12 capname="net_admin" Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:208): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:209): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:210): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-0:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.047:211): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/1-1:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session closed for user root /etc/apparmor.d/usr.bin.lsusb does not exist. sudo apparmor_status shows that lsusb is in enforce mode. Only after putting /usb/bin/lsusb into complain mode the command starts to work. Best regards Heinrich --- ProblemType: Bug ApportVersion: 2.31.0+git20250220-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20250225 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) DistroRelease: Ubuntu 25.04 Package: apparmor 4.1.0~beta5-0ubuntu5 PackageArchitecture: riscv64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.14.0-4-generic root=UUID=d7adaa9d-66b4-4ce4-a45f-3651ae4bbb85 ro efi=debug earlycon=sbi sysctl.kernel.watchdog_thresh=60 ProcVersionSignature: Ubuntu 6.14.0-4.4.1~1-generic 6.14.0-rc3 Syslog: 2025-02-25T12:34:08.711312+00:00 ubuntu dbus-daemon[909]: [system] AppArmor D-Bus mediation is enabled Tags: cloud-image plucky Uname: Linux 6.14.0-4-generic riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True mtime.conffile..etc.apparmor.d.lsusb: 2025-02-25T12:57:31.410467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/200/+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 2105395] Re: Failure: The 3.0 solver produced a worse result
** Changed in: apt (Ubuntu) Milestone: None => ubuntu-25.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2105395 Title: Failure: The 3.0 solver produced a worse result Status in apt package in Ubuntu: Triaged Bug description: Ocurred when closing rhytminbox ProblemType: AptSolver DistroRelease: Ubuntu 25.04 Package: apt 2.9.34 ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0 Uname: Linux 6.14.0-13-generic x86_64 ApportVersion: 2.32.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 29 14:47:42 2025 InstallationDate: Installed on 2025-03-29 (0 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Beta amd64 (20250326.6) SourcePackage: apt Title: Failure: The 3.0 solver produced a worse result UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2105395/+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 2080620] Re: Compositing/Semitransparency of Plasma/Kwin broken using llvmpipe on x11 since mesa 24.2.2
On 03/04/2025 15:02, Timo Aaltonen wrote: > this should be fixed now in plucky at least? Yes, and now marked as such. In oracular the issue is still there, but since the main concern was the impact on the live install ISO, and that ship has long sailed, I have marked that as low priority. Feel free to change to "won't fix" if that seems more appropriate. ** Also affects: mesa (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Plucky) Importance: Critical Status: Incomplete ** Changed in: mesa (Ubuntu Plucky) Status: Incomplete => Fix Released ** Changed in: mesa (Ubuntu Oracular) Status: New => Confirmed ** Changed in: mesa (Ubuntu Oracular) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2080620 Title: Compositing/Semitransparency of Plasma/Kwin broken using llvmpipe on x11 since mesa 24.2.2 Status in Mesa: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Oracular: Confirmed Status in mesa source package in Plucky: Fix Released Bug description: Version: 24.2.2-1ubuntu1 Release: oracular 24.10 After upgrade to mesa 24.2.2-1ubuntu1 in oracular, compositing/semitransparency of Plasma/Kwin broken using llvmpipe on x11. Very noticeable on Plasma widgets/panels. This is particularly prominent for testers trying our live ISO session (is still X11 for compatibility) in VMs such as Virtualbox/qmemu/etc with no acceleration. With the 24.10 beta coming in less than a weeks time, this is bad timing. EDIT: Also as a result of this issue, the try/install screen on the live ISO session is wrongly tinted orange. This occurs under the same conditions as the transparency issue. An issue has been opened upstream by a user/developer on Mandriva with the same issue. https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840#top Screen shots can be seen there of the impact. I have commented and added screenshots from Kubuntu 24.10. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2080620/+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 2099990] Re: lsusb fails due to apparmor
Installed apparmor-utils package and aa-complain is ok now. But i never did editing in apparmor.d files before yesterday, and on 24.04 lsusb was not complaining. After upgrading to 25.04 it started the problem. So really strange to have a .save file if no one has edited anything neither before or later. For me it's solved and closed anyway. But the cause of extra .save file is not derivated from a local edit, must be somewhere else. Let's see if someone else has this prob, otherwise just close. -- 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/200 Title: lsusb fails due to apparmor Status in apparmor package in Ubuntu: Fix Released Bug description: With apparmor 4.1.0~beta5-0ubuntu5 on a RISC-V Microchip Icicle Kit I see that the kernel discovers USB: [ +0.008662] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.007425] usb 1-1: Product: Ultra [ +0.003688] usb 1-1: Manufacturer: SanDisk [ +0.004245] usb 1-1: SerialNumber: 010187b422912d2f128c699458cec5c82b7af2ece2713972b09d1de68f741b2afecb66a842d0ff9957008a558107452c91e7 [ +0.011662] usb-storage 1-1:1.0: USB Mass Storage device detected [ +0.012149] scsi host0: usb-storage 1-1:1.0 [ +0.011826] usbcore: registered new interface driver usb-storage [ +0.035775] usbcore: registered new interface driver uas But lsusb shows not device. Looking as journalctl shows that apparmor is blocking: Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:207): apparmor="DENIED" operation="capable" class="cap" profile="lsusb" pid=1510 comm="lsusb" capability=12 capname="net_admin" Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:208): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:209): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:210): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-0:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.047:211): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/1-1:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session closed for user root /etc/apparmor.d/usr.bin.lsusb does not exist. sudo apparmor_status shows that lsusb is in enforce mode. Only after putting /usb/bin/lsusb into complain mode the command starts to work. Best regards Heinrich --- ProblemType: Bug ApportVersion: 2.31.0+git20250220-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20250225 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) DistroRelease: Ubuntu 25.04 Package: apparmor 4.1.0~beta5-0ubuntu5 PackageArchitecture: riscv64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.14.0-4-generic root=UUID=d7adaa9d-66b4-4ce4-a45f-3651ae4bbb85 ro efi=debug earlycon=sbi sysctl.kernel.watchdog_thresh=60 ProcVersionSignature: Ubuntu 6.14.0-4.4.1~1-generic 6.14.0-rc3 Syslog: 2025-02-25T12:34:08.711312+00:00 ubuntu dbus-daemon[909]: [system] AppArmor D-Bus mediation is enabled Tags: cloud-image plucky Uname: Linux 6.14.0-4-generic riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True mtime.conffile..etc.apparmor.d.lsusb: 2025-02-25T12:57:31.410467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/200/+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 2106133] [NEW] Gnome Papers "Sign Digitally" Feature Fails Due to AppArmor Restrictions
Public bug reported:
Description:
I am unable to digitally sign PDF documents in Gnome Papers using my hardware
device "Giesecke & Devrient GmbH StarSign CUT S" with a certificate. The
signing process fails due to AppArmor blocking access to necessary directories.
Affected Directories:
AppArmor restricts Gnome Papers from accessing the following paths:
~/.pki/nssdb
/sys/devices/
Steps to Reproduce:
1. Open Gnome Papers.
2. Attempt to sign a PDF using the "Sign Digitally" feature with a hardware
security device.
3. The signing process fails due to restricted access.
Workaround:
Manually editing the AppArmor profile resolves the issue:
Open the file "/etc/apparmor.d/usr.bin.papers" and add the following lines:
owner @{HOME}/.pki/** lrk,
/sys/devices/** r,
/run/pcscd/pcscd.comm rw,
Reload AppArmor:
sudo systemctl restart apparmor
Expected Behavior:
Gnome Papers should be able to access the necessary directories and sign PDFs
using the hardware device without requiring manual AppArmor modifications.
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: apparmor 4.1.0~beta5-0ubuntu12
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 3 10:50:21 2025
InstallationDate: Installed on 2025-04-02 (1 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Beta amd64 (20250326.6)
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.14.0-13-generic
root=UUID=e5c8dae6-79c1-4a2a-aa55-7a53dcc8a41b ro quiet splash pcie_aspm=off
nvme_core.default_ps_max_latency_us=0
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
vt.handoff=7
SourcePackage: apparmor
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: apparmor
Importance: Undecided
Status: New
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Affects: papers (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug plucky wayland-session
** Also affects: papers (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2106133
Title:
Gnome Papers "Sign Digitally" Feature Fails Due to AppArmor
Restrictions
Status in AppArmor:
New
Status in apparmor package in Ubuntu:
New
Status in papers package in Ubuntu:
New
Bug description:
Description:
I am unable to digitally sign PDF documents in Gnome Papers using my hardware
device "Giesecke & Devrient GmbH StarSign CUT S" with a certificate. The
signing process fails due to AppArmor blocking access to necessary directories.
Affected Directories:
AppArmor restricts Gnome Papers from accessing the following paths:
~/.pki/nssdb
/sys/devices/
Steps to Reproduce:
1. Open Gnome Papers.
2. Attempt to sign a PDF using the "Sign Digitally" feature with a hardware
security device.
3. The signing process fails due to restricted access.
Workaround:
Manually editing the AppArmor profile resolves the issue:
Open the file "/etc/apparmor.d/usr.bin.papers" and add the following lines:
owner @{HOME}/.pki/** lrk,
/sys/devices/** r,
/run/pcscd/pcscd.comm rw,
Reload AppArmor:
sudo systemctl restart apparmor
Expected Behavior:
Gnome Papers should be able to access the necessary directories and sign PDFs
using the hardware device without requiring manual AppArmor modifications.
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: apparmor 4.1.0~beta5-0ubuntu12
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 3 10:50:21 2025
InstallationDate: Installed on 2025-04-02 (1 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Beta amd64 (20250326.6)
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.14.0-13-generic
root=UUID=e5c8dae6-79c1-4a2a-aa55-7a53dcc8a41b ro quiet splash pcie_aspm=off
nvme_core.default_ps_max_latency_us=0
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
vt.handoff=7
SourcePackage: apparmor
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2106133/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscrib
[Touch-packages] [Bug 2080620] Re: Compositing/Semitransparency of Plasma/Kwin broken using llvmpipe on x11 since mesa 24.2.2
this should be fixed now in plucky at least? ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2080620 Title: Compositing/Semitransparency of Plasma/Kwin broken using llvmpipe on x11 since mesa 24.2.2 Status in Mesa: New Status in mesa package in Ubuntu: Incomplete Bug description: Version: 24.2.2-1ubuntu1 Release: oracular 24.10 After upgrade to mesa 24.2.2-1ubuntu1 in oracular, compositing/semitransparency of Plasma/Kwin broken using llvmpipe on x11. Very noticeable on Plasma widgets/panels. This is particularly prominent for testers trying our live ISO session (is still X11 for compatibility) in VMs such as Virtualbox/qmemu/etc with no acceleration. With the 24.10 beta coming in less than a weeks time, this is bad timing. EDIT: Also as a result of this issue, the try/install screen on the live ISO session is wrongly tinted orange. This occurs under the same conditions as the transparency issue. An issue has been opened upstream by a user/developer on Mandriva with the same issue. https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840#top Screen shots can be seen there of the impact. I have commented and added screenshots from Kubuntu 24.10. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2080620/+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 2064025] Re: Ubuntu 24.04: Accented characters persisting in gnome-text-editor (X11 session)
** Summary changed: - Ubuntu 24.04: Accented characters persisting in gnome-text-editor (in X11 session) + Ubuntu 24.04: Accented characters persisting in gnome-text-editor (X11 session) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2064025 Title: Ubuntu 24.04: Accented characters persisting in gnome-text-editor (X11 session) Status in ibus: Fix Released Status in ibus package in Ubuntu: Triaged Bug description: In the GNOME text editor, after typing an accent (e.g., "~"), the symbol remains visible at the cursor location instead of disappearing after subsequent character input. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 16:47:16 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2064025/+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 2103601] Re: 25.0.1 breaks gdm on panfrost
** Also affects: mesa (Ubuntu Plucky) Importance: Undecided Status: Confirmed ** Changed in: mesa (Ubuntu Plucky) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2103601 Title: 25.0.1 breaks gdm on panfrost Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Plucky: Confirmed Bug description: Summary === At boot gdm shows an entirely black screen with some weird screen artifacts. The mouse still works. After experimenting a bit I found that logging in blindly works and only wayland seems to be affected. Changing the gdm config to wayland=false makes it render properly. The problem appeared after a recent update to mesa 25.04. Downgrading everything manually resolves the problem. Downgrading only libgl1-mesa-dri did not help. Other Debian users seem to be affected too, see https://github.com/hexdump0815/imagebuilder/issues/314 Hardware Device: Asus Chromebook CM14 SOC: mt8186 GPU: Mali-G52 r1 (Panfrost) Packages libegl-mesa0/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] libgl1-mesa-dri/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] libglx-mesa0/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] mesa-libgallium/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] mesa-va-drivers/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] mesa-vdpau-drivers/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] mesa-vulkan-drivers/plucky,now 25.0.1-2ubuntu1 arm64 [installed,automatic] Happy to collect more info or run tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2103601/+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
