May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225779] New: gtest.pc injects a bogus include directory which breaks libstdc++ headers
by bugzilla_noreply＠suse.com 01 Jul '24

01 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225779 Bug ID: 1225779 Summary: gtest.pc injects a bogus include directory which breaks libstdc++ headers Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- > pkg-config --cflags gtest -DGTEST_HAS_PTHREAD=1 -lpthread -I/usr/lib64/pkgconfig/../../include The `-I` is changed to `-isystem` by a downstream build system (Google Ninja) When calling g++-13 with this flag on a file which includes `<cstdlib>`, i'm getting a confusing build error: In file included from ../../v8/include/v8.h:21, from ../../third_party/electron_node/src/node.h:79, from ../../third_party/electron_node/src/api/async_resource.cc:1: /usr/include/c++/13/cstdlib:79:15: fatal error: stdlib.h: No such file or directory 79 | #include_next <stdlib.h> | ^~~~~~~~~~ This is gtest-1.10.0-1.10.x86_64 The problem happens on both 15.5 and 15.6, does not happen on Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1220085] New: Data races reported by KCSAN on s390x
by bugzilla_noreply＠suse.com 01 Jul '24

01 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1220085 Bug ID: 1220085 Summary: Data races reported by KCSAN on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: miroslav.franc(a)suse.com Reporter: miroslav.franc(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ihno(a)suse.com, marcela.maslanova(a)suse.com, ro(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 872851 --> https://bugzilla.suse.com/attachment.cgi?id=872851&action=edit dmesg log from s390x VM z15 factory KCSAN enabled kernel* on s390x reports a lot of data races. See the dmesg log for details. * https://download.suse.de/ibs/home:/mfranc:/branches:/SUSE:/Factory:/Head:/k… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1225174] New: conflicto actualizacion
by bugzilla_noreply＠suse.com 30 Jun '24

30 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225174 Bug ID: 1225174 Summary: conflicto actualizacion Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: allanvejar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- <html>Ha fallado la resolución de dependencias:<br/><br/>el elemento tlp-1.6.1-2.1.noarch que se va a instalar tiene un conflicto con tuned, que proporciona el elemento tuned-2.22.1.2+git.86ac977-3.1.noarch instalado</html> -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 1222993] New: maliit-keyboard should have libqt5-qtwayland as dependency
by bugzilla_noreply＠suse.com 30 Jun '24

30 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222993 Bug ID: 1222993 Summary: maliit-keyboard should have libqt5-qtwayland as dependency Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: suse.com(a)s.bjoern-tantau.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I just installed maliit-keyboard and selected it in KDE as my virtual keyboard. But it would not appear. I fixed it by installing libqt5-qtwayland. So I guess this should be a dependency of maliit. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219521] New: dmd compiler cannot find standard library
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1219521 Bug ID: 1219521 Summary: dmd compiler cannot find standard library 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: andrea.manzini(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- To reproduce on a Tumbleweed installation: # zypper in dmd dub sudo zypper in dub dmd Loading repository data... Reading installed packages... Resolving package dependencies... The following recommended package was automatically selected: phobos-devel The following 4 NEW packages are going to be installed: dmd dub libphobos2-0_105 phobos-devel # cat > main.d import std.stdio; void main() { writeln("Hello, world"); } # dmd main.d /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: cannot find -lphobos2: No such file or directory collect2: error: ld returned 1 exit status Error: linker exited with status 1 as a workaround, installing # zypper in phobos-devel-static the main executable gets created -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225278] New: Firefox's Search Provider doesn't work on GNOME (and possibly other DEs)
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225278 Bug ID: 1225278 Summary: Firefox's Search Provider doesn't work on GNOME (and possibly other DEs) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: ant.romano(a)pm.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I'm using openSUSE Tumbleweed w/ snapshot 20240523, Firefox 126.0 (.rpm) and GNOME 46.1. On Firefox, the `browser.gnome-search-provider.enabled` parameter is set to true, while "Firefox" is listed as an enabled search provider on GNOME (Settings -> Search). The "GNOME shell integration" extension is also enabled, although I'm not sure it is required. Despite my premises, Firefox simply does not appear as a search provider when trying to search through GNOME. I've tried searching for solutions or at least for people with the same issue and found out this article from a Fedora: https://mastransky.wordpress.com/2023/10/13/q3-firefox-linux-update/ although I have no idea how to correctly follow the steps he described. I can only state that the Mozilla Firefox Search Provider service indeed is _not_ "Activatable". -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[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