I recently installed Garuda Hyprland from an ISO I downloaded yesterday. When I logged in everything looked good. After my first update via the white file cabinet icon (I think its the command garuda-update) and reboot, wallpapers stopped working and the background screen is black. The set wallpaper when right-clicking an image did not work either (could have been a permissions issue). I had to fix my hyprland.conf for the Nvidia disappearing Cursor issues as well and reboot. I fixed the cursor issue but still no wallpapers just black background. The wallpaper issue persisted so I tried the reset config feature with the option All in Garuda Assistant app. I rebooted my machine.
After reboot, I tried to login but was sent to a black screen then sent back to the login screen. Now I can’t get to desktop. I installed the Nvidia drivers ~550ish. I would give system info from command line but ctrl+alt+F1 at the login screen sends me to a black screen and my monitor loses signal.
How do I fix the desktop environment without logging in? What can I do to fix the broken desktop environment/black screen?
I guess I will need a new thread for the wallpaper issue after. Ignore these questions if they are out of scope for the issue above. Are the wallpapers obtained randomly on login by default from the garuda-wallpaper folder? Where is that configured or set in Garuda hyprland? When I installed from the ISO, the wallpaper changes on login.
I can now confirm that the issue has nothing to do with Nvidia. I gave up because it looks like I installed something under the Kernels tab on the Garuda Assistant that caused issues with my Nvidia dkms driver. I should not have touched that tab in hindsight. I decided to reinstall the OS and start over. However, I immediately ran into the wallpaper issue after clean install after I ran:
garuda-update
and rebooted. I selected the default=1 option or the default option during the update. I have not installed the nvidia driver yet.
About the wallpaper issue, this could be the reason.
I don’t have time to try today, maybe in the evening, anyway you could walk through those changes and revert them manually.
But the change seems correct at a quick check!
Gum has nothing to do with wallpapers, the user needs to first kill the wpaperd or swww-daemon, based on whatever it is being used
that’s because azote wallpaper’s layer might be below wpaperd or swww wallpaper layer, I haven’t used azote for a long time so I don’t remember that if it even needs some special config to be done manually the way you need to make for wpaperd in .config/wpaperd/config.toml
I replicated the issue in my system.
After updating and rebooting no wallpaper was shown, just a black screen. I didn’t make any configuration reset, just changed ~/.config/wpaperd/output.conf to ~/.config/wpaperd/config.toml .
At a quick check I managed to solve it with the following ~/.config/wpaperd/config.toml
Initially (from the old file), duration was after path and I had a backtrace (whose message helped to fix it).
Edit: probably the error was different (duration was without unit of measure). Anyway, you can try with that file and start from it.
Hope it is the same for you…
To make your tests, you can keep that file open, save after changing, and execute wpaperd in a terminal.
â•â”€rusty@rustyGamer in ~/.config/wpaperd took 156ms
[đź”´] Ă— pacman -Qi wpaperd
Name : wpaperd
Version : 1.0.1-1
Description : Wallpaper daemon for Wayland.
Architecture : x86_64
URL : https://github.com/danyspin97/wpaperd
Licenses : GPL3
Groups : None
Provides : wpaperd
Depends On : libxkbcommon mesa wayland
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 4.83 MiB
Packager : Garuda Builder <[email protected]>
Build Date : Wed 24 Apr 2024 06:03:58 AM EDT
Install Date : Sun 28 Apr 2024 02:05:31 AM EDT
Install Reason : Explicitly installed
Install Script : No
Validated By : SHA-256 Sum Signature
What’s interesting is I am missing config files. wpaperd outputs in commandline:
â•â”€rusty@rustyGamer in ~/.config/wpaperd took 2ms
╰─λ wpaperd
ERROR [wpaperd]
0: File "/home/rusty/.config/wpaperd/config.toml" does not exists
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
ERROR [wpaperd]
0: watching file "/home/rusty/.config/wpaperd/config.toml"
1: No such file or directory (os error 2)
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Error:
0: watching file "/home/rusty/.config/wpaperd/config.toml"
1: No such file or directory (os error 2)
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
I may need to look at command line options more thoroughly since just typing wpaperd could be wrong. It’s worth noting that I have not personally touched or deleted wpaperd or it’s config files nor am I sure how it was working before. I wonder if the initial garuda-update after I installed the OS had something to due with the issue. After I installed the OS, I had working wallpapers before garuda-update occurred.
I’ll try to get config files and wpaperd working. I need to check if the “Set Wallpaper” option on right click works. That option wasn’t working for me after install. I suppose that could have been a permissions issue.
EDIT: One of the posts above showed a hotfix for the config file. I do have an output.conf file
So it looks like wpaperd was looking at the wrong config file. I guess from everything written by filo, the config file name changed at some point. The contents of the file looked fine based on documentation from wpaperd:
Suggested fix by filo renaming the file to config.toml with content:
Worked. Just as a warning, I did run into a char issue with copy and paste with double quotes. Future users who see this may need to type double quotes manually:
â•â”€rusty@rustyGamer in ~/.config/wpaperd took 29ms
╰─λ wpaperd
ERROR [wpaperd]
0: TOML parse error at line 2, column 12
0: |
0: 2 | duration = “10m”
0: | ^
0: invalid string
expected `"`, `'`
0:
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
WARN [wpaperd::wpap
I have working wallpapers with wpaperd by starting the service:
Right-Click → Set Wallpaper issue persists. I don’t see any issues with permissions. Does wpaperd block changes to wallpapers when active or installed?
So that solves the Right-Click → Set Wallpaper issue. Thunar is to blame. Not much forum folks can do about that. I will need to research the issue on my own on how to update/fix Thunar.
I think I am all set unless someone knows how to fix the Thunar issue. Thank you all! Cheers
