though I have no hope that anything will ever be fixed - I see some of these for years now.
First problem: Authorization of accounts
Interestingly I read in some other thread that the login should be saved in gnome-keyring or kwallet automatically. I cant talk about “K”, but I can tell that it is not in gnome-keyring using xfce as desktop on arch linux. It does not complain either, so a user has really no idea if something is saved, not saved or broken.
Things are significantly worse if you use more than one account. Because then you have to fight with your browser during entering the login data to enter the correct login data for the account in question. If you have one ready you may well be driven to clear cookies and web cache of your browser to be even able to enter the second login data at all.
Question is: why use a browser at all for login? Why not simply enter the login data inside the application?
Second problem: Multithreading? Whats that?
If you thought that multiple account will be synced in parallel you probably are pretty astonished to see that someone wrote a linux application without ever having heard of multithreading. Of course your accounts wait for syncing until the one before is completed.
Third problem: Logging and output in the app window
Am I really interested in seeing few lines of files? No I am not. At best it should tell me what file it syncs currently (file 34/20467 “my latest doc.odt”), but endless lists of files in a window make no sense. Better would be to show the ongoings of every login/account in parallel. A button to watch and solve conflicts (per login) is really enough.
I know most people won’t use the app anyway because it is quite unusable for years now, still I want to state clearly why rclone, foldersync and the like are in heavy use while the nextcloud client is just flushed..
Why are you posting here if you’re not going to reply anyway? Just to vent your frustration?
Regarding the first problem you described (XFCE & gnome-keyring), I can say that it has been working fine for me for a decade. Specifically with Debian (XFCE) and Xubuntu. To do this, gnome-keyring needs to be opened at login. However, it won’t open if you use passwordless login. But that has always been known.
Which, by the way, isn’t exclusive to XFCE. Even in GNOME or Plasma, it doesn’t unlock automatically when you log in with a fingerprint, for example—unless you remove the password entirely, which of course reduces security (even if full-disk encryption mitigates that somewhat). Either way, these aren’t really issues with the Nextcloud client itself, but rather broader Linux desktop limitations.
Logging out of the first account in the browser should be enough.
Because this wouldn’t work with 2FA enabled or other authentication methods such as OAuth/OpenID Connect. Also, you really shouldn’t store your main account password on every device. For better security, you should create device- or app-specific passwords instead. The browser-based login flow automates this process, making it easier for users to securely connect their devices than if they had to manually create an app/device password and then copy and paste it into the client.
That’s something the developers would have to answer. You might want to check GitHub to see if there’s already a feature request for that, and if not, open one. That would certainly be more helpful than snarky comments here on the forum.
Do you have any actual numbers to back up that rather bold theory? That was a retorical question
It kind of works, in that it prompts you for the password after logging in, but only until you enter the password incorrectly once. For me, it stopped working after that and I had to reset it completely to get it working again.
Also, at least on GNOME, it’s not really possible to configure fingerprint authentication independently for the login and lock screen, or at least, there doesn’t seem to be an obvious way to do so. You can, of course, still use your password on the login screen, which I think circumvents the keyring issue. Still, it really should be configurable independently, as I don’t consider biometrics to be as secure as a password. Therefore, it should be possible to disable it for the login screen while still allowing it for the lock screen.
But that’s totally off-topic here and not something the Nextcloud developers can change. Or rather, I think it’s better that they rely on existing mechanisms for storing credentials instead of implementing their own solution, which could in turn introduce its own issues.
