[Stable Update] 2026-02-01 - Kernels, COSMIC, Plasma, GNOME, Mesa

Announcements Stable Updates
28

It should be noted though that Plasma Login Manager in its current state is not on par with SDDM. There seem to be a couple of features missing, e.g. the ability to hide certain users (see https://bugs.kde.org/show_bug.cgi?id=515108).

29

:backhand_index_pointing_up: There’s the problem.

You should update, then install it manually, then go from there.

2 Likes
30

Well, it still hasn’t even been released yet, so that would make sense.

1 Like
31

OK, i did the update (no rebooting yet) and that’s the result:

marc@marc-pc ~]$ sudo pacman -Syu plasma-login-manager
[sudo] Mot de passe de marc : 
:: Synchronisation des bases de données de paquets

 core est Ă  jour
 extra est Ă  jour
 multilib est Ă  jour
:: DĂ©but de la mise Ă  jour complĂšte du systĂšme

résolution des dépendances

recherche des conflits entre paquets


Paquets (1) plasma-login-manager-6.5.91-1

Taille totale du téléchargement :  0,51 MiB
Taille totale installée :          1,65 MiB

:: ProcĂ©der Ă  l’installation ? [O/n] 
:: Récupération des paquets

 plasma-login-manager-6.5.91-1-x86_64      519,1 KiB  7,92 MiB/s 00:00 [########################################] 100%
(1/1) vérification des clés dans le trousseau                          [########################################] 100%
(1/1) vĂ©rification de l’intĂ©gritĂ© des paquets                          [########################################] 100%
(1/1) chargement des fichiers des paquets                              [########################################] 100%
(1/1) analyse des conflits entre fichiers                              [########################################] 100%
(1/1) vĂ©rification de l’espace disque disponible                       [########################################] 100%
:: Traitement des changements du paquet

(1/1) installation de plasma-login-manager                             [########################################] 100%
:: ExĂ©cution des crochets (« hooks ») de post-transaction

(1/7) Creating system user accounts...
Creating group 'plasmalogin' with GID 967.
Creating user 'plasmalogin' (PLASMALOGIN Greeter Account) with UID 967 and GID 967.
(2/7) Reloading system manager configuration...
(3/7) Reloading user manager configuration...
(4/7) Creating temporary files...
(5/7) Arming ConditionNeedsUpdate...
(6/7) Reloading system bus configuration...
(7/7) Updating the desktop file MIME type cache...
[marc@marc-pc ~]$ systemctl disable sddm
Failed to disable unit: Access denied
[marc@marc-pc ~]$
32

Then why advise users to migrate? At least add a note regarding PLM’s beta status.

33

remember to use sudo with commands that modify the system. So:

sudo systemctl disable sddm
sudo systemctl enable plasmalogin
1 Like
34

Arf, obviously

Thanks, it works!

I reboot now
 :worried:

Edit: it’s ok after reboot! :wink:

35

There was nothing of the sort. It was just mentioned that it was possible, that you can if you wanted to:

Also, there are many posts regarding plasma login manager where it’s explicitly stated that it’s still a work in progress and that the official launch is only later this month.

2 Likes
36

I didn’t use sudo but it worked well.

1 Like
37

I think some settings (such as wallpaper) can be handled with system settings > login screen.

38

Today I discovered that it is not possible to search in whatever forum software this is, if the search term is too short. So I am unable to search for “vi” in this thread, to see if anyone else is having pamac threaten to remove vi, for conflicting with “ex-vi-compat”?

Edit: Found relevant thread: [SOLVED] why vi is now suggested to be replaced with ex-vi-compat ? / Pacman & Package Upgrade Issues / Arch Linux Forums

39

There was a discussion in Testing Updates recently:

After checking that I didn’t need the vi/vim/ex-vi-compat packages for anything (I use meld instead of vim for pacdiff), I removed the 3 packages without any issues:

[2026-01-27T12:17:03+1100] [ALPM] removed ex-vi-compat (1-3)
[2026-01-27T12:17:03+1100] [ALPM] removed vim (9.1.2077-1)
[2026-01-28T20:54:11+1100] [ALPM] removed vim-runtime (9.1.2077-1)
41

all went well, except after logging in, Wellcome screen and Solaar window have reset properties. They do now open under current mouse cursor position instead of specifically giver properties in KDE Plasma window “Special application settings”
But this is more of KDE Plasma thing to remember, where the window was last time opened.

42

How do I enable Cosmic on an existing installation?

43

Just one minor problem; radicale wouldn’t start after the upgrade. Fixed by reinstalling radicale-infcloud-git.

1 Like
44

Since last night’s update, I’ve been getting the following error in Docker Desktop: qemu: process terminated unexpectedly: signal: aborted (core dumped)
I can launch Docker Desktop, but it crashes after a few minutes.

45

I suppose a window opened (or a text prompt) and asked you for your password. polkit can substitute sudo in some cases. But if polkit is not available for some reason (as seems to be the case of the user I was helping to) then you must use sudo. Also there are actions that can’t be done with polkit. Try for example: touch /etc/test.txt

2 Likes
46

If you are on GNOME atm it is quite easy, as both DEs are not interfering each other:

  • install the needed COSMIC packages, e.g. via “sudo pacman -Syu cosmic-session” or via the pamac-gui. This will install the needed additional apps as well.
  • logout and select “cosmic” at the login screen instead of GNOME
  • install additional cosmic apps that might exist on top of the default installation

I am not using KDE, so I have no clue if Cosmic and KDE are able to be installed without issues in parallel. With GNOME it seems to work quite well, it is installed on one of my notebooks since November 25 or so, I did switch back to Gnome as my daily driver without any issues and from time to time I am taking a look into cosmic.

Please also read here:

1 Like
"Install Desktop Environments" Wiki page outdated
47

Hello can’t update, an idea ?

error: failed retrieving file 'ca-certificates-mozilla-3.120-1-x86_64.pkg.tar.zst.sig' from ftp.cc.uoc.gr : The requested URL returned error: 503
error: failed retrieving file 'lib32-curl-8.18.0-4-x86_64.pkg.tar.zst.sig' from ftp.cc.uoc.gr : The requested URL returned error: 503
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.

EDIT: It was the mirrors


48

The wording could certainly have been better, though. I too interpreted this to be a recommendation or even a necessary step.

Something along the lines of “users now have the option to migrate to the new Plasma Login Manager (currently beta)” would’ve been much more fitting.

2 Likes