There was a name clash between the signal and the AccelButton.
This work has been sponsored by the City of Munich's LiMux project.
Forward port of kde-workspace ce7746b2dd1426efc627ab17ec8ea9b2eaa1d656
The user switching dialog from the screen locker was destroyed when the
cancel button was pressed. As a result you coudn't open it again.
The screen locker uses a PlasmaComponents.PageStack to show the password input
and user switching dialogs.
When a dialog is popped from the stack it is destroyed by PageStack.
Fix this by turning userSessionsUI into a Component so it is automatically
created.
This work has been sponsored by the City of Munich's LiMux project.
Forward port of kde-workspace 3341db4430026914da4c6b5f90c1ef6920bae9d1
This adds a button that allows toggling keyboard layouts from the
lockscreen. It talks and listens to the KDED's keyboard module.
REVIEW: 119794
BUG: 338518
FIXED-IN: 5.0.2
The lock screen will now show a warning when Caps Lock is enabled, like it used to
in KDE 4 screen locker.
The patch also removes the old X-based Caps Lock detection from greeterapp.cpp and
instead uses the Keystate DataEngine.
REVIEW: 119797
Currently KLauncher is responsible for starting all of the autostart
files. It intelligently starts only the files which should be started in
the KDE environment.
Once this is done, KLauncher then decides to also start all the files
in the autostart folder, but does that without checking which should be
started. I'm not sure why both KSMServer and KLauncher are overlaping
and doing the same thing. But it seems that KLauncher is the correct
place to do this. Specially since ksmserver uses kioclient5 in order to
start the applications.
BUG: 335878
REVIEW: 118977