November 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1216463] Default UEFI firmware choice set up by gnome-boxes Windows 10/11 assistant can't boot into Windows 10 install disk
by bugzilla_noreply＠suse.com 02 Nov '23

02 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216463 https://bugzilla.suse.com/show_bug.cgi?id=1216463#c10 James Fehlig <jfehlig(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kallan(a)suse.com --- Comment #10 from James Fehlig <jfehlig(a)suse.com> --- (In reply to ell1e from comment #9) > virt-manager launches and works fine without root here, which is the part > that worries me. I assume to create HW accelerated VMs it should normally > require some sort of elevation? A normal user should be able to start a kvm-accelerated VM, but it will have limited privileges and functionality. See some of the links I referenced in #5. BTW, I'm not sure if vTPM works with an unprivileged VM. It's clear the type of VM you are trying to create does not work unprivileged. From your virt-manager log, I see it's unable to connect to the system daemon: [Wed, 01 Nov 2023 20:55:01 virt-manager 5426] DEBUG (engine:180) Autostart connection error: Unable to connect to libvirt qemu:///system. Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory Libvirt URI is: qemu:///system I think the socket path is a little misleading. Perhaps virt-manager is only reporting the last one it tried. On Leap 15.5, the monolithic libvirtd is still the "preferred" deployment, so the path should be /var/run/libvirt/libvirt-sock. But that's a cosmetic detail. Do you have the libvirtd service enabled? E.g. is it shown as enabled and running in the output of 'systemctl status libvirtd.service'? If not, enable and start it (systemctl enable libvirtd.service && systemctl start libvirtd.service), then see if you can connect to the system daemon with virt-manager. You should be prompted for root passwd before you can actually do anything useful on the privileged connection. KVM+TPM2.0+Win10/11 has been tested on SLES 15 SP5, which has the same virtualization components as Leap 15.5, but only with the libvirt system daemon. I think you will also have success after connecting virt-manager to your system daemon. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216831] New: error: Verifying a signature using certificate E96C496E4E77C159C2FCA053062F9FD4D6D11CE4
by bugzilla_noreply＠suse.com 02 Nov '23

02 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216831 Bug ID: 1216831 Summary: error: Verifying a signature using certificate E96C496E4E77C159C2FCA053062F9FD4D6D11CE4 Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: opensuse(a)cubelike.com QA Contact: packagehub-bugs(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Attempting to download packages results in the following errors: GPG key at https://download.opensuse.org/repositories/hardware:/razer/Fedora_38/repoda… (0xD6D11CE4) is already installed error: Verifying a signature using certificate E96C496E4E77C159C2FCA053062F9FD4D6D11CE4 (hardware OBS Project <hardware(a)build.opensuse.org>): 1. Certificiate 062F9FD4D6D11CE4 invalid: certificate is not alive because: The primary key is not live because: Expired on 2023-05-23T13:32:57Z 2. Key 062F9FD4D6D11CE4 invalid: key is not alive because: The primary key is not live because: Expired on 2023-05-23T13:32:57Z ... The GPG keys listed for the "hardware:razer (Fedora_38)" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository.. Failing package is: openrazer-daemon-3.7.0-1.1.noarch GPG Keys are configured as: https://download.opensuse.org/repositories/hardware:/razer/Fedora_38/repoda… Public key for openrazer-kernel-modules-dkms-3.7.0-1.1.noarch.rpm is not trusted. Failing package is: openrazer-kernel-modules-dkms-3.7.0-1.1.noarch GPG Keys are configured as: https://download.opensuse.org/repositories/hardware:/razer/Fedora_38/repoda… Public key for openrazer-meta-3.7.0-1.1.noarch.rpm is not trusted. Failing package is: openrazer-meta-3.7.0-1.1.noarch GPG Keys are configured as: https://download.opensuse.org/repositories/hardware:/razer/Fedora_38/repoda… Public key for python3-openrazer-3.7.0-1.1.noarch.rpm is not trusted. Failing package is: python3-openrazer-3.7.0-1.1.noarch GPG Keys are configured as: https://download.opensuse.org/repositories/hardware:/razer/Fedora_38/repoda… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1216677] python3-yamllint "No module named 'pkg_resources'"
by bugzilla_noreply＠suse.com 02 Nov '23

02 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216677 https://bugzilla.suse.com/show_bug.cgi?id=1216677#c3 --- Comment #3 from Marcus Meissner <meissner(a)suse.com> --- openSUSE-RU-2023:0346-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1151703,1216677 CVE References: JIRA References: Sources used: openSUSE Backports SLE-15-SP4 (src): python-yamllint-1.22.1-bp154.2.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1151703] python3-yamllint is missing requirement on python3-setuptools
by bugzilla_noreply＠suse.com 02 Nov '23

02 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1151703 https://bugzilla.suse.com/show_bug.cgi?id=1151703#c4 --- Comment #4 from Marcus Meissner <meissner(a)suse.com> --- openSUSE-RU-2023:0346-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1151703,1216677 CVE References: JIRA References: Sources used: openSUSE Backports SLE-15-SP4 (src): python-yamllint-1.22.1-bp154.2.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216677] python3-yamllint "No module named 'pkg_resources'"
by bugzilla_noreply＠suse.com 02 Nov '23

02 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216677 https://bugzilla.suse.com/show_bug.cgi?id=1216677#c2 --- Comment #2 from Marcus Meissner <meissner(a)suse.com> --- openSUSE-RU-2023:0347-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1151703,1216677 CVE References: JIRA References: Sources used: openSUSE Backports SLE-15-SP5 (src): python-yamllint-1.22.1-bp155.3.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1151703] python3-yamllint is missing requirement on python3-setuptools
by bugzilla_noreply＠suse.com 02 Nov '23

02 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1151703 https://bugzilla.suse.com/show_bug.cgi?id=1151703#c3 --- Comment #3 from Marcus Meissner <meissner(a)suse.com> --- openSUSE-RU-2023:0347-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1151703,1216677 CVE References: JIRA References: Sources used: openSUSE Backports SLE-15-SP5 (src): python-yamllint-1.22.1-bp155.3.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1215943] [Build 20231003] openQA test fails in podman_pods
by bugzilla_noreply＠suse.com 02 Nov '23

02 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215943 https://bugzilla.suse.com/show_bug.cgi?id=1215943#c5 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kukuk(a)suse.com |dmueller(a)suse.com CC| |kukuk(a)suse.com --- Comment #5 from Thorsten Kukuk <kukuk(a)suse.com> --- The files zless, zmore and zgrep are from Dirk: https://build.opensuse.org/package/rdiff/openSUSE:Factory/busybox-links?lin… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216784] New: koosmile p8 black display
by bugzilla_noreply＠suse.com 02 Nov '23

02 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216784 Bug ID: 1216784 Summary: koosmile p8 black display Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: deathgaze2497(a)protonmail.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 870558 --> https://bugzilla.suse.com/attachment.cgi?id=870558&action=edit xorg log file install opensuse with hdmi. Display on koosmile p8 is black with a backlight on upon boot. I believe it is intel i915 driver related here are some of the errors displayed. Oct 31 04:14:57 user-Default-string kernel: i915 0000:00:02.0: [drm] *ERROR* hback porch < 16 pixels Oct 31 04:14:57 user-Default-string kernel: i915 0000:00:02.0: [drm] *ERROR* hback porch < 16 pixels Oct 31 04:16:59 user-Default-string kernel: i915 0000:00:02.0: [drm] *ERROR* hback porch < 16 pixels Oct 31 04:17:00 user-Default-string kernel: i915 0000:00:02.0: [drm] *ERROR* hback porch < 16 pixels Oct 31 04:17:39 user-Default-string kernel: i915 0000:00:02.0: [drm] *ERROR* hback porch < 16 pixels Oct 31 04:18:04 user-Default-string kernel: i915 0000:00:02.0: [drm] *ERROR* hback porch < 16 pixels Oct 31 04:18:05 user-Default-string kernel: i915 0000:00:02.0: [drm] *ERROR* hback porch < 16 pixels Oct 31 04:18:06 user-Default-string kernel: i915 0000:00:02.0: [drm] *ERROR* hback porch < 16 pixels Oct 31 04:19:14 user-Default-string kernel: i915 0000:00:02.0: [drm] *ERROR* hback porch < 16 pixels Oct 31 04:27:03 user-Default-string kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=28466 end=28467) time 7 us, min 1271, max 1279, scanline start 1280, end 1280 Oct 31 04:27:51 user-Default-string kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=31353 end=31354) time 7 us, min 1271, max 1279, scanline start 1280, end 1281 20: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.i4vzlYvwb6C SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Device Name: "Onboard - Video" Model: "Intel VGA compatible controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x46d1 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x7270 Driver: "i915" Driver Modules: "i915" Memory Range: 0x6000000000-0x6000ffffff (rw,non-prefetchable) Memory Range: 0x4000000000-0x400fffffff (ro,non-prefetchable) I/O Ports: 0x5000-0x503f (rw) Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) IRQ: 127 (131010 events) Module Alias: "pci:v00008086d000046D1sv00008086sd00007270bc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown Primary display adapter: #20 DSI-1 connected 1600x1000+0+0 right (normal left inverted right x axis y axis) 108mm x 172mm 1000x1600 60.48*+ 800x600 60.25 640x480 60.00 320x240 59.52 960x600 60.29 928x580 60.13 800x500 60.46 768x480 60.42 720x480 60.27 640x400 59.95 320x200 58.96 864x486 60.38 720x400 60.22 640x350 59.77 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1216836] New: POR_Recovery_Count rapidly rising since a week
by bugzilla_noreply＠suse.com 02 Nov '23

02 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216836 Bug ID: 1216836 Summary: POR_Recovery_Count rapidly rising since a week Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Storage Assignee: kernel-bugs(a)suse.de Reporter: dutchkind(a)txoriaskea.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since just over a week the POR_Recovery_Count of my internal ssd is rapidly rising, in two years it went up to 44 and now in just over a week it is already over 70, adding each poweroff one count. What has changed causing this? Has the one or two seconds after poweroff that the power to the disk is maintained been reduced? I know there is controversy about this, but this count is probably not for nothing to keep and it would be good to tackle the cause. I have been looking through the systemd journal and can't really find anything that could cause it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216429] VUL-0: CVE-2023-46267: roundcube: XSS via a text/html e-mail message containing an SVG image with a USE element
by bugzilla_noreply＠suse.com 02 Nov '23

02 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216429 https://bugzilla.suse.com/show_bug.cgi?id=1216429#c3 --- Comment #3 from Marcus Meissner <meissner(a)suse.com> --- openSUSE-SU-2023:0345-1: An update that fixes one vulnerability is now available. Category: security (important) Bug References: 1216429 CVE References: CVE-2023-5631 JIRA References: Sources used: openSUSE Backports SLE-15-SP5 (src): roundcubemail-1.6.4-bp155.2.6.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0