Package Details: plasma-login-manager-git r1941.6606669-2

Git Clone URL: https://aur.archlinux.org/plasma-login-manager-git.git (read-only, click to copy)
Package Base: plasma-login-manager-git
Description: Plasma Login provides a display manager for KDE Plasma, forked from SDDM and with an new frontend providing a greeter, wallpaper plugin integration and System Settings module (KCM).
Upstream URL: https://invent.kde.org/plasma/plasma-login-manager
Licenses: CC-BY-3.0 AND BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only OR GPL-3.0-only AND GPL-2.0-or-later AND LGPL-2.0-or-later AND LGPL-2.1-or-later
Conflicts: plasma-login-manager
Provides: display-manager
Submitter: huyz
Maintainer: peregrinus
Last Packager: peregrinus
Votes: 10
Popularity: 3.42
First Submitted: 2025-04-02 15:01 (UTC)
Last Updated: 2026-01-17 10:19 (UTC)

Latest Comments

1 2 Next › Last »

techmanwalker commented on 2026-01-17 20:53 (UTC) (edited on 2026-01-17 20:54 (UTC) by techmanwalker)

This issue can be fixed only if the mantainer of libplasma-git change their provides line to:

provides=("${pkgname%-git}=${pkgver%%_*}")

With this, dependency resolution now works correctly because it removes the conflicting underscore that makes it fail in the first place.

peregrinus commented on 2026-01-17 18:08 (UTC)

@SashaMTR: I don't think you can just install libplasma-git without the rest of plasma at that version?

What I did is: I configured the testing repositories0, including kde-unstable, as it has the correct libplasma version available in there. Alternatively, you could wait until the end of the month, around which time 6.5.91 is expected to be released upstream1, and might then soon also be available in Archlinux' normal repositories.

Just a heads-up: If you have plasma-meta installed, then plasma-login-manager from the kde-unstable repo will be pulled in, which is a few version behind this git package. The two packages will conflict, and you would have to remove plasma-meta before you could install this git package.

It is up to you if this is worth the trouble until the end of the month (or whenever all of this lands in Archlinux via non-testing repos), or if you would rather stick to the previous version until then.

I hope this helps.

SashaMTR commented on 2026-01-17 13:22 (UTC)

There a issue with libplasma : libplasma>=6.5.90 (required by : plasma-login-manager-git) I already have installed libplasma-git with version 6.5.90_r17834.ge28735e04-1 but it seems to ignore the version i have .

peregrinus commented on 2025-12-30 07:36 (UTC) (edited on 2025-12-30 07:36 (UTC) by peregrinus)

@gdamjan: I looked into moving the tmpfiles to the Systemd service file, but I cannot see how this can be done.

The tmpfiles configuration looks like this (form upstream):

# Home dir of the plasmalogin user, also contains state.conf
d       /var/lib/plasmalogin    0750    plasmalogin     plasmalogin
# This contains X11 auth files passed to Xorg and the greeter
d       /run/plasmalogin        0711    root    root
# Sockets for IPC
r!      /tmp/plasmalogin-auth*
# xauth files passed to user sessions
r!      /tmp/xauth_*
# "r!" above means to remove the files if existent (r), but only at boot (!).
# tmpfiles.d/tmp.conf declares a periodic cleanup of old /tmp/ files, which
# would ordinarily result in the deletion of our xauth files. To prevent that
# from happening, explicitly tag these as X (ignore).
X       /tmp/plasmalogin-auth*
X       /tmp/xauth_*

The creation of directories, including the setting of correct permissions, is possible. But I cannot find how we could deal with the (not / only at boot) cleaning of specific /tmp files.

As a result, I have kept the upstream tmpfiles configuration.

(The sysusers we also keep, because we want a static user with not-changing UID and home dir - not a new random user every time the service is started).

I hope this explains the decision. I am open to hearing any alternative suggestions, and thanks for bringing this up!

peregrinus commented on 2025-12-27 05:54 (UTC) (edited on 2025-12-29 17:52 (UTC) by peregrinus)

Great idea, thanks! I'll add it to my ToDo!

Edit: I saw that upstream provides tmpfiles + sysuser, and decided to go with those.

gdamjan commented on 2025-12-26 20:35 (UTC)

instead of tmpfiles creating /var/lib/plasmalogin and /run/plasmalogin, another approach is to have them in the .service file as StateDirectory=plasmalogin and RuntimeDirectory=plasmalogin (and the coresponding RuntimeDirectoryMode=, StateDirectoryMode=)

this way the existence of the directories is more naturally tied to the runtime of the service, ie. when the service is started they'll exist even without triggering tmpfiles. Also runtime dir. will be cleared on restarts, stops.

techmanwalker commented on 2025-12-19 19:08 (UTC)

It builds fine for me, you may want to unflag this as outdated by bumping the pkgrel now

mblumenstingl commented on 2025-12-12 15:12 (UTC)

@smirky please try again, I think this was fixed upstream with https://invent.kde.org/plasma/plasma-login-manager/-/commit/24ef88c788b3138b4b52a47f5f5cee780ddace7f

smirky commented on 2025-11-27 18:42 (UTC) (edited on 2025-11-27 18:42 (UTC) by smirky)

I can't build it using this PKGBUILD.

-- Autodetected UID_MIN=1000 from /etc/login.defs
-- Autodetected UID_MAX=60000 from /etc/login.defs
CMake Error at data/CMakeLists.txt:42 (message):
  Unknown operating system detected!

  No provided PAM configuration files exist for OS ID 'arch' or its ID_LIKE
  ''.

  Please re-run with '-DINSTALL_PAM_CONFIGURATION=BOOL:OFF' and provide your
  own PAM configuration.


-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: plasma-login-manager-git-exit status 4

arojas commented on 2025-08-25 11:31 (UTC)

@Fohqul no, that is already handled by pacman hooks.

1 2 Next › Last »