Setup Issues
Tmux plugins not loading
Tmux plugins not loading
Error: Tmux starts but plugins (tpm, catppuccin, etc.) are not working or showing errors.Solution:The Tmux Plugin Manager (tpm) needs to be installed manually. Run:After installation:
- Start tmux or reload your configuration:
tmux source ~/.config/tmux/tmux.conf - Press
Ctrl+SpacethenI(capital i) to install plugins - Restart tmux sessions for changes to take effect
tmux.conf:130Polkit authentication prompts not appearing
Polkit authentication prompts not appearing
Error: Applications requiring elevated permissions fail silently or timeout.Solution:Install the Hyprland polkit authentication agent:The agent is configured to start automatically in If still not working, verify the service is running:
modules/autostart.conf:20:Font rendering issues or missing icons
Font rendering issues or missing icons
Error: Icons appear as boxes, waybar modules show For Fedora:JetBrainsMono Nerd Font (alternative):After installation, log out and log back in to ensure fonts are loaded.
[] instead of symbols, or fonts look incorrect.Solution:Install the required Nerd Fonts:For Arch Linux:Stow conflicts with existing files
Stow conflicts with existing files
Error: Understanding .stowrc:
The
stow command fails with “existing target is not owned by stow” errors.Solution:Backup and remove conflicting files before running stow:.stowrc configuration uses:--target=~- Installs to home directory--dotfiles- Convertsdot-prefix to.in target--ignore=.stowrc- Doesn’t symlink the stow config itself
Hyprland Issues
Display not detected or incorrect resolution
Display not detected or incorrect resolution
Error: External monitor not showing up, wrong resolution, or positioned incorrectly.Solution:
- List available outputs:
-
Check your monitor configuration in the appropriate config file:
- Desktop:
~/.config/hypr/modules/displays.conf - Laptop:
~/.config/hypr/modules/displays-laptop.conf
- Desktop:
-
The default configurations use:
- Primary:
eDP-1,1920x1200@60,0x0,1 - Secondary:
HDMI-A-2,1600x900@60,1921x0,1
- Primary:
- Update the monitor variables in your config:
- Reload Hyprland:
Super + Shift + Rorhyprctl reload
Hyprland fails to start or crashes on login
Hyprland fails to start or crashes on login
Error: Black screen after login, or immediate crash to TTY.Solution:
- Check Hyprland logs:
-
Common causes:
- Missing dependencies: Verify all autostart applications are installed
- Invalid config syntax: Check for typos in
hyprland.conf - Missing module files: Ensure all imported modules exist
- Test with minimal config:
- If working, gradually re-enable modules to identify the problematic one.
Workspace switching not working
Workspace switching not working
Error: Keybindings for workspace switching have no effect.Solution:
- Verify keybindings are loaded:
-
Check
modules/keybindings.confis properly sourced in your main config - Test if the mod key is working:
- Reload configuration:
Super + Shift + R
Autostart applications not launching
Autostart applications not launching
Error: Waybar, notification daemon, or other autostart apps don’t start with Hyprland.Solution:Check If missing, install the required packages:Check for errors in the Hyprland log after login.
modules/autostart.conf for the list of autostart applications:nm-applet- Network managerblueman-applet- Bluetoothmako- Notificationshyprpolkitagent- Authenticationhyprpaper- Wallpaper
Waybar Issues
Waybar not appearing or invisible
Waybar not appearing or invisible
Error: Waybar doesn’t show after login or becomes invisible.Solution:
- Check if waybar is running:
- Manually start waybar to see errors:
- Check the configuration syntax:
- Verify dependencies are installed:
Waybar modules showing errors or missing data
Waybar modules showing errors or missing data
Error: Specific waybar modules display errors, show “N/A”, or are empty.Solution:Common module issues:Network module:
- Requires
network-manager-applet - Check:
nmcli device status
- Requires
power-profiles-daemon - Install:
sudo dnf install power-profiles-daemon - Enable:
systemctl enable --now power-profiles-daemon
- Only works on laptops
- Check battery path:
ls /sys/class/power_supply/
How to reload waybar after configuration changes
How to reload waybar after configuration changes
Solution:Method 1: Kill and restart (hard reload)Method 2: Soft reload (SIGUSR2)Method 3: Using Justfile
If you have Method 4: Hyprland keybind
Use
just installed:Super + Shift + R if configured in your keybindings.Note: Hard reload is needed for structural config changes, soft reload works for style updates.Application Issues
Flatpak applications not launching
Flatpak applications not launching
Error: Flatpak apps like Zen Browser or Quran Companion don’t start.Solution:
- Verify the application is installed:
- Install if missing:
- Check permissions:
- Run from terminal to see errors:
Rofi menu not showing or wrong theme
Rofi menu not showing or wrong theme
Clipboard history not working
Clipboard history not working
Error: Clipboard manager (cliphist) doesn’t store or recall clipboard history.Solution:The autostart configuration includes:
- Install cliphist:
- Verify wl-paste is running:
- Test clipboard storage:
Configuration Issues
Changes to config files not taking effect
Changes to config files not taking effect
Solution:After modifying configuration files:For Hyprland:Or use keybind: For Tmux:Or inside tmux:
Super + Shift + RFor Waybar:Ctrl+Space then :source ~/.config/tmux/tmux.confFor complete reload:
Log out and log back in to HyprlandLocal customizations being overwritten
Local customizations being overwritten
Solution:Use local override files that are gitignored:Tmux local config:
Create Hyprland local config:
Add a source line at the end of your This follows the 12-factor approach of separating config from environment-specific settings.
~/.config/tmux/tmux.local.conf for your customizations.
This file is automatically sourced at tmux.conf:127:hyprland.conf:Getting More Help
If your issue isn’t covered here:- Check the FAQ for additional questions
- Review the Hyprland wiki: https://wiki.hyprland.org
- Check application-specific logs in
/tmpor~/.local/share/ - Run applications from terminal to see error output
- Review your specific module configuration in
~/.config/hypr/modules/