May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213785] New: [Build 20230729] openQA test fails in perf
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1213785 Bug ID: 1213785 Summary: [Build 20230729] openQA test fails in perf Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3468080/modules/perf /steps/33 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation tcp_sendmsg is out of .text, skip it. Probe point 'tcp_sendmsg' not found. Error: Failed to add events. openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_misc@64bit fails in [perf](https://openqa.opensuse.org/tests/3468080/modules/perf/steps/33) ## Test suite description Maintainer: zluo(a)suse.de -- Tests: iotop, gd, perf and journalctlLevels -- see poo#93820 for details ## Reproducible Fails since (at least) Build [20230729](https://openqa.opensuse.org/tests/3467348) ## Expected result Last good: [20230728](https://openqa.opensuse.org/tests/3465334) (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 3

[Bug 1222576] New: Virtualbox doesn't work with secure boot
by bugzilla_noreply＠suse.com 28 Jun '24

28 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222576 Bug ID: 1222576 Summary: Virtualbox doesn't work with secure boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When secure boot is enabled, the virtual machine does not start. "The virtual machine 'Windows 11' has terminated unexpectedly during startup with exit code 1 (0x1). Result Code: NS_ERROR_FAILURE (0X80004005) Component: MachineWrap Interface: IMachine {300763af-5d6b-46e6-aa96-273eac15538a}" "Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing '/usr/sbin/vboxconfig' as root. If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information. where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT." -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217688] New: mariadb: a table is missing inserted entries from concurrent processes
by bugzilla_noreply＠suse.com 28 Jun '24

28 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1217688 Bug ID: 1217688 Summary: mariadb: a table is missing inserted entries from concurrent processes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://jira.mariadb.org/browse/MDEV-32871 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: danilo.spinella(a)suse.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871082 --> https://bugzilla.suse.com/attachment.cgi?id=871082&action=edit db inserter With mariadb: 11.0.2, 11.1.2 and 11.1.3 (from server:database): From my c++ code, using connector-c, I do: SET autocommit=0 CREATE TABLE IF NOT EXISTS sources(id INTEGER AUTO_INCREMENT PRIMARY KEY, src VARCHAR(1024) NOT NULL UNIQUE) INSERT IGNORE INTO sources(src) VALUES (?) START TRANSACTION And then a lot of: INSERT IGNORE INTO sources(src) VALUES ('src-003431-00001') src is composed of pid and values from 0 to 49. So they are all unique. Finally, I do: COMMIT If I run 10 instances in parallel like: for aa in {1..10} ; do ./db & done ; wait I see: select count(id), substr(src,5,6) as sss from sources group by sss; +-----------+--------+ | count(id) | sss | +-----------+--------+ | 50 | 003430 | | 50 | 003431 | | 50 | 003432 | | 40 | 003433 | | 50 | 003434 | | 50 | 003435 | | 50 | 003436 | | 50 | 003437 | | 50 | 003438 | | 50 | 003439 | +-----------+--------+ I.e. Some of pids stored only last 40 values, numbers 0..9 are missing in the table: select src from sources where src like '%003433%' order by src ; +------------------+ | src | +------------------+ | src-003433-00010 | | src-003433-00011 | | src-003433-00012 | | src-003433-00013 | | src-003433-00014 | | src-003433-00015 | | src-003433-00016 | | src-003433-00017 | | src-003433-00018 | | src-003433-00019 | | src-003433-00020 | | src-003433-00021 | | src-003433-00022 | | src-003433-00023 | | src-003433-00024 | | src-003433-00025 | | src-003433-00026 | | src-003433-00027 | | src-003433-00028 | | src-003433-00029 | | src-003433-00030 | | src-003433-00031 | | src-003433-00032 | | src-003433-00033 | | src-003433-00034 | | src-003433-00035 | | src-003433-00036 | | src-003433-00037 | | src-003433-00038 | | src-003433-00039 | | src-003433-00040 | | src-003433-00041 | | src-003433-00042 | | src-003433-00043 | | src-003433-00044 | | src-003433-00045 | | src-003433-00046 | | src-003433-00047 | | src-003433-00048 | | src-003433-00049 | +------------------+ Is this a bug in my program (attached) or the db? If I look into the general log, I see the inserts which apparently did not get into the table: grep src-003433 /tmp/glog 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00000') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00000') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00000') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00000') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00000') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00001') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00002') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00003') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00004') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00005') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00006') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00007') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00008') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00009') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00010') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00010') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00011') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00012') Note also the repeated inserts. They come from a deadlock, so I repeat the exec in a loop (see the code). Dockers with mariadb:latest (11.2.2) mariadb:11.1.3 mariadb:11.1.2 all run FINE too. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1224149] New: [SELinux] sdbootutil (snapperd_t) failes to execute systemd-pcrlock (init_exec_t)
by bugzilla_noreply＠suse.com 28 Jun '24

28 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224149 Bug ID: 1224149 Summary: [SELinux] sdbootutil (snapperd_t) failes to execute systemd-pcrlock (init_exec_t) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE MicroOS 10:~ # sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 33 10:~ # zypper info selinux-policy Loading repository data... Reading installed packages... Information for package selinux-policy: --------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : selinux-policy Version : 20240321-1.2 Arch : noarch Vendor : openSUSE Installed Size : 24.8 KiB Installed : Yes (automatically) Status : up-to-date Source package : selinux-policy-20240321-1.2.src Upstream URL : https://github.com/fedora-selinux/selinux-policy.git Summary : SELinux policy configuration Description : SELinux Reference Policy. A complete SELinux policy that can be used as the system policy for a variety of systems and used as the basis for creating other policies. 10:~ # rpm -q sdbootutil sdbootutil-1+git20240506.573a6a4-1.1.x86_64 10:~ # rpm -qf /usr/lib/systemd/systemd-pcrlock systemd-experimental-255.4-3.1.x86_64 10:~ # ls -l /etc/systemd/tpm2-pcr-public-key.pem /etc/systemd/tpm2-pcr-private-key.pem ls: cannot access '/etc/systemd/tpm2-pcr-public-key.pem': No such file or directory ls: cannot access '/etc/systemd/tpm2-pcr-private-key.pem': No such file or directory 10:~ # sdbootutil defaults to systemd-pcrlock if is is present and no previous keypair for the signed policy is present. 10:~ # semodule -DB 10:~ # systemctl start snapper-cleanup.service 10:~ # semodule -B 10:~ # ausearch -m AVC,USER_AVC,SELINUX_ERR,USER_SELINUX_ERR -ts boot ---- time->Sun May 12 08:54:27 2024 type=AVC msg=audit(1715493267.232:132): avc: denied { execute } for pid=1325 comm="sdbootutil" name="systemd-pcrlock" dev="dm-0" ino=57169 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:init_exec_t:s0 tclass=file permissive=0 ---- time->Sun May 12 08:54:27 2024 type=AVC msg=audit(1715493267.232:133): avc: denied { execute } for pid=1325 comm="sdbootutil" name="systemd-pcrlock" dev="dm-0" ino=57169 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:init_exec_t:s0 tclass=file permissive=0 10:~ # Other denials for snapper_t are list in boo#1224120 for which I have local policy override. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1221771] New: error message: "gtk-update-icon-cache: The generated cache was invalid" caused by package zypp-gui
by bugzilla_noreply＠suse.com 28 Jun '24

28 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221771 Bug ID: 1221771 Summary: error message: "gtk-update-icon-cache: The generated cache was invalid" caused by package zypp-gui Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When installing different packages I see the following error message: gtk-update-icon-cache: The generated cache was invalid. warning: %triggerin(gtk3-tools-3.24.34-150400.3.6.1.x86_64) scriptlet failed, exit status 1 This happens after installing the package zypp-gui because such package installs some icons in /usr/share/icons/hicolor/16x16/places that have spaces in their name. The issue was fixed upstream in zypp-gui since version 0.2.0 therefore tumbleweed is not affected by this bug. But Leap 15.5 and 15.6 are. There are two possible ways to fix the issue in Leap: 1) upgrade zypp-gui to version 0.2.0 or later 2) modify the spec file in this way: %prep %autosetup +for i in data/icons/country/*\ * ; do mv "$i" ${i// /.} ; done %build -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1224808] New: dracut incorrectly modify btrfs compression level for /
by bugzilla_noreply＠suse.com 27 Jun '24

27 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224808 Bug ID: 1224808 Summary: dracut incorrectly modify btrfs compression level for / 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: fcrozat(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On a MicroOS Desktop system, I'm trying to enable btrfs compression on root fs. The change is made at /etc/fstab level. The initial fstab relevant line was: UUID=no_interest_here / btrfs ro 0 0 Changed to: UUID=no_interest_here / btrfs ro,compress=zstd:1 0 0 and then running transaction-update initrd to ensure dracut is run in the transactional system. However, the stored kernel cmdline by dracut becomes: dracut[I]: root=UUID=980c03f5-35f5-405d-8686-d51ec67c17b4 rootfstype=btrfs rootflags=rw,relatime,seclabel,compress=,ssd,discard=async,space_cache=v2,subvolid=774,subvol=/@/.snapshots/619/snapshot,subvol=@/.snapshots/619/snapshot compress parameter is being stripped. This is with dracut-059+suse.588.g528264be-1.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1224995] New: Native Firefox package on Plasma Wayland runs the KDE File Picker under XWayland, not respecting HDPI scaling
by bugzilla_noreply＠suse.com 27 Jun '24

27 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224995 Bug ID: 1224995 Summary: Native Firefox package on Plasma Wayland runs the KDE File Picker under XWayland, not respecting HDPI scaling Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: radicalite(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875025 --> https://bugzilla.suse.com/attachment.cgi?id=875025&action=edit Filepicker comparsion between Native Firefox on TW and Flatpak Firefox When using the file picker from the native Firefox package, the file picker runs in XWayland, this isn't noticeable on non HiDPI displays unless there's a HiDPI display connected, or are simply using a HiDPI screen as the only screen, then this becomes instantly noticeable. This behaviour isn't consistent with applications from the rest of the system (moving aside VLC, but the app itself runs entirely under XWayland by default...), as they run the file picker under Wayland, following the correct scaling setting. the Firefox flatpak also runs the file picker under Wayland correctly (via Portal). This behaviour also doesn't happen with the native Firefox package on TWGNOME, running the GTK file picker under Wayland with respect to scaling, so I assume this happens from the OpenSUSE KDE patches added to Firefox? Install is a fresh TWKDE install. Comparison in image Operating System: openSUSE Tumbleweed 20240520 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6267U CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® Iris® Graphics 550 Manufacturer: Apple Inc. Product Name: MacBookPro13,2 System Version: 1.0 Display config is 2560x1600@175%@60hz (Built-in Screen) set to left 1920x1080@100%@120hz (Acer Technologies VG242Y) set to right, set as primary display. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222533] New: Libreoffice needs 100% CPU for 3 minutes to open Lenovo compatibility matrix
by bugzilla_noreply＠suse.com 27 Jun '24

27 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222533 Bug ID: 1222533 Summary: Libreoffice needs 100% CPU for 3 minutes to open Lenovo compatibility matrix Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874156 --> https://bugzilla.suse.com/attachment.cgi?id=874156&action=edit perf record data for loading the file with native TW package Upstream: https://bugs.documentfoundation.org/show_bug.cgi?id=160595 Environment: OpenSUSE Tumbleweed 20240329, GNOME/X11, libreoffice-calc-24.2.2.2-1.2.x86_64 Offending file: Lenovo Accessories and Options Compatibility Matrix (OCM) https://download.lenovo.com/pccbbs/options_iso/ocm_apr_2024.xlsx (access via http://www.lenovo.com/accessoriesguide) Steps to reproduce: Download and open the file with calc. Results: Calc hangs with 100% CPU with "load document" progress bar at ~80%. It finishes after ~3 minutes. With the flatpak version of Libreoffice, opening the file takes only ~15s. "perf report" shows for the openSUSE native package: Samples: 520K of event 'cycles:P', Event count (approx.): 366840243651 Overhead Command Shared Object Symbol 49.69% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7a8 27.60% soffice.bin libglib-2.0.so.0.8000.0 [.] g_node_insert_before 2.49% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7ac 1.32% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7af 0.85% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7b7 0.43% soffice.bin libc.so.6 [.] malloc 0.27% soffice.bin libuno_cppu.so.3 [.] typelib_typedescriptionreference_equals 0.23% soffice.bin libc.so.6 [.] _int_free -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222156] New: After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 27 Jun '24

27 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 Bug ID: 1222156 Summary: After an upgrade the graphical interface no longer works Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: rm.canella(a)gmail.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On my HP 255 G5 Notebook PC, following "zypper dup --no-allow-vendor-change" (openSUSE-20231218-0) the system no longer starts in graphics mode. - I did some checks and the problem seems to be on the "radeonsi_dri" driver; The following error message appears in the dmesg: [ 84.119680] gnome-shell[1557]: segfault at 40 ip 00007ff2ca32b98d sp 00007ffe59c27170 error 4 in radeonsi_dri.so[7ff2c9c91000+1476000] likely on CPU 1 (core 1, socket 0) - Doing an lspci the video card is: 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R3 Graphics] (rev 40) - And the following is the output of the zypper info kernel-firmware-radeon command: Information for package kernel-firmware-radeon: ------------------------------------------------- Repository : Main Repository (OSS) Name : kernel-firmware-radeon Version: 20240322-1.1 Arch : noarch Vendor: openSUSE Installed Size: 3.3 MiB Installed : Yes (automatically) Status: up-to-date Source package : kernel-firmware-20240322-1.1.src Upstream URL: https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/ Summary : Kernel firmware files for Radeon graphics driver Description: This package contains compressed kernel firmware files for Radeon graphics driver. -- You are receiving this mail because: You are on the CC list for the bug.

1 38

[Bug 1224285] New: 6.9 broke pidfd
by bugzilla_noreply＠suse.com 26 Jun '24

26 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224285 Bug ID: 1224285 Summary: 6.9 broke pidfd 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… commit cb12fd8e0dabb9a1c8aef55a6a41e2c255fcdf4b Author: Christian Brauner <brauner(a)kernel.org> Date: Mon Feb 12 16:32:38 2024 +0100 pidfd: add pidfs Without the commit, lsof shows: systemd ... 59 [pidfd:899] With the commit: systemd ... 1187 pidfd For util-linux, its test fail with: > [ 125s] --- tests/expected/lsfd/column-name-pidfd 2024-05-06 07:20:54.655845940 +0000 > [ 125s] +++ tests/output/lsfd/column-name-pidfd 2024-05-15 01:04:15.406666666 +0000 > [ 125s] @@ -1,2 +1,2 @@ > [ 125s] -3 anon_inode:[pidfd] pid=1 comm= nspid=1 > [ 125s] +3 pidfd:[INODENUM] pidfd:[INODENUM] > [ 125s] pidfd:ASSOC,KNAME,NAME: 0 > [ 125s] lsfd: NAME and KNAME column: [02] pidfd ... FAILED (lsfd/column-name-pidfd) And: > [ 125s] --- tests/expected/lsfd/column-type-pidfd 2024-05-06 07:20:54.655845940 +0000 > [ 125s] +++ tests/output/lsfd/column-type-pidfd 2024-05-15 01:04:15.573333333 +0000 > [ 125s] @@ -1,2 +1,2 @@ > [ 125s] -3 UNKN pidfd > [ 125s] +3 REG REG > [ 125s] pidfd:ASSOC,STTYPE,TYPE: 0 > [ 125s] lsfd: TYPE and STTYPE column: [02] pidfd ... FAILED (lsfd/column-type-pidfd) -- You are receiving this mail because: You are on the CC list for the bug.

1 8