January 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1234379] New: parser complains about adwaita theme RC files
by bugzilla_noreply＠suse.com 14 Mar '25

14 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1234379 Bug ID: 1234379 Summary: parser complains about adwaita theme RC files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- /usr/share/themes/Adwaita-dark/gtk-2.0/main.rc:733: error: unexpected identifier 'direction', expected character '}' /usr/share/themes/Adwaita-dark/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1232948] New: VUL-0: CVE-2024-51744: trivy: github.com/golang-jwt/jwt/v4: Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations in golang-jwt
by bugzilla_noreply＠suse.com 14 Mar '25

14 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1232948 Bug ID: 1232948 Summary: VUL-0: CVE-2024-51744: trivy: github.com/golang-jwt/jwt/v4: Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations in golang-jwt Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/426863/ OS: Other Status: NEW Whiteboard: CVSSv3.1:SUSE:CVE-2024-51744:3.1:(AV:N/AC:H/PR:N/UI:R/ S:U/C:L/I:N/A:N) Severity: Normal Priority: P5 - None Component: Security Assignee: dmueller(a)suse.com Reporter: andrea.mattiazzo(a)suse.com QA Contact: security-team(a)suse.de Blocks: 1232936 Target Milestone: --- Found By: --- Blocker: --- golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-51744 https://www.cve.org/CVERecord?id=CVE-2024-51744 https://github.com/golang-jwt/jwt/commit/7b1c1c00a171c6c79bbdb40e4ce7d19706… https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r https://bugzilla.redhat.com/show_bug.cgi?id=2323735 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1216537] New: xdg-utils perl requirement
by bugzilla_noreply＠suse.com 13 Mar '25

13 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1216537 Bug ID: 1216537 Summary: xdg-utils perl requirement Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: simonf.lees(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jslaby(a)suse.com Target Milestone: --- Found By: --- Blocker: --- xdg-utils requires perl via /usr/bin/xdg-screensaver. On minimal systems we'd like to avoid any extra script interpreters. Any chance to avoid using perl there? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1236023] New: Unable to mount filesystems from file managers or GNOME Disks after Tumbleweed upgrade to Cinnamon 6.4
by bugzilla_noreply＠suse.com 13 Mar '25

13 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1236023 Bug ID: 1236023 Summary: Unable to mount filesystems from file managers or GNOME Disks after Tumbleweed upgrade to Cinnamon 6.4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: nsleasy(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- -After upgrade of Cinnamon from 6.2.9 to 6.4.6, user is not able to mount filesystems of any type using 'GNOME Disks' or any file browser (Thunar or Nemo). -Mounting and unmounting of external (USB) filesystem (ext4) fails as well. -Can mount filesystems from the command line, but cannot unmount them from any of the above GUI components. -Mounting an encrypted VeraCrypt filesystem on NTFS works normally. -Suspect missing or incompatible GNOME component necessary for the Cinnamon environment. -Upgrade was performed as follows and completed successfully: zypper mr -d Packman zypper dup --allow-vendor-change zypper mr -e Packman zypper dup --from Packman --allow-vendor-change -Base upgrade was as follows: **** ideapad:~ # zypper dup --allow-vendor-change Retrieving repository 'google-chrome' metadata ..................................................[done] Building repository 'google-chrome' cache .......................................................[done] Retrieving repository 'openSUSE-Tumbleweed-Non-Oss' metadata ................................................................................................................................................[done] Building repository 'openSUSE-Tumbleweed-Non-Oss' cache .....................................................................................................................................................[done] Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata ....................................................................................................................................................[done] Building repository 'openSUSE-Tumbleweed-Oss' cache .........................................................................................................................................................[done] Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 166 items are locked and will not be changed by any action: Available: libreoffice libreoffice-base libreoffice-base-drivers-postgresql libreoffice-branding-upstream libreoffice-calc libreoffice-calc-extensions libreoffice-draw libreoffice-filters-optional libreoffice-gdb-pretty-printers libreoffice-glade libreoffice-gnome libreoffice-gtk3 libreoffice-impress libreoffice-kdeintegration libreoffice-l10n-af libreoffice-l10n-am libreoffice-l10n-ar libreoffice-l10n-as libreoffice-l10n-ast libreoffice-l10n-be libreoffice-l10n-bg libreoffice-l10n-bn libreoffice-l10n-bn_IN libreoffice-l10n-bo libreoffice-l10n-br libreoffice-l10n-brx libreoffice-l10n-bs libreoffice-l10n-ca libreoffice-l10n-ca_valencia libreoffice-l10n-ckb libreoffice-l10n-cs libreoffice-l10n-cy libreoffice-l10n-da libreoffice-l10n-de libreoffice-l10n-dgo libreoffice-l10n-dsb libreoffice-l10n-dz libreoffice-l10n-el libreoffice-l10n-en libreoffice-l10n-en_GB libreoffice-l10n-en_ZA libreoffice-l10n-eo libreoffice-l10n-es libreoffice-l10n-et libreoffice-l10n-eu libreoffice-l10n-fa libreoffice-l10n-fi libreoffice-l10n-fr libreoffice-l10n-fur libreoffice-l10n-fy libreoffice-l10n-ga libreoffice-l10n-gd libreoffice-l10n-gl libreoffice-l10n-gu libreoffice-l10n-gug libreoffice-l10n-he libreoffice-l10n-hi libreoffice-l10n-hr libreoffice-l10n-hsb libreoffice-l10n-hu libreoffice-l10n-hy libreoffice-l10n-id libreoffice-l10n-is libreoffice-l10n-it libreoffice-l10n-ja libreoffice-l10n-ka libreoffice-l10n-kab libreoffice-l10n-kk libreoffice-l10n-km libreoffice-l10n-kmr_Latn libreoffice-l10n-kn libreoffice-l10n-ko libreoffice-l10n-kok libreoffice-l10n-ks libreoffice-l10n-lb libreoffice-l10n-lo libreoffice-l10n-lt libreoffice-l10n-lv libreoffice-l10n-mai libreoffice-l10n-mk libreoffice-l10n-ml libreoffice-l10n-mn libreoffice-l10n-mni libreoffice-l10n-mr libreoffice-l10n-my libreoffice-l10n-nb libreoffice-l10n-ne libreoffice-l10n-nl libreoffice-l10n-nn libreoffice-l10n-nr libreoffice-l10n-nso libreoffice-l10n-oc libreoffice-l10n-om libreoffice-l10n-or libreoffice-l10n-pa libreoffice-l10n-pl libreoffice-l10n-pt_BR libreoffice-l10n-pt_PT libreoffice-l10n-ro libreoffice-l10n-ru ... and 48 more items. Installed: libreoffice-branding-openSUSE libreoffice-icon-themes libreoffice-share-linker libreoffice7.6 libreoffice7.6-base libreoffice7.6-calc libreoffice7.6-dict-en libreoffice7.6-dict-es libreoffice7.6-dict-fr libreoffice7.6-draw libreoffice7.6-en-US libreoffice7.6-freedesktop-menus libreoffice7.6-impress libreoffice7.6-math libreoffice7.6-ure libreoffice7.6-writer p7zip p7zip-full Run 'zypper locks -s' to see the complete list of locked items. The following 116 packages are going to be upgraded: cinnamon cinnamon-control-center cinnamon-control-center-common cinnamon-control-center-lang cinnamon-gschemas cinnamon-lang cinnamon-screensaver-lang cinnamon-session cinnamon-session-lang cinnamon-settings-daemon cinnamon-settings-daemon-lang cjs cpupower cpupower-bash-completion dnsmasq ed gdk-pixbuf-loader-jxl gimp-plugin-jxl google-chrome-stable inxi kernel-firmware-all kernel-firmware-amdgpu kernel-firmware-ath10k kernel-firmware-ath11k kernel-firmware-ath12k kernel-firmware-atheros kernel-firmware-bluetooth kernel-firmware-bnx2 kernel-firmware-brcm kernel-firmware-chelsio kernel-firmware-dpaa2 kernel-firmware-i915 kernel-firmware-intel kernel-firmware-iwlwifi kernel-firmware-liquidio kernel-firmware-marvell kernel-firmware-media kernel-firmware-mediatek kernel-firmware-mellanox kernel-firmware-mwifiex kernel-firmware-network kernel-firmware-nfp kernel-firmware-nvidia kernel-firmware-platform kernel-firmware-prestera kernel-firmware-qcom kernel-firmware-qlogic kernel-firmware-radeon kernel-firmware-realtek kernel-firmware-serial kernel-firmware-sound kernel-firmware-ti kernel-firmware-ueagle kernel-firmware-usb-network kexec-tools libcinnamon-control-center1 libcinnamon-desktop-data libcinnamon-desktop-devel libcinnamon-desktop-lang libcinnamon-desktop4 libcjs0 libcpupower1 libcvc0 libeconf-devel libeconf0 libjxl0_11 libjxl0_11-x86-64-v3 libncurses6 libnemo-extension1 libraptor2-0 librist4 libstorage-ng-lang libstorage-ng-ruby libstorage-ng1 libsubid5 libtiff-devel libtiff-devel-docs libtiff6 libxreaderdocument3 libxreaderview3 login_defs mac ncurses-devel ncurses-utils nemo nemo-extension-fileroller nemo-extension-preview nemo-extension-seahorse nemo-extension-share nemo-extensions-lang nemo-lang openSUSE-release openSUSE-release-appliance-custom parallel-printer-support perl-XML-Twig python311-Pillow python311-pyOpenSSL python311-yt-dlp shadow suse-module-tools suse-module-tools-scriptlets tack terminfo terminfo-base terminfo-iterm terminfo-screen typelib-1_0-CinnamonDesktop-3_0 typelib-1_0-CjsPrivate-1_0 typelib-1_0-Cvc-1_0 typelib-1_0-Nemo-3_0 typelib-1_0-XreaderDocument-1_5 typelib-1_0-XreaderView-1_5 xreader xreader-plugin-pdfdocument yast2-bootloader yt-dlp The following product is going to be upgraded: openSUSE Tumbleweed 20250112-0 -> 20250115-0 The following 57 packages are going to be downgraded: Mesa Mesa-KHR-devel Mesa-dri Mesa-gallium Mesa-libEGL-devel Mesa-libEGL1 Mesa-libGL-devel Mesa-libGL1 Mesa-libglapi0 Mesa-libva cinnamon-gschemas-branding-openSUSE ffmpeg-7 gdk-pixbuf-loader-libheif libavcodec58_134 libavcodec60 libavcodec61 libavdevice60 libavdevice61 libavfilter10 libavfilter7_110 libavfilter9 libavformat58_76 libavformat60 libavformat61 libavresample4_0 libavutil56_70 libavutil58 libavutil59 libcinnamon-desktop-data-branding-openSUSE libfdk-aac2 libgbm1 libheif-aom libheif-dav1d libheif-ffmpeg libheif-jpeg libheif-openjpeg libheif-rav1e libheif-svtenc libheif1 libpostproc55_9 libpostproc57 libpostproc58 libquicktime0 libswresample3_9 libswresample4 libswresample5 libswscale5_9 libswscale7 libswscale8 libvlc5 libvlccore9 libxvidcore4 vlc vlc-codec-gstreamer vlc-noX vlc-qt vlc-vdpau The following 57 packages are going to change vendor: Mesa http://packman.links2linux.de -> openSUSE Mesa-KHR-devel http://packman.links2linux.de -> openSUSE Mesa-dri http://packman.links2linux.de -> openSUSE Mesa-gallium http://packman.links2linux.de -> openSUSE Mesa-libEGL-devel http://packman.links2linux.de -> openSUSE Mesa-libEGL1 http://packman.links2linux.de -> openSUSE Mesa-libGL-devel http://packman.links2linux.de -> openSUSE Mesa-libGL1 http://packman.links2linux.de -> openSUSE Mesa-libglapi0 http://packman.links2linux.de -> openSUSE Mesa-libva http://packman.links2linux.de -> openSUSE ffmpeg-7 http://packman.links2linux.de -> openSUSE gdk-pixbuf-loader-libheif http://packman.links2linux.de -> openSUSE libavcodec58_134 http://packman.links2linux.de -> openSUSE libavcodec60 http://packman.links2linux.de -> openSUSE libavcodec61 http://packman.links2linux.de -> openSUSE libavdevice60 http://packman.links2linux.de -> openSUSE libavdevice61 http://packman.links2linux.de -> openSUSE libavfilter10 http://packman.links2linux.de -> openSUSE libavfilter7_110 http://packman.links2linux.de -> openSUSE libavfilter9 http://packman.links2linux.de -> openSUSE libavformat58_76 http://packman.links2linux.de -> openSUSE libavformat60 http://packman.links2linux.de -> openSUSE libavformat61 http://packman.links2linux.de -> openSUSE libavresample4_0 http://packman.links2linux.de -> openSUSE libavutil56_70 http://packman.links2linux.de -> openSUSE libavutil58 http://packman.links2linux.de -> openSUSE libavutil59 http://packman.links2linux.de -> openSUSE libfdk-aac2 http://packman.links2linux.de -> openSUSE libgbm1 http://packman.links2linux.de -> openSUSE libheif-aom http://packman.links2linux.de -> openSUSE libheif-dav1d http://packman.links2linux.de -> openSUSE libheif-ffmpeg http://packman.links2linux.de -> openSUSE libheif-jpeg http://packman.links2linux.de -> openSUSE libheif-openjpeg http://packman.links2linux.de -> openSUSE libheif-rav1e http://packman.links2linux.de -> openSUSE libheif-svtenc http://packman.links2linux.de -> openSUSE libheif1 http://packman.links2linux.de -> openSUSE libpostproc55_9 http://packman.links2linux.de -> openSUSE libpostproc57 http://packman.links2linux.de -> openSUSE libpostproc58 http://packman.links2linux.de -> openSUSE libquicktime0 http://packman.links2linux.de -> openSUSE librist4 http://packman.links2linux.de -> openSUSE libswresample3_9 http://packman.links2linux.de -> openSUSE libswresample4 http://packman.links2linux.de -> openSUSE libswresample5 http://packman.links2linux.de -> openSUSE libswscale5_9 http://packman.links2linux.de -> openSUSE libswscale7 http://packman.links2linux.de -> openSUSE libswscale8 http://packman.links2linux.de -> openSUSE libvlc5 http://packman.links2linux.de -> openSUSE libvlccore9 http://packman.links2linux.de -> openSUSE libxvidcore4 http://packman.links2linux.de -> openSUSE mac http://packman.links2linux.de -> openSUSE vlc http://packman.links2linux.de -> openSUSE vlc-codec-gstreamer http://packman.links2linux.de -> openSUSE vlc-noX http://packman.links2linux.de -> openSUSE vlc-qt http://packman.links2linux.de -> openSUSE vlc-vdpau http://packman.links2linux.de -> openSUSE The following 5 NEW packages are going to be installed: kernel-default-6.12.9-1.1 python311-xlrd typelib-1_0-Gck-1 typelib-1_0-Gcr-3 typelib-1_0-Xmlb-1_0 The following 25 packages are going to be REMOVED: libSPIRV-Tools-2024_4_rc1 libcamera-base0_3 libcamera0_3 libpoppler-cpp1 libpoppler139 libpoppler144 libproc2-0 libruby3_3-3_3 python310-gobject python310-gobject-Gdk python310-gobject-cairo python310-pip python310-pycairo python310-xlrd ruby3.3 ruby3.3-rubygem-abstract_method ruby3.3-rubygem-cfa ruby3.3-rubygem-cfa_grub2 ruby3.3-rubygem-cheetah ruby3.3-rubygem-fast_gettext ruby3.3-rubygem-gem2rpm ruby3.3-rubygem-nokogiri ruby3.3-rubygem-ruby-augeas ruby3.3-rubygem-ruby-dbus ruby3.3-rubygem-simpleidn The following package requires a system reboot: kernel-default-6.12.9-1.1 116 packages to upgrade, 57 to downgrade, 5 new, 25 to remove, 57 to change vendor. Package download size: 880.6 MiB Package install size change: | 1.40 GiB required by packages that will be installed 167.6 MiB | - 1.24 GiB released by packages that will be removed Note: System reboot required. Backend: classic_rpmtrans Continue? [y/n/v/...? shows all options] (y): **** -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222716] New: libssh tries to read config from wrong crypto-policies location
by bugzilla_noreply＠suse.com 13 Mar '25

13 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1222716 Bug ID: 1222716 Summary: libssh tries to read config from wrong crypto-policies location Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: pmonrealgonzalez(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- libssh-config ships /etc/libssh/libssh_server.config which contains # Parse system-wide crypto configuration file Include /usr/etc/crypto-policies/back-ends/libssh.config But there is no such file. It's supposed to be /etc/crypto-policies/back-ends/libssh.config Probably caused by the fix for bug 1211718. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1231490] New: [Build 20241008-SELinux] openQA test fails in installation: AutoYaST forgets SELinux packages
by bugzilla_noreply＠suse.com 13 Mar '25

13 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1231490 Bug ID: 1231490 Summary: [Build 20241008-SELinux] openQA test fails in installation: AutoYaST forgets SELinux packages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4548531/modules/inst allation/steps/16 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: yast2-maintainers(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes Created attachment 877882 --> https://bugzilla.suse.com/attachment.cgi?id=877882&action=edit YaST installation logs The linked QA test uses AutoYaST with a rather simple profile to install TW with SELinux enforcing by default. The AY profile has: <software> <install_recommended config:type="boolean">true</install_recommended> <products config:type="list"> <product>openSUSE</product> </products> <patterns config:type="list"> <pattern>apparmor</pattern> <pattern>base</pattern> <pattern>gnome</pattern> </patterns> </software> And the control.xml has: <lsm> <select>selinux</select> <apparmor> <patterns>apparmor</patterns> <selectable config:type="boolean">true</selectable> </apparmor> <selinux> <mode>enforcing</mode> <configurable config:type="boolean">true</configurable> <selectable config:type="boolean">true</selectable> <patterns>selinux</patterns> </selinux> <configurable config:type="boolean">true</configurable> </lsm> Result is that SELinux is enabled in enforcing mode, but the selinux pattern is not installed. y2log shows: 2024-10-10 07:43:49 <1> install(4028) [Ruby] modules/Packages.rb(log_resolvables):2392 Resolvables of type pattern set by app_high: 2024-10-10 07:43:49 <1> install(4028) [Ruby] modules/Packages.rb(block in log_resolvables):2396 - {:name=>"apparmor", :version=>"20200505-54.1", :arch=>"x86_64", :status=>:selected} 2024-10-10 07:43:49 <1> install(4028) [Ruby] modules/Packages.rb(block in log_resolvables):2396 - {:name=>"base", :version=>"20200505-54.1", :arch=>"x86_64", :status=>:selected} 2024-10-10 07:43:49 <1> install(4028) [Ruby] modules/Packages.rb(block in log_resolvables):2396 - {:name=>"gnome", :version=>"20201210-21.4", :arch=>"x86_64", :status=>:selected} ... 2024-10-10 07:50:44 <1> install(4028) [Ruby] lsm/config.rb(propose_default):56 The settings are {:select=>"selinux", :apparmor=>{"patterns"=>"apparmor", "selectable"=>true}, :selinux=>{"mode"=>"enforcing", "configurable"=>true, "selectable"=>true, "patterns"=>"selinux"}, :configurable=>true} 2024-10-10 07:50:44 <1> install(4028) [Ruby] lsm/config.rb(select):67 Selected LSM with id: selinux 2024-10-10 07:50:44 <1> install(4028) [Ruby] modules/PackagesProposal.rb(SetResolvables):154 Setting resolvables ["selinux"] of type pattern for LSM 2024-10-10 07:50:44 <1> install(4028) [Ruby] installation/finish_client.rb(run):51 Called Installation::Clients::SecurityFinish.run with Info FWICT the lsm configuration step is too late, after solving has already completed? ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-autoyast_gnome@64bit fails in [installation](https://openqa.opensuse.org/tests/4548531/modules/installatio… ## Test suite description Maintainer: QE Yast Testing autoyast installation with given profile and expect SLES with gnome. Please, see the profile for more details. Profile is available in distri git repo under data subdirectory. Same as autoyast_gnome but with product defined in the profile. ## Reproducible Fails since (at least) Build [20241008-SELinux](https://openqa.opensuse.org/tests/4548531) (current job) ## Expected result Last good: [20241009](https://openqa.opensuse.org/tests/4547166) (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 13

[Bug 1232669] New: gdm: gdm-config not working on openSUSE
by bugzilla_noreply＠suse.com 13 Mar '25

13 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1232669 Bug ID: 1232669 Summary: gdm: gdm-config not working on openSUSE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: matthias.gerstner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dimstar(a)opensuse.org Target Milestone: --- Found By: --- Blocker: --- Newer GDM versions ship with a `gdm-config` utility that is supposed to allow configuring things like fingerprint authentication and smartcard authentication. It turns out this utility is not working on openSUSE: gdm-config smartcard -e (gdm-config:32822): Gdm-CRITICAL **: 17:31:29.942: Failed to handle “smartcard” command: No PAM module available for Smart Card authentication The reason why it fails is, that it looks for the gdm-smartcard PAM file in /etc, not in /usr/lib/pam.d: strace gdm-config smartcard -e |& grep smartcard execve("/usr/bin/gdm-config", ["gdm-config", "smartcard", "-e"], 0x7ffeaa26de10 /* 58 vars */) = 0 newfstatat(AT_FDCWD, "/etc/pam.d/gdm-smartcard", 0x7ffed4ce4810, 0) = -1 ENOENT (No such file or directory) (gdm-config:32830): Gdm-CRITICAL **: 17:33:00.721: Failed to handle “smartcard” command: No PAM module available for Smart ) = 128 But even when working around this by placing a symlink, this still doesn't work: gdm-config smartcard -e (gdm-config:32857): Gdm-CRITICAL **: 17:38:31.688: Failed to handle “smartcard” command: Failed to run a required distro hook: No distro detected, no hook to run It seems during build time of GDM the DISTRO meson option needs to be set and a "distro hook" script needs to be specified that performs the necessary configuration steps, if any. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1226116] New: nvidia-open-driver-G06 ... 550.90.07: Fails suspend/recover from powersaving
by bugzilla_noreply＠suse.com 13 Mar '25

13 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1226116 Bug ID: 1226116 Summary: nvidia-open-driver-G06 ... 550.90.07: Fails suspend/recover from powersaving Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: burnus(a)gmx.de QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 875386 --> https://bugzilla.suse.com/attachment.cgi?id=875386&action=edit nvidia-bug-report.log.gz from nvidia-bug-report.sh --safe-mode [That's on a Lenovo P1 Gen 6 with "NVIDIA RTX A1000 6GB Laptop GPU".] When going to the suspend mode, it looks quite normal (screen gets dark, powerlight blinks.) However, when one presses a button: (1) it shows the terminal Window - not the Wayland desktop - with two unrelated warnings: i2c_hid_acpi i2c-ELAN0686:00: i2c_hid_get_input: incomplete report (31/65280) iwlwifi 0000:00:14.3: WRT: Invalid buffer destination (2) When going to Alt+F2, it shows a login screen but then nothing works (well, SysRq-{S,U,B} does work), but nothing on that screen nor Alt-Shift-F... When skipping (2): (3) When going to a terminal (e.g. Alt-F1), login is possible. Getting some diagnostic output: * nvidia-bug-report.sh stops early as an access to /proc/driver/nvidia/gpus/0000:01:00.0/information (I think it was that file) got stuck (lsof -p<pid> showed that file) – likewise, nvidia-smi did not output anything (both interruptible by 'ctrl-C'. * A reboot failed with some message by systemd related to nvidia-*.service; I thought it was nvidia-powerd.service, but looking at the logs, it could be also nvidia-suspend.service. In any case, it stated something that disabling (or enabling?) wasn't possible while the service was currently enabled (or disabled?). * "nvidia-bug-report.sh --safe-mode" this did work → see attached file. * * * dmesg showed many lines of the form: kernel: NVRM: kbusVerifyBar2_GM107: MMUTest BAR0 window offset 0x70e000 returned garbage 0x0 The attached .gz file from "nvidia-bug-report.sh --safe-mode" contains both dmesg and "journalctl -b -0" and has the line above 1,750,353 times. The "journalctl -b -0" output it contains (→ attachment) has: Jun 07 20:59:33 tux.net-b.de /usr/bin/nvidia-powerd[1477]: Dbus Connection is established Jun 07 21:29:48 tux.net-b.de suspend[3509]: nvidia-suspend.service Jun 07 21:29:48 tux.net-b.de logger[3509]: <13>Jun 7 21:29:48 suspend: nvidia-suspend.service Jun 07 21:29:48 tux.net-b.de kernel: NVRM: nvCheckFailedNoLog: Check failed: pMemDesc->_pInternalMapping != NULL @ mem_desc.c:2260 Jun 07 21:29:48 tux.net-b.de kernel: NVRM: nvAssertFailedNoLog: Assertion failed: 0 @ mem_utils.c:574 Jun 07 21:29:48 tux.net-b.de kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Ran out of a critical resource, other than memory [NV_ERR_INSUFFICIENT_RESOURCES] (0x0000001A) returned from memmgrMemCopy(pMemoryManager, &sysSurface, &vidSurface, copySize, TRANSFER_FLAGS_PREFER_CE) @ fbsr_gm107.c:1156 * * * I think the issue occurred when doing the suspend and not when waking up the system, but I might be mistaken. - I thought wall time showed it, but I am not completely sure as I woke it up quite quickly; however, the quoted assertion fails directly after nvidia-suspend.service, which implies that it happens during the suspend. BTW: With the older 550.78 driver, leaving the laptop a while alone (→ power save mode) ended up with a reboot or shortly showing the terminal (similar output as above) before rebooting. Thus, the 550.78 issue was definitely a suspend/power-save issue. [The triggered reboot would be harder to diagnose than the issue I have now.] * * * Installed nvidia packages (rpm -qa '*nvidia*') - all are now 550.90.07-23.1: nvidia-open-driver-G06-signed-kmp-default-550.90.07_k6.9.3_1-1.1.x86_64 kernel-firmware-nvidia-20240519-1.1.noarch nvidia-compute-G06-32bit-550.90.07-23.1.x86_64 nvidia-gl-G06-550.90.07-23.1.x86_64 nvidia-video-G06-32bit-550.90.07-23.1.x86_64 nvidia-compute-utils-G06-550.90.07-23.1.x86_64 nvidia-video-G06-550.90.07-23.1.x86_64 nvidia-utils-G06-550.90.07-23.1.x86_64 libnvidia-egl-wayland1-1.1.13-1.3.x86_64 nvidia-compute-G06-550.90.07-23.1.x86_64 nvidia-gl-G06-32bit-550.90.07-23.1.x86_64 kernel-firmware-nvidia-gspx-G06-550.90.07-1.1.x86_64 * * * Side remarks: (a) Contrary to the classic drivers, the open kernel driver offers the pageableMemoryAccess property, which permits via Linux kernel HMM support to migrate memory pages to/from the device when a the page is accessed. That's used, e.g., by GCC 15 (mainline) with OpenMP offload support when Unified-Shared Memory (USM) has been requested. See https://gcc.gnu.org/onlinedocs/libgomp/nvptx.html / https://gcc.gnu.org/gcc-15/changes.html (b) The open kernels drivers permit showing the screen to both an external monitor and to the laptop screen, which didn't work with the default/classic driver. (c) The more recent classic/non-'open kernels' driver also tended to crash occasionally (either reboot [typically when doing 'zypper dup'; possibly due to some systemd interaction] - or a freeze with a kernel fail (blinking shift lock; not even SysRq worked), which is a known but unsolved issue for the 550 driver according to the Nvidia Linux forum. Thus, except for the issue reported in this bug, the open-kernels driver is better. :-) And the future (said to be the default with Nvidia's 555 driver). -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1235997] New: After zypper dup in TW for 2082 packages, machine does not revive
by bugzilla_noreply＠suse.com 13 Mar '25

13 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1235997 Bug ID: 1235997 Summary: After zypper dup in TW for 2082 packages, machine does not revive Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: non.space.1(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Takashi, et al: Seems like the recurring problem of non-revival from suspend has recurred in both my TW && my Leap 15.6 installs after the recent large package upgrade in TW. This time, however it does not seem to be related to switching away from nouveau as it did the last time. Lsmod shows "nouveau" all over the place. Posted the issue on the forum, so far no developments on resolving the issue. Requested data has been provided there. In the case of TW I found that regressing to the previous kernel, from the new 6.12.8-2 back to 6.12.6-1 did work to bring revival from suspend back. However, in Leap 15.6 where based upon your suggestion I have dev kernels & regular installed, grub does not show any distinguishing information to help select another kernel. For instance, in advanced options, since the newest kernel did not revive, selecting both #3 & #4 "hang" at "crng init clone" line. Dropping down to line #6 brings the same kernel as the newest kernel, 6.12.9-lp155.2.g0ae2136-default . . . which does not revive from suspend. As previously, in both TW & Leap 15.6, clicking the keyboard starts the machine up, but the display remains black. Link to forum thread: https://forums.opensuse.org/t/after-zypper-dup-in-tw-for-2082-packages-toda… -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1227292] New: VUL-0: CVE-2020-28598: PrusaSlicer: out-of-bounds write in the Admesh stl_fix_normal_directions() functionality
by bugzilla_noreply＠suse.com 12 Mar '25

12 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1227292 Bug ID: 1227292 Summary: VUL-0: CVE-2020-28598: PrusaSlicer: out-of-bounds write in the Admesh stl_fix_normal_directions() functionality Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/303974/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: code(a)bnavigator.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: --- An out-of-bounds write vulnerability exists in the Admesh stl_fix_normal_directions() functionality of Prusa Research PrusaSlicer 2.2.0 and Master (commit 4b040b856). A specially crafted AMF file can lead to code execution. An attacker can provide a malicious file to trigger this vulnerability. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-28598 https://talosintelligence.com/vulnerability_reports/TALOS-2020-1222 http://www.cvedetails.com/cve/CVE-2020-28598/ https://www.cve.org/CVERecord?id=CVE-2020-28598 https://bugzilla.redhat.com/show_bug.cgi?id=2294728 -- You are receiving this mail because: You are on the CC list for the bug.

1 2