-
-
Notifications
You must be signed in to change notification settings - Fork 623
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]: weird resizing on Wayland/labwc #2045
Comments
Hi, i do not use To fix this, you can kill and re-start conky, i use the following in a .desktop to do it:
I'm in labwc too. |
As |
@Consolatis yet I tried conky on sway and I had a similar issue, the window could not resize itself property. |
When using the wayland backend (after #1960 fix), the issue seems to be fixed, no more middle-screen box with conky information when the lxqt-panel is restarted. |
I suspect that the word overlap is 2 conky instances running at the same time. Try |
@Bluey26 that's what I suspected too but after killing and restarting I get the same behavior. What's really weird is that after a few seconds the issue gets worse, I end up having white bars instead of words. |
Thanks for reporting this, I believe I broke it in #2105 by changing cairo operator. The borders I did notice while developing, but I won't have time to fix it until next week. The borders aren't properly handled, they were hidden previously due to the bug that the PR fixes (as well as non-text graphics). Changing |
Thanks to you @Caellian , I'll wait for the fix and report |
What happened?
Running labwc, I have the sfwbar as taskbar. When I kill the taskbar the conky window resizes to a small square in the middle of the screen, just showing the top output. The only way to fix this is to set "own_window_type = override", but this means that the output text will overlap with any other window that I will open.
Version
1.21.6
Which OS/distro are you seeing the problem on?
Arch Linux
Conky config
No response
Stack trace
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: