sing in error

[kotovasia5120]

The problem

After logging into your browser and entering your email and name.
the name is not activatable

Release version

3.3.18-linux1

Operating system

Operating System: SteamOS 3.6.12 Build: 20240905.101 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.5.0-valve19-1-neptune-65-g8e4b171a9b33 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Custom APU 0932 Memory: 14.5 ГиБ of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Valve Product Name: Galileo System Version: 1

Steps to reproduce the behavior

No response

Log files

2024-09-12.desktop.production.log

2024-09-12T10:46:06.530Z - info: [ui] [AppStore] loading 0 repositories from store
2024-09-12T10:46:06.614Z - info: [ui] launching: 3.3.18-linux1 (Linux 6.5.0-valve19-1-neptune-65-g8e4b171a9b33)
2024-09-12T10:46:06.615Z - info: [ui] execPath: '/app/github-desktop/github-desktop'
2024-09-12T10:46:10.888Z - info: [ui] [SignInStore] initializing OAuth flow
2024-09-12T10:46:10.898Z - info: [main] opening in browser: https://github.com/login/oauth/authorize?client_id=3a723b10ac5575cc5bb9&scope=repo%20user%20workflow&state=57701426-fa38-43c3-ab95-a97f07df1987
2024-09-12T10:46:17.169Z - info: [main] Received possible protocol arguments: 3
2024-09-12T10:46:17.169Z - info: [main] Processing protocol url
2024-09-12T10:46:17.172Z - info: [ui] [Dispatcher] requesting authenticated user
2024-09-12T10:46:17.260Z - info: [main] Received possible protocol arguments: 2
2024-09-12T10:46:17.315Z - info: [main] Processing protocol url
2024-09-12T10:46:18.265Z - info: [ui] [SignInStore] account resolved
2024-09-12T10:46:18.266Z - info: [ui] [AppStore] adding account kotovasia5120 (kotovasia) to store
2024-09-12T10:46:18.280Z - error: [ui] Error adding account 'kotovasia5120'
Error: The name is not activatable

Screenshots

No response

Additional context

No response

[kotovasia5120]

changing the name doesn't help

[shiftkey]

This is a keychain related issue - we need to store the credential securely on the OS and we use libsecret APIs to do this - we know gnome-keyring supports this but without a backend this seems to be the source of failures.

See #1020 for an in-depth discussion of options