I believe these are known issue with Wayland and QT5
@Henry78 try running:
QT_QPA_PLATFORM=xcb nextcloud and see if it helps.
I still don’t have a full picture of the problem, but the long version of the story is more or less this: Fedora now ships Gnome with Wayland as graphic backend by default, Xorg is being deprecated.
Now every GUI toolkit (GTK, QT, …) will have to use Wayland, and after 12 years the support is not yet complete in the ecosystem. Namely QT is the culprit here. The nextcloud GUI client is built on top of QT. QT applications will try to use the wayland backend, it’s like you launch nextcloud with
Since wayland support is not yet complete in QT, you can try forcing
QT_QPA_PLATFORM=xcb and QT will use the
xwayland backend, which is a sort of compatibility layer between an Xorg client and the wayland compositor.
I am on a Debian bullseye using Wayland and Sway and I must have xwayland installed to run nextcloud, pretty annoying but at least there’a workaround.
I will update this thread as I learn more.
hope this helps.