X11 Remnant | Will they be removed?

Hello! I have eagerly welcomed KDE Plasma 6.8.0. Finally, it was made possible for us.
Thank you Tumbleweed team!

With 6.8.0 arrival, I hoped the X11 remants would also be freed up. Maybe it’s too early, maybe they are still needed, but as an exclusive user of Wayland for many years, I would be interested in removed as dependencies. I see them as unnecessary old legacy and moreover possibly security issue.

This is a short list X11 remants i could gather. Of course, there are others remant as well.

i  | xsettingsd                                 | Provides settings to X11 applications                                            | package
i  | xdpyinfo                                   | Utility to display information about an X server                                 | package
i  | xprop                                      | Property displayer for X                                                         | package
i  | xrdb                                       | X server resource database utility                                               | package
i  | xsetroot                                   | Utility to set X root window parameter                                           | package
i  | xsettingsd                                 | Provides settings to X11 applications                                            | package
i  | libXss1                                    | X11 Screen Saver extension client library                                        | package
i  | libxkbfile1                                | X11 keyboard file manipulation library                                           | package
i  | libxkbcommon-x11-0                         | Library for handling xkb descriptions using XKB-X11                              | package
i  | libXinerama1                               | Xinerama extension to the X11 Protocol                                           | package
i  | libXfixes3                                 | X11 miscellaneous "fixes" extension library                                      | package
i  | libXext6                                   | Common extensions to the X11 protocol                                            | package
i  | libXau6                                    | X11 authorization protocol library                                               | package
i  | libxcb-composite0                          | X11 Composite Extension C library                                                | package
i  | libxcb-cursor0                             | XCB cursor library (libxcursor port)                                             | package
i  | libxcb-damage0                             | X11 Damage Extension C library                                                   | package
i  | libxcb-dri3-0                              | X11 DRI3 Extension C library                                                     | package
i  | libxcb-glx0                                | X11 GLX Extension C library                                                      | package
i  | libxcb-icccm4                              | XCB utility module for client- and WM-side ICCCM helpers                         | package
i  | libxcb-image0                              | XCB utility module for XImage/XShmImage-like functions                           | package
i  | libxcb-keysyms1                            | XCB utility module for X keycode constants and conversions                       | package
i  | libxcb-present0                            | X11 Present Extension C library                                                  | package
i  | libxcb-randr0                              | X11 RandR Extension C library                                                    | package
i  | libxcb-render0                             | X11 Render Extension C library                                                   | package
i  | libxcb-res0                                | X11 Resource Extension C library                                                 | package
i  | libxcb-shape0                              | X11 Shape Extension C library                                                    | package
i  | libxcb-shm0                                | X11 Shared Memory Extension C library                                            | package
i  | libxcb-sync1                               | X11 Sync Extension C library                                                     | package
i  | libxcb-xfixes0                             | X11 Xfixes Extension C library                                                   | package
i  | libxcb-xinput0                             | X11 XInput Extension C library                                                   | package
i  | libxcb-xkb1                                | X11 Keyboard Extension C library                                                 | package
i  | libxcb1                                    | X11 core protocol C library                                                      | package
i  | libXcomposite1                             | X11 protocol Composite extension client library                                  | package
i  | libX11-6                                   | Core X11 protocol client library                                                 | package
i  | libva-x11-2                                | X11 backend for the Video Acceleration API                                       | package
i  | libICE6                                    | X11 Inter-Client Exchange Library                                                | package
i  | libfontenc1                                | X11 font encoding library                                                        | package
---
i  | xwayland                                   | Xwayland Xserver                                                                 | package

What will their status be going forward?

1 Like

Just leave them be. Imagine there are a lot of applications ( f.e. browsers ) that are not changed to wayland-only.

3 Likes

Not sure what your concern is really.

It depends on the dependencies of installed applications and toolkits that may still be required. So even if Plasma Wayland doesn’t require them, individual third-party applications (eg Spotify, older IDEs or games) may still depend on X11 libraries. Some games and applications running via Steam, Proton or Wine may also rely on X11.

XWayland remains useful for running X11 applications in a Wayland session, for a start. A fair number of users probably still rely on that.

You can investigate the dependencies of the above list of packages for yourself…
zypper se --requires-pkg <package-name>
rpm -q --whatrequires <package-name>

6 Likes

Thank you for the explanations,

My Tumbleweed is installed almost from scratch with 200+ packages years ago, so i did with KDE Plasma pretty much minimal wayland only.

Simply i just want to have as few packages as possible. I do not see them as necessary for the applications i have installed.

But your clarification is understandable, some apps or 3rd parts may require those.

I’ll check @deano_ferrari commands, I am sure they are still necessary for the system or apps, otherwise zypper pa --unneeded and zypper pa --orphaned would have listed them as unnecessary.

@x0r:

Despite my “thumbs up” support to the previous posts here, here’s my zypper log entries for a few things that I’ve kicked out of this fairly new Tumbleweed system upgraded from a years and years old Leap and pre-Leap system:

2026-10-07 09:48:47|remove |twm|1.0.13.1-1.6|x86_64|root@???|
2026-10-07 09:49:25|remove |icewm-lang|4.1.0-1.1|noarch|root@???|
2026-10-07 09:49:25|remove |xclock|1.2.1-1.2|x86_64||
2026-10-07 09:49:25|remove |xscreensaver-lang|6.16-1.1|noarch||
2026-10-07 09:49:25|remove |icewm|4.1.0-1.1|x86_64|root@???|
2026-10-07 09:49:26|remove |xscreensaver|6.16-1.1|x86_64||
2026-10-07 09:49:26|remove |icewm-default|4.1.0-1.1|x86_64|root@???|
2026-10-07 09:49:27|remove |xscreensaver-data|6.16-1.1|x86_64||
2026-10-07 09:49:27|remove |icewm-theme-branding|1.2.6-2.3|noarch|root@???|
2026-10-07 09:52:58|remove |xclip|0.13+git20220129-1.7|x86_64|root@???|
2026-10-07 09:53:34|remove |xdmbgrd|0.8-2.9|x86_64|root@???|
2026-10-07 09:59:37|remove |xterm|410-1.3|x86_64|root@???|

Removing TWM and IceWM with “clean-deps” got rid of the SDDM login screen’s Window Manager choices.
“xdmbgrd” and “xterm” were two other X11 artifacts which didn’t have any remaining dependencies.

AFAICS, this system is now pretty much “Wayland-only” … :sunglasses:

1 Like

@x0r:

There is one thing I forgot to mention and, it doesn’t really matter because, with KDE Plasma version 6.8 it’s disappeared anyway –

2026-08-12 16:16:44|command|root@???|'zypper' 'remove' '--clean-deps' 'plasma6-session-x11'|
# 2026-08-12 16:16:44 plasma6-session-x11-6.7.4-1.1.x86_64 removed ok
# Additional rpm output:
# update-alternatives: warning: alternative /usr/share/xsessions/plasma6.desktop (part of link group default-xsession.desktop) doesn't exist; removing from list of alternatives
# update-alternatives: warning: /etc/alternatives/default-xsession.desktop is dangling; it will be updated with best choice
# update-alternatives: using /usr/share/xsessions/icewm-session.desktop to provide /usr/share/xsessions/default.desktop (default-xsession.desktop) in auto mode
# 
2026-08-12 16:16:44|remove |plasma6-session-x11|6.7.4-1.1|x86_64|root@???|
2026-08-12 16:17:22|command|root@???|'zypper' 'remove' '--clean-deps' 'plasma6-session-x11-debuginfo'|
2026-08-12 16:17:22|remove |plasma6-session-x11-debuginfo|6.7.4-1.1|x86_64|root@???|
2026-08-12 16:17:22|remove |plasma6-workspace-debugsource|6.7.4-1.1|x86_64||
2026-08-12 16:17:22|remove |plasma6-workspace-debuginfo|6.7.4-1.1|x86_64||
2026-08-12 16:18:05|command|root@???|'zypper' 'install' 'plasma6-workspace-debuginfo'|
2026-08-12 16:18:06|install|plasma6-workspace-debugsource|6.7.4-1.1|x86_64||openSUSE:repo-oss-debug|***|
2026-08-12 16:18:08|install|plasma6-workspace-debuginfo|6.7.4-1.1|x86_64|root@???|openSUSE:repo-oss-debug|***|

Yes, it has really disappeared from the openSUSE repositories: <plasma6-session-x11>

More information here:

How did you set sddm to use wayland instead of X11 for the login?

I have /etc/sddm.conf.d/10-wayland.conf with the following config…

[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell


[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1

This configures SDDM itself to use Wayland for the login greeter, rather than X11, but make sure that you are using the native sddm.service (and not display-manager-legacy.service).

1 Like

This file comes with the installation of package sddm-config-wayland

And the package description tells clearly:

This package adds a config file to let SDDM run with wayland as backend
instead of X11.

2 Likes

I didn’t; the standard openSUSE Tumbleweed configuration provides everything that’s needed.


The sddm.conf man (5) page:

   /usr/lib/sddm/sddm.conf.d
          System configuration directory
 > ls /usr/lib/sddm/sddm.conf.d/
00-general.conf  10-plasma.conf  10-theme.conf  11-kwin_wayland.conf  20-breeze-openSUSE.conf
 > 
 > grep -i 'wayland' /usr/lib/sddm/sddm.conf.d/*
/usr/lib/sddm/sddm.conf.d/10-plasma.conf:DefaultSession=/usr/share/wayland-sessions/plasmawayland.desktop
/usr/lib/sddm/sddm.conf.d/10-plasma.conf:GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell
/usr/lib/sddm/sddm.conf.d/10-plasma.conf:[Wayland]
/usr/lib/sddm/sddm.conf.d/10-plasma.conf:CompositorCommand=kwin_wayland --no-global-shortcuts --no-lockscreen --locale1
/usr/lib/sddm/sddm.conf.d/11-kwin_wayland.conf:GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell
/usr/lib/sddm/sddm.conf.d/11-kwin_wayland.conf:[Wayland]
/usr/lib/sddm/sddm.conf.d/11-kwin_wayland.conf:CompositorCommand=kwin_wayland --no-global-shortcuts --no-lockscreen --locale1
 > 
 > cat /usr/lib/sddm/sddm.conf.d/10-plasma.conf 
[General]
DefaultSession=/usr/share/wayland-sessions/plasmawayland.desktop
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

[Theme]
Current=breeze-openSUSE
CursorTheme=breeze_cursors

[Wayland]
CompositorCommand=kwin_wayland --no-global-shortcuts --no-lockscreen --locale1
 > 
 > cat /usr/lib/sddm/sddm.conf.d/11-kwin_wayland.conf 
[General]
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

[Wayland]
# --locale1 was introduced in kwin 5.27
CompositorCommand=kwin_wayland --no-global-shortcuts --no-lockscreen --locale1
 > 
 > rpm --query --whatprovides /usr/lib/sddm/sddm.conf.d/10-plasma.conf 
sddm-qt6-branding-openSUSE-6.8.0-1.1.x86_64
 > 
 > rpm --query --whatprovides /usr/lib/sddm/sddm.conf.d/11-kwin_wayland.conf 
sddm-branding-openSUSE-0.21.0+git57-1.1.noarch
 > 

But, thinks to Hui, I’ve now noticed the SDDM Wayland configuration package – which seems to be not installed by default … :unamused:

 > rpm -ql sddm-config-wayland 
/usr/lib/sddm/sddm.conf.d/11-wayland.conf
/usr/share/licenses/sddm-config-wayland
/usr/share/licenses/sddm-config-wayland/LICENSE
 > rpm --query --whatprovides /usr/lib/sddm/sddm.conf.d/11-wayland.conf
sddm-config-wayland-1.0-1.3.noarch
 > 
 > diff -cw /usr/lib/sddm/sddm.conf.d/11-wayland.conf /usr/lib/sddm/sddm.conf.d/11-kwin_wayland.conf
*** /usr/lib/sddm/sddm.conf.d/11-wayland.conf   2025-12-21 20:34:12.000000000 +0100
--- /usr/lib/sddm/sddm.conf.d/11-kwin_wayland.conf      2026-08-02 12:11:23.000000000 +0200
***************
*** 1,2 ****
  [General]
! DisplayServer=wayland
--- 1,6 ----
  [General]
! GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell
! 
! [Wayland]
! # --locale1 was introduced in kwin 5.27
! CompositorCommand=kwin_wayland --no-global-shortcuts --no-lockscreen --locale1
 >

I’ll remove the package “sddm-config-wayland” → having the SDDM configuration parameter “DisplayServer” set to the value “wayland” results in nice big fonts on the login greeter but, the login greeter isn’t running on a VT.

And, if you have multiple users on the system, when you logout from one of the other user sessions, the screen remains black and <ctrl-alt-F1 … F12> to another user session doesn’t do anything until the following System Request is executed: → “Kill all the processes related to the current Terminal” … :unamused:

Hello! Thanks for your suggestion. I never had any of those, i installed my Tumbleweed minimally from TTY also built KDE minimally aswell. No Xorg or X11 from me, but some X11 tails are in Wayland session, and i wanted to know if they would be removed, though it’s understandable that it’s too soon yet for them for reasons cited above. I don’t use login manager, i am a single user, run startplasma-wayland from an auto script.

I have been KDE Wayland standalone for about 3 years, if KDE removed X11 session now personally, I did it earlier. Of course, also thanks to the Tumbleweed console capability, where one can build it more or less like in Arch.

“sddm-config-wayland” This is a problematic package. I also removed the package after experiencing the issues you mention. :frowning_face: Are there any additional steps one should take after the removal of this package?

After restarting the Display Manager systemd service, I haven’t seen any other issues – to date I haven’t cleaned out the ~sddm/.cache/ directory but, that may well change … :thinking:

On my Slowroll system, I use SDDM Wayland but have never installed the sddm-config-wayland package. Just the minimal manual config as described already.

sddm-config-wayland seems to add /usr/lib/sddm/sddm.conf.d/11-wayland.conf

You mention the override file /etc/sddm.conf.d/10-wayland.conf which has a different number.

How do I check if I use the native sddm.service? When fiddling with the wayland.conf files in a VM I’m always greeted by tty during next bootup.

systemctl status sddm.service

1 Like

Thanks!

Guess this is the native service but still no luck with the config files.

systemctl status sddm.service
○ sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; disabled; preset: disabled)
Active: inactive (dead)
Docs: man:sddm(1)
man:sddm.conf(5)

The last time I checked, if you do nothing beyond installing tumbleweed, with Plasma selected as the desktop, and then run sudo systemctl enable --now --force sddm.service sddm will run as a wayland client, you don’t need to touch anything else, don’t have to write any config files.

That’s been a few months ago now, as I don’t actually use tumbleweed directly for anything, so it may have changed in 6.8, but I’ve not seen any major changes to the sddm package recently.

3 Likes