November 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213486] New: [Build 44.3] openQA test fails in fanotify14
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1213486 Bug ID: 1213486 Summary: [Build 44.3] openQA test fails in fanotify14 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/3439183/modules/fano tify14/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-15.4-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@64bit_virtio fails in [fanotify14](https://openqa.opensuse.org/tests/3439183/modules/fanotify14/st… ## Test suite description ## Reproducible Fails since (at least) Build [44.2](https://openqa.opensuse.org/tests/3438422) ## Expected result Last good: [44.1](https://openqa.opensuse.org/tests/3436580) (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 8

[Bug 1216121] New: rust1.7{1,2,3} fail to build with newest binutils
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1216121 Bug ID: 1216121 Summary: rust1.7{1,2,3} fail to build with newest binutils Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Keywords: build Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: burnus(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: william.brown(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I have no idea why rust1.7{1,2,3} fails, I just note that with the new binutils https://build.opensuse.org/request/show/1113885 as shown below. The current error message does not point to anything obvious with regards to binutils - but looks more like a generic Rust build issue. But it as it does compile on opensuse:Factory, it must have something to do with binutils. The fails is: [ 191s] Finished release [optimized] target(s) in 1m 54s [ 192s] Building LLD for x86_64-unknown-linux-gnu ... [ 192s] CMake Deprecation Warning at /home/abuild/rpmbuild/BUILD/rustc-1.73.0-src/src/llvm-project/cmake/Modules/CMakePolicy.cmake:6 (cmake_policy): [ 192s] The OLD behavior for policy CMP0114 will be removed from a future version [ 192s] of CMake. [ 192s] [ 192s] The cmake-policies(7) manual explains that the OLD behaviors of all [ 192s] policies are deprecated and that a policy should be set to OLD only under [ 192s] specific short-term circumstances. Projects should be ported to the NEW [ 192s] behavior and not rely on setting a policy to OLD. [ 192s] Call Stack (most recent call first): [ 192s] CMakeLists.txt:6 (include) [ 192s] [ 192s] [ 192s] -- The C compiler identification is GNU 13.2.1 [ 192s] -- The CXX compiler identification is GNU 13.2.1 [ 192s] -- Detecting C compiler ABI info [ 192s] -- Detecting C compiler ABI info - done ... [ 194s] -- Configuring done (2.2s) [ 194s] CMake Error at /usr/lib64/cmake/llvm/AddLLVM.cmake:714 (target_link_libraries): [ 194s] Target "lldELF" links to: [ 194s] [ 194s] zstd::libzstd_static [ 194s] [ 194s] but the target was not found. Possible reasons include: [ 194s] [ 194s] * There is a typo in the target name. [ 194s] * A find_package call is missing for an IMPORTED target. [ 194s] * An ALIAS target is missing. [ 194s] [ 194s] Call Stack (most recent call first): [ 194s] cmake/modules/AddLLD.cmake:13 (llvm_add_library) [ 194s] ELF/CMakeLists.txt:21 (add_lld_library) [ 194s] [ 194s] [ 194s] -- Generating done (0.0s) [ 194s] CMake Warning: [ 194s] Manually-specified variables were not used by the project: [ 194s] [ 194s] CMAKE_ASM_COMPILER [ 194s] [ 194s] [ 194s] CMake Generate step failed. Build files cannot be regenerated correctly. [ 194s] thread 'main' panicked at /home/abuild/rpmbuild/BUILD/rustc-1.73.0-src/vendor/cmake/src/lib.rs:975:5: [ 194s] [ 194s] command did not execute successfully, got: exit status: 1 [ 194s] [ 194s] build script failed, must exit now [ 194s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 194s] finished in 2.256 seconds [ 194s] Build completed unsuccessfully in 0:02:30 [ 194s] error: Bad exit status from /var/tmp/rpm-tmp.YhjGx1 (%build) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215937] New: VUL-0: CVE-2023-43907: optipng: global buffer overflow via the 'buffer' variable at gifread.c
by bugzilla_noreply＠suse.com 03 Sep '24

03 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1215937 Bug ID: 1215937 Summary: VUL-0: CVE-2023-43907: optipng: global buffer overflow via the 'buffer' variable at gifread.c Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/380479/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: pgajdos(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: gabriele.sonnu(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- OptiPNG v0.7.7 was discovered to contain a global buffer overflow via the 'buffer' variable at gifread.c. References: https://github.com/Frank-Z7/z-vulnerabilitys/blob/main/optipng-global-buffe… http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43907 -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1215641] New: XDG Portal File Picker not working on latest snapshot
by bugzilla_noreply＠suse.com 02 Sep '24

02 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1215641 Bug ID: 1215641 Summary: XDG Portal File Picker not working on latest snapshot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs(a)suse.de Reporter: socvirnyl.estela(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Snapshot 20230921 has a bug where a user cannot open a filechooser/filepicker. A snippet of the log through `journalctl -f` is shown below: ``` Sep 24 12:29:37 sentient-slate firefox-bin[3253]: Server is missing xdg_foreign support Sep 24 12:29:37 sentient-slate firefox-bin[3253]: Failed to export handle, could not set transient for Sep 24 12:29:37 sentient-slate firefox-bin[3253]: Can't open portal file chooser: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.FileChooser” on object at path /org/freedesktop/portal/desktop ``` I have to rollback for now to a previous snapshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1213162] New: kf.kio.core: Invalid URL: QUrl("//@/<smtp>.xfb")
by bugzilla_noreply＠suse.com 31 Aug '24

31 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1213162 Bug ID: 1213162 Summary: kf.kio.core: Invalid URL: QUrl("//@/<smtp>.xfb") 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: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting on 06/272023, probably after installing Tumbleweed snapshot 20230625, I no longer can invite people using korganizer, if the invitation mail address has a format like "lastname, firstname" <opensuse(a)mike.franken.de> "firstname lastname" <opensuse(a)mike.franken.de> "anything" <opensuse(a)mike.franken.de> Using such an address produces the following warning messages in my log: kontact[4212]: kf.kio.core: Invalid URL: QUrl("//@/opensuse@mike.franken.de.xfb") kontact[4212]: kf.kio.core: Invalid URL: QUrl("//@/opensuse@mike.franken.de.ifb") kontact[4212]: kf.kio.core: Invalid URL: QUrl("//@/opensuse@mike.franken.de.vfb") No invitation mail is sent in this case. Using just <opensuse(a)mike.franken.de> works ok. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217710] New: icecream fails to compile remotely, falls back to local compilation
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1217710 Bug ID: 1217710 Summary: icecream fails to compile remotely, falls back to local compilation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jimis(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Icecream fails to find libraries, when executing cc1plus on the remote host. On the remote host we see: cc1plus: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory This causes all compilations to fail and re-run locally. The reason is that the binary is linked to hardware-dependent shared libraries under `/lib64/glibc-hwcaps` directory, and icecream-create-env fails to transfer the generic versions of the libraries too. $ ldd /usr/lib64/gcc/x86_64-suse-linux/13/cc1plus | grep hwcap libz.so.1 => /lib64/glibc-hwcaps/x86-64-v3/libz.so.1.3 (0x00007f8f2020e000) libzstd.so.1 => /lib64/glibc-hwcaps/x86-64-v3/libzstd.so.1.5.5 (0x00007f8f20161000) The fix is already upstream, but icecream hasn't had a release in almost 2 years. Could you please cherry-pick the fix and make icecream usable again? https://github.com/icecc/icecream/pull/602 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1214167] New: OBS: nothing provides lzip
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1214167 Bug ID: 1214167 Summary: OBS: nothing provides lzip Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: manfred99(a)gmx.ch QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- In the package rcs (https://build.opensuse.org/package/show/devel:tools:scm/rcs) there is a build error for Leap 15.4 and Leap 15.5: "unresolvable: nothing provides lzip" Although both distributions provide lzip, and the required "BuildRequires: lzip" is given in the spec file. The issue seems to be, that OBS builds against a subset of packages (drawing by Jan Engelhardt): SLE-15.5-Base `-- SLE-15.5-Update <- devel:tools:scm is pointing here `-- SLE-15.5-Backports <- lzip is available from here `-- Leap:15.5 `-- Leap:15.5:Update Which explains why this can not work. But there are software projects (such as RCS) which only distribute lzip-compressed release tarballs. IMHO such a basic, widely used compression tool should be available in SLE-15.5-Base or SLE-15.5-Update, so that OBS can use it to build packages. Alternatively there should be a mechanism to provide essential building blocks to OBS (outside of SLE-.*), so that OBS can do its duty. At the moment there is no possibility to build software which provides lzip-tarballs. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215219] New: xdg-utils: cannot open https/https urls, malformed character
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1215219 Bug ID: 1215219 Summary: xdg-utils: cannot open https/https urls, malformed character Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: gianmarco.torti(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- package installed info: Information for package xdg-utils: ---------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : xdg-utils Version : 1.1.3+20230830-1.1 Arch : noarch Vendor : openSUSE Installed Size : 348.4 KiB Installed : Yes Status : up-to-date Source package : xdg-utils-1.1.3+20230830-1.1.src Upstream URL : https://www.freedesktop.org/wiki/Software/xdg-utils/ with this version is not possible to open any url with http / https prefix , this is the error: xdg-open https://www.kernel.org start : This command cannot be run due to the error: The system cannot find the file specified. At line:1 char:1 + start https\www.kernel.org + ~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Start-Process], InvalidOperationException + FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand NOTE: opensuse tumbleweed installed in WSL subsystem with older version xdg-utils-1.1.3+20210805-2.3.noarch there are no problems -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217312] New: Google websites do not work in Firefox
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1217312 Bug ID: 1217312 Summary: Google websites do not work in Firefox 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: bart.vanassche+novell(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since more than a year, multiple Google websites, e.g. Google Search, Google Docs and Gmail, do not work well with the Firefox software included with openSUSE Tumbleweed. It often happens that loading one of these websites stalls. Logging in to a Google account doesn't work at all. I don't see this issue if I download Firefox binaries from the Mozilla website and load my existing profile (firefox/firefox -profileManager). Does this perhaps mean that there is a problem with changes made to the Firefox software that is available from openSUSE? Tumbleweed version: $ rpm -qf /etc/issue.net openSUSE-release-20231117-2596.1.x86_64 Firefox versions: $ rpm -q MozillaFirefox MozillaFirefox-119.0.1-1.1.x86_64 Binary downloaded from the Mozilla website: firefox-119.0.1.tar.bz2 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1216393] New: Electron/Chromium can't render h264 in webrtc
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1216393 Bug ID: 1216393 Summary: Electron/Chromium can't render h264 in webrtc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bjorn.bidar(a)thaodan.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- * Description: When trying to stream WebRTC with h264 in Electron/Chromium the screen stays black even thou OpenH264 is correctly installed. * How to reproduce: 1. Open Chromium 2. Open https://mozilla.github.io/webrtc-landing/pc_test_no_h264.html 3. Click test ** Another option is to use: https://mozilla.github.io/webrtc-landing/pc_test.html 1. Tick require h264 2. Start the video, wait 3. The message now should be "No H264 found in the offer!!!" * Background and reason for the bug: openSUSE builds both Chromium and Electron in a way that h264 isn't compiled into both packages but loaded using the Openh264 provided by openSUSE but blessed by Cisco. However Chromium has to use some of the openh264 to build even thou it's not used during runtime. The gyp option `rtc_use_h264` has be set to true and third_party/openh264 has to be included in the tarball (already the case in the upstream third_party/openh264 tarball). This is due webrtc using openh264 headers in third_party/webrtc/modules/video_coding/codecs/h264/h264_encoder_impl.cc -- You are receiving this mail because: You are on the CC list for the bug.

1 1