July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1227506] New: freshclam is not quiet anymore
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227506 Bug ID: 1227506 Summary: freshclam is not quiet anymore 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: bjoernv(a)arcor.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since the latest snapshots (tested on TW 20240704) freshclam ignores the "--quiet" option. This is annoying if freshclam is handled via cronjob. # freshclam ClamAV update process started at Mon Jul 8 13:28:05 2024 daily.cld database is up-to-date (version: 27330, sigs: 2064003, f-level: 90, builder: raynman) main.cld database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) bytecode.cld database is up-to-date (version: 335, sigs: 86, f-level: 90, builder: raynman) # freshclam --quiet ClamAV update process started at Mon Jul 8 13:28:09 2024 daily.cld database is up-to-date (version: 27330, sigs: 2064003, f-level: 90, builder: raynman) main.cld database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) bytecode.cld database is up-to-date (version: 335, sigs: 86, f-level: 90, builder: raynman) # rpm -q libfreshclam3 clamav libfreshclam3-1.3.1-1.1.x86_64 clamav-1.3.1-1.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228221] New: The pcsc-lite-devel-32bit package is missing
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228221 Bug ID: 1228221 Summary: The pcsc-lite-devel-32bit package is missing Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: fgouget(a)codeweavers.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The pcsc-lite-devel-32bit package is missing in openSUSE15.6: # zypper install pcsc-lite-devel-32bit Loading repository data... Reading installed packages... Package 'pcsc-lite-devel-32bit' not found. Resolving package dependencies... Nothing to do. Wine uses this package to allow 32-bit Windows applications to access smart cards: https://gitlab.winehq.org/wine/wine/-/blob/master/configure.ac?ref_type=hea… -- 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 1222170] New: build.opensuse.org returns 422 (Unprocessable Content), possibly due to UTF-8
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1222170 Bug ID: 1222170 Summary: build.opensuse.org returns 422 (Unprocessable Content), possibly due to UTF-8 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: piotrekd(a)vivaldi.net QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Hello, I registered a new (open)SUSE account. I can use it to log into build.opensuse, but after I do so, the website becomes unusable because trying to open it returns only the HTTP error 422 (Unprocessable Content) to the browser (no special page like the 404 one). I *guess* this may be caused by the non-ASCII (UTF-8) “ł” character that appears in my user name. The registration form at https://idp-portal.suse.com allowed me to use it, so I did. That site works just fine when I log in. BugZilla seems to work OK too. The openSUSE Open Build Service does not, however. Kind regards. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1226523] New: cnf suggests wrong package installation
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226523 Bug ID: 1226523 Summary: cnf suggests wrong package installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: smbd.jp(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- ``` $ rpm -q cnf cnf-0.6.0~0-3.4.x86_64 $ rpm -q gettext-runtime gettext-runtime-0.22.5-5.0.2.1.sr20240605.x86_64 ``` ``` $ cnf envsubst The program 'envsubst' can be found in following packages: * gettext-runtime [ path: /usr/bin/envsubst, repository: openSUSE:repo-oss ] * gettext-runtime-mini [ path: /usr/bin/envsubst, repository: openSUSE:repo-oss ] * envsubst [ path: /usr/bin/envsubst, repository: openSUSE:update-slowroll ] * envsubst [ path: /usr/bin/envsubst, repository: openSUSE:update-slowroll ] * envsubst-mini [ path: /usr/bin/envsubst, repository: openSUSE:update-slowroll ] * envsubst-mini [ path: /usr/bin/envsubst, repository: openSUSE:update-slowroll ] Try installing with: sudo zypper install <selected_package> ``` But gettext-runtime does not have envsubst. In the first place, gettext-runtime is already installed. ``` $ rpm -q gettext-runtime gettext-runtime-0.22.5-5.0.2.1.sr20240605.x86_64 $ rpm -ql gettext-runtime | grep envsubst $ ``` And why envsubst and envsubst-mini are shown twice, even though they are in the same repository? supplement: ``` $ cat /etc/zypp/repos.d/openSUSE:repo-oss.repo [openSUSE:repo-oss] name=repo-oss enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/slowroll/repo/oss service=openSUSE $ cat /etc/zypp/repos.d/openSUSE:update-slowroll.repo [openSUSE:update-slowroll] name=update-slowroll enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/update/slowroll/repo/oss priority=80 service=openSUSE ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1227215] New: Tight binding of php to apache
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227215 Bug ID: 1227215 Summary: Tight binding of php to apache 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: dead_mozay(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Why was this done? https://build.opensuse.org/projects/devel:languages:php/packages/php8/files… >>>Requires: group(www) >>>Requires: user(wwwrun) >>>%attr(0755, %{apache_user}, root) %dir %{_localstatedir}/lib/%{php_name} >>>%attr(0755, %{apache_user}, root) %dir %{_localstatedir}/lib/%{php_name}/sessions For nginx users, this constantly overwrites the rights to the /var/lib/php8 directory and the files in it -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222752] New: ugrep: build results depend on CPU
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1222752 Bug ID: 1222752 Summary: ugrep: build results depend on CPU Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: Andreas.Stieger(a)gmx.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1100677 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our ugrep binaries depend on the build machine CPU again. It seems SR 1166721 reverted my previous SR 818786 related: https://github.com/Genivia/ugrep/pull/50 CPU march=native ; partial fix The buildroot diff shows +++ /home/abuild/rpmbuild/BUILD.unsorted/ugrep-5.1.4/Makefile @@ -327,9 +327,9 @@ SED = /usr/bin/sed SET_MAKE = SHELL = /usr/bin/bash -SIMD_AVX2_FLAGS = -mavx2 +SIMD_AVX2_FLAGS = SIMD_AVX512BW_FLAGS = -SIMD_FLAGS = -msse2 -DHAVE_AVX2 +SIMD_FLAGS = -msse2 -DHAVE_SSE2 There are multiple ways to solve that: - never use AVX2 (as before) - always use AVX2 - detect AVX2 at runtime instead of compile-time -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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

[Bug 1218303] New: VUL-0: CVE-2023-6704: libavif,chromium,ungoogled-chromium: use after free in libavif
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1218303 Bug ID: 1218303 Summary: VUL-0: CVE-2023-6704: libavif,chromium,ungoogled-chromium: use after free in libavif Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: aaronpuchert(a)alice-dsl.net, andrea.mattiazzo(a)suse.com, Andreas.Stieger(a)gmx.de, gmbr3(a)opensuse.org, security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- It was reported that libavif before 1.0.3, and as bundled in Chromium, contained a use-after-free bug. colorProperties could be pointing to a dangling pointer if findAlphaItem() resizes the meta.items array. Also bundled in chromium, see bug 1218048 References: https://github.com/AOMediaCodec/libavif/pull/1808 https://github.com/AOMediaCodec/libavif/commit/b984f48be99b41405cb4a7d44380… https://github.com/AOMediaCodec/libavif/releases/tag/v1.0.3 https://bugs.chromium.org/p/chromium/issues/detail?id=1504792 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1227332] New: chromium/chrome wrapper causes library issues (symbol lookup error)
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227332 Bug ID: 1227332 Summary: chromium/chrome wrapper causes library issues (symbol lookup error) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs(a)suse.de Reporter: S48GS(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Exact same as https://bugzilla.redhat.com/show_bug.cgi?id=2277228 But they say it fixed in 124+ when im on latest Chrome and Chromium(125+) and it not fixed. Context is openSUSE Tumbleweed. (I show bug for Chromium, but it exact same for google-chrome from google repository) Bug: Run /usr/bin/chromium-browser visit https://fosstorrents.com/distributions/kali-linux/ click any magnet-link (scroll down) Chromium will ask to open with xdg-open or with transmission. to check magnet is registered: xdg-mime query default x-scheme-handler/magnet it should display transmission-gtk.desktop Click open in Chromium - nothing happen with error in terminal: /usr/bin/transmission-gtk: symbol lookup error: /lib64/libgtk-4.so.1: undefined symbol: vkCreateXlibSurfaceKHR Fix/prove that it not problem with anything else: cd /usr/lib64/chromium ./chrome open same link as above - click magnet link - click open - transmission launched and everything works -- You are receiving this mail because: You are on the CC list for the bug.

1 2