Created attachment 106036 [details] Support information First of all, this started happening when I moved my installation on a faster ssd (Samsung 960 pro), so I think it could be a race condition. When I select any kind of aurorae theme for kwin, on every boot compositing is disabled and the compositor kcm is opened automatically. I have to manually enable compositing either with the keyboard shortcut or with said kcm. After this, everything works normally. This does not happen with the breeze theme. I can reproduce it with a fresh user too.
Could you find out if compositing was disabled because kwin crashed? If yes, the backtrace for the crash would be useful.
I have no evidence that kwin is crashing (no crash dumps, nothing in xsession-errors), please find my xsession-errors attached if you want to take a look. Also i can confirm that inserting a 1-second sleep before kwin starts solves the problem.
Created attachment 106079 [details] xsession-errors
please provide output of: qdbus org.kde.KWin /KWin supportInformation and please attach your kwinrc.
Created attachment 106140 [details] kwinrc
Support information is attached to the first post :) I've attached kwinrc
The output of this command is missing: qdbus org.kde.KWin /KWin supportInformation
Ah wait, it was already attached in comment #0. Merci.
Try switching to OpenGL 2
Unfortunately it still happens with Opengl 2
could you please enable all debug categories for KWin through kdebugsettings and paste the output with that for a failing run.
Still waiting for more debug output
Created attachment 108526 [details] xsession-errors with debugging enabled Sorry for the delay, I hadn't access to this machine for a while... here's the log
Thanks for adding
What's the togglecompositing you have in autostart?
(In reply to Martin Flöser from comment #15) > What's the togglecompositing you have in autostart? It's my workaround for this bug: #!/bin/sh sleep 3 xdotool key shift+alt+F12
To make this more robust you can interact with the dbus interface to enable compositing without the need to toggle
This issue report is quite old. Can you please confirm, that it still persists with KDE 5.23?
Thanks for the reminder, it looks like it was solved a few releases ago