Bonjour,

J'ai fais l'upgrade bookworm -> trixie depuis quelques jours sur mon desktop, 
et depuis il a
souvent du mal à se réveiller (d'une mise en veille simple, pas encore essayé 
l'hibernation).

Ce matin l'écran affichait l'écran de veille avec l'heure (d'hier soir au 
moment de sa mise en
veille), sans curseur souris, et impossible de déclencher la demande de pass 
pour rouvrir la
session X.

Ctrl+maj+Fxx pour ouvrir une nouvelle session cli ne donnait rien non plus

Pourtant, d'après les logs le système tournait normalement (les cron se sont 
lancés
régulièrement cette nuit), j'en déduis donc que c'est plutôt la mise en veille 
d'hier soir qui
a planté…

# demande de mise en veille

2026-01-06T23:09:26.960472+01:00 ldlc17 dbus-daemon[2663]: [session uid=1000 
pid=2663 pidfd=5] Activating service name='org.cinnamon.ScreenSaver' requested 
by ':1.212' (uid=1000 pid=47748 comm="/usr/bin/python3 
/usr/share/cinnamon-screensaver/c")
2026-01-06T23:09:27.152462+01:00 ldlc17 org.cinnamon.ScreenSaver[47755]: 
Loading AccountsService
2026-01-06T23:09:27.152570+01:00 ldlc17 org.cinnamon.ScreenSaver[47755]: 
Fractional scaling active: False
2026-01-06T23:09:27.166073+01:00 ldlc17 org.cinnamon.ScreenSaver[47755]: Trying 
to connect to logind...
2026-01-06T23:09:27.167092+01:00 ldlc17 dbus-daemon[2663]: [session uid=1000 
pid=2663 pidfd=5] Successfully activated service 'org.cinnamon.ScreenSaver'
2026-01-06T23:09:27.167371+01:00 ldlc17 org.cinnamon.ScreenSaver[47755]: 
Starting screensaver...
2026-01-06T23:09:27.216405+01:00 ldlc17 org.cinnamon.ScreenSaver[47755]: 
Cinnamon Screensaver support not found in current theme - adding some...
2026-01-06T23:09:27.833154+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737367.8327] manager: sleep: sleep requested (sleeping: no  enabled: yes)
2026-01-06T23:09:27.833316+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737367.8328] device (enp109s0f1): state change: unavailable -> unmanaged 
(reason 'unmanaged-sleeping', managed-type: 'full')
2026-01-06T23:09:27.833608+01:00 ldlc17 ModemManager[1958]: <msg> 
[sleep-monitor-systemd] system is about to suspend
2026-01-06T23:09:27.846755+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737367.8443] device (p2p-dev-wlp110s0): state change: disconnected -> 
unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
2026-01-06T23:09:27.847010+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737367.8446] manager: NetworkManager state is now ASLEEP
2026-01-06T23:09:27.847125+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737367.8448] device (wlp110s0): state change: activated -> deactivating 
(reason 'sleeping', managed-type: 'full')
2026-01-06T23:09:27.857374+01:00 ldlc17 dbus-daemon[1656]: [system] Activating 
via systemd: service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 
pid=1932 comm="/usr/sbin/NetworkManager --no-daemon")
2026-01-06T23:09:27.866502+01:00 ldlc17 systemd[1]: Starting 
NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
2026-01-06T23:09:27.918603+01:00 ldlc17 dbus-daemon[1656]: [system] 
Successfully activated service 'org.freedesktop.nm_dispatcher'
2026-01-06T23:09:27.919293+01:00 ldlc17 systemd[1]: Started 
NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
2026-01-06T23:09:27.925863+01:00 ldlc17 kernel: wlp110s0: deauthenticating from 
1c:57:3e:a1:59:a1 by local choice (Reason: 3=DEAUTH_LEAVING)
2026-01-06T23:09:28.115716+01:00 ldlc17 wpa_supplicant[1933]: wlp110s0: 
CTRL-EVENT-DISCONNECTED bssid=1c:57:3e:a1:59:a1 reason=3 locally_generated=1
2026-01-06T23:09:28.117048+01:00 ldlc17 wpa_supplicant[1933]: wlp110s0: 
CTRL-EVENT-DSCP-POLICY clear_all
2026-01-06T23:09:28.118728+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737368.1178] device (wlp110s0): state change: deactivating -> disconnected 
(reason 'sleeping', managed-type: 'full')
2026-01-06T23:09:28.119635+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737368.1190] dhcp4 (wlp110s0): canceled DHCP transaction
2026-01-06T23:09:28.119790+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737368.1191] dhcp4 (wlp110s0): activation: beginning transaction (timeout 
in 45 seconds)
2026-01-06T23:09:28.119875+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737368.1191] dhcp4 (wlp110s0): state changed no lease
2026-01-06T23:09:28.156695+01:00 ldlc17 avahi-daemon[1653]: Interface 
wlp110s0.IPv4 no longer relevant for mDNS.
2026-01-06T23:09:28.156870+01:00 ldlc17 avahi-daemon[1653]: Leaving mDNS 
multicast group on interface wlp110s0.IPv4 with address 192.168.1.159.
2026-01-06T23:09:28.156939+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737368.1565] device (wlp110s0): set-hw-addr: set MAC address to 
52:8B:C9:11:01:56 (scanning)
2026-01-06T23:09:28.160552+01:00 ldlc17 avahi-daemon[1653]: Withdrawing address 
record for 192.168.1.159 on wlp110s0.
2026-01-06T23:09:28.160949+01:00 ldlc17 avahi-daemon[1653]: Joining mDNS 
multicast group on interface wlp110s0.IPv4 with address 192.168.1.159.
2026-01-06T23:09:28.163205+01:00 ldlc17 avahi-daemon[1653]: New relevant 
interface wlp110s0.IPv4 for mDNS.
2026-01-06T23:09:28.164932+01:00 ldlc17 avahi-daemon[1653]: Registering new 
address record for 192.168.1.159 on wlp110s0.IPv4.
2026-01-06T23:09:28.165054+01:00 ldlc17 avahi-daemon[1653]: Withdrawing address 
record for 192.168.1.159 on wlp110s0.
2026-01-06T23:09:28.165135+01:00 ldlc17 avahi-daemon[1653]: Leaving mDNS 
multicast group on interface wlp110s0.IPv4 with address 192.168.1.159.
2026-01-06T23:09:28.165217+01:00 ldlc17 avahi-daemon[1653]: Interface 
wlp110s0.IPv4 no longer relevant for mDNS.
2026-01-06T23:09:28.206160+01:00 ldlc17 gvfsd-wsdd[47810]: Failed to spawn the 
wsdd daemon: L’exécution du processus fils « wsdd » a échoué (Aucun fichier ou 
dossier de ce nom)
2026-01-06T23:09:28.207344+01:00 ldlc17 gvfsd-network[12366]: Couldn't create 
directory monitor on wsdd:///. Error: Le montage automatique a échoué : Échec 
du lancement du démon wsdd sous-jacent.
2026-01-06T23:09:28.244923+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737368.2447] device (wlp110s0): supplicant interface state: completed -> 
disconnected
2026-01-06T23:09:28.246807+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737368.2464] device (wlp110s0): state change: disconnected -> unmanaged 
(reason 'unmanaged-sleeping', managed-type: 'full')
2026-01-06T23:09:28.277080+01:00 ldlc17 wpa_supplicant[1933]: wlp110s0: 
CTRL-EVENT-SCAN-FAILED ret=-100
2026-01-06T23:09:28.277220+01:00 ldlc17 NetworkManager[1932]: <info>  
[1767737368.2769] device (wlp110s0): set-hw-addr: reset MAC address to 
00:28:F8:4D:72:86 (unmanage)
2026-01-06T23:09:28.287307+01:00 ldlc17 wpa_supplicant[1933]: p2p-dev-wlp110s: 
CTRL-EVENT-DSCP-POLICY clear_all
2026-01-06T23:09:28.287457+01:00 ldlc17 wpa_supplicant[1933]: p2p-dev-wlp110s: 
CTRL-EVENT-DSCP-POLICY clear_all
2026-01-06T23:09:28.287526+01:00 ldlc17 wpa_supplicant[1933]: nl80211: deinit 
ifname=p2p-dev-wlp110s disabled_11b_rates=0
2026-01-06T23:09:28.295912+01:00 ldlc17 org.cinnamon.ScreenSaver[47755]: 
AccountsService ready
2026-01-06T23:09:28.296062+01:00 ldlc17 org.cinnamon.ScreenSaver[47755]: 
Successfully using logind
2026-01-06T23:09:28.355479+01:00 ldlc17 wpa_supplicant[1933]: wlp110s0: 
CTRL-EVENT-DSCP-POLICY clear_all
2026-01-06T23:09:28.386062+01:00 ldlc17 systemd[1]: Reached target sleep.target 
- Sleep.
2026-01-06T23:09:28.387953+01:00 ldlc17 systemd[1]: Starting 
systemd-suspend.service - System Suspend...
2026-01-06T23:09:28.410193+01:00 ldlc17 wpa_supplicant[1933]: wlp110s0: 
CTRL-EVENT-DSCP-POLICY clear_all
2026-01-06T23:09:28.410321+01:00 ldlc17 wpa_supplicant[1933]: nl80211: deinit 
ifname=wlp110s0 disabled_11b_rates=0
2026-01-06T23:09:28.449186+01:00 ldlc17 systemd[1]: [email protected]: Unit now 
frozen-by-parent.
2026-01-06T23:09:28.449302+01:00 ldlc17 systemd[1]: session-1.scope: Unit now 
frozen-by-parent.
2026-01-06T23:09:28.449367+01:00 ldlc17 systemd[1]: user-1000.slice: Unit now 
frozen-by-parent.
2026-01-06T23:09:28.449418+01:00 ldlc17 systemd[1]: user.slice: Unit now frozen.
2026-01-06T23:09:28.449673+01:00 ldlc17 systemd-sleep[47831]: Successfully 
froze unit 'user.slice'.
2026-01-06T23:09:28.460361+01:00 ldlc17 systemd[1]: Stopping atop.service - 
Atop advanced performance monitor...
2026-01-06T23:09:28.594614+01:00 ldlc17 systemd[1]: atop.service: Deactivated 
successfully.
2026-01-06T23:09:28.594936+01:00 ldlc17 systemd[1]: Stopped atop.service - Atop 
advanced performance monitor.
2026-01-06T23:09:28.595380+01:00 ldlc17 systemd[1]: atop.service: Consumed 
13.741s CPU time, 38.7M memory peak.
2026-01-06T23:09:28.597518+01:00 ldlc17 systemd-sleep[47831]: Performing sleep 
operation 'suspend'...
2026-01-06T23:09:28.598242+01:00 ldlc17 kernel: PM: suspend entry (deep)
2026-01-06T23:09:28.721963+01:00 ldlc17 kernel: Filesystems sync: 0.123 seconds
2026-01-06T23:09:38.278961+01:00 ldlc17 systemd[1]: 
NetworkManager-dispatcher.service: Deactivated successfully.


# je vois pas de pb dans ce qui précède, pourtant 6 min plus tard cron se met 
en route
# donc le système n'est pas très "suspend"…

2026-01-06T23:15:01.446513+01:00 ldlc17 CRON[47852]: (root) CMD (command -v 
debian-sa1 > /dev/null && debian-sa1 1 1)
2026-01-06T23:17:01.451061+01:00 ldlc17 CRON[47856]: (root) CMD (cd / && 
run-parts --report /etc/cron.hourly)


$> journalctl --since=2026-01-06T23:09:00 --until=2026-01-06T23:59:59 
--priority=warning
janv. 06 23:09:28 ldlc17.lairdutemps.org gvfsd-wsdd[47810]: Failed to spawn the 
wsdd daemon: L’exécution du processus fils « wsdd » a échoué (Aucun fichier ou 
dossier de ce nom)
janv. 06 23:09:28 ldlc17.lairdutemps.org gvfsd-network[12366]: Couldn't create 
directory monitor on wsdd:///. Error: Le montage automatique a échoué : Échec 
du lancement du démon wsdd sous-jacent.


C'est lui le coupable ?
Je n'ai pas de montage gvfsd, ce paquet est là en dépendance d'un autre 
(bcompare, et je vois pas le rapport)

lors de la tentative de réveil je n'ai rien de spécial dans les logs, 
journalctl ne me sort aucun warning, 
je vois bien les messages liés au fait d'avoir débranché / rebranché souris et 
clavier, mais rien d'anormal,
comme si tout fonctionnait correctement avec simplement une sortie vidéo figée 
sur ce qu'il avait au moment
du suspend (j'aurais dû tenter de débrancher / rebrancher l'écran).

Une autre piste où chercher ?

Merci


-- 
Daniel

Il faut toute une vie pour apprendre à vivre.
Sénèque.

Répondre à