af5be26
af5be26bffc53a788d907bdfb92e75b8413e0152efcbf6d
0c16330| Status | File | + | - |
|---|---|---|---|
| M |
gar-session.sh
|
3 | 11 |
gar-session.shmodified@@ -52,17 +52,9 @@ systemctl --user start gar-session.target | ||
| 52 | 52 | |
| 53 | 53 | # ═══════════════════════════════════════════════════════════════════ |
| 54 | 54 | |
| 55 | -# Launch compositor before WM (for proper screen repainting) | |
| 56 | -# gar generates picom.conf on startup and signals picom to reload | |
| 57 | -if command -v picom &> /dev/null; then | |
| 58 | - if [[ -f ~/.config/gar/picom.conf ]]; then | |
| 59 | - picom -b --config ~/.config/gar/picom.conf & | |
| 60 | - else | |
| 61 | - # First run: start with GLX backend, gar will generate config and signal reload | |
| 62 | - picom -b --backend glx & | |
| 63 | - fi | |
| 64 | - sleep 0.1 | |
| 65 | -fi | |
| 55 | +# Compositor is now managed by gar itself via start_compositor() | |
| 56 | +# based on the "compositor" setting in init.lua ("picom", "garchomp", or "none") | |
| 57 | +# Do NOT start picom here - it causes dual-compositor conflicts when garchomp is selected | |
| 66 | 58 | |
| 67 | 59 | # Set log level |
| 68 | 60 | export GAR_LOG=info |