Nextcloud window not showing up

Hi everyone!

I installed the Nextcloud client (current version 3.6.2) on Fedora 37 via sudo dnf install nextcloud-client-nautilus (which also installed nextcloud-client) and it appears to work fine for the most part. It appears to be well integrated in Nautilus, and I can open the settings window from there.

However when I try to open the main Nextcloud window to add a new account (as those can’t be added from the settings window, oddly enough), the window just doesn’t show up anywhere. I tried on an X11 session with the same result. I even added an extension to show the tray icon and launch it from there, to no avail.

I checked this thread but disabling extensions didn’t solve it for me.

Is anyone having this issue too? Any pointers to what could be causing it?

1 Like

It seem you might be confusing the Nextcloud Client for the nautilus plugin and Gnome Online Accounts. The Settings window one is Gnome’s Online Accounts which is a also separate thing from the Nextcloud Client.

Nextcloud Client - Official Nextcloud client for synchronizing folders. This is what gives you a tray icon.
Nextcloud Client Nautilus Extension - This adds menu items like sharing in context menus when you’re in synchronized folders configured with the Nextcloud Client
Gnome Online Accounts - This also shows up in Nautilus and basically does a webdavs mount on demand but demand but does not do a local FS sync - good for accessing and copying files, especially if you don’t have much local storage, but slower and less reliable. This is entirely separate from the Nextcloud Client and nautilus plugin for it.

Thanks for the reply!

Maybe I didn’t explain myself well, but I’m aware of the differences between those three things.

What I meant is that the Nextcloud Client Nautilus Extension allows me to open the Nextcloud Client settings (not the Online Account settings, that’s an entirely different thing):

78956067e4a01a59d803072fac948c4363dd45ad.png

However, due to some strange decision by the developers of the Nextcloud Client, it’s not possible to add another Nextcloud account to it from there.

You need to use the client’s main dialog, but that dialog is not opening for me. It should open by launching the Nextcloud Client from the dash, or by clicking the top panel indicator (if you have that enabled).

(The screenshots are just for clarity and were taken in a different computer)

PS: As I’m new to the forum, I couldn’t post more than one image to the previous post, but this is what I’m referring to when I say “Nextcloud Client main window or main dialog”.

d78eea31671337e973f87ed0d6c81bff4917c04d.png

This is the only place you can set additional Nextcloud accounts in the client, AFAIK, but it’s not showing up.

(Again, the screenshots are just for clarity and were taken in a different computer)

Oh weird - it’s currently working for me on Fedora 37:

48371dc2b36a5f171c61ff9934aadd1ffabb3986.png

$ rpm -q nextcloud-client
nextcloud-client-3.6.2-1.fc37.x86_64

Do you see any errors in journalctl -f while you try opening it?

I have the exact same version :+1:

Thanks for the pointer! This is what I get when launching the app:

journalctl output
dic 14 20:29:46 ithaca-lx nextcloud[13307]: QSocketNotifier: Can only be used with threads started with QThread
dic 14 20:29:46 ithaca-lx gnome-shell[2307]: service string = :1.305
dic 14 20:29:46 ithaca-lx gnome-shell[2307]: busName string = :1.305
dic 14 20:29:46 ithaca-lx gnome-shell[2307]: object string = /StatusNotifierItem
dic 14 20:29:46 ithaca-lx nextcloud[13331]: QSocketNotifier: Can only be used with threads started with QThread
dic 14 20:29:47 ithaca-lx gnome-keyring-daemon[2146]: asked to register item /org/freedesktop/secrets/collection/login/8, but it's already registered
dic 14 20:29:49 ithaca-lx nextcloud[13365]: QSocketNotifier: Can only be used with threads started with QThread
dic 14 20:29:50 ithaca-lx gnome-shell[2307]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownProperty: Property org.kde.StatusNotifierItem.IconAccessibleDesc was not found in object /StatusNotifierItem
                                             _promisify/proto[asyncFunc]/</<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:446:45
                                             ### Promise created here: ###
                                             getProxyProperty@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/util.js:55:31
                                             refreshPropertyOnProxy@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/util.js:73:39
                                             _translateNewSignals/<@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:268:18
                                             _translateNewSignals@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:267:50
                                             _onProxySignal/<@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:294:56
                                             _onProxySignal@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:294:38
                                             async*AppIndicatorsAppIndicator/<@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:105:76
dic 14 20:29:50 ithaca-lx gnome-shell[2307]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownProperty: Property org.kde.StatusNotifierItem.IconAccessibleDesc was not found in object /StatusNotifierItem
                                             _promisify/proto[asyncFunc]/</<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:446:45
                                             ### Promise created here: ###
                                             getProxyProperty@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/util.js:55:31
                                             refreshPropertyOnProxy@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/util.js:73:39
                                             _translateNewSignals/<@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:268:18
                                             _translateNewSignals@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:267:50
                                             _onProxySignal/<@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:294:56
                                             _onProxySignal@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:294:38
                                             async*AppIndicatorsAppIndicator/<@/home/jt/.local/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:105:76

Once launched, when I try to open the client’s window from the tray indicator (the only way I could find to explicitly tell it to open the window apart of just launching the app), journalctl shows nothing more. It just does nothing.

Searching for one of the errors I arrived at another user asking the same, with no answers.

The other errors seem related to the appindicator extension itself. I’ll try again disabling it.

Have the same issue myself. Don’t have any problem on KDE Spin though.
BTW, I have the following extensions installed:
AppIndicator and KStatusNofierItemSupport
Dash to Panel
ddterm
Desktop Icons NG (DING)
Gnome Clipboard
Lock Keys
No overview at start-up
OpenWeather
Screenshot Tool (and gnome-screenshot package)
Vitals

1 Like

Yeah, same issue on my end. I can confirm it’s not caused by any extensions as I tried that on a fresh F37 Workstation desktop install as well as on my laptop.

The only thing that shows up in my journalctl is:
Dec 27 17:02:05 surfacebook2 systemd[1488]: Started app-gnome-com.nextcloud.desktopclient.nextcloud-5089.scope - Application launched by gnome-shell.

If anyone knows some black magic that can fix it I’m all ears (:

1 Like

Aight, after a month of dealing with this mildly annoying bug I decided to check if the Nextcloud Client 3.6.6 from Updates-Testing will fix the issue. Surprise surprise, it did.

sudo dnf --enablerepo=updates-testing update nextcloud-client

Gui shows up fine, doesn’t matter if I open it up via AppIndicator or straight from the dash. Seems like it was nextcloud-client’s fault after all.

2 Likes

Thanks for the followup! I’ll try to update and see how it goes.

Edit: I can now confirm it works!

1 Like