Bug 425268

Summary:	Logout screen shows a blank blurred overlay with no UI controls on it
Product:	[Plasma] plasmashell	Reporter:	Nate Graham <nate>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED FIXED
Severity:	normal	CC:	claudius.ellsel, isma.af, plasma-bugs, uhhadd
Priority:	VHI	Keywords:	regression
Version:	master
Target Milestone:	1.0
Platform:	Other
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=425272
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Blank logout screen

Description Nate Graham 2020-08-12 17:22:52 UTC

Created attachment 130830 [details]
Blank logout screen

This started happening to me in the last week or two, on both X11 and Wayland. See attached screenshot. The screenshot shows Wayland, which additionally suffers from the window being windowed rather than full screen (Bug 423953).

I tried bisecting the following back to about the middle of July:

- plasma-framework bisected to a851c78bfe4dce58b2902c061d8f96834c2ed50e (July 18)
- plasma-workspace bisected to be421fa88ff26b7c04ab1a47f4a23b757e1057f9 (July 16)
- plasma-desktop bisected to 117c84289279f5d8868f8142aa09c8d0841bdaf3 (July 16)
- kdeplasma-addons bisected to ba8309e74c6ae480293d54dc8237ad8664910387 (July 16)
- Tried to bisect kwin to cf2712887701a97c2c1acda4f916efa0a08c5561 (July 14) with plasma-wayland-protocols 75dea9022260e857cf59a18d7271816d1e2e3e4e (May 19) however I could not get KWin to build :(

I was not able to find the commit that caused this. :( So it may be some local issue on my machine, but I have not been successful in figuring out what it is.

Additional data point: Running `/home/nate/kde/usr/lib64/libexec/ksmserver-logout-greeter` in a terminal window with no arguments displays nothing, but adding any argument at all (even nonsense args like --foobar) makes the logout screen appear correctly exactly as I would expect.

Comment 1 Janet Blackquill 2020-08-19 15:55:49 UTC

Can reproduce.

Comment 2 David Edmundson 2020-08-21 13:48:11 UTC

Spoke online, it's a setup problem.

@carson if you can reproduce and 

dbus-send --session --print-reply --dest=org.freedesktop.DBus  /org/freedesktop/DBus org.freedesktop.DBus.ListActivatableNames

contains org.kde.LogoutPrompt please reopen


If not your DBus activatable services aren't set up properly.

Comment 3 Ismael Asensio 2020-08-26 21:02:30 UTC

(In reply to David Edmundson from comment #2)
> Spoke online, it's a setup problem.
> 
> @carson if you can reproduce and 
> 
> dbus-send --session --print-reply --dest=org.freedesktop.DBus 
> /org/freedesktop/DBus org.freedesktop.DBus.ListActivatableNames
> 
> contains org.kde.LogoutPrompt please reopen
> 
> 
> If not your DBus activatable services aren't set up properly.

Re-opening on your hint.

dbus-send --session --print-reply --dest=org.freedesktop.DBus  /org/freedesktop/DBus org.freedesktop.DBus.ListActivatableNames | grep Logout
      string "org.kde.LogoutPrompt"

Comment 4 Nate Graham 2020-09-14 20:49:29 UTC

This is caused by an installation problem. You need to have all kinds of fancy dbus things installed to /, or else to have your dbus/kauth/polkit dirs include the place where you're installing them.

I have not managed to do this successfully. See also Bug 425272.

Comment 5 Claudius Ellsel 2020-09-15 14:28:43 UTC

Currently there does not seem to be proper documentation available on what "fancy dbus things" are needed to be setup.

Also, since this started happening for you only recently, did something change in that period requiring more dbus related things to be set up appropriately?

Also see David's comment which suggests that things should be setup properly if 

> dbus-send --session --print-reply --dest=org.freedesktop.DBus 
> /org/freedesktop/DBus org.freedesktop.DBus.ListActivatableNames
> 
> contains org.kde.LogoutPrompt

which apparently is the case for Ismael.

So was that statement based on wrong assumptions or something like that?

Comment 6 David Edmundson 2020-09-15 15:34:47 UTC

>Also see David's comment which suggests that things should be setup properly if 

That proves there's /a/ login prompt. It doesn't indicate which one it will load if you have two on your system.

Comment 7 Claudius Ellsel 2020-09-15 15:39:54 UTC

(In reply to David Edmundson from comment #6)
> That proves there's /a/ login prompt. It doesn't indicate which one it will
> load if you have two on your system.

Alright thanks for clarifying. Then that statement probably did not apply to a broader context, but just to Carson in particular.

Comment 8 Claudius Ellsel 2020-10-04 18:13:41 UTC

(In reply to Nate Graham from comment #4)
> This is caused by an installation problem. You need to have all kinds of
> fancy dbus things installed to /, or else to have your dbus/kauth/polkit
> dirs include the place where you're installing them.
> 
> I have not managed to do this successfully. See also Bug 425272.

It works for me currently again. Since I did not change any dbus or other things I'd assume that this is not caused by that not being setup properly but by something else that got changed in between probably.

Thus I mark this as fixed (changing from not a bug). Feel free to object or revert if something is wrong with my reasoning.