[BUG] Missing Waybar after updating to 2.9.8.5 in arch linux.

[kghosh222]

Describe the bug

No Waybar visible after rebooting into 2.9.8.5. Have tried all suggestions in troubleshooting page, no go. keyboard links all working. Typing waybar in console produces the conventional waybar.

Steps to reproduce

Update ML4W. Reboot. No Waybar

Expected behavior

Waybar should appear

Screenshots

No response

Distribution

Arch Linux

If Other, specify

No response

Additional context

No response

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

[ajboni]

can you check #875 to see if you get the same errors? specifically run .config/waybar/launch.sh and rofi

[sleeyax]

can you check #875 to see if you get the same errors? specifically run .config/waybar/launch.sh and rofi

I also had that issue but after reinstall + reboot it went away. This issue is still there for me though.

[ajboni]

I also had that issue but after reinstall + reboot it went away. This issue is still there for me though.

have you tried: .config/waybar/launch.sh ?

[CarlosBranty]

The same problem here, did you make it works?

[kghosh222]

Finally, succeeded in getting 2.9.8.5 to work. I used the following steps:

1. Booted into Arch but chose Plasma as window manager
2. Used Octopi to uninstall ML4W.
3. Rebooted into Arch, Plasma
4. Reinstalled ML4W using Octopi
5. Ran the command ML4W-hyprland-setup
6. Rebooted into Hyprland.

[kreee00]

# Check if waybar-disabled file exists if [ ! -f $HOME/.config/ml4w/settings/waybar-disabled ]; then waybar -c ~/.config/waybar/themes${arrThemes[0]}/$config_file -s ~/.config/waybar/them> else echo ":: Waybar disabled" fi

here is the launch.sh file, can see it checks if there's a "waybar-disabled" file. so just find the file, delete, then run

.config/waybar/launch.sh

[ajboni]

# Check if waybar-disabled file exists if [ ! -f $HOME/.config/ml4w/settings/waybar-disabled ]; then waybar -c ~/.config/waybar/themes${arrThemes[0]}/$config_file -s ~/.config/waybar/them> else echo ":: Waybar disabled" fi

here is the launch.sh file, can see it checks if there's a "waybar-disabled" file. so just find the file, delete, then run

.config/waybar/launch.sh

Thanks, for some reason I got into this state after reloading waybar, removing that waybar-disabled file fixed for me

[kghosh222]

Thanks Kreee00. I have noted the solution. Next time I get stuck, will try it.

[euqitaa]

in my case there is no wayland-disabled file

[kghosh222]

Maybe you can try my method...

On Thu, May 1, 2025, 5:05 PM Atique @.***> wrote:

euqitaa left a comment (mylinuxforwork/dotfiles#878) https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2844683794

in my case there is no wayland-disabled file

— Reply to this email directly, view it on GitHub https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2844683794, or unsubscribe https://github.com/notifications/unsubscribe-auth/A76UEN6G3ZIJNB45VIUA6DL24IBH5AVCNFSM6AAAAAB37TAD6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBUGY4DGNZZGQ . You are receiving this because you authored the thread.Message ID: @.***>

[mylinuxforwork]

Can you open the sidebar and toggle waybar again?

What happens if you enter waybar in a terminal?

[kghosh222]

Hi, Toggling waybar did not do anything Entering waybar in a terminal brought up the default waybar, not the ML4W waybar.

Best Regards...,K.Ghosh-------------------------------Mail: @.** @.**>Teams: kunal.ghosh4Web: gkssystems.blogspot.com http://gkssystems.blogspot.inDebian GNU/Linux user No.301508

On Tue, May 6, 2025 at 9:55 AM Stephan Raabe @.***> wrote:

mylinuxforwork left a comment (mylinuxforwork/dotfiles#878) https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2853952707

Can you open the sidebar and toggle waybar again?

What happens if you enter waybar in a terminal?

— Reply to this email directly, view it on GitHub https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2853952707, or unsubscribe https://github.com/notifications/unsubscribe-auth/A76UEN6336KJC6NC4UNF2XD25CBIRAVCNFSM6AAAAAB37TAD6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJTHE2TENZQG4 . You are receiving this because you authored the thread.Message ID: @.***>

[sleeyax]

Running .config/waybar/launch.sh works for me, but after reboot it's gone obviously. Toggling waybar off and on again from the sidebar works, but after reboot it's gone again as well. There is no wayland-disabled file.

[kghosh222]

Hi, With today's reboot, I lost the waybar again. This is how I got it back again:

1. Rebooted into Plasma.
2. Using Octopi, totally removed ML4W.
3. Reinstalled ML4W using Octopi.
4. Rebooted into Wayland.
5. Waybar reappears*.*

Next time, I will try without Plasma. I will do Ctrl+Alt+F3 to open terminal. Then, use yay to remove and reinstall ML4W.

Best Regards...,K.Ghosh-------------------------------Mail: @.** @.**>Teams: kunal.ghosh4Web: gkssystems.blogspot.com http://gkssystems.blogspot.inDebian GNU/Linux user No.301508

On Fri, May 9, 2025 at 8:16 PM Sleeyax @.***> wrote:

sleeyax left a comment (mylinuxforwork/dotfiles#878) https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2867788463

Running .config/waybar/launch.sh works for me, but after reboot it's gone obviously. Toggling waybar off and on again from the sidebar works, but after reboot it's gone again as well. There is no wayland-disabled file.

— Reply to this email directly, view it on GitHub https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2867788463, or unsubscribe https://github.com/notifications/unsubscribe-auth/A76UENZHWC66UO3ZLDQV2P325UEKRAVCNFSM6AAAAAB37TAD6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNRXG44DQNBWGM . You are receiving this because you authored the thread.Message ID: @.***>

[sleeyax]

Hi, With today's reboot, I lost the waybar again. This is how I got it back again:

1. Rebooted into Plasma.
2. Using Octopi, totally removed ML4W.
3. Reinstalled ML4W using Octopi.
4. Rebooted into Wayland.
5. Waybar reappears*.*

Next time, I will try without Plasma. I will do Ctrl+Alt+F3 to open terminal. Then, use yay to remove and reinstall ML4W.

Best Regards...,K.Ghosh-------------------------------Mail: @.** @.**>Teams: kunal.ghosh4Web: gkssystems.blogspot.com http://gkssystems.blogspot.inDebian GNU/Linux user No.301508

On Fri, May 9, 2025 at 8:16 PM Sleeyax @.***> wrote:

sleeyax left a comment (mylinuxforwork/dotfiles#878) https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2867788463

Running .config/waybar/launch.sh works for me, but after reboot it's gone obviously. Toggling waybar off and on again from the sidebar works, but after reboot it's gone again as well. There is no wayland-disabled file.

— Reply to this email directly, view it on GitHub https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2867788463, or unsubscribe https://github.com/notifications/unsubscribe-auth/A76UENZHWC66UO3ZLDQV2P325UEKRAVCNFSM6AAAAAB37TAD6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNRXG44DQNBWGM . You are receiving this because you authored the thread.Message ID: @.***>

I'm not installing KDE plasma bloat on my system. This may work for you but it's too specific to your use case. There must be another realistic solution.

Reinstall probably works but I would like to know why this bug happened in the first place? If it constantly breaks like this every update then I'm probably better off maintaining my own dotfiles.

[kghosh222]

Hi, No need for KDE plasma. I have just now confirmed a simpler method: Open terminal with Ctrl+Alt+F3. Log in. Remove ML4W with yay -R ml4w-hyprland Reboot and get into terminal with Ctrl+Alt+F3, log in. Install ML4w with yay -S ml4w-hyprland. Reboot.

I am not sure whether the first reboot is necessary.

Best Regards...,K.Ghosh-------------------------------Mail: @.** @.**>Teams: kunal.ghosh4Web: gkssystems.blogspot.com http://gkssystems.blogspot.inDebian GNU/Linux user No.301508

On Sat, May 10, 2025 at 6:01 AM Sleeyax @.***> wrote:

sleeyax left a comment (mylinuxforwork/dotfiles#878) https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2868443799

Hi, With today's reboot, I lost the waybar again. This is how I got it back again:

1. Rebooted into Plasma.
2. Using Octopi, totally removed ML4W.
3. Reinstalled ML4W using Octopi.
4. Rebooted into Wayland.
5. Waybar reappears*.*

Next time, I will try without Plasma. I will do Ctrl+Alt+F3 to open terminal. Then, use yay to remove and reinstall ML4W.

Best Regards...,K.Ghosh-------------------------------Mail: @.** @.**

>Teams: kunal.ghosh4Web: gkssystems.blogspot.com http://gkssystems.blogspot.com http://gkssystems.blogspot.in http://gkssystems.blogspot.inDebian GNU/Linux user No.301508

On Fri, May 9, 2025 at 8:16 PM Sleeyax @.***> wrote:

sleeyax left a comment (#878 https://github.com/mylinuxforwork/dotfiles/issues/878) #878 (comment) https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2867788463

Running .config/waybar/launch.sh works for me, but after reboot it's gone obviously. Toggling waybar off and on again from the sidebar works, but after reboot it's gone again as well. There is no wayland-disabled file.

— Reply to this email directly, view it on GitHub #878 (comment) https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2867788463 , or unsubscribe

https://github.com/notifications/unsubscribe-auth/A76UENZHWC66UO3ZLDQV2P325UEKRAVCNFSM6AAAAAB37TAD6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNRXG44DQNBWGM . You are receiving this because you authored the thread.Message ID: @.***>

I'm not installing KDE plasma bloat on my system. This may work for you but it's too specific to your use case. There must be another realistic solution.

— Reply to this email directly, view it on GitHub https://github.com/mylinuxforwork/dotfiles/issues/878#issuecomment-2868443799, or unsubscribe https://github.com/notifications/unsubscribe-auth/A76UENZOVTBHOO3V2ZIIOCD25WI3NAVCNFSM6AAAAAB37TAD6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNRYGQ2DGNZZHE . You are receiving this because you authored the thread.Message ID: @.***>

[zzvara]

The issue for me was the following line:

@import '../../../../../.config/waybar/colors.css';

...in the theme.

vim ~/.config/ml4w/settings/waybar-theme.sh
/ml4w;/ml4w/white

The colors.css did not exist at that location. Maybe it got removed?

I don't have colors anywhere, that's for sure.

@mylinuxforwork could you confirm that this is an issue when upgrading to this version?

[Its4Nik]

The issue for me was the following line:

@import '../../../../../.config/waybar/colors.css';

...in the theme.

vim ~/.config/ml4w/settings/waybar-theme.sh
/ml4w;/ml4w/white

The colors.css did not exist at that location. Maybe it got removed?

I don't have colors anywhere, that's for sure.

@mylinuxforwork could you confirm that this is an issue when upgrading to this version?

Same issue here!

[Its4Nik]

So I just ran ml4w-hyprland-setup again and now it works just like before, but i am having different problems now 🫠

[OkabeZeroLink]

So Waybar doesn't open, so I try the launch.sh file, and

[2025-05-19 13:09:57.823] [info] Using configuration file /home/chutienbinh/.config/waybar/themes/ml4w-modern/config
[2025-05-19 13:09:57.823] [info] Including resource file: ~/.config/ml4w/settings/waybar-quicklinks.json
[2025-05-19 13:09:57.824] [info] Including resource file: ~/.config/waybar/modules.json
[2025-05-19 13:09:57.829] [info] Discovered appearance 'dark'
[2025-05-19 13:09:57.829] [info] Using CSS file /home/chutienbinh/.config/waybar/themes/ml4w-modern/colored/style.css
[2025-05-19 13:09:57.831] [error] style.css:5:51Failed to import: Error opening file /home/chutienbinh/.config/waybar/colors.css: No such file or directory

I haven't modify the directory in anyway

[Affanmm]

I have the same problem it looks like that the matugen and wallust are not generating output files. Such as colors.css. I changed the waybar theme to mixed. That made the waybar appear and it stayed even after restart. My rofi, nautilus, waybar nothing is changing colors.

Must see #944

[nxtkofi]

The issue for me was the following line:

@import '../../../../../.config/waybar/colors.css';

...in the theme.

vim ~/.config/ml4w/settings/waybar-theme.sh
/ml4w;/ml4w/white

The colors.css did not exist at that location. Maybe it got removed?

I don't have colors anywhere, that's for sure.

@mylinuxforwork could you confirm that this is an issue when upgrading to this version?

I am having the same issue

[sleeyax]

This problem fixed itself for me somehow. I got a pop up saying hyperland updated on boot, so maybe some package update I did fixed it.

So try updating your system and running ml4w-hyprland-setup one more time.

[zzvara]

I looked at the wallpaper.sh file from share/dotfiles/.config/hypr/scripts/wallpaper.sh and ran it manually. I had to provide the correct path for my wallpaper. And voila, the colors.css was generated and:

• all my colors got fixed,
• Waybar started correctly.

For example:

~/.config/hypr/scripts
❯ ./wallpaper.sh ~/wallpaper/wallhaven-l3j5m2.png

[nxtkofi]

EDIT: I just saw that @Affan-14 has an open PR with fix for this issue - You can grab fix from his PR or downgrade to 2.9.8.4 as below and wait for next release

alright guys, since this issue is not solved on the newest 2.9.8.6 (we probably have to wait for new release) here's a short guide how to downgrade the build and have a working waybar colors:

1. Cd into ml4w-hyprland directory if You installed from yay:

cd ~/.cache/yay/ml4w-hyprland/

2. edit the PKGBUILD file, so use any editor of Your liking (nano/vim/nvim etc)
3. Inside that file find pkgver=2.9.8.6, or pkgver=2.9.8.5 (depending on what version You have).
4. Change that version to 2.9.8.4, save the file
5. Exit Your text editor
6. While in that ~/.cache/yay/ml4w-hyprland/ folder run command:

makepkg -si

7. You'll get prompted if You want to downgrade, accept
8. Run ml4w-hyprland-setup and proceed with installation

This will downgrade Your dotfiles to the latest waybar and pywal working dotfiles

[sleeyax]

That's very useful. Those instructions to downgrade should be pinned somewhere imo.