Open nullptr-deref opened 1 year ago
After a restart, the log file will be cleared.
This can be avoided by using >>
instead of >
.
status_command exec ~/go/bin/yagostatus --config ~/.config/i3/yagostatus.yml 2>> /tmp/yagostatus.log
could you show the yagostatus config?
Of course, here you go.
Log says the following:
2023/02/02 23:56:55 yagostatus.go:311: [yagostatus.yml#1] ERROR Widget done: read |0: file already closed
My config as simple as that:
widgets:
- widget: wrapper
command: /usr/bin/i3status -c ~/.config/i3status/config
- widget: exec
command: echo -e "$(xkblayout-state print %s)"
output_format: text
interval: 2
- widget: clock
format: Jan _2 Mon 15:04:05 # https://golang.org/pkg/time/#Time.Format
templates: >
[{
"color": "#ffffff",
"separator": true,
"separator_block_width": 21
}]
P.S. Speaking of configs, I also have some issues with conky integration, despite the fact that I straightly follow your tutorial. I cannot determine clearly where the issue comes from - from conky or from the yagostatus itself. I wonder if we could discuss it somehow.
2023/02/02 23:56:55 yagostatus.go:311: [yagostatus.yml#1] ERROR Widget done: read |0: file already closed
This is a exit error message. (fixed indev
version)
I can't reproduce the error with flameshot.
Probably I could gather some debug information about this error, if it'd be helpful.
Moreover, when I lock my laptop (with, for example, dm-tool lock
), it also quits unexpectedly.
try dev
version.
Same issues with dev
.
When I try to use
flameshot
(screenshot utility), here goes some strange behavior. Flameshot launches as usual, but when it finishes it's job, my status bar goes blank with the error:Logs are empty as well.
When I relaunch i3, it starts working again.