July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220501] New: Kernel panics on EEVDF
by bugzilla_noreply＠suse.com 20 Sep '24

20 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220501 Bug ID: 1220501 Summary: Kernel panics on EEVDF 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: l4rryc0n5014(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873070 --> https://bugzilla.suse.com/attachment.cgi?id=873070&action=edit Compressed copy of /var/log/journal, accessed from Windows with WinBTRFS My laptop has been kernel panicking quite frequently as of late. At first I thought it was because of the boot option `pcie_aspm=force acpi_backlight=native` but it wasn't. I dropped into recovery mode to check `journalctl` and I found the recent panics were due to: EEVDF scheduling fail, picking leftmost BUG: kernel NULL pointer dereference, address: 00000000000000a0 I saw a lot of `EEVDF scheduling fail` before the entries cuts off for the next boot session which was me ACPI shutting down the laptop each time it grinds to a halt. Sometimes, I saw two additional entries in the journal: #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page A quick search on the first two entries yielded <https://lkml.org/lkml/2024/2/19/678>. Not sure how to read the thing considering it's Linux kernel stuffs. I also thought it was due to data corruption or something on the `/` and `/home` but `btrfs check --force --check-data-csum` said both were healthy, and I reinstalled openSUSE back Feb 19 after zeroing the two partitions for good measure (due to mishaps that compromised data integrity). The only things that has anything to do with the kernel I installed were VBox, Docker, KVM and QEMU, and the NVIDIA driver with blacklisting `nouveau` using https://en.opensuse.org/SDB:NVIDIA_the_hard_way, the rest was from https://en.opensuse.org/SDB:NVIDIA_drivers for G06 with a bunch more G06 stuff installed. Included is a compressed file or /var/log/journal which should include my laptop model; but for safety measure, I am using an Acer Nitro 5 (AN515-46-R6QR) running AMD Ryzen 7 6800H with an NVIDIA 3060 Mobile, upgraded to 32GB of RAM from stock configuration of 16GB with an additional 2TB drive added to the spare M.2 slot. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1214406] New: [kubeadm1.27] Multiple Issues before `kubeadm init` runs successfully
by bugzilla_noreply＠suse.com 19 Sep '24

19 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1214406 Bug ID: 1214406 Summary: [kubeadm1.27] Multiple Issues before `kubeadm init` runs successfully Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: priyanka.saggu(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- 1. The Kubernetes package on TW seems to require cri-o as runtime dependency, however, it requires containerd. Thus, - cri-o should not be installed as a dependency - containerd had to be installed enabled and started (containerd doesn't have an rccontainerd link) 2. kubelet.service does not start: It complains about the option `--container-runtime` not being known. This option is pulled in from /etc/sysconfig/kubelet. It needs to be deleted from this file. It is not clear who has created this file and which package owns it. The rpm database does not know it. Since it is pulled in by ..../systemd/system/kubelet.service.d/10-kubeadm.conf I suspect it comes from kubernetes1.27-kubeadem but it's hard to tell where it is created - at least not in a post-install script. It would be good if the file was '%ghost' in the %files section of the package it originates from. The same is true for the environment file /var/lib/kubelet/kubeadm-flags.env which is written by `kubeadm init`. 3. 'kubeadm init' checks if the kubelet service is enabled. 4. Moreover, it requires a reboot to start all dependent services and load all required kernel modules: - br_netfilter needs to be loaded - containerd needs to be started This was fine for kubic these packages were originally meant for as this had transactional updates and required a reboot. On a 'regular' system where this is not the case, these modules should probably be loaded and services be started from a 'postinstall' script. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1226598] New: AUDIT-FIND: logiops: unrestricted D-Bus service allows for privilege escalation with user interaction required
by bugzilla_noreply＠suse.com 19 Sep '24

19 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1226598 Bug ID: 1226598 Summary: AUDIT-FIND: logiops: unrestricted D-Bus service allows for privilege escalation with user interaction required Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- logiops [0][1], in its default configuration, allows any unprivileged user to configure its `logid` daemon via an unrestricted D-Bus service, including setting malicious keyboard macros. This could potentially enable privilege escalation with minimal user interaction required. The most basic proof-of-concept assigns a shell command to all buttons for connected peripherals. A more crafty attacker could tailor this operation to specific software used on the system, possibly monitoring the process list and mapping malicious macros at exactly the right moment. [0] https://github.com/PixlOne/logiops [1] https://bugzilla.suse.com/show_bug.cgi?id=1225543#c3 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227647] New: msi crash
by bugzilla_noreply＠suse.com 18 Sep '24

18 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1227647 Bug ID: 1227647 Summary: msi crash Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: PowerPC-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: g.fischer(a)r-a-c.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, I ran into the following with leap 15.6 on a power8 with vios: [ 26.069618] kernel BUG at ../drivers/pci/msi/msi.c:154! [ 26.069627] Oops: Exception in kernel mode, sig: 5 [#1] [ 26.069634] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries [ 26.069642] Modules linked in: bonding tls af_packet rfkill xt_state xt_conntrack iptable_filter xt_MASQUERADE iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp iptable_mangle ext4 crc16 mbcache jbd2 ibmveth(X) crct10dif_vpmsum rtc_generic fuse configfs ip_tables x_tables xfs libcrc32c sr_mod cdrom xhci_pci xhci_pci_renesas ibmvscsi(X) scsi_transport_srp sd_mod xhci_hcd scsi_dh_emc scsi_dh_rdac scsi_dh_alua t10_pi crc64_rocksoft_generic crc64_rocksoft sg crc64 usbcore scsi_mod vmx_crypto gf128mul crc32c_vpmsum usb_common [ 26.069732] Supported: Yes, External [ 26.069738] CPU: 3 PID: 772 Comm: irqbalance Not tainted 6.4.0-150600.23.7-default #1 SLE15-SP6 add0c91aba136d1acbe3fcdb4fead2567d86023a [ 26.069750] Hardware name: IBM,8284-22A POWER8E (raw) 0x4b0201 0xf000004 of:IBM,FW860.51 (SV860_165) hv:phyp pSeries [ 26.069757] NIP: c000000000996ae8 LR: c00000000010a478 CTR: c00000000010a450 [ 26.069765] REGS: c000000036a2b490 TRAP: 0700 Not tainted (6.4.0-150600.23.7-default) [ 26.069773] MSR: 8000000000021033 <SF,ME,IR,DR,RI,LE> CR: 88004828 XER: 20000000 [ 26.069790] CFAR: c00000000010a474 IRQMASK: 1 GPR00: c00000000010a478 c000000036a2b730 c000000001987d00 c000000028484bc0 GPR04: c000000036a2b7e0 0000000000000000 0000000020000000 c0080000204a0d90 GPR08: c000000002a01888 0000000000000001 c000000003825e40 0000000000001003 GPR12: c00000000010a450 c00000001ecacb00 0000000000000000 0000000000000000 GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR24: c0000000029a61e8 c0000000029a68d0 c00000002f13b000 c00000000292bf88 GPR28: c000000036a2b928 c000000036a2b7e0 c000000028484bc0 c000000028e520d0 [ 26.069880] NIP [c000000000996ae8] __pci_read_msi_msg+0x48/0x290 [ 26.069892] LR [c00000000010a478] pseries_msi_compose_msg+0x28/0x40 [ 26.069902] Call Trace: [ 26.069907] [c000000036a2b780] [c00000002f13b118] 0xc00000002f13b118 [ 26.069917] [c000000036a2b7a0] [c000000000219d04] irq_chip_compose_msi_msg+0x54/0x80 [ 26.069928] [c000000036a2b7c0] [c000000000221584] msi_domain_set_affinity+0x84/0x100 [ 26.069940] [c000000036a2b810] [c00000000021324c] irq_do_set_affinity+0x1bc/0x290 [ 26.069951] [c000000036a2b870] [c0000000002134a4] irq_set_affinity_locked+0x184/0x250 [ 26.069962] [c000000036a2b8b0] [c0000000002135dc] __irq_set_affinity+0x6c/0xc0 [ 26.069973] [c000000036a2b900] [c00000000021f33c] write_irq_affinity.isra.9+0x16c/0x1b0 [ 26.069984] [c000000036a2ba60] [c00000000067ef88] proc_reg_write+0x108/0x1b0 [ 26.069996] [c000000036a2ba90] [c0000000005a4c10] vfs_write+0x100/0x440 [ 26.070008] [c000000036a2bb50] [c0000000005a517c] ksys_write+0xdc/0x130 [ 26.070019] [c000000036a2bba0] [c000000000034bb8] system_call_exception+0x158/0x320 [ 26.070030] [c000000036a2be50] [c00000000000d6a0] system_call_common+0x160/0x2c4 [ 26.070041] --- interrupt: c00 at 0x7fffaca227e0 [ 26.070048] NIP: 00007fffaca227e0 LR: 00007fffaca227b8 CTR: 0000000000000000 [ 26.070054] REGS: c000000036a2be80 TRAP: 0c00 Not tainted (6.4.0-150600.23.7-default) [ 26.070062] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 28004422 XER: 00000000 [ 26.070085] IRQMASK: 0 GPR00: 0000000000000004 00007ffff9c291e0 00007fffacb36d00 0000000000000006 GPR04: 0000010008000500 0000000000000008 0000000000000030 00007fffacf4c400 GPR08: 00007fffacf44d48 0000000000000000 0000000000000000 0000000000000000 GPR12: 0000000000000000 00007fffacf4c400 0000000000000000 0000000000000000 GPR16: 0000000000000000 0000000000000000 0000000000000000 0000010008009010 GPR20: 00007ffff9c2ac08 00007ffff9c2ac10 0000004100000000 0000000000000000 GPR24: 0000000000000000 0000000000000019 000000011d8bec58 0000010008000500 GPR28: 0000000000000008 0000010008000500 0000000000000000 0000000000000006 [ 26.070171] NIP [00007fffaca227e0] 0x7fffaca227e0 [ 26.070177] LR [00007fffaca227b8] 0x7fffaca227b8 [ 26.070183] --- interrupt: c00 [ 26.070188] Code: fbe1fff8 7c7e1b78 f821ffb1 7c9d2378 ebe30008 e92d0c78 f9210028 39200000 813fffd0 7d290034 5529d97e 69290001 <0b090000> a123004c 712a0001 4182016c [ 26.070219] ---[ end trace 0000000000000000 ]--- If you need any more info, just let me know. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1226971] New: VUL-0: CVE-2024-38355: nodejs-underscore: socket.io: unhandled 'error' event
by bugzilla_noreply＠suse.com 17 Sep '24

17 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1226971 Bug ID: 1226971 Summary: VUL-0: CVE-2024-38355: nodejs-underscore: socket.io: unhandled 'error' event Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/411493/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: hillwoodroc(a)gmail.com Reporter: camila.matos(a)suse.com QA Contact: security-team(a)suse.de CC: amajer(a)suse.com, camila.matos(a)suse.com, security-team(a)suse.de, smash_bz(a)suse.de Blocks: 1226965 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1226965 +++ Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit `15af22fc22` which has been included in `socket.io(a)4.6.2` (released in May 2023). The fix was backported in the 2.x branch as well with commit `d30630ba10`. Users are advised to upgrade. Users unable to upgrade may attach a listener for the "error" event to catch these errors. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-38355 https://www.cve.org/CVERecord?id=CVE-2024-38355 https://github.com/socketio/socket.io/commit/15af22fc22bc6030fcead322c106f0… https://github.com/socketio/socket.io/commit/d30630ba10562bf987f4d2b42440fc… https://github.com/socketio/socket.io/security/advisories/GHSA-25hc-qcg6-38… https://bugzilla.redhat.com/show_bug.cgi?id=2293192 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225697] New: Problem video driver i915
by bugzilla_noreply＠suse.com 16 Sep '24

16 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225697 Bug ID: 1225697 Summary: Problem video driver i915 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: sidewinderx(a)libero.it QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: I have a problem that is not clear to me I guess with the Intel G33 i915 video drivers. Upgrading from 15.4 to 15.5 opensuse leap I have freezes while navigating through the system menus and mainly I can’t launch graphics programs for pcb creation which didn’t happen in previous versions. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1219528] New: go 1.22rc2 breaks mockery
by bugzilla_noreply＠suse.com 16 Sep '24

16 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1219528 Bug ID: 1219528 Summary: go 1.22rc2 breaks mockery Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- package: https://build.opensuse.org/package/show/home:darix:restic/mockery upstream issue: https://github.com/vektra/mockery/issues/752 stack trace in upstream issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221701] New: GCC 14: libquicktime package fails
by bugzilla_noreply＠suse.com 15 Sep '24

15 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1221701 Bug ID: 1221701 Summary: GCC 14: libquicktime package fails 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: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: danilo.spinella(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building libquicktime with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: error: File not found: /home/abuild/rpmbuild/BUILDROOT/libquicktime-1.2.4+git20180804.fff99cd-5.5.x86_64/usr/lib64/libquicktime/lqt_lame.so ./libquicktime-1.2.4+git20180804.fff99cd/config.log: conftest.c:59:5: error: return type defaults to 'int' [-Wimplicit-int] ./libquicktime-1.2.4+git20180804.fff99cd/config.log: 59 | main() ./libquicktime-1.2.4+git20180804.fff99cd/config.log: | ^~~~ Builds with automatically generated: Index: libquicktime-1.2.4+git20180804.fff99cd/configure.ac =================================================================== --- libquicktime-1.2.4+git20180804.fff99cd.orig/configure.ac +++ libquicktime-1.2.4+git20180804.fff99cd/configure.ac @@ -282,6 +282,7 @@ have_lame="false" AC_TRY_RUN([ #include <lame/lame.h> #include <stdio.h> +int main() { int version_major; See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1225797] New: Kaffeine cannot scan for channels any more and blocks long time when opened since Kernel update.
by bugzilla_noreply＠suse.com 15 Sep '24

15 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225797 Bug ID: 1225797 Summary: Kaffeine cannot scan for channels any more and blocks long time when opened since Kernel update. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Need some help to debug this. I had to reinstall the system, all works but the dvb-t refuses in kaffeine to sync the channels. First I had doubts about the firmware, but then in dmesg you see it loads well and the card is recognized. [ 906.573480] [T17018] m88ds3103 13-0069: found a 'Montage Technology M88RS6000' in cold state [ 906.574387] [T17018] m88ds3103 13-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw' [ 907.610003] [T17200] cx23885 0000:03:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM [ 925.478898] [T17018] m88ds3103 13-0069: firmware did not run [ 925.640755] [T17830] si2168 13-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw' [ 925.640761] [T17830] si2168 13-0064: firmware download failed -22 [ 925.646039] [T17830] si2157 14-0060: found a 'Silicon Labs Si2157-A30 ROM 0x50' [ 925.646137] [T17830] si2157 14-0060: Using ROM firmware. [ 925.694758] [T17830] si2157 14-0060: firmware version: 3.0.5 So the firmware is OK. I have the codecs from Packman installed, even MESA. So that should work now, as it always had. I get the following output if I try: first remark, about a 30 seconds delay were Kaffeine does not pop up. Then the logging goes on. The delay is cause by: 02-06-24 16:55:59.484 [Warning ] kf.service.services: KServiceTypeTrader: serviceType "ThumbCreator" not found 02-06-24 16:55:59.484 [Warning ] kf.service.services: KServiceTypeTrader: serviceType "ThumbCreator" not found 02-06-24 16:55:59.769 [Warning ] kf.service.services: KServiceTypeTrader: serviceType "ThumbCreator" not found 02-06-24 16:55:59.770 [Warning ] kf.service.services: KServiceTypeTrader: serviceType "ThumbCreator" not found When searching channels I get nothing, only 02-06-24 16:58:42.941 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile 02-06-24 16:58:45.541 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile 02-06-24 16:58:48.141 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile 02-06-24 16:58:50.741 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile 02-06-24 16:58:53.341 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile 02-06-24 16:58:55.941 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile 02-06-24 16:58:58.541 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile Translation would be: "resource temporarily not available". I am puzzled, not really understanding what the program complains about. Is the card broken, the signal not available? What is FE_SET_TONE? As this happened after the radeon issues on the 6.8 kernels and now with 6.9.1-1-default I have the multimonitor issue resolved but the TV-Sat card is out of service, I would suppose that is directly related with the update. Is there a way to e.g. try out the functionality by rolling back in a repo with older kernels that were working? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1228164] New: [Build 20240719] openQA test fails in vlc - incomplete video image
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1228164 Bug ID: 1228164 Summary: [Build 20240719] openQA test fails in vlc - incomplete video image Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4351867/modules/vlc/ steps/26 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: nada-infinita(a)posteo.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes Created attachment 876174 --> https://bugzilla.suse.com/attachment.cgi?id=876174&action=edit Image displaying vlc display incomplete. ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-gnome@Laptop_64 fails in [vlc](https://openqa.opensuse.org/tests/4351867/modules/vlc/steps/26) ## Test suite description Revert schedule to working settings - dleuenberger, 20211117 ## Reproducible Fails since (at least) Build [20240719](https://openqa.opensuse.org/tests/4351053) ## Expected result Last good: [20240718](https://openqa.opensuse.org/tests/4350448) (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 9