Client 3.0.1 flatpak crash on ubuntu/fedora

[lapor-kris]

Expected behaviour
When run the desktop client, it should open.

Actual behaviour
System freezes, screen starts to flicker a bit (part where the window of the client should be).

Steps to reproduce:

1. Install Nextcloud desktop client 3.0.1 from Flathub (Flatpak)
2. Open the client
3. Observe

Client configuration
Client version: 3.01

Operating system: Ubuntu 20.04 and Fedora 32

OS language: Slovenian

Qt version used by client package (Linux only, see also Settings dialog): ?

Client package (From Nextcloud or distro) (Linux only): Flatpak

Installation path of client:?

Server configuration
Nextcloud version: 19.0.1

[tilosp]

I can't reproduce this, tried it both on Ubuntu 20.04 and on Fedora 32.

• Is the flatpak and it's dependencies up to date (run flatpak update -y)

• Have you tried resetting the client by deleting the ~/.var/app/com.nextcloud.desktopclient.nextcloud directory?

• Could you run the client from the command line using flatpak run com.nextcloud.desktopclient.nextcloud and post the output here?

[lapor-kris]

I deleted the client and installed it again. This time it opens the old styled client, but computer freezes. I had to take a picture with my phone. Any help? This is on Fedora 32, with all updates (flatpak aswell).
Edit: I use Wayland

[tilosp]

I am not sure what you mean by "old styled client", I attached a screenshot of what it looks like on my side.
The log output looks the same on my side (see below).

Since the entire gnome shell is freezing I would guess it is some extension. What extensions are you using?
Are you using any extension to get the systray working, since the 3.0.0 version has a new systray menu that might break something.
Other than that could you test if the behaviour is the same an x11 session?
You can also take a look at the logs, after it freezes reset and boot again, than you can use journalctl -b -1 to take a look at the logs of the last boot. Look somewhere near the end.

QSocketNotifier: Can only be used with threads started with QThread
Using Wayland-EGL
2020-09-04 06:21:36:697 [ debug default ]	[ unknown ]:	static bool LibSecretKeyring::findPassword(const QString&, const QString&, QKeychain::JobPrivate*)
2020-09-04 06:21:37:827 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	screenRect: QRect(0,0 1920x1006)
2020-09-04 06:21:37:827 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	taskbarRect: QRect(0,0 32x1006)
2020-09-04 06:21:37:827 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	taskbarScreenEdge: OCC::Systray::TaskBarPosition::Left
2020-09-04 06:21:37:827 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowReferencePoint ]:	trayIconCenter: QPoint(0,0)
2020-09-04 06:21:37:827 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	taskbarScreenEdge: OCC::Systray::TaskBarPosition::Left
2020-09-04 06:21:37:827 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	screenRect: QRect(0,0 1920x1006)
2020-09-04 06:21:37:827 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	windowRect (reference) QRect(36,0 401x511)
2020-09-04 06:21:37:827 [ debug nextcloud.gui.systray ]	[ OCC::Systray::computeWindowPosition ]:	windowRect (adjusted ) QRect(36,0 401x511)
2020-09-04 06:21:37:829 [ debug default ]	[ unknown ]:	Using the 'xdg-shell' shell integration

[lapor-kris]

Oh, I am sorry, I only saw the other interface, that was on their blog.
Nevertheless, here are the logs.
Thanks

[returntrip]

I am getting similar issues. I have tried to reset the client. I can setup everything OK but when I click on "Open main dialog" I either get no screen displayed or I get this screen garbage:

In X11 all works fine:

In the log I get a few of these messages:

2020-09-04 14:27:24:623 [ warning qt.qpa.xcb ]: QXcbConnection: XCB error: 136 (Unknown), sequence: 1184, resource id: 2097213, major code: 134 (Unknown), minor code: 17
2020-09-04 14:27:24:623 [ warning qt.qpa.xcb ]: QXcbConnection: XCB error: 11 (BadAlloc), sequence: 1189, resource id: 2097205, major code: 147 (Unknown), minor code: 2
2020-09-04 14:27:24:623 [ warning qt.qpa.xcb ]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1190, resource id: 2097215, major code: 147 (Unknown), minor code: 4
2020-09-04 14:27:24:624 [ warning qt.qpa.xcb ]: QXcbConnection: XCB error: 4 (BadPixmap), sequence: 1194, resource id: 2097215, major code: 146 (Unknown), minor code: 1
2020-09-04 14:27:24:624 [ warning qt.qpa.xcb ]: QXcbConnection: XCB error: 11 (BadAlloc), sequence: 1195, resource id: 2097205, major code: 147 (Unknown), minor code: 2
2020-09-04 14:27:24:624 [ warning qt.qpa.xcb ]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1196, resource id: 2097217, major code: 147 (Unknown), minor code: 4
2020-09-04 14:27:24:630 [ warning qt.qpa.xcb ]: QXcbConnection: XCB error: 4 (BadPixmap), sequence: 1197, resource id: 2097217, major code: 146 (Unknown), minor code: 1

[tilosp]

Could you try if it works under wayland using xwayland, this can be done by running it like this flatpak run --nosocket=wayland com.nextcloud.desktopclient.nextcloud .

And you can also try the beta version of this app, which uses a newer runtime:
flatpak install https://flathub.org/beta-repo/appstream/com.nextcloud.desktopclient.nextcloud.flatpakref
flatpak run com.nextcloud.desktopclient.nextcloud//beta

[tilosp]

And it would also be good to know if it's reproducible in appimage version of 3.0.1 too.
https://download.nextcloud.com/desktop/releases/Linux/Nextcloud-3.0.1-x86_64.AppImage

[lapor-kris]

Xwayland also breaks the system.
Beta works.

[returntrip]

• xwayland - nojoy - no window being displayed
• beta flatpak works, but the dialog seems being displayed in random places (some time top middle of the screen, some times at the bottom etc)
• AppImage, works and behaves like the beta flatpak...

Let me know if you want to see the randomness tied to the dialog, I have a couple of screenshots.

[tilosp]

* beta flatpak works, but the dialog seems being displayed in random places (some time top middle of the screen, some times at the bottom etc)

that is a limitation of wayland, apps cant set their own position. So it's expected.

[returntrip]

@tilosp Is it expected for the dialog to close as soon as it loses focus? I use "focus on hover" and the dialog closes as soon as I focus on a different window.

[tilosp]

@tilosp Is it expected for the dialog to close as soon as it loses focus? I use "focus on hover" and the dialog closes as soon as I focus on a different window.

I not sure, I guess it's supposed to work like any other right click menu. Maybe take a look at nextcloud/desktop#877 and nextcloud/desktop#1565