GitLab

Using real logind causes issues with CI as it's dependent on external
factors and it can leave the host machine is an unclean state.

We can't mock it like we do in the internal tests as easily and it
wouldn't be very useful to do so. We can't disable completly as
lockscreentest relies on externally emitting a signal on this object.

KLibexec doesn't work on usr-merged distros as libraries can be loaded
through a different path (/lib*) than they are installed to (/usr/lib*).

BUG: 452817

Whilst authenticating we emit signals and expect callbacks to prompts.
The pam worker is inside pam_authenticate in the nested event loop.

It is not expected for GUI clients to call authenticate twice without a
cancel inbetween, but we should still guard against it as it causes a
mess.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

kcheckpass existed because historically we needed to be root to check
passwords. This hasn't been true for tens of years. There are no
security benefits, all authentication is based on the exit status of the
greeter application.

This patch drops kcheckpass and brings everything in process, but in
another thread.

This also reports back more fine grained PAM control at the same time
(following on from !29) forwarding all prompts and messages.

The unit test has been replaced with one that actually checks against a
real PAM using pam_wrapper to force a fake user.

In preparation check the version and fall back to breeze

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Loren Burkholder authored Apr 22, 2022 and Fushan Wen committed Apr 22, 2022

I've noticed that KScreenLocker will always recommend using virtual terminal 2 to recover from a crash, even if you are on virtual terminal 2. This MR should fix that.

Please note that I have not actually tested this for two reasons: (1) I have no idea how to make KScreenLocker crash, and even if I did, (2) I don't have a Plasma dev environment set up to crash it in (although I'd be happy to do so).

Wallpaper kcms use sometimes the Plasmoid object (conditionally) to
check some parameters.

Recently, we ported from the old "plasmoid" context to the Plasmoid
attached property coming from org.kde.plasma.plasmoid. This needs to
have its import available otherwise QML rightly refuses to load
anything.

This includes the import by only registering a dummy empty object so it
doesn't complain anymore.

BUG: 452757

KWayland::Server is deprecated and KWaylandServer is going to be merged
with KWin.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

We never call this constructor manually

Task: https://phabricator.kde.org/T14733

This is where systemsettings will look for plugins when not going thourgh KServiceTypeTarder

Task: https://phabricator.kde.org/T14517

Task: https://phabricator.kde.org/T14983

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

This is now done as part of the plasma integration plugin.

Task: https://phabricator.kde.org/T12135

PACKAGE_PREFIX_DIR will be used in the generated code of the @PACKAGE_@
placeholder, and can be changed by find_dependency() calls. Worked by
chance so far, but happens with Qt6. This then results in build failures
in consumers trying to locate kscreenlocker's D-Bus files.

This also includes some of the necessary code changes, but especially the
port to KWaylandServer is still missing.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Julius Zint authored Jan 21, 2022 and David Edmundson committed Feb 02, 2022

The Layer Shell Qt library is updated to match its API more closely to
the protocol. It is now possible, or rather required if the behavior
should not change, to specify a desired output for a LayerShell window.

Otherwise the KCM will not show up in plasma-settings.