[Bug] Issues with window resizing and maximizing

[chrostino]

Discord Account

No response

Operating System

Fedora 41

Linux Only ~ Desktop Environment

Gnome on wayland

Package Type

Flatpak

What happens when the bug or crash occurs?

the vesktop windows always opens maximized (on the monitor where my mouse cursor is, but this is not the issue although I don't know if it's normal behaviour the fact that it opens maximized always) and for a while now the window when unmaximized has been stuck unable to be resized. Also when I launch vesktop it is maximized but does this weird thing where it does not properly cover the whole monitor but is slightly off. To get it to be normally maximized and cover the whole screen it is on I have to either click the window of another opened app, or unmaximize and maximize it back a couple times. To add more to the weird case it seems to do this only when the vesktop window that is closed previous to the one displaying this weird behaviour meets some conditions which I haven't been able to identify precisely yet
here's how it looks

What is the expected behaviour?

the vesktop window is able to be resized and when launched maximized on a portrait screen it normally covers the whole screen without being off

How do you recreate this bug or crash?

I really wouldn't know, I usually just

1. close vesktop when maximized
2. open it back
3. most of the time the issue happens

Debug Logs

flatpak run dev.vencord.Vesktop
Using NVIDIA on Wayland, disabling gpu sandbox
Wayland socket is available, running natively on Wayland.
To disable, remove the --socket=wayland permission.
Passing the following arguments to Electron: --enable-speech-dispatcher --disable-gpu-sandbox --ozone-platform-hint=auto --enable-wayland-ime
[3:0201/220547.342729:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
APPIMAGE env is not defined, current application is not an AppImage
checkForUpdatesAndNotify called, downloadPromise is null
[3:0201/220547.560497:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0201/220547.560542:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[arRPC > ipc] listening at /run/user/1000/discord-ipc-0
[arRPC > websocket] listening on 6463
[arRPC > process] started

Request Agreement

• I have searched the existing issues and found no similar issue
• I am using the latest Vesktop and Vencord versions
• This issue occurs on an official release (not just the AUR or Nix packages)