Page 1 of 2

MXLinux 23 sysVinit related Wayland "challenges"/ problems.

Posted: Wed Jan 17, 2024 9:10 am
by manyroads
By way of setting correct expectations, the system desktop configuration I am running has been tested and run earlier on Debian (vanilla, and Lilidog all systemd), Devuan (non-systemd); arch systemd based distros EOS & manjaro. None of the aforementioned demonstrate the problems, I will highlight in this thread. The primary reason, I suppose is because none afford the dual init systemd / sysV option.

To get to the quick, I am testing/ running a laptop (I'll include the laptop details below- QXPI) running the following:

- MX Linux 23 (ahs) current release.
- A group of dissimilar window managers (from a single user space) including:
-- bspwm (x11)
-- dwm (x11)
-- hlwm (x11)
-- i3wm (x11)
-- SwayWM (Wayland)
-- xfce4 (x11)
-Display Manager (x11 & Wayland)
-- lightdm
-- slick-greeter

For this thread, I will only include problems that exists in my install of MX23 sysVinit and not in MX23 systemd. I will list problems as I encounter them as unique posts in this thread.
MODs:
If you wish to kill this thread or move it elsewhere, please feel free to 'do what is best.'
Proof-of life image MX23 (systemd) running dwm.
Image

Proof-of-life image MX23 (sysVinit) running SwayWM
Image

QSI:

Code: Select all

System:
  Kernel: 6.6.11-1-liquorix-amd64 [6.6-15~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.6.11-1-liquorix-amd64
    root=UUID=<filter> ro quiet hush init=/lib/systemd/systemd
  Desktop: dwm v: 6.4 vt: 7 dm: LightDM v: 1.32.0 Distro: MX-23.1_ahs_x64 Libretto October 15
    2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: Dell product: Inspiron 5493 v: N/A serial: <superuser required> Chassis:
    type: 10 serial: <superuser required>
  Mobo: Dell model: 0M4FW1 v: A00 serial: <superuser required> UEFI: Dell v: 1.24.0
    date: 09/12/2022
Battery:
  ID-1: BAT0 charge: 32.1 Wh (100.0%) condition: 32.1/42.0 Wh (76.4%) volts: 13.0 min: 11.4
    model: BYD DELL 1VX1H9A type: Li-ion serial: <filter> status: full
CPU:
  Info: model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake gen: core 10 level: v4
    note: check built: 2019-21 process: Intel 10nm family: 6 model-id: 0x7E (126) stepping: 5
    microcode: 0xC2
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 320 KiB
    desc: d-4x48 KiB; i-4x32 KiB L2: 2 MiB desc: 4x512 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1274 high: 3459 min/max: 400/1201 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1425 2: 1500 3: 598 4: 1201 5: 400 6: 439
    7: 1175 8: 3459 bogomips: 19046
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: Enhanced IBRS
  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, RSB filling,
    PBRSB-eIBRS: SW sequence
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel arch: Gen-11
    process: Intel 10nm built: 2019-21 ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:8a56 class-ID: 0300
  Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:4
    chip-ID: 0c45:671e class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 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: eDP-1 model: ChiMei InnoLux 0x14d4 built: 2017 res: 1920x1080 hz: 60 dpi: 158
    gamma: 1.2 size: 309x173mm (12.17x6.81") diag: 354mm (13.9") ratio: 16:9 modes: 1920x1080
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel UHD Graphics (ICL GT1)
    direct-render: Yes
Audio:
  Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel
    alternate: snd_sof_pci_intel_icl bus-ID: 00:1f.3 chip-ID: 8086:34c8 class-ID: 0403
  API: ALSA v: k6.6.11-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 RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8136 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell
    driver: ath10k_pci v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0
    chip-ID: 168c:0042 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:5 chip-ID: 0cf3:e009
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
    sub-v: 25a hci-v: 4.2
  Info: acl-mtu: 1024:8 sco-mtu: 50:8 link-policy: rswitch hold sniff
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
Drives:
  Local Storage: total: 1.86 TiB used: 678.74 GiB (35.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 043 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT1050MX300SSD4 size: 978.09 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: R031
    scheme: GPT
Partition:
  ID-1: / raw-size: 977.84 GiB size: 961.41 GiB (98.32%) used: 678.74 GiB (70.6%) fs: ext4
    dev: /dev/sdb2 maj-min: 8:18
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 411 KiB (0.2%) fs: vfat
    dev: /dev/sdb1 maj-min: 8:17
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 5 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 71.0 C mobo: 46.0 C
  Fan Speeds (RPM): cpu: 2570
Repos:
  Packages: pm: dpkg pkgs: 2462 libs: 1227 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  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/microsoft-edge.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://mxrepo.com/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
    1: deb [arch=amd64] https://repo.skype.com/deb stable main
Info:
  Processes: 331 Uptime: 1h 23m wakeups: 619 Memory: 23.25 GiB used: 3.99 GiB (17.2%) Init: systemd
  v: 252 target: graphical (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
It is my hope that this thread will help MX and antiX prepare for Wayland, should that be a desirable team objective.

Re: MXLinux 23 sysVinit related Wayland "challenges"/ problems.

Posted: Wed Jan 17, 2024 9:55 am
by manyroads
Niggling problem #1: missing systray items

When running Wayland SwayWM sysV & systemd you will note differences in systray items. Several are missing from Waybar under sysV. Any ideas, why? They should be identical.

The only differences in the environments is that one is booted under sysV and the other is booted under systemd. If you check the right hand conky at the bottom you will note which image booted with systemd or sysV. Methinks something is amiss...

Image Image

Re: MXLinux 23 sysVinit related Wayland "challenges"/ problems.

Posted: Wed Jan 17, 2024 10:13 am
by Adrian
Have you tried Plasma? Do you see similar problems in Plasma? If not, it means the problem lays with SwayWM...

Re: MXLinux 23 sysVinit related Wayland "challenges"/ problems.

Posted: Wed Jan 17, 2024 12:36 pm
by manyroads
Adrian wrote: Wed Jan 17, 2024 10:13 am Have you tried Plasma? Do you see similar problems in Plasma? If not, it means the problem lays with SwayWM...
SwayWM and Plasma are among those that don't always play nicely together or 'compatibly' on Wayland.

I, also, discovered that my MX install was missing some Wayland essential software. I was trying to load nwg-panel, which failed to install due to missing:
gir1.2-gtklayershell-0.1
Here is the package I tried to install that failed:
nwg-panel_0.9.21-5_all.deb
( https://software.opensuse.org/download. ... =nwg-panel )


I installed that and now it tries to run but dies. Presumably there is something else that is missing. I'll rummage to see if I can figure it out.

FWIW I'll install Plasma Wayland to see what happens...

Re: MXLinux 23 sysVinit related Wayland "challenges"/ problems.

Posted: Wed Jan 17, 2024 12:46 pm
by Adrian
FWIW I'll install Plasma Wayland to see what happens...
Why don't you try the KDE ISO?

Re: MXLinux 23 sysVinit related Wayland "challenges"/ problems.

Posted: Wed Jan 17, 2024 1:06 pm
by manyroads
Adrian wrote: Wed Jan 17, 2024 12:46 pm
FWIW I'll install Plasma Wayland to see what happens...
Why don't you try the KDE ISO?
I don't have a good answer for that... other than I don't want to build off of KDE. I'm pretty certain an install of gnome (wayland) stands a chance of fixing things but folks here are gnome-averse. In any case SwayWM should work on a vanilla Wayland base (such is this old guy's opinion).

Here is what I did try, based on your earlier note, the below items were only tested under sysV:
1. I installed wayland-protocols & wayland-utilities: they both did nothing useful. On the bad end the broke sudo -E so that synaptic no longer worked on Wayland. I removed both.
2. I installed kwin-wayland. It broke SwayWM and caused it to fail completely without successful login function. I removed it and rebooted, things are back to functioning.

Re: MXLinux 23 sysVinit related Wayland "challenges"/ problems.

Posted: Wed Jan 17, 2024 1:08 pm
by dolphin_oracle
manyroads wrote: Wed Jan 17, 2024 9:55 am Niggling problem #1: missing systray items

When running Wayland SwayWM sysV & systemd you will note differences in systray items. Several are missing from Waybar under sysV. Any ideas, why? They should be identical.

The only differences in the environments is that one is booted under sysV and the other is booted under systemd. If you check the right hand conky at the bottom you will note which image booted with systemd or sysV. Methinks something is amiss...

Image Image
i guess would be that whatever is provide the autostart functions on swayWM has a systemd user service to launch it, which would not exist under sysV. this would likely not be a problem on DEs.

Re: MXLinux 23 sysVinit related Wayland "challenges"/ problems.

Posted: Wed Jan 17, 2024 1:10 pm
by siamhie
manyroads wrote: Wed Jan 17, 2024 12:36 pm
I, also, discovered that my MX install was missing some Wayland essential software. I was trying to load nwg-panel, which failed to install due to missing:
gir1.2-gtklayershell-0.1
Here is the package I tried to install that failed:
nwg-panel_0.9.21-5_all.deb
( https://software.opensuse.org/download. ... =nwg-panel )


I installed that and now it tries to run but dies. Presumably there is something else that is missing. I'll rummage to see if I can figure it out.

I presume you have all the other dependencies installed?

Code: Select all

Debian GNU/Linux Dependencies

git curl bluez-tools gir1.2-gtklayershell-0.1 libgtk-3-0 pulseaudio-utils gir1.2-dbusmenu-gtk3-0.4 gir1.2-playerctl-2.0 playerctl 
python3-dasbus python3-gi-cairo python3-i3ipc python3-netifaces python3-psutil python3-requests python3-setuptools 
python3-wheel sway-notification-center

Additionally, pipewire or pulseaudio for sound, light,brightnessctl or ddcutil for brightness slider, fonts-noto-color-emoji for 
weather icons, and wlr-randr if you're using Hyprland instead of sway.

Note: Locale variables must be set (sudo dpkg-reconfigure locales).

https://github.com/nwg-piotr/nwg-panel/ ... pendencies

Re: MXLinux 23 sysVinit related Wayland "challenges"/ problems.

Posted: Wed Jan 17, 2024 5:05 pm
by manyroads
@siamhie Yes. All normal Debian pre-requisites are installed. I have been following the Debian Wayland/ Sway wiki install recommendations. Everything has worked fine on vanilla Debian (sid) and Lilidog/ Beardog but those installs were all systemd-only based. The only place I have had a problem thus far is here. Arch has worked fine as well. It's peculiar. But, it should be noted that Piotr Mueller (the primary dev of nwg) is a known anti-Debian guy; he's a 'bit' arch biased. Nonetheless, I'll reinstall everything in the list you provided to see what happens. I'll report back.

Re: MXLinux 23 sysVinit related Wayland "challenges"/ problems.

Posted: Wed Jan 17, 2024 5:11 pm
by manyroads
dolphin_oracle wrote: Wed Jan 17, 2024 1:08 pm
manyroads wrote: Wed Jan 17, 2024 9:55 am Niggling problem #1: missing systray items

When running Wayland SwayWM sysV & systemd you will note differences in systray items. Several are missing from Waybar under sysV. Any ideas, why? They should be identical.

[...]
i guess would be that whatever is provide the autostart functions on swayWM has a systemd user service to launch it, which would not exist under sysV. this would likely not be a problem on DEs.
That seems reasonable. I've looked into the SwayWM autostart to see what I am able to determine. What I found is the following:

Code: Select all

# GTK3 applications take a long time to start
exec systemctl --user import-environment DISPLAY WAYLAND_DISPLAY SWAYSOCK
exec hash dbus-update-activation-environment 2>/dev/null && \
     dbus-update-activation-environment --systemd DISPLAY WAYLAND_DISPLAY SWAYSOCK
I'm not sure what this is or what I would do to get around it.

FWIW below is my entire autostart, in case anyone else wants to take a look.

Code: Select all

# Notification #####################
exec dunst -conf  ~/.config/dunst/dunstrc &
#exec mako

# Autolock

# Lock screen after 15 minutes; turn off display after another 5 minutes.
#
# Note that in the context of idle system power management, it is *NOT* a good
# idea to turn off displays by 'disabling outputs' for example by
# `wlr-randr --output <whatever> --off` because this re-arranges views
# (since a837fef). Instead use a wlr-output-power-management client such as
# https://git.sr.ht/~leon_plickat/wlopm
#swayidle -w \
#	timeout 900 'swaylock-fancy -f -c 000000' \
#	timeout 1200 'wlopm --off \*' \
#	resume 'wlopm --on \*' \
#	before-sleep 'swaylock-fancy -f -c 000000' 

# Lock screen after 5 minutes
#exec swayidle -w timeout 300 'swaylock-fancy' before-sleep 'swaylock-fancy -f' 
exec swayidle -w timeout 300 'swaylock' before-sleep 'swaylock -f'
# swfbar
# exec swfbar

# Wallpaper is being set in the theme script in conf.d

# To cheat & run synaptic
#exec xhost +si:localuser:root

# Network Applet
exec nm-applet --indicator

# GTK3 applications take a long time to start
exec systemctl --user import-environment DISPLAY WAYLAND_DISPLAY SWAYSOCK
exec hash dbus-update-activation-environment 2>/dev/null && \
     dbus-update-activation-environment --systemd DISPLAY WAYLAND_DISPLAY SWAYSOCK
     
# Welcome App
# exec dex -a -s /etc/xdg/autostart/:~/.config/autostart/  

# Sway Fader
# exec python3 ~/.config/sway/scripts/swayfader.py  

exec --no-startup-id conky -c ~/.conky/sway/.sway-1rc
exec --no-startup-id conky -c ~/.conky/sway/.sway-2rc
exec gammastep-indicator

# swayr
exec env RUST_BACKTRACE=1 RUST_LOG=swayr=debug swayrd > /tmp/swayrd.log 2>&1

###################################################################
########### Cleanup x11 wm processes  #############################
########### & add back those which work ###########################
###################################################################

# Dropbox #####################
#pkill dropbox 
#~/.dropbox-dist/dropboxd &
exec sleep 5 && DISPLAY= dropbox start -i & 

# Networking & Sounds #####################
exec nm-applet &
exec start-pulseaudio-x11 &
exec pnmixer &
exec pasystray &
exec pamixer &  ## under test
exec /usr/bin/blueman-applet &

# Notification #####################
exec dunst -conf  ~/.config/dunst/dunstrc &

# USB unmounter #####################
exec udiskie --smart-tray --automount --notify &