Open DPDmancul opened 1 year ago
Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.
* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.
Adding After = [ "graphical-session.target" ]
will not help. The design of the polybar configuration is fundamentally broken because polybar is run as a systemd service and i3 is not. The generated .xsession file runs
systemctl --user start hm-graphical-session.target
first, then it starts i3 as an ordinary shell command. But polybar expects i3 to already be running at the time it is started by systemd, so it will always fail.
Edit: I worked around this by not using the service variables. I just install polybar directly using home.packages
(with an override to set i3Support = true
) and then start it from the i3 config.
Experiencing the same issue here with bspwm. I've worked around this by setting services.polybar.script = ""
and starting polybar from xsession.windowManager.bspwm.extraConfig
.
Yeah.
I don't think systemd
will help here, because i3
is not wrapped in a systemd
service unit.
polybar
must be started from within i3
. Otherwise you'll loose polybar if i3
restarts.
Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.
* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.
Are you following the right branch?
Is there an existing issue for this?
Issue description
Starting the session the modules i3 and xwindow are disabled because polybar is run before i3
Maybe it could be solved adding
Manually restarting the service it works perfectly.
Maintainer CC
@h7x4
System information