XFCE on wayland

Hello! I have xfce desktop manager. Is it possible to run it on wayland?

Mariusz

System:
  Kernel: 6.1.31-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
    root=UUID=b8c044ba-3855-4296-80c1-38218b0791fd rw rootflags=subvol=@
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3 ibt=off
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
    v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0 Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Compulab model: fitlet2 v: 1.31
    serial: <superuser required> UEFI: American Megatrends
    v: FLT2.TPM.0.46.02.01 date: 05/24/2021
CPU:
  Info: model: Intel Atom E3950 bits: 64 type: MCP arch: Goldmont level: v2
    built: 2016 process: Intel 14nm family: 6 model-id: 0x5C (92) stepping: 9
    microcode: 0x48
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 224 KiB
    desc: d-4x24 KiB; i-4x32 KiB L2: 2 MiB desc: 2x1024 KiB
  Speed (MHz): avg: 1992 min/max: 800/2000 scaling: driver: intel_cpufreq
    governor: schedutil cores: 1: 1992 2: 1992 3: 1992 4: 1992 bogomips: 12752
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Apollo Lake [HD Graphics 505] driver: i915 v: kernel
    arch: Gen-9 process: Intel 14n built: 2015-16 ports:
    active: HDMI-A-1,HDMI-A-2 empty: DP-1 bus-ID: 00:02.0 chip-ID: 8086:5a84
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
    s-diag: 1055mm (41.54")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary,left model: HP 25es
    serial: <filter> built: 2017 res: 1920x1080 hz: 60 dpi: 88 gamma: 1.2
    size: 553x309mm (21.77x12.17") diag: 633mm (24.9") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: right model: HP 25es
    serial: <filter> built: 2018 res: 1920x1080 hz: 60 dpi: 88 gamma: 1.2
    size: 553x309mm (21.77x12.17") diag: 633mm (24.9") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 23.1.1 renderer: Mesa Intel HD Graphics 505 (APL
    3) direct-render: Yes
Audio:
  Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl, snd_soc_avs,
    snd_sof_pci_intel_apl bus-ID: 00:0e.0 chip-ID: 8086:5a98 class-ID: 0403
  API: ALSA v: k6.1.31-1-lts status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 0.3.71 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: Intel I211 Gigabit Network driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 8086:1539
    class-ID: 0200
  IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel I211 Gigabit Network driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 02:00.0 chip-ID: 8086:1539
    class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-3: Intel I211 Gigabit Network driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: c000 bus-ID: 03:00.0 chip-ID: 8086:1539
    class-ID: 0200
  IF-ID-1: eno1 state: down mac: <filter>
Drives:
  Local Storage: total: 119.24 GiB used: 25.96 GiB (21.8%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: BIWIN model: SSD size: 119.24 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
    serial: <filter> fw-rev: 2A scheme: GPT
Partition:
  ID-1: / raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 25.96 GiB (21.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 25.96 GiB (21.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 25.96 GiB (21.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 25.96 GiB (21.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 7.4 GiB used: 19 MiB (0.3%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 51.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 248 Uptime: 6h 5m wakeups: 0 Memory: available: 7.4 GiB
  used: 2.98 GiB (40.2%) Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 13.1.1 Packages: pm: pacman pkgs: 1514
  libs: 419 tools: pamac,paru Shell: Bash v: 5.1.16 running-in: xfce4-terminal
  inxi: 3.3.27
Garuda (2.6.16-1):
  System install date:     2023-03-10
  Last full system update: 2023-05-31 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:            

Whoogle say, no.

3 Likes

Hey Colin! Thank you, this is good news. Will keep an eye on xfce 4.20.

2 Likes

Here is the roadmap if you are curious: releng:wayland_roadmap [Xfce Wiki]

It's a lot of work ahead and it's fully decided yet if they will actually transition to Wayland or not, but their notes seem thoughtful and reasonable in my opinion. I hope they succeed! :slightly_smiling_face:

3 Likes

Hope so too! Thanks for the roadmap link.

hey bluishhumility if you don't mind me asking how do you keep yourself update with linux news? I am talking about stuff like broken packages, up and coming new features and things like that. I earlier thought that archlinux would post that if a certain package was broken in their repos but that doesn't seem to be the case. Is the only solution to visit the dev site for each individual package we use or is there some consolidated site that publishes news for all this stuff like broken package updates, new up and coming development and stuff like that.

Mostly I just read a lot, in this and a few other forums. If I am researching an issue, I might end up reading through a bug tracker or blog or something, but I generally don't seek out resources like that unless they are related to something I am trying to learn more about. Most things I learn about just from browsing through the forums and reading through new topics.

2 Likes