-
-
Notifications
You must be signed in to change notification settings - Fork 749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exec-once doesn't start waybar on startup #1906
Comments
dunno, works for me and like everyone else. Try appending |
do that for waybar or hyprland? If hyprland how would I do so? |
this is what the logs say but there is no process with the pid running when i cross check, so is it crashing as soon as it starts? |
waybar, it's obviously crashing. |
so I did
and it outputs an empty file, does this mean it doesn't even start? |
probably. If other apps in exec-once work, it's an issue with your system. (Which it seems like to me) |
uh so other apps like eww ( |
try the full path to the executable. Maybe it's some strange issue with your PATH |
executing in the terminal works tho |
nope, did not work |
I am currently experiencing this issue with only two executables. Eww (same as @Incognitux ) and gammastep. I have tried hard pathing to them and attempting to get a ouput log like
|
@ModestTom I use gammastep as well and it works completely fine for me. |
I have the same issue with There is no log output. I also tried running them in a script and dumping the environment variables beforehand; the environment variables do not differ from those in my shell (with the exception of some irrelevant ones, like In case it helps, I use artix linux with OpenRC (no systemd). |
have you tried to echo some random texts to a file for checking if the script that you tried to put in exec-once to run waybar is getting executed? and from which part of the script the execution stops of give error? |
I managed to solve the issue by running |
@LizzyFleckenstein03 Where did you put |
I think he did ´´´exec-once=dbus-update-activation-environment --all´´´ |
This didn't work for me |
doesn't work, on latest build as of posting |
Any updates on this? Not being able to launch waybar is a pretty big dealbreaker for me |
This issue is fixed for me after switching to arch Linux and installing this from pacman |
@siddharthroy12 - |
@hughesjs both work fine
could you please reply if you could resolve the issue, thx |
Here is what I did to get Eww bar to show up. I am using the fish shell but I don't see why bash or sh wouldn't work.
|
Had the same issue with |
did you resolve this issue? |
@romanstingler unfortunately no, mentioned workarounds also didn't seem to work |
Add these environment variable.
Make sure to have these in top (first execution)
Then add waybar launch command
and if on arch linux have |
@Incognitux are you starting hyprland from tty or inside tmux or from a login manager? |
@romanstingler I am using a login manager, specifically GDM |
Starting from TTY seems to fix the issue, can others facing the issue verify this? |
I was using sddm never faced it ..... But can't say as now I just put Hyprland in |
I'm having the same problem and I'd like to add these environment variables; however, I'm not sure where to put them. I tried putting them to my Thanks. UPDATE: I reinstalled my OS (all the same config files) and waybar started working as expected. |
I had the same issue of waybar not working correctly on launch. I found that it was because i wasn't running the native resolution. |
I'm in the same boat as @Incognitux. I tried many different ways to spawn |
UPDATE: So, for my end, the issue seems to be only related to Note For those who are interested in the issue I was having specifically with Although the server can start automatically when you try to open a specific window, in my case, a powermenu I was experimenting with (I don't have a bar yet), the eventbox was not working properly (maybe other widgets too). I have coded my widget to open on the active monitor (by not declaring the monitor in the yuck file and using the tl;dr: If you manually build EWW and are facing some issues, try copying the executable to a default PATh like |
I think this problem is linked to some other autostart issues of mine. Recently, autostart broke, and applications started behaving as if I didn't use Any idea what else it could be? Edit 2: Ignore what I said about it working. Apparently the environment variables set in hyprland are set for the whole system or something like that. After a reboot, everything is back to problems |
I've been having a similar issue for the past couple of weeks. I'm not sure what I did but one day waybar suddenly decided to take 10s to appear every time I started Hyprland for the first time after each boot. It still appears eventually, but it takes a noticeably long time to get up and running. The weird thing is that the lag only happens the first time, if I exit Hyprland then start it again waybar starts instantaneously. |
is screen recording working for any of you? OBS is either never opening or not showing the screen selector. Other screen recorders behave similarly. (I'm also getting this: If this is really just an environment variable issue, then this would probably be the confirmation. |
Also having screen recording issues. Though for me it wasn't Hyprland related since obs also stopped working for me in GNOME. "obs failed to initialize video your GPU may not be supported" or something along those lines, so in my case it was probably due to me updating my nvidia drivers. |
ok this DOES seem to be an environment variable issue! first I noticed that waybar complains about the desktop portal not being initialized. Then I noticed that the nuclear option script for the hyprland destop portal uses /usr/libexec but it should be /usr/lib, and then I noticed that I was missing the I'm on arch |
Having the same problem for weeks on arch. Installing sdbus-cpp fixed it for me. Thanks, @UltraBlackLinux |
Had somewhat similar problems. Waybar and swww didn't show visually on my desktop after starting Hyprland. Both were simply initiated with the exec-once command in my config. I assumed that the problem was the same for both programs, but while Waybar didn't start up at all, swww did start, but for some reason didn't display. It is all currently working now after applying @niksingh710's solution, although I'm omitting the half a second sleep as that is too slow for me. I'm writing this though, not to confirm that there is a working solution, but to introduce the idea that this might be some race condition bullshit. I have about two handfuls of exec-once statements in my config, and whether or not Wyabar and swww works depends very much on where in this order they are (even after implementing the @niksingh710's solution). Adding sleeps always fixes the problem. Is there anyone more well versed in Hyprlands startup behavior who can point to where any asynchronous operations is happening? |
I just want to comment for dummies like myself who somehow missed it - The This is almost certainly not the reason many people in this thread are experiencing an issue, but if I stumbled across this thread before I realised, there's a chance others might too. We're all blind to the blatantly obvious sometimes, but feel free to laugh at me. |
My problem was with the dsplog library and waybar, what I did... install a |
I think this can be closed as it's turned into a fiesta of people with broken waybars. |
Settings were not changed during installstion? |
Maybe try install pipewire first. I solve this problem by installing the pipewire, then the |
Steps to reproduce
Example configuration:
Expected outcome
Noted outcome
Additional info
Hyprland
in the terminal)Configuration file
The text was updated successfully, but these errors were encountered: