February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1207892] New: [Build 20230202] dracut: dips integrity check failed
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207892 Bug ID: 1207892 Summary: [Build 20230202] dracut: dips integrity check failed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3091784/modules/fips _setup/steps/22 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-fips@64bit_virtio fails in [fips_setup](https://openqa.opensuse.org/tests/3091784/modules/fips_setup/st… ## Test suite description ## Reproducible Fails since (at least) Build [20221127](https://openqa.opensuse.org/tests/2910314) ## Expected result Last good: [20221126](https://openqa.opensuse.org/tests/2908533) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1205149] New: %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205149 Bug ID: 1205149 Summary: %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- kernel rpm scriptlets will be moved to a separate subpackage (see https://github.com/openSUSE/suse-module-tools/pull/64) kmps do already (pre)require suse-kernel-rpm-scriptlets just fine. However during build those prerequires are not seen by the OBS schedule as they are hidden inside the %suse_kernel_module_package macro. So the package install check after build fails due to missing scriptlets. Therefore %kernel_module_package_buildreqs needs to list suse-kernel-rpm-scriptlets -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1194784] New: Yast should use RSpec verifying doubles everywhere
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1194784 Bug ID: 1194784 Summary: Yast should use RSpec verifying doubles everywhere Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lslezak(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- This should avoid bugs in the unit tests. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1201815] New: Inconsistent Bluetooth status display
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201815 Bug ID: 1201815 Summary: Inconsistent Bluetooth status display Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860354 --> http://bugzilla.opensuse.org/attachment.cgi?id=860354&action=edit Bluetooth status in GNOME Sometimes when the Bluetooth status is "disabled", the suggested action in the GNOME menu is "Turn Off" (instead of "Turn On"). So yo have to "Turn Off" even if it's off, just to be able to see (if at all) a "Turn On" again. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1203092] New: GNU grep 3.8 egrep / grep warnings and migration to grep -E / grep -F
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1203092 Bug ID: 1203092 Summary: GNU grep 3.8 egrep / grep warnings and migration to grep -E / grep -F Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: schwab(a)suse.de Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- GNU grep from 3.8 emitting warnings when invoking egrep/fgrep https://build.opensuse.org/request/show/1001097 > egrep and fgrep commands, deprecated since 2007, now warn that they are obsolescent and should be replaced by grep -E / -F We should look to eliminate egrep/fgrep from the distribution and replace all usages of egrep/fgrep with grep -E and grep -F, respectively. At the moment dropping these items breaks the grep build itself, it's all over the place. -- You are receiving this mail because: You are on the CC list for the bug.

1 33

[Bug 1197477] New: network port on monitor integrated usb hub never detects a link
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1197477 Bug ID: 1197477 Summary: network port on monitor integrated usb hub never detects a link Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: josua.m(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Greetings everybody! I recently got a new Monitor on my desk with an integrated USB-3.0 Hub and an integrated RJ45 network interface. But with openSUSE Leap (both 15.3 and 15.4-Beta), the system never detects a link - as shown by the ethtool output below: sudo ethtool usb0 [sudo] Passwort f�r root: Settings for usb0: Current message level: 0x00000007 (7) drv probe link Link detected: no I have tested this with two laptops: - An ASUS UX331UN (i7-8250U) running Leap 15.3 - An ROG G14 (Ryzen 5800) running Leap 15.4 Beta I have also tested 2 other operating systems - On Windows the interface works - On Ubuntu Focal the interface works Very rarely, a link is detected for a very short time, leading to networkmanager applet indicating connection attempt for a second or two. I caputres such a case in the dmesg below: [11867.152288] usb 1-3: new high-speed USB device number 15 using xhci_hcd [11867.302285] usb 1-3: New USB device found, idVendor=0424, idProduct=2806, bcdDevice= 2.10 [11867.302292] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11867.302295] usb 1-3: Product: USB2806 Smart Hub [11867.302298] usb 1-3: Manufacturer: Microchip [11867.304310] hub 1-3:1.0: USB hub found [11867.304698] hub 1-3:1.0: 6 ports detected [11867.432196] usb 2-4: new SuperSpeed Gen 1 USB device number 9 using xhci_hcd [11867.456449] usb 2-4: New USB device found, idVendor=0424, idProduct=5806, bcdDevice= 2.10 [11867.456457] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11867.456462] usb 2-4: Product: USB5806 Smart Hub [11867.456465] usb 2-4: Manufacturer: Microchip [11867.457681] hub 2-4:1.0: USB hub found [11867.457710] hub 2-4:1.0: 5 ports detected [11867.600165] usb 1-3.6: new high-speed USB device number 16 using xhci_hcd [11867.704259] usb 1-3.6: New USB device found, idVendor=0424, idProduct=284c, bcdDevice= 2.00 [11867.704266] usb 1-3.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11867.704269] usb 1-3.6: Product: Hub Feature Controller [11867.704272] usb 1-3.6: Manufacturer: Microchip [11867.708519] hid-generic 0003:0424:284C.0005: hiddev96,hidraw1: USB HID v1.10 Device [Microchip Hub Feature Controller] on usb-0000:00:14.0-3.6/input1 [11867.780407] usb 2-4.3: new SuperSpeed Gen 1 USB device number 10 using xhci_hcd [11867.800927] usb 2-4.3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=33.00 [11867.800933] usb 2-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [11867.800936] usb 2-4.3: Product: USB 10/100/1000 LAN [11867.800939] usb 2-4.3: Manufacturer: Realtek [11867.800941] usb 2-4.3: SerialNumber: 0033000001 [11867.825408] cdc_ncm 2-4.3:2.0: MAC-Address: b0:4f:13:d7:59:ae [11867.825414] cdc_ncm 2-4.3:2.0: setting rx_max = 16384 [11867.825522] cdc_ncm 2-4.3:2.0: setting tx_max = 16384 [11867.826100] cdc_ncm 2-4.3:2.0 usb0: register 'cdc_ncm' at usb-0000:00:14.0-4.3, CDC NCM, b0:4f:13:d7:59:ae [11867.972746] usb 1-3.6: USB disconnect, device number 16 [11868.208085] usb 1-3.6: new high-speed USB device number 17 using xhci_hcd [11868.312781] usb 1-3.6: New USB device found, idVendor=0424, idProduct=2840, bcdDevice= 2.10 [11868.312788] usb 1-3.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11868.312792] usb 1-3.6: Product: Hub Feature Controller [11868.312796] usb 1-3.6: Manufacturer: Microchip [11870.916715] cdc_ncm 2-4.3:2.0 usb0: 1000 mbit/s downlink 1000 mbit/s uplink [11871.172732] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready [11888.115889] usb 1-3.6: reset high-speed USB device number 17 using xhci_hcd [11888.221821] usb 1-3.6: device firmware changed [11888.221922] usb 1-3.6: USB disconnect, device number 17 [11888.303624] usb 1-3.6: new high-speed USB device number 18 using xhci_hcd [11888.407663] usb 1-3.6: New USB device found, idVendor=0424, idProduct=284c, bcdDevice= 2.00 [11888.407670] usb 1-3.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11888.407674] usb 1-3.6: Product: Hub Feature Controller [11888.407677] usb 1-3.6: Manufacturer: Microchip [11888.411497] hid-generic 0003:0424:284C.0006: hiddev96,hidraw1: USB HID v1.10 Device [Microchip Hub Feature Controller] on usb-0000:00:14.0-3.6/input1 Also adding an lsusb: Bus 002 Device 010: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 009: ID 0424:5806 Microchip Technology, Inc. (formerly SMSC) USB5806 Smart Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 13d3:5a09 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 018: ID 0424:284c Microchip Technology, Inc. (formerly SMSC) Hub Feature Controller Bus 001 Device 015: ID 0424:2806 Microchip Technology, Inc. (formerly SMSC) USB2806 Smart Hub Bus 001 Device 006: ID 0781:55a1 SanDisk Corp. Cruzer Spark Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I'd be happy to do experiments if somebody can point me in a meaningful direction on how to approach this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1208460] New: Blank screen with Radeon RX 5700
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208460 Bug ID: 1208460 Summary: Blank screen with Radeon RX 5700 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: adam(a)mizerski.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/109.0 Build Identifier: Few days ago my Radeon RX 5700 after 3 years of working absolutely fine, kind of stopped working. The symptoms are: - At BIOS and GRUB there is video output. - If I run the system with "nomodeset" kernel option, then there is video output (obviously without acceleration and limited to low resolution). - It's not a faulty cable, because I tested it with other cables. I usually use HDMI cable, but with DisplayPort it's the same. - It's not a faulty monitor, because I use it also with my laptop on a second input. - If I put my card into another computer with Windows, it works with acceleration, like there's nothing wrong. - But if I start my Tumbleweed with amdgpu drivers, then as soon as kernel loads drm driver (so it's even before Xorg starts), the screen goes blank (the monitor shows "no signal" and shuts off). It doesn't matter if I boot my Tumbleweed with current or previous kernel. It doesn't matter if it's my Tumbleweed or a Leap 15.4 booted from usb stick. dmesg: https://paste.opensuse.org/pastes/c4df53bb0f7a It says: amdgpu 0000:09:00.0: [drm] Cannot find any crtc or sizes Xorg.0.log: https://paste.opensuse.org/pastes/e9bd760602d1 It says: (WW) AMDGPU(0): Unable to find connected outputs I also tried: - remove "quiet", remove "splash=silent", and append "plymouth.enable=0" (as written at https://en.opensuse.org/SDB:Nomodeset:_Work_Around_Graphic_Upgrade_&_Instal…) - nothing changed - amdgpu.dc=0 - screen stays on, but shows nothing (just black) Reproducible: Always Steps to Reproduce: Just boot the system Actual Results: Screen goes into suspend Expected Results: Graphics on screen -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1208091] New: VUL-0: CVE-2023-25165: trivy: helm: getHostByName Function Information Disclosure
by bugzilla_noreply＠suse.com 05 Mar '23

05 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208091 Bug ID: 1208091 Summary: VUL-0: CVE-2023-25165: trivy: helm: getHostByName Function Information Disclosure Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/356535/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: dmueller(a)suse.com Reporter: thomas.leroy(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1208083 Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1208083 +++ CVE-2023-25165 Helm is a tool that streamlines installing and managing Kubernetes applications.`getHostByName` is a Helm template function introduced in Helm v3. The function is able to accept a hostname and return an IP address for that hostname. To get the IP address the function performs a DNS lookup. The DNS lookup happens when used with `helm install|upgrade|template` or when the Helm SDK is used to render a chart. Information passed into the chart can be disclosed to the DNS servers used to lookup the IP address. For example, a malicious chart could inject `getHostByName` into a chart in order to disclose values to a malicious DNS server. The issue has been fixed in Helm 3.11.1. Prior to using a chart with Helm verify the `getHostByName` function is not being used in a template to disclose any information you do not want passed to DNS servers. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25165 https://bugzilla.redhat.com/show_bug.cgi?id=2168458 https://www.cve.org/CVERecord?id=CVE-2023-25165 https://github.com/helm/helm/commit/5abcf74227bfe8e5a3dbf105fe62e7b12deb58d2 https://github.com/helm/helm/security/advisories/GHSA-pwcw-6f5g-gxf8 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1207285] New: VirtualBox 7.0.6 is available (new version with Security fixes)
by bugzilla_noreply＠suse.com 05 Mar '23

05 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207285 Bug ID: 1207285 Summary: VirtualBox 7.0.6 is available (new version with Security fixes) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All URL: https://www.virtualbox.org/wiki/Changelog-7.0#v6 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: jayjayjazz(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: Community User Blocker: --- VirtualBox 7.0.6 (released January 17 2023) This is a maintenance release. The following items were fixed and/or added: [1] - VMM: Fixed guru running the FreeBSD loader on older Intel CPUs without unrestricted guest support (bug #21332) - GUI: Fixed virtual machines grouping when VM was created or modified in command line (bugs #11500, #20933) - GUI: Introduced generic changes in settings dialogs - VirtioNet: Fixed broken network after loading saved state (bug #21172) - Storage: Added support for increasing the size of the following VMDK image variants: monolithicFlat, monolithicSparse, twoGbMaxExtentSparse, twoGbMaxExtentFlat - VBoxManage: Added missing --directory switch for guestcontrol mktemp command - Mouse Integration: Guest was provided with extended host mouse state (bug #21139) - DnD: Introduced generic improvements - Guest Control: Fixed handling creation mode for temporary directories (bug #21394) - Linux Host and Guest: Added initial support for building UEK7 kernel on Oracle Linux 8 - Linux Host and Guest: Added initial support for RHEL 9.1 kernel - Windows Host: Fixed support for VM autostart (bug#21349) - Linux Guest Additions: Added initial support for kernel 6.2 for vboxvideo - Audio: The "--audio" option in VBoxManage is now marked as deprecated; please use "--audio-driver" and "--audio-enabled" instead. This will allow more flexibility when changing the driver and/or controlling the audio functionality Additionally, it fixes 6 CVE's: [2] CVE-2023-21886 Oracle VM VirtualBox Core Multiple Yes 8.1 Network High None None Un- changed High High High Prior to 6.1.42, prior to 7.0.6 CVE-2023-21898 Oracle VM VirtualBox Core None No 5.5 Local Low Low None Un- changed None None High Prior to 6.1.42, prior to 7.0.6 See Note 1 CVE-2023-21899 Oracle VM VirtualBox Core None No 5.5 Local Low Low None Un- changed None None High Prior to 6.1.42, prior to 7.0.6 See Note 1 CVE-2023-21884 Oracle VM VirtualBox Core None No 4.4 Local Low High None Un- changed None None High Prior to 6.1.42, prior to 7.0.6 CVE-2023-21885 Oracle VM VirtualBox Core None No 3.8 Local Low Low None Changed Low None None Prior to 6.1.42, prior to 7.0.6 See Note 2 CVE-2023-21889 Oracle VM VirtualBox Core None No 3.8 Local Low Low None Changed Low None None Prior to 6.1.42, prior to 7.0.6 Note 1: Applies to VirtualBox VMs running Windows 7 and later. Note 2: Applies to Windows only. Links: [1] https://www.virtualbox.org/wiki/Changelog-7.0#v6 [2] https://www.oracle.com/security-alerts/cpujan2023.html#AppendixOVIR -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1206945] New: Change DPLUGIN_DIRECTORY breaks php-imagick
by bugzilla_noreply＠suse.com 05 Mar '23

05 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206945 Bug ID: 1206945 Summary: Change DPLUGIN_DIRECTORY breaks php-imagick 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: suse+build(a)de-korte.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The recent changes to libheif seems to break php-imagick: dlopen: /usr/libexec/libheif/libheif-rav1e.so: undefined symbol: _ZNK4heif14HeifPixelImage18get_bits_per_pixelE12heif_channel -- You are receiving this mail because: You are on the CC list for the bug.

1 8