December 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1224773] NVIDIA KMP: initrd not regenerated on transactional systems using systemd-boot like Aeon >= RC2
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(aplanas(a)suse.com) | |, | |needinfo?(iforster(a)suse.com | |) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 1231784] xvkbd special keys not working on KDE Plasma of Leap 15.6 (regression)
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231784 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|xvkbd special keys not |xvkbd special keys not |working |working on KDE Plasma of | |Leap 15.6 (regression) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231784] xvkbd special keys not working
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231784 https://bugzilla.suse.com/show_bug.cgi?id=1231784#c2 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|X11 Applications |KDE Workspace (Plasma) CC|sndirsch(a)suse.com | --- Comment #2 from Stefan Dirsch <sndirsch(a)suse.com> --- I think this is independant of xvkbd, but related to KDE Plasma instead. Reassigning. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224773] NVIDIA KMP: initrd not regenerated on transactional systems using systemd-boot like Aeon >= RC2
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c94 --- Comment #94 from Stefan Dirsch <sndirsch(a)suse.com> --- Hmm. How can I detect if I am on such a system where apparently lsinitrd is not supposed to work? Then I would just always trigger a dracut run on such a system and things would work - assuming mkdir -p /run/regenerate-initrd touch /run/regenerate-initrd/all results in a transactional-update initrd run instead of 'dracut ...". Letting lsinitrd fail, detect this and then always trigger a dracut run sounds like a rather stupid approach. But yeah, this would be possible as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234471] laptop fails to suspend (sleep) due to issue with nvidia GPU driver
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234471 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gfx-bugs(a)suse.de |sndirsch(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234547] New: FreeCAD failing to run due to dependency
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234547 Bug ID: 1234547 Summary: FreeCAD failing to run due to dependency Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: fbourdonnec(a)chez.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- FreeCad 1.0.0-1.2 needs Opencascade 7.2.2 Tumbleweed provides Opencascade 7.8.1 FreeCad cannot do anything usefull. Example of missing lib libTKMesh.so.7.2.2 -- 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 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c62 --- Comment #62 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Guillermo Perez from comment #61) > ~> sdbootutil -v --ask-pin update-predictions > Error: Can't determine root subvolume Do you have a default snapshot? sudo snapper ls This should show a list of snapshots, and one of the should be marked with "*". If this is not the case, somehow you system lacks of default subvolume. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234471] laptop fails to suspend (sleep) due to issue with nvidia GPU driver
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234471 https://bugzilla.suse.com/show_bug.cgi?id=1234471#c8 --- Comment #8 from Stefan Dirsch <sndirsch(a)suse.com> --- Note to myself: If removing that option helps, that would be a dup of boo#1226116 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234469] YaST2 Qt UI can't connect to display
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234469 https://bugzilla.suse.com/show_bug.cgi?id=1234469#c2 --- Comment #2 from Stefan Hundhammer <shundhammer(a)suse.com> --- You can also check if it's something with the root account trying to open the graphical desktop that you started as a non-root user: sudo zypper in yast2-widget-demo yast2 widget_demo -- You are receiving this mail because: You are on the CC list for the bug.

1 0