Bug 365591

Summary:	window compositing won't start at login
Product:	[Plasma] kwin	Reporter:	Naufal Fachrian <naufal.fachrian>
Component:	compositing	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	5.7.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Compositor setting that I am using. qdbus org.kde.KWin /KWin supportInformation (on) qdbus org.kde.KWin /KWin supportInformation )off) kwin state after login no translucency kwin after --replace translucency on

Description Naufal Fachrian 2016-07-13 04:43:28 UTC

Window compositing won't start at login and I have enabled the compositor on startup. I need to restart plasmashell in order to enable compositor.

I use KDE Neon 5.7.0 ISO

Reproducible: Always

Steps to Reproduce:
1. Login
2. Compositor won't start until you restart plasmashell

Actual Results:  
compositor won't start automatically

Expected Results:  
compositor should be started automatically

Logout then login again should fix it. But, should I re-login just to activate compositor?
I have created script to restart plasmashell and make it as a startup autostart, but it won't help.

#!/bin/bash
killall plasmashell &&
kstart5 plasmashell

but if I run it manually, it'll help.

Comment 1 Naufal Fachrian 2016-07-13 04:45:42 UTC

Created attachment 100054 [details]
Compositor setting that I am using.

Comment 2 Martin Flöser 2016-07-13 06:22:37 UTC

please provide output of:
qdbus org.kde.KWin /KWin supportInformation

when the compositor is running and when not running.

Comment 3 James Rodriguez 2016-07-13 14:32:28 UTC

I think I have similiar issue. Before plasma 5.7 there was like 50% chance that composition will be on after login. After composition it's always off.

Comment 4 James Rodriguez 2016-07-13 14:34:33 UTC

Created attachment 100066 [details]
qdbus org.kde.KWin /KWin supportInformation (on)

Comment 5 James Rodriguez 2016-07-13 14:36:12 UTC

Created attachment 100067 [details]
qdbus org.kde.KWin /KWin supportInformation )off)

Comment 6 Thomas Lübking 2016-07-13 15:23:15 UTC

given the upload time and order:
I think Martin wants to see the information when compositing is not "enabled" (need to restart plasmashell points something entirely different) on login, so please confirm you did *not* cause this state by explicitly suspending the compositor, but it actually reflects the situation right after the login.

Comment 7 Thomas Lübking 2016-07-13 15:26:05 UTC

ftr, I bet on bug #364641

Comment 8 James Rodriguez 2016-07-13 17:36:06 UTC

Created attachment 100070 [details]
kwin state after login no translucency

Ok I blew it. I admit. I'm sorry.

Composition is always on but translucency (and contrast effect) is off after login on plasma panel, notification popups and krunner. Sometimes contrast effect works on krunner after login but never on plasma panel. After disabling contrast effect there is still no translucency on plasma panel after login. After restart kwin everything works

I don't want to hijack this bugthread maybe my problem is unrelated to the author's.

Comment 9 James Rodriguez 2016-07-13 17:37:28 UTC

Created attachment 100071 [details]
kwin after --replace translucency on

Comment 10 Thomas Lübking 2016-07-13 17:42:03 UTC

No problem ;-)
And no: I'm pretty sure your both just facing bug #364641 (explanation of the failure over there, it's in libplasma, though. KWin isn't the problem at all. It's a simple race on the availability check for the compositor)

Comment 11 Martin Flöser 2016-11-02 13:21:14 UTC

Assuming duplicate of the well known and fixed issue of bug #364641. In case the later version does not fix it, please reopen.

*** This bug has been marked as a duplicate of bug 364641 ***