Xfce (wayland)

General system Newbie
1

so my xcfe4 version is 4.20 , which supposedly support wayland.
now iv’e heard a lot of bad about wayland , but still want to try and see what and what not works .
when i reboot and get to login screen ,i can choose between sessions , xfce4 ( default ) and xfce4 (wayland ) .
when i choose wayland it just goes back to login screen ?
am i missing something ?

specs :

[jp@jp14 ~]$ inxi -Fxxc0z
System:
  Kernel: 6.13.1-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.43 wm: xfwm4 dm: LightDM
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Laptop System: SAMSUNG product: RV410/RV510/S3510/E3510 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: SAMSUNG model: RV410/RV510/S3510/E3510 serial: <superuser required>
    BIOS: Phoenix v: 03UC.P026.20101027.LX date: 10/27/2010
Battery:
  ID-1: BAT1 charge: 34.8 Wh (98.0%) condition: 35.5/44.4 Wh (80.0%)
    volts: 12.4 min: 11.1 model: SAMSUNG Electronics serial: N/A
    status: not charging
CPU:
  Info: dual core model: Celeron T3500 bits: 64 type: MCP arch: Penryn rev: A
    cache: L1: 128 KiB L2: 1024 KiB
  Speed (MHz): avg: 2095 min/max: N/A cores: 1: 2095 2: 2095 bogomips: 8378
  Flags: ht lm nx pae sse sse2 sse3 ssse3
Graphics:
  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Samsung Co
    driver: i915 v: kernel arch: Gen-5 ports: active: LVDS-1,VGA-1
    empty: DP-1,DP-2,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:2a42
  Device-2: Z-Star Micro Webcam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 4-4:3 chip-ID: 0ac8:c33f
  Display: x11 server: X.Org v: 21.1.15 compositor: xfwm4 v: 4.20.0 driver:
    X: loaded: modesetting alternate: fbdev,intel,vesa dri: crocus gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2732x768 s-dpi: 96
  Monitor-1: LVDS-1 pos: primary,left model: Seiko Epson 0x5441
    res: 1366x768 hz: 60 dpi: 101 diag: 395mm (15.5")
  Monitor-2: VGA-1 pos: right model: Samsung S19B300 res: 1366x768 hz: 60
    dpi: 85 diag: 470mm (18.5")
  API: EGL v: 1.5 platforms: device: 0 drv: crocus device: 1 drv: swrast
    gbm: drv: crocus surfaceless: drv: crocus x11: drv: crocus inactive: wayland
  API: OpenGL v: 4.5 compat-v: 2.1 vendor: intel mesa v: 24.3.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Mobile Intel GM45 Express (CTG)
    device-ID: 8086:2a42
  Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 82801I HD Audio vendor: Samsung Co driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e
  API: ALSA v: k6.13.1-arch1-1 status: kernel-api
  Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Marvell 88E8040 PCI-E Fast Ethernet vendor: Samsung Co
    driver: sky2 v: 1.30 pcie: speed: 2.5 GT/s lanes: 1 port: 3000
    bus-ID: 04:00.0 chip-ID: 11ab:4354
  IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Broadcom BCM4313 802.11bgn Wireless Network Adapter
    vendor: Wistron NeWeb driver: wl v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 06:00.0 chip-ID: 14e4:4727
  IF: wlan0 state: dormant mac: <filter>
Bluetooth:
  Device-1: Broadcom BCM2070 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 5-2:3 chip-ID: 0a5c:219c
  Report: btmgmt ID: hci0 rfk-id: 3 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: N/A
Drives:
  Local Storage: total: 476.94 GiB used: 13.75 GiB (2.9%)
  ID-1: /dev/sda model: P3-512 size: 476.94 GiB speed: 3.0 Gb/s
    serial: <filter>
Partition:
  ID-1: / size: 468.38 GiB used: 13.75 GiB (2.9%) fs: ext4 dev: /dev/sda1
Swap:
  ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 62.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 4 GiB available: 3.76 GiB used: 1.32 GiB (35.0%)
  Processes: 173 Power: uptime: 7m wakeups: 0 Init: systemd v: 257
    default: graphical
  Packages: pm: pacman pkgs: 923 Compilers: clang: 19.1.7 gcc: 14.2.1
    Shell: Bash v: 5.2.37 running-in: xfce4-terminal inxi: 3.3.37
[jp@jp14 ~]$
2

You need to install labwc and can not remember if something else was required. Tried it sometime back and at that time it needed a little more loving.

3

thanks , i’ll wait and see if “something else” is posted lol

4

probz waisting my time with wayland ,specially that i have nvidia ,but still wanna see

5

https://wiki.archlinux.org/title/Xfce

See section 4.18 Using the experimental Wayland support

6

thanks for that
“things will not work like you expect it to and a lot of stuff are generally broken.”
think i won’t bother with wayland
:sunglasses:

1 Like
7

If it is that you’d like to try Wayland, try something that actually has full Wayland support, like Gnome, KDE or Hyprland. Hyprland is what I’d recommend since you already have a DE.

Then again, Xfce isn’t really a full DE, so Gnome or KDE shouldn’t really cause issues anyway.

I was sceptical about Wayland (still am, actually) like you, but when it comes to gaming, it just works better than X11 at the moment for my device (with Nvidia graphics). Even using Cinnamon’s experimental Wayland session gives me better compatibility with games than using any of my X11 sessions (Cinnamon, Openbox, i3).

The only reason I still don’t care for Wayland as a daily driver is that I use Hyprland, and screen sharing still involves jumping through hoops to get things to work properly.

1 Like
8

I tried it with Wayfire and noticed quickly that under Wayland you have only one workspace available, which is a big no for me.

I’m fine with X11, I don’t miss anything not using Wayland.

1 Like