Manjaro is deleting Xorg from my system

Context

I just happened to reinstall my system from scratch last week. And I made sure that Xorg was installed and selected under Settings > SDDM > Behaviour, because I remember this now being a choice due to this issue I had, where Xorg had been deleted from my 2 long-term set-up’s and I had to reinstall Xorg.

Issue

I was actually going to say that KDE had changed Xorg to Wayland on reboot, but after a screenshot, I can see that Xorg has been deleted again upon update or reboot.

image

So, I opened another thread with them, because I thought it was a slightly different issue, but it is not and that’s when a KDE developer told me to check with Manjaro. Also, I remember that I had another thread for this here in Manjaro, so I am just now going back and forth between the two forums and the issue keeps resurfacing.

Environment

I am in the testing branch
Manjaro 25.1.0
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.1.158-2-MANJARO (64-bit)

Since Plasma 6.4 the wayland session will be the only one installed when the users does not manually specify kwin-x11.

With the split of kwin into kwin-wayland and kwin-x11, users running the old X11 session needs to manually install plasma-x11-session, or they will not be able to login. Currently pacman is not able to figure out your personal setup, and it wouldn’t be ok to install plasma-x11-session and kwin-x11 for every one using Plasma.

tldr: Install plasma-x11-session if you are still using x11

3 Likes

@dmt said in the old thread that

X11 is no longer installed by default for new installs. An update shouldn’t remove valid packages unless there’s a conflict. :man_shrugging:

But this new install with the latest KDE ISO downloaded from the Manjaro site about a week ago had Xorg installed in it and it has been deleted after a reboot today.

Again, I checked after the fresh system install, because I use Xorg and it was there. And now, it has been uninstalled as you can see in the screenshot. This is not the first time that I am running into this issue.

Nope - nothing has been uninstalled - the ability to run an x11 session was part of Plasma session but has been removed by upstream KDE Plasma.

On Plasma 6.4 the wayland session will be the only one installed when the users does not manually specify kwin-x11.

With the recent split of kwin into kwin-wayland and kwin-x11, users running the old X11 session needs to manually install plasma-x11-session, or they will not be able to login. Currently pacman is not able to figure out your personal setup, and it wouldn’t be ok to install plasma-x11-session and kwin-x11 for every one using Plasma.

tldr: Install plasma-x11-session if you are still using x11

Arch Linux - News: Plasma 6.4.0 will need manual intervention if you are on X11

What you see is a consequence of changes in Plasma - and when you switch branch from stable to testing - you jump from Plasma 6.3.6 to Plasma 6.5.3 - there fore you are affected and you must manually install the x11-session

sudo pacman -S plasma-x11-session
2 Likes

Alright, but it was already installed. I checked right after installing the system, because I need it for my set-up and I know that this was now a choice and it had already disappeared once from two systems. So, this is now the third time that moving plasma versions has uninstalled plasma-x11-session.

Did you try installing it?

Is your system fully synchronised?

I would suggest this may be better?:

sudo pacman -Syu plasma-x11-session

As I just said, it was already installed and I checked and this is the third system where this has happened.

Try simply responding to the post. I modified to -Syu to ensure synchronisation before installing.

After this, it will be installed and never uninstalled without you saying so.

I used Plasma for 9 years, it is still installed.

The only time you will experience the removal of the session option in sddm for launching an x11 session, is when you switch from stable to testing.

I think you confuse the option in sddm with the actual package - because a package explicitly installed by the user will not get removed on updates.

Plasma used to provide a launcher in /usr/share/xsessions and that launcher was part of a plasma package so it will be removed when that package is upgraded.

6 Likes

@Centaro it is simple. With Plasma release 6.4 the X11 files got split out. So if you regular update your system from 6.3 series, which still shipped the files in kwin and plasma-session packages and you didn’t install plasma-x11-session, which is a new package the X11 session won’t be available. Upstream Arch decided not to provide meta packages which would also install those new split packages.

New ISOs will provide Wayland only Plasma with 25.1 release of Manjaro Linux. Same goes for the GNOME edition. Only XFCE will default to X11 still and will ship it on the upcoming release of Manjaro.

3 Likes

Oh, got you, @linux-aarhus. That’s the whole issue. Thank you for pointing out the confusion. As always, on point.

Indeed, /usr/share/xsessions is now an empty directory.

drwxr-xr-x 0 root 24 Nov 23:04 xsessions/

Thank you @philm for the extra bits.

I does not exist at the official stable repros

sudo pacman -Syu plasma-x11-session
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
error: target not found: plasma-x11-session

It seems to be in the AUR only, but which one is the correct choice (if at all)?

pamac build plasma-x11-session
Preparing...
Checking plasma-x11-session-sonic-bin dependencies...
Checking plasma-x11-session-lite-bin dependencies...
Checking plasma-x11-session-sonic dependencies...
Checking plasma-workspace-sonic dependencies...
Checking kwin-x11-sonic dependencies...
Checking libplasma-git dependencies...
Checking plasma-activities-git dependencies...
Checking kcmutils-git dependencies...
Checking kcolorscheme-git dependencies...
Checking kconfig-git dependencies...
Checking kcoreaddons-git dependencies...
Checking kglobalaccel-git dependencies...
Checking ki18n-git dependencies...
Checking kiconthemes-git dependencies...
Checking kio-git dependencies...
Checking kirigami-git dependencies...
Checking knotifications-git dependencies...
Checking kpackage-git dependencies...
Checking ksvg-git dependencies...
Checking kwidgetsaddons-git dependencies...
Checking kwindowsystem-git dependencies...
Checking extra-cmake-modules-git dependencies...
Checking kdoctools-git dependencies...
Checking plasma-wayland-protocols-git dependencies...
Checking kconfigwidgets-git dependencies...
Checking kguiaddons-git dependencies...
Checking kitemviews-git dependencies...
Checking kservice-git dependencies...
Checking kxmlgui-git dependencies...
Checking karchive-git dependencies...
Checking kauth-git dependencies...
Checking kbookmarks-git dependencies...
Checking kcompletion-git dependencies...
Checking kcrash-git dependencies...
Checking kdbusaddons-git dependencies...
Checking kjobwidgets-git dependencies...
Checking kwallet-git dependencies...
Checking solid-git dependencies...
Checking kcodecs-git dependencies...
Checking polkit-qt6-git dependencies...
Choose a provider for plasma-x11-session:
1:  plasma-x11-session-lite-bin   6.5.3-1    AUR
2:  plasma-x11-session-sonic      6.5.3-2    AUR
3:  plasma-x11-session-sonic-bin  6.5.3-2.4  AUR

Enter a number (default=1): 

Please clarify @linux-aarhus @Ben

The first Linux EOL in the history !! https://youtu.be/xzYGg5hhiWo

This package is only in unstable and testing:

Since you are on stable branch (according to your profile) there is no package of that name.

Installing from the AUR at this time would not be advisable when on stable.

What would be the point of installing the plasma-x11-session on stable when there is x11 support still on stable?

4 Likes

My bad, I wasn’t aware that it is still supported on stable.

Thank you.

OK - that is understandable - just to be crystal clear

Given the reference to Arch Linux announcement and

I thought I made it very clear, the x11 session launcher is default present on stable but removed on testing (/usr/share/xsessions/plasma.desktop) because the plasma-workspace package no longer provides the launcher.

2 Likes

Clearer than that, you stated:

a package explicitly installed by the user will not get removed on updates.

This is what confused me, as x11 was never removed for me… this could be answered with pacman -Qi plasma-x11-session… as mine is explicit, it remained.

Oh - that is understandable - it can be quite confusing…

I don’t recall a package named plasma-x11-session before Plasma 6.4?

May I have you looking at your /var/log/pacman.log - search for plasma-x11-session - see what comes up - I am curios :slight_smile:

The package kwin-x11 which is a dependency of plasma-x11-session where the latter provides a plasmax11.desktop launcher.

The consequence of upstream KDE Plasma splitting of the sessions into x11 and wayland for the workspace.

2 Likes
➤ cat pacman.log | rg plasma-x11
81850 │ [2025-10-18T20:20:36+0700] [PACMAN] Running 'pacman -S --config /etc/pacman.conf -- extra/plasma-x11-session'
81852 │ [2025-10-18T20:20:43+0700] [ALPM] installed plasma-x11-session (6.4.5-3)
81861 │ [2025-10-18T20:20:44+0700] [PACMAN] Running 'pacman -D -q --asdeps --config /etc/pacman.conf -- plasma-x11-session'
82660 │ [2025-10-26T13:39:57+0700] [ALPM] upgraded plasma-x11-session (6.4.5-3 -> 6.5.0-1)
82906 │ [2025-10-26T14:52:34+0700] [ALPM] removed plasma-x11-session (6.5.0-1)
88413 │ [2025-11-29T20:30:56+0700] [PACMAN] Running 'pacman -S --config /etc/pacman.conf -- extra/plasma-x11-session'
88416 │ [2025-11-29T20:31:07+0700] [ALPM] installed plasma-x11-session (6.5.3-2)
88428 │ [2025-11-29T20:31:08+0700] [PACMAN] Running 'pacman -D -q --asexplicit --config /etc/pacman.conf -- plasma-x11-session'

Yup.

That is what happen behind the scene - on upgrade - the package manager remove the previous package then unpack the new package.

Let’s say you got the idea - I switch my system from testing to stable and do a full sync with downgrade.

Then list alien packages

pacman -Qqm

The package plasma-x11-session will appear in that list because it does not exist in the stable branch (time of writing).

Switch the system to unstable and do a full system upgrade - the package will not be removed - and it will no longer be listed as alien.

1 Like