-
Notifications
You must be signed in to change notification settings - Fork 807
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]: 3.14.x asks to log in on every start #7231
Comments
Also having the same problem. Had to revert back to 3.13.4 |
Not being familiar with Ubuntu Mate 22, do you what is supposed to be storing secrets on this platform ? |
Appears to be the same experience on standard Gnome Fedora 40. I've even had to reenter the E2E numonic forcing a resync Which raises the question, does it work for people who have plasma for their Desktop? |
I'm experiencing the same issue with two ubuntu noble 24.04.1 installs using appimage. |
Same for me (LM22 Cinnamon). I'm asked for a kdewallet password. I never used kdewallet. |
Same with Ubuntu 24.04.1, appimage. |
+1, Ubuntu 24.02.1, appimage 3.14.1 |
Same here (Ubuntu 24.04.1, using Nextcloud AppImage 3.14.0 or 3.14.1), it also crashes with segmentation fault regularly. Rolled back to 3.13 |
Confirmed on LM22 (Noble base). |
+1 |
I've the same issue in Debian SID ... I'm not using kdewallet at all. |
Same with ubuntu 24.04.1 and NextCloud AppImage 3.14.0 and 3.14.1, the latter version fixing nothing. |
Where to find the previous AppImage please ? |
Just chiming in to say I have had this problem too, with both 3.14.0 and 3.14.1. I'm using Ubuntu 24.04.1, GNOME 46, and the NextCloud AppImage. 3.13.4 continues to work as expected, so I have rolled back to it after both updates and am staying there for now. |
Got the same problem since doing the dist upgrade to 24.04.1 today, |
Having this problem since 3.14.0, updating to 3.14.1 didn't fix it. |
Confirm same problem here on LM22 since 3.14.0 |
Same here, Fedora 40 + 3.14.0 and 3.14.1 reverted to 3.13.4 and fine with it. |
please avoid posting too much comments without more information |
and by the way, I did not notice because I have kwallet configured and running |
Fact: There was no problem with 3.13.4. There is a problem with 3.14.0 and 3.14.1. If I go back to 3.14.3, the issue disappears. Comments: I don't know if kwallet is installed. What is the name of the package ? Not kwallet obviously, the package does not seem to exist. Besides, I use Ubuntu with Gnome. I suspect that kwallet belongs to KDE. Not everyone uses KDE. There is a place where secret are stored with Gnome. The old version 3.13.4 does put the secret in this place. Not the versions 3.14.0 and 3.14.1. Something is clearly broken in 3.14.0 and 3.14.1. |
the release 3.14.1 is working fine with ubuntu 22.04 stock installation and my question is for anybody that want to help not just @phi0042 |
as I cannot reproduce with ubuntu 22.04, you have to know that I will keep working on this only if the tone of the conversation is nice, respectful and useful |
@mgallien these are the lines in my logs that contain the string 'error' (case insensitive) :
gnome-keyring-daemon is running. I cannot find any lines in my logs mentioning storage of secrets. What's the pattern I should be looking for? |
The explanation is simple by searching the forum : with 3.14, Gnome Keyrings is not detected/used anymore for some reason. Which is what I wrote earlier : with 3.14, the secret is not stored anymore for some reason. This means that anyone using Ubuntu 24.04 with KDE will not have any issue. As for the log file, it is huge. |
Fedora 40 with Gnome shell 46.5 $ sudo dnf list installed | grep kwallet I don't remember installing kwallet. It has not been configured or any rings created that I know of. Just from retrying and app registration against browser login. The below two are from initial startup |
|
Thanks for this, works perfectly. |
I think we are in all agreement that officially supported releases simply should work without any additional fixes by the end user or their support staff... |
the title of this ticket is [[Bug]: 3.14.0/3.14.1 asks to log in on every start , it could be change with [[Bug]: 3.14.0/3.14.1/3.14.2 asks to log in on every start : I confirm the bug on ubuntu / 3.14.2 . |
Again in 3.14.2?!? |
This comment has been minimized.
This comment has been minimized.
Well, i suppose i'll keep unpacking the appimage, removing libglib and repacking the appimage again 'til the developer does it for me. |
I don't have capacity to chase this down. I'll stay on an old version until this is remediated. |
Still an issue in 3.14.3. Looks like #7455 might fix this if it can be reviewed. |
Here are the steps to make it work until an official fix is out. The following example uses version 3.14.3
./Nextcloud-3.14.3-x86_64.AppImage --appimage-extract
cd ./squashfs-root
./AppRun
rm ./usr/lib/libglib-2.0.so.0
cd ..
ARCH=x86_64 VERSION=3.14.3 ~/Applications/appimagetool-855-x86_64.AppImage ./squashfs-root Thanks to the earlier comments from @jvanderneutstulen and @JoshuaPettus |
Although this PR unfortunately seems to only provide a hack/workaround for the actual issue instead of resolving the underlying problem. I stumbled upon this with a build distributed through apt recently and thus a real solution would be preferred (although I cannot help with this). In the meantime, I am using the AppImage build, but this feels like a hacky workaround as well. |
Still waiting for an official fix. Meanwhile I had to remove libglib-2.0.so.0 from the appimage, as usual. |
Confirm the same problem on Fedora 41 (GNOME 47) with any Nextcloud desktop app version 3.14.X |
Still an issue on client v 3.14.3. Stable release. Windows 10 64bit english. Client logs itself out on every reboot. |
I"m hoping so too. I will revisit later.
Unfortunately downloading 3.15.0 shows up internally in settings as 3.14.3 and the Github url with starred version numbers is no longer working in Gearlever
Get BlueMail for Android
…On 27 Nov 2024, 07:39, at 07:39, "Ben." ***@***.***> wrote:
Fixed on my side on 3.15.0 , Thanks @cmuck and @mgallien
--
Reply to this email directly or view it on GitHub:
#7231 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
It did update for me to 3.15.0. On first start it once again prompted for signin in my browser, however after that I shut it down and relaunched and it did not prompt. Seems to be fixed. @Travis-Ecc The update URL I'm using in Gear Lever is: github.com/nextcloud-releases/desktop/releases/download//Nextcloud--x86_64.AppImage It eliminated the asterix it seems, but after download and between the two dashes after Nextcloud. |
Yep I have the same url but it isn't saving for me AS for the download I downloaded the AppImage and the download was the 3.15.0 but when I check it out iin the app it shows this I even redownloaded and tried again but get the same. |
|
Solved here, Fedora 40. Thanks! |
Solved for (my) Ubuntu 24.04 too. Thanks everyone for suggested workarounds! Many thanks for fixing the underlying issue @cmuck, @camilasan, @mgallien! |
Hesitant to jump the gun, but I can also report that so far the issue seems resolved on Win 10 as well. |
Bug description
Every time the desktop client starts, it opens a browser window asking me to authorize it with my Nextcloud instance. Downgrading to 3.13.4 fixes the issue (the client logs in immediately and transparently upon starting). The issue occurs in 3.14.0 and persists in 3.14.3.
Steps to reproduce
Expected behavior
If I've logged in previously, I should not be asked to log in again when the client starts
Which files are affected by this bug
n/a
Operating system
Linux
Which version of the operating system you are running.
Linux Mint 22 Cinnamon
Package
Official Linux AppImage
Nextcloud Server version
29.0.7
Nextcloud Desktop Client version
3.14.1
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)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
No response
Additional info
I don't want to post a full debug archive since it contains information I'd consider sensitive. Here's some relevant logs though:
The text was updated successfully, but these errors were encountered: