-
Notifications
You must be signed in to change notification settings - Fork 815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Add account button disappeared #6358
Comments
Duplicate of #6167 See there for the situation. It's Flatpak specific. |
I have the same problem outside of Flatpak, it's not even installed. Tried deleting |
I have done the same steps as well with no luck. I am running Arch linux KDE Plasma 6 and I'm using the |
I have the same problem on Plasma 6 and nextcloud-client 3.13.0 on Solus OS. I also tried with flathub nextcloud-client version but the problem remained. |
This problem also appears when installing from fedoras repositories (using Question remains: is it a Nextcloud problem or does the problem lie somewhere else? Seeing that it appears under Gnome, Plasma and on Arch and Fedora, I would assume that it's a Nextcloud problem, but I might be off here. |
Same Problem here with Fedora 40 - Plasma 6. |
Same problem on Arch Linux, KDE Plasma 6, installed via pacman, no flatpak. |
|
I am on Arch Linux, using 3.12.3 from Flathub, adding the |
Same issue. Fedora 40, KDE 6.1.1. Downloaded from Fedora repo via dnf. |
Building against QT6 seems like it is solving this issue when using the client directly from the distribution package manager (see flathub/com.nextcloud.desktopclient.nextcloud#164) and maybe this issue should be deferred to each distribution packagers ((Arch)[https://archlinux.org/packages/extra/x86_64/nextcloud-client/] and (Fedora)[https://packages.fedoraproject.org/pkgs/nextcloud-client/nextcloud-client/]) |
Same issue. |
Is there a way to force verbose output from the sync client? Maybe it reports what the problem is. |
Same problem here on all computers with KDE Plasma (not using Flatpak). |
Or there's a bug in recent versions of NC client. nextcloud-client-git is version 3.13.0, while "normal" version is 3.13.2 (newer). In other hand, I don't know when exactly this issue started, maybe it was in "normal" version for a long time too... |
I still hold my point that unless we get verbose output, we can not identify what causes this regression. I do not have the setup to check this now or in the foreseeable future. |
I also have the same problem KDE, Plasma, native nextcloud client (no flatpak) I'm happy to deliver logfiles when someone tells me what kind of logfiles are needed and how to generate them. |
Same here, KDE Plasma 6.0.5 on Manjaro, installed with pacman. Client version : 3.13.2git. When I launch it from cli, this is the log I see, don't knwo if it's related:
So I removed /home/[username]/.local/share/Nextcloud for them, thinking it will help, but the client keeps recreating the folder and the .log 🤔 |
@Pikari0 this is not related to QT errors. |
Bug seems to be fixed in v3.13.3 (KDE Plasma 6) |
Can approve. Bug fixed in v3.13.3 with KDE Plasma on Wayland. |
Bug description
There is no (more) button to add another account in my NC client. I currently have three and want to add a fourth.
Steps to reproduce
Expected behavior
Find the button to add an account (and the GUI to not be this broken)
Operating system
Linux
Which version of the operating system you are running.
Ubuntu 23.10
Nextcloud Desktop Client version
3.11.0 (flatpak)
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4) with
flatpak update
. Also triedflatpak install --reinstall
, to no avail.Additional info
In the following screenshot, I've indicated where I was expecting to find the "Add account" button (I recall it being here before), as well as the missing (but clickable) buttons for things like Talk, at the top. Other white blocks are my redactions for privacy, but the text behind them is grey-on-grey, hard to read, suggesting problems with a dark theme.
The text was updated successfully, but these errors were encountered: