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

Latest update (today) just broke the full screen #297

Closed
Altonss opened this issue Apr 10, 2022 · 13 comments
Closed

Latest update (today) just broke the full screen #297

Altonss opened this issue Apr 10, 2022 · 13 comments

Comments

@Altonss
Copy link

Altonss commented Apr 10, 2022

I belived I already had 5.38.0 since a few days, but just received another update just now, and I noticed the fullscreen is now broken (on Fedora 35, Gnome). The window doesn't open full screen anymore, some "space"/"padding" remains around the borders...
Has anyone experienced the same?

@bermeitinger-b
Copy link
Collaborator

The latest update should have fixed everything (yeah lol) about Wayland.

Could you provide a screenshot, the log from starting from terminal, and you are 100% sure that it didn't occur as of yesterday?

@Altonss
Copy link
Author

Altonss commented Apr 10, 2022

It started with the last update today, difficult to provide a screenshot as it contains rather personnal information :) And the log doesn't seem very informative...

@Altonss
Copy link
Author

Altonss commented Apr 10, 2022

Signal is now really unstable, crashes and has visual glitches. I will try to turn off the tray icon to see if it solves the issue.
EDIT: it hasn't resolved the full screen issue

@Altonss
Copy link
Author

Altonss commented Apr 10, 2022

Here a screenshot when I try to go fullscreen
image

@ethanbowering24
Copy link

The latest update should have fixed everything (yeah lol) about Wayland.

Could you provide a screenshot, the log from starting from terminal, and you are 100% sure that it didn't occur as of yesterday?

Similar story here, used signal this morning on my laptop. Got a notification that flatpak had updated signal. Opened it up and although it is still usable, fullscreen no longer works properly with strange padding around the window, and the UI scaling is off. I have censored my chats, they appear fine though.

image

@ethanbowering24
Copy link

The latest update should have fixed everything (yeah lol) about Wayland.
Could you provide a screenshot, the log from starting from terminal, and you are 100% sure that it didn't occur as of yesterday?

Similar story here, used signal this morning on my laptop. Got a notification that flatpak had updated signal. Opened it up and although it is still usable, fullscreen no longer works properly with strange padding around the window, and the UI scaling is off. I have censored my chats, they appear fine though.

image

Trying to manipulate the window just locked up my whole system. Couldn't even crtl alt fx into a different TTY

@Altonss
Copy link
Author

Altonss commented Apr 10, 2022

Have experienced the same glitches :)

@ethanbowering24
Copy link

ethanbowering24 commented Apr 10, 2022

Downgrading to commit from April 8th fixes my issue, like this guide

https://docs.flatpak.org/en/latest/tips-and-tricks.html?highlight=downgrade

sudo flatpak update --commit=9c0cbb69aaa663403f7d8dedceed5d7d9a3cc97a31f8060a07ea570cb81fc430 org.signal.Signal to downgrade, followed by

flatpak mask org.signal.Signal to prevent it from updating again.

flatpak mask --remove org.signal.Signal to unmask when this is fixed and resume updates.

@GlenMerlin
Copy link

On my system signal opens for a fraction of a second before crashing my entire DE and softlocking my computer same update version

@Summertime
Copy link

whenever resizing the window, the window would seemingly close itself and be unrecoverable (I don't have a tray icon extension atm)

@bermeitinger-b
Copy link
Collaborator

These seem to be different issues. I can reproduce the gaps for the fullscreen. Apparently, at some point electron and/or chromium changed something. I'll revert the wayland fixes which will remove specific fixes but it'll not crash at least I guess.

@Altonss
Copy link
Author

Altonss commented Apr 14, 2022

The problem has been fixed, so I will close the issue. Thanks @bermeitinger-b :)

@Altonss Altonss closed this as completed Apr 14, 2022
@somoant
Copy link

somoant commented Apr 19, 2022

probably it's electron/chromium bug electron/electron#33161

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants