nakada0907/n-daisuke897-blog
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

docs: add post on fixing GitHub Copilot CLI system vault error

Browse source 
Add new blog post explaining how to resolve the "system vault not available"
error when installing GitHub Copilot CLI using systemd and gnome-keyring.
Includes step-by-step instructions with command examples.
This commit is contained in:
Daisuke Nakahara 2026-01-02 21:28:51 +09:00
parent 989b829a20
commit 1cf9933d08
1 changed files with 64 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

64
src/blog/post-5.md Normal file
View file

@ -0,0 +1,64 @@
---
title: 'Fixing GitHub Copilot CLI System Vault Error with systemd'
pubDate: 2026-01-02
author: 'Nakahara Daisuke'
tags: ["GitHub", "AI"]
---
When installing GitHub Copilot CLI, you may encounter the error message: `The system vault (keychain, keyring, password manager, etc.) is not available. You may need to install one.` The solution was documented in [this issue](https://github.com/github/copilot-cli/issues/49).
This article explains how to resolve this issue using `systemd`.
### Install via Apt
```bash
$ sudo apt update
```
```bash
$ sudo apt install -y \
gnome-keyring \
libsecret-1-0 \
libsecret-tools \
seahorse
```
### Verify systemd is running
```bash
$ systemctl is-system-running
```
### Check if the user service is enabled
```bash
$ systemctl --user status gnome-keyring-daemon
○ gnome-keyring-daemon.service - GNOME Keyring daemon
Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.service; enabled; preset: enabled)
Active: inactive (dead)
TriggeredBy: ○ gnome-keyring-daemon.socket
```
```bash
$ systemctl --user enable gnome-keyring-daemon
```
```bash
$ systemctl --user start gnome-keyring-daemon
```
```bash
$ systemctl --user status gnome-keyring-daemon
● gnome-keyring-daemon.service - GNOME Keyring daemon
Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.service; enabled; preset: enabled)
Active: active (running) since Fri 2026-01-02 08:36:46 JST; 3s ago
Invocation: d830e5563e974edc9265650d11dfa086
TriggeredBy: ● gnome-keyring-daemon.socket
Main PID: 5222 (gnome-keyring-d)
Tasks: 5 (limit: 9422)
Memory: 3.4M (peak: 3.9M)
CPU: 37ms
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-keyring-daemon.service
└─5222 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring
Jan 02 08:36:46 hostname systemd[649]: Started gnome-keyring-daemon.service - GNOME Keyring daemon.
Jan 02 08:36:46 hostname gnome-keyring-daemon[5222]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Jan 02 08:36:46 hostname gnome-keyring-daemon[5222]: another secret service is running
Jan 02 08:36:46 hostname gnome-keyring-d[5222]: another secret service is running
```
> **Note**: This article was translated from Japanese to English and reviewed with the assistance of AI (GitHub Copilot).