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
Flatpak has incorrect display scaling in Flatpak #611
Comments
You might wanna try our RPM for now. |
Sure, But I will switch to it permanently if update is available via dnf. |
I checked out the It would be better if the same in Flatpak too. But rpm uses X11 whereas flatpak uses Wayland. My suggestion is it to scale the Window at 70% and centered in screen by default while opening and also remember the windows position & size. Note : When I close upscayl myself. System sends notification it is crashed. |
@NayamAmarshe - A crash log of Upscayl Flatpak crashing. I know this should be separate issue. But no time for me to fill the issue template. If you can split this into another issue. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is still happening, please reply to indicate so. |
Please fix this scaling issue. |
Could you try running the flatpak with --socket=wayland ? This feels like it might be an XWayland issue |
Erm @NayamAmarshe, could you configure dosu to not act on "help wanted"? |
Checklist
Description
While opening the Flatpak version of the app. Instead of scaling within the screen size. It overflows beyond the screen and needs to rescale it.
Upscayl.zip - A Screenrecording to give a overview on my issue.
This is the case in any OS ever since I started using Upscayl. It doesn't even remember the window position and size.
And there is been constant crashes too. I can't even create crash logs too. There's been backtrace failure or missing data.
Using Fedora 39, Kernel 6.6.8, KDE Plasma.
Related Problem(s)
No response
Alternatives
No response
The text was updated successfully, but these errors were encountered: