Bug 381071

Summary: Compositing disabled on boot when any aurorae theme is chosen
Product: [Plasma] kwin Reporter: Alberto Mattea <alberto>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: alberto, kde.org
Priority: NOR    
Version: 5.10.0   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Support information
xsession-errors
kwinrc
xsession-errors with debugging enabled

Description Alberto Mattea 2017-06-10 17:42:24 UTC
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.
Comment 1 Christoph Feck 2017-06-11 23:52:25 UTC
Could you find out if compositing was disabled because kwin crashed? If yes, the backtrace for the crash would be useful.
Comment 2 Alberto Mattea 2017-06-13 15:26:11 UTC
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.
Comment 3 Alberto Mattea 2017-06-13 15:26:31 UTC
Created attachment 106079 [details]
xsession-errors
Comment 4 Martin Flöser 2017-06-17 12:40:57 UTC
please provide output of:
qdbus org.kde.KWin /KWin supportInformation

and please attach your kwinrc.
Comment 5 Alberto Mattea 2017-06-17 12:51:43 UTC
Created attachment 106140 [details]
kwinrc
Comment 6 Alberto Mattea 2017-06-17 12:52:22 UTC
Support information is attached to the first post :)
I've attached kwinrc
Comment 7 Christoph Feck 2017-06-18 03:41:01 UTC
The output of this command is missing:

qdbus org.kde.KWin /KWin supportInformation
Comment 8 Christoph Feck 2017-06-18 03:41:49 UTC
Ah wait, it was already attached in comment #0. Merci.
Comment 9 Martin Flöser 2017-06-18 07:15:41 UTC
Try switching to OpenGL 2
Comment 10 Alberto Mattea 2017-06-19 10:30:34 UTC
Unfortunately it still happens with Opengl 2
Comment 11 Martin Flöser 2017-07-22 19:17:17 UTC
could you please enable all debug categories for KWin through kdebugsettings and paste the output with that for a failing run.
Comment 12 Martin Flöser 2017-10-22 17:11:52 UTC
Still waiting for more debug output
Comment 13 Alberto Mattea 2017-10-23 16:28:07 UTC
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
Comment 14 Martin Flöser 2017-10-23 18:23:56 UTC
Thanks for adding
Comment 15 Martin Flöser 2018-02-01 20:05:38 UTC
What's the togglecompositing you have in autostart?
Comment 16 Alberto Mattea 2018-02-02 21:05:45 UTC
(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
Comment 17 Martin Flöser 2018-02-03 07:45:46 UTC
To make this more robust you can interact with the dbus interface to enable compositing without the need to toggle
Comment 18 kde.org 2021-11-06 20:01:21 UTC
This issue report is quite old. Can you please confirm, that it still persists with KDE 5.23?
Comment 19 Alberto Mattea 2021-11-07 10:49:33 UTC
Thanks for the reminder, it looks like it was solved a few releases ago