November 2024 - openSUSE Bugs - openSUSE Mailing Lists

[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