Desktop Environment Configurations - buggerman/re-arch GitHub Wiki
RE-ARCH Desktop Environment Configurations
Detailed information about all supported desktop environments and their optimized configurations.
🎨 Supported Desktop Environments
RE-ARCH supports four carefully curated desktop environments, each with optimized package selections, performance tuning, and security enhancements:
1. 🔷 KDE Plasma (Recommended)
Why KDE Plasma is Recommended:
- Most Complete: Extensive feature set with excellent stability
- Performance Optimized: Superior resource management and responsiveness
- Highly Customizable: Deep configuration options without compromising stability
- Modern Standards: Full Wayland support with seamless X11 fallback
- Gaming Excellence: Best gaming performance with built-in optimizations
- Developer Friendly: Excellent development tools integration
Key Packages:
plasma-desktop
- Core desktop environmentplasma-nm
- Network management integrationplasma-pa
- Audio management integrationpowerdevil
- Power managementsddm
- Display manager with native KDE integrationkonsole
- Terminal emulatordolphin
- File managerdiscover
- Package manager GUI (native KDE)
Configuration:
# Installation command
archinstall --config-url https://re-arch.xyz/config-kde.json --creds-url https://re-arch.xyz/creds.json
2. 🟣 GNOME
Why Choose GNOME:
- Modern Interface: Clean, intuitive, touch-optimized design
- Accessibility Leader: Industry-leading accessibility features
- Wayland Pioneer: Built-first for Wayland with mature implementation
- Integrated Ecosystem: Seamless application integration and workflow
- Enterprise Ready: Backed by Red Hat with enterprise support
Key Packages:
gnome-shell
- Core desktop environmentgnome-control-center
- System settingsgnome-terminal
- Terminal emulatorgdm
- Display manager with GNOME integrationgnome-software
- Package manager GUIgnome-power-manager
- Power managementgnome-bluetooth
- Bluetooth integrationxdg-desktop-portal-gnome
- Desktop portal for sandboxed apps
Configuration:
# Installation command
archinstall --config-url https://re-arch.xyz/config-gnome.json --creds-url https://re-arch.xyz/creds.json
3. 🟡 XFCE
Why Choose XFCE:
- Resource Efficient: Minimal memory and CPU usage
- Rock Solid: Proven stability and reliability
- Traditional Workflow: Familiar desktop paradigm and interface
- Highly Themeable: Extensive customization and theming options
- Legacy Hardware: Perfect for older or resource-constrained systems
Key Packages:
xfce4
- Core desktop environmentxfce4-goodies
- Additional utilities and pluginsxfce4-terminal
- Terminal emulatorlightdm
- Lightweight display managerlightdm-gtk-greeter
- GTK-based login screengnome-software
- Package manager GUI (best Flatpak frontend)xfce4-power-manager
- Power managementxfce4-pulseaudio-plugin
- Audio integration
Configuration:
# Installation command
archinstall --config-url https://re-arch.xyz/config-xfce.json --creds-url https://re-arch.xyz/creds.json
4. 🔵 Hyprland
Why Choose Hyprland:
- Next-Gen Tiling: Advanced dynamic tiling window manager
- Wayland Native: Built specifically for modern Wayland protocol
- Performance Leader: Exceptional performance and resource efficiency
- Infinitely Configurable: Scriptable configuration with advanced options
- Power User Focused: Keyboard-driven workflow for productivity experts
Key Packages:
hyprland
- Core window managerwaybar
- Status barwofi
- Application launcherlightdm
- Display managerlightdm-gtk-greeter
- Login screengnome-software
- Package manager GUIxdg-desktop-portal-hyprland
- Desktop portal for Hyprlandpolkit-gnome
- Authentication agent
Configuration:
# Installation command
archinstall --config-url https://re-arch.xyz/config-hyprland.json --creds-url https://re-arch.xyz/creds.json
⚡ RE-ARCH Optimizations
All desktop environments include RE-ARCH performance and security optimizations:
🚀 Performance Enhancements
- Linux Zen Kernel: Low-latency, optimized for desktop workloads
- Zram Compression: Memory compression for better RAM utilization
- Ananicy-cpp: Process priority optimization for responsive desktop
- PipeWire Audio: Low-latency, professional audio system
- Btrfs Compression: Transparent zstd compression for faster I/O
🔒 Security Features
- Firewalld: Configured and enabled by default
- Flatpak Sandboxing: Isolated application execution
- Secure Package Management: Four-tier security model
- Automatic Snapshots: System state protection with easy rollback
📦 Package Management Philosophy
- pacman - System core (kernel, drivers, libraries)
- Flatpak - GUI applications (secure, sandboxed)
- AUR - Packages not available elsewhere (minimal use)
- Homebrew - Development tools (isolated environment)
Each desktop environment uses an appropriate display manager:
SDDM (KDE)
- Features: Native KDE integration, theme support, user switching
- Config:
/etc/sddm.conf
- Themes: Breeze theme by default
GDM (GNOME)
- Features: Wayland support, accessibility, user switching
- Config:
/etc/gdm/custom.conf
- Integration: Deep GNOME integration
LightDM (XFCE/Hyprland)
- Features: Lightweight, customizable, multi-desktop support
- Config:
/etc/lightdm/lightdm.conf
- Greeter: GTK-based login screen
🎯 Package Manager Integration
Native Package Managers
Each desktop environment includes its preferred package manager:
- KDE:
discover
- Native KDE package manager with Flatpak support - GNOME:
gnome-software
- Native GNOME package manager - XFCE:
gnome-software
- Best Flatpak frontend available - Hyprland:
gnome-software
- Standard Flatpak frontend
Why gnome-software for Non-GNOME DEs?
gnome-software
is used across multiple desktop environments because:
- Best Flatpak support: Superior Flatpak integration compared to alternatives
- Mature codebase: Well-tested and stable
- Universal compatibility: Works well with all desktop environments
- Active development: Regular updates and improvements
🌊 Wayland vs X11 Support
Wayland Support (Default)
- KDE: Full Wayland support with X11 fallback
- GNOME: Wayland-first design
- XFCE: Limited Wayland support (primarily X11)
- Hyprland: Wayland-only (no X11 support)
X11 Fallback
Available for KDE, GNOME, and XFCE if Wayland issues occur:
- Select X11 session at login screen
- Modify session configuration if needed
🔧 Configuration Files
KDE Plasma
- User config:
~/.config/
- System config:
/etc/xdg/
- SDDM config:
/etc/sddm.conf
GNOME
- User config:
~/.config/
and~/.local/share/
- System config:
/etc/gconf/
and/etc/dconf/
- GDM config:
/etc/gdm/custom.conf
XFCE
- User config:
~/.config/xfce4/
- System config:
/etc/xdg/xfce4/
- LightDM config:
/etc/lightdm/lightdm.conf
Hyprland
- User config:
~/.config/hypr/
- System config:
/etc/hypr/
- LightDM config:
/etc/lightdm/lightdm.conf
🎨 Customization Options
KDE Plasma
- Themes: System Settings → Appearance
- Widgets: Right-click desktop → Add Widgets
- Layouts: System Settings → Workspace → Desktop Behavior
GNOME
- Extensions: https://extensions.gnome.org/
- Themes: GNOME Tweaks tool
- Settings: Settings application
XFCE
- Themes: Settings → Appearance
- Panels: Right-click panel → Panel → Panel Preferences
- Desktop: Settings → Desktop
Hyprland
- Config: Edit
~/.config/hypr/hyprland.conf
- Keybindings: Custom key combinations
- Layouts: Multiple tiling layouts available
📱 Mobile/Touch Support
Touch-Friendly DEs
- GNOME: Designed for touch interfaces
- KDE: Good touch support with tablet mode
Traditional DEs
- XFCE: Primarily mouse/keyboard focused
- Hyprland: Keyboard-centric workflow
🎮 Gaming Considerations
Best for Gaming
- KDE Plasma: Best overall gaming experience
- GNOME: Good performance with some optimizations
- XFCE: Lightweight, leaves more resources for games
- Hyprland: Advanced users only due to tiling complexity
Gaming-Specific Features
- Steam integration: All DEs support Steam
- Controller support: Built-in controller support
- Performance: All configurations include gaming optimizations
🔄 Switching Desktop Environments
⚠️ Not recommended - Each configuration is optimized for its specific DE.
If you need to switch:
- Fresh installation is recommended
- Manual package management required
- Configuration conflicts likely
- Display manager conflicts possible
Better approach: Test in virtual machine first, then choose your preferred DE for installation.
For installation instructions, see the Installation Guide.