Plasma crash and freeze in Manjaro Testing

Ive been recently getting some plasma crashes that causes several apps that im using to crash all at once. Say im talking on discord and then go to firefox, then when im ready to go to back to discord, i find out that the entirety of plasmashell, discord and even other apps im using have outright crashed and dont respond, making me have to force quit them and restart them, sometimes even losing progress in whatever app im in. I have looked at some of the lines of the error in yakuake and it has some kio core lines and crashes, im unsure what the error roots from as its entirely software, and im not even sure if its solely a 5.18.5 issue or not as i cant really manage to search it on my own

First of all, have you updated your system yet? There was a major update only a few days ago. :arrow_down:

Secondly, what kernel are you using, and what graphics driver? Please post the output of the following command. :arrow_down:

inxi -Fxxxza 

I should have mentioned im on testing, and everything i have is completely up to date. Here is the output, and im on kernel 5.6.15, eventually going to be on 5.7 once i reboot. And if it matters i have been using xrender under compositor, and am currently seeing if it acts the say under opengl 3.1

System:
  Host: lillie-bladestealth Kernel: 5.6.15-1-MANJARO x86_64 bits: 64 
  compiler: gcc v: 10.1.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6-x86_64 
  root=UUID=54982d93-07b2-4d71-a5a6-790d453d8d66 rw quiet apparmor=1 
  security=apparmor udev.log_priority=3 
  Desktop: KDE Plasma 5.18.5 tk: Qt 5.14.2 wm: kwin_x11 dm: SDDM 
  Distro: Manjaro Linux 
Machine:
  Type: Laptop System: Razer product: Blade Stealth v: 4.06 serial: <filter> 
  Chassis: type: 9 serial: <filter> 
  Mobo: Razer model: Blade Stealth serial: <filter> UEFI: Razer v: 2.1 
  date: 12/11/2017 
Battery:
  ID-1: BAT0 charge: 42.2 Wh condition: 53.4/53.8 Wh (99%) volts: 13.1/11.6 
  model: Razer Razer Blade Stealth type: Unknown serial: <filter> 
  status: Charging 
CPU:
  Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP 
  arch: Kaby Lake family: 6 model-id: 8E (142) stepping: A (10) 
  microcode: CA L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 
  bogomips: 32012 
  Speed: 800 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
  Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
  Type: l1tf mitigation: PTE Inversion 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  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: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Razer USA driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:5917 
  Display: x11 server: X.Org 1.20.8 driver: intel compositor: kwin_x11 
  tty: N/A 
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.7 
  direct render: Yes 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Razer USA 
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71 
  Sound Server: ALSA v: k5.6.15-1-MANJARO 
Network:
  Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter 
  vendor: Bigfoot Networks driver: ath10k_pci v: kernel port: f040 
  bus ID: 01:00.0 chip ID: 168c:003e 
  IF: wlp1s0 state: up mac: <filter> 
  Device-2: Qualcomm Atheros type: USB driver: btusb bus ID: 1-6:3 
  chip ID: 0cf3:e300 
Drives:
  Local Storage: total: 238.47 GiB used: 59.11 GiB (24.8%) 
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-00000 
  size: 238.47 GiB block size: physical: 512 B logical: 512 B 
  speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: CXB7401Q scheme: MBR 
Partition:
  ID-1: / raw size: 30.00 GiB size: 29.40 GiB (98.01%) 
  used: 16.49 GiB (56.1%) fs: ext4 dev: /dev/nvme0n1p1 
  ID-2: /home raw size: 207.97 GiB size: 203.70 GiB (97.95%) 
  used: 42.62 GiB (20.9%) fs: ext4 dev: /dev/nvme0n1p2 
Sensors:
  System Temperatures: cpu: 41.5 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 236 Uptime: 11h 43m Memory: 15.53 GiB used: 2.02 GiB (13.0%) 
  Init: systemd v: 245 Compilers: gcc: 10.1.0 Shell: bash v: 5.0.17 
  running in: konsole inxi: 3.0.37 

I'll amend the thread title then. :wink:

Well, that might make a difference, because you're using an in-kernel graphics driver.

XRender does all of its compositing in software. OpenGL employs hardware-assisted compositing, so that would always be the better choice. Your graphics processor should be able to handle it.

1 Like

Alright, just rebooted, i guess ill update whether or not it happens again, which may be a while if it does.

1 Like

Please don't report issues if you haven't rebooted after a major update like that.

You can use needrestart to help you see what services need to be restarted and which proceses are running out of date binaries.

1 Like

This isnt an issue that happened before i rebooted, its a recurring issue that happens 3 times a day when using xrender, it doesnt happen on opengl. I only just installed kernel 5.7 last night and hadnt rebooted yet

So, update, it has not crashed at all today, so the issue has been xrender this entire time, though now i hae screen tearing when scrolling in some apps again, guess its better than plasma crashing.

quick edit: If your using KDE plasma and experience plasmashell crashes, try changing the compositor settings a little

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by