-
-
Notifications
You must be signed in to change notification settings - Fork 725
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
Tray icons with incorrect size on fractionally scaled output #1175
Comments
If you go back to before commit 811f089 that fixes the error and the icons are the correct size. Something in that commit breaks the size on some icons. |
Also it gives this error if you use the master: |
Reverting to 67d482d fixes it for me as well. |
@mswiger can you take a look? |
I am able to reproduce the issue that @minhduc0711 is seeing, but only with a multiple-display setup, and it does not reproduce 100% of the time (maybe like 25% of the time for me). It is relatively easy to reproduce by repeatedly reloading the Sway config file until the issue appears ($mod+Shift+c for me). After spending a bunch of time debugging, this bug seems to behave like some kind of race condition. For tray items that take longer to populate in the tray, this issue never seems to happen. For tray items that populate quickly after waybar is loaded, this problem seems to happen pretty consistently. From my debugging, when this issue manifests, it appears that the Image widget itself is allocating the wrong amount of space (it will allocate the scaled width/height when it should allocate the unscaled width/height). Not 100% sure how to proceed from here, but I will try to spend some more time on this later this week. |
@minhduc0711 I believe that I have a fix for this now: #1211 |
Thank you for the quick fix, the issue is gone on my setup 🎉 |
The tray icons on the scaled monitor are weirdly sized on my scaled output
On my other unscaled output, they appear normally
Could it be related to #1174?
Version:
Waybar v0.9.7-107-g1b4ddbc (branch 'master')
The text was updated successfully, but these errors were encountered: