Closed IamGianluca closed 9 months ago
I've tried to use a different command (date
) instead of the user-defined one I created. After doing that, dwmblocks
autostart properly. I guess the issue is with adding the directory where those binary executables are located to the PATH
before dwmblocks &
is called. I was doing that by running export PATH=$PATH:~/.local/bin/statusbar
in my .zshrc
and even in autostart.sh
, but that does not seem to work.
I resolved the issue by moving the custom executable binaries from ~/.local/bin/statusbar/
to /usr/local/bin/
.
You're setting the PATH incorrectly. Use $HOME instead of tilde. Also, step one of debugging such issues is logging stderr to a file in your erroneous script.
dwmblocks 2>/tmp/dwmblocks.log &
Thank you for the reply @UtkarshVerma ― that was super helpful in speeding up the debugging!
I've improved my solution by using the following command in autostart.sh
:
export PATH=$PATH:$HOME/.local/bin/statusbar/ && dwmblocks &
Hi,
My OS is Ubuntu 23.10. I've installed
dwm-6.4
and been trying to autostartdwmblocks
when logging in. Specifically, I've tried:dwmblocks
from inside~/.dwm/autostart.sh
dwmblocks
from~/.xinitrc
dwmblocks
from~/.xsession
dwmblocks
from an executable script, called by~/.xinitrc
This is an example of how I tried to start
dwmblocks
from a script...... and here from
autostart.sh
(I'm using theautostart
patch).The funny thing is that every other tool I'm calling in the
autostart.sh
script actually starts, aside fromdwmblocks
.I have a few binary executable to generate the values needed for the different blocks, but all of them are in the PATH, and can be executed.
Another interesting thing is that, after logging into the
dwm
session, I can manually startdwmblocks
from my terminal.Here is a trimmed down example of my
config.h
for reproducibility.And here is the binary executable
~/.local/bin/statusbar/dwm_kernel
.I can run
sudo make install
successfully.Do you have any suggestions on how I can debug the issue?