Plasmashell crashes frequently

Support KDE Plasma
1

plasmashell crashes with coredump quite frequently, even after i reset all the settings and cleared the cache , it keeps crashing with core dump

Feb 26 18:18:23 the-beast systemd-coredump[585488]: Process 528982 (plasmashell) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Feb 26 18:18:23 the-beast systemd[1]: Started Process Core Dump (PID 585488/UID 0).
Feb 26 18:18:27 the-beast systemd-coredump[585489]: [🡕] Process 528982 (plasmashell) of user 1000 dumped core.
                                                    
                                                    Stack trace of thread 529415:
                                                    #0  0x00007f62b89c093f n/a (libQt6Core.so.6 + 0x1c093f)
                                                    #1  0x00007f62b89c24f3 _ZNK9QMimeData4dataERK7QString (libQt6Core.so.6 + 0x1c24f3)
                                                    #2  0x00007f62b8ee19ff n/a (libKF6GuiAddons.so.6 + 0x359ff)
                                                    #3  0x00007f62b8ed82c6 n/a (libKF6GuiAddons.so.6 + 0x2c2c6)
                                                    #4  0x00007f62ba937ac6 n/a (libffi.so.8 + 0x7ac6)
                                                    #5  0x00007f62ba93476b n/a (libffi.so.8 + 0x476b)
                                                    #6  0x00007f62ba93706e ffi_call (libffi.so.8 + 0x706e)
                                                    #7  0x00007f62bb67f48d n/a (libwayland-client.so.0 + 0x448d)
                                                    #8  0x00007f62bb6802e9 n/a (libwayland-client.so.0 + 0x52e9)
                                                    #9  0x00007f62bb6806f3 wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x56f3)

any possibility of a fix?

2

There’s always a possibility.

You’ll need to provide some more info on your setup for anyone to diagnose this. The output of inxi -zv8 would be a good start, along with journalctl -b --no-pager.

3

ok here is my inxi -zv8

System:
  Kernel: 6.19.2-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.19-x86_64
    root=UUID=b1beb20b-cc4f-48d6-b4dd-8af0c2d1c655 rw quiet apparmor=1
    security=apparmor resume=UUID=3cf867c8-0a8f-4184-8734-723e7fc75c34
    udev.log_priority=3 nordrand
  Desktop: KDE Plasma v: 6.5.5 tk: Qt v: N/A info: frameworks v: 6.23.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MEG X570 ACE (MS-7C35) v: 1.0
    serial: <superuser required> uuid: <superuser required> Firmware: UEFI
    vendor: American Megatrends LLC. v: 1.H0 date: 03/21/2022
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 80 GiB available: 78.46 GiB used: 9.73 GiB (12.4%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 32 GiB speed: 2667 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: N/A
    part-no: N/A serial: <filter>
  Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 2667 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: G.Skill
    part-no: F4-2666C19-8GNT serial: N/A
  Device-3: Channel-B DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 32 GiB speed: 2667 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: TeamGroup
    part-no: TIMETEC-UD4-3200 serial: N/A
  Device-4: Channel-B DIMM 1 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 2667 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: G.Skill
    part-no: F4-2666C19-8GNT serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 7 3800X bits: 64 type: MT MCP arch: Zen 2 gen: 2
    level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
    family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701034
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
    desc: 8x512 KiB L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 1758 min/max: 577/4560 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 1758 2: 1758 3: 1758
    4: 1758 5: 1758 6: 1758 7: 1758 8: 1758 9: 1758 10: 1758 11: 1758 12: 1758
    13: 1758 14: 1758 15: 1758 16: 1758 bogomips: 124798
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid
    f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs
    irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
    msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae
    pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
    pfthreshold pge pni popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a
    rdtscp rep_good sep sev sev_es sha_ni skinit smap smca smep ssbd sse sse2
    sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext
    tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme
    vmmcall wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt
    xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP:
    always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
    470/480/570/570X/580/580X/590] vendor: Micro-Star MSI driver: amdgpu
    v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20
    pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,
    DVI-D-1, HDMI-A-1, HDMI-A-2 bus-ID: 2d:00.0 chip-ID: 1002:67df
    class-ID: 0300 temp: 54.0 C
  Device-2: Creative Live! Cam Chat HD [VF0700]
    driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    mode: 2.0 bus-ID: 1-2.1.3:8 chip-ID: 041e:4088 class-ID: 0102
    serial: <filter>
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
  Monitor-1: DP-1 model: LG (GoldStar) HDR 4K serial: <filter> built: 2021
    res: mode: 3840x2160 hz: 60 scale: 100% (1) dpi: 163 gamma: 1.2 chroma: red:
    x: 0.682 y: 0.314 green: x: 0.278 y: 0.675 blue: x: 0.153 y: 0.047 white:
    x: 0.314 y: 0.329 size: 600x340mm (23.62x13.39") diag: 690mm (27.2")
    ratio: 16:9 modes: 3840x2160, 2560x1440, 1920x1080, 1600x900, 1280x1024,
    1280x800, 1152x864, 1280x720, 1024x768, 800x600, 720x480, 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.5-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 580 Series (radeonsi
    polaris10 ACO DRM 3.64 6.19.2-1-MANJARO) device-ID: 1002:67df
    memory: 7.81 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.4.341 layers: 13 device: 0 type: discrete-gpu name: AMD
    Radeon RX 580 Series (RADV POLARIS10) driver: mesa radv v: 25.3.5-arch1.1
    device-ID: 1002:67df surfaces: N/A device: 1 type: cpu name: llvmpipe
    (LLVM 21.1.6 256 bits) driver: mesa llvmpipe v: 25.3.5-arch1.1 (LLVM
    21.1.6) device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: radeontop wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere HDMI Audio [Radeon RX
    470/480 / 570/580/590] vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 2d:00.1
    chip-ID: 1002:aaf0 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 2f:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Creative Live! Cam Chat HD [VF0700]
    driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    mode: 2.0 bus-ID: 1-2.1.3:8 chip-ID: 041e:4088 class-ID: 0102
    serial: <filter>
  Device-4: Logitech Blue Microphones
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 1-2.4:9 chip-ID: 046d:0ab7 class-ID: 0300
    serial: <filter>
  API: ALSA v: k6.19.2-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.10 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-4: PulseAudio v: 17.0-98-gb096 status: active with:
    1: pulseaudio-alsa type: plugin 2: pulseaudio-jack type: module
    tools: pacat,pactl,pavucontrol
Network:
  Device-1: Intel I211 Gigabit Network vendor: Micro-Star MSI driver: igb
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 26:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp38s0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: d000 bus-ID: 27:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 28:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  IF-ID-1: br-0756a9521d5f state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-2: br-5655c497c93d state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-3: br-57a97fd3c046 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-4: br-710d85c1ab54 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-5: br-76cdcd711295 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-6: br-bf450616fe74 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-7: br-efd9a0dc4821 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-8: docker0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-9: virbr0 state: down mac: <filter>
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  Info: services: NetworkManager, sshd, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:3 chip-ID: 8087:0029
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 4.66 TiB used: 1.05 TiB (22.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 PRO 512GB
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 PRO 512GB
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Timetec model: 30TTQNS3SATA-2TB
    size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 5A0
  ID-4: /dev/sdd maj-min: 8:48 vendor: Timetec model: 30TTQNS3SATA-2TB
    size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 5A0
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 459.43 GiB size: 451.15 GiB (98.20%)
    used: 305.93 GiB (67.8%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 label: N/A
    uuid: b1beb20b-cc4f-48d6-b4dd-8af0c2d1c655
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 284 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: N/A
    uuid: 5BC1-C783
  ID-3: /home raw-size: 1.86 TiB size: 1.86 TiB (100.00%)
    used: 478.94 GiB (25.1%) fs: btrfs dev: /dev/sdc maj-min: 8:32 label: home
    uuid: b5bb9d2d-5a6e-49bf-85e9-22638a7f30a4
  ID-4: /mnt/data raw-size: 445.69 GiB size: 437.63 GiB (98.19%)
    used: 290.73 GiB (66.4%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 label: data
    uuid: b7c78c38-2f94-4800-8b9f-a35e78422a06
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 17.21 GiB used: 684 KiB (0.0%)
    priority: -1 dev: /dev/sda3 maj-min: 8:3 label: N/A
    uuid: 3cf867c8-0a8f-4184-8734-723e7fc75c34
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-2:2 info: Realtek RTS5411 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Hub-3: 1-2.1:4 info: Realtek RTS5411 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Device-1: 1-2.1.1:6 info: Razer USA DeathAdder V2 Mini
    type: mouse,keyboard driver: hid-generic,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 500mA
    chip-ID: 1532:008c class-ID: 0300
  Device-2: 1-2.1.2:7 info: Logitech Logitech Mechanical keyboard
    type: keyboard,HID driver: hid-generic,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 250mA
    chip-ID: 046d:c341 class-ID: 0300 serial: <filter>
  Device-3: 1-2.1.3:8 info: Creative Live! Cam Chat HD [VF0700]
    type: video,audio driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 200mA
    chip-ID: 041e:4088 class-ID: 0102 serial: <filter>
  Device-4: 1-2.4:9 info: Logitech Blue Microphones type: audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 046d:0ab7 class-ID: 0300 serial: <filter>
  Device-5: 1-4:3 info: Intel AX200 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0029 class-ID: e001
  Hub-4: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 2-2:2 info: Realtek Hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0411
    class-ID: 0900
  Hub-6: 2-2.1:3 info: Realtek Hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0411
    class-ID: 0900
  Hub-7: 3-0:1 info: hi-speed hub with single TT ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-5:2 info: Micro Star MEG X570 ACE type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1462:7c35 class-ID: 0300
    serial: <filter>
  Hub-8: 3-6:3 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Hub-9: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-10: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-11: 5-4:2 info: Realtek RTS5411 Hub ports: 3 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Device-1: 5-4.3:3 info: Realtek BillBoard Device type: billboard
    driver: N/A interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 500mA chip-ID: 0bda:5450 class-ID: 1100 serial: <filter>
  Hub-12: 6-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 43.0 C mobo: 41.0 C gpu: amdgpu temp: 55.0 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 1906 fan-3: 0 fan-4: 0 fan-5: 0 fan-6: 0
    fan-7: 1029 gpu: amdgpu fan: 205
Repos:
  Packages: 2302 pm: pacman pkgs: 2196 libs: 514 tools: pamac pm: pkg pkgs: 0
    pm: flatpak pkgs: 84 pm: snap pkgs: 22
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirrors2.manjaro.org/stable/$repo/$arch
    2: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    3: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    4: https://manjaro.mirrors.uk2.net/stable/$repo/$arch
    5: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    6: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
    7: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    8: https://ftp.yz.yamagata-u.ac.jp/pub/linux/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 465
  1: cpu: 12.3% command: firefox pid: 559315 mem: 1325.5 MiB (1.6%)
  2: cpu: 6.3% command: firefox pid: 559457 mem: 100.5 MiB (0.1%)
  3: cpu: 3.1% command: kwin_wayland pid: 528724 mem: 355.3 MiB (0.4%)
  4: cpu: 2.6% command: steamwebhelper pid: 543089 mem: 520.3 MiB (0.6%)
  5: cpu: 2.6% command: firefox pid: 593999 mem: 790.5 MiB (0.9%)
  Memory top: 5 of 465
  1: mem: 1325.5 MiB (1.6%) command: firefox pid: 559315 cpu: 12.3%
  2: mem: 851.8 MiB (1.0%) command: thunderbird pid: 530200 cpu: 0.6%
  3: mem: 790.5 MiB (0.9%) command: firefox pid: 593999 cpu: 2.6%
  4: mem: 733.4 MiB (0.9%) command: firefox pid: 559528 cpu: 1.3%
  5: mem: 594.8 MiB (0.7%) command: steam pid: 542757 cpu: 0.7%
Info:
  Processes: 465 Power: uptime: 2d 1h 14m states: freeze,mem,disk
    suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 31.37 GiB
    services: org_kde_powerdevil,upowerd Init: systemd v: 259
    default: graphical tool: systemctl
  Compilers: clang: 21.1.8 gcc: 15.2.1 Shell: Bash v: 5.3.9
    running-in: konsole inxi: 3.3.40
4

the log data is 1.7 megs , should i attach it?

5

Even with the -b flag? journalctl -b --no-pager. The -b flag should output only for the current boot. If your machine has been on for a while it may be quite large. Can you reboot, wait for the problem to occur then run journalctl -b --no-pager?

6

Hmm, a bit strange.

I remember back when Plasma was 5.27, I could get frequent crashes and Plasma would restart.

But since Plasma 6.x, I have never experienced any crashes.

What strikes me as a little odd is the memory array; I would have thought that a channel would have the same size units - I may be wrong of course - which is why the question comes:

  • Have you checked with your mainboard manual that the sequence is correct?

But I am thinking that you may have some sort of timing error between your memory modules - it appears to be different origins - only the 8G DIMMs appear to be from same origin - hopefully they are bought as a boxed pair (designed to work together).

  • Channel-A DIMM 0 - no name
  • Channel-A DIMM 1 - G.Skill
  • Channel-B DIMM 0 - TeamGroup
  • Channel-B DIMM 1 - G.Skill

I think I read somewhere that boards with AMD CPU/APU may be overly sensitive to using memory mixed from different origins and batches. For some there is even a list of verified vendors along with the DIMM size tested.

I am thinking - first step is to do some memory testing - and prepare yourself, this is time consuming, very time consuming.

From your mainboard manual, locate the socket the system sees as the first socket.

Then unplug all other ram modules but that.

  1. Verify the system can load the operating system.
  2. Boot the system using a memtest iso and test the module.
  3. When it pass the tast, reboot your system and use it normally to test if the crashes continues, using that module only.
  4. Replace the tested module with the next and repeat this sequence.

For the next test, use four stickers to mark the modules e.g. 8-1, 8-2, 32-1, 32-2 and use a notepad to note how you arrange the modules. Which module in which bank.

As per your manual populate the bank

  • With two 8G modules - and test
  • Revert the 8G module location - and retest
  • If supported - Move the 8G module to the second bank(channel) - and retest
  • If supported - Revert the 8G module location in the second bank(channel) - and retest

Repeat this with the 32G modules

1 Like
7

Hi @bogi,

Are you using the Open GL or the Vulkan backend?

I know the Vulkan one is still heavily experimental/alpha quality and does, indeed, cause frequent crashes, from personal experience.

Check by running the following:

kcmshell6 kcm_qtquicksettings

Set it to Open GL if it’s set to Vulkan, and Apply afterwards.

Close the window and test.

If it’s not that,

:man_shrugging:

sorry.

8

tho i added the 2x32 gig modules later, that addition was a few month ago, and the system was running stable for at least 6 month, the crashes only started after the latest updates

9

Good think :+1:

I remembered that when I run kinfo I get a message

WARNING: radv is not a conformant Vulkan implementation, testing use only.

Which leads to the question @bogi - do you have the package vulkan-radeon installed?

12

it was set to auto, i am sure it was using vulcan, and it worked totally fine until the latest kde update, i only have the crashed after the update

Operating System: Manjaro Linux 
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.19.2-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 16 Ă— AMD Ryzen 7 3800X 8-Core Processor
Memory: 80 GiB of RAM (78.5 GiB usable)
Graphics Processor: AMD Radeon RX 580 Series

i set it to open gl, let’s see what happens

Mod Edit: Merged consecutive posts.

13

My kinfo is a little different because it complains about the vulkan implementation

 $ kinfo
WARNING: radv is not a conformant Vulkan implementation, testing use only.
Operating System: Manjaro Linux 
KDE Plasma Version: 6.6.1
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 7.0.0-rc1-next-20260223-1-next-git-01146-g779cae956c83 (64-bit)
Graphics Platform: Wayland
Processors: 24 Ă— AMD Ryzen Threadripper PRO 5945WX 12-Cores
Memory: 128 GiB of RAM (125.6 GiB usable)
Graphics Processor: AMD Radeon AI PRO R9700
14

To me this looks more like something to create a report at https://bugs.kde.org/

You can get a better stacktrace using coredumpctl list and coredumpctl info [PID]

15

i agree, this looks like a kde crash issue, note nothing else is crashing , just this one program , everything else is funning FINE , i really don’t think it’s the ram, that has been running fine for many month without a hitch , i may take it with kde, but i has hoping Manjaro would carry a bigger weight forwarding it to kde than me complaining about my system

16

there are several recent bugs reported , this seems to a problem

in the latest kde release

17

Are you referring to plasmashell as component or are you referring to an app that causes plasmashell to crash?

If you are certain it is not a possible memory issue, I can think of a couple of ways to troubleshoot - listed in order to test

  1. create a new user - login and use the system as usual - make notes of apps running and which app is active when the crash happen

  2. make a system snapshot using - timeshift - store the snapshot on an external device

  • switch to testing branch
    sudo pacman-mirrors -aS testing && sudo pacman -Syyu
  • login with your test user and test using the same applications, using the same sequence that you used with number one suggestion
18

since plasmashell is the only program that keeps crashing like that, i would rather wait for the next plasma update , i can still use my desktop, only my taskbar and icons disappear when it crashes, it would be nice if it didn’t do that tho … i am not setting my main rig into testing , i like my life lol

19

I honestly have had no crashed that weren’t self-induces, so I really don’t think an update is going to “fix” it.

But anyway, if it crashes like that there Ă­s a possibility of restarting plasma without having to re-login or restart. Simply run:

kquitapp6 plasmashell || killall plasma && kstart plasmashell

This worked for me until I figured out it was Vulkan…

20

I have - Wayland was quite unstable with Plasma 5.27.

Which makes me think @bogi

Is it the same if you use X11 session?

I understand that - I only remember this from the latest Plasma 5 where the shell would occasionally restart - I cannot remember seeing it after the major version change to Plasma 6 (that may be be my memory playing tricks on me) - that is why I speculate, that it could somehow be hardware related.

Stable branch was updated February 23. - is this the update you are referring to?

I just checked - testing doesn’t have Plasma 6.6. yet - you would have to move to unstable to get past 6.5

 $ mbn info plasma-desktop -q
Branch         : archlinux
Name           : plasma-desktop
Version        : 6.6.1-1
Repository     : extra
Build Date     : Tue 24 Feb 2026 22:13:36 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : unstable
Name           : plasma-desktop
Version        : 6.6.1-1
Repository     : extra
Build Date     : Tue 24 Feb 2026 22:13:36 
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : testing
Name           : plasma-desktop
Version        : 6.5.5-1
Repository     : extra
Build Date     : Tue 13 Jan 2026 21:11:15 
Packager       : Tomaz Canabrava <tcanabrava@archlinux.org>
Branch         : stable
Name           : plasma-desktop
Version        : 6.5.5-1
Repository     : extra
Build Date     : Tue 13 Jan 2026 21:11:15 
Packager       : Tomaz Canabrava <tcanabrava@archlinux.org>
21

yes i think so

22

yes i think so

Is that

  • the update on 23.?
  • the x11 session?