January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1219384] New: [Build 20240130] openQA test fails in openssl_fips_cipher
by bugzilla_noreply＠suse.com 16 May '24

16 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219384 Bug ID: 1219384 Summary: [Build 20240130] openQA test fails in openssl_fips_cipher Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3905406/modules/open ssl_fips_cipher/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openssl has split out the fips providers. Trying to use openssl with fips results in FATAL: Startup failure (dev note: apps_startup()) for openssl 40C7BD59537F0000:error:12800067:DSO support routines:dlfcn_load:could not load the shared library:crypto/dso/dso_dlfcn.c:118:filename(/usr/lib64/ossl-modules/fips.so): /usr/lib64/ossl-modules/fips.so: cannot open shared object file: No such file or directory 40C7BD59537F0000:error:12800067:DSO support routines:DSO_load:could not load the shared library:crypto/dso/dso_lib.c:152: 40C7BD59537F0000:error:07880025:common libcrypto routines:provider_init:reason(524325):crypto/provider_core.c:904:name=fips 40C7BD59537F0000:error:0700006D:configuration file routines:module_run:module initialization error:crypto/conf/conf_mod.c:276:module=providers, value=provider_sect retcode=-1 The fips pattern should be responsible to pull in the fips provider in this case openQA test in scenario microos-Tumbleweed-MicroOS-Image-x86_64-microos_fips@64bit fails in [openssl_fips_cipher](https://openqa.opensuse.org/tests/3905406/modules/open… ## Test suite description microos FIPS enablement and some FIPS specific tests. ## Reproducible Fails since (at least) Build [20231001](https://openqa.opensuse.org/tests/3612603) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217750] New: Nonfunctional brightness keys on Lenovo Slim 7 16" AMD
by bugzilla_noreply＠suse.com 15 May '24

15 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217750 Bug ID: 1217750 Summary: Nonfunctional brightness keys on Lenovo Slim 7 16" AMD Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: variable_valuables761(a)simplelogin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871117 --> https://bugzilla.suse.com/attachment.cgi?id=871117&action=edit Output of "brightnessctl -l" for Lenovo 16ARH7 It seems the brightness keys (Fn+F5,Fn+F6) do not work in the latest Tumbleweed KDE snapshot on the Lenovo Slim 7 16" AMD, 16ARH7, 82UX0001US (and this same model is called Yoga outside the United States). It seems the internal display's brightness values are bugged and show up as 0 and "0 (-2147483648%)" in brightnessctl rather than something within the expected range. I've attached the output of "brightnessctl -l", which shows the display and some of the keyboard/charging LEDs on the laptop. Glad to provide any other logs that could be helpful. Hope this is the right place to report this. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1217840] New: rpmlint does not check anymore for packages built without distro %{optflags}
by bugzilla_noreply＠suse.com 15 May '24

15 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217840 Bug ID: 1217840 Summary: rpmlint does not check anymore for packages built without distro %{optflags} 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: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: dimstar(a)opensuse.org, dmueller(a)suse.com, fvogt(a)suse.com Target Milestone: --- Found By: --- Blocker: --- At some point, rpmlint checked for packages built without distro %{optflags}. This is not the case anymore. It was added upstream in https://github.com/rpm-software-management/rpmlint/issues/341 So, this should be a matter of setting MandatoryOptflags to the right settings? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217776] New: rpm-build pulling Qt6 dependency without need
by bugzilla_noreply＠suse.com 13 May '24

13 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217776 Bug ID: 1217776 Summary: rpm-build pulling Qt6 dependency without need Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- ``` zypper in obs-service-source_validator Loading repository data... Reading installed packages... [TechPreview] $ZYPP_SINGLE_RPMTRANS=1 : New rpm install backend is enabled If you find any bugs or issues please let us know: https://bugzilla.opensuse.org/ Component: libzypp (or zypper) And please attach the /var/log/zypper.log to the bug report. Resolving package dependencies... The following 15 NEW packages are going to be installed: gcc13-c++ gcc-c++ libqt5-qtdeclarative-tools libQt6JsonRpc6 libQt6LanguageServer6 libQt6QmlCompiler6 libstdc++6-devel-gcc13 obs-service-source_validator python-rpm-packaging qml-autoreqprov qt6-base-common-devel qt6-declarative-tools qt6-macros rpm-build rpm-build-perl 15 new packages to install. Overall download size: 29,6 MiB. Already cached: 0 B. After the operation, additional 107,8 MiB will be used. ``` I tracked this down to `zypper in rpm-build` which then triggers: ``` rpm -q --requires libQt6Qml6 (qml-autoreqprov if rpm-build) ``` on some Qt devel package I could understand a dependency like this. but for a library package this feels excessive. source_validator/rpmbuild should not build a Qt6 devel stack. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218678] New: VUL-0: CVE-2022-36763: EDK2 is susceptible to a vulnerability in the Tcg2MeasureGptTable() function, allowing a user to trigger a heap buffer overflow via a local network. Successful exploitation of this vulnerability may result in a compromise of co ...
by bugzilla_noreply＠suse.com 13 May '24

13 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1218678 Bug ID: 1218678 Summary: VUL-0: CVE-2022-36763: EDK2 is susceptible to a vulnerability in the Tcg2MeasureGptTable() function, allowing a user to trigger a heap buffer overflow via a local network. Successful exploitation of this vulnerability may result in a compromise of co ... Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/390488/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: guillaume.gardet(a)opensuse.org Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: stoyan.manolov(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- EDK2 is susceptible to a vulnerability in the Tcg2MeasureGptTable() function, allowing a user to trigger a heap buffer overflow via a local network. Successful exploitation of this vulnerability may result in a compromise of confidentiality, integrity, and/or availability. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36763 https://www.cve.org/CVERecord?id=CVE-2022-36763 https://github.com/tianocore/edk2/security/advisories/GHSA-xvv8-66cq-prwr -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1218422] New: Can't build hyprland plugins due to improper header locations
by bugzilla_noreply＠suse.com 11 May '24

11 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1218422 Bug ID: 1218422 Summary: Can't build hyprland plugins due to improper header locations Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: johndoe1352460(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I cannot build the plugins for Hyprland due to the improper locations of headers. When building hyprbars for hyprland it expects <wlr/util/transform.h> but the full path of the file is /usr/include/hyprland/wlroots. I'm guessing it expects it to be /usr/include/hyprland/wlr with the pkgconfig parameter inclduing -I/usr/include/hyprland What I did to fix this issue is create a symlink /usr/include/hyprland/wlr that points to /usr/include/hyprland/wlroots and add -I${includedir}/hyprland to the cflags in /usr/share/pkgconfig/hyprland.pc After I do that the hyprbars plugin builds just fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1216042] New: Kernels fail to build in Kernel:stable:Backport
by bugzilla_noreply＠suse.com 09 May '24

09 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1216042 Bug ID: 1216042 Summary: Kernels fail to build in Kernel:stable:Backport Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The recently updated binutils in openSUSE_Leap_15.4 generate new DT_ tags which dwarves does not know about: [ 1122s] Unsupported DW_TAG_unspecified_type(0x3b) [ 1122s] Encountered error while encoding BTF. osc branch --nodevelproject openSUSE:Factory dwarves Kernel:stable:Backport would probably solve this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1217232] New: bees does not build on Leap 15.6
by bugzilla_noreply＠suse.com 09 May '24

09 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217232 Bug ID: 1217232 Summary: bees does not build on Leap 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello bees does not build on Leap 15.6 this should be fixed before Beta (Feb 2023) https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6 Build log from Leap 15.6 https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… [ 23s] /usr/include/linux/btrfs.h:667:43: error: flexible array member 'btrfs_ioctl_same_args::info' not at end of 'struct crucible::BtrfsExtentSame' [ 23s] struct btrfs_ioctl_same_extent_info info[]; [ 23s] ^ [ 23s] In file included from extentwalker.cc:5:0: [ 23s] ../include/crucible/fs.h:40:7: note: next member 'int crucible::BtrfsExtentSame::m_fd' declared here [ 23s] int m_fd; [ 23s] ^~~~ [ 23s] ../include/crucible/fs.h:34:9: note: in the definition of 'struct crucible::BtrfsExtentSame' [ 23s] struct BtrfsExtentSame : public btrfs_ioctl_same_args { [ 23s] ^~~~~~~~~~~~~~~ [ 23s] In file included from ../include/crucible/btrfs.h:17:0, [ 23s] from ../include/crucible/fs.h:11, [ 23s] from extentwalker.cc:5: [ 23s] /usr/include/linux/btrfs.h:687:12: error: flexible array member 'btrfs_data_container::val' not at end of 'struct crucible::BtrfsDataContainer' [ 23s] __u64 val[]; /* out */ [ 23s] ^ [ 23s] In file included from extentwalker.cc:5:0: [ 23s] ../include/crucible/fs.h:66:19: note: next member 'std::vector<unsigned char> crucible::BtrfsDataContainer::m_data' declared here [ 23s] vector<uint8_t> m_data; [ 23s] ^~~~~~ [ 23s] ../include/crucible/fs.h:56:9: note: in the definition of 'struct crucible::BtrfsDataContainer' [ 23s] struct BtrfsDataContainer : public btrfs_data_container { [ 23s] ^~~~~~~~~~~~~~~~~~ [ 23s] In file included from ../include/crucible/fs.h:14:0, [ 23s] from extentwalker.cc:5: [ 23s] /usr/include/linux/fiemap.h:37:34: error: flexible array member 'fiemap::fm_extents' not at end of 'struct crucible::Fiemap' [ 23s] struct fiemap_extent fm_extents[]; /* array of mapped extents (out) */ [ 23s] ^ [ 23s] In file included from extentwalker.cc:5:0: [ 23s] ../include/crucible/fs.h:155:24: note: next member 'std::vector<crucible::FiemapExtent> crucible::Fiemap::m_extents' declared here [ 23s] vector<FiemapExtent> m_extents; [ 23s] ^~~~~~~~~ [ 23s] ../include/crucible/fs.h:144:9: note: in the definition of 'struct crucible::Fiemap' [ 23s] struct Fiemap : public fiemap { [ 23s] ^~~~~~ [ 23s] make[1]: *** [Makefile:48: extentwalker.o] Error 1 [ 23s] make[1]: *** Waiting for unfinished jobs.... [ 23s] In file included from ../include/crucible/btrfs.h:17:0, [ 23s] from ../include/crucible/fs.h:11, [ 23s] from fs.cc:1: [ 23s] /usr/include/linux/btrfs.h:667:43: error: flexible array member 'btrfs_ioctl_same_args::info' not at end of 'struct crucible::BtrfsExtentSame' [ 23s] struct btrfs_ioctl_same_extent_info info[]; [ 23s] ^ [ 23s] In file included from fs.cc:1:0: [ 23s] ../include/crucible/fs.h:40:7: note: next member 'int crucible::BtrfsExtentSame::m_fd' declared here [ 23s] int m_fd; [ 23s] ^~~~ [ 23s] ../include/crucible/fs.h:34:9: note: in the definition of 'struct crucible::BtrfsExtentSame' [ 23s] struct BtrfsExtentSame : public btrfs_ioctl_same_args { [ 23s] ^~~~~~~~~~~~~~~ [ 23s] In file included from ../include/crucible/btrfs.h:17:0, [ 23s] from ../include/crucible/fs.h:11, [ 23s] from fs.cc:1: [ 23s] /usr/include/linux/btrfs.h:687:12: error: flexible array member 'btrfs_data_container::val' not at end of 'struct crucible::BtrfsDataContainer' [ 23s] __u64 val[]; /* out */ [ 23s] ^ [ 23s] In file included from fs.cc:1:0: [ 23s] ../include/crucible/fs.h:66:19: note: next member 'std::vector<unsigned char> crucible::BtrfsDataContainer::m_data' declared here [ 23s] vector<uint8_t> m_data; [ 23s] ^~~~~~ [ 23s] ../include/crucible/fs.h:56:9: note: in the definition of 'struct crucible::BtrfsDataContainer' [ 23s] struct BtrfsDataContainer : public btrfs_data_container { [ 23s] ^~~~~~~~~~~~~~~~~~ [ 23s] In file included from ../include/crucible/fs.h:14:0, [ 23s] from fs.cc:1: [ 23s] /usr/include/linux/fiemap.h:37:34: error: flexible array member 'fiemap::fm_extents' not at end of 'struct crucible::Fiemap' [ 23s] struct fiemap_extent fm_extents[]; /* array of mapped extents (out) */ [ 23s] ^ [ 23s] In file included from fs.cc:1:0: [ 23s] ../include/crucible/fs.h:155:24: note: next member 'std::vector<crucible::FiemapExtent> crucible::Fiemap::m_extents' declared here [ 23s] vector<FiemapExtent> m_extents; [ 23s] ^~~~~~~~~ [ 23s] ../include/crucible/fs.h:144:9: note: in the definition of 'struct crucible::Fiemap' [ 23s] struct Fiemap : public fiemap { [ 23s] ^~~~~~ [ 23s] make[1]: *** [Makefile:48: fs.o] Error 1 [ 24s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/bees-0.7/lib' [ 24s] make: *** [Makefile:34: lib] Error 2 [ 24s] error: Bad exit status from /var/tmp/rpm-tmp.rcToPR (%build) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1216950] New: openssl-3 should offer ktls capability but has OPENSSL_NO_KTLS enabled
by bugzilla_noreply＠suse.com 07 May '24

07 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1216950 Bug ID: 1216950 Summary: openssl-3 should offer ktls capability but has OPENSSL_NO_KTLS enabled Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: bruno(a)ioda-net.ch QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I've been trying to benefit of ktls support offered by the kernel (6.5.9-1-default as time reporting), but none of the experimentation to implement ktls failed. This is due because OpenSSL 3.1.4 24 has OPENSSL_NO_KTLS defined. Would it be possible to review that parameter, and offer developer and user the same capability that other operating system offer (Fedora for example) ? Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1217299] New: zypp:plugins/zypper-changelog-plugin: Bug repodata is now using zstd compression
by bugzilla_noreply＠suse.com 06 May '24

06 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217299 Bug ID: 1217299 Summary: zypp:plugins/zypper-changelog-plugin: Bug repodata is now using zstd compression Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: zbalogh(a)suse.com Reporter: ianmepham(a)gmail.com QA Contact: screening-team-bugs(a)suse.de CC: nadvornik(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I'm running Tumbleweed x86_64, all up-to-date as of 18 Nov 2023 with snapshot 20231116. The package zypper-changelog-plugin I'm using is version 0.3-1.2. Recently zypper-changelog has stopped working with no error messages nor any other output given. I've tested both trying to download the changelog for a single package, such as with zypper-changelog --package vim, as well as the changelogs for any upcoming system updates with zypper-changelog ‐‐update I understand that the repodata is now compressed with zstd rather than gz as mentioned in the Factory mailing list here https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… I tested modifying zypper-changelog to accept both gz and zstd compressed repodata so it would work with both the official repos and any other repos which still use gz compression. Please keep in mind that I've only tested this in Tumbleweed. It also requires using zstdcat in place of zcat. Fortunately zstdcat also supports gz compression. The version of zstdcat I tested this with is 1.5.5-3.5. Here's a diff of the changes I've tested to give you an idea of what I mean comparing the current version 0.3-1.2 zypper-changelog and a modified test version: 147c147 < if file.endswith("primary.xml.gz"): --- > if file.endswith(("primary.xml.zst", "primary.xml.gz")): 172c172 < zcat_process = subprocess.Popen(["zcat", --- > zstdcat_process = subprocess.Popen(["zstdcat", 176c176 < stdout_value, stderr_value = zcat_process.communicate() --- > stdout_value, stderr_value = zstdcat_process.communicate() I understand that using a tuple is considered to be more pythonic, but I'm not sure if some may find it more legible to do something like this: if file.endswith("primary.xml.zst") or if file.endswith("primary.xml.gz"): I've not really done stuff like this before so my sincere apologies if I've picked the wrong option or made a mistake in this bug report. I'm also just an amateur with Python too so I may have easily overlooked something. Please ask if you need any more information. Thank you for your time and for such a useful tool. -- You are receiving this mail because: You are on the CC list for the bug.

1 2