January 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1235085] New: distribution-logos-openSUSE-icons needs to be added to install images
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235085 Bug ID: 1235085 Summary: distribution-logos-openSUSE-icons needs to be added to install images Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: epp.linux(a)gmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- The libxfce4ui-2-0 package provides information to the About Xfce window in the Xfce desktop. Upon upgrading Tumbleweed to Xfce 4.20, About Xfce now displays the distribution logo in the window. Initially, on two systems in which I used the 20241215-0 install image, this logo was not displayed, but displayed a generic display monitor shown in previous versions. I submitted a bug report upstream to Xfce at https://gitlab.xfce.org/xfce/libxfce4ui/-/issues/122 It was determined that the 'distribution-logos-openSUSE-icons' package requires installation for the logo to be displayed. Once installed, the logo now appears in About Xfce. On two of my other systems with Tumbleweed installed, this package was already installed. The install image used then, was 20230822-0. Sometime between the release of the 20230822-0 and 20241215-0 installation images, this package apparently was removed from the image and it should be restored to the image, due to the Xfce requirement. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1234675] Update nvidia driver to latest 550.142 release
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234675 https://bugzilla.suse.com/show_bug.cgi?id=1234675#c1 --- Comment #1 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1234675) was mentioned in https://build.opensuse.org/request/show/1234916 Factory / nvidia-open-driver-G06-signed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234914] New: kernel-firmware-nvidia-gspx-G06-cuda lagging behind breaks nvidia-open for Tumbleweed users
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234914 Bug ID: 1234914 Summary: kernel-firmware-nvidia-gspx-G06-cuda lagging behind breaks nvidia-open for Tumbleweed users Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: bizyaev(a)zoho.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- • kernel-firmware-nvidia-gspx-G06-cuda is at the only available version 560.35.03. • nvidia-open-driver-G06-signed-cuda-kmp-default has versions 560.35.03_k6.11.8_1-2.1 and 565.57.01_k6.12.6_1-3.1, but only the former can be installed because of kernel-firmware-nvidia-gspx-G06-cuda's version. • Notice how the kernel module's versions are kernel-specific, but nothing prevents zypper from upgrading the kernel to 6.12.6 anyway, leaving users without a working GPU driver. The workaround is to keep booting with the old kernel while it's still available in the system. It's unclear what blocks timely updates for kernel-firmware-nvidia-gspx-G06-cuda, since kernel-firmware-nvidia-gspx-G06 (the non-CUDA counterpart) is at the correct version 565.57.01, and both are shipped by openSUSE. This is not a one-time issue, it happens regularly, effectively limiting system updates for NVIDIA CUDA users to the short time windows when kernel-firmware-nvidia-gspx-G06-cuda's and nvidia-open-driver-G06-signed-cuda-kmp-default's versions align. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1234780] X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - Cannot boot with kernel 6.12
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234780 https://bugzilla.suse.com/show_bug.cgi?id=1234780#c7 --- Comment #7 from pallas wept <pallaswept(a)proton.me> --- Thanks Stefan. Will I need to change any packages or just a normal dup? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234914] kernel-firmware-nvidia-gspx-G06-cuda lagging behind breaks nvidia-open for Tumbleweed users
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234914 https://bugzilla.suse.com/show_bug.cgi?id=1234914#c6 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pallaswept(a)proton.me --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- *** Bug 1234780 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234780] X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - Cannot boot with kernel 6.12
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234780 https://bugzilla.suse.com/show_bug.cgi?id=1234780#c6 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(pallaswept@proton | |.me) | Status|IN_PROGRESS |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- Thanks. This is apparently a dup of boo#1234914 *** This bug has been marked as a duplicate of bug 1234914 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234914] kernel-firmware-nvidia-gspx-G06-cuda lagging behind breaks nvidia-open for Tumbleweed users
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234914 https://bugzilla.suse.com/show_bug.cgi?id=1234914#c5 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #5 from Stefan Dirsch <sndirsch(a)suse.com> --- Closing as fixed. Update should be available in TW next week. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234914] kernel-firmware-nvidia-gspx-G06-cuda lagging behind breaks nvidia-open for Tumbleweed users
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234914 https://bugzilla.suse.com/show_bug.cgi?id=1234914#c4 --- Comment #4 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Stefan Dirsch from comment #3) > (In reply to Ilya Bizyaev from comment #2) > > I tried to switch to kernel-firmware-nvidia-gspx-G06, but, unfortunately, > > got hit with > > https://forums.developer.nvidia.com/t/patch-for-565-57-01-linux-kernel-6-12/ > > 313260, so I cannot confirm that it works yet. Looks like openSUSE will need > > a patch... > > 550.142 already includes > > [...] > #if defined(NV_FILE_OPERATIONS_FOP_UNSIGNED_OFFSET_PRESENT) > .fop_flags = FOP_UNSIGNED_OFFSET, > #endif > [...] > > so I don't think this patch is still needed for 550.142. But it still > applies to 565.57.01, so I will add it for this version. done --> https://build.opensuse.org/request/show/1234916 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234914] kernel-firmware-nvidia-gspx-G06-cuda lagging behind breaks nvidia-open for Tumbleweed users
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234914 https://bugzilla.suse.com/show_bug.cgi?id=1234914#c3 --- Comment #3 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Ilya Bizyaev from comment #2) > I tried to switch to kernel-firmware-nvidia-gspx-G06, but, unfortunately, > got hit with > https://forums.developer.nvidia.com/t/patch-for-565-57-01-linux-kernel-6-12/ > 313260, so I cannot confirm that it works yet. Looks like openSUSE will need > a patch... 550.142 already includes [...] #if defined(NV_FILE_OPERATIONS_FOP_UNSIGNED_OFFSET_PRESENT) .fop_flags = FOP_UNSIGNED_OFFSET, #endif [...] so I don't think this patch is still needed for 550.142. But it still applies to 565.57.01, so I will add it for this version. > But I think I found what prevented me from upgrading to 565 with > kernel-firmware-nvidia-gspx-G06: the "cuda-drivers" package requires > "nvidia-driver-G06-kmp or nvidia-open-driver-G06-kmp", neither of which is > provided by nvidia-open-driver-G06-signed-cuda-kmp-default. I had to > uninstall "cuda-drivers" and CUDA runtime components for dependencies to > resolve. CUDA Deps changed a lot since 555. :-( -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1235084] New: Rusticl OpenCL driver not works when nvidia-compute package installed
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235084 Bug ID: 1235084 Summary: Rusticl OpenCL driver not works when nvidia-compute package installed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: jic4656(a)naver.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- nvidia-compute-G06 package installs 'nvidia.icd' under below directory "/etc/OpenCL/vendors/" However, mesa opencl implementation packages like rusticl or clover installs .icd file under "/usr/share/OpenCL/vendors". When I run 'clinfo', it only detects nvidia platform. But, if I move .icd file of rusticl into "/etc/OpenCL/vendors", it detects both platform well. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1235083] [Build 20250103] openQA test fails in gdal
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235083 https://bugzilla.suse.com/show_bug.cgi?id=1235083#c1 --- Comment #1 from Bruno Friedmann <bruno(a)ioda-net.ch> --- Latest build in App:Geo seems to already have this new poppler App Geo is able to find the new lib and the build is correct https://build.opensuse.org/package/live_build_log/Application:Geo/gdal/open… [356/393] cumulate libpoppler139-24.07.0-4.1 While gdal failed to build on Factory for another reason https://build.opensuse.org/package/live_build_log/openSUSE:Factory/gdal/sta… So nothing to do with poppler at first look. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234780] X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - Cannot boot with kernel 6.12
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234780 https://bugzilla.suse.com/show_bug.cgi?id=1234780#c5 --- Comment #5 from pallas wept <pallaswept(a)proton.me> --- Thanks Stefan that update should do the trick. > rpm -qa | grep nvidia nvidia-compute-G06-32bit-565.57.01-1.x86_64 libnvidia-container-tools-1.17.3-1.x86_64 nvidia-drivers-G06-565.57.01-1.x86_64 kernel-firmware-nvidia-gspx-G06-565.57.01-1.x86_64 kernel-firmware-nvidia-gspx-G06-550.127.05-1.1.x86_64 nvidia-video-G06-32bit-565.57.01-1.x86_64 nvidia-gl-G06-32bit-565.57.01-1.x86_64 libnvidia-container1-1.17.3-1.x86_64 nvidia-video-G06-565.57.01-1.x86_64 kernel-firmware-nvidia-gspx-G06-550.135-1.1.x86_64 nvidia-container-toolkit-1.17.3-1.x86_64 nvidia-libXNVCtrl-565.77-1.1.x86_64 nvidia-open-565.57.01-1.x86_64 nvidia-gl-G06-565.57.01-1.x86_64 kernel-firmware-nvidia-gspx-G06-550.120-2.1.x86_64 kernel-firmware-nvidia-gspx-G06-560.35.03-0.x86_64 kernel-firmware-nvidia-20241211-1.1.noarch nvidia-compute-G06-565.57.01-1.x86_64 nvidia-utils-G06-565.57.01-1.x86_64 nvidia-compute-utils-G06-565.57.01-1.x86_64 nvidia-container-toolkit-base-1.17.3-1.x86_64 nvidia-open-driver-G06-kmp-default-565.57.01-1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1235083] New: [Build 20250103] openQA test fails in gdal
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235083 Bug ID: 1235083 Summary: [Build 20250103] openQA test fails in gdal Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4748713/modules/gdal /steps/18 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Poppler was updated with a soname bump and as usual, gdal requires now an update to build against this new version of poppler openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_textmode@64bit fails in [gdal](https://openqa.opensuse.org/tests/4748713/modules/gdal/steps/18) ## Test suite description Maintainer: slindomansilla(a)suse.de. Mainly post-installation console extra tests. ## Reproducible Fails since (at least) Build [20240702](https://openqa.opensuse.org/tests/4315747) ## Expected result Last good: [20240611](https://openqa.opensuse.org/tests/4267371) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1234780] X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - Cannot boot with kernel 6.12
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234780 https://bugzilla.suse.com/show_bug.cgi?id=1234780#c4 --- Comment #4 from Stefan Dirsch <sndirsch(a)suse.com> --- 565.77 packages are not available yet in CUDA repo. https://developer.download.nvidia.com/compute/cuda/repos/opensuse15/x86_64/ Update to 550.142 driver is planned for next week. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234780] X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - Cannot boot with kernel 6.12
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234780 https://bugzilla.suse.com/show_bug.cgi?id=1234780#c3 --- Comment #3 from Stefan Dirsch <sndirsch(a)suse.com> --- Yes, typo. Should have been --> rpm -qa | grep nvidia -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234789] buggy authentication message
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234789 https://bugzilla.suse.com/show_bug.cgi?id=1234789#c4 --- Comment #4 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234773] New: openSUSE-2024-411 is not installable - built against wrong libgarcon-branding-openSUSE version?
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234773 Bug ID: 1234773 Summary: openSUSE-2024-411 is not installable - built against wrong libgarcon-branding-openSUSE version? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- bor@10:~> sudo zypper in -t patch openSUSE-2024-411 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: 1: the to be installed libgarcon-data-4.18.2-bp156.4.3.1.noarch requires 'libgarcon-branding = 4.18.2', but this requirement cannot be provided not installable providers: libgarcon-branding-upstream-4.18.2-bp156.4.3.1.noarch[repo-backports-update] libgarcon-branding-openSUSE-4.18.0+git4.79f6d44-lp156.2.2.16.noarch[repo-update] Solution 1: Following actions will be done: deinstallation of libgarcon-data-4.18.1-bp156.3.5.noarch deinstallation of libgarcon-1-0-4.18.1-bp156.3.5.x86_64 deinstallation of libgarcon-lang-4.18.1-bp156.3.5.noarch deinstallation of xfce4-power-manager-plugin-4.18.2-bp156.1.7.x86_64 deinstallation of xfce4-panel-lang-4.18.5-bp156.1.4.noarch deinstallation of xfdesktop-4.18.1-bp156.2.8.x86_64 deinstallation of xfce4-xkb-plugin-0.8.3-bp156.2.5.x86_64 deinstallation of xfce4-whiskermenu-plugin-2.8.3-bp156.1.1.x86_64 deinstallation of xfce4-screensaver-4.18.2-bp156.1.10.x86_64 deinstallation of xfce4-appfinder-4.18.0-bp156.2.8.x86_64 deinstallation of patterns-xfce-xfce_basis-20230212-lp156.3.2.x86_64 deinstallation of xfdesktop-lang-4.18.1-bp156.2.8.noarch deinstallation of xfce4-xkb-plugin-lang-0.8.3-bp156.2.5.noarch deinstallation of xfce4-whiskermenu-plugin-lang-2.8.3-bp156.1.1.noarch deinstallation of xfce4-appfinder-lang-4.18.0-bp156.2.8.noarch deinstallation of xfce4-panel-profiles-1.0.14-bp156.1.1.noarch deinstallation of xfce4-pulseaudio-plugin-0.4.8-bp156.1.3.x86_64 deinstallation of patterns-xfce-xfce-20230212-lp156.3.2.x86_64 deinstallation of patterns-xfce-xfce_office-20230212-lp156.3.2.x86_64 deinstallation of xfce4-pulseaudio-plugin-lang-0.4.8-bp156.1.3.noarch Solution 2: downgrade of libgarcon-branding-openSUSE-4.18.0+git4.79f6d44-lp156.2.8.1.noarch to libgarcon-branding-openSUSE-4.18.0+git4.79f6d44-lp156.2.2.16.noarch Solution 3: do not install patch:openSUSE-2024-411-1.noarch Solution 4: break libgarcon-data-4.18.2-bp156.4.3.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c): bor@10:~> sudo zypper in libgarcon-data Loading repository data... Reading installed packages... Resolving package dependencies... Problem: 1: the to be installed libgarcon-data-4.18.2-bp156.4.3.1.noarch requires 'libgarcon-branding = 4.18.2', but this requirement cannot be provided not installable providers: libgarcon-branding-upstream-4.18.2-bp156.4.3.1.noarch[repo-backports-update] libgarcon-branding-openSUSE-4.18.0+git4.79f6d44-lp156.2.2.16.noarch[repo-update] Solution 1: downgrade of libgarcon-branding-openSUSE-4.18.0+git4.79f6d44-lp156.2.8.1.noarch to libgarcon-branding-openSUSE-4.18.0+git4.79f6d44-lp156.2.2.16.noarch Solution 2: do not install libgarcon-data-4.18.2-bp156.4.3.1.noarch Solution 3: break libgarcon-data-4.18.2-bp156.4.3.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): bor@10:~> -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1234780] X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - Cannot boot with kernel 6.12
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234780 https://bugzilla.suse.com/show_bug.cgi?id=1234780#c2 --- Comment #2 from pallas wept <pallaswept(a)proton.me> --- (In reply to Stefan Dirsch from comment #1) > Which driver version are you using? > > --> rpm -qa | grep be > > Could be that you already need 565.57.01 or 550.135. Hi Stefan, Happy New Year. I have 565.57.01-1. From what I can tell, this bug was only fixed in 550.142 and 565.77, but neither are on the cuda repository as yet. I don't mind using packages from a different repo, if I can keep the cuda support. > --> rpm -qa | grep be This gets me output for a lot of different packages, perhaps there is a typo? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234870] New: Virtualbox-guests-tools: /usr/lib/systemd/system/vboxclient.service: Unknown key 'ExecCondition' in section [Unit]
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234870 Bug ID: 1234870 Summary: Virtualbox-guests-tools: /usr/lib/systemd/system/vboxclient.service: Unknown key 'ExecCondition' in section [Unit] Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: mark.wenzel(a)t-online.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In a virtualbox virtual machine running openSUSE 15.6 as guest operating system in text mode: - Install virtualbox-guest-tools from http://download.opensuse.org/update/leap/15.6/oss: Name : virtualbox-guest-tools Version : 7.1.4-lp156.2.4.1 Arch : x86_64 Anbieter : openSUSE Installierte Größe : 2,6 MiB Installiert : Ja Status : aktuell In journal the following error is logged any time systemd reloads (i.e when installing updates of any packages): systemd[1]: /usr/lib/systemd/system/vboxclient.service:4: Unknown key 'ExecCondition' in section [Unit], ignoring. - Show status: systemctl status vboxclient.service: ... systemd[1]: /usr/lib/systemd/system/vboxclient.service:4: Unknown key 'ExecCondition' in section [Unit], ignoring. ... ExecCondition should appear in [Service] section, not in [Unit] section. Link to relevant documentation: https://www.freedesktop.org/software/systemd/man/latest/systemd.service.htm… When using 'ExecCondition' in section [Service] the exit code should not be -1 because this means a failure. Instead a return code of 1 would indicate that this service will be not started because of unmet condition. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1235080] New: Tor-browser AppArmor-profiles failing: paths incorrect (AppArmor not activating)
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235080 Bug ID: 1235080 Summary: Tor-browser AppArmor-profiles failing: paths incorrect (AppArmor not activating) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: opensuse.k1akb(a)slmail.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- For Tor-Browser installations using the "Tor Browser Launcher" tool, AppArmor profiles are ineffective because their paths are incorrect. This concerns at least 3 files: - /etc/apparmor.d/torbrowser.Browser.firefox - /etc/apparmor.d/torbrowser.Tor.tor - /etc/apparmor.d/tunables/torbrowser In all cases, almost at the top: `@{torbrowser_firefox_executable} = /home/*/...` Issues, AFAICT: 1. Better to use `@{HOME}/.local/...` (instead of `/home/*/.local/...`) 2. Instead of `.../tor-browser_*/...`, it should read `.../tor-browser/...` in paths. (All very near top of the profile-files.) It seems that by default the profiles are configured as enforced, but `aa-status` does not show them to activate. After I make these changes and use `apparmor_parser -r <profile>` for all three profiles, then run Tor-Browser from the (KDE) launcher, everything works as expected and AppArmor activates according to `aa-status`. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234789] New: buggy authentication message
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234789 Bug ID: 1234789 Summary: buggy authentication message Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0 Build Identifier: When starting an X application at the command line, I am getting an error message about "MIT-MAGIC-COOKIE-1". Here's an example: % xterm Warning: Tried to connect to session manager, Authentication Rejected, reason : MIT-MAGIC-COOKIE-1 authentication rejected However, the application does start. I've tried this on another computer, where all is fine. I'm not sure what is special about this system, other than it is using an NVME disk. I am using KDE Plasma 5, and I use SDDM as display manager Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222748] RIP: 0010:rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv] and RIP: 0033:0x7fac1690f3df - virtualbox host
by bugzilla_noreply＠suse.com 04 Jan '25

04 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222748 https://bugzilla.suse.com/show_bug.cgi?id=1222748#c3 Jan Engelhardt <jengelh(a)inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Jan Engelhardt <jengelh(a)inai.de> --- openSUSE:Factory/virtualbox commit ---------------------------------- r277 | dimstar_suse | 2024-05-08 09:38:34 | 11c302f702e95fec4bba27788bdb6aac | 7.0.18 | rq1172513 ---------------------------------- should have fixed that, judging by upstream ticket https://www.virtualbox.org/ticket/21952 . -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234780] X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - Cannot boot with kernel 6.12
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234780 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234780] X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - Cannot boot with kernel 6.12
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234780 https://bugzilla.suse.com/show_bug.cgi?id=1234780#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pallaswept(a)proton.me Flags| |needinfo?(pallaswept@proton | |.me) Status|NEW |IN_PROGRESS --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- Which driver version are you using? --> rpm -qa | grep be Could be that you already need 565.57.01 or 550.135. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1235077] New: Fedora:41 and Rawhide: have choice for libOpenCL.so.1()(64bit)
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235077 Bug ID: 1235077 Summary: Fedora:41 and Rawhide: have choice for libOpenCL.so.1()(64bit) Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- When trying to build anything depending on ffmpeg for new Fedora, i'm getting an error: unresolvable: have choice for libOpenCL.so.1()(64bit) needed by libavutil-free: OpenCL-ICD-Loader ocl-icd, have choice for libOpenCL.so.1(OPENCL_1.0)(64bit) needed by libavutil-free: OpenCL-ICD-Loader ocl-icd, have choice for libOpenCL.so.1(OPENCL_1.2)(64bit) needed by libavutil-free: OpenCL-ICD-Loader ocl-icd Please add an appropriate Prefer: to the prjconf. (OpenCL-ICD-Loader seems to be the new one) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234858] Intel hybrid driver "hybrid_drv_video.so" for VA API (VAAPI) does not work
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234858 https://bugzilla.suse.com/show_bug.cgi?id=1234858#c2 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #2 from Stefan Dirsch <sndirsch(a)suse.com> --- https://build.opensuse.org/request/show/1234809 Should be available soon in TW. I don't plan to fix this still for SP6/Leap 15.6. Also I don't think I have Intel hardware old enough to test this driver. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234858] Intel hybrid driver "hybrid_drv_video.so" for VA API (VAAPI) does not work
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234858 https://bugzilla.suse.com/show_bug.cgi?id=1234858#c1 --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- done ------------------------------------------------------------------- Fri Jan 3 22:36:02 UTC 2025 - Stefan Dirsch <sndirsch(a)suse.com> - fixed driver for current libva by switchting to gentoo patches (boo#1234858) * intel-hybrid-codec-driver-2.0.0-gcc10-fix.patch * intel-hybrid-codec-driver-2.0.0-invalid-read-fix.patch * intel-hybrid-codec-driver-2.0.0-nullptr-fix.patch * intel-hybrid-codec-driver-2.0.0-vadriverinit-fix.patch * intel-hybrid-codec-driver-2.0.0-x11-fix.patch - supersedes the following patches * U_Update-the-dependency-to-libva-2.0.patch * n_libva-2.0-ABI-header-fix.patch * u_gcc10.patch - raised driver version number to 2.0.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234858] Intel hybrid driver "hybrid_drv_video.so" for VA API (VAAPI) does not work
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234858 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234789] buggy authentication message
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234789 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx(a)yahoo.com Flags| |needinfo?(nwr10cst-oslnx@ya | |hoo.com) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234789] buggy authentication message
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234789 https://bugzilla.suse.com/show_bug.cgi?id=1234789#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- Hard to debug. I suggest to rename your ~/.Xauthority file and restart your Xsession. Then hopefully the issue is gone. Try this first. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234914] kernel-firmware-nvidia-gspx-G06-cuda lagging behind breaks nvidia-open for Tumbleweed users
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234914 https://bugzilla.suse.com/show_bug.cgi?id=1234914#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(bizyaev(a)zoho.com) Status|NEW |IN_PROGRESS Priority|P5 - None |P3 - Medium Assignee|gfx-bugs(a)suse.de |sndirsch(a)suse.com CC| |bizyaev(a)zoho.com, | |eich(a)suse.com --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- kernel-firmware-nvidia-gspx-G06-cuda=565.57.01 is only needed on SLES for historic reasons. Actually it became a fake/meta package. You don't need it on TW. $ rpm --requires -qp nvidia-open-driver-G06-signed-cuda-kmp-default-565.57.01_k6.12.6_1-173.2.x86_64.rpm | grep -v ksym | grep gsp (kernel-firmware-nvidia-gspx-G06 = 565.57.01 if nvidia-compute-utils-G06 = 565.57.01) So once you install nvidia-compute-utils-G06 = 565.57.01 the appropriate kernel-firmware package gets installed. Both are in NVIDIA's CUDA repo. https://developer.download.nvidia.com/compute/cuda/repos/opensuse15/x86_64/ Not sure why this doesn't work on your TW installation. Maybe it helps to uninstall old nvidia-open-driver-G06-signed-cuda-kmp-default and kernel-firmware-nvidia-gspx-G06-cuda packages. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230552] VUL-0: CVE-2024-45770: pcp: `pmpost` symlink attack allows escalating `pcp` to `root` user
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1230552 https://bugzilla.suse.com/show_bug.cgi?id=1230552#c18 --- Comment #18 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2025:0011-1: An update that solves three vulnerabilities and has two security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2025/suse-su-20250011-1 Category: security (moderate) Bug References: 1217826, 1222815, 1230551, 1230552, 1231345 CVE References: CVE-2023-6917, CVE-2024-45769, CVE-2024-45770 Maintenance Incident: [SUSE:Maintenance:36517](https://smelt.suse.de/incident/36517/) Sources used: openSUSE Leap 15.4 (src): pcp-6.2.0-150400.5.9.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230551] VUL-0: CVE-2024-45769: pcp: `pmcd` heap corruption through metric pmstore operations
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1230551 https://bugzilla.suse.com/show_bug.cgi?id=1230551#c22 --- Comment #22 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2025:0011-1: An update that solves three vulnerabilities and has two security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2025/suse-su-20250011-1 Category: security (moderate) Bug References: 1217826, 1222815, 1230551, 1230552, 1231345 CVE References: CVE-2023-6917, CVE-2024-45769, CVE-2024-45770 Maintenance Incident: [SUSE:Maintenance:36517](https://smelt.suse.de/incident/36517/) Sources used: openSUSE Leap 15.4 (src): pcp-6.2.0-150400.5.9.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222815] New: Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222815 Bug ID: 1222815 Summary: Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- just installing pcp and pmlogger leads to: # systemctl start pmlogger Failed to start pmlogger.service: Unit pmlogger_daily.timer not found. this unit is currently in pcp-zeroconf. however pmlogger.service is in pcp (main package). if zeroconf is supposed to be optional, then the pmlogger_daily.timer dependency is supposed to be made optional. otherwise the timer needs to be moved into the main package (like it appears to be upstream) -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1234995] New: libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 Bug ID: 1234995 Summary: libvirt: libvirt: virtimetest failing with the change to year 2025 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The `virtimetest` in libvirt started failing with the transition to the year 2025. This failure is blocking Tumbleweed development. I've created a Submit Request with a temporary fix: https://build.opensuse.org/request/show/1234542. I plan to accept it today in Factory to unblock development. However, this issue needs a more permanent solution, hence this bug report. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227477] Add Mesa-demo package to media (was: eglinfo tool is required but could not be found)
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1227477 https://bugzilla.suse.com/show_bug.cgi?id=1227477#c25 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(fvogt(a)suse.com) --- Comment #25 from Stefan Dirsch <sndirsch(a)suse.com> --- eglinfo on SP6/Leap 15.6 is still in Mesa-demo [1] # rpm -ql Mesa-demo|grep eglinfo /usr/lib64/mesa-demos/egl/opengl/eglinfo Even if we already would ship/provide this package for SP6/Leap 15.6 I doubt the info center would find it in this path. This begs the question why Fabian thinks this issues has been fixed for SP6. @Fabian, please explain. Thanks! @Felix Please don't confuse my colegues with your 3rd party elginfo (Fedora and whatever) packages. Thanks! [1] This has changed for TW though, where it is in Mesa-demo-egl now. --> /usr/bin/eglinfo -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234773] openSUSE-2024-411 is not installable - built against wrong libgarcon-branding-openSUSE version?
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234773 https://bugzilla.suse.com/show_bug.cgi?id=1234773#c5 --- Comment #5 from Marcus Meissner <meissner(a)suse.com> --- openSUSE-RU-2025:0002-1: An update that has one recommended fix can now be installed. Category: recommended (important) Bug References: 1234773 CVE References: JIRA References: Sources used: openSUSE Leap 15.6 (src): xfce4-branding-openSUSE-4.18.0+git4.79f6d44-lp156.10.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 https://bugzilla.suse.com/show_bug.cgi?id=1234995#c8 James Fehlig <jfehlig(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #8 from James Fehlig <jfehlig(a)suse.com> --- (In reply to Ana Guerrero from comment #7) > Hi Jim, > > Libvirt isn't a leaf package, it's in ring1. When a package from the rings > suddenly fails to build, it blocks packaging in staging, breaks other > builds, and delays testing. This actually happened at the worst possible > time, while the rings and staging were rebuilding. I suppose there are good reasons for ring1, but it seems odd for an optional package not installed by default. > So, what can we do to avoid this next year? I trust you as the maintainer to > choose the best solution. It would be best if the environment behaved properly when transitioning to a new year, but to avoid wasting even more time I've decided to simply extend the EOY window where the tests are skipped. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228593] New: thinkpad x13s aarch64 continue reset during grub2 load kernel
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228593 Bug ID: 1228593 Summary: thinkpad x13s aarch64 continue reset during grub2 load kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: macromarship(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I just bought a thinkpad x13s aarch64. Following HCL:suse I have successfully installed latest version. And I have copied the dtb file to system_drv partition as page requested. But after grub2 load kernel, the computer continues reset. About 7-8 times failed then 1 success. This makes I am afraid to reboot computer because next time will take more tries to come in. I notice the UEFI version is 1.60 or 1.70, which is a higher version than 1.58. Upgrade your UEFI firmware to the newer versions which can support LINUX boot v1.49 or later versions. The latest version tested: v1.58 I have read all the tickets on this website. Can any help guide how to resolve this? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1234312] [Build 20241208] openQA test fails in virt_install
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234312 https://bugzilla.suse.com/show_bug.cgi?id=1234312#c1 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Charles Arnold <carnold(a)suse.com> --- I believe this is working now. With the latest Tumbleweed there is a new virt-manager / virt-install. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231408] New: VUL-0: CVE-2024-25885: python-xhtml2pdf: regular expression denial of service through the getcolor function in utils.py
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1231408 Bug ID: 1231408 Summary: VUL-0: CVE-2024-25885: python-xhtml2pdf: regular expression denial of service through the getcolor function in utils.py Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/423265/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: python-maintainers(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- An issue in the getcolor function in utils.py of xhtml2pdf v0.2.13 allows attackers to cause a Regular expression Denial of Service (ReDOS) via supplying a crafted string. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25885 https://www.cve.org/CVERecord?id=CVE-2024-25885 http://dirk.com http://xhtml2pdf.com https://gist.github.com/salvatore-abello/c88dd0027496774023ef36c7b576d206 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1234234] New: Enrollemnt of TPM2 no longer functional
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234234 Bug ID: 1234234 Summary: Enrollemnt of TPM2 no longer functional Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello there I didn't had any issues with the TPM2 FDE until yesterday. Everything was working fine until now. Here is what happened: 1) I booted up the PC as usual and noticed Gnome-Software was opposing a secureboot sdx update 2) At first I tried to perform this update using Gnome-Software itself but the "Download and Install" button did nothing. Formerly it worked, downloaded the firmnware and prompted my to restart the computer. 3) As Gnome-Software didn't worked I ran > sudo fwupdmgr update manually and performed the update. Everything was as expected. No errors only "Update successful" 4) I rebooted the system as I now expected the TPM prediction to be invalid as it was usually the case with these kind of updates. 5) Got asked for either my recovery key or the user defined password I once set as I setted up the computer. 6) At first I tried to just update the TPM predictions as described in the Encryption guide of Aeon: > sudo sdbootutil --ask-pin update-predictions Entered my password (not the key) and all seemed good. No unexpected messages no errors 7) Rebooted to verify it has worked. It didn't I was prompted to enter my key or the password 8) I then attempted a full re-enrollment of my TPM as I did after installing the nvidia dirver as I setted up the PC. Hence I knew this worked because it did so in the past > sudo sdbootutil unenroll --method=tpm2 > dracut-install: ERROR: installing 'grub2-editenv' > dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.FBHI0O/initramfs -a date btrfs awk grub2-editenv > Cleaning /boot/efi > Removed /aeon/6.11.8-1-default/initrd-45f6758dc12fca1deebe84d7d6af9abafc75cf10 > No slots to remove selected. Nothing I seemed wrong to me. Grub makes sense because Aeon does not use GRUB and I knew this message from my first re-enrollment as I setted up the system > sudo systemd-cryptenroll > No device specified, defaulting to '/dev/nvme0n1p2'. > SLOT TYPE > 0 recovery > 1 password Nothing suspicious I suppose > sudo sdbootutil enroll --method=tpm2 > dracut-install: ERROR: installing 'grub2-editenv' > dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.M7EqLz/initramfs -a date btrfs awk grub2-editenv > Cleaning /boot/efi > Removed /aeon/6.11.8-1-default/initrd-f6a6ad1b0a2f511a784675b06e1339a8d04110e0 > Recovery PIN: <REDACTED> > You can also scan it with your mobile phone: > <REDACTED> > keyctl_set_timeout: Permission denied I was surprised receiving a new QR Code and a new recovery key which wasn't the old one. Nevertheless I wrote it down and rebooted. Also the "Permission Denied" message is new to me. 9) Got ask for either the recovery key or my password. However the key shown on screen before did not worked. I tired this 2 times, the system rebooted, ask for the key or the password and I tired the recovery key once more to no avail. I then used my password which still was functional Is there anything else I can add to this bug report , any logs to help down track down the issue? Other things I tired in the mean time: 1) Forcefully removing the recovery key using: > sudo systemd-cryptenroll --wipe-slot=2 /dev/nvme0n1p2 Back the the recovery key was in slot 2 This worked and then set a recovery key manually using the key I had noted down. > sudo systemd-cryptenroll /dev/nvme0n1p2 --recovery-key This worked as well But re-enrolling the TPM afterwards didn't worked either 2) Reset the TPM via the BIOS and doing a full re-enrollment again. No success. 3) Reverting the secure boot update, doing a full re-enrollment. No success. 4) Re-doing the secure boot update, doing a full re-enrollment. No success. 5) Performing a full BIOS updated the old fashioned way as the mainboard vendor had a new update out as of NOv. 12 2024, doing a full re-enrollment. No success. The board is a Gigabyte B650 GAMING X AX V2 (rev. 1.x) with the latest BIOS version F32e: https://www.gigabyte.com/Motherboard/B650-GAMING-X-AX-V2-rev-1x/support#sup… Kind regards, V. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1235066] New: opensuse-update fails for libgarcon-data-4.18.2-bp156.4.3.1.noarch
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235066 Bug ID: 1235066 Summary: opensuse-update fails for libgarcon-data-4.18.2-bp156.4.3.1.noarch Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: andreas.kyek(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 Build Identifier: erver:~ # export LANG=en_US.utf8 server:~ # /usr/lib/YaST2/bin/online_update Problem: 1: the to be installed libgarcon-data-4.18.2-bp156.4.3.1.noarch requires 'libgarcon-branding = 4.18.2', but this requirement cannot be provided not installable providers: libgarcon-branding-upstream-4.18.2-bp156.4.3.1.noarch[repo-backports-update] libgarcon-branding-openSUSE-4.18.0+git4.79f6d44-lp156.2.2.16.noarch[repo-update] libgarcon-branding-openSUSE-4.18.0+git4.79f6d44-lp156.2.2.16.noarch[repo-update-oss] Solution 1: Following actions will be done: do not install patch:openSUSE-2024-411-1.noarch downgrade of xfce4-panel-lang-4.18.6-bp156.2.3.1.noarch to xfce4-panel-lang-4.18.5-bp156.1.4.noarch Solution 2: Following actions will be done: do not install patch:openSUSE-2024-380-1.noarch do not install patch:openSUSE-2024-411-1.noarch Solution 3: Following actions will be done: deinstallation of libgarcon-data-4.18.1-bp156.3.5.noarch deinstallation of libgarcon-lang-4.18.1-bp156.3.5.noarch deinstallation of libgarcon-1-0-4.18.2-bp156.4.3.1.x86_64 deinstallation of xfdesktop-4.18.1-bp156.2.8.x86_64 deinstallation of xfce4-xkb-plugin-0.8.3-bp156.2.5.x86_64 deinstallation of xfce4-whiskermenu-plugin-2.8.3-bp156.1.1.x86_64 deinstallation of xfce4-appfinder-4.18.0-bp156.2.8.x86_64 deinstallation of xfdesktop-lang-4.18.1-bp156.2.8.noarch deinstallation of xfce4-xkb-plugin-lang-0.8.3-bp156.2.5.noarch deinstallation of xfce4-whiskermenu-plugin-lang-2.8.3-bp156.1.1.noarch deinstallation of xfce4-panel-lang-4.18.6-bp156.2.3.1.noarch deinstallation of xfce4-pulseaudio-plugin-0.4.8-bp156.1.3.x86_64 deinstallation of xfce4-power-manager-plugin-4.18.4-bp156.2.3.1.x86_64 deinstallation of xfce4-panel-profiles-1.0.14-bp156.1.1.noarch deinstallation of xfce4-appfinder-lang-4.18.0-bp156.2.8.noarch deinstallation of xfce4-notes-plugin-1.11.0-bp156.1.3.x86_64 deinstallation of xfce4-pulseaudio-plugin-lang-0.4.8-bp156.1.3.noarch deinstallation of xfce4-session-lang-4.18.4-bp156.2.3.1.noarch deinstallation of xfce4-notes-plugin-lang-1.11.0-bp156.1.3.noarch Solution 4: deinstallation of libgarcon-branding-openSUSE-4.18.0+git4.79f6d44-lp156.2.8.1.noarch Solution 5: break libgarcon-data-4.18.2-bp156.4.3.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/4/5/c/d/?] (c): c Reproducible: Always Steps to Reproduce: 1. start /usr/lib/YaST2/bin/online_update 2. 3. Actual Results: see details - conflict cannot be solved Expected Results: no conflicts -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1234997] New: Bottles crashes upon launch. "Namespace Xdp not available"
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234997 Bug ID: 1234997 Summary: Bottles crashes upon launch. "Namespace Xdp not available" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: Michael.Gusik(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- System: -OpenSuse Tumbleweed -[1] HP Laptop 17-cp0xxx & [2] Self-build Desktop -[1]&[2] Linux 6.12.6-1-default -[1] AMD Ryzen 5 5500U & [2] Intel I7-8700k -[1]&[2] KDE Plasma 6.2.4 -[1]&[2] KWin (Wayland) Bug: Bottles Crashes on startup. Console output: Traceback (most recent call last): File "/usr/bin/bottles", line 49, in <module> from bottles.frontend import main File "/usr/share/bottles/bottles/frontend/main.py", line 29, in <module> gi.require_version("Xdp", "1.0") File "/usr/lib64/python3.11/site-packages/gi/__init__.py", line 122, in require_version raise ValueError('Namespace %s not available' % namespace) ValueError: Namespace Xdp not available Steps to Reproduce: -Have working installation -Execute: zypper dup -Described behaviour above Additional info: I had Bottles installed on both my laptop and my Main PC. It had been working since i was using OpenSuse Tumbleweed (ca. September 2024). After a recent update on my Main PC, Bottles refused to start with this exact behaviour. Attributing this to something i did wrong and not being willing to investigate, i put this topic aside. Today i updated my Laptop and the same thing happened, which leads me to believe, that this is a problem with the provided package. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1229048] New: Always prompted for recovery key, but could not update predictions
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1229048 Bug ID: 1229048 Summary: Always prompted for recovery key, but could not update predictions Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: vandeft(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:129.0) Gecko/20100101 Firefox/129.0 Build Identifier: The recovery key prompt started after disabling and enabling Secure Boot. I tried running the following command as recommended on the troubleshooting page: sudo sdbootutil --ask-pin update-predictions The problem is that I get the error: "Provided PIN Incorrect or TPM2 locked after too many retries" even after only entering the recovery key once. I know it was entered correctly because I copied it from my password manager. Reproducible: Always Steps to Reproduce: 1. Disable Secure Boot and restart 2. Enable Secure Boot and restart 3. Boot openSUSE Aeon and enter recovery key 4. Open terminal and run "sudo sdbootutil --ask-pin update-predictions" 5. Enter recovery key Actual Results: sdbootutil tries to restore the link between my system and its encryption, but fails. Expected Results: sdbootutil should succeed in restoring the link between my system and its encryption. ○ → sudo sdbootutil -vv --ask-pin update-predictions Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy Found container virtualization none. Failed to check file system type of "/efi": No such file or directory File system "/boot" is not a FAT EFI System Partition (ESP) file system. Using EFI System Partition at /boot/efi. Directory "/boot" is not the root of the file system. Didn't find an XBOOTLDR partition, using the ESP as $BOOT. Reading EFI variable /sys/firmware/efi/efivars/LoaderEntries-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f. Reading EFI variable /sys/firmware/efi/efivars/LoaderEntryOneShot-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f. open("/sys/firmware/efi/efivars/LoaderEntryOneShot-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f") failed: No such file or directory Reading EFI variable /sys/firmware/efi/efivars/LoaderEntryDefault-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f. Reading EFI variable /sys/firmware/efi/efivars/LoaderEntrySelected-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f. Found default: id "opensuse-aeon-6.10.3-1-default-22.conf" is matched by LoaderEntryDefault TPM PC Client Platform Firmware Profile: family 2.0, revision 0.0 Ignoring device path element type=0x04 subtype=0x07 Ignoring device path element type=0x04 subtype=0x06 Ignoring device path element type=0x02 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x03 subtype=0x17 Ignoring device path element type=0x04 subtype=0x01 Garbage after device path end, ignoring. Loaded 'libtss2-esys.so.0' via dlopen() Loaded 'libtss2-rc.so.0' via dlopen() Loaded 'libtss2-mu.so.0' via dlopen() Using TPM2 TCTI driver 'device' with device '/dev/tpmrm0'. Loaded 'libtss2-tcti-device.so.0' via dlopen() Loaded TCTI module 'tcti-device' (TCTI module for communication with Linux kernel interface.) [Version 2] TPM successfully started up. Getting TPM2 capability 0x0000 property 0x0001 count 127. Getting TPM2 capability 0x0002 property 0x011f count 256. Getting TPM2 capability 0x0008 property 0x0000 count 508. Getting TPM2 capability 0x0005 property 0x0000 count 1. Reading PCR selection: [sha1(0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha1(0+1+2+3+4+5+6+7)] PCR value: 0:sha1=23745cb6a52f04f520bcb67a57a8ceeaa67cdcf7 PCR value: 1:sha1=b57cd41bd48870f77d0d89830a04ee328fe916b0 PCR value: 2:sha1=b2a83b0ebf2f8374299a5b2bdfc31ea955ad7236 PCR value: 3:sha1=b2a83b0ebf2f8374299a5b2bdfc31ea955ad7236 PCR value: 4:sha1=5822de53cb1b4fb68f7535304b12309e833c93c8 PCR value: 5:sha1=4fd367f64ae596ff430c5c81ccd39c8f3febf992 PCR value: 6:sha1=b2a83b0ebf2f8374299a5b2bdfc31ea955ad7236 PCR value: 7:sha1=e820d059eeab7d4b134ceae88672f569d4a7eb74 Reading PCR selection: [sha1(8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha1(8+9+10+11+12+13+14+15)] PCR value: 8:sha1=0000000000000000000000000000000000000000 PCR value: 9:sha1=28420f38f0c0493e60bc4349ff11f2bc1cadf744 PCR value: 10:sha1=0f7ed4a3679f7f30a7934952afd2de10d93ad37b PCR value: 11:sha1=0000000000000000000000000000000000000000 PCR value: 12:sha1=b170a442bed9b3c14c3b6a72cc3866dc6d844382 PCR value: 13:sha1=0000000000000000000000000000000000000000 PCR value: 14:sha1=677f1f77d72332e8e8041f16b6c082bf077ece84 PCR value: 15:sha1=0000000000000000000000000000000000000000 Reading PCR selection: [sha1(16+17+18+19+20+21+22+23)] Read PCR selection: [sha1(16+17+18+19+20+21+22+23)] PCR value: 16:sha1=0000000000000000000000000000000000000000 PCR value: 17:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 18:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 19:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 20:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 21:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 22:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 23:sha1=0000000000000000000000000000000000000000 Reading PCR selection: [sha256(0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(0+1+2+3+4+5+6+7)] PCR value: 0:sha256=c1f2e40d330b6a6b982f00c5aa76ac32800a36f7afdb294bf34569f1433335bb PCR value: 1:sha256=da33d382da316e5c6be06d1164b785dbec2ed2c9aaf3938c43dbcf675d074846 PCR value: 2:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 3:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 4:sha256=2c8acbf406e4ea74fa014baf1180c8f28d7c60cb3a27265d274b027885cc2416 PCR value: 5:sha256=c0b661f390b58a95f7c0173ae70e0cccaa6917f6108de9542463c578cee1d203 PCR value: 6:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 7:sha256=22f5a51babd581abe57a405f84e41c8f3da14c41ab345f274ba406d998886962 Reading PCR selection: [sha256(8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(8+9+10+11+12+13+14+15)] PCR value: 8:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 9:sha256=d4d845f23d71324ec38766e1c19f2cfe2bd413ecf27ae3b0681a5aaab38d897f PCR value: 10:sha256=e47fa4366c3527eabfabcdbb73db784214a87af792ffcdd0fc2ff44c76185f93 PCR value: 11:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 12:sha256=a443f6cf29ccc0245b39893ebf2d8bd221a021d9f68c3124849f0cb20e965832 PCR value: 13:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 14:sha256=1095b057262e3e9e1b0f3952228f2b2741be5d85dbfe5951c7e41279ceb2ebe8 PCR value: 15:sha256=0000000000000000000000000000000000000000000000000000000000000000 Reading PCR selection: [sha256(16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(16+17+18+19+20+21+22+23)] PCR value: 16:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 17:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 18:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 19:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 20:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 21:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 22:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 23:sha256=0000000000000000000000000000000000000000000000000000000000000000 /var/lib/pcrlock.d/250-firmware-code-early.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/550-firmware-code-late.pcrlock.d/generated.pcrlock written. TPM PC Client Platform Firmware Profile: family 2.0, revision 0.0 Ignoring device path element type=0x04 subtype=0x07 Ignoring device path element type=0x04 subtype=0x06 Ignoring device path element type=0x02 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x03 subtype=0x17 Ignoring device path element type=0x04 subtype=0x01 Garbage after device path end, ignoring. Loaded 'libtss2-esys.so.0' via dlopen() Loaded 'libtss2-rc.so.0' via dlopen() Loaded 'libtss2-mu.so.0' via dlopen() Using TPM2 TCTI driver 'device' with device '/dev/tpmrm0'. Loaded 'libtss2-tcti-device.so.0' via dlopen() Loaded TCTI module 'tcti-device' (TCTI module for communication with Linux kernel interface.) [Version 2] TPM successfully started up. Getting TPM2 capability 0x0000 property 0x0001 count 127. Getting TPM2 capability 0x0002 property 0x011f count 256. Getting TPM2 capability 0x0008 property 0x0000 count 508. Getting TPM2 capability 0x0005 property 0x0000 count 1. Reading PCR selection: [sha1(0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha1(0+1+2+3+4+5+6+7)] PCR value: 0:sha1=23745cb6a52f04f520bcb67a57a8ceeaa67cdcf7 PCR value: 1:sha1=b57cd41bd48870f77d0d89830a04ee328fe916b0 PCR value: 2:sha1=b2a83b0ebf2f8374299a5b2bdfc31ea955ad7236 PCR value: 3:sha1=b2a83b0ebf2f8374299a5b2bdfc31ea955ad7236 PCR value: 4:sha1=5822de53cb1b4fb68f7535304b12309e833c93c8 PCR value: 5:sha1=4fd367f64ae596ff430c5c81ccd39c8f3febf992 PCR value: 6:sha1=b2a83b0ebf2f8374299a5b2bdfc31ea955ad7236 PCR value: 7:sha1=e820d059eeab7d4b134ceae88672f569d4a7eb74 Reading PCR selection: [sha1(8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha1(8+9+10+11+12+13+14+15)] PCR value: 8:sha1=0000000000000000000000000000000000000000 PCR value: 9:sha1=28420f38f0c0493e60bc4349ff11f2bc1cadf744 PCR value: 10:sha1=0f7ed4a3679f7f30a7934952afd2de10d93ad37b PCR value: 11:sha1=0000000000000000000000000000000000000000 PCR value: 12:sha1=b170a442bed9b3c14c3b6a72cc3866dc6d844382 PCR value: 13:sha1=0000000000000000000000000000000000000000 PCR value: 14:sha1=677f1f77d72332e8e8041f16b6c082bf077ece84 PCR value: 15:sha1=0000000000000000000000000000000000000000 Reading PCR selection: [sha1(16+17+18+19+20+21+22+23)] Read PCR selection: [sha1(16+17+18+19+20+21+22+23)] PCR value: 16:sha1=0000000000000000000000000000000000000000 PCR value: 17:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 18:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 19:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 20:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 21:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 22:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 23:sha1=0000000000000000000000000000000000000000 Reading PCR selection: [sha256(0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(0+1+2+3+4+5+6+7)] PCR value: 0:sha256=c1f2e40d330b6a6b982f00c5aa76ac32800a36f7afdb294bf34569f1433335bb PCR value: 1:sha256=da33d382da316e5c6be06d1164b785dbec2ed2c9aaf3938c43dbcf675d074846 PCR value: 2:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 3:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 4:sha256=2c8acbf406e4ea74fa014baf1180c8f28d7c60cb3a27265d274b027885cc2416 PCR value: 5:sha256=c0b661f390b58a95f7c0173ae70e0cccaa6917f6108de9542463c578cee1d203 PCR value: 6:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 7:sha256=22f5a51babd581abe57a405f84e41c8f3da14c41ab345f274ba406d998886962 Reading PCR selection: [sha256(8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(8+9+10+11+12+13+14+15)] PCR value: 8:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 9:sha256=d4d845f23d71324ec38766e1c19f2cfe2bd413ecf27ae3b0681a5aaab38d897f PCR value: 10:sha256=e47fa4366c3527eabfabcdbb73db784214a87af792ffcdd0fc2ff44c76185f93 PCR value: 11:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 12:sha256=a443f6cf29ccc0245b39893ebf2d8bd221a021d9f68c3124849f0cb20e965832 PCR value: 13:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 14:sha256=1095b057262e3e9e1b0f3952228f2b2741be5d85dbfe5951c7e41279ceb2ebe8 PCR value: 15:sha256=0000000000000000000000000000000000000000000000000000000000000000 Reading PCR selection: [sha256(16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(16+17+18+19+20+21+22+23)] PCR value: 16:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 17:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 18:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 19:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 20:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 21:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 22:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 23:sha256=0000000000000000000000000000000000000000000000000000000000000000 /var/lib/pcrlock.d/250-firmware-config-early.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/550-firmware-config-late.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/600-gpt.pcrlock.d/generated.pcrlock written. Hashing 216 @ 0 → 216 Hashing 76 @ 220 → 296 Hashing 720 @ 304 → 1024 Hashing 117760 @ 1024 → 118784 Hashing 379392 @ 118784 → 498176 Hashing 512 @ 498176 → 498688 Hashing 512 @ 498688 → 499200 Hashing 179712 @ 499200 → 678912 Hashing 6656 @ 678912 → 685568 Hashing 512 @ 685568 → 686080 Hashing 111616 @ 686080 → 797696 Hashing 512 @ 797696 → 798208 Hashing 125368 @ 798208 → 923576 Hashing 216 @ 0 → 216 Hashing 76 @ 220 → 296 Hashing 720 @ 304 → 1024 Hashing 117760 @ 1024 → 118784 Hashing 379392 @ 118784 → 498176 Hashing 512 @ 498176 → 498688 Hashing 512 @ 498688 → 499200 Hashing 179712 @ 499200 → 678912 Hashing 6656 @ 678912 → 685568 Hashing 512 @ 685568 → 686080 Hashing 111616 @ 686080 → 797696 Hashing 512 @ 797696 → 798208 Hashing 125368 @ 798208 → 923576 Hashing 216 @ 0 → 216 Hashing 76 @ 220 → 296 Hashing 720 @ 304 → 1024 Hashing 117760 @ 1024 → 118784 Hashing 379392 @ 118784 → 498176 Hashing 512 @ 498176 → 498688 Hashing 512 @ 498688 → 499200 Hashing 179712 @ 499200 → 678912 Hashing 6656 @ 678912 → 685568 Hashing 512 @ 685568 → 686080 Hashing 111616 @ 686080 → 797696 Hashing 512 @ 797696 → 798208 Hashing 125368 @ 798208 → 923576 Hashing 216 @ 0 → 216 Hashing 76 @ 220 → 296 Hashing 720 @ 304 → 1024 Hashing 117760 @ 1024 → 118784 Hashing 379392 @ 118784 → 498176 Hashing 512 @ 498176 → 498688 Hashing 512 @ 498688 → 499200 Hashing 179712 @ 499200 → 678912 Hashing 6656 @ 678912 → 685568 Hashing 512 @ 685568 → 686080 Hashing 111616 @ 686080 → 797696 Hashing 512 @ 797696 → 798208 Hashing 125368 @ 798208 → 923576 /var/lib/pcrlock.d/630-shim-efi-application.pcrlock.d/generated.pcrlock written. Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 784 @ 240 → 1024 Hashing 74752 @ 1024 → 75776 Hashing 20480 @ 75776 → 96256 Hashing 512 @ 96256 → 96768 Hashing 512 @ 96768 → 97280 Hashing 512 @ 97280 → 97792 Hashing 512 @ 97792 → 98304 Hashing 512 @ 98304 → 98816 Hashing 0 @ 98816 → 98816 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 784 @ 240 → 1024 Hashing 74752 @ 1024 → 75776 Hashing 20480 @ 75776 → 96256 Hashing 512 @ 96256 → 96768 Hashing 512 @ 96768 → 97280 Hashing 512 @ 97280 → 97792 Hashing 512 @ 97792 → 98304 Hashing 512 @ 98304 → 98816 Hashing 0 @ 98816 → 98816 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 784 @ 240 → 1024 Hashing 74752 @ 1024 → 75776 Hashing 20480 @ 75776 → 96256 Hashing 512 @ 96256 → 96768 Hashing 512 @ 96768 → 97280 Hashing 512 @ 97280 → 97792 Hashing 512 @ 97792 → 98304 Hashing 512 @ 98304 → 98816 Hashing 0 @ 98816 → 98816 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 784 @ 240 → 1024 Hashing 74752 @ 1024 → 75776 Hashing 20480 @ 75776 → 96256 Hashing 512 @ 96256 → 96768 Hashing 512 @ 96768 → 97280 Hashing 512 @ 97280 → 97792 Hashing 512 @ 97792 → 98304 Hashing 512 @ 98304 → 98816 Hashing 0 @ 98816 → 98816 /var/lib/pcrlock.d/640-boot-loader-efi-application.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/641-sdboot-loader-conf.pcrlock written. Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14741504 @ 20480 → 14761984 Hashing 4608 @ 14761984 → 14766592 Hashing 0 @ 14766592 → 14766592 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14741504 @ 20480 → 14761984 Hashing 4608 @ 14761984 → 14766592 Hashing 0 @ 14766592 → 14766592 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14741504 @ 20480 → 14761984 Hashing 4608 @ 14761984 → 14766592 Hashing 0 @ 14766592 → 14766592 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14741504 @ 20480 → 14761984 Hashing 4608 @ 14761984 → 14766592 Hashing 0 @ 14766592 → 14766592 /var/lib/pcrlock.d/650-kernel-efi-application.pcrlock.d/linux-1.pcrlock written. /tmp/sdbootutil.pzayUU/cmdline.pcrlock written. /var/lib/pcrlock.d/710-kernel-cmdline-boot-loader.pcrlock.d/cmdline-1.pcrlock written. /tmp/sdbootutil.pzayUU/cmdline.pcrlock written. /var/lib/pcrlock.d/710-kernel-cmdline-boot-loader.pcrlock.d/cmdline-2.pcrlock written. Recovery PIN: TPM PC Client Platform Firmware Profile: family 2.0, revision 0.0 Ignoring device path element type=0x04 subtype=0x07 Ignoring device path element type=0x04 subtype=0x06 Ignoring device path element type=0x02 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x03 subtype=0x17 Ignoring device path element type=0x04 subtype=0x01 Garbage after device path end, ignoring. Loaded 'libtss2-esys.so.0' via dlopen() Loaded 'libtss2-rc.so.0' via dlopen() Loaded 'libtss2-mu.so.0' via dlopen() Using TPM2 TCTI driver 'device' with device '/dev/tpmrm0'. Loaded 'libtss2-tcti-device.so.0' via dlopen() Loaded TCTI module 'tcti-device' (TCTI module for communication with Linux kernel interface.) [Version 2] TPM successfully started up. Getting TPM2 capability 0x0000 property 0x0001 count 127. Getting TPM2 capability 0x0002 property 0x011f count 256. Getting TPM2 capability 0x0008 property 0x0000 count 508. Getting TPM2 capability 0x0005 property 0x0000 count 1. Reading PCR selection: [sha1(0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha1(0+1+2+3+4+5+6+7)] PCR value: 0:sha1=23745cb6a52f04f520bcb67a57a8ceeaa67cdcf7 PCR value: 1:sha1=b57cd41bd48870f77d0d89830a04ee328fe916b0 PCR value: 2:sha1=b2a83b0ebf2f8374299a5b2bdfc31ea955ad7236 PCR value: 3:sha1=b2a83b0ebf2f8374299a5b2bdfc31ea955ad7236 PCR value: 4:sha1=5822de53cb1b4fb68f7535304b12309e833c93c8 PCR value: 5:sha1=4fd367f64ae596ff430c5c81ccd39c8f3febf992 PCR value: 6:sha1=b2a83b0ebf2f8374299a5b2bdfc31ea955ad7236 PCR value: 7:sha1=e820d059eeab7d4b134ceae88672f569d4a7eb74 Reading PCR selection: [sha1(8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha1(8+9+10+11+12+13+14+15)] PCR value: 8:sha1=0000000000000000000000000000000000000000 PCR value: 9:sha1=28420f38f0c0493e60bc4349ff11f2bc1cadf744 PCR value: 10:sha1=0f7ed4a3679f7f30a7934952afd2de10d93ad37b PCR value: 11:sha1=0000000000000000000000000000000000000000 PCR value: 12:sha1=b170a442bed9b3c14c3b6a72cc3866dc6d844382 PCR value: 13:sha1=0000000000000000000000000000000000000000 PCR value: 14:sha1=677f1f77d72332e8e8041f16b6c082bf077ece84 PCR value: 15:sha1=0000000000000000000000000000000000000000 Reading PCR selection: [sha1(16+17+18+19+20+21+22+23)] Read PCR selection: [sha1(16+17+18+19+20+21+22+23)] PCR value: 16:sha1=0000000000000000000000000000000000000000 PCR value: 17:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 18:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 19:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 20:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 21:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 22:sha1=ffffffffffffffffffffffffffffffffffffffff PCR value: 23:sha1=0000000000000000000000000000000000000000 Reading PCR selection: [sha256(0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(0+1+2+3+4+5+6+7)] PCR value: 0:sha256=c1f2e40d330b6a6b982f00c5aa76ac32800a36f7afdb294bf34569f1433335bb PCR value: 1:sha256=da33d382da316e5c6be06d1164b785dbec2ed2c9aaf3938c43dbcf675d074846 PCR value: 2:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 3:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 4:sha256=2c8acbf406e4ea74fa014baf1180c8f28d7c60cb3a27265d274b027885cc2416 PCR value: 5:sha256=c0b661f390b58a95f7c0173ae70e0cccaa6917f6108de9542463c578cee1d203 PCR value: 6:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 7:sha256=22f5a51babd581abe57a405f84e41c8f3da14c41ab345f274ba406d998886962 Reading PCR selection: [sha256(8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(8+9+10+11+12+13+14+15)] PCR value: 8:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 9:sha256=d4d845f23d71324ec38766e1c19f2cfe2bd413ecf27ae3b0681a5aaab38d897f PCR value: 10:sha256=e47fa4366c3527eabfabcdbb73db784214a87af792ffcdd0fc2ff44c76185f93 PCR value: 11:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 12:sha256=a443f6cf29ccc0245b39893ebf2d8bd221a021d9f68c3124849f0cb20e965832 PCR value: 13:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 14:sha256=1095b057262e3e9e1b0f3952228f2b2741be5d85dbfe5951c7e41279ceb2ebe8 PCR value: 15:sha256=0000000000000000000000000000000000000000000000000000000000000000 Reading PCR selection: [sha256(16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(16+17+18+19+20+21+22+23)] PCR value: 16:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 17:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 18:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 19:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 20:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 21:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 22:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 23:sha256=0000000000000000000000000000000000000000000000000000000000000000 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. Found 2 possible variants of component '650-kernel-efi-application' in event log (linux-1, linux-2). Proceeding. Couldn't find component '750-enter-initrd' in event log. Didn't find component '800-leave-initrd' in event log, assuming system hasn't reached it yet. Didn't find component '850-sysinit' in event log, assuming system hasn't reached it yet. Didn't find component '900-ready' in event log, assuming system hasn't reached it yet. Skipped 2 components after location '940-' (950-shutdown, 990-final). Unable to recognize 1 components in event log. Event log record 29 (PCR 14, "Raw: MokList\000") not matching any component. PCR 0 (platform-code) matches event log and fully consists of recognized measurements. Including in set of PCRs. PCR 4 (boot-loader-code) matches event log and fully consists of recognized measurements. Including in set of PCRs. PCR 5 (boot-loader-config) matches event log and fully consists of recognized measurements. Including in set of PCRs. PCR 7 (secure-boot-policy) matches event log and fully consists of recognized measurements. Including in set of PCRs. PCR 9 (kernel-initrd) matches event log and fully consists of recognized measurements. Including in set of PCRs. No PCRs dropped from protection mask. PCRs in protection mask: 0 (platform-code), 4 (boot-loader-code), 5 (boot-loader-config), 7 (secure-boot-policy), 9 (kernel-initrd) Added prediction result 1 for PCR 0 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 2 for PCR 0 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@600-0xffffffff:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 1 for PCR 4 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 2 for PCR 4 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@600-0xffffffff:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 1 for PCR 5 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 2 for PCR 5 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@600-absent:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 3 for PCR 5 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@600-0xffffffff:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 4 for PCR 5 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@600-0xffffffff:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@600-absent:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 1 for PCR 7 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 2 for PCR 7 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@600-0xffffffff:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 1 for PCR 9 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 2 for PCR 9 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-2:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 3 for PCR 9 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:620-secureboot-authority@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-3:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Predicted future PCRs in 1.979ms. [ { "pcr" : 0, "values" : [ "c1f2e40d330b6a6b982f00c5aa76ac32800a36f7afdb294bf34569f1433335bb", "42898f424c28badd6fe7cbeb49c107f80ac910760b69ed9b6bd32920a2a65b33" ] }, { "pcr" : 4, "values" : [ "2c8acbf406e4ea74fa014baf1180c8f28d7c60cb3a27265d274b027885cc2416", "27cbe31f31e033805684ec185def5e32b6d4cb08432d64f43a377bec0243cefb" ] }, { "pcr" : 5, "values" : [ "c0b661f390b58a95f7c0173ae70e0cccaa6917f6108de9542463c578cee1d203", "935075d2a20e8ddc861722f2bdc0de78aad8f306843f092910c6ed32dbe888e4", "072b91ff3de7696151dbb5584575e8ac348c670a34f271fb099f617c2afd4448", "0ed87e2ffb634d91b6e20da816eec3dd2284b8fe0035fde8531c3e96370a8f18" ] }, { "pcr" : 7, "values" : [ "22f5a51babd581abe57a405f84e41c8f3da14c41ab345f274ba406d998886962", "1a2deb2d5316c9093ef8a6f4e20dbac5e0be296eb0efe0be0a3e23e621157a3c" ] }, { "pcr" : 9, "values" : [ "d4d845f23d71324ec38766e1c19f2cfe2bd413ecf27ae3b0681a5aaab38d897f", "0d1b30845de98a7dd32201a94aad68f18a0665cd25cde2d599cccb0b363ee2b9", "433a0b89e7fcab6694c177acb686489bec81018e14fe4ce954d5438316603177" ] } ] Using TPM2 TCTI driver 'device' with device '/dev/tpmrm0'. Loaded 'libtss2-tcti-device.so.0' via dlopen() Loaded TCTI module 'tcti-device' (TCTI module for communication with Linux kernel interface.) [Version 2] TPM successfully started up. Getting TPM2 capability 0x0000 property 0x0001 count 127. Getting TPM2 capability 0x0002 property 0x011f count 256. Getting TPM2 capability 0x0008 property 0x0000 count 508. Getting TPM2 capability 0x0005 property 0x0000 count 1. Starting HMAC encryption session. Converting PIN into TPM2 HMAC-SHA256 object. Loading external key into TPM. Starting policy session. Submitting PolicySigned policy for HMAC-SHA256. Acquiring policy digest. Session policy digest: c3261b61d61ae9cebc2fbe4e64ab2548b58ef9dd3643d1cf172bd28a74132fd5 Calculating new PCR policy to write... PolicyPCR calculated digest: 6b4175491ce0b23cd5d93dbc3f3364768a64283951ae62610c56871f1843d8fd Calculated PCR policy variant 1 for PCR 0 PolicyPCR calculated digest: c2bb1c9990f5b7b6b8dfb343b21b2d532e20486b871387679b6f82ef6e5ea27e Calculated PCR policy variant 2 for PCR 0 OR Branch #0: 6b4175491ce0b23cd5d93dbc3f3364768a64283951ae62610c56871f1843d8fd OR Branch #1: c2bb1c9990f5b7b6b8dfb343b21b2d532e20486b871387679b6f82ef6e5ea27e PolicyOR calculated digest: cd5d6970e6b52fc15ab5d3b9ce978cd2848198ac7d1f902dd9b660f13d58ff8f Combined 2 variants in OR policy. PolicyPCR calculated digest: 32aced0716b3b3a9385be277f969bfb6dd7d683ed1a881212d736bd2ecc08701 Calculated PCR policy variant 1 for PCR 4 PolicyPCR calculated digest: c07fdb3efd446bff0d2fa4c59e78da8bf66437052b487e22df015363827fd844 Calculated PCR policy variant 2 for PCR 4 OR Branch #0: 32aced0716b3b3a9385be277f969bfb6dd7d683ed1a881212d736bd2ecc08701 OR Branch #1: c07fdb3efd446bff0d2fa4c59e78da8bf66437052b487e22df015363827fd844 PolicyOR calculated digest: e5806d8dfbfd4b188b458fa271d2e75490cc659684f238d02b56d1680597eb57 Combined 2 variants in OR policy. PolicyPCR calculated digest: 8cc15772306c7d06c4d1638458d0561318f1b80f3f97b812d401ee45356f3883 Calculated PCR policy variant 1 for PCR 5 PolicyPCR calculated digest: c6c8983c5b6bd48524cc0b84b1d3529ddbb7ddafc439f605e2d1adb296017485 Calculated PCR policy variant 2 for PCR 5 PolicyPCR calculated digest: ad2f61d1f30b27bc2d2139f01a144108ab0b31c2837f18736581d04d1c68d33f Calculated PCR policy variant 3 for PCR 5 PolicyPCR calculated digest: 30f63fb7db60131c9ca62bac1af4269f6947a506a940975b93110ddccdd9099c Calculated PCR policy variant 4 for PCR 5 OR Branch #0: 8cc15772306c7d06c4d1638458d0561318f1b80f3f97b812d401ee45356f3883 OR Branch #1: c6c8983c5b6bd48524cc0b84b1d3529ddbb7ddafc439f605e2d1adb296017485 OR Branch #2: ad2f61d1f30b27bc2d2139f01a144108ab0b31c2837f18736581d04d1c68d33f OR Branch #3: 30f63fb7db60131c9ca62bac1af4269f6947a506a940975b93110ddccdd9099c PolicyOR calculated digest: ed8533e59387bea4f6dfadbfac6e7bc6d43d696be8329ab21a1af31bc16266c5 Combined 4 variants in OR policy. PolicyPCR calculated digest: 62f42e42a8b2bcf3e5b50071e7003f3e84923c77c27e0ba2fee00f80ac636279 Calculated PCR policy variant 1 for PCR 7 PolicyPCR calculated digest: 838e0466d318fae0f4a380d3c50131ad787a608d7a0d87ef1b2a325137121a0e Calculated PCR policy variant 2 for PCR 7 OR Branch #0: 62f42e42a8b2bcf3e5b50071e7003f3e84923c77c27e0ba2fee00f80ac636279 OR Branch #1: 838e0466d318fae0f4a380d3c50131ad787a608d7a0d87ef1b2a325137121a0e PolicyOR calculated digest: 80fc0a160542eac4c8364982675e3e1e6d1f89cf31f61c9e5907f99a753e4f87 Combined 2 variants in OR policy. PolicyPCR calculated digest: 7911cd4e5ff5175d18b57643a3576932a237abd97f5240f2c7318b8586775c53 Calculated PCR policy variant 1 for PCR 9 PolicyPCR calculated digest: 9d69423bfe4901d61f0792e69e2da706b22c8a80d4289abd8d592774c11565d9 Calculated PCR policy variant 2 for PCR 9 PolicyPCR calculated digest: ce0d60c2d319db72aecc881eb8d42d6dc17beca8394af8a832d6a0f297604db1 Calculated PCR policy variant 3 for PCR 9 OR Branch #0: 7911cd4e5ff5175d18b57643a3576932a237abd97f5240f2c7318b8586775c53 OR Branch #1: 9d69423bfe4901d61f0792e69e2da706b22c8a80d4289abd8d592774c11565d9 OR Branch #2: ce0d60c2d319db72aecc881eb8d42d6dc17beca8394af8a832d6a0f297604db1 PolicyOR calculated digest: a95db79012016c57c33f257e0fd02d1da8862c6740bcfa599c5145819e374d24 Combined 3 variants in OR policy. Calculated new PCR policy in 526us. Writing new PCR policy to NV index... WARNING:esys:src/tss2-esys/api/Esys_NV_Write.c:310:Esys_NV_Write_Finish() Received TPM Error ERROR:esys:src/tss2-esys/api/Esys_NV_Write.c:110:Esys_NV_Write() Esys Finish ErrorCode (0x0000099d) Failed to write NV index: tpm:session(1):a policy check failed Failed to write to NV index: State not recoverable Error creating the policy! Provided PIN incorrect or TPM2 locked after too many retries NVIndex policy created -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1232734] New: Recovery key re-enrollement seemed to work but eventually broke the bootloader
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1232734 Bug ID: 1232734 Summary: Recovery key re-enrollement seemed to work but eventually broke the bootloader Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Transactional Update Assignee: rbrown(a)suse.com Reporter: vincent.conus(a)pm.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:132.0) Gecko/20100101 Firefox/132.0 Build Identifier: Having a similar issue with the recovery key being requested after system update, as described in issue 1228863, I tried and went through a full re-enrollement, as described on the Advanced documentation. https://bugzilla.opensuse.org/show_bug.cgi?id=1228863 This step was not working and I kept getting prompt that the recovery key was unvalid, even though I just used it to manually unlock my system. Following the advice in comment https://bugzilla.opensuse.org/show_bug.cgi?id=1228863#c12, I tried and ran `systemd-cryptenroll --tpm2-device=auto /dev/nvme0n1p2`. This seemed to work, since I could successfully enter my recovery key, and after running `sudo systemd-cryptenroll`, a TPM entry was visible. However, after rebooting the system, no partition was available to boot anymore! I'm guessing the re-enrollement broke the bootloader... Reproducible: Didn't try Steps to Reproduce: 1. At some point, a system update reboot would start asking me to enter the recovery key. This happens randomly as some updates on the same machine worked just fine. 2. `sudo sdbootutil --ask-pin update-predictions` fails, then trying a full re-enrollement. 3.`sudo sdbootutil unenroll --method=tpm2` seems to work 4. `sudo systemd-cryptenroll`: no more TPM entry 5. `sudo sdbootutil enroll --method=tpm2` fails, saying the recovery key is wrong. 6. `echo 5 | sudo tee /sys/class/tpm/tpm0/ppi/request` 7. reboot, recovery key 8. `systemd-cryptenroll --tpm2-device=auto /dev/nvme0n1p2` is successful 9. `sudo systemd-cryptenroll` is succseful: a TPM entry was visible 10. Reboot 11. No more bootable partition visible from the BIOS !! Actual Results: No more bootable partition visible on boot. No really knowing what to do, I proceed with a full system re-install. Because of that, I don't have any logs at hand. I'll update this ticket it the bug re-appear! Expected Results: The system restart as usual, using TPM2.0 without asking for the recovery key. Some error messages spitted by the full re-enrollement commands suggest that the fact that I have another NVMe SSD in my laptop, also containing a LUKS partition confused the TMP system, as some command seemed to try to work on the other disk instead of the system one. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217920] New: QT_IM_MODULE is always set on plasma 5.27.9
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1217920 Bug ID: 1217920 Summary: QT_IM_MODULE is always set on plasma 5.27.9 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: i(a)xuzhao.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- According to the fcitx5 on wayland wiki page: https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland QT_IM_MODULE and GTK_IM_MODULE and SDL_IM_MODULE are not suggested to be set on fcitx5+plasma_wayland>5.27. However, after I install fcitx5 on opensuse 20231117, these environment variables are still being set by default. Is there a way that I can disable setting these environment variables on startup? -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1234692] Moval of dbus-launch to dbus-daemon prevents start of Dolphin super user mode
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234692 https://bugzilla.suse.com/show_bug.cgi?id=1234692#c8 Christophe Marin <christophe(a)krop.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #8 from Christophe Marin <christophe(a)krop.fr> --- Closing. I also fixed krusader 2 days ago. Opening krusader as root from dolphin context menu should be possible now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234618] New: Add package for Brother printers
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234618 Bug ID: 1234618 Summary: Add package for Brother printers Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: rbrown(a)suse.com Reporter: emtorres(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a Brother laser printer. The system correctly autodetects the printer, but since it does not have the 'brlaser' driver, it adds it as if it were an HP printer. It could be useful as it supports multiple Brother laser printers (don't know how popular Brother printers are :)). The package is printer-driver-brlaser Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1230006] New: Mobile Broadband unavailable after installation
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1230006 Bug ID: 1230006 Summary: Mobile Broadband unavailable after installation Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: hja37(a)aol.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On a fresh installation of openSUSE Aeon, it is not possible to configure a Mobile Broadband connection due to a missing dependency of ModemManager, libmbim. Without this library ModemManager is unable to configure the modem. Observable behaviour is Mobile Network is absent from GNOME settings. Solution: Install missing libmbim dependency and reboot the system. Mobile Broadband is then configurable from GNOME settings, as expected. # transactional-update pkg in libmbim -- You are receiving this mail because: You are on the CC list for the bug.

1 4