January 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1234858] Intel hybrid driver "hybrid_drv_video.so" for VA API (VAAPI) does not work
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234858 https://bugzilla.suse.com/show_bug.cgi?id=1234858#c2 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #2 from Stefan Dirsch <sndirsch(a)suse.com> --- https://build.opensuse.org/request/show/1234809 Should be available soon in TW. I don't plan to fix this still for SP6/Leap 15.6. Also I don't think I have Intel hardware old enough to test this driver. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234858] Intel hybrid driver "hybrid_drv_video.so" for VA API (VAAPI) does not work
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234858 https://bugzilla.suse.com/show_bug.cgi?id=1234858#c1 --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- done ------------------------------------------------------------------- Fri Jan 3 22:36:02 UTC 2025 - Stefan Dirsch <sndirsch(a)suse.com> - fixed driver for current libva by switchting to gentoo patches (boo#1234858) * intel-hybrid-codec-driver-2.0.0-gcc10-fix.patch * intel-hybrid-codec-driver-2.0.0-invalid-read-fix.patch * intel-hybrid-codec-driver-2.0.0-nullptr-fix.patch * intel-hybrid-codec-driver-2.0.0-vadriverinit-fix.patch * intel-hybrid-codec-driver-2.0.0-x11-fix.patch - supersedes the following patches * U_Update-the-dependency-to-libva-2.0.patch * n_libva-2.0-ABI-header-fix.patch * u_gcc10.patch - raised driver version number to 2.0.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234858] Intel hybrid driver "hybrid_drv_video.so" for VA API (VAAPI) does not work
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234858 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234789] buggy authentication message
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234789 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx(a)yahoo.com Flags| |needinfo?(nwr10cst-oslnx@ya | |hoo.com) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234789] buggy authentication message
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234789 https://bugzilla.suse.com/show_bug.cgi?id=1234789#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- Hard to debug. I suggest to rename your ~/.Xauthority file and restart your Xsession. Then hopefully the issue is gone. Try this first. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234914] kernel-firmware-nvidia-gspx-G06-cuda lagging behind breaks nvidia-open for Tumbleweed users
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234914 https://bugzilla.suse.com/show_bug.cgi?id=1234914#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(bizyaev(a)zoho.com) Status|NEW |IN_PROGRESS Priority|P5 - None |P3 - Medium Assignee|gfx-bugs(a)suse.de |sndirsch(a)suse.com CC| |bizyaev(a)zoho.com, | |eich(a)suse.com --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- kernel-firmware-nvidia-gspx-G06-cuda=565.57.01 is only needed on SLES for historic reasons. Actually it became a fake/meta package. You don't need it on TW. $ rpm --requires -qp nvidia-open-driver-G06-signed-cuda-kmp-default-565.57.01_k6.12.6_1-173.2.x86_64.rpm | grep -v ksym | grep gsp (kernel-firmware-nvidia-gspx-G06 = 565.57.01 if nvidia-compute-utils-G06 = 565.57.01) So once you install nvidia-compute-utils-G06 = 565.57.01 the appropriate kernel-firmware package gets installed. Both are in NVIDIA's CUDA repo. https://developer.download.nvidia.com/compute/cuda/repos/opensuse15/x86_64/ Not sure why this doesn't work on your TW installation. Maybe it helps to uninstall old nvidia-open-driver-G06-signed-cuda-kmp-default and kernel-firmware-nvidia-gspx-G06-cuda packages. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230552] VUL-0: CVE-2024-45770: pcp: `pmpost` symlink attack allows escalating `pcp` to `root` user
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1230552 https://bugzilla.suse.com/show_bug.cgi?id=1230552#c18 --- Comment #18 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2025:0011-1: An update that solves three vulnerabilities and has two security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2025/suse-su-20250011-1 Category: security (moderate) Bug References: 1217826, 1222815, 1230551, 1230552, 1231345 CVE References: CVE-2023-6917, CVE-2024-45769, CVE-2024-45770 Maintenance Incident: [SUSE:Maintenance:36517](https://smelt.suse.de/incident/36517/) Sources used: openSUSE Leap 15.4 (src): pcp-6.2.0-150400.5.9.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230551] VUL-0: CVE-2024-45769: pcp: `pmcd` heap corruption through metric pmstore operations
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1230551 https://bugzilla.suse.com/show_bug.cgi?id=1230551#c22 --- Comment #22 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2025:0011-1: An update that solves three vulnerabilities and has two security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2025/suse-su-20250011-1 Category: security (moderate) Bug References: 1217826, 1222815, 1230551, 1230552, 1231345 CVE References: CVE-2023-6917, CVE-2024-45769, CVE-2024-45770 Maintenance Incident: [SUSE:Maintenance:36517](https://smelt.suse.de/incident/36517/) Sources used: openSUSE Leap 15.4 (src): pcp-6.2.0-150400.5.9.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222815] New: Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222815 Bug ID: 1222815 Summary: Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- just installing pcp and pmlogger leads to: # systemctl start pmlogger Failed to start pmlogger.service: Unit pmlogger_daily.timer not found. this unit is currently in pcp-zeroconf. however pmlogger.service is in pcp (main package). if zeroconf is supposed to be optional, then the pmlogger_daily.timer dependency is supposed to be made optional. otherwise the timer needs to be moved into the main package (like it appears to be upstream) -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1234995] New: libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 Bug ID: 1234995 Summary: libvirt: libvirt: virtimetest failing with the change to year 2025 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The `virtimetest` in libvirt started failing with the transition to the year 2025. This failure is blocking Tumbleweed development. I've created a Submit Request with a temporary fix: https://build.opensuse.org/request/show/1234542. I plan to accept it today in Factory to unblock development. However, this issue needs a more permanent solution, hence this bug report. -- You are receiving this mail because: You are on the CC list for the bug.

1 1