v1.4.0 - failing to login and use anything related to credentials
Metadata
Current evaluation
No code fix was identified; Charmcraft 1.4.0 could not access the desktop keyring from its snap environment. Installing gnome-keyring restored login on Kubuntu, while exported credentials offered another workaround.
Resolution: closed not a bug
Reason: The reporter confirmed Kubuntu began working after installing gnome-keyring. CHARMCRAFT_AUTH was also identified as a workaround for environments without an accessible keyring, indicating an environment/configuration limitation rather than an application-code fix.
Evaluated by: mr-cal-bot
No scores available.
Issue body
I somehow got this candidate release on Ubuntu 20.04 LTS .. will likely look to revert to stable but.. seems I login but nothing works
```
$ charmcraft login
Opening an authorization web page in your browser.
If it does not open, please open this URL:
https://api.jujucharms.com/identity/login?did=9149c5blahlblahblah
Logged in as 'MYUSER'.
$ charmcraft status MYCHARM
Not logged in.
Full execution log: '/home/MYUSER/snap/charmcraft/common/cache/charmcraft/log/charmcraft-20220122-170629.358793.log'
$ cat /home/MYUSER/snap/charmcraft/common/cache/charmcraft/log/charmcraft-20220122-170629.358793.log
2022-01-22 17:06:29.359 Starting charmcraft version 1.4.0
2022-01-22 17:06:29.359 Raw pre-parsed sysargs: args={'help': False, 'verbose': False, 'quiet': False, 'trace': False, 'project_dir': None} filtered=['status', 'MYCHARM']
2022-01-22 17:06:29.359 General parsed sysargs: command='status' args=['MYCHARM']
2022-01-22 17:06:29.359 Couldn't find config file '/home/MYUSER/Dev/git/scharms/MYCHARM/charmcraft.yaml'
2022-01-22 17:06:29.359 Command parsed sysargs: Namespace(name='MYCHARM')
2022-01-22 17:06:29.410 Retrieving credentials for 'charmcraft' on HttpUrl('https://api.charmhub.io', scheme='https', host='api.charmhub.io', tld='io', host_type='domain') from keyring 'auth MemoryKeyring'.
2022-01-22 17:06:29.410 Credentials not found in the keyring 'auth MemoryKeyring'
2022-01-22 17:06:29.410 Not logged in.
2022-01-22 17:06:29.412 Traceback (most recent call last):
2022-01-22 17:06:29.412 File "/snap/charmcraft/761/lib/charmcraft/commands/store/client.py", line 94, in request_urlpath_json
2022-01-22 17:06:29.412 response = super().request(method, self.api_base_url + urlpath, *args, **kwargs)
2022-01-22 17:06:29.412 File "/snap/charmcraft/761/lib/craft_store/base_client.py", line 151, in request
2022-01-22 17:06:29.412 headers["Authorization"] = self._get_authorization_header()
2022-01-22 17:06:29.412 File "/snap/charmcraft/761/lib/craft_store/store_client.py", line 96, in _get_authorization_header
2022-01-22 17:06:29.412 auth = self._auth.get_credentials()
2022-01-22 17:06:29.412 File "/snap/charmcraft/761/lib/craft_store/auth.py", line 150, in get_credentials
2022-01-22 17:06:29.412 raise errors.NotLoggedIn()
2022-01-22 17:06:29.412 craft_store.errors.NotLoggedIn: Not logged in.
2022-01-22 17:06:29.412 Full execution log: '/home/MYUSER/snap/charmcraft/common/cache/charmcraft/log/charmcraft-20220122-170629.358793.log'
charmcraft version
1.4.0
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | No code fix was identified; Charmcraft 1.4.0 could not access the desktop keyring from its snap environment. Installing gnome-keyring restored login on Kubuntu, while exported credentials offered another workaround. | |
| stealth/space-bunny-alpha | — | closed not a bug | Credentials could not be persisted because the snap lacked keyring access. Installing gnome-keyring restored login on Kubuntu 20.04; CHARMCRAFT_AUTH provided another workaround. | |
| stealth/space-bunny-alpha | — | closed not a bug | Closed after users confirmed installing gnome-keyring restored credential access; CHARMCRAFT_AUTH was another workaround. No fixing PR was recorded. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed. The snap failed to persist credentials due to keyring issues. Maintainers provided workarounds: installing gnome-keyring or using CHARMCRAFT_AUTH. Users confirmed these resolved the problem, leading to closure. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. Maintainer identified snap confinement limiting keyring access, causing login persistence failures. Resolved via workarounds: installing gnome-keyring or using the CHARMCRAFT_AUTH environment variable. Reporter confirmed success. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed. Snap confinement blocks system keyring access. Workarounds: install gnome-keyring or export credentials via CHARMCRAFT_AUTH. Developers are investigating native KDE Wallet support within the snap. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #719 [1.5.0] Charmcraft login not finding keyring | charmcraft | closed | Closed as a headless keyring/session configuration issue; running Charmcraft in dbus-run-session with gnome-keyring unlocked made login succeed. No code fix was recorded. | |
| #672 charmcraft 1.4.0: impossible to login to charmhub | charmcraft | closed | Closed as intended behavior: the headless remote host had no local keyring, so Charmcraft could not persist credentials; exporting credentials was the supported workaround. |