Kwin_x11 crashing repeatedly

same problem facing :smiling_face_with_tear:
itā€™s a bug???

https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=kwin-x11;dist=unstable

.

My first thought would be to disable anything that puts demands on the compositor. Disable the KDE visual effects in KDEā€™s system settings to see if that helps.
You might also want to try disabling any plasmoids you have installed.

but in my case the settings manager is crashedā€¦its open with black screen
this is my garuda inxiā€¦

ā•°ā”€Ī» garuda-inxi
System:
Kernel: 5.15.84-1-lts arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=bf08036d-22f5-4042-836f-34387c2571c4 rw rootflags=subvol=@
splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=36ca17a6-c461-4bb5-b067-65ca87b9600c loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.26.4 tk: Qt v: 5.15.7 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: H110M-S2 v: N/A
serial: <superuser required>
Mobo: Gigabyte model: H110M-S2-CF v: x.x serial: <superuser required>
UEFI: American Megatrends v: F21 date: 06/09/2017
CPU:
Info: model: Intel Core i3-6100 bits: 64 type: MT MCP arch: Skylake-S
gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
model-id: 0x5E (94) stepping: 3 microcode: 0xF0
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 800 min/max: 800/3700 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 29598
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: IBRS
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: IBRS, IBPB: conditional, RSB filling,
PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GT218 [GeForce G210] driver: nouveau v: kernel non-free:
series: 340.xx status: legacy (EOL) last: release: 340.108 kernel: 5.4
xorg: 1.20 arch: Tesla process: 40-80nm built: 2006-13 pcie: gen: 1
speed: 2.5 GT/s lanes: 16 ports: active: VGA-1 empty: DVI-I-1,HDMI-A-1
bus-ID: 01:00.0 chip-ID: 10de:0a60 class-ID: 0300 temp: 37.0 C
Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7
compositor: kwin_x11 driver: X: loaded: nouveau unloaded: modesetting
alternate: fbdev,nv,vesa dri: nouveau gpu: nouveau display-ID: :0
screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
Monitor-1: VGA-1 model: LG (GoldStar) HD serial: <filter> built: 2017
res: 1366x768 hz: 60 dpi: 85 gamma: 1.2 size: 410x230mm (16.14x9.06")
diag: 470mm (18.5") ratio: 16:9 modes: max: 1366x768 min: 720x400
API: OpenGL v: 3.3 Mesa 22.3.1 renderer: NVA8 direct render: Yes
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170
class-ID: 0403
Device-2: NVIDIA High Definition Audio driver: snd_hda_intel v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0be3
class-ID: 0403
Sound API: ALSA v: k5.15.84-1-lts running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.63 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1.58 TiB used: 34.44 GiB (2.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT240BX500SSD1
size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 056 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST3500413AS
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: JC4B scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD10EZEX-60WN4A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: 1A01 scheme: MBR
Partition:
ID-1: / raw-size: 64.52 GiB size: 64.52 GiB (100.00%)
used: 16.38 GiB (25.4%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
ID-2: /boot/efi raw-size: 600 MiB size: 598.8 MiB (99.80%)
used: 608 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 125.51 GiB size: 125.51 GiB (100.00%)
used: 18.06 GiB (14.4%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
ID-4: /var/log raw-size: 64.52 GiB size: 64.52 GiB (100.00%)
used: 16.38 GiB (25.4%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
ID-5: /var/tmp raw-size: 64.52 GiB size: 64.52 GiB (100.00%)
used: 16.38 GiB (25.4%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.79 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda2 maj-min: 8:2
ID-2: swap-2 type: zram size: 7.71 GiB used: 93 MiB (1.2%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 34.0 C mobo: N/A gpu: nouveau temp: 37.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 249 Uptime: 49m wakeups: 0 Memory: 7.71 GiB
used: 3.89 GiB (50.4%) Init: systemd v: 252 default: graphical
tool: systemctl Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 1583
libs: 374 tools: octopi,pamac,paru Shell: fish v: 3.5.1 default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.24
Garuda (2.6.12-1):
System install date:     2022-11-15
Last full system update: 2022-12-21
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Snapper
Failed units:            dev-binderfs.mount systemd-networkd-wait-online.service

kwin -replase couldnot work
but i canā€™t understand why my kde system settings couldnot opening?
is there any other way?

1 Like

Try disabling the compositor with key combo, and then see if you can open the System Settings.

1 Like

i did it

using ctrl+shift+F12
and also using qdbus org.kde.KWin /Compositor suspend

but sill settings is blackā€¦

1 Like

I'm still waiting on a new disk, but I can confirm that I've also tried to disable compositing via keybind as well, and it gave me the identical result.

1 Like

Bumping to keep this alive. I got covid, still recovering.

3 Likes

I know you have been waiting a long time for a solution to this, however we try to discourage empty bumps on the forum. It is far better to include any recent fixes you have attempted or new information you have found pertaining to your issue. Empty bumps are simply considered clutter when reading the the latest posts list and should be avoided.

Have you tried creating a new user to see if the issue persists on a new account?

I know the following is not going to help resolve your problem, but it may make it easier to correct a lockup when it occurs. Restarting plasma or kwin is much simpler with either a desktop file shortcut on your dock or a key binding shortcut for the restart command.

Use a command similar to the following to make sure the new session does not end when closing the terminal window used for restarting plasma:

kquitapp5 plasmashell; plasmashell > /dev/null 2>&1 & disown; sleep 2; exit
1 Like

Brand new Linux user (a few weeks spent distro hopping) and I'm having the same issue as you.

On a fresh install, just after updating everything, I was browsing settings and experienced a freeze for a good 10-15 seconds and then was greeted with a bunch of popups saying that Kwin had recovered.

I read the entire thread with baited breath hoping you had resolved this issue.

Bummer.

1 Like

Yes.

Unfortunately there is no way to get back to a working graphical environment once it hangs. Iā€™ve done a couple partial updates since to get specific things to work. Itā€™s not been fun package jenga especially without any useful logs, but itā€™s been enough to get a browser working with help from a friend. Also tried using DISPLAY=:0 from another TTY for it.


Today I got my new disk, Iā€™m going to be reinstalling and slowly migrating [most] of my config back over, and seeing if there is a point where something causes problems. Iā€™ll probably move back to Zen kernel, but I will definitely test others as well; and post the final results here. I almost hope I can reproduce the same issue on a fresh install, just so it can be figured out before the next release.

1 Like

I'm still getting crashes, but much less frequently. I'll definitely post more when I can reliably reproduce them, but it seems like adding widgets repeatedly can sometimes trigger it, though not always. When it does crash there, it is almost a second after the widget list is shown.

spectacle doesn't open a graphical window, or print an error. This could have been the case since the new install, I did not confirm if it worked at that moment. --help and --version produce outputs.

1 Like

A post was split to a new topic: KDE just crashes out of nowhere