Wayland: Questions and Screen Sharing Issues with Zoom and Slack

ZeR0ByTe · 25 December 2025 10:59

Hi, I have some doubts and I’d like to know if you can help me, as always .
I have two laptops running Manjaro KDE, and I’m trying to use Wayland.

Note: In the inxi -Fazy output below it will show X11, because while I’m writing this I’m currently using X11.

I’m having problems sharing my screen in Slack and Zoom.

Slack issue:
When other people draw on the shared screen, I can’t see the drawings. I can only see them if I’m watching my own screen being shared together with the video of the other person and myself. This makes it impossible to work with other windows, because I can’t see the drawings.

Zoom issues:
The problem is a bit strange.

On Laptop 1, when I share my screen, I can’t see the green border indicating that sharing is active. Other people can see my screen, but I don’t get the toolbar to stop sharing or to see if they are drawing. Also, my screen share appears inside a tab.
On Laptop 2, everything works perfectly. I can see the toolbar to stop sharing, mute the microphone, etc.

Additionally, when I share my screen in Zoom, it’s extremely slow.

Both laptops have the same versions of Zoom and Slack installed.

local/slack-desktop 4.47.69-1
    Slack Desktop (Beta) for Linux
local/zoom 6.7.0-1
    Video Conferencing and Web Conferencing Service

Using X11 everything works perfectly.

Questions:

Are there alternative clients for Slack and Zoom? I need both for work, and I’d really like to use Wayland if possible.
Is anyone else experiencing the same problems?
I’m not a Linux expert, but I don’t understand why there is a push towards Wayland if many tools still don’t work properly
Should I continue using X11 for my work? What do you recommend?

I’m trying to switch to Wayland because I’ve read that it’s more modern and better.

Thanks for your time and Happy Christimas!

Laptop 1 - inxi -Fazy

System:
  Kernel: 6.12.63-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=e8ad0b83-8ba5-4838-bd74-fb0464854b35 rw
    resume=UUID=f868137e-dac2-4bd8-b260-70ad9aef5f1d udev.log_priority=3
    optimus-manager.startup=hybrid nvidia_drm.modeset=1
  Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A info: frameworks v: 6.21.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: PCSpecialist product: GM6PX0X v: Standard
    serial: <superuser required>
  Mobo: TongFang model: GM6PX0X v: Standard serial: <superuser required>
    part-nu: 0001 uuid: <superuser required> Firmware: UEFI vendor: American
    Megatrends LLC. v: N.1.09A02 date: 05/15/2023
Battery:
  ID-1: BAT0 charge: 95.1 Wh (96%) condition: 99.1/99.1 Wh (100%) volts: 16.35
    min: 15.48 model: standard type: Li-ion serial: <filter> charging:
    status: not charging cycles: N/A
CPU:
  Info: model: 13th Gen Intel Core i9-13900HX bits: 64 type: MST AMCP
    arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
    process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
    microcode: 0x132
  Topology: cpus: 1x dies: 1 clusters: 12 cores: 24 threads: 32 mt: 8 tpc: 2
    st: 16 smt: enabled cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32
    KiB, 16x64 KiB L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
  Speed (MHz): avg: 976 min/max: 800/5200:5400:3900 scaling:
    driver: intel_pstate governor: powersave cores: 1: 976 2: 976 3: 976 4: 976
    5: 976 6: 976 7: 976 8: 976 9: 976 10: 976 11: 976 12: 976 13: 976 14: 976
    15: 976 16: 976 17: 976 18: 976 19: 976 20: 976 21: 976 22: 976 23: 976
    24: 976 25: 976 26: 976 27: 976 28: 976 29: 976 30: 976 31: 976 32: 976
    bogomips: 154880
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection 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: 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: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel Raptor Lake-S UHD Graphics vendor: AIstone Global
    driver: i915 v: kernel alternate: xe arch: Xe process: Intel 10nm
    built: 2020-21 ports: active: none off: eDP-1 empty: DP-1, DP-2, HDMI-A-1,
    HDMI-A-2, HDMI-A-3, HDMI-A-4 bus-ID: 00:02.0 chip-ID: 8086:a788
    class-ID: 0300
  Device-2: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile]
    vendor: AIstone Global driver: nvidia v: 580.119.02
    alternate: nouveau,nvidia_drm non-free: 550-580.xx+
    status: current (as of 2025-11) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 8
    ports: active: none off: DP-3,HDMI-A-5 empty: DP-4,eDP-2 bus-ID: 01:00.0
    chip-ID: 10de:28a0 class-ID: 0300
  Device-3: Trust USB Camera driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:3 chip-ID: 145f:0203
    class-ID: 0102 serial: <filter>
  Device-4: Chicony FHD Webcam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:4 chip-ID: 04f2:b7c2
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia dri: iris
    gpu: i915,nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5360x1440 s-dpi: 110 s-size: 1239x333mm (48.78x13.11")
    s-diag: 1283mm (50.51")
  Monitor-1: not-matched mapped: DP-0 pos: primary,top-right res:
    mode: 3440x1440 hz: 160 scale: 100% (1) dpi: 109
    size: 800x330mm (31.5x12.99") diag: 865mm (34.07") modes: N/A
  Monitor-2: not-matched mapped: HDMI-0 pos: bottom-l res: mode: 1920x1080
    hz: 60 scale: 100% (1) dpi: 94 size: 521x293mm (20.51x11.54")
    diag: 598mm (23.53") modes: N/A
  Monitor-3: eDP-1 mapped: eDP-1-1 note: disabled model: BOE Display 0x0a3b
    built: 2021 res: 1920x1080 dpi: 189 gamma: 1.2 size: 344x215mm (13.54x8.46")
    diag: 406mm (16") ratio: 16:10 modes: 2560x1600
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.119.02
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4060 Laptop
    GPU/PCIe/SSE2 memory: 7.81 GiB
  API: Vulkan v: 1.4.335 layers: 8 device: 0 type: discrete-gpu name: NVIDIA
    GeForce RTX 4060 Laptop GPU driver: nvidia v: 580.119.02
    device-ID: 10de:28a0 surfaces: N/A device: 1 type: integrated-gpu
    name: Intel Graphics (RPL-S) driver: mesa intel v: 25.3.1-arch1.2
    device-ID: 8086:a788 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Raptor Lake High Definition Audio vendor: AIstone Global
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
    bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
  Device-2: NVIDIA AD107 High Definition Audio vendor: AIstone Global
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 10de:22be class-ID: 0403
  Device-3: Trust USB Camera driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:3 chip-ID: 145f:0203
    class-ID: 0102 serial: <filter>
  API: ALSA v: k6.12.63-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel 700 Series CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:7a70 class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: AIstone Global driver: r8169
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 3a:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp58s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IF-ID-2: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
  Info: services: NetworkManager,sshd
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:10 chip-ID: 8087:0033
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 1.86 TiB used: 646.69 GiB (33.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Solidgm model: SSDPFKNU020TZ
    size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 002C temp: 16.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 120 GiB size: 117.81 GiB (98.17%) used: 81.99 GiB (69.6%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 301 MiB size: 300.4 MiB (99.79%)
    used: 308 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 1.34 TiB size: 1.31 TiB (98.35%)
    used: 564.7 GiB (42.0%) fs: ext4 dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 26.5 C mobo: N/A gpu: nvidia temp: 31 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 64 GiB note: est. available: 62.53 GiB used: 3.97 GiB (6.3%)
  Processes: 544 Power: uptime: 1m states: freeze,mem,disk suspend: s2idle
    avail: deep wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend,
    test_resume image: 24.98 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
    tool: systemctl
  Packages: 1873 pm: dpkg pkgs: 1 pm: pacman pkgs: 1797 libs: 432
    tools: pamac,yay pm: flatpak pkgs: 59 pm: snap pkgs: 16 Compilers:
    gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: zellij inxi: 3.3.40

Laptop 2 - inxi -Fazy

System:
 Kernel: 6.12.63-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v:
 15.2.1
   clocksource: tsc avail: acpi_pm
   parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.12-x86_64
   root=UUID=30356c56-5d64-4af1-86d9-2aac6cad9fb4 rw rootflags=su
bvol=@ quiet
   splash resume=UUID=7dcfe72e-0479-465c-b1a5-6352b197c7bf
   udev.log_priority=3
 Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A info: frameworks v: 6
.21.0
   wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
 Type: Laptop System: Micro-Star product: Prestige 13 AI Evo A1MG
 v: REV:1.0
   serial: <superuser required> Chassis: type: 10 serial: <superu
ser required>
 Mobo: Micro-Star model: MS-13Q2 v: REV:1.0 serial: <superuser re
quired>
   part-nu: 13Q2.1 uuid: <superuser required> Firmware: UEFI vend
or: American
   Megatrends LLC. v: E13Q2IMS.103 date: 12/06/2023
Battery:
 ID-1: BAT1 charge: 57.3 Wh (77.4%) condition: 74.1/72.4 Wh (102.
2%)
   volts: 16.2 min: 15.48 model: MSI BIF0_9 type: Li-ion serial:
N/A charging:
   status: discharging cycles: N/A
CPU:
 Info: model: Intel Core Ultra 7 155H bits: 64 type: MST AMCP
   arch: Meteor Lake level: v3 note: check built: 2023+ process:
Intel 4 (7nm)
   family: 6 model-id: 0xAA (170) stepping: 4 microcode: 0x25
 Topology: cpus: 1x dies: 1 clusters: 9 cores: 16 threads: 22 mt:
 6 tpc: 2
   st: 10 smt: enabled cache: L1: 1.6 MiB desc: d-10x32 KiB, 6x48
 KiB; i-16x64
   KiB L2: 18 MiB desc: 9x2 MiB L3: 24 MiB desc: 1x24 MiB
 Speed (MHz): avg: 400 min/max: 400/4500:4800:3800:2500 scaling:
   driver: intel_pstate governor: powersave cores: 1: 400 2: 400
3: 400 4: 400
   5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13:
 400 14: 400
   15: 400 16: 400 17: 400 18: 400 19: 400 20: 400 21: 400 22: 40
0
   bogomips: 131824
 Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 s
sse3 vmx
 Vulnerabilities:
 Type: gather_data_sampling status: Not affected
 Type: indirect_target_selection 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: reg_file_data_sampling status: Not affected
 Type: retbleed status: Not affected
 Type: spec_rstack_overflow status: Not affected
 Type: spec_store_bypass mitigation: Speculative Store Bypass dis
abled via
   prctl
 Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user
 pointer
   sanitization
 Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: co
nditional;
   PBRSB-eIBRS: Not affected; BHI: BHI_DIS_S
 Type: srbds status: Not affected
 Type: tsa status: Not affected
 Type: tsx_async_abort status: Not affected
 Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
 Device-1: Intel Meteor Lake-P [Intel Arc Graphics] vendor: Micro
-Star MSI
   driver: i915 v: kernel alternate: xe arch: Xe-LPG process: Int
el 4 (7nm+)
   built: 2023+ ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1
   bus-ID: 0000:00:02.0 chip-ID: 8086:7d55 class-ID: 0300
 Device-2: Bison FHD Camera driver: uvcvideo type: USB rev: 2.0
   speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-4:3 chip-ID: 5986
:1193
   class-ID: fe01 serial: <filter>
 Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.9
   compositor: kwin_x11 driver: X: loaded: modesetting alternate:
 fbdev,vesa
   dri: iris gpu: i915 display-ID: :0 screens: 1
 Screen-1: 0 s-res: 2880x1800 s-dpi: 96 s-size: 762x476mm (30.00x
18.74")
   s-diag: 898mm (35.37") monitors: <missing: xrandr>
 Monitor-1: eDP-1 model: Samsung 0x41a8 built: 2021 res: 2880x180
0 dpi: 256
   gamma: 1.2 size: 286x179mm (11.26x7.05") diag: 337mm (13.3") r
atio: 16:10
   modes: 2880x1800
 API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: ir
is
   device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x1
1: drv: iris
   inactive: wayland
 API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.3.1-ar
ch1.2
   glx-v: 1.4 direct-render: yes renderer: Mesa Intel Arc Graphic
s (MTL)
   device-ID: 8086:7d55 memory: 30.31 GiB unified: yes
 API: Vulkan v: 1.4.335 layers: 2 device: 0 type: integrated-gpu
name: Intel
   Arc Graphics (MTL) driver: mesa intel v: 25.3.1-arch1.2
   device-ID: 8086:7d55 surfaces: N/A
 Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
   de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyi
nfo,xprop
Audio:
 Device-1: Intel Meteor Lake-P HD Audio vendor: Micro-Star MSI
   driver: sof-audio-pci-intel-mtl
   alternate: snd_hda_intel,snd_sof_pci_intel_mtl bus-ID: 0000:00
:1f.3
   chip-ID: 8086:7e28 class-ID: 0401
 API: ALSA v: k6.12.63-1-MANJARO status: kernel-api with: aoss
   type: oss-emulator tools: alsactl,alsamixer,amixer
 Server-1: JACK v: 1.9.22 status: off tools: N/A
 Server-2: PipeWire v: 1.4.9 status: active with: 1: pipewire-pul
se
   status: active 2: wireplumber status: active 3: pipewire-alsa
type: plugin
   tools: pactl,pw-cat,pw-cli,wpctl
Network:
 Device-1: Intel Wi-Fi 7 AX1775 /AX1790 /BE20 /BE401/BE1750 2x2
   vendor: Rivet Networks driver: iwlwifi v: kernel bus-ID: 0000:
55:00.0
   chip-ID: 8086:272b class-ID: 0280
 IF: wlp85s0f0 state: up mac: <filter>
 Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152
 type: USB
   rev: 3.0 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-2:
2
   chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
 IF: enp0s13f0u2 state: down mac: <filter>
 IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N
/A
 Info: services: NetworkManager, systemd-timesyncd, wpa_supplican
t
Bluetooth:
 Device-1: Intel BE200 Bluetooth driver: btusb v: 0.8 type: USB r
ev: 2.0
   speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:7 chip-ID: 8087
:0036
   class-ID: e001
 Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recom
mends
RAID:
 Hardware-1: Intel Volume Management Device NVMe RAID Controller
Intel
   driver: vmd v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 808
6:7d0b rev:
   class-ID: 0104
Drives:
 Local Storage: total: 953.87 GiB used: 21.2 GiB (2.2%)
 SMART Message: Required tool smartctl not installed. Check --rec
ommends
 ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: MZVL21T
0HDLU-00BT7
   size: 953.87 GiB block-size: physical: 512 B logical: 512 B sp
eed: 63.2 Gb/s
   lanes: 4 tech: SSD serial: <filter> fw-rev: GXD71W2Q temp: 21.
9 C
   scheme: GPT
Partition:
 ID-1: / raw-size: 120 GiB size: 120 GiB (100.00%) used: 10.86 Gi
B (9.1%)
   fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
 ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
   used: 648 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p4 maj-min: 259
:4
 ID-3: /home raw-size: 827.58 GiB size: 827.58 GiB (100.00%)
   used: 10.34 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p3 maj-min:
259:3
 ID-4: /var/log raw-size: 120 GiB size: 120 GiB (100.00%)
   used: 10.86 GiB (9.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min:
259:2
Swap:
 Kernel: swappiness: 60 (default) cache-pressure: 100 (default) z
swap: no
 ID-1: swap-1 type: partition size: 6 GiB used: 0 KiB (0.0%) prio
rity: -2
   dev: /dev/nvme0n1p1 maj-min: 259:1
Sensors:
 System Temperatures: cpu: 31.0 C mobo: N/A
 Fan Speeds (rpm): cpu: 2318 fan-2: 0 fan-3: 0 fan-4: 0
Info:
 Memory: total: 32 GiB available: 31.04 GiB used: 2.01 GiB (6.5%)
 Processes: 428 Power: uptime: 0m states: freeze,mem,disk suspend
: s2idle
   avail: deep wakeups: 0 hibernate: platform avail: shutdown, re
boot, suspend,
   test_resume image: 12.4 GiB services: org_kde_powerdevil,
   power-profiles-daemon, upowerd Init: systemd v: 258 default: g
raphical
   tool: systemctl
 Packages: pm: pacman pkgs: 1249 libs: 330 tools: pamac pm: flatp
ak pkgs: 0
   Compilers: gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole i
nxi: 3.3.40
``

soundofthunder · 25 December 2025 11:24

Neither Slack or Zoom are provided by the official Manjaro repositories – I assume they are both from the AUR, which is not officially supported by Manjaro (or Arch Linux).

The topic category has been adjusted accordingly. If these are not from the AUR, but instead are third-party software, the category will need to be changed again.

As these are not officially supported, and you are responsible for maintaining them, any assistance from forum members may be limited – I use neither of these, personally.

Is there a question here?

One doesn’t need to be a “Linux expert”, but assuredly, one needs more knowledge than how to click buttons to install software, like Windows.
It’s important to take the initiative and learn as much as you can if, as you suggest, you depend on Linux for work.

We recommend nothing. The questions are too vague to provide any meaningful response, but as a general rule of thumb Nvidia graphics are often the weak link.

If using KDE or Gnome, you have little choice but to use Wayland.

I’ve personally used Wayland exclusively (with AMD graphics) for over two and 1/2 years without any significant issues.

Problems with both Wayland or X11 can arise dependent on hardware configurations and the level of individual system maintenance.

A so-called rolling release distribution isn’t for everyone. It typically needs to be maintained and updated constantly – problems are inevitable – the key issue is how well prepared the system administrator (you) are to handle these issues effectively.

If you have any doubt, then perhaps a point release distribution will be arguable more stable for work, long-term. That being the case, I’d suggest the new Debian 13 (Trixie) which, incidentally, also runs Wayland as default.

The only official Manjaro edition that still defaults to X11 is Manjaro XFCE, which is an acquired taste if you’re used to Plasma. I suppose X11 will eventually be dropped from XFCE as well, but for now it looks like it will stay for a while.

I hope you can glean something useful from my comments. With any luck, other forum members who happen to use either of Slack or Zoom might be able to help further (to the extent possible), whenever they are able.

Regards.

linux-aarhus · 25 December 2025 13:09

I recommend using the tool that work for you.

If that is X11 then X11 it is.

Screen sharing with Zoom and Slack on Wayland will come - eventually…

Yes Wayland is modern - with modern comes some limitations - tightened security for applications.

Your profile says KDE Plasma - so you still have time.

If I were relying heavily on X11 for my work I’d probably use Xfce - they are not on the highway headed for Wayland.

ZeR0ByTe · 25 December 2025 15:17

Thank you both @linux-aarhus @soundofthunder for taking the time to reply and share your perspectives.

I’m aware that both Slack and Zoom are not maintained by the Manjaro team and are provided as third-party software (AUR / external binaries). My intention with this post was not to blame the system, but rather to hear about real user experiences: whether others are facing the same issues with Wayland, if there are any viable alternatives (different clients, browser usage, etc.), or if there are known workarounds—especially regarding screen sharing and the Zoom toolbar, which interestingly appears on one laptop but not on the other despite having the same software installed.

I like to stay up to date and try newer technologies (always on the stable branch), which is why I wanted to give Wayland a proper try. However, since these tools are critical for my daily work and everything works flawlessly on X11, I’ll stick with X11 for now to avoid friction.

That said, I really appreciate the insights and context you’ve provided, and I’ll keep the thread open in case others want to share their experiences with Slack or Zoom on Wayland, or suggest alternatives for screen sharing that work better.

Thanks again