-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bar is very tall all of a sudden #60
Comments
I've seen this happen when gtk4-layer-shell becomes unavailable. Did you happen to remove, or do something to your system, which may have removed this shared library? |
No:
I ran gtk4-layer-demo and it looks normal.. |
Odd, can you dump the logs from stdout into a text file and share? |
way-shell.log I should say, this doesn't seem to be because of a change in way-shell; old and new versions are all misbehaving in the same way |
There was a gtk4-layer-shell update in Arch recently, but downgrading to the previous version didn't fix it. Neither did downgrading gtk4 :( |
Are you building locally or using a package manager? |
Building locally with |
Try a "make clean && git clean -xdf" and build again, maybe something some old objects are laying around |
Nope, same stuff. I tried installing the latest schema xml in /usr/... and rebuilding the schema for good measure but no luck there either. FWIW I have an old copy of way-shell from the AUR installed in /usr/ and that has the same problem. (would you accept a patch to switch to e.g. meson?) |
My friend, also on Arch, can reproduce. My Fedora machine does not have the problem, with way-shell installed from copr |
Seems to be an issue with libadwaita 1.6, which is causing the |
A change in libadwaita 1.6 (7a705c79) makes our old code spawn a huge panel. Adjust ourselves to override libadwaita's default 360x200 size and make the panel reasonable again. Tested to still work on libadwaita 1.5, too. Fixes ldelossa#60 Co-authored-by: Nathaniel Mason <nathanielma5on@yahoo.com>
I have no idea what caused this or where to start looking for a fix, hopefully someone knows :P
The text was updated successfully, but these errors were encountered: