October 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1189946] New: [trackerbug] Ancient patch cleanup
by bugzilla_noreply＠suse.com 09 Dec '22

09 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1189946 Bug ID: 1189946 Summary: [trackerbug] Ancient patch cleanup 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: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jeffm(a)suse.com, mkubecek(a)suse.com Found By: --- Blocker: --- This is the tracker bug for cleaning up old patches in the master branch. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 1203519] New: floating shutdown problem on pinebook pro
by bugzilla_noreply＠suse.com 08 Dec '22

08 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203519 Bug ID: 1203519 Summary: floating shutdown problem on pinebook pro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: werwolf131313(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- intermittent shutdown problem on pinebook pro, the problem is expressed as follows: after the laptop is turned off (it doesn��t matter by the button in the menu or via sudo systemctl shutdown), a regular shutdown occurs, the service stop log is visible and everything is as it should be, BUT, after the screen goes blank, the board remains on. this can be checked if you try to turn it on, pressing the button does not work. only a long press of the power key (to completely turn off) for 7-10 seconds, and a second press (to turn it on) allows you to turn on the pinebook. the problem is not observed in other distributions (tried on manjaro, armbian, gentoo) and is specific to opensuse. in my case, the installation differs from the typical one in that the operating system is installed on a microsd card (due to the death of emmc), can this affect? but in other distributions, even installed on the same microsd card, the problem is not observed. I'm using opensuse tumbleweed installed from the openSUSE-Tumbleweed-ARM-KDE-pinebookpro.aarch64.raw.xz image. at the moment there are all the latest updates, but the problem has existed for quite a long time. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1193599] New: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193599 Bug ID: 1193599 Summary: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following errors appear at boot broken atomic modeset userspace detected, disabling atomic [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Full log https://paste.opensuse.org/83436185 Hardware Dell Precision 7530 CPU: Intel Xeon E-2186M GPU: Intel P630 / Nvidia Quadro P3200 -- You are receiving this mail because: You are the assignee for the bug.

1 33

[Bug 1191933] New: Kernel can not update on Secure boot envirnment
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191933 Bug ID: 1191933 Summary: Kernel can not update on Secure boot envirnment 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: kokeko(a)mac.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Current 20211012, update to 20211016 or 20211019. Kernel-default update failed by fallowing error. subprocess error, secure boot enabled. Is it something change? -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1200781] New: xhci stop working. Works briefly after reboot, or remove and load xhci_pci & xhci_hcd.
by bugzilla_noreply＠suse.com 30 Nov '22

30 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200781 Bug ID: 1200781 Summary: xhci stop working. Works briefly after reboot, or remove and load xhci_pci & xhci_hcd. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: publio.escipion.el.africano(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSuSE Leap 15.4 x86_64, kernel 4.14.21-150400.22-default, in a Lenovo IdeaPad 3 15ADA05: https://psref.lenovo.com/syspool/Sys/PDF/IdeaPad/IdeaPad_3_15ADA05/IdeaPad_… An external mouse stops working after a brief period of time, after login into KDE, or after removing and loading xhci_pci & xhci_hcd. System complaints of: �xhci_hcd 0000:02:00.3 WARNIGN: Host System Error� and: �usb 2-3: device not accepting address 2, error -108� I've tried two bluetooth mice, and a standard cord mouse. The same result. It seems that it's the USB controllers are the only components affected, so far. Mousepad works properly, but I'm not use to it. I have to constantly remove and load xhci_pci & xhci_hcd, as root. rmmod xhci_pci rmmod xhci_hcd modprobe xhci_pci modprobe xhci_hcd Mouse works after that for a short time. Nota bene: Devices work properly under openSuSE Leap 15.2 x86_64, kernel 5.3.18-lp152.106-default (old HP Pavillion). This bug resembles https://bugzilla.opensuse.org/show_bug.cgi?id=1193652 -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1204063] New: Kernel 5.19.8 appears to be missing lpuart earlycon and console
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204063 Bug ID: 1204063 Summary: Kernel 5.19.8 appears to be missing lpuart earlycon and console Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: afaerber(a)suse.com Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ddavis(a)suse.com, dmueller(a)suse.com, guillaume.gardet(a)arm.com, kernel-bugs(a)opensuse.org, mbrugger(a)suse.com, mkubecek(a)suse.com Found By: --- Blocker: --- Despite kernel command line "console=ttyLP0,115200 earlycon=lpuart32,0x5a060000,115200" on an NXP i.MX 8QM based Variscite VAR-SOM-MX8 module based device, I am not seeing any kernel serial output other than EFI stub: Loading Linux 5.19.8-1-default ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... or without EFI: Starting kernel ... Having ruled out a red herring of EFI stub: ERROR: Failed to install memreserve config table! as caused by old U-Boot 2018.03 having a hardcoded config table array size of 2, the lack of output most likely is because of: CONFIG_SERIAL_FSL_LPUART=m git-blame points to a SLE15-SP2 sync: https://github.com/openSUSE/kernel-source/commit/769684a2fa08#diff-a9e1c242… Serial Kconfig options need to be built-in (=y) in order to enable their sub-option *_CONSOLE=y, needed for both console= and earlycon= kernel options. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1203748] New: Laptop very slow in battery mode (Lenovo Thinkpad T470)
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1203748 Bug ID: 1203748 Summary: Laptop very slow in battery mode (Lenovo Thinkpad T470) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sndirsch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- For some reason my laptop gets very slow in battery only mode. I notice this when watching videos. It makes it rather unusable when not connecting it to power. It looks like it goes into some deep powersave mode. I would like to avoid this even if this would half the running time in battery mode. Which information do you need? -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 1202138] New: PowerPC machine crashes frequently after upgrading to Leap 15.4
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202138 Bug ID: 1202138 Summary: PowerPC machine crashes frequently after upgrading to Leap 15.4 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: marius.kittler(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading a PowerPC machine (the openQA worker qa-power8-4-kvm.qa.suse.de) from Leap 15.3 to Leap 15.4 that machine crashes frequently. It usually does not stay on for more than a few hours. Downgrading the machine (by rolling back to the last BTRFS snapshot with Leap 15.3) allows the machine to run stable again. Note that there's actually a second machine (the openQA worker qa-power8-5-kvm.qa.suse.de) that we managed to operate without crashes on Leap 15.4. Both machines seems very similar to me so I'm not sure whether one is crashing and the other one not. Note that in the first place both machines did not boot on Leap 15.4. It seemed to be stuck at some point and the kernel logged messages like ``` [ 197.877239][ C62] watchdog: BUG: soft lockup - CPU#62 stuck for 25s! [swapper/62:0]` quite frequently ``` quite frequently. So I added the kernel parameter `nmi_watchdog=0`. With this parameter both machines could boot on Leap 15.4 (but as mentioned only qa-power8-5 runs stable without crashing). So the kernel command line used is: ``` root=UUID=89ca2dff-86af-478b-8d4c-2a45ca689fd5 nospec kvm.nested=1 kvm_intel.nested=1 kvm_amd.nested=1 kvm-arm.nested=1 crashkernel=210M nmi_watchdog=0 ``` Not sure what other details could be relevant. Unfortunately the journal does not have any interesting message right before the crash. Via SOL I could once see a kernel panic being logged: ``` QA-Power8-4-kvm login: [ 365.807470][ T3923] EXT4-fs error (device sdb1) in ext4_free_inode:362: Corrupt filesystem [ 438.050890][ T94] Kernel panic - not syncing: corrupted stack end detected inside scheduler [ 438.051046][ T94] CPU: 16 PID: 94 Comm: ksof ``` (The filesystem error is likely just a symptom of the crashes.) Any advice what I could try? Maybe another kernel parameter? Maybe booting Leap 15.4 but with the kernel version from 15.3 (not sure how I'd do that, though - so any advice would be welcome if that idea sounds helpful)? By the way, that's `/proc/cpuinfo` on the problematic machine: ``` root=UUID=eebe647f-e867-416e-a0fa-7a6732bfcf9d nospec kvm.nested=1 kvm_intel.nested=1 kvm_amd.nested=1 kvm-arm.nested=1 crashkernel=210M martchus@QA-Power8-4-kvm:~> cat /proc/cpuinfo processor : 0 cpu : POWER8, altivec supported clock : 3857.000000MHz revision : 2.0 (pvr 004d 0200) [�� repeated 7 more times with processor 8, 16, 24, 32, 40, 48 and 56] timebase : 512000000 platform : PowerNV model : 8348-21C machine : PowerNV 8348-21C firmware : OPAL MMU : Hash ``` On the stable machine it looks very similar but it is actually a model with more processors: ``` processor : 0 cpu : POWER8 (raw), altivec supported clock : 3857.000000MHz revision : 2.0 (pvr 004d 0200) [�� repeated 13 more times with processor 8, 16, 24, ��] timebase : 512000000 platform : PowerNV model : 8335-GCA machine : PowerNV 8335-GCA firmware : OPAL MMU : Hash ``` That's the relevant ticket on the openQA infrastructure tracker (for additional context): https://progress.opensuse.org/issues/114565 -- You are receiving this mail because: You are the assignee for the bug.

1 32

[Bug 1204382] New: kernel-obs-build 5.3 from SLE 15 SP3 is not loading in qemu anymore
by bugzilla_noreply＠suse.com 17 Nov '22

17 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204382 Bug ID: 1204382 Summary: kernel-obs-build 5.3 from SLE 15 SP3 is not loading in qemu anymore Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: adrian.schroeter(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We noticed that the kernel-obs-build is not loading in KVM for armv7l anymore. This was noticed in openSUSE:Step:15.3 project, but we used this kernel also so far as default kernel for any distributions which do not bring their own kernel. Switching to SP4 has solved the issues, but SP3 kernel used to work also. It might be caused by switching to SP4 as host OS (qemu 5.3 to 6.2), not verified yet. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 1204705] New: KDE Plasma fails to start with Kernel 6.0.3
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204705 Bug ID: 1204705 Summary: KDE Plasma fails to start with Kernel 6.0.3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: postix(a)posteo.eu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since updating from kernel 6.0.2 to 6.0.3 on openSUSE TW, KDE Plasma 5.26.1 running X11 or Wayland fails to start, after logging in from SDDM: * The cursor works, but no panel shows up, the desktop starts to freeze, i.e. turns gray after a while * Pressing CTRL+ALT+DEL opens the power-management overlay, where logging out works * Shutting down the system does not work after having logged in once, but takes infinitely long and requires a forced shut down Going back to kernel 6.0.2 fixes the issue. An interesting part of the journalctl is likely the following: ``` 09:56:43 kernel: BUG: kernel NULL pointer dereference, address: 00000000000001c8 09:56:43 kernel: #PF: supervisor write access in kernel mode 09:56:43 kernel: #PF: error_code(0x0002) - not-present page 09:56:43 kernel: PGD 0 P4D 0 09:56:43 kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI 09:56:43 kernel: CPU: 16 PID: 1419 Comm: rasdaemon Tainted: G O 6.0.3-1-default #1 openSUSE Tumbleweed 50a6ebc5cb1873d6b9c639843cdd1ed0089a1281 09:56:43 kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-E GAMING, BIOS 4204 02/24/2022 09:56:43 kernel: RIP: 0010:ring_buffer_wake_waiters+0x1c/0xa0 09:56:43 kernel: Code: 48 39 d0 73 ed 0f 0b eb e9 0f 1f 44 00 00 55 48 89 fd 53 48 63 de 83 fb ff 74 36 48 8b 47 40 48 8b 1c d8 48 81 c3 78 01 00 00 <48> 83 43 50 01 31 c9 31 d2 48 8d 7b 20 be 03 00 00 00 e8 cd af f3 09:56:43 kernel: RSP: 0018:ffffaa7a815a7e20 EFLAGS: 00010206 09:56:43 kernel: RAX: ffff908c434db500 RBX: 0000000000000178 RCX: 0000000000000010 09:56:43 kernel: RDX: ffff908c78ed8000 RSI: 0000000000000018 RDI: ffff908c434da900 09:56:43 kernel: RBP: ffff908c434da900 R08: ffff908c50b82e00 R09: ffff908c8206b200 09:56:43 kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff908c8206b200 09:56:43 kernel: R13: ffff908c4387ef20 R14: ffff908c90fddbc0 R15: 0000000000000000 09:56:43 kernel: FS: 00007fd7463a6340(0000) GS:ffff90934ee00000(0000) knlGS:0000000000000000 09:56:43 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 09:56:43 kernel: CR2: 00000000000001c8 CR3: 0000000105574000 CR4: 0000000000750ee0 09:56:43 kernel: PKRU: 55555554 09:56:43 kernel: Call Trace: 09:56:43 kernel: <TASK> 09:56:43 kernel: tracing_buffers_release+0x49/0x90 09:56:43 kernel: __fput+0x91/0x250 09:56:43 kernel: task_work_run+0x5c/0x90 09:56:43 kernel: exit_to_user_mode_prepare+0x1cb/0x1f0 09:56:43 kernel: syscall_exit_to_user_mode+0x17/0x40 09:56:43 kernel: do_syscall_64+0x67/0x80 09:56:43 kernel: ? syscall_exit_to_user_mode+0x17/0x40 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? syscall_exit_to_user_mode+0x17/0x40 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: ? do_syscall_64+0x67/0x80 09:56:43 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd 09:56:43 kernel: RIP: 0033:0x7fd74658e014 09:56:43 kernel: Code: 00 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 90 90 80 3d 8d 09 0f 00 00 74 13 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 44 c3 0f 1f 00 48 83 ec 18 89 7c 24 0c e8 51 09:56:43 kernel: RSP: 002b:00007ffce5e64348 EFLAGS: 00000202 ORIG_RAX: 0000000000000003 09:56:43 kernel: RAX: 0000000000000000 RBX: 00007ffce5e64490 RCX: 00007fd74658e014 09:56:43 kernel: RDX: 0000000000000000 RSI: 00007ffce5e64540 RDI: 000000000000001d 09:56:43 kernel: RBP: 00007ffce5e65a10 R08: 000055939344e6c0 R09: 0000000000000000 09:56:43 kernel: R10: 0000000000000008 R11: 0000000000000202 R12: 0000000000000001 09:56:43 kernel: R13: 00007ffce5e644d8 R14: 000055939344e6c0 R15: 000055939344e6c0 09:56:43 kernel: </TASK> 09:56:43 kernel: Modules linked in: amd64_edac(-) cmac algif_hash algif_skcipher af_alg vboxdrv(O) qrtr bnep dmi_sysfs wacom nls_iso8859_1 nls_cp437 vfat fat intel_rapl_msr iwlmvm intel_rapl_common asus_ec_sensors mac80211 libarc4 snd_hda_codec_realtek snd_hda_codec_generic btusb edac_mce_amd snd_hda_codec_hdmi btrtl snd_usb_audio btbcm snd_hda_intel btintel snd_intel_dspcfg btmtk snd_intel_sdw_acpi kvm_amd snd_hda_codec snd_usbmidi_lib iwlwifi bluetooth snd_rawmidi snd_hda_core joydev snd_seq_device kvm ecdh_generic eeepc_wmi snd_hwdep asus_wmi cfg80211 battery snd_pcm irqbypass ledtrig_audio sparse_keymap r8169 platform_profile snd_timer video pcspkr wmi_bmof efi_pstore mxm_wmi realtek snd igb k10temp i2c_piix4 mdio_devres soundcore libphy rfkill dca tiny_power_button button acpi_cpufreq fuse configfs ip_tables x_tables hid_generic usbhid amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul xhci_pci xhci_pci_renesas drm_ttm_helper ttm xhci_hcd 09:56:43 kernel: iommu_v2 gpu_sched ghash_clmulni_intel drm_buddy aesni_intel drm_display_helper nvme usbcore crypto_simd cryptd cec ccp nvme_core sp5100_tco rc_core wmi btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq v4l2loopback(O) videodev mc sg br_netfilter bridge stp llc dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs 09:56:43 kernel: CR2: 00000000000001c8 09:56:43 kernel: ---[ end trace 0000000000000000 ]--- 09:56:43 kernel: RIP: 0010:ring_buffer_wake_waiters+0x1c/0xa0 09:56:43 kernel: Code: 48 39 d0 73 ed 0f 0b eb e9 0f 1f 44 00 00 55 48 89 fd 53 48 63 de 83 fb ff 74 36 48 8b 47 40 48 8b 1c d8 48 81 c3 78 01 00 00 <48> 83 43 50 01 31 c9 31 d2 48 8d 7b 20 be 03 00 00 00 e8 cd af f3 09:56:43 kernel: RSP: 0018:ffffaa7a815a7e20 EFLAGS: 00010206 09:56:43 kernel: RAX: ffff908c434db500 RBX: 0000000000000178 RCX: 0000000000000010 09:56:43 kernel: RDX: ffff908c78ed8000 RSI: 0000000000000018 RDI: ffff908c434da900 09:56:43 kernel: RBP: ffff908c434da900 R08: ffff908c50b82e00 R09: ffff908c8206b200 09:56:43 kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff908c8206b200 09:56:43 kernel: R13: ffff908c4387ef20 R14: ffff908c90fddbc0 R15: 0000000000000000 09:56:43 kernel: FS: 00007fd7463a6340(0000) GS:ffff90934ee00000(0000) knlGS:0000000000000000 09:56:43 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 09:56:43 kernel: CR2: 00000000000001c8 CR3: 0000000105574000 CR4: 0000000000750ee0 09:56:43 kernel: PKRU: 55555554 ``` SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20221023 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-1-default (64-bit) / 6.0.3-1-default (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are the assignee for the bug.

1 26