[Bug]: main (blue background) UI gone in 3.5 under Gnome/Wayland/Ubuntu 22.04

[artfulrobot]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

Previously there used to be a funny little popup window thing, which I think is considered the main UI, as pictured below:

Now there isn't.If I click the tray icon I get a menu (Add account, Pause sync for all, ... Settings...) and the only UI I can get to is the Settings screen. (Previously, in 3.4 it was called "Open main dialog")

The main UI did provide a few features that I can't live without; e.g. re conficts.

I've tried all types of clicking on the icon but can't get it to appear any more. If that UI was gone forever because the functionality had been moved into the (much better behaved) settings window that would be fine, but I don't think that's what's happened; I think it's a bug that it's missing?

Steps to reproduce

Described above.

Expected behavior

There should be some way to make the main UI show up. e.g. put a "Show main window" (or some other phrase) in the popup menu, alongside Settings etc. Or double-click or something.

Which files are affected by this bug

N/A

Operating system

Linux

Which version of the operating system you are running.

Ubuntu 22.04

Package

Appimage 3.5.0 "ubuntu-5.15.0-25-generic"

Nextcloud Server version

23.0.4

Is this bug present after an update or on a fresh install?

Updated to a major version (ex. 3.3.6 to 3.4.0) 3.4 → 3.5

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

No response

Additional info

No response

[mvv588]

Same on Mint 20.3 with Cinnamon, this is a regression, I'm using the PPA .The menu was broken some versions ago which was fixed in the last(?) version.

[mvvvmd]

Same as this issue we had before resolved by @ivaradi

[claucambra]

Same as this issue we had before resolved by @ivaradi

Not the same issue, here the "Open main dialog" option does not appear in the system tray menu at all, though the tray window is able to appear if invoked in some other way (like trying to open a new instance the client while it is already running)...

[claucambra]

Same as this issue we had before resolved by @ivaradi

Not the same issue, here the "Open main dialog" option does not appear in the system tray menu at all, though the tray window is able to appear if invoked in some other way (like trying to open a new instance the client while it is already running)...

Indeed it is a bug, investigating

[loxK]

Confirmed on Ubuntu 21.10 too (Gnome on Xorg)

[masakkre]

Same at Ubuntu mate 20.04, the last version (3.4.4 I think) works fine

[Rudiberto]

Nearly the same on Ubuntu 20.04 focal (Mint Xfce).
Description: nothing happens clicking on the icon. On right-click, the sub menu appears.
The actual AppImage 3.5.0 works fine, now, even with translation.

[claucambra]

@ivaradi heads up, we have an additional new dependency with qml-module-qt-labs-platform -- sorry for not notifying earlier, without this the main dialog will not appear (even with fixes to the menu)

[ivaradi]

@claucambra thanks for the update, the builds with the new dependency are in progress.

[claucambra]

@claucambra thanks for the update, the builds with the new dependency are in progress.

Thank you :)

[brtptrs]

I've just upgraded to and tested:
3.5.0-20220505.175928.ccb79dc69-1.0~focal1 (11 hours ago)
unfortunately the Problem still exists.

On Ubuntu 20.04.4 with X11

[masakkre]

On Ubuntu Mate 20.04, updated to the latest version this morning and istalled the new dependency, the problem still exists. In my case, when I clic on the try icon, into the submenu, insted of seeing the "Open main dialog" option, I have this 2 options: "Add account" and "pause sync".

[claucambra]

A fix is in the pipelines with #4484 and it should be part of the next bugfix release.

A workaround in the mean time if you need the tray window is to try to run a new instance of the client, which will invoke the tray window

[jeensg]

A fix is in the pipelines with #4484 and it should be part of the next bugfix release.

A workaround in the mean time if you need the tray window is to try to run a new instance of the client, which will invoke the tray window

The mentioned fix works here on xUbuntu 20.04. Thank you!
(opening a new instance doesn't help unfortunately)

[jeensg]

Well, just installed 3.5.1-20220518.151043.930206f06-1.0~focal1 ... option for maindialog now exists, but is not opening again :-(

If I can contribute with logs, I would need advice on what to post. Thank you!

I don't know if it's related to #4069 again?

[mad73923]

Same here.
installed 3.5.1-20220518.151043.930206f06-1.0~focal1 on Linux Mint 20.3 Cinnamon. Main dialog does NOT open.

[claucambra]

Well, just installed 3.5.1-20220518.151043.930206f06-1.0~focal1 ... option for maindialog now exists, but is not opening again :-(

If I can contribute with logs, I would need advice on what to post. Thank you!

I don't know if it's related to #4069 again?

Thanks for reporting, will investigate

[claucambra]

Can't reproduce on 22.04, will test 20.04

[claucambra]

Okay, can reproduce on 22.04, same symptom as #4069 , QtQuick version 2.15 is not installed. @ivaradi can we apply the prior QtQuick component version patch to 3.5.1?

[mad73923]

Same here:

[nerozero]

Same here, No text visible at all, super huge icons unusable on 720p screen

[nerozero]

The actual image of the status after update:

[ivaradi]

@claucambra, on 22.04, immediately after an installation and the initial login and synchronization,
the "Open main dialog" menu item does not appear and all the other items do not work.
The log contains entries like:

qrc:/qml/src/gui/tray/Window.qml:146: TypeError: Cannot read property 'headerColor' of null

There are many such entries, each time a property of UserModel.currentUser is referenced.
So it seems, that the initial login procedure does not set currentUser.

After killing nextcloud (since the "Exit" menu item does not work either) and
restarting, all menu items, including "Open main dialog", appear and work.

On 20.04, the QtQuick version patch was applied, but it did not update some new QtQuick module version numbers. After having added those, I also have this black background problem. In the log I can see entries like:

qrc:/qml/theme/Style/Style.qml:21:5: Unable to assign [undefined] to QColor

whenever a property of the Theme object is accessed. I did some debugging and the Theme object gets created, but for some reason none of the property getter functions are called. I will continue debugging, but some hint would be nice about what could have changed between 3.4 and 3.5 that might cause this behaviour with Qt 5.12 (but not with Qt 5.15).

[ivaradi]

I have implemented a workaround for 20.04, and now it seems to work, though I am not sure what undesirable side effects the
workaround may have. Please, test the new version.

The workaround is that the line

`qmlRegisterType<Theme>("com.nextcloud.desktopclient", 1, 0, "Theme");`

is moved after the instatiation of OCC::Application in the main function in main.cpp.

@claucambra please, check what this change causes, and whether it hints at what might the real problem be.

[claucambra]

@ivaradi thanks for the quick workaround, I will investigate

[mvvvmd]

Works now for me on Mint with the last update, very happy.

Edit: The share dialog does not open, the scaling also seems of for me, the top right icon is fuzzy. This is Linux Mint 20.3 Una with Cinnamon. The talk notification popup is also all black with just a decline button, it comes up in the middle of the screen.

[Rudiberto]

Also working on MINT 20.04 here
🥇

[jeensg]

Works here with xUbuntu 20.04.4 LTS (version: 3.5.1-20220522.112322.930206f06-1.0~focal1). Thank you very much for your fast fixes!!!

[Slater91]

I still face this issue on KDE neon (Ubuntu 20.04-based) with all the latest updates installed. Even if I start the client from the terminal and even if I enable debug logging (nextcloud --logdebug) I don't get any errors.

[jeensg]

I still face this issue on KDE neon (Ubuntu 20.04-based) with all the latest updates installed. Even if I start the client from the terminal and even if I enable debug logging (nextcloud --logdebug) I don't get any errors.

Which exact version do you have installed? (apt policy nextcloud-desktop)

[Slater91]

Which exact version do you have installed? (apt policy nextcloud-desktop)

The package installed is version 3.5.1-20220522.112322.930206f06-1.0~focal1, provided by http://ppa.launchpad.net/nextcloud-devs/client/ubuntu focal/main amd64.

[claucambra]

Which exact version do you have installed? (apt policy nextcloud-desktop)

The package installed is version 3.5.1-20220522.112322.930206f06-1.0~focal1, provided by http://ppa.launchpad.net/nextcloud-devs/client/ubuntu focal/main amd64.

Unfortunately, KDE Neon has different versions of Qt libraries to Ubuntu and the Ubuntu PPA versions of the client are not compatible with Neon.

For Neon users that want to use the most up to date version of the desktop client we recommend the official AppImage which avoids issues with Qt versioning.

[mvv588]

For Neon users that want to use the most up to date version of the desktop client we recommend the official AppImage which avoids issues with Qt versioning.

I realize this ticket is closed but I would like to respond. The Appimage really isn't a great solution. In my use case we deploy all software using apt to several hundred laptops and desktops. We would need to device some new method of deployment for getting a stable NC desktop client experience for our users.

The long duration and frequency of the app being broken does not reflect wel on NC as a whole from our users point of few. and hinders adoption. Some sort of resolution for getting a stable apt repo would be very helpful. We are looking to move to enterprise however I don't think this does offer a stable NC client.

[claucambra]

For Neon users that want to use the most up to date version of the desktop client we recommend the official AppImage which avoids issues with Qt versioning.

I realize this ticket is closed but I would like to respond. The Appimage really isn't a great solution. In my use case we deploy all software using apt to several hundred laptops and desktops. We would need to device some new method of deployment for getting a stable NC desktop client experience for our users.

The long duration and frequency of the app being broken does not reflect wel on NC as a whole from our users point of few. and hinders adoption. Some sort of resolution for getting a stable apt repo would be very helpful. We are looking to move to enterprise however I don't think this does offer a stable NC client.

The AppImage working fine is proof that the issue here is not the client itself, but rather the way the client is packaged for distributions. In the case of Ubuntu 20.04-based distributions, it is an issue of Ubuntu LTS releases forcing the use of versions of Qt which are significantly out of date, requiring the Nextcloud PPA packagers to patch the client to work correctly on these distributions. This will inevitably cause some bugs to arise.

In the case of KDE Neon specifically, it is as I explained -- KDE Neon uses different versions of Qt which break packages built for Ubuntu 20.04 and the version of Qt it ships with.

You can of course go and use versions of the client with patches for old versions of Qt, or try to use a different distribution's packages on your own distro, but what we cannot do is recommend these as supported solutions for the reasons above.

The Ubuntu PPA packages, while not officially packaged nor maintained by Nextcloud, are still packages that we pay attention to, and take the time to fix bugs with (see this issue!). We cannot, however, change the way that our dependencies are packaged in distributions. What we can do is bypass this issue with solutions such as AppImages. These solutions may not be perfect, but they ensure that the client works as intended across most Linux distributions.

[avatar1024]

Appimage/flatpack are a solution but one question remains:

How do we get file manager integration using the Appimage or Flatpack version without installing the repo version?? Having both version installed works but is messy a you have to be careful which version autostarts, and you also have to check repo version matches flatpack version for the integration. Is there a better solution being thought of here?

I have to say the Flatpack/Appimage version do work extremely well and offer the best experience I've every had with the client but it would be good to have an integrated solution that goes with those versions for file manager integration.

[claucambra]

Appimage/flatpack are a solution but one question remains:

How do we get file manager integration using the Appimage or Flatpack version without installing the repo version?? Having both version installed works but is messy a you have to be careful which version autostarts, and you also have to check repo version matches flatpack version for the integration. Is there a better solution being thought of here?

As far as I understand there aren't any technical reasons for a hard dependency between the client package and the file manager integration packages -- this would be more of a packaging issue. We can try to indicate to packagers that we'd prefer the client and file integration packages not be hard dependencies of each other, but it is again up to the packagers to decide what to do here.

Packaging for distributions is tricky for us there is no silver bullet that gets us everything with so all these moving parts. If we find a better way of distributing the client, we will of course pursue it

[Rudiberto]

Since version 3.5.3-20220729.170743.c48a8d89e-1.0~focal1 the problem is back on Mint Xfce 20.04 Focal
AppImage has now an annoying "KDE-Wallet" Dialog, hard to cancel!!
Maintainers can send me the pre-version and I will test it. No problem for me, if it's a problem for them.

[Rudiberto]

This time the problem really piss me off, because the crappy APPimage always wants to be verified via Firefox. Since I connect to various accounts, mixing various calendars on mobile devices and using a safe password on every browser on all my computers, I'm really annoyed.
I' worrying, that using the APP-Token on one device will cause having to use it on every other device too, and can we be sure that the next non-APP-image client version (which I will pin FORE SURE) can handle the app-token?

[Rudiberto]

I just received the newest working version: 3.5.4-20220806.084713.fea986309-1.0~focal1_all
THX, it's pinned now

[anver]

I compiled from source and clicking "Open main dialog" did not show up the dialog. I'm using ubuntu 22.04

Source package : stable 3.6

commands used to compile
cd stable-3.6
mkdir build && cd $_
cmake .. -DCMAKE_INSTALL_PREFIX=/usr
sudo make install

The app installs perfectly fine except for the main dialog is not opening at all.

[claucambra]

I compiled from source and clicking "Open main dialog" did not show up the dialog. I'm using ubuntu 22.04

Source package : stable 3.6

commands used to compile cd stable-3.6 mkdir build && cd $_ cmake .. -DCMAKE_INSTALL_PREFIX=/usr sudo make install

The app installs perfectly fine except for the main dialog is not opening at all.

You are likely missing QtQuick modules which, though not necessary to compile, are needed by the client to display the tray window. I recommend you check the client logs to see what is going on with your build of the client

[anver]

`Found SharedMimeInfo: /usr/bin/update-mime-database (found version "2.1")
-- Found Doxygen: /usr/bin/doxygen (found version "1.9.1") found components: doxygen missing components: dot
-- Found X11: /usr/include
-- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so
-- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found KF5CoreAddons: /usr/lib/x86_64-linux-gnu/cmake/KF5CoreAddons/KF5CoreAddonsConfig.cmake (found version "5.92.0")
-- Found KF5KIO: /usr/lib/x86_64-linux-gnu/cmake/KF5KIO/KF5KIOConfig.cmake (found version "5.92.0")
-- Found KF5: success (found suitable version "5.92.0", minimum required is "5.16.0") found components: CoreAddons KIO
-- Looking for GLIBC
-- Looking for GLIBC - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
-- Found CMocka: /usr/lib/x86_64-linux-gnu/libcmocka.so
-- The following OPTIONAL packages have been found:

• Sphinx
• PdfLatex
• Qt5WebChannel (required version >= 5.15.3)
• Qt5Positioning (required version >= 5.15.3)
• Qt5WebEngineCore (required version >= 5.15.3)
• Qt5PrintSupport (required version >= 5.15.3)
• Qt5WebEngineWidgets
• Qt5WebEngine
• Qt5LinguistTools
• SharedMimeInfo, A database of common MIME types, https://freedesktop.org/wiki/Software/shared-mime-info/
• Doxygen
• KF5Service (required version >= 5.92.0)
• KF5Bookmarks (required version >= 5.92.0)
• KF5Completion (required version >= 5.92.0)
• KF5ItemViews (required version >= 5.92.0)
• KF5JobWidgets (required version >= 5.92.0)
• KF5Solid (required version >= 5.92.0)
• KF5Auth (required version >= 5.92.0)
• KF5Codecs (required version >= 5.92.0)
• KF5Config (required version >= 5.92.0)
• KF5ConfigWidgets (required version >= 5.92.0)
• KF5XmlGui (required version >= 5.92.0)
• KF5WidgetsAddons (required version >= 5.92.0)
• CMocka

-- The following REQUIRED packages have been found:

• Inotify
• OpenSSL (required version >= 1.1)
• ZLIB
• Qt5Keychain
• PkgConfig
• SQLite3 (required version >= 3.8.0)
• Qt5WebSockets
• Qt5Svg
• Qt5QuickControls2
• ECM (required version >= 5.16.0)
• KF5CoreAddons (required version >= 5.92.0)
• Qt5Widgets (required version >= 5.15.2)
• Qt5Concurrent (required version >= 5.15.2)
• Qt5DBus (required version >= 5.15.2)
• KF5KIO (required version >= 5.16.0)
• KF5 (required version >= 5.16.0)
• Qt5Core
• Qt5Test
• Qt5Xml
• Qt5Network
• Qt5Qml
• Qt5QmlModels (required version >= 5.15.3)
• Qt5Gui (required version >= 5.15.3)
• Qt5Quick
• Qt5
  `

These are the cmake logs, I think all necessary modules are found

[claucambra]

Please re-read my prior comment carefully:

You are likely missing QtQuick modules which, though not necessary to compile, are needed by the client to display the tray window. I recommend you check the client logs to see what is going on with your build of the client

[anver]

Please re-read my prior comment carefully:

You are likely missing QtQuick modules which, though not necessary to compile, are needed by the client to display the tray window. I recommend you check the client logs to see what is going on with your build of the client

I tried everything I know, I even tried on a clean install of ubuntu 22.04

sudo apt update && sudo apt install -y build-essential cmake pkg-config qtbase5-dev qtkeychain-qt5-dev libqt5websockets5-dev libqt5svg5-dev qtdeclarative5-dev qtquickcontrols2-5-dev qtbase5-private-dev librsvg2-bin software-properties-common freeglut3-dev gdb git iputils-ping libgl1-mesa-dev
libglu1-mesa-dev libjpeg-dev libmysqlclient-dev libnss3-dev libopus-dev
libpng-dev libsqlite3-dev libssl-dev libx11-xcb-dev libxcb-xinerama0-dev
libxcb-xkb-dev libxcb1-dev libxcursor-dev libxi-dev libxml2-dev libxrender-dev
libxslt-dev lzip mesa-common-dev nano perl python3 valgrind wget zlib1g-dev
'^libxcb.*-dev' libxkbcommon-dev libxkbcommon-x11-dev libgl-dev g++ qt5-default openssl libssl-dev libzip-dev qtwebengine5-dev qt5keychain-dev sqlite3 libsqlite3-dev libqt5svg5-dev zlib1g-dev shared-mime-info libkf5archive-dev extra-cmake-modules libkf5kio-dev libqt5webkit5-dev qml-module-qtquick-controls qttools5-dev pkg-config qt5keychain-dev libkf5archive-dev libqt5websockets5-dev libqt5svg5-dev qtdeclarative5-dev qtquickcontrols2-5-dev librsvg2-bin sphinx-common texlive-latex-base doxygen libkf5kio-dev libcmocka-dev

Then

mkdir build && cd $_
cmake .. -DCMAKE_INSTALL_PREFIX=/usr
sudo make install

install worked and I don't get any errors or logs when clicking the "Open main dialog" menu, am I missing something ? Is there anything I need to do ?

[claucambra]

I tried everything I know, I even tried on a clean install of ubuntu 22.04

sudo apt update && sudo apt install -y build-essential cmake pkg-config qtbase5-dev qtkeychain-qt5-dev libqt5websockets5-dev libqt5svg5-dev qtdeclarative5-dev qtquickcontrols2-5-dev qtbase5-private-dev librsvg2-bin software-properties-common freeglut3-dev gdb git iputils-ping libgl1-mesa-dev \

    libglu1-mesa-dev libjpeg-dev libmysqlclient-dev libnss3-dev libopus-dev \

    libpng-dev libsqlite3-dev libssl-dev libx11-xcb-dev libxcb-xinerama0-dev \

    libxcb-xkb-dev libxcb1-dev libxcursor-dev libxi-dev libxml2-dev libxrender-dev \

    libxslt-dev lzip mesa-common-dev nano perl python3 valgrind wget zlib1g-dev \

    '^libxcb.*-dev' libxkbcommon-dev libxkbcommon-x11-dev libgl-dev g++ qt5-default openssl libssl-dev libzip-dev  qtwebengine5-dev qt5keychain-dev sqlite3 libsqlite3-dev libqt5svg5-dev zlib1g-dev  shared-mime-info libkf5archive-dev extra-cmake-modules libkf5kio-dev libqt5webkit5-dev qml-module-qtquick-controls qttools5-dev pkg-config qt5keychain-dev libkf5archive-dev libqt5websockets5-dev libqt5svg5-dev qtdeclarative5-dev qtquickcontrols2-5-dev librsvg2-bin sphinx-common texlive-latex-base doxygen libkf5kio-dev libcmocka-dev

Then

mkdir build && cd $_

cmake .. -DCMAKE_INSTALL_PREFIX=/usr

sudo make install

install worked and I don't get any errors or logs when clicking the "Open main dialog" menu, am I missing something ? Is there anything I need to do ?

A couple of things:

1. I can see from your package list the only QML module you are installing is QtQuick Controls. The tray window requires several more. I recommend taking a look at the packaging for Ubuntu to make sure you are installing all the ones you need
2. The desktop client does not log to the terminal by default. You will have to enable debug logging to files in the settings. Open the client's settings and hit F12, you will get a window explaining how to get the debug logs. Then look into these to see what the problem is (most likely which QML module the application is complaining about not finding)
3. Let's keep this discussion off of this thread as we are pinging everyone in this issue, and this is not relevant to the bug already fixed. Feel free to open a post on our forum if you need further help: https://help.nextcloud.com

[arch-user-france1]

The bug might not be fixed.
It still doesn't show anything when opened, but if I enable the overview with the super-key I can see a window with the nextcloud icon, just invisible.