Skip to content

GDM session

This content is for v0.1.1. Switch to the latest version for up-to-date documentation.

After installing, select the ARGVUS session in GDM/display manager.

The session launchers are provided by the argvus-session package. argvus-session prepares the session environment and executes argvus-start, which launches Hyprland with start-hyprland and loads $XDG_CONFIG_HOME/hypr/hyprland.lua only when a complete user override exists. Otherwise it starts from the packaged /usr/share/argvus/hypr/hyprland.lua. User preferences such as theme, accent and spacing are read from $XDG_CONFIG_HOME/argvus, and generated runtime config is read from $XDG_STATE_HOME/argvus/config.

If GDM returns to the login screen, check the logs:

Terminal window
sed -n '1,320p' ~/.local/state/argvus/session.log
journalctl --user -b -u 'wayland-wm@*' --no-pager

On VirtualBox, power off the VM and select VMSVGA, at least 128 MB of video memory, and Enable 3D Acceleration under Settings > Display. Keep drivers and Mesa up to date on the Arch guest:

Terminal window
sudo pacman -Syu --needed virtualbox-guest-utils mesa
sudo systemctl enable --now vboxservice.service

The launcher detects virtual machines, clears physical GPU overrides, enables the rendering fallbacks accepted by Hyprland, and uses the current packaged Lua unless the user has explicitly provided a complete Hyprland override. The user-selected theme keeps loading. Hyprland support in VMs still depends on the virtual GPU provided by the hypervisor.

The package does not write to $HOME during installation. Defaults live in /usr/share/argvus/.