April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1223095] New: Repository "Validation Check Failed"
by bugzilla_noreply＠suse.com 27 Apr '24

27 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223095 Bug ID: 1223095 Summary: Repository "Validation Check Failed" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: garian.nobinger(a)gmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Going from Yast2 to Software Manager, in the last couple months I've started getting a popup saying: Validation Check Failed (in bold) File repomd.xml from repository update-sle (15.5) http://cdn.opensuse.org/update/leap/15.5/sle is signed with the following GnuPG key, but the integrity check failed: ID: 70AF9E8139DB7C82 Fingerprint: FEAB 5025 39D8 46DB 2C09 61CA 70AF 9E81 39DB 7C82 Name: SuSE Package Signing Key <build(a)suse.de> Created: 09/21/2020 Expires: 09/20/2024 The file has been changed, either by accident or by an attacker, since the repository creator signed it. Using it is a big risk for the integrity and security of your system. Use it anyway? Y/N Ive gone to https://en.opensuse.org/openSUSE:Signing_Keys and looked for a matching key, but don't see one. So I hesitate to blindly trust it. What's the deal with repo signatures suddenly breaking? I've ignored this for a few months thinking it was probably a temporary mistake that would get resolved, but so far hasn't gone away. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223441] could not connect to packman site
by bugzilla_noreply＠suse.com 27 Apr '24

27 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223441 https://bugzilla.suse.com/show_bug.cgi?id=1223441#c1 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID CC| |dimstar(a)opensuse.org Status|NEW |RESOLVED --- Comment #1 from Dominique Leuenberger <dimstar(a)opensuse.org> --- Random external Websites not being reachable are not bugs in Tumbleweed Besides that, the site seems to be reachable again -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223441] New: could not connect to packman site
by bugzilla_noreply＠suse.com 27 Apr '24

27 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223441 Bug ID: 1223441 Summary: could not connect to packman site Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: epistemepromeneur(a)free.fr QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- When updating with discover i get this error : <html>Dépôt indisponible:<br/><br/>Erreur de téléchargement (curl) pour 'http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/Essentials/x86_64/libavutil56_70-4.4.4-1699.16.pm.1.x86_64.rpm' : Code d'erreur : Connection failed Message d'erreur : Failed to connect to ftp.gwdg.de port 80 after 52 ms: Couldn't connect to server </html> -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222756] New: Bluetooth: auto-connected devices are not shown as connected
by bugzilla_noreply＠suse.com 27 Apr '24

27 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222756 Bug ID: 1222756 Summary: Bluetooth: auto-connected devices are not shown as connected 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: i(a)guoyunhe.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When a paired Bluetooth headset was auto-connected, the device works but system tray and bluetoothctl are not showing it as connected: bluetoothctl info 64:68:76:1C:E3:67 Device 64:68:76:1C:E3:67 (public) Name: 漫步者•花再 Free Pro Alias: 漫步者•花再 Free Pro Class: 0x00240404 (2360324) Icon: audio-headset Paired: yes Bonded: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: SDP (00000001-0000-1000-8000-00805f9b34fb) UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Cont.. (0000110f-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) UUID: Generic Audio (00001203-0000-1000-8000-00805f9b34fb) UUID: Vendor specific (66666666-6666-6666-6666-666666666666) UUID: Vendor specific (edf00000-edfe-dfed-fedf-edfedfedfedf) Battery Percentage: 0x32 (50) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1192844] vlc dvd:// crashes in Mesa init_source
by bugzilla_noreply＠suse.com 27 Apr '24

27 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1192844 https://bugzilla.suse.com/show_bug.cgi?id=1192844#c19 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |NORESPONSE --- Comment #19 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. So this can't be tested easily any longer. Feel free to reopen once you can and the issue remains. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223215] New: VUL-0: CVE-2023-49501: ffmpeg: buffer overflow via the config_eq_output function in libavfilter/asrc_afirsrc.c
by bugzilla_noreply＠suse.com 27 Apr '24

27 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223215 Bug ID: 1223215 Summary: VUL-0: CVE-2023-49501: ffmpeg: buffer overflow via the config_eq_output function in libavfilter/asrc_afirsrc.c Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/402757/ OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: jengelh(a)inai.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Buffer Overflow vulnerability in Ffmpeg v.n6.1-3-g466799d4f5 allows a local attacker to execute arbitrary code via the config_eq_output function in the libavfilter/asrc_afirsrc.c:495:30 component. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-49501 https://www.cve.org/CVERecord?id=CVE-2023-49501 https://github.com/FFmpeg/FFmpeg https://trac.ffmpeg.org/ticket/10686 https://trac.ffmpeg.org/ticket/10686#no1 https://bugzilla.redhat.com/show_bug.cgi?id=2276114 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1222730] New: VUL-0: CVE-2023-49528: ffmpeg-6: buffer overflow vulnerability in the dialogue enhance audio filter
by bugzilla_noreply＠suse.com 27 Apr '24

27 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222730 Bug ID: 1222730 Summary: VUL-0: CVE-2023-49528: ffmpeg-6: buffer overflow vulnerability in the dialogue enhance audio filter Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/401578/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: jengelh(a)inai.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Buffer Overflow vulnerability in FFmpeg version n6.1-3-g466799d4f5, allows a local attacker to execute arbitrary code and cause a denial of service (DoS) via the af_dialoguenhance.c:261:5 in the de_stereo component. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-49528 https://www.cve.org/CVERecord?id=CVE-2023-49528 https://trac.ffmpeg.org/ticket/10691 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1223210] KDE6: Can not record screen on Wayland - Spectacle error
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223210 https://bugzilla.suse.com/show_bug.cgi?id=1223210#c3 ell1e <el(a)horse64.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |el(a)horse64.org --- Comment #3 from ell1e <el(a)horse64.org> --- I have possibly the same problem, Plasma 5 screen recording worked fine and Plasma 6 it's broken with both Spectacle and OBS: $ spectacle libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 kpipewire_record_logging: VAAPI: Display initialized kpipewire_record_logging: VAAPI: API version 1 . 20 kpipewire_record_logging: VAAPI: Mesa Gallium driver 24.0.3 for AMD Radeon Graphics (radeonsi, renoir, LLVM 18.1.2, DRM 3.57, 6.8.5-1-default) in use for device "/dev/dri/renderD128" kpipewire_record_logging: DRM device not found libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 kpipewire_record_logging: VAAPI: Display initialized kpipewire_record_logging: VAAPI: API version 1 . 20 kpipewire_record_logging: VAAPI: Mesa Gallium driver 24.0.3 for AMD Radeon Graphics (radeonsi, renoir, LLVM 18.1.2, DRM 3.57, 6.8.5-1-default) in use for device "/dev/dri/renderD128" kpipewire_record_logging: DRM device not found qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml" qt.multimedia.ffmpeg.libsymbolsresolver: Couldn't load VAAPI library libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 kpipewire_record_logging: VAAPI: Display initialized kpipewire_record_logging: VAAPI: API version 1 . 20 kpipewire_record_logging: VAAPI: Mesa Gallium driver 24.0.3 for AMD Radeon Graphics (radeonsi, renoir, LLVM 18.1.2, DRM 3.57, 6.8.5-1-default) in use for device "/dev/dri/renderD128" kpipewire_record_logging: DRM device not found libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 kpipewire_record_logging: VAAPI: Display initialized kpipewire_record_logging: VAAPI: API version 1 . 20 kpipewire_record_logging: VAAPI: Mesa Gallium driver 24.0.3 for AMD Radeon Graphics (radeonsi, renoir, LLVM 18.1.2, DRM 3.57, 6.8.5-1-default) in use for device "/dev/dri/renderD128" kpipewire_record_logging: DRM device not found -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222305] New: cannot build anything for (32-bit) arm tumbleweed
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222305 Bug ID: 1222305 Summary: cannot build anything for (32-bit) arm tumbleweed Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: armv7 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Building against openSUSE:Factory/snapshot architecture armv7l or armv6l results in the following error message in log: ``` [ 6s] setting hostarch to armv7l [ 6s] Detected virtio-serial support [ 10s] booting kvm... [ 10s] ### VM INTERACTION START ### [ 10s] Using virtio-serial support [ 10s] linux64 /usr/bin/qemu-system-aarch64 -nodefaults -no-reboot -nographic -vga none -cpu host,aarch64=off -enable-kvm -M virt,accel=kvm,usb=off,gic-version=host -sandbox on -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-device,rng=rng0 -object iothread,id=io0 -runas qemu -net none -kernel /var/cache/obs/worker/root_34/.mount/boot/kernel -initrd /var/cache/obs/worker/root_34/.mount/boot/initrd -append root=/dev/disk/by-id/virtio-0 rootfstype=ext4 rootflags=noatime elevator=noop nmi_watchdog=0 rw ia32_emulation=1 oops=panic panic=1 quiet console=hvc0 init=/.build/build -m 10240 -drive file=/var/cache/obs/worker/root_34/root,format=raw,if=none,id=disk,cache=unsafe,aio=io_uring -device virtio-blk-device,iothread=io0,drive=disk,serial=0 -drive file=/var/cache/obs/worker/root_34/swap,format=raw,if=none,id=swap,cache=unsafe,aio=io_uring -device virtio-blk-device,iothread=io0,drive=swap,serial=1 -device virtio-serial,max_ports=2 -device virtconsole,chardev=virtiocon0 -chardev stdio,id=virtiocon0 -chardev socket,id=monitor,server=on,wait=off,path=/var/cache/obs/worker/root_34/root.qemu/monitor -mon chardev=monitor,mode=readline -smp 4 [ 10s] qemu-system-aarch64: can't apply global host-arm-cpu.aarch64=off: 'aarch64' feature cannot be disabled unless KVM is enabled and 32-bit EL1 is supported [ 10s] ### VM INTERACTION END ### [ 10s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [ 10s] or the build host has a kernel or hardware problem... gave up after 10 failed build attempts... ``` aarch64 works fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1222305] cannot build anything for (32-bit) arm tumbleweed
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222305 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Major -- You are receiving this mail because: You are on the CC list for the bug.

1 0