[Sécurité] Gnome keyring daemon manquant (Encours)

[primokorn]

Bonjour,

J'utilise le flatpak Pika Backup pour faire une sauvegarde de certaines données de mon /home.
Pour cela, j'avais installé gnome-keyring et libsecret il y a quelques mois et tout fonctionnait bien. Aujourd'hui, j'ai voulu lancer une sauvegarde et j'ai le message :
"Retrieving encryption password from the keyring failed. Pika Backup requires a keyring daemon ("secret service") to store passwords."

Le wiki parle du gnome-keyring-daemon qui est censé se lancer quand on ouvre la session via un service utilisateur systemd.

Mes versions :
gnome-keyring 1:42.1-3
libsecret 0.21.1-1
pam 1.5.3-3

OS: Arch Linux x86_64
Host: 81LK IdeaPad L340-15IRH Gaming
Kernel: 6.1.58-1-lts
DE: Plasma 5.27.8

Merci d'avance pour votre aide.

Code : Tout sélectionner

$ journalctl --boot | grep gnome
>> Démarrage
oct. 20 15:25:11 arch gnome-keyring-daemon[710]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
oct. 20 15:25:11 arch gnome-keyring-daemon[710]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
oct. 20 15:25:11 arch gnome-keyring-d[710]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
oct. 20 15:25:14 arch systemd[693]: app-gnome\x2dkeyring\x2dpkcs11@autostart.service: Skipped due to 'exec-condition'.
oct. 20 15:25:14 arch systemd[693]: app-gnome\x2dkeyring\x2dsecrets@autostart.service: Skipped due to 'exec-condition'.
oct. 20 15:25:14 arch systemd[693]: app-gnome\x2dkeyring\x2dssh@autostart.service: Skipped due to 'exec-condition'.
oct. 20 15:25:15 arch DiscoverNotifie[1167]: Warning: Treating remote fetch error as non-fatal since runtime/org.gnome.World.PikaBackup.Locale/x86_64/stable is already installed: No such ref 'runtime/org.gnome.World.PikaBackup.Locale/x86_64/stable' in remote flathub
oct. 20 15:25:15 arch DiscoverNotifie[1167]: Warning: Treating remote fetch error as non-fatal since runtime/org.gnome.Platform/x86_64/44 is already installed: No such ref 'runtime/org.gnome.Platform/x86_64/44' in remote flathub
oct. 20 15:25:15 arch DiscoverNotifie[1167]: Warning: Treating remote fetch error as non-fatal since runtime/org.gnome.Platform.Locale/x86_64/44 is already installed: No such ref 'runtime/org.gnome.Platform.Locale/x86_64/44' in remote flathub
oct. 20 15:25:15 arch DiscoverNotifie[1167]: Warning: Treating remote fetch error as non-fatal since app/org.gnome.World.PikaBackup/x86_64/stable is already installed: No such ref 'app/org.gnome.World.PikaBackup/x86_64/stable' in remote flathub

>>>> Après lancement Pika Backup
oct. 20 15:25:48 arch dbus-daemon[713]: [session uid=1000 pid=713] Activating service name='org.gnome.World.PikaBackup' requested by ':1.23' (uid=1000 pid=905 comm="/usr/bin/plasmashell --no-respawn")
oct. 20 15:25:49 arch systemd[693]: Started app-flatpak-org.gnome.World.PikaBackup-1616.scope.
oct. 20 15:25:49 arch dbus-daemon[713]: [session uid=1000 pid=713] Successfully activated service 'org.gnome.World.PikaBackup'
oct. 20 15:25:49 arch xdg-desktop-portal-kde[956]: xdp-kde-settings: Namespace  "org.gnome.desktop.a11y.interface"  is not supported
oct. 20 15:25:52 arch org.gnome.World.PikaBackup[1636]: thread 'main' panicked at 'Can't reset a OnceCell: Connection { inner: ConnectionInner { server_guid: Guid("09f0b1c432e66b2d3b49794265327fb7"), cap_unix_fd: true, bus_conn: true, unique_name: OnceCell(OwnedUniqueName(UniqueName(Str(Owned(":1.62"))))), registered_names: Mutex { data: {} }, raw_conn: Mutex { data: Connection { event: Event { .. }, raw_in_buffer: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], raw_in_fds: [], raw_in_pos: 0, out_pos: 0, out_msgs: [], prev_seq: 2 }, poisoned: false, .. }, serial: 2, executor: Executor { executor: Executor { state: OnceCell(State { queue: ConcurrentQueue { len: 0, capacity: None, is_closed: false }, local_queues: RwLock { data: [], poisoned: false, .. }, notified: false, sleepers: Mutex { data: Sleepers { count: 1, wakers: [(1, Waker { data: 0x7f6458006230, vtable: 0x557e84973720 })], free_ids: [2, 3] }, poisoned: false, .. }, active: Mutex { data: Slab { len: 1, cap: 4 }, poisoned: false, .. } }), _marker: PhantomData<core::cell::UnsafeCell<&()>> } }, socket_reader_task: OnceCell(Task(Some(Task { header: Header { scheduled: false, running: false, completed: false, closed: false, awaiter: false, task: true, ref_count: 2, metadata: () } }))), msg_receiver: InactiveReceiver { inner: RwLock { data: Inner { queue: [], capacity: 64, receiver_count: 0, inactive_receiver_count: 1, sender_count: 1, head_pos: 0, overflow: false, await_active: false, is_closed: false, send_ops: Event { .. }, recv_ops: Event { .. } }, poisoned: false, .. } }, method_return_receiver: InactiveReceiver { inner: RwLock { data: Inner { queue: [], capacity: 8, receiver_count: 0, inactive_receiver_count: 1, sender_count: 2, head_pos: 1, overflow: false, await_active: false, is_closed: false, send_ops: Event { .. }, recv_ops: Event { .. } }, poisoned: false, .. } }, msg_senders: Mutex { data: {Some(OwnedMatchRule(MatchRule { msg_type: Some(MethodReturn), sender: None, interface: None, member: None, path_spec: None, destination: None, args: [], arg_paths: [], arg0namespace: None })): Sender { inner: RwLock { data: Inner { queue: [], capacity: 8, receiver_count: 0, inactive_receiver_count: 1, sender_count: 2, head_pos: 1, overflow: false, await_active: false, is_closed: false, send_ops: Event { .. }, recv_ops: Event { .. } }, poisoned: false, .. } }, Some(OwnedMatchRule(MatchRule { msg_type: Some(Error), sender: None, interface: None, member: None, path_spec: None, destination: None, args: [], arg_paths: [], arg0namespace: None })): Sender { inner: RwLock { data: Inner { queue: [], capacity: 8, receiver_count: 0, inactive_receiver_count: 1, sender_count: 2, head_pos: 1, overflow: false, await_active: false, is_closed: false, send_ops: Event { .. }, recv_ops: Event { .. } }, poisoned: false, .. } }, None: Sender { inner: RwLock { data: Inner { queue: [], capacity: 64, receiver_count: 0, inactive_receiver_count: 1, sender_count: 1, head_pos: 0, overflow: false, await_active: false, is_closed: false, send_ops: Event { .. }, recv_ops: Event { .. } }, poisoned: false, .. } }} }, subscriptions: Mutex { data: {} }, object_server: OnceCell(Uninit), object_server_dispatch_task: OnceCell(Uninit) } }', /run/build/pika-backup/cargo/vendor/ashpd-0.4.0/src/proxy.rs:33:38
oct. 20 15:25:52 arch org.gnome.World.PikaBackup[1636]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[eathesitant]

If you're encountering an issue where the GNOME Keyring daemon is missing or not functioning properly, here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Check if GNOME Keyring is installed: First, ensure that GNOME Keyring is installed on your system. It's usually a separate package that might not be installed by default on some distributions.

On Arch Linux, you can install it using the package manager:
```
sudo pacman -S gnome-keyring
```

On Debian/Ubuntu-based systems:
```
sudo apt-get install gnome-keyring
```

2. Restart GNOME Keyring: Sometimes, the GNOME Keyring service might have stopped or failed to start properly. You can try restarting it:

```
gnome-keyring-daemon --replace
```

This command restarts the GNOME Keyring daemon. After restarting, check if the issue persists.

3. Check autostart settings: Ensure that GNOME Keyring is set to start automatically when you log in to your desktop environment. You can check this in your desktop environment's settings or use a tool like `gnome-session-properties` to manage startup applications.

4. Permissions and environment variables: Ensure that the necessary environment variables are set correctly. GNOME Keyring should typically be started and managed by your desktop environment automatically. If you're using a custom setup, make sure that the environment variables like `GNOME_KEYRING_SOCKET` and `GNOME_KEYRING_PID` are set correctly.

5. Check for conflicting applications: Sometimes, other applications or scripts might interfere with GNOME Keyring. Ensure that there are no conflicting configurations or scripts that might prevent GNOME Keyring from starting.

6. Reboot your system: In some cases, simply rebooting your system can resolve issues related to services not starting properly.

If none of these steps resolve the issue, you may need to look into more specific logs (`journalctl` on systemd-based systems like Arch Linux) to identify any error messages or further clues as to why GNOME Keyring is not working as expected.