Troubleshooting
Start here
Section titled “Start here”vela doctorIt lists what is missing, not linked or not running, with the command that fixes most of them.
The install printed errors
Section titled “The install printed errors”Red lines while the packages install are usually dnf trying another mirror
after one failed, and the package installs anyway; vela doctor shows
whether anything ended up missing. The installer keeps a record of the run,
with dnf’s warnings and errors, in ~/.local/state/vela/install.log.
The shell
Section titled “The shell”vela shell log # its log, livevela shell restart # or super + shift + Rqs -c vela --log-rules 'qml.debug=true' # run it in the foreground, chattilyNothing appears after logging in
Section titled “Nothing appears after logging in”- Is it Hyprland? On the login screen, the session must be Hyprland.
- Is the shell running? From a terminal (super + return):
vela shell start, thenvela shell log. - Is Hyprland new enough? vela’s config needs 0.56 or newer;
vela doctorsays which you have. - Icons show as words? The Material Symbols font is missing; run the
installer again, or see
vela doctor.
Hyprland’s config
Section titled “Hyprland’s config”Hyprland --verify-config -c ~/.config/hypr/hyprland.luachecks it without applying anything.
Stuck on a locked screen
Section titled “Stuck on a locked screen”If the password is not accepted, or the lock screen is blank, switch to a console with ctrl + alt + F3 and log in. Then, in order:
-
The shell is still running – release the lock:
Terminal window export XDG_RUNTIME_DIR=/run/user/$(id -u) WAYLAND_DISPLAY=wayland-1qs -c vela ipc call lock unlock -
The shell has died – the compositor keeps the session locked (that is how screen locking is meant to work). Clear it:
Terminal window for d in /run/user/$(id -u)/hypr/*/; dos=$(basename "$d")HYPRLAND_INSTANCE_SIGNATURE=$s hyprctl eval 'hl.clear_crashed_lockscreen()' && breakdone -
Neither works – end the session:
hyprctl dispatch exit, or reboot.
Switch back with ctrl + alt + F1 (or F2).
“matugen is older than 4.0”
Section titled ““matugen is older than 4.0””vela doctor says this when the matugen installed is Fedora’s rather than
vela’s own build. Palettes still work, from the wallpaper’s dominant colour,
but not quite the way vela is made for. Install vela’s build with
~/.local/share/vela-dots/bootstrap.sh --matugen; if that says there is no
build for your Fedora release yet, see matugen.
Colours did not change in an app
Section titled “Colours did not change in an app”GTK apps take a new palette the next time they start; fuzzel and hyprlock the
next time they open. The shell, Hyprland, kitty and cava change at once. If
none of them changed, run vela wallpaper <image> in a terminal and read what
it says.