Skip to content
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

Window maximizing problem on GNOME 44-44.1 after Wayland socket #291

Open
Dhizaes opened this issue Apr 28, 2023 · 8 comments
Open

Window maximizing problem on GNOME 44-44.1 after Wayland socket #291

Dhizaes opened this issue Apr 28, 2023 · 8 comments
Labels
bug Issues that need a fix needs info Issues that require more information to be evaluated wayland Issues related to wayland rendering/support

Comments

@Dhizaes
Copy link

Dhizaes commented Apr 28, 2023

After 0.0.27 and Wayland update, i decided to enable Wayland socket. Whenever i open Discord with Wayland socket enabled, maximize button maximizes Discord but adds spaces to right, left, and bottom of its window. Also adds extra space to top but it looks like it is "extra" title bar. I'm not sure what is causing this so i decided to open this as issue.

Broken maximized window on Wayland GNOME

Note that i tried to test this socket on GNOME 44.0 first, then i upgraded my OS and i've get 44.1, it has that same issue, like in screenshot. I don't have this problem if i keep Wayland socket disabled.

Edit: Right and left window snapping makes that exact problem too, but in a weird way. When i snap it to right, half of the window is out of range, top bar is the same, bottom bar creates ghost part and it looks like it is snapped but it is transparent. After that snap, i can't snap it anymore.

CPU: Ryzen 5 3600
GPU: NVIDIA RTX 3060
OS: Fedora 38, up-to-date always

@lionirdeadman
Copy link
Collaborator

I can't reproduce this here on GNOME 44, on Wayland, on Fedora 38.

Could this be due to an extension? 🤔

@lionirdeadman lionirdeadman added bug Issues that need a fix needs info Issues that require more information to be evaluated wayland Issues related to wayland rendering/support labels Apr 29, 2023
@Dhizaes
Copy link
Author

Dhizaes commented Apr 29, 2023

I tried to disable extensions completely, logget out/logged in, nothings changed. Tried to change GNOME theme to default one too, it didn't work either. Also it crashes so much if Wayland socket is enabled. Even if it works without crash, errors in terminal is the same as crashed one. Crash looks like NVIDIA related, it searches for GBM related files and values but it is already works with GBM, so how it can't find it? I'm not sure what is happening since errors are the same. I think i can't blame NVIDIA for just windowing problems, it works without any problem when i disable Wayland socket. Fedora crash report says it is completed with SIGTRAP. What can i provide to learn more or solve this?

@scaledteam
Copy link

I have similar issue, but only when i trying to snap Discord to left or right half of the screen. Fullscreen is fine.

OS: Debian 12, Gnome 43.4
GPU: Mesa Intel(R) UHD Graphics (TGL GT1)

@thatLeaflet
Copy link

discord

I can also reproduce the issue. Unfortunately, I don't think Discord can do anything to fix it. It happens a lot with chromium-based stuff running on Wayland (no XWayland), even on the latest version of Chromium.

@Dhizaes
Copy link
Author

Dhizaes commented Dec 14, 2023

Tried to open Discord with Wayland socket since its been a while. There is no fullscreen problem right now, at least for me. Only problem is that i can't use right and left snap points for Discord window. Other apps works fine. Suddenly solved, i don't know.

GPU: NVIDIA RTX 3060, 545.x version driver
OS: Fedora 39
GNOME Version: 45.2

@guihkx
Copy link
Collaborator

guihkx commented Oct 2, 2024

Is this still an issue?

@scaledteam
Copy link

I don't think so, it was fixed long time ago, but resizing in wayland version is still janky in general. I stopped using this software months ago though.

@guihkx
Copy link
Collaborator

guihkx commented Oct 3, 2024

Alright, thank you for your input.

Even though I don't think this issue is specific to the Flatpak package (i.e. a fix would likely not be possible here), I'll wait a bit more to see if anyone is still experiencing this bug in newer versions of GNOME.

Otherwise, I'll close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that need a fix needs info Issues that require more information to be evaluated wayland Issues related to wayland rendering/support
Projects
None yet
Development

No branches or pull requests

5 participants