October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1227420] New: openSUSE missing fi keymap
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227420 Bug ID: 1227420 Summary: openSUSE missing fi keymap Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: jarkko.torvinen(a)iki.fi QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On Tumbleweed installer, when selecting keyboard "Finnish", it results in "fi-kotoistus" in /etc/vconsole.conf. Gnome is not aware of such layout, resulting in non-working keymap in Gnome desktop, gnome-settings listing input source as "fi+kotoistus", and you need to change it to "Finnish" or "Finnish (classic)" to have working keyboard. On Aeon, keyboard selection is done with gnome initial setup. It has options "Finnish" and "Finnish (classic)" (as above with TW gnome-settins). 1) "Finnish" results in "fi" in /etc/vconsole.conf, but fi.map.gz does not exist in openSUSE, resulting in failing unit systemd-vconsole-setup 2) "Finnish (classic)" results in "fi-classic" in /etc/vconsole.conf, and everything works fine So both TW and Aeon are broken if you simply select obvious choices "Finnish". TW in GNOME, Aeon in form of failing unit during boot. On TW, selecting "Finnish" does not alter /etc/vconsole.conf anymore, so it does not break it, only initial setup with Aeon. Other distros (Debian,Arch for example) ship with "fi" map, and works as should. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1232640] New: tesseract-ocr fails to run
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232640 Bug ID: 1232640 Summary: tesseract-ocr fails to run Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: jcarricksmith(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to run tesseract in openSUSE Leap 15.6 the error message:- tesseract: error while loading shared libraries: libOpenCL.so.1: cannot open shared object file: No such file or directory appears. Installing package libOpenCL1 package creates /usr/lib64/ocl-icd/libOpenCL.so.1 Creating a link to this in /usr/lib64/ gives me a workaround. I don't what the appropriate fix is. Many thanks John -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1231325] New: dracut-pcr-signature races with udev for ESP symlinks
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231325 Bug ID: 1231325 Summary: dracut-pcr-signature races with udev for ESP symlinks Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: aplanas(a)suse.com Target Milestone: --- Found By: --- Blocker: --- My FDE VM systematically fails to automatically unlock root the first time after host has been restarted. I compared PCR values and TPM log between bad and good cases and no changes are present - the values are identical. Then I remembered that not so long ago the same VM failed to boot, with log in https://bugzilla.suse.com/attachment.cgi?id=873748. Which shows [ 23.780502] localhost pcr-signature.sh[417]: mount: /tmp/pcr-signature: wrong fs type, bad option, bad superblock on /dev/disk/by-partuuid/4d904b6d-6495-4891-8481-fe0fbdacec21, missing codepage or helper program, or other error. ... [ 24.814025] localhost systemd[1]: systemd-cryptsetup(a)cr_root.service: Control process exited, code=exited, status=1/FAILURE and then I looked into dracut-pcr-oracle changelog which says commit ae07fc611de1884207614125533482477e9e2f8b Author: Alberto Planas <aplanas(a)suse.com> Date: Tue Apr 16 19:19:21 2024 +0200 Do not hard fail when error in mount which explains why my VM stopped to fail, but continued to require manual unlocking. pcr-signature.sh is using DEV="/dev/disk/by-partuuid/${ESP_UUID}" where ${ESP_UUID} is taken from EFI NVRAM, but it never actually checks that it exists or waits for this link to appear. Which pretty much explains my failures. pcr-signature.sh must really be split into two parts 1. systemd generator that determines device and adds Requires and After for this device to (root device) systemd-cryptsetup@.service. 2. The script that mounts this device. Actually, if we go generator route we could just as well create the proper mount unit for the LoaderDevice and simply add the proper dependencies. Because currently there is obvious race condition between multiple encrypted device, each attempting to mount and then unmount LoaderDevice. Having the proper mount unit will solve this as well. Hmm ... I expected that it would race with /boot/efi mount on Tumbleweed, but I was surprised that with systemd-boot ESP is not mounted in initrd. I am not sure why, but this may be potential source of problems with grub2 BLS module. Because we cannot mount the same FAT filesystem twice. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1220626] New: bash-completion: error: "bash: have: command not found"
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1220626 Bug ID: 1220626 Summary: bash-completion: error: "bash: have: command not found" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: werner(a)suse.com Target Milestone: --- Found By: --- Blocker: --- This was problem in the past (#1060111) and now, after update to 2.12.0-1.1 (https://build.opensuse.org/request/show/1149849) it strikes again: bash: have: command not found bash: have: command not found bash: have: command not found $ rpm -qa |grep bash-completion perf-bash-completion-6.7.6-83.14.x86_64 SwayNotificationCenter-bash-completion-0.10.0-1.1.noarch bash-completion-2.12.0-1.1.noarch playerctl-bash-completion-2.4.1-1.11.noarch cpupower-bash-completion-6.7.6-6.9.noarch ethtool-bash-completion-6.7-1.1.noarch lightdm-bash-completion-1.32.0-2.5.noarch tig-bash-completion-2.5.8-1.6.noarch python-tqdm-bash-completion-4.66.1-3.4.noarch firewalld-bash-completion-2.1.1-1.2.noarch udisks2-bash-completion-2.10.0-2.2.noarch augeas-bash-completion-1.14.1-1.2.x86_64 virt-v2v-bash-completion-2.4.0-3.1.noarch docker-bash-completion-25.0.3_ce-2.1.noarch alacritty-bash-completion-0.13.1-1.2.noarch whois-bash-completion-5.5.20-1.2.noarch subversion-bash-completion-1.14.3-1.4.noarch kmod-bash-completion-31-2.2.noarch android-tools-bash-completion-34.0.4-2.3.noarch iproute2-bash-completion-6.7-1.2.x86_64 wl-clipboard-bash-completion-2.2.0-1.2.noarch btrfsprogs-bash-completion-6.7.1-1.1.x86_64 mbimcli-bash-completion-1.28.4-2.2.noarch pulseaudio-bash-completion-17.0-2.1.x86_64 yt-dlp-bash-completion-2023.12.30-1.4.noarch nvme-cli-bash-completion-2.8-1.1.noarch fwupd-bash-completion-1.9.13-1.1.noarch ModemManager-bash-completion-1.20.6-2.2.noarch mpv-bash-completion-0.37.0+git20231121.2a57a6ee-1.3.noarch $ rpm -q bash bash-5.2.26-10.3.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1231661] New: wget incorrectly truncate long file names
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231661 Bug ID: 1231661 Summary: wget incorrectly truncate long file names Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: osukup(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- wget on SLE-15/Leap 15 truncates names not based on name length but on length of whole patch. wget version 1.20.3 log example: ~~~ The name is too long, 257 chars total. Trying to shorten... New name is download.suse.de/ibs/SUSE:/ALP:/Products:/Marble:/6.0:/ToTest/product/repo/SL-Micro-6.0-x86_64/repodata/fd6a97967b76bd8a32e3045f048c3e126758a1dfd80a8c20aa9b3c45051c64252fc0e2a2d13d80bcdb60b0bcdfd234d39b4b3379d58e677ba4034b80836596aa-lic. --2024-10-14 08:04:47-- https://download.suse.de/ibs/SUSE:/ALP:/Products:/Marble:/6.0:/ToTest/produ… Connecting to download.suse.de (download.suse.de)|10.145.50.110|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 78097 (76K) [application/x-download] Saving to: ‘download.suse.de/ibs/SUSE:/ALP:/Products:/Marble:/6.0:/ToTest/product/repo/SL-Micro-6.0-x86_64/repodata/fd6a97967b76bd8a32e3045f048c3e126758a1dfd80a8c20aa9b3c45051c64252fc0e2a2d13d80bcdb60b0bcdfd234d39b4b3379d58e677ba4034b80836596aa-lic’ download.suse.de/ibs/SUSE:/ALP:/Products:/Marble:/6.0:/ToTest/product/repo/SL-Micro-6.0-x86_64/repodata/fd6a97967b76bd8a32e3045f048c3e126758a1dfd80a8c20aa9b3c45051c64252fc0e2a2d13d80bcdb60b0bcdfd234d39b4b3379d58e677ba4034b80836596aa-lic 0%[ ] 0 --.-KB/s download.suse.de/ibs/SUSE:/ALP:/Products:/Marble:/6.0:/ToTest/product/repo/SL-Micro-6.0-x86_64/repodata/fd6a97967b76bd8a32e3045f048c3e126758a1dfd80a8c20aa9b3c45051c64252fc0e2a2d13d80bcdb60b0bcdfd234d39b4b3379d58e677ba4034b80836596aa-lic 100%[=======================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================>] 76.27K --.-KB/s in 0.002s ~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1224403] New: bpftrace: ERROR: Error attaching probe: 'kprobe:swap_readpage'
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1224403 Bug ID: 1224403 Summary: bpftrace: ERROR: Error attaching probe: 'kprobe:swap_readpage' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- bpftrace fails to attach probe: # echo -e "\ninterval:s:5 { exit(); }" | cat /usr/share/bpftrace/tools/swapin.bt - | bpftrace - stdin:1-16: WARNING: swap_readpage is not traceable (either non-existing, inlined, or marked as "notrace"); attaching to it will likely fail Attaching 3 probes... cannot attach kprobe, probe entry may not exist ERROR: Error attaching probe: 'kprobe:swap_readpage' # echo $? 255 It has been failing for some time (at least since 20240412, but probably much longer). -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1232669] New: gdm: gdm-config not working on openSUSE
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232669 Bug ID: 1232669 Summary: gdm: gdm-config not working on openSUSE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: matthias.gerstner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dimstar(a)opensuse.org Target Milestone: --- Found By: --- Blocker: --- Newer GDM versions ship with a `gdm-config` utility that is supposed to allow configuring things like fingerprint authentication and smartcard authentication. It turns out this utility is not working on openSUSE: gdm-config smartcard -e (gdm-config:32822): Gdm-CRITICAL **: 17:31:29.942: Failed to handle “smartcard” command: No PAM module available for Smart Card authentication The reason why it fails is, that it looks for the gdm-smartcard PAM file in /etc, not in /usr/lib/pam.d: strace gdm-config smartcard -e |& grep smartcard execve("/usr/bin/gdm-config", ["gdm-config", "smartcard", "-e"], 0x7ffeaa26de10 /* 58 vars */) = 0 newfstatat(AT_FDCWD, "/etc/pam.d/gdm-smartcard", 0x7ffed4ce4810, 0) = -1 ENOENT (No such file or directory) (gdm-config:32830): Gdm-CRITICAL **: 17:33:00.721: Failed to handle “smartcard” command: No PAM module available for Smart ) = 128 But even when working around this by placing a symlink, this still doesn't work: gdm-config smartcard -e (gdm-config:32857): Gdm-CRITICAL **: 17:38:31.688: Failed to handle “smartcard” command: Failed to run a required distro hook: No distro detected, no hook to run It seems during build time of GDM the DISTRO meson option needs to be set and a "distro hook" script needs to be specified that performs the necessary configuration steps, if any. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1232062] New: Mozc Japanese keyboard not available after setting the locale
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232062 Bug ID: 1232062 Summary: Mozc Japanese keyboard not available after setting the locale Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: vincent.conus(a)pm.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Overview: --- On my two most recent install of Aeon, the post-install setup of locale to add Japanese keyboard succeed at adding the fonts and packages, but the MOZC keyboard does not appear in the keyboard option in the settings menu of GNOME. Steps to reproduce: --- 1) Fresh Aeon install. 2) `sudo transactional-update -n run zypper -n aloc ja_JA` 3) reboot Actual results: --- No additional Japanese keyboards available. Expected results: --- MOZC Japanese keyboard should appear in the list of Japanese language keyboard. Variation of the problem: --- I first encountered this issue when I tried to add both Japanese and Thai keyboard, with a command such as: `sudo transactional-update -n run zypper -n aloc ja_JA th_TH` I assumed the second locale was the issue, but on another new install, the "normal" command meant to add only Japanese variable produced the same resultsi This happened on two different machines. Version: --- I have this issue since at least the 20241011 snapshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227180] New: Potential regression io-io_uring-nops reports 3-8% decrease in mainline
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227180 Bug ID: 1227180 Summary: Potential regression io-io_uring-nops reports 3-8% decrease in mainline Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: gabriel.bertazi(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- grid Infrastructure reports a 3-8% regression on io_uring nops test, found on Simba2 test potentially introduced by: Report Message-ID (Internal: <667e4b04./dspYBfaSWvQlPH0%root(a)laplace.suse.de>) Last Good/First Bad commit ========================== Last good commit: 23fbdde6205d9351bb52a4b8f11ec38bdbc8561a First bad commit: 0667db14e1f029d56243aa2509ebc5f944388200 From 0667db14e1f029d56243aa2509ebc5f944388200 Mon Sep 17 00:00:00 2001 From: Pavel Begunkov <asml.silence(a)gmail.com> Date: Mon, 18 Mar 2024 22:00:34 +0000 Subject: [PATCH] io_uring: refactor io_req_complete_post() Comparison ========== initial initial last penup last penup first good-96fca68c4fbf bad-afcd48134c58 bad-6498c5c9 bad-87585b05 good-23fbdde6 good-e5c12945 bad-0667db14 Min kIOPS 1429690.00 ( 0.00%) 1321070.00 ( -7.60%) 1384300.00 ( -3.17%) 1387440.00 ( -2.96%) 1447660.00 ( 1.26%) 1440670.00 ( 0.77%) 1383010.00 ( -3.27%) Hmean kIOPS 1593231.10 ( 0.00%) 1465349.28 * -8.03%* 1538450.10 * -3.44%* 1529321.56 * -4.01%* 1594227.00 ( 0.06%) 1595295.82 ( 0.13%) 1539502.39 * -3.37%* Stddev kIOPS 20306.39 ( 0.00%) 18381.94 ( 9.48%) 18745.79 ( 7.69%) 16745.21 ( 17.54%) 17985.08 ( 11.43%) 18572.15 ( 8.54%) 18746.99 ( 7.68%) CoeffVar kIOPS 1.27 ( 0.00%) 1.25 ( 1.58%) 1.22 ( 4.40%) 1.09 ( 14.09%) 1.13 ( 11.48%) 1.16 ( 8.66%) 1.22 ( 4.46%) Max kIOPS 1596750.00 ( 0.00%) 1469160.00 ( -7.99%) 1541920.00 ( -3.43%) 1532590.00 ( -4.02%) 1597540.00 ( 0.05%) 1598520.00 ( 0.11%) 1542790.00 ( -3.38%) BHmean-50 kIOPS 1596569.59 ( 0.00%) 1468943.05 ( -7.99%) 1541505.71 ( -3.45%) 1532015.50 ( -4.04%) 1597234.47 ( 0.04%) 1598279.59 ( 0.11%) 1542587.95 ( -3.38%) BHmean-95 kIOPS 1596456.58 ( 0.00%) 1468444.20 ( -8.02%) 1541379.66 ( -3.45%) 1531885.72 ( -4.04%) 1597010.06 ( 0.03%) 1598150.62 ( 0.11%) 1542470.52 ( -3.38%) BHmean-99 kIOPS 1595092.95 ( 0.00%) 1466984.13 ( -8.03%) 1540200.20 ( -3.44%) 1530919.05 ( -4.02%) 1595875.70 ( 0.05%) 1597044.89 ( 0.12%) 1541282.00 ( -3.37%) -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1232566] New: VUL-0: chromium: 130.0.6723.91 stable release
by bugzilla_noreply＠suse.com 05 Nov '24

05 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232566 Bug ID: 1232566 Summary: VUL-0: chromium: 130.0.6723.91 stable release Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://chromereleases.googleblog.com/2024/10/stable-c hannel-update-for-desktop_29.html OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: ro(a)suse.com Reporter: Andreas.Stieger(a)gmx.de QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-des… Fixed in Chromium 130.0.6723.91: * CVE-2024-10487: Out of bounds write in Dawn * CVE-2024-10488: Use after free in WebRTC -- You are receiving this mail because: You are on the CC list for the bug.

1 3