November 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1233149] New: System got stuck in "setting up" screen on first boot
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233149 Bug ID: 1233149 Summary: System got stuck in "setting up" screen on first boot Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: lzcoder(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878470 --> https://bugzilla.suse.com/attachment.cgi?id=878470&action=edit journalctl -p crit After installing the system with 20241106 image, it got stuck at the “setting up” screen on first boot. In my case I waited more than 30 minutes (in previous installations I didn't have to wait that long) and after waiting I restarted my system and everything seems to work correctly. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1232244] New: AUDIT-0: xfce4-power-manager: New PolKit rules added
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1232244 Bug ID: 1232244 Summary: AUDIT-0: xfce4-power-manager: New PolKit rules added Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878186 --> https://bugzilla.suse.com/attachment.cgi?id=878186&action=edit Full build log xfce4-power-manager-4.19.3 has added polkit rules [ 43s] RPMLINT report: [ 43s] =============== [ 44s] xfce4-power-manager.x86_64: E: polkit-unauthorized-privilege (Badness: 10000) org.xfce.power.xfce4-pm-helper (auth_admin:auth_admin:yes) [ 44s] The package allows unprivileged users to carry out privileged operations [ 44s] without authentication. This could cause security problems if not done [ 44s] carefully. If the package is intended for inclusion in any SUSE product please [ 44s] open a bug report to request review of the package by the security team. [ 44s] Please refer to [ 44s] https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs for [ 44s] more information. [ 44s] [ 44s] (none): E: badness 10000 exceeds threshold 1000, aborting. OBS repo: https://build.opensuse.org/package/show/home:manfred-h:X11:xfce:4.19/xfce4-… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1233673] New: Update nvidia driver to latest 550.135 release
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233673 Bug ID: 1233673 Summary: Update nvidia driver to latest 550.135 release Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Update nvidia driver to latest 550.135 release -- You are receiving this mail because: You are on the CC list for the bug.

1 4

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

16 Dec '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 15

[Bug 1220088] New: Hibernate completes shuts machine off *then* machine automatically turns back on.
by bugzilla_noreply＠suse.com 14 Dec '24

14 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220088 Bug ID: 1220088 Summary: Hibernate completes shuts machine off *then* machine automatically turns back on. 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: pj.opensuse(a)gmx.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, when hibernate is envoked from the Tumbleweed menu the hibernate feature seems to complete and shutoff the machine for 2 seconds...... Then the machine automatically powers back on. I enter the LUKS password and the machine continues to boot. I enter the user password at SDDM screen. After loading KDE I can then see that Hibernate has indeed worked. Largest issue is machine is cycling, (powering back on) after hibernation has been envoked. I have shut off all wake-on power options in the bios settings. The machine is kept very current with the latest updates. What are your thoughts on this? -Best Regards -- You are receiving this mail because: You are on the CC list for the bug.

1 25

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

13 Dec '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 31

[Bug 1230779] New: Update nvidia driver to latest 550.xxx release
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1230779 Bug ID: 1230779 Summary: Update nvidia driver to latest 550.xxx release Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Update nvidia driver to latest 550.xxx release -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1232057] New: Update nvidia driver to latest 550.127.05 release
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1232057 Bug ID: 1232057 Summary: Update nvidia driver to latest 550.127.05 release Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Update nvidia driver to latest 550.127.05 release -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1229716] New: Update nvidia driver to version 550.107.02
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1229716 Bug ID: 1229716 Summary: Update nvidia driver to version 550.107.02 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Update nvidia driver to version 550.107.02 ... -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1233824] New: [s390x] gnome-remote-desktop RDP-server does not start on s390x
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233824 Bug ID: 1233824 Summary: [s390x] gnome-remote-desktop RDP-server does not start on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: martin.sirringhaus(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I can't get RDP to work on s390x, so I tried the same steps on a x86_64 VM and on s390x: ``` sudo zypper in -y gnome-remote-desktop freerdp-server # You probably have to do `su -` here first for this one: sudo -u gnome-remote-desktop winpr-makecert \ -silent -rdp -path ~gnome-remote-desktop rdp-tls # Set RDP_USER and RDP_PASS to whatever you want sudo grdctl --system rdp set-credentials "$RDP_USER" "$RDP_PASS" sudo grdctl --system rdp set-tls-key /var/lib/gnome-remote-desktop/rdp-tls.key sudo grdctl --system rdp set-tls-cert /var/lib/gnome-remote-desktop/rdp-tls.crt sudo grdctl --system rdp enable sudo systemctl --now enable gnome-remote-desktop.service ``` On both systems I get basically the same output for this: ``` # grdctl --system status Init TPM credentials failed because No TPM device found, using GKeyFile as fallback. Overall: Unit status: active RDP: Status: enabled Port: 3389 TLS certificate: /var/lib/gnome-remote-desktop/rdp-tls.crt TLS fingerprint: 1f:76:bb:d3:bd:42:fd:51:af:e7:89:64:e1:00:c2:78:d9:16:20:63:2b:08:84:ac:38:4e:79:48:c9:4a:07:db TLS key: /var/lib/gnome-remote-desktop/rdp-tls.key Username: (hidden) ``` `systemctl start gnome-remote-desktop` works fine on both systems, telling me that the service is up and running. On my VM, however, I get ``` Nov 27 14:04:03 localhost.localdomain systemd[1]: Starting GNOME Remote Desktop... Nov 27 14:04:03 localhost.localdomain gnome-remote-de[4244]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback Nov 27 14:04:03 localhost.localdomain systemd[1]: Started GNOME Remote Desktop. Nov 27 14:04:04 localhost.localdomain gnome-remote-de[4244]: RDP server started localhost:~ # ss -punta | grep gnome tcp LISTEN 0 10 *:3389 *:* users:(("gnome-remote-de",pid=4244,fd=9)) ``` whereas on s390x, I get: ``` Nov 27 12:47:41 firefox.prg2.suse.org systemd[1]: Starting GNOME Remote Desktop... Nov 27 12:47:41 firefox.prg2.suse.org gnome-remote-de[15170]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback Nov 27 12:47:41 firefox.prg2.suse.org systemd[1]: Started GNOME Remote Desktop. firefox:~ # ss -punta | grep gnome firefox:~ # ``` Setting G_MESSAGES_DEBUG=all didn't reveal anything, either. Basically, all RDP-related output is missing on s390x. No additional info (that is not also logged on x86_64 with this env-variable). The RDP-server simply doesn't start up on s390x without any errors or logging. -- You are receiving this mail because: You are on the CC list for the bug.

1 34

[Bug 1225688] New: [tw] [hexchat] gnome-shell The program 'hexchat' received an X Window System error when connecting to netwok
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1225688 Bug ID: 1225688 Summary: [tw] [hexchat] gnome-shell The program 'hexchat' received an X Window System error when connecting to netwok Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/4236088/modules/hexc hat/steps/28 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: richard.fan(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Description The issue is a sporadic one, but I can see the issue several times in openQA automation tests. it can be seen on both x86_64 and aarch64 platforms. Steps to reproduce the issue: 1. Upgrade the system from leap15.x to tw 2. start hexchat 3. config a nickname and connect to "Libera.Chat" Error logs like below: >May 30 09:49:37.300575 susetest gnome-shell[30709]: The program 'hexchat' received an X Window System error. >May 30 09:49:37.300575 susetest gnome-shell[30709]: This probably reflects a bug in the program. >May 30 09:49:37.307179 susetest gnome-shell[30709]: The error was 'BadWindow (invalid Window parameter)'. >May 30 09:49:37.307179 susetest gnome-shell[30709]: (Details: serial 6056 error_code 3 request_code 38 minor_code 0) >May 30 09:49:37.307179 susetest gnome-shell[30709]: (Note to programmers: normally, X errors are reported asynchronously; >May 30 09:49:37.307179 susetest gnome-shell[30709]: that is, you will receive the error a while after causing it. >May 30 09:49:37.307179 susetest gnome-shell[30709]: To debug your program, run it with the --sync command line >May 30 09:49:37.307179 susetest gnome-shell[30709]: option to change this behavior. You can then get a meaningful >May 30 09:49:37.307179 susetest gnome-shell[30709]: backtrace from your debugger if you break on the gdk_x_error() function.) Please refer to the attached log for more information. ## openQA Observation as below: openQA test in scenario opensuse-Tumbleweed-NET-aarch64-zdup-Leap-15.5-gnome@aarch64 fails in [hexchat](https://openqa.opensuse.org/tests/4236088/modules/hexchat/steps/28) ## Test suite description Maintained by qe-core ## Reproducible Fails since (at least) Build [20240529](https://openqa.opensuse.org/tests/4235968) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1232670] New: [SELinux] importctl cannot write to /var/lib/extensions
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1232670 Bug ID: 1232670 Summary: [SELinux] importctl cannot write to /var/lib/extensions 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: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Importing sysext images with importctl does not work, since SELinux blocks writing in that directory: node122:~ # importctl pull-raw --class=sysext https://download.opensuse.org/repositories/home:/kukuk:/sysext/mkosi/gcc-20… --verify=no Enqueued transfer job 1. Press C-c to continue download in background. Pulling 'https://download.opensuse.org/repositories/home:/kukuk:/sysext/mkosi/gcc-20…', saving as 'gcc-20.2.x86-64'. Operating on image directory '/var/lib/extensions'. Failed to create /var/lib/extensions/.#verityebe0580e99f54026: Permission denied Verity integrity file could not be retrieved, proceeding without. Failed to create /var/lib/extensions/.#roothash96cdb063d430dc58: Permission denied Root hash file could not be retrieved, proceeding without. Failed to create /var/lib/extensions/.#roothash.p7s70c3902ea1954e95: Permission denied Root hash signature file could not be retrieved, proceeding without. Downloading 241.2M for https://download.opensuse.org/repositories/home:/kukuk:/sysext/mkosi/gcc-20…. Failed to create /var/lib/extensions/.#rawd292069b0f58e5ea: Permission denied Failed to retrieve image file. Exiting. type=SERVICE_START msg=audit(1730372760.872:336): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-importd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' type=AVC msg=audit(1730372764.279:337): avc: denied { write } for pid=2413 comm="systemd-pull" name="extensions" dev="dm-0" ino=143939 scontext=system_u:system_r:systemd_importd_t:s0 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=dir permissive=0 type=AVC msg=audit(1730372764.282:338): avc: denied { write } for pid=2413 comm="systemd-pull" name="extensions" dev="dm-0" ino=143939 scontext=system_u:system_r:systemd_importd_t:s0 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=dir permissive=0 type=AVC msg=audit(1730372764.289:339): avc: denied { write } for pid=2413 comm="systemd-pull" name="extensions" dev="dm-0" ino=143939 scontext=system_u:system_r:systemd_importd_t:s0 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=dir permissive=0 type=AVC msg=audit(1730372767.479:340): avc: denied { write } for pid=2413 comm="systemd-pull" name="extensions" dev="dm-0" ino=143939 scontext=system_u:system_r:systemd_importd_t:s0 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=dir permissive=0 type=SERVICE_STOP msg=audit(1730372797.529:341): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-importd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1228272] New: When using systemd-boot, dracut uses wrong target file
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228272 Bug ID: 1228272 Summary: When using systemd-boot, dracut uses wrong target file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: tilman.vogel(a)web.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When after an upgrade, /usr/lib/module-init-tools/regenerate-initrd-posttrans runs dracut -f --kver "$kver" the generated initrd goes to /boot/efi/<somehexid>/$kver/initrd which looks right but is in fact incorrect because /boot/efi/loader/entries/<somehexid>-$kver.conf actually uses initrd /<somehexid>/$kver/initrd-$kver Note the trailing "-$kver". So, after running dracut, there are two initrds: /boot/efi/<somehexid>/$kver/initrd /boot/efi/<somehexid>/$kver/initrd-$kver of which the former is the new one but ignored and the latter is an older one which will still be used. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228797] New: python3-schema and python3-daemon not available with sle-module-pythons
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228797 Bug ID: 1228797 Summary: python3-schema and python3-daemon not available with sle-module-pythons Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: egotthold(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am attempting to build cobbler-tftp here [1]. This is failing due to two dependencies not being enabled for sle-module-pythons. I would desire that sle15allpythons is used so the package builds for both 3.6 and 3.11. Both versions in Leap are available at the moment with 3.6 and are compatible with it. [1]: https://build.opensuse.org/package/show/systemsmanagement:cobbler:release34… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1233167] New: [Build 20241109] Mesa 24.2.x - shifted colors on s390x
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233167 Bug ID: 1233167 Summary: [Build 20241109] Mesa 24.2.x - shifted colors on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4634296/modules/boot loader_start/steps/33 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation We have a color shift when installing on an s390x mainframe; introduced with Mesa 24.2.x openQA test in scenario opensuse-Tumbleweed-DVD-s390x-autoyast_zvm@s390x-zVM-vswitch-l2 fails in [bootloader_start](https://openqa.opensuse.org/tests/4634296/modules/bootloa… ## Test suite description Create HDD for s390x textmode ## Reproducible Fails since (at least) Build [20241109](https://openqa.opensuse.org/tests/4633979) ## Expected result Last good: [20241105](https://openqa.opensuse.org/tests/4622286) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse… -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1224773] New: Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 Bug ID: 1224773 Summary: Cannot install NVIDIA drivers in latest Aeon RC2 Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: sunscape1(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Installing NVIDIA drivers in Aeon RC2 (https://en.opensuse.org/SDB:NVIDIA_drivers) fails because the MOK cannot be enrolled after boot. Error during installation using pkg is: SKIP: /var/lib/nvidia-pubkeys/MOK-nvidia-driver-G06-550.78-22.1-default.der is not in MokList Without the nvidia-pubkeys folder it is impossible to enroll the MOK or try to enable it after reboot. The key doesn't exist :( -- You are receiving this mail because: You are on the CC list for the bug.

1 38

[Bug 1231826] New: open-vm-tools 12.5.0 was released - please rebase
by bugzilla_noreply＠suse.com 11 Dec '24

11 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231826 Bug ID: 1231826 Summary: open-vm-tools 12.5.0 was released - please rebase Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: john.wolfe(a)broadcom.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- open-vm-tools 12.5.0 was released on Oct 08, 2024 - based on build 24276846. There are no new features in the open-vm-tools 12.5.0 release. This is primarily a maintenance release that addresses a few issues, including: - A Github pull request. Please see the Resolved Issues section of the Release Notes. - Avoid deprecated function warnings if using libxml2 version 2.13.0 or later. For a more complete list of issues resolved in this release, see the Resolved Issues section of the Release Notes. For complete details, see: https://github.com/vmware/open-vm-tools/releases/tag/stable-12.5.0 Release Notes are available at: https://github.com/vmware/open-vm-tools/blob/stable-12.5.0/ReleaseNotes.md The granular changes that have gone into the 12.5.0 release are in the ChangeLog at: https://github.com/vmware/open-vm-tools/blob/stable-12.5.0/open-vm-tools/Ch… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1233774] New: python-rpm-macros changes %packager of all OBS-produced packages
by bugzilla_noreply＠suse.com 11 Dec '24

11 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233774 Bug ID: 1233774 Summary: python-rpm-macros changes %packager of all OBS-produced packages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: mcepl(a)suse.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- abuild@a4:/usr/lib/rpm> rpm -qf /usr/lib/rpm/macros.d/macros.python_all python-rpm-macros-20240618.1e386da-150400.3.13.1.noarch abuild@a4:/usr/lib/rpm> cat macros.python_all ... ### from SUSE:Maintenance:34487 %_repository SUSE_SLE-15-SP4_Update %vendor SUSE LINUX Products GmbH, Nuernberg, Germany %packager http://bugs.opensuse.org %vendor %maintenance_vendor %distribution %maintenance_distribution %packager https://www.suse.com/ ... -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1231795] New: python3-config contains some garbage flags
by bugzilla_noreply＠suse.com 11 Dec '24

11 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231795 Bug ID: 1231795 Summary: python3-config contains some garbage flags Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- OS: openSUSE Tumbleweed 20241016 Version: python311-devel-3.11.10-1.2.x86_64 Observed: $ >x.c; gcc `python3-config --cflags` -c x.c -Wmissing-include-dirs cc1: warning: Vendor/: No such file or directory [-Wmissing-include-dirs] Expected: Don't let -IVendor escape from the python internal build into the python3-config script. Since python3.pc does not have the problem, I wonder if anyone should even ever use python3-config to begin with. Opinions? -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1231836] New: [MicroOS]: emergency mode after attempting to mount /.snapshots
by bugzilla_noreply＠suse.com 11 Dec '24

11 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231836 Bug ID: 1231836 Summary: [MicroOS]: emergency mode after attempting to mount /.snapshots Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Filesystems Assignee: kernel-fs(a)suse.de Reporter: egotthold(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878122 --> https://bugzilla.suse.com/attachment.cgi?id=878122&action=edit Failing boot During the nightly reboot of one of my MicroOS systems, I am getting intermittent drops into the emergency shell. Rebooting the device helps in most cases, in other cases, a second reboot is needed. I am using /etc/fstab with the following content [1]. In the attachments, one of those failing boots can be observed. The community it seems has this issue also for a good while - https://forums.opensuse.org/t/random-boot-failures-in-microos/176605 [1]: /etc/fstab UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 / btrfs ro 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /usr/local btrfs subvol=/@/usr/local 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /srv btrfs subvol=/@/srv 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /root btrfs subvol=/(a)/root,x-initrd.mount 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /opt btrfs subvol=/@/opt 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /home btrfs subvol=/@/home 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /boot/writable btrfs subvol=/@/boot/writable 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /boot/grub2/x86_64-efi btrfs subvol=/@/boot/grub2/x86_64-efi 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /boot/grub2/i386-pc btrfs subvol=/@/boot/grub2/i386-pc 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /.snapshots btrfs subvol=/(a)/.snapshots 0 0 UUID=83c66cbc-e40b-4b67-987f-3b41f613932c /var btrfs defaults,x-initrd.mount 0 0 UUID=EEE3-4BD4 /boot/efi vfat utf8 0 2 UUID=1c5adbee-7e1a-471e-9d04-0e583d29d8ec /var/data auto nofail,subvol=/,x-parent=8d06eb2d:af57615e:15d28725:65d23c58 0 0 overlay /etc overlay defaults,lowerdir=/sysroot/var/lib/overlay/168/etc:/sysroot/etc,upperdir=/sysroot/var/lib/overlay/169/etc,workdir=/sysroot/var/lib/overlay/169/work-etc,x-systemd.requires-mounts-for=/var,x-systemd.requires-mounts-for=/sysroot/var,x-initrd.mount 0 0 -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1231566] New: Base:System/dbus-1: Bug Resplit the dbus package.
by bugzilla_noreply＠suse.com 10 Dec '24

10 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231566 Bug ID: 1231566 Summary: Base:System/dbus-1: Bug Resplit the dbus package. Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: simonf.lees(a)suse.com Reporter: fxzxmic(a)hotmail.com QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am curious if there are still wayland software using dbus-launch now. In Fedora, if I execute the following command "dnf provides /usr/bin/dbus-launch", I will only get: "dbus-x11". On Fedora, the dbus package no longer contains any content. So I propose to completely move dbus-launch to dbus-x11. Also, for the dbus-daemon-launch-helper, I think it should be a part of the dbus-daemon. As for rcdbus, it said: "The service command and the rc* symlinks have been deprecated and will be removed in a future release." -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1230361] New: scap-security-guide: reproducible builds issue (date)
by bugzilla_noreply＠suse.com 10 Dec '24

10 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1230361 Bug ID: 1230361 Summary: scap-security-guide: reproducible builds issue (date) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: rumen.chikov(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: meissner(a)suse.com Blocks: 1047218 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our scap-security-guide varied in each build, even when varying as little as possible. This is because, there is a build date+time embedded in the output: --- old//usr/share/scap-security-guide/tailoring/rhel8_stig_delta_tailoring.xml 2024-09-02 13:58:51.000000000 +0000 +++ new//usr/share/scap-security-guide/tailoring/rhel8_stig_delta_tailoring.xml 2024-09-02 13:58:51.000000000 +0000 @@ -1,4 +1,4 @@ -<xccdf-1.2:Tailoring xmlns:xccdf-1.2="http://checklists.nist.gov/xccdf/1.2" id="xccdf_content-disa-delta_tailoring_default"><xccdf-1.2:version time="2024-09-06T15:14:18.947277+00:00">1</xccdf-1.2:version><xccdf-1.2:Profile id="xccdf_org.ssgproject.content_profile_stig_delta_tailoring" extends="xccdf_org.ssgproject.content_profile_stig"><xccdf-1.2:title override="true">DISA STIG for Red Hat Enterprise Linux 8</xccdf-1.2:title> +<xccdf-1.2:Tailoring xmlns:xccdf-1.2="http://checklists.nist.gov/xccdf/1.2" id="xccdf_content-disa-delta_tailoring_default"><xccdf-1.2:version time="2024-09-06T15:15:45.696526+00:00">1</xccdf-1.2:version><xccdf-1.2:Profile id="xccdf_org.ssgproject.content_profile_stig_delta_tailoring" extends="xccdf_org.ssgproject.content_profile_stig"><xccdf-1.2:title override="true">DISA STIG for Red Hat Enterprise Linux 8</xccdf-1.2:title> If timestamps cannot be dropped, they should use $SOURCE_DATE_EPOCH https://reproducible-builds.org/docs/source-date-epoch/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1233689] New: Kleopatra not recognizing KDEWallet GPG Certificate after Tumbleweed KDE Update
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233689 Bug ID: 1233689 Summary: Kleopatra not recognizing KDEWallet GPG Certificate after Tumbleweed KDE Update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Critical Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: vfvs(a)riseup.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I’m using Tumbleweed KDE. After 23 November 2024 update, Kleopatra stopped recognizing the GPG certificate where KDEWallet’ passwords are stored. It looks like Kleopatra doesn't have the permissions to access the home subfolder ~/.gnupg/ where keys are stored. I checked the folder permissions and the other settings but they were fine, and I couldn’t figure out the issue. So, I reverted to the previous snapshot via GRUB, and everything works fine. This is an example of what I get from journalctl -xe : Nov 23 16:31:42 ip5w.homenet.telecomitalia.it kleopatra[2899]: inotify_add_watch(/home/user/.gnupg/private-keys-v1.d/D75EEB36F099AD06F27DEAB050F0AE011B042175.key) failed: (Permission denied) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1226763] New: Missing non-oss source repo for aarch64
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1226763 Bug ID: 1226763 Summary: Missing non-oss source repo for aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We have a source repo for non-oss ports on s390x and ppc but not on arm we can either add it for Arm, or drop it for others guillaume_g As it exists for x86_64, I guess we should publish it for :ARM as well https://download.opensuse.org/source/tumbleweed/repo/non-oss/ (using patterns component so it ends on rel-eng) -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1233764] New: VUL-0: CVE-2024-11403: qt6-webengine: libjxl: Out of Bounds Memory Read/Write in libjxl
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233764 https://bugzilla.suse.com/show_bug.cgi?id=1233764#c1 Bug ID: 1233764 Summary: VUL-0: CVE-2024-11403: qt6-webengine: libjxl: Out of Bounds Memory Read/Write in libjxl Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/429996/ OS: Other Status: NEW Whiteboard: CVSSv3.1:SUSE:CVE-2024-11403:6.7:(AV:N/AC:H/PR:L/UI:R/ S:U/C:H/I:H/A:L) Severity: Normal Priority: P5 - None Component: Security Assignee: christophe(a)krop.fr Reporter: andrea.mattiazzo(a)suse.com QA Contact: security-team(a)suse.de Blocks: 1233763 Target Milestone: --- Found By: --- Blocker: --- --- Comment #1 from Andrea Mattiazzo <andrea.mattiazzo(a)suse.com> --- There exists an out of bounds read/write in LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33d24c99. The JPEG decoder used by the JPEG XL encoder when doing JPEG recompression (i.e. if using JxlEncoderAddJPEGFrame on untrusted input) does not properly check bounds in the presence of incomplete codes. This could lead to an out-of-bounds write. In jpegli which is released as part of the same project, the same vulnerability is present. However, the relevant buffer is part of a bigger structure, and the code makes no assumptions on the values that could be overwritten. The issue could however cause jpegli to read uninitialised memory, or addresses of functions. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-11403 https://www.cve.org/CVERecord?id=CVE-2024-11403 https://github.com/libjxl/libjxl/commit/9cc451b91b74ba470fd72bd48c121e9f33d… https://bugzilla.redhat.com/show_bug.cgi?id=2328670 -- You are receiving this mail because: You are on the CC list for the bug.

1 3