Wayland and x11 config files?

Support KDE Plasma
,
1

What happens to the x11 configs when I use Wayland, they are located under /etc/X11/xorg.conf.d/* and I assume they will continue to be loaded when the system starts.
Should these be removed?

00-keyboard.conf  10-monitor.conf  20-intel.conf

system details

$ inxi -Fxxxz
System:
  Kernel: 6.9.0-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc
  Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A wm: kwin_x11 with: cairo-dock
    vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Dell product: OptiPlex 7040 v: N/A
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: Dell model: 0HD5W2 v: A00 serial: <superuser required> part-nu: 06B9
    uuid: <superuser required> UEFI-[Legacy]: Dell v: 1.11.1 date: 10/10/2018
CPU:
  Info: quad core model: Intel Core i7-6700 bits: 64 type: MT MCP smt: enabled
    arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 3400 min/max: 800/3400 cores: 1: 3400 2: 3400 3: 3400
    4: 3400 5: 3400 6: 3400 7: 3400 8: 3400 bogomips: 54417
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 530 vendor: Dell driver: i915 v: kernel
    arch: Gen-9 ports: active: HDMI-A-1,HDMI-A-3 empty: DP-1, DP-2, DP-3,
    HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:1912 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 23.2.6
    compositor: kwin_x11 driver: X: loaded: intel dri: i965 gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1014x285mm (39.92x11.22")
    s-diag: 1053mm (41.47")
  Monitor-1: HDMI-A-1 mapped: HDMI1 pos: right model: Acer K242HL
    serial: <filter> res: 1920x1080 hz: 60 dpi: 92
    size: 530x300mm (20.87x11.81") diag: 609mm (24") modes: max: 1920x1080
    min: 720x400
  Monitor-2: HDMI-A-3 mapped: HDMI3 pos: primary,left model: Acer K242HL
    serial: <filter> res: 1920x1080 hz: 60 dpi: 92
    size: 530x300mm (20.87x11.81") diag: 609mm (24") modes: max: 1920x1080
    min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast surfaceless: drv: iris x11: drv: iris
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.0.6-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 530 (SKL GT2)
    device-ID: 8086:1912
  API: Vulkan v: 1.3.279 layers: N/A surfaces: xcb,xlib device: 0
    type: integrated-gpu driver: mesa intel device-ID: 8086:1912
Audio:
  Device-1: Focusrite-Novation Focusrite Scarlett 2i2 driver: snd-usb-audio
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-4:3 chip-ID: 1235:8016
    class-ID: fe01
  Device-2: USB MIDI Interface driver: snd-usb-audio type: USB rev: 1.1
    speed: 12 Mb/s lanes: 1 bus-ID: 1-7:5 chip-ID: fc02:0101 class-ID: 0103
  API: ALSA v: k6.9.0-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator
  Server-1: sndiod v: N/A status: off
  Server-2: JACK v: 1.9.22 status: active with: 1: a2jmidid status: active
    2: nsmd status: off
  Server-3: PipeWire v: 1.0.5 status: off with: wireplumber status: off
  Server-4: PulseAudio v: 17.0 status: active with: 1: pulseaudio-alsa
    type: plugin 2: pulseaudio-jack type: module
Network:
  Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b7 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: wireguard1 state: unknown speed: N/A duplex: N/A mac: N/A
Drives:
  Local Storage: total: 1.39 TiB used: 257.05 GiB (18.1%)
  ID-1: /dev/sda vendor: SanDisk model: SDSSDH3 500G size: 465.76 GiB
    speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 20RL scheme: GPT
  ID-2: /dev/sdb vendor: Silicon Power model: SPCC Solid State Disk
    size: 953.87 GiB speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 916a
    scheme: GPT
Partition:
  ID-1: / size: 57.37 GiB used: 30.98 GiB (54.0%) fs: ext4 dev: /dev/sda2
  ID-2: /boot size: 511 MiB used: 171.3 MiB (33.5%) fs: vfat dev: /dev/sda1
  ID-3: /home size: 152.74 GiB used: 62.27 GiB (40.8%) fs: ext4
    dev: /dev/sda3
Swap:
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 34.0 C pch: 49.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB available: 31.11 GiB used: 2.95 GiB (9.5%)
  Processes: 279 Power: uptime: 26m states: freeze,mem,disk suspend: deep
    wakeups: 0 hibernate: platform Init: systemd v: 255 default: graphical
  Packages: pm: pacman pkgs: 1601 Compilers: clang: 17.0.6 gcc: 13.2.1
    Shell: Bash v: 5.2.26 running-in: konsole inxi: 3.3.34
2

They are only relevant when using X11. They are not used with Wayland.

2 Likes
3

Hi @cluster,

What @mithrial said.

However, if there are any custom files you should backup them manually, or delete them manually. files in *.d directories are custom as far as I know and you’ll need to do what you want to do with those files manually.

1 Like
4

Yes, these files are loaded system-wide before SDDM login …
so I suspect these settings are not being unloaded only when using wayland …

5

Unless SDDM still uses X11.

To ensure it’s using Wayland, see:

https://wiki.archlinux.org/title/SDDM#Wayland

1 Like
6

hmm, I have no problems with the previous SDDM settings from x11 (black screen or errors), everything works …
I’ll take a look at 10-wayland.conf again straight away.

This system was always very fast until KDE 6, but now that I’m using wayland it’s just as fast as before with KDE5 … maybe even a little faster.