June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1224773] Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c32 Alberto Planas Dominguez <aplanas(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(aplanas(a)suse.com) | --- Comment #32 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Ignaz Forster from comment #31) > @Alberto: On a first glance I couldn't find any RPM macro integration so > that a RPM package calling %regenerate_initrd_post would trigger the initrd > rebuild on a systemd-boot system. Am I missing something, or do we still > have to implement this? regenerate-initrd-posttransaction script has been updated here: https://github.com/openSUSE/suse-module-tools/pull/103 It is still under review, and requires a new plugin in sdbootutil, that is here: https://github.com/openSUSE/sdbootutil/pull/92 This plugin is a tukit (transactional-update) plugin, using a new mechanism implemented here: https://github.com/openSUSE/transactional-update/pull/122 So all has been implemented, and all of them are waiting reviews (except sdbootutil#92 that I reviewed myself :P) The new mechanism should be working as this: 1) tukit can execute plugins in a -pre / -post fashion similar to snapper, for each verb like "call", "callext", "open", "abort". The exact list is documented in transactional-update#122 2) sdbootutil provides a plugin for callext-post, that will inspect $bind_dir/run/regenerate-initrd. If it is present inside the transaction it will be copied outside in the host /run 3) regenerate-initrd-posttrans is now aware of transactional systems with a separate /boot partition (that is the case for FDE when using systemd-boot or grub2-bls) If detected and the scriptlet is called _inside_ the transaction it will do nothing, as this would require changing something _outside_ the transaction (the risk of that is that you can see initrds that are not attached to any transaction, for example) 4) sdbootutil provides the old snapper plugin that is executed once the transaction is closed and available, and will call regenerate-initrd-posttrans if the host /run contains the regenerate-initrd/ directory, but now from outside the transaction -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224773] Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c31 Ignaz Forster <iforster(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aplanas(a)suse.com Flags|needinfo?(iforster(a)suse.com |needinfo?(aplanas(a)suse.com) |) | --- Comment #31 from Ignaz Forster <iforster(a)suse.com> --- (In reply to Stefan Dirsch from comment #29) > 2. transactional-update initrd doesn't work together with systemd-boot Correct, currently systemd-boot is not directly integrated into transactional-update itself yet (i.e. the commands "initrd", "bootloader" and "grub.cfg" don't do the right thing on a systemd-boot system). systemd-boot support is generically implemented as a snapper plugin using the "sdbootutil" instead, because of course you can also use systemd-boot on non-transactional systems. The sdbootutil script also includes detection whether it is necessary to regenerate the initrd. @Alberto: On a first glance I couldn't find any RPM macro integration so that a RPM package calling %regenerate_initrd_post would trigger the initrd rebuild on a systemd-boot system. Am I missing something, or do we still have to implement this? > 1. transactional-update initrd is not being executed when installing a KMP See answer above - this is something which needs to be implemented on a RPM macro level... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225863] New: Chromium crashes on startup
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225863 Bug ID: 1225863 Summary: Chromium crashes on startup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: dev(a)dominik-schmidt.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After updating openSUSE Tumbleweed the other day Chromium is now crashing for me on startup (i.e. I don't get to see a window at all). My system is completely up to date, I switched all packages from packman to repo-oss. When running Chromium in GDB I can retrieve this backtrace: > 0x000055555e2ec853 in partition_alloc::internal::FreelistCorruptionDetected(unsigned long) () > (gdb) bt > #0 0x000055555e2ec853 in partition_alloc::internal::FreelistCorruptionDetected(unsigned long) () > #1 0x000055555e2fc487 in allocator_shim::internal::PartitionMalloc(allocator_shim::AllocatorDispatch const*, unsigned long, void*) () > #2 0x000055555dc170f2 in base::allocator::dispatcher::internal::DispatcherImpl<base::PoissonAllocationSampler>::AllocFn(allocator_shim::AllocatorDispatch const*, unsigned long, void*) () > #3 0x000055555e2fba1b in malloc () > #4 0x00007ffff36aa75e in strdup () at /lib64/libc.so.6 > #5 0x00007ffff72a7439 in () at /lib64/libfontconfig.so.1 > #6 0x00007ffff72a8f3c in () at /lib64/libfontconfig.so.1 > #7 0x00007ffff72ad2c5 in () at /lib64/libfontconfig.so.1 > #8 0x00007ffff71ce988 in () at /lib64/libexpat.so.1 > #9 0x00007ffff71cb7c4 in () at /lib64/libexpat.so.1 > #10 0x00007ffff71cdc49 in () at /lib64/libexpat.so.1 > #11 0x00007ffff71c2258 in () at /lib64/libexpat.so.1 > #12 0x00007ffff71ca3e5 in XML_ParseBuffer () at /lib64/libexpat.so.1 > #13 0x00007ffff72a97d5 in () at /lib64/libfontconfig.so.1 > #14 0x00007ffff72aa11e in () at /lib64/libfontconfig.so.1 > #15 0x00007ffff72924ef in () at /lib64/libfontconfig.so.1 > #16 0x00007ffff728d5b9 in () at /lib64/libfontconfig.so.1 > #17 0x00007ffff72927d9 in FcInit () at /lib64/libfontconfig.so.1 > #18 0x000055555f0e7a78 in base::NoDestructor<gfx::(anonymous namespace)::GlobalFontConfig>::NoDestructor<>() () > #19 0x000055555f0e7a06 in base::internal::Invoker<base::internal::FunctorTraits<gfx::InitializeGlobalFontConfigAsync()::$_0&&>, base::internal::BindState<false, false, false, gfx::InitializeGlobalFontConfigAsync()::$_0>, void ()>::RunOnce(base::internal::BindStateBase*) () > #20 0x000055555e236f4b in base::TaskAnnotator::RunTaskImpl(base::PendingTask&) () > #21 0x000055555e25aef8 in base::internal::TaskTracker::RunTaskImpl(base::internal::Task&, base::TaskTraits const&, base::internal::TaskSource*, base::internal::SequenceToken const&) () > #22 0x000055555e25afc1 in base::internal::TaskTracker::RunSkipOnShutdown(base::internal::Task&, base::TaskTraits const&, base::internal::TaskSource*, base::internal::SequenceToken const&) () > #23 0x000055555e25abf3 in base::internal::TaskTracker::RunTask(base::internal::Task, base::internal::TaskSource*, base::TaskTraits const&) () > #24 0x000055555e25a717 in base::internal::TaskTracker::RunAndPopNextTask(base::internal::RegisteredTaskSource) () > #25 0x000055555e26d2df in base::internal::WorkerThread::RunWorker() () > #26 0x000055555e26ceaa in base::internal::WorkerThread::RunPooledWorker() () > #27 0x000055555e26cd2a in base::internal::WorkerThread::ThreadMain() () > #28 0x000055555e28a08a in base::(anonymous namespace)::ThreadFunc(void*) () > #29 0x00007ffff3692ba2 in start_thread () at /lib64/libc.so.6 > #30 0x00007ffff371400c in clone3 () at /lib64/libc.so.6 I also tried 125.0.6422.141-1965.1-x86_64 from network:chromium/chromium, but it shows the same behavior. As it looks related to fontconfig, I ran > fc-cache -f -v as user and root with no success either. Happy to provide any additional system information, logs, outputs... Thanks in advance -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225870] New: Missing glibc-locale-base-32bit breaks system updates
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225870 Bug ID: 1225870 Summary: Missing glibc-locale-base-32bit breaks system updates Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: romans32401(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When I try to do updates in KDE Discover, I get the following error: <html>Dependency resolution failed:<br/><br/>the installed steam-1.0.0.79-1.4.x86_64 requires 'glibc-locale-base-32bit', but this requirement cannot be provided</html> It also won't let me update other packages, even if I deselect all of the glibc ones. I was able to do updates through zypper, but even after rebooting, I still see (this time only) glibc-32bit under updates and I get the same error. I think this is related to this recent bug https://bugzilla.opensuse.org/show_bug.cgi?id=1225809 . Trying zypper up again gives me the following output: Loading repository data... Reading installed packages... The following 56 package updates will NOT be installed: gdk-pixbuf-loader-libheif glibc-32bit libavcodec58_134 libavcodec60 libavfilter9 libavformat58_76 libavformat60 libavutil56_70 libavutil58 libfdk-aac2 libfdk-aac2-32bit libgbm1 libgbm1-32bit libheif1 libheif-aom libheif-dav1d libheif-ffmpeg libheif-jpeg libheif-openjpeg libheif-rav1e libheif-svtenc libpostproc55_9 libpostproc57 libquicktime0 libswresample3_9 libswresample4 libswscale5_9 libswscale7 libvdpau_r600 libvdpau_radeonsi libvlc5 libvlccore9 libvulkan_radeon libvulkan_radeon-32bit libxvidcore4 Mesa Mesa-32bit Mesa-dri Mesa-dri-32bit Mesa-gallium Mesa-gallium-32bit Mesa-KHR-devel Mesa-libEGL1 Mesa-libEGL-devel Mesa-libGL1 Mesa-libGL1-32bit Mesa-libglapi0 Mesa-libglapi0-32bit Mesa-libGL-devel Mesa-libva Mesa-vulkan-device-select Mesa-vulkan-device-select-32bit vlc-codec-gstreamer vlc-lang vlc-noX vlc-qt Nothing to do. Trying zypper in glibc-32bit gives me the following output: Loading repository data... Reading installed packages... Resolving package dependencies... Problem: 1: the installed steam-1.0.0.79-1.4.x86_64 requires 'glibc-locale-base-32bit', but this requirement cannot be provided deleted providers: glibc-locale-base-32bit-2.39-7.1.x86_64 Solution 1: deinstallation of steam-1.0.0.79-1.4.x86_64 Solution 2: do not install glibc-32bit-2.39-8.1.x86_64 Solution 3: break steam-1.0.0.79-1.4.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225875] New: VUL-0: CVE-2024-36127: apko: exposure of HTTP basic auth credentials in log output
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225875 Bug ID: 1225875 Summary: VUL-0: CVE-2024-36127: apko: exposure of HTTP basic auth credentials in log output Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/408521/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: opensuse_buildservice(a)ojkastl.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- apko is an apk-based OCI image builder. apko exposures HTTP basic auth credentials from repository and keyring URLs in log output. This vulnerability is fixed in v0.14.5. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-36127 https://www.cve.org/CVERecord?id=CVE-2024-36127 https://github.com/chainguard-dev/apko/commit/2c0533e4d52e83031a04f6a83ec63… https://github.com/chainguard-dev/apko/security/advisories/GHSA-v6mg-7f7p-q… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1225869] Package openblas flavors openmp, pthreads and serial do not build with gcc14 because of new errors
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225869 https://bugzilla.suse.com/show_bug.cgi?id=1225869#c1 Egbert Eich <eich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |mjambor(a)suse.com --- Comment #1 from Egbert Eich <eich(a)suse.com> --- Sorry, I don't have time to do this. Please find someone else. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225867] New: games:tools/steam: Steam requires 'glibc-locale-base-32bit' which is no longer available in Tumbleweed
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225867 Bug ID: 1225867 Summary: games:tools/steam: Steam requires 'glibc-locale-base-32bit' which is no longer available in Tumbleweed Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: gmbr3(a)opensuse.org Reporter: pavel.urusov(a)gmail.com QA Contact: screening-team-bugs(a)suse.de CC: opensuse(a)dstoecker.de Target Milestone: --- Found By: --- Blocker: --- Trying to update OpenSUSE Tumbleweed with 'zypper dup' leads to the following error: Problem: 1: the installed steam-1.0.0.79-1.4.x86_64 requires 'glibc-locale-base-32bit', but this requirement cannot be provided deleted providers: glibc-locale-base-32bit-2.39-7.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225868] New: games:tools/gamescope: gamescope always crashes on systems with AMD Polaris GPUs
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225868 Bug ID: 1225868 Summary: games:tools/gamescope: gamescope always crashes on systems with AMD Polaris GPUs Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: gmbr3(a)opensuse.org Reporter: pavel.urusov(a)gmail.com QA Contact: screening-team-bugs(a)suse.de CC: opensuse(a)dstoecker.de Target Milestone: --- Found By: --- Blocker: --- The version of Gamescope currently available in the Tumbleweed repositories always crashes on systems with AMD Polaris GPUs (RX 4x0/5x0 families): https://github.com/ValveSoftware/gamescope/issues/1218 The fix has already been upstreamed, please consider downgrading the package to version 3.14.2 until Valve releases a new version which incorporates the fixes. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225690] VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 125.0.6422.141
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225690 https://bugzilla.suse.com/show_bug.cgi?id=1225690#c3 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED --- Comment #3 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- TW snapshot is out, Leap 15.6 update still building. Done -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221557] New: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221557 Bug ID: 1221557 Summary: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Flatpak Assignee: rbrown(a)suse.com Reporter: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0 Build Identifier: Hello there this came to my attention as OBS Studio updated their flatpak from 30.0.2 to 30.1.0 where they also changed the used runtime form KDE Platform 6.5 to 6.6. Since that update browser sources and browser docks do no longer work if they are pointing at an HTTPS protected site. While with runtime 6.5 it still works fine (more details below). Browser docks are only available in a X11 session due to bugs under Wayland but also the only one to actually show an error message while browser sources are completely silent and simply keep empty. Beside the steps to reproduce other findings made in the meantime before reporting here. This happens on openSUSE Leap 15.6, openSUSE Tumbleweed, openSUSE Aeon and openSUSE Kalpa. Running the OBS Studio flatpak on virtually any other Linux distribution (Tested Ubuntu 22.04, Fedora 39, Arch Linux) does work just fine. Nevertheless I report the bug for Aeon as Aeon and Kalpa heavily rely on flatpaks and this issue is more imminent for them than for regular Tumbleweed and Leap. Other things I tried was running the OBS Studio 30.1.0 *.dep package from inside a Ubuntu 22.04 distrobox container running on my openSUSE Aeon host. Browser sources and docks worked just fine. Also I ran a Ubuntu 22.04 VM on my openSUSE Aeon host using Gnome Boxes and the flatpak version of OBS Studio, browser sources and docks worked just fine too. Furthermore I build the OBS Studio flatpak locally using fkatpab-builder from inside a openSUSE Tumbleweed distrobox using runtime 6.5 instead of 6.6. That OBS Studio flatpak did worked just fine on my openSUSE Aeon and inside the openSUSE Tumlbeweed distrobox container. Whilst building it with 6.6 was broken again. To build OBS Studio with a different runtime do the following: 1) git clone --recursive https://github.com/obsproject/obs-studio.git 2) Change the content of obs-studio/build-aux/com.obsproject.Studio to ruse runtime 6.5 instead of 6.6 (line 4) 3) flatpak-builder --force-clean --install-deps-from=flathub --user --install --ccache --mirror-screenshots-url=https://dl.flathub.org/media/ build-dir build-aux/com.obsproject.Studio.json --user --install Reproducible: Always Steps to Reproduce: 1. Install OBS Studio flatpak 30.1.0 2. Add a browser dock or a browser source pointing to an https site 3. See nothing or in case of a dock the error: ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Actual Results: Empty browser source or a browser dock showing ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Expected Results: Browser sources and docks to work Thsi bug was firstly reported to OBS Studio where we found out it's actually the runtime causeing the issue: https://github.com/obsproject/obs-studio/issues/10385 And reported to KDE where they asked me to better open up the issue directly for openSUSE as other distributions are not affected over here: https://bugs.kde.org/show_bug.cgi?id=483746 -- You are receiving this mail because: You are on the CC list for the bug.

1 1