Est ce cette info serait parlante ?
$ systemctl status snapd
**`●`**` snapd.service - Snap Daemon
Loaded: loaded (/usr/lib/systemd/system/snapd.service; `**`disabled`**`; preset: `**`disabled`**`)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: `**`active (running)`**` since Wed 2024-02-14 08:30:37 CET; 31s ago
TriggeredBy: `**`●`**` snapd.socket
Main PID: 3295 (snapd)
Tasks: 22 (limit: 19018)
Memory: 645.5M
CPU: 7.630s
CGroup: /system.slice/snapd.service
└─3295 /usr/libexec/snapd/snapd
févr. 14 08:30:37 pc-bureau systemd[1]: `**`snapd.service: Got notification message from PID 3307, but reception only permitted for main PID 3295`**`
févr. 14 08:30:37 pc-bureau systemd[1]: `**`snapd.service: Got notification message from PID 3313, but reception only permitted for main PID 3295`**`
févr. 14 08:30:37 pc-bureau snapd[3295]: overlord.go:271: Acquiring state lock file
févr. 14 08:30:37 pc-bureau snapd[3295]: overlord.go:276: Acquired state lock file
févr. 14 08:30:37 pc-bureau snapd[3295]: daemon.go:247: started snapd/2.61.1-0.fc39 (series 16; classic; devmode) fedora/39 (amd64) linux/6.7.4-200.fc39.x86_64.
févr. 14 08:30:37 pc-bureau snapd[3295]: daemon.go:340: adjusting startup timeout by 2m25s (pessimistic estimate of 30s plus 5s per snap)
févr. 14 08:30:37 pc-bureau snapd[3295]: backends.go:58: AppArmor status: apparmor not enabled
févr. 14 08:30:37 pc-bureau systemd[1]: Started snapd.service - Snap Daemon.
févr. 14 08:30:38 pc-bureau systemd[1]: `**`snapd.service: Got notification message from PID 3496, but reception only permitted for main PID 3295`**`
févr. 14 08:30:40 pc-bureau snapd[3295]: storehelpers.go:791: cannot refresh: snap has no updates available: "bare", "bashtop", "core", "core18", "core20", "core22", "cups", "freeplane-mindmapping", "gnome-3-28-1804", "gnome-3-38-2004">
Edit Nicosss : Correction balises Markdown -> Voir FAQ