[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 James changed: What|Removed |Added Resolution|--- |FIXED

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 James changed: What|Removed |Added Version|5.6.4 |5.7.0 -- You are receiving this

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 --- Comment #5 from James --- Now plasma-workspace 5.6.3-1 Still strange. The environment does not change, before and after running startplasmacompositor. systemd does not clear the files in /tmp/, just logging out and in again, so

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 --- Comment #4 from James --- Ok - finally - yes "export $(dbus-launch)" - BUT - apparently there is a running: /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation that comes up with

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 --- Comment #3 from James --- Ok, thanks. After exiting startkde the first time, this being the context for startplasmacompositor, there is: ps lU 1000 F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 4

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 Martin Gräßlin changed: What|Removed |Added CC||mgraess...@kde.org ---

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 James changed: What|Removed |Added Version|5.6.1 |5.6.2 -- You are receiving this

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 --- Comment #1 from James --- I've now upgraded to 5.6.2. Something I've noticed: Prior to the upgrade, and continuing after the upgrade, I have now gotten kde into some mode where, independent of startplasmacompositor,