-
Notifications
You must be signed in to change notification settings - Fork 677
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
Linux client stuck on connecting #11925
Comments
This issue was marked stale because it has been open for 30 days with no activity. Remove the stale label or comment or this will be closed in 7 days. |
The issue was marked as stale for 7 days and closed automatically. |
This issue was marked stale because it has been open for 30 days with no activity. Remove the stale label or comment or this will be closed in 7 days. |
The issue was marked as stale for 7 days and closed automatically. |
Pre-submission Checks
Describe the bug
The Linux client is not able to connect on startup. The GUI starts up properly but gets stuck on connecting.
The only way to trigger working sync is:
Account -> Log out -> Log in -> authenticate using browser -> click into existing session in browser -> Linux client now shows connected
Expected behavior
Starting the desktop Linux client should have working sync
Steps to reproduce the issue
No response
Screenshots
The displayed message is
Connecting to https://server.com...
Logs
Client startup HTTP requests
This is a table of HTTP requests made at client start up.
Notably, Windows and macOS clients make a request to /konnect/v1/token but the Linux client does not.
Windows
macOS
Linux
Linux logout/login HTTP requests
After doing the log out and login from the Linux client, sync works again.
Linux client logs
client_startup.log
client_logout_login_working.log
Client version number
All clients tested were 5.3.1.14018.
Desktop environment (Linux only)
Ubuntu 24.04
Client package version and origin (Linux only)
Installed from ownCloud mirrors
Installation path (Windows only)
No response
Server information
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: