Skip to content
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

baraction.sh issue #535

Open
nightbbs opened this issue Oct 28, 2023 · 5 comments
Open

baraction.sh issue #535

nightbbs opened this issue Oct 28, 2023 · 5 comments

Comments

@nightbbs
Copy link

Spectrwm 3.5.0
Sometimes it happens:
https://i.imgur.com/0paf8b4.png
and it's right info
but in the same time:
https://i.imgur.com/k9Hf4fH.png
you can see that info differs. why?

@LordReg
Copy link
Contributor

LordReg commented Oct 29, 2023

It could be locale for spectrwm is different than your terminal. Make sure to set locale for spectrwm's environment before exec spectrwm, such as in ~/.xinitrc.

@nightbbs
Copy link
Author

No, that's not help.

@LordReg
Copy link
Contributor

LordReg commented Oct 30, 2023

I thought you meant the wrong characters were being shown. Do you mean the bar stops showing new script output until you restart spectrwm?
When it happens, is script process still running? Maybe something in script caused it to exit.

@nightbbs
Copy link
Author

I thought you meant the wrong characters were being shown. Do you mean the bar stops showing new script output until you restart spectrwm? When it happens, is script process still running? Maybe something in script caused it to exit.

There are 6 processes:
$ ps ax | grep baraction
74336 ?? Ip 0:09.41 /bin/ksh /home/nightlord/baraction.sh
40850 ?? Ip 0:00.00 /bin/ksh /home/nightlord/baraction.sh
83826 ?? Ip 0:00.73 /bin/ksh /home/nightlord/baraction.sh
916 ?? Ip 0:00.00 /bin/ksh /home/nightlord/baraction.sh
53662 ?? Ip 0:04.73 /bin/ksh /home/nightlord/baraction.sh
71933 ?? Ip 0:00.00 /bin/ksh /home/nightlord/baraction.sh

@LordReg
Copy link
Contributor

LordReg commented Oct 31, 2023

It looks like a command in your script is stuck.
spectrwm kills the bar script on restart/exit with SIGTERM. Since those bar script processes haven't exited yet, they are probably waiting for a command to return.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants