August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1218125] New: cmake outdated
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1218125 Bug ID: 1218125 Summary: cmake outdated Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- All SLE service packs have a cmake except SP5, current version in Leap is 3.20, some projects insist on more recent version like 3.23, Factory has 3.27. Sounds like it's time to upgrade cmake again. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1217747] New: colord: reproducible builds: icc varies from CPU
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1217747 Bug ID: 1217747 Summary: colord: reproducible builds: icc varies from CPU Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://github.com/omgovich/colord/issues/122 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: gnome-bugs(a)suse.de Blocks: 1100677 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for ALP+openSUSE, I found that our colord package varied from differences in .icc files caused by differences in build machine CPU capabilities (probably AVX) Also filed upstream at https://github.com/omgovich/colord/issues/122 but they seem inactive. You find a reproducer and more details there. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228864] New: per-Bootloader can break systemd-boot installations dropping shim.efi
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1228864 Bug ID: 1228864 Summary: per-Bootloader can break systemd-boot installations dropping shim.efi Classification: openSUSE Product: openSUSE Leap Micro Version: 6.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: screening-team-bugs(a)suse.de Reporter: aplanas(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When calling pbl.sh --install to install the bootloader in a systemd-boot it will drop the shim.efi, breaking secure boot and predictions in systemd-boot systems. Ideally in BLS systems it should call for now 'sdbootutil install' or 'sdbootutil update', as it will take care of keeping the shim.efi and renaming the bootloader as grub.efi, so secure boot is enabled in both systems -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1228862] New: When sdbootuil is used, transactional-update bootloader will address only the grub2 case
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1228862 Bug ID: 1228862 Summary: When sdbootuil is used, transactional-update bootloader will address only the grub2 case 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: aplanas(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When sdbootutil is used, the bootloader can be systemd-boot or grub2 with the BLS patches. `transactional-update bootloader` should be aware and avoid the changes in the grub configuration file, and the boot loader installation via pbl.sh --install. pbl.sh is not aware of sdbootutil for bootloader installation and will drop the shim.efi if systemd-boot is used -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1228647] New: RpmDb issues after zypper source-install with single_rpmtrans backend
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1228647 Bug ID: 1228647 Summary: RpmDb issues after zypper source-install with single_rpmtrans backend Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: ma(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876407 --> https://bugzilla.suse.com/attachment.cgi?id=876407&action=edit RPM debug output from single_rpmtrans si The issue occurs only if the single_rpmtrans backend drives the installation of a source.rpm.(seen with rpm-4.14.3 on Leap-15.4; rpm-4.19.1.1 on TW) After the install (at least) the bin-packages fileslist is replaced by the one of the .src.rpm. > hobbes:~ (0)# rpm -qa rpm > rpm-4.14.3-150400.59.3.1.x86_64 > hobbes:~ (0)# rpm -ql rpm | head -n 1 > /bin/rpm > > hobbes:~ (0)# zypper -n si rpm > Backend: single_rpmtrans > (1/1) Installing: rpm-4.14.3-150400.59.3.1.src ...........................[done] > > hobbes:~ (0)# rpm -qa rpm > rpm-4.14.3-150400.59.3.1.x86_64 > hobbes:~ (0)# rpm -ql rpm | head -n 1 > /usr/src/packages/SOURCES/RPM-HOWTO.tar.bz2 Not fixed by a rebuilddb: > hobbes:~ (0)# rpm --rebuilddb > hobbes:~ (0)# rpm -qa rpm > rpm-4.14.3-150400.59.3.1.x86_64 > hobbes:~ (0)# rpm -ql rpm | head -n 1 > /usr/src/packages/SOURCES/RPM-HOWTO.tar.bz2 A reinstall of the bin-package is required to fix it. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1226194] New: Make JeOS images work with u-boot BOOTSTD
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1226194 Bug ID: 1226194 Summary: Make JeOS images work with u-boot BOOTSTD Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: mbrugger(a)suse.com Reporter: schwab(a)suse.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- U-Boot configurations that use CONFIG_BOOTSTD_DEFAULTS or CONFIG_BOOTSTD_FULL no longer find the device tree file on the disk (they pass on the builtin device tree instead). Either the patch 0001-XXX-openSUSE-XXX-Prepend-partition-.patch needs to be ported to BOOTSTD or the boot setup needs to be changed. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1229909] New: Discord outdated (0.0.65 > 0.0.66) and crashes in current non-oss Tumbleweed Repos
by bugzilla_noreply＠suse.com 06 Oct '24

06 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229909 Bug ID: 1229909 Summary: Discord outdated (0.0.65 > 0.0.66) and crashes in current non-oss Tumbleweed Repos 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: coldreactive(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877018 --> https://bugzilla.suse.com/attachment.cgi?id=877018&action=edit Log for when it crashed. Packman version for whatever reason doesn't crash. Originally made a thread on the openSUSE Forums for troubleshooting: https://forums.opensuse.org/t/discord-keeps-crashing-when-hovering-over-gif… See attached text file for terminal output of what was going on during operation. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227597] New: OpenGL and driver's misbehaving inside Windows VM
by bugzilla_noreply＠suse.com 05 Oct '24

05 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227597 Bug ID: 1227597 Summary: OpenGL and driver's misbehaving inside Windows VM Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: x86-64 OS: Windows 10 Status: NEW Severity: Minor Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: small.coffee5952(a)fastmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875980 --> https://bugzilla.suse.com/attachment.cgi?id=875980&action=edit Windows driver/monitor I have been trying to create a functional Windows VM inside Virt-Manager for some time. I have been having an issue where the VM only operates at 1hz, but also Minecraft will simply not launch and error out. I believe these issues are related. I have attached a logfile with the Minecraft error and a screenshot of the refresh rate. Oddly, the Windows settings claims it is only running at 1hz but the advanced monitor settings in Windows for the driver claims it is running at 64hz, although it is clearly not running at 64hz. My host machine (Running openSUSE Slowroll) properly works with the monitor at 240hz. The issue occurs on VMs with the latest, stable, or without the win guest tools from https://github.com/virtio-win/virtio-win-pkg-scripts. Unless I am installing them incorrectly they seem to have no affect on the issues. My investigation of the Minecraft only got me as far as "something is wrong with OpenGL" which is distributed through the spice drivers. I am using as close to default settings as possible, but have tried tinkering with them and they have had no affect on the issues either. This issue does NOT seem to be distro specific. I have confirmed it has happened to me on Debian, Tumbleweed, and now Slowroll in the past few days. However, it has also happened to me on Arch Linux quite a few months ago. Apologies for the bad report, I have made very few bug reports ever before and was unsure where to even report it. If any more detail is needed or this should be reported elsewhere please tell me. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1219525] New: Notification on successful transactional-update is not persistent
by bugzilla_noreply＠suse.com 05 Oct '24

05 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219525 Bug ID: 1219525 Summary: Notification on successful transactional-update is not persistent Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Transactional Update Assignee: sfalken(a)cloverleaf-linux.org Reporter: sfalken(a)cloverleaf-linux.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On Kalpa, transactional-update-notifier does operate correctly on Kalpa, but it pops up when run, and only survives as long as the delay set in `System Settings->Notifications->Hide After` is set to. This isn't the intended behavior, the notification should be persistent, so the user is aware that an update has been applied, and can choose whether to reboot or not -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219803] New: Lenovo Yoga 14APH8 headphones jack requires bass speaker to be full volume
by bugzilla_noreply＠suse.com 05 Oct '24

05 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219803 Bug ID: 1219803 Summary: Lenovo Yoga 14APH8 headphones jack requires bass speaker to be full volume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pinchon.guillaume(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Symptoms : When connecting headphones to the laptop's jack it's required to set the Bass Speaker to full volume through alsamixer otherwise we get no sound. Either that or replacing in /usr/share/alsa-card-profile/mixer/paths/analog-output-headphones.conf : [Element Bass Speaker] switch = off volume = off with : [Element Bass Speaker] switch = off volume = merge System info : Operating System: openSUSE Tumbleweed 20240209 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.8.0-rc3-3.g7450939-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7840HS with Radeon 780M Graphics Memory: 27.1 Gio of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82Y8 System Version: Yoga Pro 7 14APH8 hwinfo --sound : 12: PCI 6300.1: 0403 Audio device [Created at pci.386] Unique ID: UGCg.OQPqPLYNCh0 Parent ID: JZZT.maS73mB38XF SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:63:00.1 SysFS BusID: 0000:63:00.1 Hardware Class: sound Model: "ATI Audio device" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x1640 SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x3824 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x785c8000-0x785cbfff (rw,non-prefetchable) IRQ: 90 (no events) Module Alias: "pci:v00001002d00001640sv000017AAsd00003824bc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #27 (PCI bridge) 22: PCI 6300.6: 0403 Audio device [Created at pci.386] Unique ID: puer.m6xb4yIjnP9 Parent ID: JZZT.maS73mB38XF SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:63:00.6 SysFS BusID: 0000:63:00.6 Hardware Class: sound Model: "AMD Family 17h (Models 10h-1fh) HD Audio Controller" Vendor: pci 0x1022 "AMD" Device: pci 0x15e3 "Family 17h (Models 10h-1fh) HD Audio Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x3882 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x785c0000-0x785c7fff (rw,non-prefetchable) IRQ: 43 (327 events) Module Alias: "pci:v00001022d000015E3sv000017AAsd00003882bc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #27 (PCI bridge) -- You are receiving this mail because: You are on the CC list for the bug.

1 2