Frequent KDE Plasma Crashes on Manjaro (Plasma 6.0.5 on Kernel 6.6.32-1)

[linux-aarhus]

@Kobold

Since both prog’s don’t work under Wayland

What brought you to that conclusion?

Looking over this thread - I suspect it is related to the GPU in use.

When you mention issues with resuming from sleep I assume you mean hibernate because of

@ckurdu

pci=assign-busses resume=UUID=0b9eda68-0ab7-4fba-bbb7-761b5b0b9467

and

@ckurdu

Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 34.16 GiB used: 1.13 GiB (3.3%)
    priority: -2 dev: /dev/sdc3 maj-min: 8:35 label: swap
    uuid: 0b9eda68-0ab7-4fba-bbb7-761b5b0b9467

Please see → NVIDIA/Troubleshooting - ArchWiki if there any useful troubleshooting

Also worth mentioning that the use of Nvidia GPU may pose issues when resuming from hibernation.

[Kobold]

@linux-aarhus

What brought you to that conclusion?

Its more a assumption right now as a conclusion.

Because @ckurdu told me above that he evaded Wayland because of his two proprietary program’s won’t work there.

@linux-aarhus

I suspect it is related to the GPU in use.

Possible too.

[linux-aarhus]

@Kobold

Its more a assumption right now as a conclusion.

fair enough - I use visual-studio-code-bin package - occasionally - no issues on wayland - neither with chromium - I don’t think chrome is different in that regard.

[ckurdu]

@Kobold, Maybe there is a misunderstanding.
The real reason is the Barrier app, not visual code and Chrome.

GitHub - debauchee/barrier: Open-source KVM software

@linux-aarhus
I don’t think it is a hibernation. My computer wakes up from sleep mode when I press the keyboard keys.

My power settings are

[Kobold]

@ckurdu

The real reason is the Barrier app

Maybe i missed that, but you haven’t said anything yet that you used a Virtual Machine Tool in background.

More program’s that run in the background, the higher are the possibility for bugs, that’s why i asked you earlier to shutdown all background task.

And when this program’s still permanently runs in the background and there is no transparency, this makes the bug hunting for outside people nearly impossible.

[ckurdu]

I am not aware of that. Am I using virtual machine tool?
I am using a lot of services like mariadb.service.

These are my background services. After wayland test, I can try to close them.

[ckurdu@ckurdu-last-denver ~]$ systemctl list-units --type=service --state running
  UNIT                          LOAD   ACTIVE SUB     DESCRIPTION                                   
  accounts-daemon.service       loaded active running Accounts Service
  containerd.service            loaded active running containerd container runtime
  cronie.service                loaded active running Command Scheduler
  cups.service                  loaded active running CUPS Scheduler
  dbus-broker.service           loaded active running D-Bus System Message Bus
  docker.service                loaded active running Docker Application Container Engine
  mariadb.service               loaded active running MariaDB 11.4.2 database server
  ModemManager.service          loaded active running Modem Manager
  NetworkManager.service        loaded active running Network Manager
  ollama.service                loaded active running Ollama Service
  polkit.service                loaded active running Authorization Manager
  power-profiles-daemon.service loaded active running Power Profiles daemon
  redis.service                 loaded active running Advanced key-value store
  rtkit-daemon.service          loaded active running RealtimeKit Scheduling Policy Service
  sddm.service                  loaded active running Simple Desktop Display Manager
  sshd.service                  loaded active running OpenSSH Daemon
  systemd-journald.service      loaded active running Journal Service
  systemd-logind.service        loaded active running User Login Management
  systemd-timesyncd.service     loaded active running Network Time Synchronization
  systemd-udevd.service         loaded active running Rule-based Manager for Device Events and Files
  systemd-userdbd.service       loaded active running User Database Manager
  udisks2.service               loaded active running Disk Manager
  upower.service                loaded active running Daemon for power management
  user@1000.service             loaded active running User Manager for UID 1000

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.

24 loaded units listed.

[Kobold]

@ckurdu

Am I using virtual machine tool?

From the describtion from Barrier, it sounds like a VM.

And since KVM has VM in his name, which makes me thinking it could be a Virtual Machine. But what is it then? A Remote Access Tool?

@ckurdu

These are my background services. After wayland test, I can try to close them.

Well lets see if your system is crashing again.

[ckurdu]

I got it
KVM came from Keyboard, Video Mouse.

[KVM Switch](KVM switch - Wikipedia

[vilmil]

@ckurdu

I put my Manjaro system into sleep mode, and when I tried to power up my computer in the morning, it initially opened my windows correctly but then crashed and auto-logged into KDE Plasma without the previous windows.

I tested this. I put my system into sleep and there was no problem when waking it up.
Does your problem occur every time you put it to sleep? If yes then that means this is a separate problem because I didn’t face it.

[ckurdu]

It only occurred during a long sleep state in my Manjaro OS.
I tried three times after the crashes, they went well.
I am sure they weren’t hibernate states.
So this is so weird.

After the Wayland, today the error didn’t occur. @Kobold

However, I will wait for a few more days.

[ckurdu]

Also, I realized that the Upwork app couldn’t get screenshots from Wayland.
So x11 should be crucial for me.

[Kobold]

I think i pointed to a lot options already, i didnt saw that you responsed to this.

Frequent KDE Plasma Crashes on Manjaro (Plasma 6.0.5 on Kernel 6.6.32-1)

No problem. When resetting the cache folder is not fixing the problem, you can try to create a new Login. But i guess, just one step at his time… otherwise you can’t be sure, where exactly the issue is coming from. Btw. Rename a folder should be recommend for caching, you can delete it later anyways. Besides creating a second login, which probably is the worst option because its resetting all configuration’s (do it only for testing). It’s a huge time sink and probably the most people would p…

The problem with your Wayland test is, that you don’t use the same program’s right now under Wayland that you had in use under X11.

[ckurdu]

---

I tried the following sets of programs:

• x11, Visual Code, Chrome, Upwork, Barrier, Discord: failed
• x11, Visual Code, Chrome, Upwork, Discord: failed
• x11, Chrome: failed
• x11, Firefox: failed
• Wayland, Chrome: not failed
• Wayland, Chrome, Visual Code: not failed
• Wayland, Chrome, Visual Code, Upwork (with screenshot problem): not failed

I didn’t change any background services. Below are the background services used without change in all my tries:

  UNIT                          LOAD   ACTIVE SUB     DESCRIPTION                                   
  accounts-daemon.service       loaded active running Accounts Service
  containerd.service            loaded active running containerd container runtime
  cronie.service                loaded active running Command Scheduler
  cups.service                  loaded active running CUPS Scheduler
  dbus-broker.service           loaded active running D-Bus System Message Bus
  docker.service                loaded active running Docker Application Container Engine
  mariadb.service               loaded active running MariaDB 11.4.2 database server
  ModemManager.service          loaded active running Modem Manager
  NetworkManager.service        loaded active running Network Manager
  ollama.service                loaded active running Ollama Service
  polkit.service                loaded active running Authorization Manager
  power-profiles-daemon.service loaded active running Power Profiles daemon
  redis.service                 loaded active running Advanced key-value store
  rtkit-daemon.service          loaded active running RealtimeKit Scheduling Policy Service
  sddm.service                  loaded active running Simple Desktop Display Manager
  sshd.service                  loaded active running OpenSSH Daemon
  systemd-journald.service      loaded active running Journal Service
  systemd-logind.service        loaded active running User Login Management
  systemd-timesyncd.service     loaded active running Network Time Synchronization
  systemd-udevd.service         loaded active running Rule-based Manager for Device Events and Files
  systemd-userdbd.service       loaded active running User Database Manager
  udisks2.service               loaded active running Disk Manager
  upower.service                loaded active running Daemon for power management
  user@1000.service             loaded active running User Manager for UID 1000

---

[Kobold]

@ckurdu

I didn’t change any background services.

Im not sure if a background service can lead to a Desktop Reset, but i guess this case should more related to active GUI Task’s.

Additional to my 5 points, which i posted already… you could maybe disable compositor under system settings>Display Monitor.

[ckurdu]

It seems Wayland is working well. No crash.

So what is the real problem in x11?

Before I tired,
removed cache
and I did what you sent before.

1. Disable widget’s if you have some.
2. Resetting KDE Desktop Layouts to default.
3. You may want to remove old orphan’s from KDE5 with:
   sudo pacman -Ru kf5
4. If you have AUR enabled, its worth it to check orphan’s and remove them… specially under Foreign and look for AUR inside which you didn’t had installed manually.

[Kobold]

Output of:
sudo pacman -Qqm

Disable compositor under system settings>Display Monitor or disable energy savings, i personally don’t use it on my PC with a nvidia card either.