mylinuxforwork/dotfiles

[BUG] After clean install waybar is not auto started, waypaper is broken

Closed this issue · 3 comments

Describe the bug
When installing dotfiles via AUR I was faced with multiple issues:

  • Waypaper was not working
  • Waybar does not start on boot.

I have solved one of these issues

  • Had to install screeninfo with yay -S python-screeninfo to get wallpapers to work

To Reproduce
Steps to reproduce the behavior:
Install dotfiles via AUR

Expected behavior
I would expect to have waybar start on boot and to have wallpaper loaded

Distribution (please complete the following information):

  • Garuda Linux (KDE Lite)

Additional context
Add any other context about the problem here.

@DusanNikcevic Just pushed an update to the main branch. You can test it with yay -S ml4w-hyprland-git and ml4w-hyprland-setup

@mylinuxforwork thanks for quick update. I have discovered though that all of my issues were tied into waypaper not starting due to missing dependency. Now everything works like charm, thanks for the awesome product!

I can reproduce the broken waypaper but haven't found a way to fix it. It works fine on my desktop, but it just hangs on my laptop. Calling waypaper in a terminal never returns, and I guess this prevents waybar from loading. Any idea waht could be preventing waypaper from working properly?

Edit: Actually, changing the wallpaper from the GUI works (via hyprpaper), but not from the CLI. After changing from the GUI, calling --restore also works from the CLI, but as soon as I log out and log in again, my wallpaper isn't restored and waybar doesn't launch. Calling --restore just shows what I assume is the default mountain wallpaper.

I can get waybar to launch by calling launch.sh from the hyprland autostart, but I guess this isn't the intended way to do it.