-
Notifications
You must be signed in to change notification settings - Fork 813
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
[Bug]: Nextcloud-3.7.4-x86_64.AppImage does not start in Wayland #5515
Comments
Still the same in version 3.8.2:
I'd rather call this a missing feature than a bug though. |
[UPDATE] |
Bug is still reproducible on Arch Linux, KDE Plasma Wayland, Nextcloud Client 3.11.1. It reproduces as starting under XWayland with the warning message:
If
I noticed this because I rely on fractional scaling for a good desktop experience, which does not function correctly under XWayland. |
Years and it still does not work well in wayland :( OS: TUXEDO OS jammy 22.04 x86_64 |
Bug description
The new Nextcloud Desktop Client App Image Nextcloud-3.7.4-x86_64.AppImage does not start in Wayland environment.
Error Message: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Predecessor App Image Nextcloud-3.7.3-x86_64.AppImage runs without any issue.
Steps to reproduce
Start Nextcloud-3.7.4-x86_64.AppImage and the error occurs.
Expected behavior
Nextcloud Desktop Image starts.
Which files are affected by this bug
Nextcloud-3.7.4-x86_64.AppImage
Operating system
Linux
Which version of the operating system you are running.
Linux 5.15.0-67-generic #74~20.04.1-Ubuntu SMP Wed Feb 22 14:52:34 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Package
Appimage
Nextcloud Server version
25.0.3
Nextcloud Desktop Client version
3.7.4
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Additional info
No response
The text was updated successfully, but these errors were encountered: