December 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1230891] Difficult to update mesa with Packman repo installed on Slowroll
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1230891 https://bugzilla.suse.com/show_bug.cgi?id=1230891#c30 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #30 from Stefan Dirsch <sndirsch(a)suse.com> --- Looks like meanwhile all Mesa pacakges have been updated to 24.3.1. Closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234274] New: libnvidia-egl-gbm1-32bit, libnvidia-egl-x111-32bit packages missing
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234274 Bug ID: 1234274 Summary: libnvidia-egl-gbm1-32bit, libnvidia-egl-x111-32bit packages missing 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: sndirsch(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The following -32bit packages are missing on Tumbleweed: libnvidia-egl-gbm1-32bit libnvidia-egl-x111-32bit These are subpackages of X11:XOrg/libnvidia-egl-x11 X11:XOrg/libnvidia-egl-gbm -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1234363] New: vmware command vmhgfs-fuse Segmentation fault
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234363 Bug ID: 1234363 Summary: vmware command vmhgfs-fuse Segmentation fault Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: mli(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- vmhgfs-fuse segmentation fault in SLE MICRO 6.0 # cat /etc/os-release NAME="SL-Micro" VERSION="6.0" VERSION_ID="6.0" PRETTY_NAME="SUSE Linux Micro 6.0" # uname -r 6.4.0-21-default # rpm -qa|grep -E "open-vm-tools|libvmtools0" open-vm-tools-12.4.0-1.1.x86_64 libvmtools0-12.4.0-1.1.x86_64 # vmhgfs-fuse -d Segmentation fault (core dumped) # vmhgfs-fuse -s Segmentation fault (core dumped) # vmhgfs-fuse .host:/foo/bar /mnt/bar -d Segmentation fault (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1234471] New: 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 Bug ID: 1234471 Summary: laptop fails to suspend (sleep) due to issue with nvidia GPU driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: toby(a)breckon.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 879142 --> https://bugzilla.suse.com/attachment.cgi?id=879142&action=edit dmesg after event Laptop will not enter sleep mode on lid close or manually. Laptop model: custom (UK pcspecialist.co.uk Recoil 17) --- Critical part of dmesg says: [ 125.442225] [ T6167] PM: suspend entry (s2idle) [ 125.467446] [ T6167] Filesystems sync: 0.025 seconds [ 126.005842] [ T6167] Freezing user space processes [ 126.007729] [ T6167] Freezing user space processes completed (elapsed 0.001 seconds) [ 126.007734] [ T6167] OOM killer disabled. [ 126.007735] [ T6167] Freezing remaining freezable tasks [ 126.008990] [ T6167] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [ 126.008993] [ T6167] printk: Suspending console(s) (use no_console_suspend to debug) [ 126.135691] [ T4338] NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README. [ 126.135700] [ T4338] nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5 [ 126.136481] [ T4338] nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5 [ 126.136487] [ T4338] nvidia 0000:01:00.0: PM: failed to suspend async: error -5 [ 126.888138] [ T6167] PM: Some devices failed to suspend, or early wake event detected [ 127.915694] [ T6167] OOM killer enabled. [ 127.915697] [ T6167] Restarting tasks ... done. [ 127.917864] [ T6167] random: crng reseeded on system resumption [ 127.922699] [ T6167] PM: suspend exit --- dmesg + boot.msg attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

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

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231566 https://bugzilla.suse.com/show_bug.cgi?id=1231566#c7 --- Comment #7 from Simon Lees <simonf.lees(a)suse.com> --- (In reply to Fxzx mic from comment #6) > /usr/bin/dbus-daemon > /usr/bin/dbus-run-session > > gdm only needs these two. Yep but in the context of the size of a desktop system I don't think its worth having an extra subpackage just for a 30kb binary. On the other hand having it in the dbus-daemon package means that in a context of a "Minimal" system / container environment you don't need to have any and that does make sense. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 1226017] New: fwupd fails TPM fw upgrade with 'Secure boot is enabled, but shim isn't installed to EFI/opensuse/shim.efi'
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1226017 Bug ID: 1226017 Summary: fwupd fails TPM fw upgrade with 'Secure boot is enabled, but shim isn't installed to EFI/opensuse/shim.efi' Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: anselm.gora(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 Build Identifier: fwupd expects to find EFI/opensuse/shim.efi while on openSUSE Aeon the path is EFI/systemd/shim.efi https://github.com/fwupd/fwupd/blob/eb3d26079d7b0e6f0db70b066fcb7b31ac7bcec… fwupd seems to use os release ID but it's also a build option: https://github.com/fwupd/fwupd/blob/eb3d26079d7b0e6f0db70b066fcb7b31ac7bcec… Tumbleweed seems to patch it: https://build.opensuse.org/projects/openSUSE:Factory/packages/fwupd/files/f… Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1217138] fwupdmgr update fails: Secure boot is enabled, but shim isn't installed to EFI/opensuse/shimx64.efi
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1217138 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.opensuse.o | |rg/show_bug.cgi?id=1234461 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234461] New: Update fwupd to newer version
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234461 Bug ID: 1234461 Summary: Update fwupd to newer version 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: taaem(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, there are multiple bugs in bugzilla (https://bugzilla.opensuse.org/show_bug.cgi?id=1217138 https://bugzilla.opensuse.org/show_bug.cgi?id=1226017) which could be probably resolved by updating fwupd to version at least 1.9.26. Furthermore, there is a new major release out 2.x.x. Would it be possible to either update to the latest 1.x.x version: 1.9.27 or the even the latest 2.x.x: 2.0.3? Thank you in advance and best regards, Tim -- You are receiving this mail because: You are on the CC list for the bug.

1 1

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

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233824 https://bugzilla.suse.com/show_bug.cgi?id=1233824#c28 --- Comment #28 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- Would that be a nice Christmas/New Year present for our openSUSE systems community, then? Enjoy your free days in the next weeks, and perhaps we will receive the fixes as a New Year present. :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0