- openSUSE Bugs

[Bug 1232843] VUL-0: chromium: 130.0.6723.116 stable release
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232843 https://bugzilla.suse.com/show_bug.cgi?id=1232843#c4 --- Comment #4 from Marcus Meissner <meissner(a)suse.com> --- openSUSE-SU-2024:0356-1: An update that fixes two vulnerabilities is now available. Category: security (important) Bug References: 1232843 CVE References: CVE-2024-10826,CVE-2024-10827 JIRA References: Sources used: openSUSE Backports SLE-15-SP5 (src): chromium-130.0.6723.116-bp155.2.138.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232843] VUL-0: chromium: 130.0.6723.116 stable release
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232843 https://bugzilla.suse.com/show_bug.cgi?id=1232843#c3 --- Comment #3 from Marcus Meissner <meissner(a)suse.com> --- openSUSE-SU-2024:0357-1: An update that fixes two vulnerabilities is now available. Category: security (important) Bug References: 1232843 CVE References: CVE-2024-10826,CVE-2024-10827 JIRA References: Sources used: openSUSE Backports SLE-15-SP6 (src): chromium-130.0.6723.116-bp156.2.50.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203617] In plasma5 midnight commander doesn't exit to current directory anymore
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1203617 https://bugzilla.suse.com/show_bug.cgi?id=1203617#c90 Dr. Werner Fink <werner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? CC| |dmueller(a)suse.com, | |gfx-bugs(a)suse.de, | |sbahling(a)suse.com, | |wolfgang.engel(a)suse.com --- Comment #90 from Dr. Werner Fink <werner(a)suse.com> --- In other works on KDE the file /etc/profile gets never sourced as otherwise *all* file with suffix *.sh below /usr/etc/profile.d/ and /etc/profile.d/ would be sourced at least on TW (on Leap the files *.s in /etc/profile.d/) at least for all user with a bourne shell as lopin shell. Similar for users with (t)csh as login shell. At least this how I had written the login code for X sessions some decades back[1]. Looks like this had become ignored by KDE developers or how the plasma session is meanwhile started ... [1] Current TW has still this code ... now in /usr/etc/X11/xdm/Xsession search for shell function exec_login(): [...] # # Run the X session scripts with the login shell of # the user. This function requires bash 2.0 or higher. # exec_login () { local shell=$SHELL local cmd=${shell##*/} case "${cmd}" in r*sh) shell=/bin/${cmd#r}; cmd=${shell##*/} ;; true) shell=/bin/sh ; cmd=${shell##*/} ;; esac test -f "$1" -a ! -x "$1" && set -- /bin/bash "$@" : ${HOSTNAME:=$(hostname -f)} export HOSTNAME unset TMPDIR case "${cmd}" in csh|tcsh) exec -l -a ${cmd} ${shell} -c 'exec $argv:q' "${@}" ;; bash*|zsh) exec -l -a ${cmd} ${shell} --login -c 'exec "${@}"' - "${@}" ;; dash|lksh|mksh|*pcksh|ksh*) exec -l -a ${cmd} ${shell} -l -c 'exec "${@}"' - "${@}" ;; *) exec -l -a ${cmd} ${shell} -c 'exec "${@}"' - "${@}" ;; esac } -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231928] SDDM on external screen is not functional
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231928 https://bugzilla.suse.com/show_bug.cgi?id=1231928#c6 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pstivanin(a)suse.com --- Comment #6 from Fabian Vogt <fvogt(a)suse.com> --- *** Bug 1233138 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233138] sddm multiple monitors unlock works only on secondary monitor
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233138 https://bugzilla.suse.com/show_bug.cgi?id=1233138#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE CC| |fvogt(a)suse.com Status|NEW |RESOLVED --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- Duplicate of bug 1231928. Should already be fixed in Snapshot 20241108. *** This bug has been marked as a duplicate of bug 1231928 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232837] rpm sometimes need multiple cpu minutes to update a single rpm package
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232837 https://bugzilla.suse.com/show_bug.cgi?id=1232837#c23 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CONFIRMED Assignee|screening-team-bugs(a)suse.de |werner(a)suse.com --- Comment #23 from Fabian Vogt <fvogt(a)suse.com> --- I see the same occasionally, even for trivial changes (like installing gdbm-devel), zypper spends most of its time in the posttrans hook for mandb. By coincidence, I had to strace zypper yesterday and noticed that it created thousands (!) of subprocesses in a simple transaction, which might be the cause for this. Upstream there's https://gitlab.com/man-db/man-db/-/merge_requests/2, which describes this issue quite nicely. The perforamnce issue is that mandb uses libpipeline for some tasks like decompression, but creating a process for each decompression is very expensive. Upstream optimized this away to try in-process decompression first, which resulted in a 10x speedup. However, the downstream patch https://build.opensuse.org/projects/Base:System/packages/man/files/man-db-2… adds libzio integration to man without support for the in-process mode, which causes a significant slowdown. Here a comparison of mandb runs without and with libzio: fvogt@fvogt-thinkpad:~> time sudo man-db/src/mandb --quiet --create real 0m5,862s user 0m0,012s sys 0m0,006s fvogt@fvogt-thinkpad:~> time sudo man-db/src/mandb --quiet --create real 0m32,662s user 0m0,000s sys 0m0,017s I wonder what the patch was added for. Upstream man only supports zlib for compression, so I don't think we need to deviate there and the offending patch can be dropped without replacement. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232458] zypper ignores /var/cache/zypp/packages/.no_auto_prune (Version 1.14.77, TW and Leap)
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232458 https://bugzilla.suse.com/show_bug.cgi?id=1232458#c2 --- Comment #2 from Michael Andres <ma(a)suse.com> --- Well - I stand corrected - The man page says: > /var/cache/zypp/packages > If keeppackages property is set for a repository, all the RPM file > downloaded during installation will be kept here. > ... > Subdirectories of removed or otherwise unknown repositories are > cleaned automatically. This auto-cleanup can be prevented by > creating a file named .no_auto_prune in the pkg-cache directory. So '.no_auto_prune' just prevents the package-cache removal of unknown/deleted repositories. It does not auto-enable 'keeppackages'. And this is how it is implemented. But I'll nevertheless add it to the '--details' view of 'lr'. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233138] New: sddm multiple monitors unlock works only on secondary monitor
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233138 Bug ID: 1233138 Summary: sddm multiple monitors unlock works only on secondary monitor Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: pstivanin(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This has started around a month ago, and it happens only at login. The focus is (as it should be) on the primary monitor but if I input the password and hit enter, nothing happens. I have to go on the secondary monitor, type the password there and then it logs in. $ cat /etc/os-release ID="opensuse-tumbleweed" VERSION_ID="20241106" $ rpm -qi sddm Name : sddm Version : 0.21.0 Release : 4.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231139] [SELinux] systemd-cryptsetup generator cannot read /etc/crypttab
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231139 https://bugzilla.suse.com/show_bug.cgi?id=1231139#c6 Alberto Planas Dominguez <aplanas(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Alberto Planas Dominguez <aplanas(a)suse.com> --- Uhm am having problems to reproduce the issue. I will close it and if it appears again I will reopen it with useful information -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233016] memory buff/cache issue with qemu
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233016 https://bugzilla.suse.com/show_bug.cgi?id=1233016#c7 Vlastimil Babka <vbabka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dfaggioli(a)suse.com, | |jgross(a)suse.com --- Comment #7 from Vlastimil Babka <vbabka(a)suse.com> --- Thanks. Does the "Cached:" counter drop on the bad kernel if you stop the VM before it makes the system unusable? (and if it not drop immediately, does it after a sync && echo 3 > .../drop_caches?) CCing some virtualization folks. Looks like KVM might be allocating and pinning page cache memory on 6.11 kernel in addition to consuming anonymous memory, and that doesn't happen on 6.10. Any ideas? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233087] New: profiles under /etc/profile.d are not executed in the KDE console or xterm.
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233087 Bug ID: 1233087 Summary: profiles under /etc/profile.d are not executed in the KDE console or xterm. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ecsos(a)schirra.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In Leap and the KDE desktop interface, the profiles in the console or an xterm are no longer loaded. This was detected by the midnight commander. If you switch with ALT+F1 or use lxde, for example, the midnight commander works as expected. If you run source /etc/profile.d/mc.sh beforehand, the Midnight Commander also works as expected. The Midnight Commander also works as expected under Tumbleweed. So the problem definitely only occurs under KDE and Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1203617] In plasma5 midnight commander doesn't exit to current directory anymore
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1203617 https://bugzilla.suse.com/show_bug.cgi?id=1203617#c89 --- Comment #89 from Eric Schirra <ecsos(a)schirra.net> --- So I'm slowly getting tired of working here. After my bugreport regarding the error of mc under KDE and Leap is closed again and again although I point out that the solution does not belong in the package mc, here is my last attempt. In Leap and the KDE desktop interface, the profiles in the console or an xterm are no longer loaded. This was detected by the midnight commander. If you switch with ALT+F1 or use lxde, for example, the midnight commander works as expected. If you run source /etc/profile.d/mc.sh beforehand, the Midnight Commander also works as expected. The Midnight Commander also works as expected under Tumbleweed. So the problem definitely only occurs under KDE and Leap. Here is the solution: Under Tumbleweed there is in file /etc/bash.bashrc: if test -s /etc/profile.d/mc.sh then . /etc/profile.d/mc.sh elif test -s /usr/share/mc/mc.sh then . /usr/share/mc/mc.sh fi After i put this in my bash.bashrc under Leap, mc is working as expected. After closing, you are in the last selected directory of mc and not in the start directory. This change from Tumbleweed is therefore not in the mc package. So please insert this in right package under Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232776] AUDIT-0: supergfxctl: review of D-Bus service supergfxd.service
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232776 https://bugzilla.suse.com/show_bug.cgi?id=1232776#c6 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Group|SUSE Security Internal | --- Comment #6 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- this bug can be public -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233095] yast2-storage-ng: fails to build with more recent rubygem-rspec-*
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233095 https://bugzilla.suse.com/show_bug.cgi?id=1233095#c5 --- Comment #5 from Ana Guerrero <ana.guerrero(a)suse.com> --- (In reply to Ana Guerrero from comment #4) > (In reply to José Iván López González from comment #2) > > How can I get rubygem-rspec-core-3.13.2 package for installing it locally > > and run the tests? > > Fetch it from OBS: > > https://build.opensuse.org/package/show/devel:languages:ruby:extensions/ > rubygem-rspec-expectations Sorry https://build.opensuse.org/package/show/devel:languages:ruby:extensions/rub… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233095] yast2-storage-ng: fails to build with more recent rubygem-rspec-*
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233095 https://bugzilla.suse.com/show_bug.cgi?id=1233095#c4 Ana Guerrero <ana.guerrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ana.guerrero@suse | |.com) | --- Comment #4 from Ana Guerrero <ana.guerrero(a)suse.com> --- (In reply to José Iván López González from comment #2) > How can I get rubygem-rspec-core-3.13.2 package for installing it locally > and run the tests? Fetch it from OBS: https://build.opensuse.org/package/show/devel:languages:ruby:extensions/rub… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198588] VUL-0: CVE-2022-24859: python-pypdf, python-PyPDF2: infinite loop vulnerability
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1198588 https://bugzilla.suse.com/show_bug.cgi?id=1198588#c2 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pgajdos(a)suse.com Assignee|simonf.lees(a)suse.com |security-team(a)suse.de --- Comment #2 from Petr Gajdos <pgajdos(a)suse.com> --- (In reply to Cathy Hu from comment #1) > Affected: > - openSUSE:Backports:SLE-15-SP3/python-PyPDF2 1.26.0 > - openSUSE:Backports:SLE-15-SP4/python-PyPDF2 1.26.0 Submitted: b15sp5 https://build.opensuse.org/request/show/1222741 b15sp6 https://build.opensuse.org/request/show/1222740 > - openSUSE:Factory/python-PyPDF2 1.26.0 Fixed already with version update. > - openSUSE:Backports:SLE-15-SP3/python-pypdf 1.13 Not supported anymore and not in newer backports. I think all fixed. If not, please reassign back to me. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233095] yast2-storage-ng: fails to build with more recent rubygem-rspec-*
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233095 https://bugzilla.suse.com/show_bug.cgi?id=1233095#c3 --- Comment #3 from Martin Vidner <mvidner(a)suse.com> --- I have just checked, `subvolumes` is an empty array in the passing case with older rspec -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233095] yast2-storage-ng: fails to build with more recent rubygem-rspec-*
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233095 https://bugzilla.suse.com/show_bug.cgi?id=1233095#c2 José Iván López González <jlopez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ana.guerrero@suse | |.com) CC| |ana.guerrero(a)suse.com, | |jlopez(a)suse.com --- Comment #2 from José Iván López González <jlopez(a)suse.com> --- How can I get rubygem-rspec-core-3.13.2 package for installing it locally and run the tests? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232921] New: realmd expects sssd.conf under /etc
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232921 Bug ID: 1232921 Summary: realmd expects sssd.conf under /etc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: robert.simai(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Target Milestone: --- Found By: --- Blocker: --- Current Tumbleweed. Joining a domain with realmd (0.17.1-2.4.x86_64) fails with something like "Failed to create file “/etc/sssd/sssd.conf.S9CRW2”: No such file or directory" which makes sense as the config is under /usr/etc/sssd/ nowadays. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1232458] zypper ignores /var/cache/zypp/packages/.no_auto_prune (Version 1.14.77, TW and Leap)
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232458 https://bugzilla.suse.com/show_bug.cgi?id=1232458#c1 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Michael Andres <ma(a)suse.com> --- Thanks for reporting it. Evaluation of '.no_auto_prune' broke. 'zypper lr REPO' lists the 'Keep Packages' flag, but '--details' should do it as well. We'll add it there. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232931] New: realm discover output is incomplete, missing sssd-ad
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232931 Bug ID: 1232931 Summary: realm discover output is incomplete, missing sssd-ad Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: robert.simai(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Target Milestone: --- Found By: --- Blocker: --- Domain membership fails as the discover option is missing an essential package: tw:~ # realm discover tao.test tao.test type: kerberos realm-name: TAO.TEST domain-name: tao.test configured: kerberos-member server-software: active-directory client-software: sssd required-package: sssd-tools required-package: sssd required-package: adcli required-package: samba-client login-formats: %U(a)tao.test login-policy: allow-realm-logins From the log: sssd[4560]: Could not exec /usr/libexec/sssd/sssd_pac --uid 0 --gid 0 --logger=files, reason: No such file or directory Package sssd-ad is missing from the requirements which provides /usr/libexec/sssd/sssd_pac. Without the package sssd and consequently the domain membership will fail. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221676] New: openSUSE MicroOS cannot boot up after installation from Tumbleweed
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221676 Bug ID: 1221676 Summary: openSUSE MicroOS cannot boot up after installation from Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: zluo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873628 --> https://bugzilla.suse.com/attachment.cgi?id=873628&action=edit all logs /var/log install MicroOS from Tumbleweed on my RPi 4: After installation I try to install microos_gnome_desktop without success(see blow details). Then I reboot it. But it comes to boot menu and cannot boot up and stucks forever. I tried to boot from recovery mode and it can reach to emergency mode only. -- localhost:~ # zypper in -t pattern microos_base Loading repository data... Reading installed packages... Resolving package dependencies... Problem: the to be installed pattern:microos_base-5.0-85.1.aarch64 requires 'patterns-microos-base', but this requirement cannot be provided not installable providers: patterns-microos-base-5.0-85.1.aarch64[repo-oss] Solution 1: Following actions will be done: deinstallation of product:openSUSE-20240314-0.aarch64 deinstallation of product:openSUSE-20240314-0.aarch64 deinstallation of systemd-presets-branding-openSUSE-12.2-23.3.noarch Solution 2: do not install pattern:microos_base-5.0-85.1.aarch64 Solution 3: break pattern:microos_base-5.0-85.1.aarch64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): 1 Resolving dependencies... Resolving package dependencies... The following 18 NEW packages are going to be installed: MicroOS-release MicroOS-release-appliance btrfsmaintenance busybox health-checker-plugins-MicroOS kdump kexec-tools lastlog2 liblastlog2-1 makedumpfile mandoc-bin microos-tools patterns-microos-base read-only-root-fs rebootmgr salt-transactional-update systemd-presets-branding-MicroOS wtmpdb The following NEW pattern is going to be installed: microos_base The following NEW product is going to be installed: "openSUSE MicroOS" The following 2 packages are going to be REMOVED: openSUSE-release systemd-presets-branding-openSUSE The following product is going to be REMOVED: "openSUSE Tumbleweed" 18 new packages to install, 2 to remove. Overall download size: 4.1 MiB. Already cached: 0 B. After the operation, additional 3.7 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving: MicroOS-release-appliance-20240310-2096.1.aarch64 (openSUSE-Tumbleweed-Oss) (1/18), 8.5 KiB Retrieving: MicroOS-release-appliance-20240310-2096.1.aarch64.rpm .................................................[done] Retrieving: btrfsmaintenance-0.5-2.10.noarch (openSUSE-Tumbleweed-Oss) (2/18), 36.0 KiB Retrieving: btrfsmaintenance-0.5-2.10.noarch.rpm ....................................................[done (222.1 KiB/s)] Retrieving: busybox-1.36.1-3.3.aarch64 (openSUSE-Tumbleweed-Oss) (3/18), 677.0 KiB Retrieving: busybox-1.36.1-3.3.aarch64.rpm ............................................................[done (3.5 MiB/s)] Retrieving: health-checker-plugins-MicroOS-1.10+git20240111.cb84209-1.3.noarch (openSUSE-Tumbleweed-Oss) (4/18), 10.9 KiB Retrieving: health-checker-plugins-MicroOS-1.10+git20240111.cb84209-1.3.noarch.rpm ................................[done] Retrieving: kexec-tools-2.0.28-1.1.aarch64 (openSUSE-Tumbleweed-Oss) (5/18), 116.4 KiB Retrieving: kexec-tools-2.0.28-1.1.aarch64.rpm ......................................................[done (927.1 KiB/s)] Retrieving: liblastlog2-1-1.3.1-1.1.aarch64 (openSUSE-Tumbleweed-Oss) (6/18), 17.0 KiB Retrieving: liblastlog2-1-1.3.1-1.1.aarch64.rpm ......................................................[done (60.4 KiB/s)] Retrieving: makedumpfile-1.7.4-1.3.aarch64 (openSUSE-Tumbleweed-Oss) (7/18), 274.3 KiB Retrieving: makedumpfile-1.7.4-1.3.aarch64.rpm ......................................................[done (629.2 KiB/s)] Retrieving: mandoc-bin-1.14.6-5.3.aarch64 (openSUSE-Tumbleweed-Oss) (8/18), 220.0 KiB Retrieving: mandoc-bin-1.14.6-5.3.aarch64.rpm .......................................................[done (638.1 KiB/s)] Retrieving: read-only-root-fs-1.0+git20240228.d85232a-1.1.noarch (openSUSE-Tumbleweed-Oss) (9/18), 20.9 KiB Retrieving: read-only-root-fs-1.0+git20240228.d85232a-1.1.noarch.rpm ................................[done (141.0 KiB/s)] Retrieving: rebootmgr-2.3-1.1.aarch64 (openSUSE-Tumbleweed-Oss) (10/18), 51.4 KiB Retrieving: rebootmgr-2.3-1.1.aarch64.rpm ...........................................................[done (358.5 KiB/s)] Retrieving: salt-transactional-update-3006.0-9.1.aarch64 (openSUSE-Tumbleweed-Oss) (11/18), 60.8 KiB Retrieving: salt-transactional-update-3006.0-9.1.aarch64.rpm ........................................[done (384.9 KiB/s)] Retrieving: wtmpdb-0.11.0-1.3.aarch64 (openSUSE-Tumbleweed-Oss) (12/18), 31.1 KiB Retrieving: wtmpdb-0.11.0-1.3.aarch64.rpm ...........................................................[done (180.6 KiB/s)] Retrieving: systemd-presets-branding-MicroOS-20230214-2.4.noarch (openSUSE-Tumbleweed-Oss) (13/18), 11.8 KiB Retrieving: systemd-presets-branding-MicroOS-20230214-2.4.noarch.rpm ................................[done (118.8 KiB/s)] Retrieving: MicroOS-release-20240310-2096.1.aarch64 (openSUSE-Tumbleweed-Oss) (14/18), 2.4 MiB Retrieving: MicroOS-release-20240310-2096.1.aarch64.rpm ...............................................[done (6.7 MiB/s)] Retrieving: lastlog2-1.3.1-1.1.aarch64 (openSUSE-Tumbleweed-Oss) (15/18), 24.6 KiB Retrieving: kdump-2.0.1-1.2.aarch64 (openSUSE-Tumbleweed-Oss) (16/18), 99.1 KiB Retrieving: kdump-2.0.1-1.2.aarch64.rpm .............................................................[done (265.0 KiB/s)] Retrieving: microos-tools-2.21+git12-1.1.aarch64 (openSUSE-Tumbleweed-Oss) (17/18), 25.9 KiB Retrieving: microos-tools-2.21+git12-1.1.aarch64.rpm .................................................[done (59.1 KiB/s)] Retrieving: patterns-microos-base-5.0-85.1.aarch64 (openSUSE-Tumbleweed-Oss) (18/18), 26.1 KiB Retrieving: patterns-microos-base-5.0-85.1.aarch64.rpm ...............................................[done (58.0 KiB/s)] Checking for file conflicts: ......................................................................................[done] ( 1/20) Removing openSUSE-release-20240314-2110.1.aarch64 .........................................................[done] ( 2/20) Removing systemd-presets-branding-openSUSE-12.2-23.3.noarch ...............................................[done] ( 3/20) Installing: MicroOS-release-appliance-20240310-2096.1.aarch64 .............................................[done] Created symlink /etc/systemd/system/multi-user.target.wants/btrfsmaintenance-refresh.path -> /usr/lib/systemd/system/btrfsmaintenance-refresh.path. Created symlink /etc/systemd/system/timers.target.wants/btrfs-balance.timer -> /usr/lib/systemd/system/btrfs-balance.timer. Created symlink /etc/systemd/system/timers.target.wants/btrfs-defrag.timer -> /usr/lib/systemd/system/btrfs-defrag.timer. Created symlink /etc/systemd/system/timers.target.wants/btrfs-scrub.timer -> /usr/lib/systemd/system/btrfs-scrub.timer. Created symlink /etc/systemd/system/timers.target.wants/btrfs-trim.timer -> /usr/lib/systemd/system/btrfs-trim.timer. Updating /etc/sysconfig/btrfsmaintenance ... ( 4/20) Installing: btrfsmaintenance-0.5-2.10.noarch ..............................................................[done] ( 5/20) Installing: busybox-1.36.1-3.3.aarch64 ....................................................................[done] ( 6/20) Installing: health-checker-plugins-MicroOS-1.10+git20240111.cb84209-1.3.noarch ............................[done] ( 7/20) Installing: kexec-tools-2.0.28-1.1.aarch64 ................................................................[done] ( 8/20) Installing: liblastlog2-1-1.3.1-1.1.aarch64 ...............................................................[done] ( 9/20) Installing: makedumpfile-1.7.4-1.3.aarch64 ................................................................[done] (10/20) Installing: mandoc-bin-1.14.6-5.3.aarch64 .................................................................[done] (11/20) Installing: read-only-root-fs-1.0+git20240228.d85232a-1.1.noarch ..........................................[done] (12/20) Installing: rebootmgr-2.3-1.1.aarch64 .....................................................................[done] (13/20) Installing: salt-transactional-update-3006.0-9.1.aarch64 ..................................................[done] Created symlink /etc/systemd/system/default.target.wants/wtmpdb-update-boot.service -> /usr/lib/systemd/system/wtmpdb-update-boot.service. Created symlink /etc/systemd/system/timers.target.wants/wtmpdb-rotate.timer -> /usr/lib/systemd/system/wtmpdb-rotate.timer. (14/20) Installing: wtmpdb-0.11.0-1.3.aarch64 .....................................................................[done] (15/20) Installing: systemd-presets-branding-MicroOS-20230214-2.4.noarch ..........................................[done] (16/20) Installing: MicroOS-release-20240310-2096.1.aarch64 .......................................................[done] Created symlink /etc/systemd/system/default.target.wants/lastlog2-import.service -> /usr/lib/systemd/system/lastlog2-import.service. (17/20) Installing: lastlog2-1.3.1-1.1.aarch64 ....................................................................[done] Updating /etc/sysconfig/kdump ... (18/20) Installing: kdump-2.0.1-1.2.aarch64 .......................................................................[done] (19/20) Installing: microos-tools-2.21+git12-1.1.aarch64 ..........................................................[done] (20/20) Installing: patterns-microos-base-5.0-85.1.aarch64 ........................................................[done] %posttrans(kexec-tools-2.0.28-1.1.aarch64) script output: dracut[I]: Executing: /usr/bin/dracut --kver=6.7.9-1-default -f dracut[I]: Module 'systemd-coredump' will not be installed, because command 'coredumpctl' could not be found! dracut[I]: Module 'systemd-coredump' will not be installed, because command '/usr/lib/systemd/systemd-coredump' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found! dracut[I]: Module 'systemd-pcrphase' will not be installed, because command '/usr/lib/systemd/systemd-pcrphase' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut[I]: Module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: Module 'systemd-coredump' will not be installed, because command 'coredumpctl' could not be found! dracut[I]: Module 'systemd-coredump' will not be installed, because command '/usr/lib/systemd/systemd-coredump' could not be found! dracut[I]: Module 'systemd-pcrphase' will not be installed, because command '/usr/lib/systemd/systemd-pcrphase' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: *** Including module: bash *** dracut[I]: *** Including module: systemd *** dracut[I]: *** Including module: fips *** dracut[I]: *** Including module: systemd-initrd *** dracut[I]: *** Including module: i18n *** dracut[I]: *** Including module: drm *** dracut[I]: *** Including module: health-checker *** dracut[I]: *** Including module: kernel-modules *** dracut[I]: *** Including module: kernel-modules-extra *** dracut[I]: *** Including module: resume *** dracut[I]: *** Including module: rootfs-block *** dracut[I]: *** Including module: suse-btrfs *** dracut[I]: *** Including module: suse-xfs *** dracut[I]: *** Including module: terminfo *** dracut[I]: *** Including module: udev-rules *** dracut[I]: *** Including module: securityfs *** dracut[I]: *** Including module: masterkey *** dracut[I]: *** Including module: dracut-systemd *** dracut[I]: *** Including module: integrity *** dracut[I]: *** Including module: ostree *** dracut[I]: *** Including module: selinux-microos *** dracut[I]: *** Including module: usrmount *** dracut[I]: *** Including module: base *** dracut[I]: *** Including module: fs-lib *** dracut[I]: *** Including module: shutdown *** dracut[I]: *** Including module: suse *** dracut[I]: *** Including module: suse-initrd *** dracut[I]: *** Including modules done *** dracut[I]: *** Installing kernel module dependencies *** dracut[I]: *** Installing kernel module dependencies done *** dracut[I]: *** Resolving executable dependencies *** dracut[I]: *** Resolving executable dependencies done *** dracut[I]: *** Hardlinking files *** dracut[I]: *** Hardlinking files done *** dracut[I]: *** Store current command line parameters *** dracut[I]: Stored kernel commandline: dracut[I]: rd.driver.pre=overlay dracut[I]: resume=UUID=040f3b6b-3961-46c1-a351-bd41381da55b dracut[I]: root=UUID=0280d16e-5971-4b2f-b705-317b6e96a4c3 rootfstype=ext4 rootflags=rw,noatime,nobarrier dracut[I]: *** Creating image file '/boot/initrd-6.7.9-1-default' *** dracut[I]: *** Creating initramfs image file '/boot/initrd-6.7.9-1-default' done *** %posttrans(systemd-presets-branding-MicroOS-20230214-2.4.noarch) script output: Unit /usr/lib/systemd/system/drkonqi-coredump-processor@.service is added as a dependency to a non-existent unit systemd-coredump@.service. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-init-local.service -> /usr/lib/systemd/system/cloud-init-local.service. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-final.service -> /usr/lib/systemd/system/cloud-final.service. Created symlink /etc/systemd/system/multi-user.target.wants/rebootmgr.service -> /usr/lib/systemd/system/rebootmgr.service. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-init.service -> /usr/lib/systemd/system/cloud-init.service. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-final.service -> /usr/lib/systemd/system/cloud-final.service. Created symlink /etc/systemd/system/multi-user.target.wants/rebootmgr.service -> /usr/lib/systemd/system/rebootmgr.service. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-init.service -> /usr/lib/systemd/system/cloud-init.service. Created symlink /etc/systemd/system/mdmonitor.service.wants/mdcheck_start.timer -> /usr/lib/systemd/system/mdcheck_start.timer. Created symlink /etc/systemd/system/mdmonitor.service.wants/mdcheck_continue.timer -> /usr/lib/systemd/system/mdcheck_continue.timer. Created symlink /etc/systemd/system/default.target.wants/issue-add-ssh-keys.service -> /usr/lib/systemd/system/issue-add-ssh-keys.service. Created symlink /etc/systemd/system/multi-user.target.wants/man-db-create.service -> /usr/lib/systemd/system/man-db-create.service. Created symlink /etc/systemd/system/mdmonitor.service.wants/mdmonitor-oneshot.timer -> /usr/lib/systemd/system/mdmonitor-oneshot.timer. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-config.service -> /usr/lib/systemd/system/cloud-config.service. Created symlink /etc/systemd/system/default.target.wants/health-checker.service -> /usr/lib/systemd/system/health-checker.service. Created symlink /etc/systemd/system/timers.target.wants/container-image-prune.timer -> /usr/lib/systemd/system/container-image-prune.timer. Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service -> /usr/lib/systemd/system/kubelet.service. Created symlink /etc/systemd/user/sockets.target.wants/drkonqi-coredump-launcher.socket -> /usr/lib/systemd/user/drkonqi-coredump-launcher.socket. %posttrans(microos-tools-2.21+git12-1.1.aarch64) script output: /usr/lib/tmpfiles.d/inn.conf:1: Line references path below legacy directory /var/run/, updating /var/run/news → /run/news; please update the tmpfiles.d/ drop-in file accordingly. /usr/lib/tmpfiles.d/nagios.conf:2: Line references path below legacy directory /var/run/, updating /var/run/nagios → /run/nagios; please update the tmpfiles.d/ drop-in file accordingly. Running post-transaction scripts ..................................................................................localhost:~ # zypper se microos_gnome_desktop Loading repository data... Reading installed packages... S | Name | Summary | Type --+-----------------------+-----------------------+-------- | microos_gnome_desktop | MicroOS GNOME Desktop | pattern localhost:~ # zypper se -t microos_gnome_desktop The flag type is not compatible with argument microos_gnome_desktop (Unknown package type). localhost:~ # zypper se microos_gnome_desktop Loading repository data... Reading installed packages... S | Name | Summary | Type --+-----------------------+-----------------------+-------- | microos_gnome_desktop | MicroOS GNOME Desktop | pattern localhost:~ # zypper in -t microos_gnome_desktop The flag type is not compatible with argument microos_gnome_desktop (Unknown package type). localhost:~ # reboot -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1233086] New: Cannot boot MicroOS after Slowroll to Microos repo
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233086 Bug ID: 1233086 Summary: Cannot boot MicroOS after Slowroll to Microos repo 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: kokeko(a)mac.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I change MicroOS-Slowroll to tumbleweed. Before cat /etc/os-release NAME="openSUSE MicroOS-Slowroll" # VERSION="20241002" ID="opensuse-microos" ID_LIKE="suse opensuse opensuse-tumbleweed microos sl-micro" VERSION_ID="20241002" PRETTY_NAME="openSUSE MicroOS-Slowroll" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:microos:20241002" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:MicroOS" LOGO="distributor-logo-MicroOS" install openSUSE-repos-MicroOS package (remove openSUSE-repos-Slowroll) reboot and transactional-update dup, reboot again, my machine does not boot. I check systemd log on display, cannot reach multi-user.target, reboot soon? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1233095] yast2-storage-ng: fails to build with more recent rubygem-rspec-*
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233095 https://bugzilla.suse.com/show_bug.cgi?id=1233095#c1 Martin Vidner <mvidner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner(a)suse.com --- Comment #1 from Martin Vidner <mvidner(a)suse.com> --- [ 107s] Failures: [ 107s] [ 107s] 1) Y2Partitioner::Widgets::Pages::Disks#contents when some of the devices to show are formatted as Btrfs and the Btrfs is multidevice does not include its Btrfs subvolumes in the table [ 107s] Failure/Error: expect(items).to_not include(*subvolumes) [ 107s] [ 107s] ArgumentError: [ 107s] include() is not supported, please supply an argument [ 107s] # ./test/y2partitioner/widgets/pages/disks_test.rb:98:in `block (5 levels) in <top (required)>' Likely cause: https://github.com/rspec/rspec-expectations/blob/838952dc1416c943e7933684c4… 3.13.2 / 2024-08-20 Bug Fixes: Raise an error when passing no arguments to the include matcher. (Eric Mueller, #1479) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232727] [Build 20241101] openQA test fails in boot_encrypt: no decrypt prompt
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232727 https://bugzilla.suse.com/show_bug.cgi?id=1232727#c25 --- Comment #25 from Cliff Zhao <qzhao(a)suse.com> --- Hi Thomas: I think this modification to release bochs from framebuffer forcing could ease this openQA test failure. [1]. https://build.opensuse.org/package/show/home:qzhao:branches:openSUSE:Factor… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233054] AUDIT-0: deepin-system-monitor: new policykit profiles of deepin-system-monitor
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233054 https://bugzilla.suse.com/show_bug.cgi?id=1233054#c2 --- Comment #2 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- We will look into this and the other deepin AUDITs, but we currently have different priorities. I hope to be able to deal with deepin in a couple of weeks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233054] AUDIT-0: deepin-system-monitor: new policykit profiles of deepin-system-monitor
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233054 https://bugzilla.suse.com/show_bug.cgi?id=1233054#c1 --- Comment #1 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- *** Bug 1233053 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233053] AUDIT-0: deepin-system-monitor: new policykit profiles of deepin-system-monitor
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233053 https://bugzilla.suse.com/show_bug.cgi?id=1233053#c1 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias.gerstner(a)suse.com Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #1 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- This has been created twice. *** This bug has been marked as a duplicate of bug 1233054 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233016] memory buff/cache issue with qemu
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233016 https://bugzilla.suse.com/show_bug.cgi?id=1233016#c2 --- Comment #2 from Vlastimil Babka <vbabka(a)suse.com> --- If kernel 6.10.9-1-default is OK, which kernel is not OK, is it 6.11.x? Can you attach the output of cat /proc/meminfo from the bad kernel at the point the memory/swap is considered full? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232835] AUDIT-0: upower: Review of new polkit policy (battery charge limit)
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232835 https://bugzilla.suse.com/show_bug.cgi?id=1232835#c2 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trenn(a)suse.com --- Comment #2 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- *** Bug 1233080 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233016] memory buff/cache issue with qemu
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233016 https://bugzilla.suse.com/show_bug.cgi?id=1233016#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhocko(a)suse.com, | |tiwai(a)suse.com, | |vbabka(a)suse.com Component|Kernel:Storage |Kernel Assignee|kernel-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Sounds rather like a MM issue. Adding relevant people to Cc. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230946] Can not update transactional-update on updated 6.0, transactional-update (System package)
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230946 Santiago Zarate <santiago.zarate(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |santiago.zarate(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233095] New: yast2-storage-ng: fails to build with more recent rubygem-rspec-*
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233095 Bug ID: 1233095 Summary: yast2-storage-ng: fails to build with more recent rubygem-rspec-* Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: yast2-maintainers(a)suse.de Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878451 --> https://bugzilla.suse.com/attachment.cgi?id=878451&action=edit yast2-storage-ng There are a more recent version of the rubygem-rspec-* rubygems in staging and yast2-storage-ng fails to build with them. See attached log. Everything is currently in Staging:F https://build.opensuse.org/staging_workflows/openSUSE:Factory/staging_proje… but this can change at any moment. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233086] Cannot boot MicroOS after Slowroll to Microos repo
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233086 https://bugzilla.suse.com/show_bug.cgi?id=1233086#c3 --- Comment #3 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Michiya Hagimoto from comment #0) > I change MicroOS-Slowroll to tumbleweed. Where did you find installation medias for "MicroOS-Slowroll"? This does not exist, this doesn't even make any sense. So no, there is no way to migrate from Slowroll to MicroOS, like there is no way to migrate from Tumbleweed to MicroOS. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227389] PackageKit kernel update is successful but kernel is not updated
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227389 https://bugzilla.suse.com/show_bug.cgi?id=1227389#c11 --- Comment #11 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2024:3947-1: An update that has one fix can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-ru-20243947-1 Category: recommended (moderate) Bug References: 1227389 Maintenance Incident: [SUSE:Maintenance:35870](https://smelt.suse.de/incident/35870/) Sources used: openSUSE Leap 15.6 (src): PackageKit-1.2.8-150600.4.8.2, PackageKit-branding-SLE-12.0-150600.22.7.3 Desktop Applications Module 15-SP6 (src): PackageKit-1.2.8-150600.4.8.2, PackageKit-branding-SLE-12.0-150600.22.7.3 SUSE Linux Enterprise Workstation Extension 15 SP6 (src): PackageKit-1.2.8-150600.4.8.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232920] python313+314: nogil test fails on 1-core-VM
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232920 Daniel Garcia <daniel.garcia(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|python-maintainers(a)suse.com |daniel.garcia(a)suse.com CC| |daniel.garcia(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228173] sssd: getsubids throws `libsubid_sss.so did not provide @subid_free@`
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228173 https://bugzilla.suse.com/show_bug.cgi?id=1228173#c4 Samuel Cabrero <scabrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(scabrero(a)suse.com | |) | Depends on| |1230051 --- Comment #4 from Samuel Cabrero <scabrero(a)suse.com> --- (In reply to Dylan Meysmans from comment #3) > (In reply to Samuel Cabrero from comment #2) > > Fixed in sssd 2.10 beta2. > > When can we expect sssd 2.10 to arrive for Tumbleweed? I see it is already > in network:ldap. It will arrive soon, the OBS request is in place: https://build.opensuse.org/requests/1222104. Will need to wait for https://bugzilla.suse.com/show_bug.cgi?id=1230051, though. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203617] In plasma5 midnight commander doesn't exit to current directory anymore
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1203617 https://bugzilla.suse.com/show_bug.cgi?id=1203617#c88 --- Comment #88 from Christophe Marin <christophe(a)krop.fr> --- *** Bug 1233087 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232991] New: VUL-0: CVE-2024-51744: coredns: 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 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232991 Bug ID: 1232991 Summary: VUL-0: CVE-2024-51744: coredns: 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: andrea.manzini(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 4

[Bug 1228863] System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c60 --- Comment #60 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Artur Kaufmann from comment #59) > Maybe the revision of the TPM2.0 chip is also important This is true, as older revisions does not recognize NVIndex that are also required. > > sudo tpm2_getcap properties-fixed | grep TPM2_PT_REVISION -A2 > > TPM2_PT_REVISION: > > raw: 0x8A > > value: 1.38 > > BR For sdbootutil I can fallback to pcr-oracle (signed policies). We are doing this when NVIndex fail, but a fail in PolicyOR is no detected until much (much) later. The check for the revision is a really good idea, but is hard to put it as a strong threshold, as I am not sure that the number of branches is part of the specification document (I did not see it at first glance) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227420] openSUSE missing fi keymap vs. fi-kotoistus
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227420 https://bugzilla.suse.com/show_bug.cgi?id=1227420#c37 --- Comment #37 from Jarkko Torvinen <jarkko.torvinen(a)iki.fi> --- Created attachment 878450 --> https://bugzilla.suse.com/attachment.cgi?id=878450&action=edit aeon-gnome-initial-setup-keymap-dialog -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227420] openSUSE missing fi keymap vs. fi-kotoistus
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227420 https://bugzilla.suse.com/show_bug.cgi?id=1227420#c36 --- Comment #36 from Jarkko Torvinen <jarkko.torvinen(a)iki.fi> --- Hi again, Aeon 20241106 installer is fixed and was able to try. Attaching aeon-gnome-initial-setup-keymap-dialog.png which shows the important part of setup process Aeon with Finnish(official)/fi-kotoistus: - gdm keymap works - gnome keymap works - console keymap works resulting /etc/vconsole.conf: # Written by systemd-localed(8) or systemd-firstboot(1), read by systemd-localed # and systemd-vconsole-setup(8). Use localectl(1) to update this file. FONT=eurlatgr.psfu KEYMAP=fi-kotoistus XKBLAYOUT=fi XKBVARIANT=kotoistus Aeon with Finnish/fi: - gdm keymap works - gnome keymap works - console keymap is wrong, us? - systemd-vconsole-setup.service fails resulting /etc/vconsole.conf: # Written by systemd-localed(8) or systemd-firstboot(1), read by systemd-localed # and systemd-vconsole-setup(8). Use localectl(1) to update this file. FONT=eurlatgr.psfu KEYMAP=fi XKBLAYOUT=fi So this is bad if you need to input recovery key for disk encryptio that uses "-" which is different key between us and fi layouts. Tried to install kbd-legacy: sudo transactional-update pkg install kbd-legacy sudo transactional-update initrd Now systemd-vconsole-setup succeeds, but keymap is still us The problem is that "Finnish" option is still there in gnome, also in TW keyboard settings (does not break things as only affects gnome). And that its the first option in gnome initial setup, its the obvious choice, as we have always been using simply "Finnish" or "fi". These kotoistus, official, classic, whatever, is not what I would pick, I have no idea what the reason for others is there to exist. There is generally only single "Finnish" layout. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230946] New: Can not update transactional-update on updated 6.0, transactional-update (System package)
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230946 Bug ID: 1230946 Summary: Can not update transactional-update on updated 6.0, transactional-update (System package) Classification: openSUSE Product: openSUSE Leap Micro Version: 6.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Transactional Update Assignee: lubos.kocman(a)suse.com Reporter: kokeko(a)mac.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My Leap Micro 6.0 usystem update from 5.6, cannot find transactional-update package. zypper se -si transactional-update Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+----------------------------------+---------+-----------+--------+------------------ i | dracut-transactional-update | package | 4.6.6-1.1 | noarch | (System Packages) i+ | transactional-update | package | 4.6.6-1.1 | x86_64 | (System Packages) i | transactional-update-zypp-config | package | 4.6.6-1.1 | noarch | (System Packages) transactional-update cannot find from repo. I search directly repo folder. https://download.opensuse.org/distribution/leap-micro/6.0/product/repo/open… find. https://download.opensuse.org/distribution/leap-micro/6.0/product/repo/open… anything wrong to my operation? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1230257] New: SeaMonkey: update to 2.53.19
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230257 Bug ID: 1230257 Summary: SeaMonkey: update to 2.53.19 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de CC: factory-mozilla(a)lists.opensuse.org, linux(a)daniel-bauer.com, maintenance(a)opensuse.org, Manfred.Haertel(a)rz-online.de, meissner(a)suse.com, qa-bugs(a)suse.de, security-team(a)suse.de, wolfgang.engel(a)suse.com Depends on: 1222137 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1222137 +++ Please update the SeaMonkey package in 15.5 and 15.6 to the SeaMonkey 2.53.18.9 packages provided by the mozilla/seamonkey package on OBS: <https://build.opensuse.org/package/show/mozilla/seamonkey> The latest version of SeaMonkey, 2.53.18.9, released on 4 September 2024, contains new backports of important security fixes from Firefox 115.14 and Thunderbird 115.14 ESR. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1232906] ppc64(le) isn't building the latest bpftrace due unresolvable lldb-devel
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232906 https://bugzilla.suse.com/show_bug.cgi?id=1232906#c10 --- Comment #10 from Aaron Puchert <aaronpuchert(a)alice-dsl.net> --- (In reply to Aaron Puchert from comment #9) > If it wasn't a BuildRequires, you could have used %_llvm_with_lldb. But > build requirements are resolved before we have access to macros defined in > packages. (I think. But I didn't try if OBS provides them if dependencies > are listed in order.) Although llvmN-devel has an ominous "Provides: rpm_macro(_llvm_with_lldb)". Maybe OBS can use this? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232906] ppc64(le) isn't building the latest bpftrace due unresolvable lldb-devel
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232906 Aaron Puchert <aaronpuchert(a)alice-dsl.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(aaronpuchert@alic | |e-dsl.net) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233011] New: [TW] SSH not creating user session
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233011 Bug ID: 1233011 Summary: [TW] SSH not creating user session 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: dev.dorrejo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, TW - Latest Snapshot. I just did a fresh install in a server and found that Loging to the user from SSH is not creating the session nor dbus, so when trying to work with container, systemd, and loginctl appear the user is not existent. What it must happens is: - When connecting through ssh to the machine, a XDG_RUNTIME or user-slice session must be started, which is not happening. loginctl: https://forums.opensuse.org/uploads/default/original/3X/8/3/839eaf47e96e461… systemd: https://forums.opensuse.org/uploads/default/original/3X/a/2/a21b19383dd0bab… podman: https://forums.opensuse.org/uploads/default/original/3X/e/a/ea5bb7885009ec0… Looking into what service exist: https://forums.opensuse.org/uploads/default/original/3X/5/4/54b0e0b0c667cc2… my sshd_config: ``` Port 22 ListenAddress 0.0.0.0 LogLevel VERBOSE # Strong encryption settings Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes256-ctr MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com KexAlgorithms curve25519-sha256,curve25519-sha256(a)libssh.org,diffie-hellman-group18-sha512 # Key exchange algorithms HostKeyAlgorithms ssh-ed25519,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01(a)openssh.com # Authentication settings PermitRootLogin prohibit-password PasswordAuthentication no ChallengeResponseAuthentication no AuthenticationMethods publickey # Enable only key-based login AuthorizedKeysFile .ssh/authorized_keys # Additional security settings AllowTcpForwarding yes AllowAgentForwarding no StrictModes yes IgnoreRhosts yes X11Forwarding no PermitTunnel no MaxAuthTries 2 UseDNS no PermitUserEnvironment no # Client keep-alive ClientAliveInterval 15 ClientAliveCountMax 6 # Strict HostKey settings HostKey /etc/ssh/ssh_host_ecdsa_key HostKey /etc/ssh/ssh_host_ed25519_key ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1232906] ppc64(le) isn't building the latest bpftrace due unresolvable lldb-devel
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232906 https://bugzilla.suse.com/show_bug.cgi?id=1232906#c9 --- Comment #9 from Aaron Puchert <aaronpuchert(a)alice-dsl.net> --- (In reply to Petr Vorel from comment #8) > You asked me to add it also to llvm19 (I did it wrongly only to llvm > metapackage in [1]). That wasn't wrong, just insufficient. The package would have been unresolvable. > Also, if it for any reason does not make sense to enable it for either > ppc64le or s390x, it's good to know that llvm is optional. I suppose just to > wrap "BuildRequires: lldb%{llvm_major_version}-devel" in bpftrace with > %ifarch aarch64 x86_64 (or whatever will endup having lldb-devel) would be > enough. If it wasn't a BuildRequires, you could have used %_llvm_with_lldb. But build requirements are resolved before we have access to macros defined in packages. (I think. But I didn't try if OBS provides them if dependencies are listed in order.) So I guess we'll have to bite the bullet and hardcode the architectures. Newer RPM supports %generate_buildrequires, but I have no experience with that. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228863] New: System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 Bug ID: 1228863 Summary: System asking for recovery key while booting a default mode encrypted Aeon system after automatic update Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Transactional Update Assignee: rbrown(a)suse.com Reporter: happymab.dev(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When I booted the system after the automatic update on 04 Aug 2024, the system asked for the recovery key. I booted the system using the recovery key and tried the following to fix the issue: - sudo sdbootutil update-predictions - sudo sdbootutil --ask-pin update-predictions - Clear TPM in BIOS and run sudo sdbootutil --ask-pin update-predictions None of the above actions fixed the issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 29

[Bug 1230906] python312: has some mtime based .pyc files
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230906 https://bugzilla.suse.com/show_bug.cgi?id=1230906#c14 --- Comment #14 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2024:3945-1: An update that solves one vulnerability and has one security fix can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-su-20243945-1 Category: security (moderate) Bug References: 1230906, 1232241 CVE References: CVE-2024-9287 Maintenance Incident: [SUSE:Maintenance:36307](https://smelt.suse.de/incident/36307/) Sources used: openSUSE Leap 15.3 (src): python39-core-3.9.20-150300.4.55.2, python39-documentation-3.9.20-150300.4.55.1, python39-3.9.20-150300.4.55.1 openSUSE Leap 15.5 (src): python39-core-3.9.20-150300.4.55.2, python39-documentation-3.9.20-150300.4.55.1, python39-3.9.20-150300.4.55.1 openSUSE Leap 15.6 (src): python39-core-3.9.20-150300.4.55.2, python39-documentation-3.9.20-150300.4.55.1, python39-3.9.20-150300.4.55.1 Legacy Module 15-SP5 (src): python39-core-3.9.20-150300.4.55.2, python39-3.9.20-150300.4.55.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228863] System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c58 --- Comment #58 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Artur Kaufmann from comment #57) > Created attachment 878444 [details] > Attached you can find all actions, as update-predictions failed and the TPM > stays locked. Thanks a lot. As I see the re-enrollment worked. I understand that now the system boot without asking the password? What is more interesting is now 2 entries where selected and no PolicyOR error was present. My working theory now is that there are TPM2s with different limits of PolicyOR branches. Some are 8, other 4, and yours seem to be 2. > BR -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228863] System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c57 --- Comment #57 from Artur Kaufmann <arturkaufmann(a)gmail.com> --- Created attachment 878444 --> https://bugzilla.suse.com/attachment.cgi?id=878444&action=edit Cleaned pcrlock.d & update-predictions + unenroll & enroll (In reply to Alberto Planas Dominguez from comment #56) > Artur, thanks for the information. > > As I see only three entries are selected, and this should be OK to not > exceed the limitations of PolicyOR. > > Try this: > > # Clean the predictions and update the predictions: > rm -fr /var/lib/pcrlock.d > sdbootutil -v --ask-pin update-predictions > > This will ask the recovery PIN / recovery key (was presented during the > installation). If the recovery PIN is not working anymore, you would need to > re-enroll: > > sdbootutil unenroll --method=tpm2 > sdbootutil enroll --method=tpm2 > > Is this working now? If works, can you attach again the content for > /var/lib/pcrlock.d? Attached you can find all actions, as update-predictions failed and the TPM stays locked. BR -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232851] proton-vpn-4.3.2-1.1.noarch not installable
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232851 Alexander van Kaam <alexvkaam(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexvkaam(a)gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228863] System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c56 --- Comment #56 from Alberto Planas Dominguez <aplanas(a)suse.com> --- Arthur, thanks for the information. As I see only three entries are selected, and this should be OK to not exceed the limitations of PolicyOR. Try this: # Clean the predictions and update the predictions: rm -fr /var/lib/pcrlock.d sdbootutil -v --ask-pin update-predictions This will ask the recovery PIN / recovery key (was presented during the installation). If the recovery PIN is not working anymore, you would need to re-enroll: sdbootutil unenroll --method=tpm2 sdbootutil enroll --method=tpm2 Is this working now? If works, can you attach again the content for /var/lib/pcrlock.d? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228863] System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c55 --- Comment #55 from Artur Kaufmann <arturkaufmann(a)gmail.com> --- Created attachment 878443 --> https://bugzilla.suse.com/attachment.cgi?id=878443&action=edit find /var/lib/pcrlock.d/ Additionally > sudo sdbootutil list-entries > opensuse-aeon-6.11.6-2-default-169.conf > opensuse-aeon-6.11.6-2-default-168.conf > opensuse-aeon-6.11.5-2-default-167.conf > opensuse-aeon-6.11.5-2-default-166.conf > opensuse-aeon-6.11.5-2-default-165.conf > opensuse-aeon-6.11.5-2-default-164.conf > opensuse-aeon-6.11.5-2-default-163.conf > opensuse-aeon-6.11.5-1-default-162.conf > opensuse-aeon-6.11.5-1-default-160.conf > opensuse-aeon-6.11.5-1-default-157.conf > opensuse-aeon-6.11.5-1-default-156.conf > opensuse-aeon-6.11.5-1-default-155.conf > opensuse-aeon-6.11.5-1-default-152.conf > opensuse-aeon-6.11.5-1-default-150.conf > opensuse-aeon-6.11.3-2-default-148.conf > opensuse-aeon-6.11.3-2-default-147.conf -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228173] sssd: getsubids throws `libsubid_sss.so did not provide @subid_free@`
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228173 https://bugzilla.suse.com/show_bug.cgi?id=1228173#c3 Dylan Meysmans <contact(a)mettekou.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scabrero(a)suse.com Flags| |needinfo?(scabrero(a)suse.com | |) --- Comment #3 from Dylan Meysmans <contact(a)mettekou.com> --- (In reply to Samuel Cabrero from comment #2) > Fixed in sssd 2.10 beta2. When can we expect sssd 2.10 to arrive for Tumbleweed? I see it is already in network:ldap. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228863] System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c54 --- Comment #54 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Artur Kaufmann from comment #52) > Created attachment 878441 [details] > sdbootutil -v update-predictions after update to Version 20241105 > > Hi all, > > I think I've got the same issue, after updating to Version 20241105 (see > attached log file). Can you do also `sdbootutil list-entries` ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228863] System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c53 --- Comment #53 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Artur Kaufmann from comment #52) > Created attachment 878441 [details] > sdbootutil -v update-predictions after update to Version 20241105 > pcrlock.d shows following content: > > ls -l /var/lib/pcrlock.d/ Can you do a find /var/lib/pcrlock.d ? There are directories that I would like to see the full content. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1229122] New: go1.23 release tracking
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1229122 Bug ID: 1229122 Summary: go1.23 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- go1.23 (expected August 2024) is a major release of Go. Minor releases of go1.23.x will be provided through August 2025. This issue tracks go1.23.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1219988] New: go1.20,go1.21,go1.22: ensure VERSION file is present in go1.x toolchain GOROOT
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1219988 Bug ID: 1219988 Summary: go1.20,go1.21,go1.22: ensure VERSION file is present in go1.x toolchain GOROOT Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- go1.x tool 'go tool dist' and 'go tool distpack' require the source file VERSION to be present in GOROOT. Current go1.x packaging is missing this file, ensure it is present. Example: $ go version go1.22.0 linux/amd64 $ go tool dist list go tool dist: FAILED: not a Git repo; must put a VERSION file in $GOROOT $ go tool distpack distpack: open /usr/lib64/go/1.22/VERSION: no such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218424] New: go1.22 release tracking
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1218424 Bug ID: 1218424 Summary: go1.22 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- go1.22 (expected February 2024) is a major release of Go. Minor releases of go1.22.x will be provided through February 2025. This issue tracks go1.22.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1215090] New: go1.20,go1.21: Go toolchain packages missing src/cmd/vendor/github.com/google/pprof/internal/driver/html/
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215090 Bug ID: 1215090 Summary: go1.20,go1.21: Go toolchain packages missing src/cmd/vendor/github.com/google/pprof/internal/driver /html/ Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Include the missing directory src/cmd/vendor/github.com/google/pprof/internal/driver/html/ in our go1.1x toolchain packages. This will fix failing builds with applications that directly import runtime/pprof e.g. kubeconform which failed to build with the following error: /usr/lib64/go/1.21/src/cmd/vendor/github.com/google/pprof/internal/driv er/webhtml.go:26:12: pattern html: no matching files found Upstream Go sources vendor certain tools including the pprof profiler [1]. pprof has an asset directory pprof/internal/driver/html containing only html templates used by the pprof viewer and no Go source code. Our go packaging tries to be conservative in what we include in the RPM, and with our find/glob patterns this directory has never been included in the packaging. The issue was first reported with go1.21. However, the last vendoring update was for go1.20, so we will include the fix in go1.20 packaging as well: bb917bd 2022-11-22 09:39 cmd/vendor: update vendored github.com/google/pprof for Go 1.20 release [1] https://github.com/google/pprof -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1210963] Go toolchain packages use Suggests: for optional subpackages to reduce default install
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1210963 https://bugzilla.suse.com/show_bug.cgi?id=1210963#c12 --- Comment #12 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1210963) was mentioned in https://build.opensuse.org/request/show/1222529 Backports:SLE-12 / go1.19 https://build.opensuse.org/request/show/1222530 Backports:SLE-12 / go1.20 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210938] Go application packages re-enable stripping and debuginfo
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1210938 https://bugzilla.suse.com/show_bug.cgi?id=1210938#c20 --- Comment #20 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1210938) was mentioned in https://build.opensuse.org/request/show/1222529 Backports:SLE-12 / go1.19 https://build.opensuse.org/request/show/1222530 Backports:SLE-12 / go1.20 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206346] go1.20 release tracking
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1206346 https://bugzilla.suse.com/show_bug.cgi?id=1206346#c83 --- Comment #83 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1206346) was mentioned in https://build.opensuse.org/request/show/1222530 Backports:SLE-12 / go1.20 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200441] go1.19 release tracking
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1200441 https://bugzilla.suse.com/show_bug.cgi?id=1200441#c85 --- Comment #85 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1200441) was mentioned in https://build.opensuse.org/request/show/1222529 Backports:SLE-12 / go1.19 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198427] VUL-0: CVE-2022-27536: go1.17,go1.18: crypto/x509: Certificate.Verify crash on macOS with Go 1.18
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1198427 https://bugzilla.suse.com/show_bug.cgi?id=1198427#c12 --- Comment #12 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1198427) was mentioned in https://build.opensuse.org/request/show/1222528 Backports:SLE-12 / go1.18 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198423] VUL-0: CVE-2022-24675: go1.17,go1.18: encoding/pem: stack overflow
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1198423 https://bugzilla.suse.com/show_bug.cgi?id=1198423#c10 --- Comment #10 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1198423) was mentioned in https://build.opensuse.org/request/show/1222528 Backports:SLE-12 / go1.18 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198424] VUL-0: CVE-2022-28327: go1.17,go1.18: crypto/elliptic: tolerate all oversized scalars in generic P-256
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1198424 https://bugzilla.suse.com/show_bug.cgi?id=1198424#c10 --- Comment #10 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1198424) was mentioned in https://build.opensuse.org/request/show/1222528 Backports:SLE-12 / go1.18 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193742] go1.18 release tracking
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1193742 https://bugzilla.suse.com/show_bug.cgi?id=1193742#c48 --- Comment #48 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1193742) was mentioned in https://build.opensuse.org/request/show/1222528 Backports:SLE-12 / go1.18 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233079] New: zipl errors out: Unsupported setup: data starts at boot area on (254:0)
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233079 Bug ID: 1233079 Summary: zipl errors out: Unsupported setup: data starts at boot area on (254:0) Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- see also bug#1230345 for the setup. s390zl21:~ # zipl -c /boot2/zipl.conf Using config file '/boot2/zipl.conf' (from command line) Run /lib/s390-tools/zipl_helper.device-mapper 254:0 Error: Unsupported setup: data starts at boot area on (254:0) Error: Inconsistent script output mountpoint /boot2: /dev/mapper/3600507630bffd2160000000000002000 4120288 352624 3557952 10% /boot2 s390zl21:~ # multipath -ll 3600507630bffd2160000000000002000 3600507630bffd2160000000000002000 dm-0 IBM,2107900 size=4.0G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 0:0:1:1073758240 sda 8:0 active ready running `- 1:0:1:1073758240 sdh 8:112 active ready running -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228863] System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c52 Artur Kaufmann <arturkaufmann(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #876485|0 |1 is obsolete| | --- Comment #52 from Artur Kaufmann <arturkaufmann(a)gmail.com> --- Created attachment 878441 --> https://bugzilla.suse.com/attachment.cgi?id=878441&action=edit sdbootutil -v update-predictions after update to Version 20241105 Hi all, I think I've got the same issue, after updating to Version 20241105 (see attached log file). pcrlock.d shows following content: > ls -l /var/lib/pcrlock.d/ > drwxr-xr-x. 1 root root 34 21. Okt 21:19 240-secureboot-policy.pcrlock.d > drwxr-xr-x. 1 root root 34 21. Okt 21:19 250-firmware-code-early.pcrlock.d > drwxr-xr-x. 1 root root 34 21. Okt 21:19 250-firmware-config-early.pcrlock.d > drwxr-xr-x. 1 root root 34 21. Okt 21:19 550-firmware-code-late.pcrlock.d > drwxr-xr-x. 1 root root 34 21. Okt 21:19 550-firmware-config-late.pcrlock.d > drwxr-xr-x. 1 root root 34 21. Okt 21:19 600-gpt.pcrlock.d > drwxr-xr-x. 1 root root 34 21. Okt 21:19 620-secureboot-authority.pcrlock.d > drwxr-xr-x. 1 root root 34 21. Okt 21:19 630-shim-efi-application.pcrlock.d > drwxr-xr-x. 1 root root 34 21. Okt 21:19 640-boot-loader-efi-application.pcrlock.d > -rw-r--r--. 1 root root 494 7. Nov 18:05 641-sdboot-loader-conf.pcrlock > drwxr-xr-x. 1 root root 60 23. Okt 00:04 650-kernel-efi-application.pcrlock.d > drwxr-xr-x. 1 root root 102 25. Okt 08:09 710-kernel-cmdline-boot-loader.pcrlock.d > drwxr-xr-x. 1 root root 144 25. Okt 08:09 710-kernel-cmdline-initrd-entry.pcrlock.d On boot there was an error message, after Starting Cryptography Setup for aeon-root with following content: > tpm tpm0: invalid TPM_STS.x 0xff, dumping stack for forensics -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233076] New: [hypre] Bad comment in HYPREConfig.cmake
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233076 Bug ID: 1233076 Summary: [hypre] Bad comment in HYPREConfig.cmake Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: zed.three(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The hypre-devel package is on 2.20, where the CMake config file /usr/lib64/cmake/HYPRE/HYPREConfig.cmake starts with a bad comment: ``` /****************************************************************************** * Copyright 1998-2019 Lawrence Livermore National Security, LLC and other * HYPRE Project Developers. See the top-level COPYRIGHT file for details. * * SPDX-License-Identifier: (Apache-2.0 OR MIT) ******************************************************************************/ ####### Expanded from @PACKAGE_INIT@ by configure_package_config_file() ####### ####### Any changes to this file will be overwritten by the next CMake run #### ``` This is fixed in 2.21. Please could the package be updated to a more recent version? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227049] VUL-0: CVE-2024-6104: minikube: hashicorp/go-retryablehttp: url might write sensitive information to log file
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227049 https://bugzilla.suse.com/show_bug.cgi?id=1227049#c2 Andrea Mattiazzo <andrea.mattiazzo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(carlos.lopez@suse | |.com) | --- Comment #2 from Andrea Mattiazzo <andrea.mattiazzo(a)suse.com> --- Factory is fixed. (0.7.7) Only backports needs an update: openSUSE:Backports:SLE-15-SP5/minikube github.com/hashicorp/go-retryablehttp (0.7.2) openSUSE:Backports:SLE-15-SP6/minikube github.com/hashicorp/go-retryablehttp (0.7.4) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227005] VUL-0: CVE-2024-3817: minikube: hashicorp/go-getter: argument injection when fetching remote default git branches
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227005 https://bugzilla.suse.com/show_bug.cgi?id=1227005#c2 --- Comment #2 from Andrea Mattiazzo <andrea.mattiazzo(a)suse.com> --- Affected Products / Versions: go-getter 1.5.9 up to 1.7.3; fixed in 1.7.4 openSUSE:Factory is at 1.7.6 so already fixed. openSUSE:Backports:SLE-15-SP6/minikube and openSUSE:Backports:SLE-15-SP5/minikube still needs an update. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227017] VUL-0: CVE-2024-6257: minikube: hashicorp/go-getter: Arbitrary command execution through local git config file
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227017 https://bugzilla.suse.com/show_bug.cgi?id=1227017#c3 Andrea Mattiazzo <andrea.mattiazzo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #3 from Andrea Mattiazzo <andrea.mattiazzo(a)suse.com> --- Errata: openSUSE:Backports:SLE-15-SP6/minikube and openSUSE:Backports:SLE-15-SP5/minikube still needs an update. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227017] VUL-0: CVE-2024-6257: minikube: hashicorp/go-getter: Arbitrary command execution through local git config file
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227017 https://bugzilla.suse.com/show_bug.cgi?id=1227017#c2 Andrea Mattiazzo <andrea.mattiazzo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Flags|needinfo?(carlos.lopez@suse | |.com) | Resolution|--- |FIXED --- Comment #2 from Andrea Mattiazzo <andrea.mattiazzo(a)suse.com> --- I think so, closing it as FIXED. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230425] New: Using shorter name of build root folder can build out a smaller ovmf image
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230425 Bug ID: 1230425 Summary: Using shorter name of build root folder can build out a smaller ovmf image Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: jlee(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This situation be found when I am porting edk2-stable202405 ovmf to Tumbleweed. The built out FV image size is too big for FD_SIZE_2MB config. It shows the following build error on OBS: Generating PEIFV FV ### Generating DXEFV FV ############ ['GenFv', '-a', '/home/joeyli/tmp/tmp/edk2-edk2-stable202405/Build/OvmfX64/DEBUG_GCC5/FV/Ffs/FVMAIN_COMPACT.inf', '-o', '/home/joeyli/tmp/tmp/edk2-edk2-stable202405/Build/OvmfX64/DEBUG_GCC5/FV/FVMAI Return Value = 2 GenFv: ERROR 3000: Invalid the required fv image size 0x1ac300 exceeds the set fv image size 0x1ac000 This error can also be reproduced by local build. Then I start to checking the binary of *.ffs files which are the source of FV image. e.g. Build/OvmfX64/DEBUG_GCC5/FV/Ffs/D6A2CB7F-6A18-4e2f-B43B-9920A733700ADxeCore/D6A2CB7F-6A18-4e2f-B43B-9920A733700ASEC1.1.pe32 In pe32 binary, it has many strings which are copied from the name of build root folder. e.g. ^@!(((INTN)(RETURN_STATUS)(Status)) < 0)^@/home/joeyli/tmp/tmp/edk2/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c^@DisableNullDetectionAtTheEndOfDxe(): end^M ^@/home/joeyli/tmp/tmp/edk2/MdeModulePkg/Library/ImagePropertiesRecordLib/ImagePropertiesRecordLib.c^@!!!!!!!! ImageRecord not found !!!!!!!! So, if I used a build root folder with short name. I can reduce the size of the final FV image for FD_SIZE_2MB config. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1221849] New: grub2 bash-completion failed with '_split_longopt: command not found'
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221849 Bug ID: 1221849 Summary: grub2 bash-completion failed with '_split_longopt: command not found' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: glin(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading bash-completion to 2.12, grub2 bash-completion scripts stopped to work and showed the error: _split_longopt: command not found. It's because bash-completion 2.12 renamed '_split_longopt' as '_comp__split_longopt', and bash-completion upstream(*) stated that '_split_longopt' is a private API so it should not be used directly. Instead, the script should use '_init_completion -s' or the newer '_comp_initialize -s' to initialize 'cur', 'prev', and 'split'. (*) https://github.com/scop/bash-completion/issues/1135 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218875] grub2-2.12-1.1 bash completion not working
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1218875 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221904] Patch grub2-pass-corret-root-for-nfsroot.patch is using the wrong order of GRUB_FS/GRUB_DEVICE
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221904 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230906] python312: has some mtime based .pyc files
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230906 https://bugzilla.suse.com/show_bug.cgi?id=1230906#c13 --- Comment #13 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2024:3944-1: An update that solves one vulnerability and has one security fix can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-su-20243944-1 Category: security (moderate) Bug References: 1230906, 1232241 CVE References: CVE-2024-9287 Maintenance Incident: [SUSE:Maintenance:36306](https://smelt.suse.de/incident/36306/) Sources used: SUSE Linux Enterprise Server 12 SP5 LTSS Extended Security 12-SP5 (src): python3-3.4.10-25.142.1, python3-base-3.4.10-25.142.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230118] [SELinux] Select SELinux as default MAC in enforcing mode in the tumbleweed installer
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230118 https://bugzilla.suse.com/show_bug.cgi?id=1230118#c10 --- Comment #10 from Joe S <jmscdba(a)gmail.com> --- (In reply to Cathy Hu from comment #9) > (In reply to Joe S from comment #5) > we will not require restorecond anymore for it to be selinux-ready, i > created a submission to remove the check > > ftr the selinux-ready script is super old and we are looking into reworking > it Hi Cathy, Thanks very much for the update, I will go ahead and remove the package and service from my selinux test environment. I guess that functionality was something SUSE added as I just checked one of my Fedora test machines and it does not have the selinux-ready script. Have a blessed day ! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233064] New: [Build 20241106] GNOME (X11) does not install gnome-session-xsession
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233064 Bug ID: 1233064 Summary: [Build 20241106] GNOME (X11) does not install gnome-session-xsession Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4627209/modules/firs t_boot/steps/1 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation since the split of gnome-session-xsession out of gnome-session, when purely installing a gnome(x11) setup, nothing pulls in a working gnome-session openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-create_hdd_gnome-x11@64bit fails in [first_boot](https://openqa.opensuse.org/tests/4627209/modules/first_boot/st… ## Test suite description ## Reproducible Fails since (at least) Build [20241106](https://openqa.opensuse.org/tests/4626401) ## Expected result Last good: [20241105](https://openqa.opensuse.org/tests/4622316) (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 2

[Bug 1232647] New: AUDIT-WHITELIST: sddm-kalpa whitelist of dbus configuration file
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232647 Bug ID: 1232647 Summary: AUDIT-WHITELIST: sddm-kalpa whitelist of dbus configuration file 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: sfalken(a)cloverleaf-linux.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Can I please get a review, and a whitelist, based on the following: [ 97s] sddm-kalpa.x86_64: E: dbus-file-unauthorized (Badness: 10) /usr/share/dbus-1/system.d/org.freedesktop.DisplayManager-sddm.conf (sha256 file digest default filter:daa7d493ab968d706530339465449d98e09a5f717c230b85bf0f0e3d1365de2c shell filter:b3416d1bd9f087c9be887c1610296a116cb16a5f04e81fc0d61275ccbbc99842 xml filter:4b4cbecadaf6124b64d65abcc27157a154f4f3544b1a68b1f0754282e6766c8f) [ 97s] Packaging D-Bus services requires a review and whitelisting by the SUSE [ 97s] security team. If the package is intended for inclusion in any SUSE product [ 97s] please open a bug report to request review of the package by the security [ 97s] team. Please refer to [ 97s] https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs for [ 97s] more information. Package is https://build.opensuse.org/package/show/devel:microos:kalpa/sddm-kalpa -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1232727] [Build 20241101] openQA test fails in boot_encrypt: no decrypt prompt
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232727 https://bugzilla.suse.com/show_bug.cgi?id=1232727#c24 --- Comment #24 from Cliff Zhao <qzhao(a)suse.com> --- (In reply to Thomas Zimmermann from comment #22) > I've found that the graphics problem is unrelated to the cirrus-bochs patch. > > I've branched the plymouth package from Base:System and rebuilt it on OBS. I > let OBS do the build and installed it from my branched repo with 'zypper > dup'. It does not work correctly. It is at version 22.02.122+180.b1d5aa9. > > Tumbleweed's current version is at 22.02.122+94.4bd41a3 and appears to work > correctly? > > Cliff, am I missing something? Yes, I think the update could not helps on this bug. Currently, I'm involved in a M17N issue which is emergency to GNOME. So sorry for the delay. I suppose this bug could be resolve from the Plymouth side. and this is a P5 bug, I could switch back to this several days later, and also will try to reproduce the env. As this bug be assigned to you, if you could help on it or take on it, it will be very welcome! :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232814] undefined symbol: vaMapBuffer2
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232814 Bruno Pitrus <brunopitrus(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(angiesoft(a)gmx.net | |) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232814] undefined symbol: vaMapBuffer2
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232814 https://bugzilla.suse.com/show_bug.cgi?id=1232814#c7 Bruno Pitrus <brunopitrus(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #7 from Bruno Pitrus <brunopitrus(a)hotmail.com> --- Machine-translated from German: > After the update has just been carried out, the problem has been resolved. > can be closed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232913] New: tik fails to create tmp file and exits
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232913 Bug ID: 1232913 Summary: tik fails to create tmp file and exits Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: jarkko.torvinen(a)iki.fi QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With 20241104 Aeon installer, get this: [tik][20241106-05:52:50][LOG] [create_keyfile] Creating keyfile /tmp/tik.3QLJ1dka4y /usr/bin/dd: failed to open '/tmp/tik.3QLJ1dka4y': Permission denied [tik][20241106-05:52:50][LOG] [pkexec][1] /usr/bin/dd bs=512 count=4 if=/dev/urandom of=/tmp/tik.3QLJ1dka4y iflag=fullblock [tik][20241106-05:52:50][ERROR] Command <tt>/usr/bin/dd bs=512 count=4 if=/dev/urandom of=/tmp/tik.3QLJ1dka4y iflag=fullblock</tt> FAILED And the installation does not continue -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1233058] New: Crashes after starting the aeon installation with cmd/permission error
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233058 Bug ID: 1233058 Summary: Crashes after starting the aeon installation with cmd/permission error Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: geo.kocheril(a)uos.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878436 --> https://bugzilla.suse.com/attachment.cgi?id=878436&action=edit tik.log with error log My Aeon install is somehow broken, so I am trying to reinstall, without and with importing the user data feature of tik. I tried it several times, reproducible error with: "Command <tt>/usr/bin/dd bs=512 count=4 if=/dev/urandom of=/tmp/tik.kNk6m5Ejl1 iflag=fullblock</tt> FAILED 1. start from usb ssd aeon current version (downloaded today) 2. start "install now", tried different options (not to decrypt/import old user data on disk) 3. crashes with error, see tik.log -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1232814] undefined symbol: vaMapBuffer2
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232814 https://bugzilla.suse.com/show_bug.cgi?id=1232814#c6 --- Comment #6 from Uwe Henschel <angiesoft(a)gmx.net> --- nach eben durchgeführten update ist das Problem behoben. tuxedo:~ # rpm -qvi libva2 libavutil59 Name : libva2 Version : 2.22.0 Release : 1.1 Architecture: x86_64 Install Date: Di 05 Nov 2024 16:56:18 CET Group : System/Libraries Size : 220323 License : MIT Signature : RSA/SHA512, Do 04 Jul 2024 16:33:38 CEST, Key ID 35a2f86e29b700a4 Source RPM : libva-2.22.0-1.1.src.rpm Build Date : Mi 03 Jul 2024 10:17:21 CEST Build Host : reproducible Packager : https://bugs.opensuse.org Vendor : openSUSE URL : https://01.org/linuxmedia Summary : Video Acceleration API Description : The libva library implements the Video Acceleration API. The library loads a hardware dependendent driver. This is the core runtime library. Distribution: openSUSE Tumbleweed Name : libavutil59 Version : 7.1 Release : 1699.3.pm.2 Architecture: x86_64 Install Date: Do 07 Nov 2024 16:11:16 CET Group : System/Libraries Size : 1007658 License : GPL-3.0-or-later Signature : RSA/SHA1, Mi 06 Nov 2024 22:25:17 CET, Key ID 45a1d0671abd1afb Source RPM : ffmpeg-7-7.1-1699.3.pm.2.src.rpm Build Date : Di 15 Okt 2024 10:18:54 CEST Build Host : reproducible Packager : packman(a)links2linux.de Vendor : http://packman.links2linux.de URL : https://ffmpeg.org/ Summary : FFmpeg's utility library Description : The libavutil library is a utility library to aid portable multimedia programming. It contains safe portable string functions, random number generators, data structures, additional mathematics functions, cryptography and multimedia related functionality (like enumerations for pixel and sample formats). Distribution: Essentials / openSUSE_Tumbleweed ----------- kann geschlossen werden. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190024] haveged service has become obsolete with recent kernels (>= 5.6)
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1190024 https://bugzilla.suse.com/show_bug.cgi?id=1190024#c11 --- Comment #11 from Franck Bui <fbui(a)suse.com> --- (In reply to Donald Curtis from comment #10) > it seems that, removing the haveged package results in the systemd device > handling Virtual Memory random functions will complain How does it complain exactly ? On my system sys-devices-virtual-mem-random.device only exists when haveged is installed due to the udev rules /usr/lib/udev/rules.d/90-haveged.rules it ships. That being said, it looks like haveged has some issues: - initrd is not rebuilt when the package is uninstalled (I think this problem was already reported in the past) - haveged.spec doesn't seem to call %udev_rules_update although it ships a udev rule file. Maybe the problem you saw is a consequence of these. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233054] New: AUDIT-0: deepin-system-monitor: new policykit profiles of deepin-system-monitor
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233054 Bug ID: 1233054 Summary: AUDIT-0: deepin-system-monitor: new policykit profiles of deepin-system-monitor 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: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878435 --> https://bugzilla.suse.com/attachment.cgi?id=878435&action=edit new policykit profiles new dbus service The deepin-system-monitor is a part of Deepin Desktop v23, I am going to bring it to Tumbleweed. Please check new policykit profiles and whitelist them, If these dbus services do not have security issues. OBS devel project: https://build.opensuse.org/package/show/X11:Deepin:Factory/deepin-system-mo… Upstream: https://github.com/linuxdeepin/deepin-system-monitor [ 208s] deepin-system-monitor.aarch64: E: polkit-untracked-privilege (Badness: 10) com.deepin.pkexec.deepin-system-monitor.logout (no:no:auth_admin_keep) [ 208s] deepin-system-monitor.aarch64: E: polkit-untracked-privilege (Badness: 10) org.deepin.systemmonitor.systemserver.set (no:no:auth_admin_keep) [ 208s] The polkit action is not listed in the polkit-default-privs profiles which [ 208s] makes it harder for admins to find. Furthermore improper polkit authorization [ 208s] checks can easily introduce security issues. If the package is intended for [ 208s] inclusion in any SUSE product please open a bug report to request review of [ 208s] the package by the security team. Please refer to [ 208s] https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs for [ 208s] more information. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233053] New: AUDIT-0: deepin-system-monitor: new policykit profiles of deepin-system-monitor
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1233053 Bug ID: 1233053 Summary: AUDIT-0: deepin-system-monitor: new policykit profiles of deepin-system-monitor 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: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878434 --> https://bugzilla.suse.com/attachment.cgi?id=878434&action=edit com.deepin.pkexec.deepin-system-monitor.logout new dbus service The deepin-system-monitor is a part of Deepin Desktop v23, I am going to bring it to Tumbleweed. Please check new policykit profiles and whitelist them, If these dbus services do not have security issues. OBS devel project: https://build.opensuse.org/package/show/X11:Deepin:Factory/deepin-system-mo… Upstream: https://github.com/linuxdeepin/deepin-system-monitor [ 208s] deepin-system-monitor.aarch64: E: polkit-untracked-privilege (Badness: 10) com.deepin.pkexec.deepin-system-monitor.logout (no:no:auth_admin_keep) [ 208s] deepin-system-monitor.aarch64: E: polkit-untracked-privilege (Badness: 10) org.deepin.systemmonitor.systemserver.set (no:no:auth_admin_keep) [ 208s] The polkit action is not listed in the polkit-default-privs profiles which [ 208s] makes it harder for admins to find. Furthermore improper polkit authorization [ 208s] checks can easily introduce security issues. If the package is intended for [ 208s] inclusion in any SUSE product please open a bug report to request review of [ 208s] the package by the security team. Please refer to [ 208s] https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs for [ 208s] more information. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232647] AUDIT-WHITELIST: sddm-kalpa: dbus-file-unauthorized: org.freedesktop.DisplayManager-sddm.conf
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232647 https://bugzilla.suse.com/show_bug.cgi?id=1232647#c4 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #4 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- I started the whitelisting process. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227017] VUL-0: CVE-2024-6257: minikube: hashicorp/go-getter: Arbitrary command execution through local git config file
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227017 https://bugzilla.suse.com/show_bug.cgi?id=1227017#c1 Johannes Kastl <opensuse_buildservice(a)ojkastl.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |carlos.lopez(a)suse.com Flags| |needinfo?(carlos.lopez@suse | |.com) --- Comment #1 from Johannes Kastl <opensuse_buildservice(a)ojkastl.de> --- From the Hashicorp page: Affected Products / Versions: go-getter up to 1.7.4; fixed in go-getter 1.7.5. minikube 1.34.0 contains the fixed version 1.7.6 https://github.com/kubernetes/minikube/blob/v1.34.0/go.mod#L34 This version was updated in those two SRs: https://build.opensuse.org/request/show/1199877 (to Virtualization:containers) https://build.opensuse.org/request/show/1200059 (to Factory) So I guess this can be closed? Kind Regards, Johannes -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232647] AUDIT-WHITELIST: sddm-kalpa: dbus-file-unauthorized: org.freedesktop.DisplayManager-sddm.conf
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232647 https://bugzilla.suse.com/show_bug.cgi?id=1232647#c3 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|AUDIT-0: sddm-kalpa: |AUDIT-WHITELIST: |dbus-file-unauthorized: |sddm-kalpa: |org.freedesktop.DisplayMana |dbus-file-unauthorized: |ger-sddm.conf |org.freedesktop.DisplayMana | |ger-sddm.conf --- Comment #3 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- So this is not even a fork, it's the same sddm code base, just a repackaging with different features. I still had a look into the current D-Bus implementation. Practically all of it is unimplemented. There's also no authorization. This means anybody can call the "switchToGreeter()" method (which is practically the only one that is implemented). That is not ideal, a small local DoS vector, but other display managers have similar unauthenticated D-Bus interfaces, we already tried to talk to some upstreams but had no success so far. We can whitelist this new flavour of sddm. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227005] VUL-0: CVE-2024-3817: minikube: hashicorp/go-getter: argument injection when fetching remote default git branches
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227005 https://bugzilla.suse.com/show_bug.cgi?id=1227005#c1 --- Comment #1 from Johannes Kastl <opensuse_buildservice(a)ojkastl.de> --- Unless I am mistaken, this is still not fixed upstream: https://github.com/kubernetes/minikube/blob/master/go.mod#L34 Did someone report this upstream, already? Kind Regards, Johannes -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232814] undefined symbol: vaMapBuffer2
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232814 https://bugzilla.suse.com/show_bug.cgi?id=1232814#c5 --- Comment #5 from Uwe Henschel <angiesoft(a)gmx.net> --- tuxedo:~ # zypper search electron Repository-Daten werden geladen... Installierte Pakete werden gelesen... S | Name | Summary | Type ---+-----------------------------+------------------------------------------------------------------+----------- i+ | nodejs-electron | Build cross platform desktop apps with JavaScript, HTML, and CSS | Paket | nodejs-electron | Build cross platform desktop apps with JavaScript, HTML, and CSS | Quellpaket | nodejs-electron-debuginfo | Debug information for package nodejs-electron | Paket | nodejs-electron-debugsource | Debug sources for package nodejs-electron | Paket i+ | nodejs-electron-devel | Electron development headers | Paket | nodejs-electron-doc | Electron API documentation | Paket tuxedo:~ # zypper info --requires nodejs-electron | grep libavutil libavutil.so.59()(64bit) libavutil.so.59(LIBAVUTIL_59.39_SUSE)(64bit) tuxedo:~ # ls -lh /lib64/libavutil.so.59 lrwxrwxrwx 1 root root 22 15. Okt 10:18 /lib64/libavutil.so.59 -> libavutil.so.59.39.100 tuxedo:~ # nm /lib64/libavutil.so.59.8.100 nm: '/lib64/libavutil.so.59.8.100': No such file tuxedo:~ # tuxedo:~ # ll /lib64/libavutil.so.59* lrwxrwxrwx 1 root root 22 15. Okt 10:18 /lib64/libavutil.so.59 -> libavutil.so.59.39.100 -rwxr-xr-x 1 root root 985168 15. Okt 10:18 /lib64/libavutil.so.59.39.100 tuxedo:~ # nm /lib64/libavutil.so.59.39.100 nm: /lib64/libavutil.so.59.39.100: no symbols tuxedo:~ # file /lib64/libavutil.so.59.39.100 /lib64/libavutil.so.59.39.100: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=d8ac6e2c61be37093e3bfac75395cafb813d1d52, stripped tuxedo:~ # tuxedo:~ # rpm -qvi libva2 libavutil59 Name : libva2 Version : 2.22.0 Release : 1.1 Architecture: x86_64 Install Date: Di 05 Nov 2024 16:56:18 CET Group : System/Libraries Size : 220323 License : MIT Signature : RSA/SHA512, Do 04 Jul 2024 16:33:38 CEST, Key ID 35a2f86e29b700a4 Source RPM : libva-2.22.0-1.1.src.rpm Build Date : Mi 03 Jul 2024 10:17:21 CEST Build Host : reproducible Packager : https://bugs.opensuse.org Vendor : openSUSE URL : https://01.org/linuxmedia Summary : Video Acceleration API Description : The libva library implements the Video Acceleration API. The library loads a hardware dependendent driver. This is the core runtime library. Distribution: openSUSE Tumbleweed Name : libavutil59 Version : 7.1 Release : 1699.3.pm.1 Architecture: x86_64 Install Date: Di 05 Nov 2024 17:56:51 CET Group : System/Libraries Size : 1007658 License : GPL-3.0-or-later Signature : RSA/SHA1, Do 17 Okt 2024 00:25:12 CEST, Key ID 45a1d0671abd1afb Source RPM : ffmpeg-7-7.1-1699.3.pm.1.src.rpm Build Date : Di 15 Okt 2024 10:18:54 CEST Build Host : reproducible Packager : packman(a)links2linux.de Vendor : http://packman.links2linux.de URL : https://ffmpeg.org/ Summary : FFmpeg's utility library Description : The libavutil library is a utility library to aid portable multimedia programming. It contains safe portable string functions, random number generators, data structures, additional mathematics functions, cryptography and multimedia related functionality (like enumerations for pixel and sample formats). Distribution: Essentials / openSUSE_Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227049] VUL-0: CVE-2024-6104: minikube: hashicorp/go-retryablehttp: url might write sensitive information to log file
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227049 https://bugzilla.suse.com/show_bug.cgi?id=1227049#c1 Johannes Kastl <opensuse_buildservice(a)ojkastl.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |carlos.lopez(a)suse.com Flags| |needinfo?(carlos.lopez@suse | |.com) --- Comment #1 from Johannes Kastl <opensuse_buildservice(a)ojkastl.de> --- Hi all, sorry for the late reply. minikube 0.34.0 contains the fixed version 0.7.7: https://github.com/kubernetes/minikube/blob/v1.34.0/go.mod#L35 This version was updated in those two SRs: https://build.opensuse.org/request/show/1199877 (to Virtualization:containers) https://build.opensuse.org/request/show/1200059 (to Factory) I guess this can be closed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0