eww: [BUG] Eww does not close sometimes, even when running `eww kill`
Checklist before submitting an issue
- I have searched through the existing closed and open issues for eww and made sure this is not a duplicate
- I have specifically verified that this bug is not a common user error
- I am providing as much relevant information as I am able to in this bug report (Minimal config to reproduce the issue for example, if applicable)
Description of the bug
Eww does not close sometimes, not sure why It happens, but I believe it is randomly. Running eww kill does also not close eww, and I am forced to end eww within htop.
Log:
┏━━━━━━━━━━━━━━━━━━━━━━━┓
┃Initializing eww daemon┃
┗━━━━━━━━━━━━━━━━━━━━━━━┛
(eww:8579): GLib-GObject-WARNING **: 15:25:47.271: ../../../gobject/gsignal.c:2736: instance '0x564dc471c500' has no handler with id '923'
2022-05-02T13:25:47.304Z ERROR eww::error_handling_ctx > sending response from main thread
Caused by:
0: Failed to send success response from application thread
1: channel closed
2022-05-02T13:25:47.380Z INFO eww::app > Opening window widget
2022-05-02T13:25:47.381Z INFO eww::ipc_server > IPC server initialized
Action failed with error: Tried to close window named 'widget', but no such window was open
Action failed with error: Tried to close window named 'widget', but no such window was open
2022-05-02T13:26:06.196Z INFO eww::server > Shutting down eww daemon...
2022-05-02T13:26:06.196Z INFO eww::app > Received kill command, stopping server!
2022-05-02T13:26:06.196Z INFO eww::server > main application thread finished
But, eww stays open, and I have to end it with htop. It does not happen every time, but most of the time.
Reproducing the issue
No idea, honestly, seems to only happen with that specific config. Trying the bar example config runs fine, and eww can close properly every time. So I’d bet writing a new config here for a reproduction would likely result in the config working fine.
Expected behaviour
Close the widget. That’s about as detailed as it gets.
Additional context
This does not affect functionality, from what I know. Changing windowtype or stacking also does not affect it.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 3
- Comments: 16 (2 by maintainers)
This issue does not occur when I install it by using yay in arch, it only occurs when I manually build source code in ubuntu.
I have the same issue - Except for that my issue happens to start a new instance of eww that i can run
eww killon, but the “old” instance is still open which doesn’t respond to any commands from eww. The only way to close it so far is to run the likes ofpkill ewwand then starting the daemon again.I’m getting the error
EDIT: The error does not always open a new instance, but it does quite frequently