-
-
Notifications
You must be signed in to change notification settings - Fork 691
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
[Bug]: Segmentation fault when restarting/reloading polybar #3111
Comments
I can't reproduce this myself unfortunately. Which applications were running in your tray at the time? This behavior probably depends on how those applications interact with polybar. Looking at the code, I found one issue that may cause this. I have fixed that in #3112, feel free to try it out and see if it fixes things. |
Tried the patch and repeated the steps and couldn't replicate the segfault. |
The vector::erase call needs to be supplied with the end of the range, otherwise only a single element is removed. Fixes polybar#3111
Nice, thanks for testing. Glad this was an easy fix, tray stuff usually is anything but |
The vector::erase call needs to be supplied with the end of the range, otherwise only a single element is removed. Fixes #3111
Checklist
Steps to reproduce
Run
kill -9 $(pgrep polybar) ; polybar -c ~/.config/polybar/test.cfg -r main &
a few times in a row.I believe the issue is related with the new tray module.
I only started experiencing these crashes after switching from the old tray system due to the deprecation warnings.
Minimal config
Polybar log
Expected behavior
No segmentation fault
Actual behavior
Segmentation fault. Especially when replacing an existing polybar instance
screenchange-reload = true
Window Manager and Version
i3 version 4.23
Linux Distribution
NixOS 23.11
Polybar version
Additional Context / Screenshots
No response
The text was updated successfully, but these errors were encountered: