Wayland [Solved]

[jc7006]

Is MxLinux going to stay with x11, or are they eventually going to switch to Wayland. I like X11, Wayland doesn't play well with my computer. 14th Gen Intel Processor. I also have to use the liq. kernel 6.14, my JBL Bluetooth speaker won't work on the 6.1 Kernel. Thanks in advance.

[j2mcgreg]

We need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules

[dolphin_oracle]

Xfce will remain X11 default for now.

KDE may default to wayland, haven't decided yet. but both X11 and wayland options will be available.

fluxbox will always be X11, as I doubt that WM ever gets updated to operate as a wayland compositor.

[AVLinux]

Hi,

If I understand correctly the choice of Wayland or X11 will largely depend on what Debian does upstream and then projects like MX will have to follow suit to some degree. I think we're very fortunate that Debian (and MX) are quite conservative with big changes like this and very careful about burning bridges. Wayland has a a lot of proving itself to do across all workflows even if it is working for general Desktop usage. As an example I primarily use my computers for multimedia production and use Recording programs like Ardour and there are more than a few reports on the Ardour forum of problems when using Wayland for production, many programs are going to rely on 'Xwayland' which adapts programs and applications geared to X11 to work with Wayland and my feeling is there are a lot of hidden bugs yet to show themselves as more and more users either choose Wayland or are forced to by their Distribution. Wayland is inevitable but I think it and especially Xwayland will need a lot more refining before it truly replaces X11 in a way that deeply affects Users. Certainly Trixie has no major changes in this regard and Fluxbox and all other X11 DE's will be alive and well in Trixie.

[asqwerth]

Hi,

If I understand correctly the choice of Wayland or X11 will largely depend on what Debian does upstream .........

I think it depends on the Desktop environment. If XFCE devs don't make XFCE fully Wayland-ready (right now it's only at experimental stage) then people running XFCE will still be on X11.

[jc7006]

Code: Select all

Snapshot created on: 20250515_1636
System:
  Kernel: 6.14.6-1-liquorix-amd64 [6.14-8~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.14.6-1-liquorix-amd64
    root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.5 info: plank wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.6_x64
    Libretto May 15 2025 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: HP product: HP ENVY TE01-5xxx v: N/A serial: <superuser required> Chassis:
    type: 3 serial: <superuser required>
  Mobo: HP model: 8B3B v: A (SMVB) serial: <superuser required> UEFI: AMI v: F.21
    date: 10/24/2023
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510 serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard serial: <filter>
    charge: 50% (should be ignored) rechargeable: yes status: N/A
CPU:
  Info: model: Intel Core i7-14700 bits: 64 type: MST AMCP arch: Raptor Lake gen: core 14 level: v3
    note: check built: 2022+ process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
    microcode: 0x12F
  Topology: cpus: 1x cores: 20 mt: 8 tpc: 2 st: 12 threads: 28 smt: enabled cache: L1: 1.8 MiB
    desc: d-12x32 KiB, 8x48 KiB; i-8x32 KiB, 12x64 KiB L2: 28 MiB desc: 8x2 MiB, 3x4 MiB L3: 33 MiB
    desc: 1x33 MiB
  Speed (MHz): avg: 1373 high: 5212 min/max: 800/2101 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 946 2: 1000 3: 943 4: 802 5: 2211 6: 4507
    7: 5212 8: 800 9: 800 10: 900 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800
    19: 800 20: 1200 21: 900 22: 2101 23: 800 24: 800 25: 3749 26: 1991 27: 800 28: 800
    bogomips: 118272
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional; PBRSB-eIBRS: SW
    sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Raptor Lake-S GT1 [UHD Graphics 770] vendor: Hewlett-Packard driver: i915
    v: kernel alternate: xe arch: Gen-13 process: Intel 7 (10nm) built: 2022+ ports: active: HDMI-A-1
    empty: DP-1 bus-ID: 00:02.0 chip-ID: 8086:a780 class-ID: 0300
  Device-2: Logitech HD Webcam C615 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-1:2
    chip-ID: 046d:082c class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: HP 27xw serial: <filter> built: 2015 res: 1920x1080
    hz: 60 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 24.2.8-1mx23ahs renderer: Mesa Intel Graphics (RPL-S)
    direct-render: Yes
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
    bus-ID: 1-1:2 alternate: snd_soc_avs,snd_sof_pci_intel_tgl chip-ID: 046d:082c class-ID: 0e02
    bus-ID: 00:1f.3 chip-ID: 8086:7ad0 serial: <filter> class-ID: 0403
  Device-2: Logitech HD Webcam C615 type: USB driver: snd-usb-audio,uvcvideo
  API: ALSA v: k6.14.6-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard RTL8111/8168/8411 driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: 4000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8852BE PCIe 802.11ax Wireless Network vendor: Hewlett-Packard
    driver: rtw89_8852be v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000
    bus-ID: 02:00.0 chip-ID: 10ec:b852 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-14:7
    chip-ID: 0bda:b85c class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 842d hci-v: 5.2 rev: 474
  Info: acl-mtu: 1021:6 sco-mtu: 255:12 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
Drives:
  Local Storage: total: 953.87 GiB used: 18.14 GiB (1.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SanDisk model: SK hynix BC901 HFS001TEJ9X108N
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: HPS2 temp: 33.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 953.62 GiB size: 937.58 GiB (98.32%) used: 18.14 GiB (1.9%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 43.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2532 pm: dpkg pkgs: 2524 libs: 1344 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 8
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
    2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Info:
  Processes: 471 Uptime: 1h 58m wakeups: 31 Memory: 15.31 GiB used: 3.72 GiB (24.3%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

[AVLinux]

Hi,

If I understand correctly the choice of Wayland or X11 will largely depend on what Debian does upstream .........

I think it depends on the Desktop environment. If XFCE devs don't make XFCE fully Wayland-ready (right now it's only at experimental stage) then people running XFCE will still be on X11.

Not sure,

That sounds like the tail wagging the dog, I would guess that if Debian as an organization decided that Debian 15 (as an example) was moving to Wayland primarily and dropping Xorg then the DE's would either fall in line and be fully Wayland compliant or they would be obsoleted. Perhaps it's not that cut and dried but it's certainly a grey area of authority. In the end everyone bends the knee to Red Hat's agenda (or forks themselves into a corner) eventually.. We won't know for sure until we get there..

Miracles sometimes happen, MATE resurrected Gnome 2, Trinity resurrected KDE 3. I think there will be a very strong case for keeping X11 around for a very long time in some way or another..

[DeepDayze]

Hi,

If I understand correctly the choice of Wayland or X11 will largely depend on what Debian does upstream .........

I think it depends on the Desktop environment. If XFCE devs don't make XFCE fully Wayland-ready (right now it's only at experimental stage) then people running XFCE will still be on X11.

Not sure,

That sounds like the tail wagging the dog, I would guess that if Debian as an organization decided that Debian 15 (as an example) was moving to Wayland primarily and dropping Xorg then the DE's would either fall in line and be fully Wayland compliant or they would be obsoleted. Perhaps it's not that cut and dried but it's certainly a grey area of authority. In the end everyone bends the knee to Red Hat's agenda (or forks themselves into a corner) eventually.. We won't know for sure until we get there..

Miracles sometimes happen, MATE resurrected Gnome 2, Trinity resurrected KDE 3. I think there will be a very strong case for keeping X11 around for a very long time in some way or another..

While X11 is in maintenance mode upstream and no longer getting any new feature updates aside from security updates, X11 would still need ongoing maintenance from the distro side most likely and think Debian X11 team still up to the task?

[jc7006]

Well if they go Wayland, there won't be much of choices because it looks like everyone else is going to it to. So if they do, guess its back to Apple I go...

[j2mcgreg]

Well if they go Wayland, there won't be much of choices because it looks like everyone else is going to it to. So if they do, guess its back to Apple I go...

Debian's approach has always been tried and true. It would be out of character for them to abandon X11 before Wayland is bullet proof and it's not there yet by a long chalk.