[Clos] Erreurs dans journalctl

ceric · 31-05-2024 00:19:45

Bonsoir,
en exécutant :

journalctl -r -p err

J'ai une flopée d'erreurs :

journalctl -r -p err

mai 31 01:05:51 cedric-hp-elitedesk-800-g2-sff gdm-launch-environment][713]: GL>

mai 31 01:05:48 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start a>

mai 31 01:05:48 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start a>

mai 31 01:05:47 cedric-hp-elitedesk-800-g2-sff gdm-password][1190]: gkr-pam: un>

mai 31 01:05:37 cedric-hp-elitedesk-800-g2-sff wpa_supplicant[657]: bgscan simp>

mai 31 01:05:32 cedric-hp-elitedesk-800-g2-sff kernel: mei_wdt 0000:00:16.0-05b>

mai 31 01:05:32 cedric-hp-elitedesk-800-g2-sff kernel: x86/cpu: SGX disabled by>

-- Boot f57e265e90314786adb23b8fdf979488 --

mai 31 00:12:38 cedric-hp-elitedesk-800-g2-sff kernel: watchdog: watchdog0: wat>

mai 31 00:12:37 cedric-hp-elitedesk-800-g2-sff gdm3[705]: Gdm: Failed to contac>

mai 31 00:11:33 cedric-hp-elitedesk-800-g2-sff kernel: nouveau 0000:01:00.0: fi>

mai 31 00:11:33 cedric-hp-elitedesk-800-g2-sff kernel: nouveau 0000:01:00.0: gr>

mai 31 00:11:33 cedric-hp-elitedesk-800-g2-sff kernel: nouveau 0000:01:00.0: gr>

mai 31 00:11:33 cedric-hp-elitedesk-800-g2-sff kernel: nouveau 0000:01:00.0: gr>

mai 31 00:11:33 cedric-hp-elitedesk-800-g2-sff kernel: nouveau 0000:01:00.0: gr>

mai 31 00:11:33 cedric-hp-elitedesk-800-g2-sff kernel: nouveau 0000:01:00.0: gr>

mai 31 00:11:33 cedric-hp-elitedesk-800-g2-sff kernel: nouveau 0000:01:00.0: gr>

mai 31 00:11:33 cedric-hp-elitedesk-800-g2-sff kernel: nouveau 0000:01:00.0: gr>

mai 31 00:11:05 cedric-hp-elitedesk-800-g2-sff gdm-launch-environment][715]: GL>

mai 31 00:11:02 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start a>

mai 31 00:11:02 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start a>

mai 31 00:11:02 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start a>

mai 31 00:11:01 cedric-hp-elitedesk-800-g2-sff gdm-password][1189]: gkr-pam: un>

lines 1-23

et je ne sais pas où chercher des solutions.
J'en ai pourtant moins car j'ai fait des modifications.
J'ai pourtant passé les mêmes commandes que sur un autre forum

Dernière modification par ceric (12-06-2024 21:44:54)

vv222 · 31-05-2024 12:21:06

ceric a écrit :

J'ai pourtant passé les mêmes commandes que sur un autre forum

Lesquelles? Il y a une trentaine de messages dans ce fil, et une bonne partie incluent des commandes.

ceric · 31-05-2024 17:02:34

Bonjour vv222, merci de venir me secourir, j'ai ce problème depuis mon dual boot ubuntu / debian, ça c'est sous debian :

cat /etc/fstab

# /etc/fstab: static file system information.

#

# Use 'blkid' to print the universally unique identifier for a

# device; this may be used with UUID= as a more robust way to name devices

# that works even if disks are added and removed. See fstab(5).

#

# systemd generates mount units based on this file, see systemd.mount(5).

# Please run 'systemctl daemon-reload' after making changes here.

#

# <file system> <mount point>   <type>  <options>       <dump>  <pass>

# / was on /dev/sda5 during installation

UUID=29b9c2c0-fb43-4442-932d-f201311b0707 /               ext4    errors=remount-ro 0       1

# /boot/efi was on /dev/sda2 during installation

UUID=88A3-5090  /boot/efi       vfat    umask=0077      0       1

# /home was on /dev/sda7 during installation

UUID=e36923db-455f-439d-889f-f7a03ca54c27 /home           ext4    defaults        0       2

# swap was on /dev/sda6 during installation

UUID=c48bb603-a20a-492f-a095-fb89b095dc32 none            swap    sw              0       0

Dernière modification par ceric (31-05-2024 17:05:58)

ceric · 31-05-2024 17:10:39

J'ai trouvé ma réponse ici.
Cela dit, j'aimerais bien connaître le pourquoi de cette armada dans le journalctl

Dernière modification par ceric (31-05-2024 17:16:15)

ceric · 11-06-2024 19:55:10

journalctl -r -p err

Hint: You are currently not seeing messages from other users and the system.

      Users in groups 'adm', 'systemd-journal' can see all messages.

      Pass -q to turn off this notice.

juin 11 20:16:19 cedric-hp-elitedesk-800-g2-sff systemd[1195]: Failed to start >

juin 11 20:16:19 cedric-hp-elitedesk-800-g2-sff systemd[1195]: Failed to start >

-- Boot e869153597e14b2fa6def6b0cc88ff71 --

juin 11 17:48:37 cedric-hp-elitedesk-800-g2-sff systemd[1177]: Failed to start >

-- Boot 4435cc60d8d04a87b4c03d36fd8f2341 --

juin 10 19:20:21 cedric-hp-elitedesk-800-g2-sff systemd[1206]: Failed to start >

juin 10 19:20:21 cedric-hp-elitedesk-800-g2-sff systemd[1206]: Failed to start >

-- Boot 78574b35bb5d4f21a225d801d826e805 --

juin 10 19:10:00 cedric-hp-elitedesk-800-g2-sff systemd[1194]: Failed to start >

juin 10 19:09:58 cedric-hp-elitedesk-800-g2-sff systemd[1194]: Failed to start >

-- Boot 953ddad5894b452e87488874bedea4d3 --

juin 09 13:14:12 cedric-hp-elitedesk-800-g2-sff systemd[1201]: Failed to start >

-- Boot ad4f7a217a314120be499550a857a0be --

juin 09 07:23:32 cedric-hp-elitedesk-800-g2-sff systemd[1215]: Failed to start >

-- Boot 5f262b1e862d4f03a8cc7e2bc694b887 --

juin 07 21:39:37 cedric-hp-elitedesk-800-g2-sff systemd[1205]: Failed to start >

juin 07 21:39:35 cedric-hp-elitedesk-800-g2-sff systemd[1205]: Failed to start >

juin 07 21:39:35 cedric-hp-elitedesk-800-g2-sff systemd[1205]: Failed to start >

-- Boot da337e01decd44a3b5037bd8aa9151bc --

juin 07 18:58:59 cedric-hp-elitedesk-800-g2-sff systemd[1214]: Failed to start >

juin 07 18:58:59 cedric-hp-elitedesk-800-g2-sff systemd[1214]: Failed to start >

-- Boot b40e57d918a1400f8697a499b7fa2b73 --

juin 06 19:39:19 cedric-hp-elitedesk-800-g2-sff systemd[1216]: Failed to start >

Je réouvre ce topic car je n'ai pas trouvé de solution à ces erreurs.

ceric · 11-06-2024 19:58:07

@vv222, c'est ce topic est un peu décousu; mais est-ce que quelqu'un(e) a déjà rencontré ce problème avec systemd?
J'ai trouvé ce bug, mais je ne sais pas l'exploiter.

Dernière modification par ceric (11-06-2024 20:11:14)

vv222 · 11-06-2024 20:12:31

Comme la sortie que tu partages est tronquée (« (…) Failed to start > ») il n’est pas possible d’en déduire quoi que ce soit.

Tu peux avoir la sortie complète en l’envoyant dans un fichier texte :

journalctl -r -p err > ~/journalctl.err.txt

ceric · 11-06-2024 20:18:10

@vv222, j'ai exécuté en root :

journalctl -r -p err

juin 11 20:16:23 cedric-hp-elitedesk-800-g2-sff gdm-launch-environment][716]: G>

juin 11 20:16:19 cedric-hp-elitedesk-800-g2-sff systemd[1195]: Failed to start >

juin 11 20:16:19 cedric-hp-elitedesk-800-g2-sff systemd[1195]: Failed to start >

juin 11 20:16:19 cedric-hp-elitedesk-800-g2-sff gdm-password][1168]: gkr-pam: u>

juin 11 20:16:11 cedric-hp-elitedesk-800-g2-sff wpa_supplicant[653]: bgscan sim>

juin 11 20:16:07 cedric-hp-elitedesk-800-g2-sff kernel: mei_wdt 0000:00:16.0-05>

juin 11 20:16:07 cedric-hp-elitedesk-800-g2-sff kernel: x86/cpu: SGX disabled b>

-- Boot e869153597e14b2fa6def6b0cc88ff71 --

juin 11 18:17:12 cedric-hp-elitedesk-800-g2-sff kernel: watchdog: watchdog0: wa>

juin 11 18:17:11 cedric-hp-elitedesk-800-g2-sff gdm3[714]: Gdm: Failed to conta>

juin 11 17:48:41 cedric-hp-elitedesk-800-g2-sff gdm-launch-environment][724]: G>

juin 11 17:48:40 cedric-hp-elitedesk-800-g2-sff wpa_supplicant[656]: bgscan sim>

juin 11 17:48:37 cedric-hp-elitedesk-800-g2-sff systemd[1177]: Failed to start >

juin 11 17:48:36 cedric-hp-elitedesk-800-g2-sff gdm-password][1165]: gkr-pam: u>

juin 11 17:48:26 cedric-hp-elitedesk-800-g2-sff kernel: mei_wdt 0000:00:16.0-05>

juin 11 17:48:25 cedric-hp-elitedesk-800-g2-sff kernel: x86/cpu: SGX disabled b>

-- Boot 4435cc60d8d04a87b4c03d36fd8f2341 --

juin 10 20:17:42 cedric-hp-elitedesk-800-g2-sff gdm3[709]: Gdm: Failed to conta>

juin 10 19:20:24 cedric-hp-elitedesk-800-g2-sff gdm-launch-environment][719]: G>

juin 10 19:20:21 cedric-hp-elitedesk-800-g2-sff systemd[1206]: Failed to start >

juin 10 19:20:21 cedric-hp-elitedesk-800-g2-sff systemd[1206]: Failed to start >

juin 10 19:20:20 cedric-hp-elitedesk-800-g2-sff gdm-password][1194]: gkr-pam: u>

juin 10 19:20:10 cedric-hp-elitedesk-800-g2-sff wpa_supplicant[656]: bgscan sim>

ceric · 11-06-2024 20:20:56

ça y est j'ai trouvé le fichier :

juin 11 20:16:19 cedric-hp-elitedesk-800-g2-sff systemd[1195]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1363.scope - Application launched by gnome-session-binary.

juin 11 20:16:19 cedric-hp-elitedesk-800-g2-sff systemd[1195]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1365.scope - Application launched by gnome-session-binary.

-- Boot e869153597e14b2fa6def6b0cc88ff71 --

juin 11 17:48:37 cedric-hp-elitedesk-800-g2-sff systemd[1177]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1358.scope - Application launched by gnome-session-binary.

-- Boot 4435cc60d8d04a87b4c03d36fd8f2341 --

juin 10 19:20:21 cedric-hp-elitedesk-800-g2-sff systemd[1206]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1375.scope - Application launched by gnome-session-binary.

juin 10 19:20:21 cedric-hp-elitedesk-800-g2-sff systemd[1206]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1376.scope - Application launched by gnome-session-binary.

-- Boot 78574b35bb5d4f21a225d801d826e805 --

juin 10 19:10:00 cedric-hp-elitedesk-800-g2-sff systemd[1194]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1665.scope - Application launched by gnome-session-binary.

juin 10 19:09:58 cedric-hp-elitedesk-800-g2-sff systemd[1194]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1371.scope - Application launched by gnome-session-binary.

-- Boot 953ddad5894b452e87488874bedea4d3 --

juin 09 13:14:12 cedric-hp-elitedesk-800-g2-sff systemd[1201]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1363.scope - Application launched by gnome-session-binary.

-- Boot ad4f7a217a314120be499550a857a0be --

juin 09 07:23:32 cedric-hp-elitedesk-800-g2-sff systemd[1215]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1664.scope - Application launched by gnome-session-binary.

-- Boot 5f262b1e862d4f03a8cc7e2bc694b887 --

juin 07 21:39:37 cedric-hp-elitedesk-800-g2-sff systemd[1205]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1668.scope - Application launched by gnome-session-binary.

juin 07 21:39:35 cedric-hp-elitedesk-800-g2-sff systemd[1205]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1368.scope - Application launched by gnome-session-binary.

juin 07 21:39:35 cedric-hp-elitedesk-800-g2-sff systemd[1205]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1354.scope - Application launched by gnome-session-binary.

-- Boot da337e01decd44a3b5037bd8aa9151bc --

juin 07 18:58:59 cedric-hp-elitedesk-800-g2-sff systemd[1214]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1338.scope - Application launched by gnome-session-binary.

juin 07 18:58:59 cedric-hp-elitedesk-800-g2-sff systemd[1214]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1339.scope - Application launched by gnome-session-binary.

-- Boot b40e57d918a1400f8697a499b7fa2b73 --

juin 06 19:39:19 cedric-hp-elitedesk-800-g2-sff systemd[1216]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1374.scope - Application launched by gnome-session-binary.

juin 06 19:39:19 cedric-hp-elitedesk-800-g2-sff systemd[1216]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1376.scope - Application launched by gnome-session-binary.

-- Boot b2f9b9e1c6474f8ea04001327882fe47 --

juin 05 22:38:12 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1651.scope - Application launched by gnome-session-binary.

-- Boot e55d109fa11949008e4ed5a34424f242 --

juin 05 19:18:12 cedric-hp-elitedesk-800-g2-sff systemd[1212]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1672.scope - Application launched by gnome-session-binary.

juin 05 19:18:10 cedric-hp-elitedesk-800-g2-sff systemd[1212]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1380.scope - Application launched by gnome-session-binary.

juin 05 19:18:10 cedric-hp-elitedesk-800-g2-sff systemd[1212]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1370.scope - Application launched by gnome-session-binary.

-- Boot 38eb6d0ce0f44ab9a91671a655df01e8 --

juin 04 21:26:47 cedric-hp-elitedesk-800-g2-sff systemd[1213]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1376.scope - Application launched by gnome-session-binary.

-- Boot 83b40e054bcb4763bc9bc622190fe144 --

juin 03 17:58:29 cedric-hp-elitedesk-800-g2-sff systemd[1213]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1374.scope - Application launched by gnome-session-binary.

-- Boot abd2d09be9494263bad85de8f8a05865 --

juin 02 16:06:26 cedric-hp-elitedesk-800-g2-sff systemd[1207]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1684.scope - Application launched by gnome-session-binary.

juin 02 16:06:25 cedric-hp-elitedesk-800-g2-sff systemd[1207]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1374.scope - Application launched by gnome-session-binary.

juin 02 16:06:25 cedric-hp-elitedesk-800-g2-sff systemd[1207]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1375.scope - Application launched by gnome-session-binary.

-- Boot 171e1190719d493996833aa2b492012c --

juin 02 14:47:59 cedric-hp-elitedesk-800-g2-sff systemd[1205]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1363.scope - Application launched by gnome-session-binary.

juin 02 14:47:59 cedric-hp-elitedesk-800-g2-sff systemd[1205]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1364.scope - Application launched by gnome-session-binary.

-- Boot 943a365026ff486b8417735fe3c59c36 --

juin 02 09:08:29 cedric-hp-elitedesk-800-g2-sff systemd[1209]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1361.scope - Application launched by gnome-session-binary.

-- Boot c759f0008d5743dc96608bcf3973adf5 --

juin 01 20:44:24 cedric-hp-elitedesk-800-g2-sff systemd[1201]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1364.scope - Application launched by gnome-session-binary.

juin 01 20:44:24 cedric-hp-elitedesk-800-g2-sff systemd[1201]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1355.scope - Application launched by gnome-session-binary.

juin 01 20:44:24 cedric-hp-elitedesk-800-g2-sff systemd[1201]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1357.scope - Application launched by gnome-session-binary.

-- Boot 8adb3ebdf8774a6fae0f45c0e1ee8d35 --

juin 01 19:00:24 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1680.scope - Application launched by gnome-session-binary.

juin 01 19:00:22 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1360.scope - Application launched by gnome-session-binary.

juin 01 19:00:22 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1362.scope - Application launched by gnome-session-binary.

-- Boot bb8ee2c360364eb691c82a92ce8420b0 --

juin 01 12:49:53 cedric-hp-elitedesk-800-g2-sff systemd[1205]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1684.scope - Application launched by gnome-session-binary.

juin 01 12:49:51 cedric-hp-elitedesk-800-g2-sff systemd[1205]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1378.scope - Application launched by gnome-session-binary.

juin 01 12:49:51 cedric-hp-elitedesk-800-g2-sff systemd[1205]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1368.scope - Application launched by gnome-session-binary.

-- Boot edc8506f5d224372b8a462add3f076ee --

juin 01 12:47:59 cedric-hp-elitedesk-800-g2-sff systemd[1219]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1408.scope - Application launched by gnome-session-binary.

-- Boot 8b02da5e888b4ddabac8bf3a5a598111 --

mai 31 19:49:05 cedric-hp-elitedesk-800-g2-sff systemd[1204]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1680.scope - Application launched by gnome-session-binary.

mai 31 19:49:03 cedric-hp-elitedesk-800-g2-sff systemd[1204]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1379.scope - Application launched by gnome-session-binary.

mai 31 19:49:03 cedric-hp-elitedesk-800-g2-sff systemd[1204]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1368.scope - Application launched by gnome-session-binary.

-- Boot b7af28fddb0743eb826a4a1cb74001bf --

mai 31 17:36:44 cedric-hp-elitedesk-800-g2-sff systemd[1203]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1370.scope - Application launched by gnome-session-binary.

mai 31 17:36:44 cedric-hp-elitedesk-800-g2-sff systemd[1203]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1360.scope - Application launched by gnome-session-binary.

mai 31 17:36:44 cedric-hp-elitedesk-800-g2-sff systemd[1203]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1362.scope - Application launched by gnome-session-binary.

-- Boot 26fba92e1fde43069a02d5c674bcb4bc --

mai 31 17:09:49 cedric-hp-elitedesk-800-g2-sff systemd[1200]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1376.scope - Application launched by gnome-session-binary.

mai 31 17:09:49 cedric-hp-elitedesk-800-g2-sff systemd[1200]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1364.scope - Application launched by gnome-session-binary.

mai 31 17:09:49 cedric-hp-elitedesk-800-g2-sff systemd[1200]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1365.scope - Application launched by gnome-session-binary.

-- Boot 153241e86c69425eac0eca2e3f08b863 --

mai 31 01:05:48 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1362.scope - Application launched by gnome-session-binary.

mai 31 01:05:48 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1364.scope - Application launched by gnome-session-binary.

-- Boot f57e265e90314786adb23b8fdf979488 --

mai 31 00:11:02 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1366.scope - Application launched by gnome-session-binary.

mai 31 00:11:02 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1356.scope - Application launched by gnome-session-binary.

mai 31 00:11:02 cedric-hp-elitedesk-800-g2-sff systemd[1202]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1357.scope - Application launched by gnome-session-binary.

-- Boot 3c3dd8dbb0f943a093d3c368c5dd636f --

mai 30 23:56:24 cedric-hp-elitedesk-800-g2-sff systemd[1209]: Failed to start app-gnome-im\x2dlaunch-1678.scope - Application launched by gnome-session-binary.

mai 30 23:56:22 cedric-hp-elitedesk-800-g2-sff systemd[1209]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1355.scope - Application launched by gnome-session-binary.

mai 30 23:56:22 cedric-hp-elitedesk-800-g2-sff systemd[1209]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1358.scope - Application launched by gnome-session-binary.

-- Boot 9d6483352d2d4cd9b0266168dcde297b --

mai 30 23:45:27 cedric-hp-elitedesk-800-g2-sff systemd[1204]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1383.scope - Application launched by gnome-session-binary.

mai 30 23:45:27 cedric-hp-elitedesk-800-g2-sff systemd[1204]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1369.scope - Application launched by gnome-session-binary.

mai 30 23:45:27 cedric-hp-elitedesk-800-g2-sff systemd[1204]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1370.scope - Application launched by gnome-session-binary.

-- Boot c821d1aa8449466dbb476ea2e92049cc --

mai 30 18:56:05 cedric-hp-elitedesk-800-g2-sff systemd[1209]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1351.scope - Application launched by gnome-session-binary.

-- Boot 45b92152edd1464b9d2e01894e7ba5d2 --

mai 29 23:35:58 cedric-hp-elitedesk-800-g2-sff systemd[1203]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1381.scope - Application launched by gnome-session-binary.

mai 29 23:35:58 cedric-hp-elitedesk-800-g2-sff systemd[1203]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1373.scope - Application launched by gnome-session-binary.

mai 29 23:35:58 cedric-hp-elitedesk-800-g2-sff systemd[1203]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1374.scope - Application launched by gnome-session-binary.

-- Boot 0d0b8eb5d2e7414cbfc2646983860019 --

mai 29 21:15:07 cedric-hp-elitedesk-800-g2-sff systemd[1201]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1354.scope - Application launched by gnome-session-binary.

mai 29 21:15:07 cedric-hp-elitedesk-800-g2-sff systemd[1201]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1357.scope - Application launched by gnome-session-binary.

-- Boot 82f8ee903b094d63adc97894c642370c --

mai 29 19:05:26 cedric-hp-elitedesk-800-g2-sff systemd[1203]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-5190.scope - Application launched by gnome-session-binary.

mai 29 19:05:26 cedric-hp-elitedesk-800-g2-sff systemd[1203]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-5191.scope - Application launched by gnome-session-binary.

mai 29 18:10:36 cedric-hp-elitedesk-800-g2-sff systemd[1203]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1368.scope - Application launched by gnome-session-binary.

-- Boot af9d632e5667420ca771d301677dcafd --

mai 29 00:40:00 cedric-hp-elitedesk-800-g2-sff systemd[1204]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1368.scope - Application launched by gnome-session-binary.

mai 29 00:40:00 cedric-hp-elitedesk-800-g2-sff systemd[1204]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1370.scope - Application launched by gnome-session-binary.

-- Boot 4a6ce227766b4995828acc39374f31fe --

mai 29 00:27:15 cedric-hp-elitedesk-800-g2-sff systemd[1204]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1356.scope - Application launched by gnome-session-binary.

-- Boot a605b4174ba4405a9da2d75029d63190 --

mai 29 00:24:18 cedric-hp-elitedesk-800-g2-sff sudo[3339]:   cedric : user NOT in sudoers ; TTY=pts/0 ; PWD=/home/cedric ; USER=root ; COMMAND=/usr/bin/nano /etc/default/grub

mai 29 00:06:13 cedric-hp-elitedesk-800-g2-sff systemd[1209]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1365.scope - Application launched by gnome-session-binary.

-- Boot 9d245f0dd3ac4faa95e20938cecfcf81 --

mai 28 23:59:04 cedric-hp-elitedesk-800-g2-sff systemd[1200]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1639.scope - Application launched by gnome-session-binary.

mai 28 23:59:03 cedric-hp-elitedesk-800-g2-sff systemd[1200]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1368.scope - Application launched by gnome-session-binary.

mai 28 23:59:03 cedric-hp-elitedesk-800-g2-sff systemd[1200]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1359.scope - Application launched by gnome-session-binary.

mai 28 23:59:03 cedric-hp-elitedesk-800-g2-sff systemd[1200]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1361.scope - Application launched by gnome-session-binary.

-- Boot 4c82cd6dbe9a409eab3abab0242c0e2e --

mai 28 23:40:02 cedric-hp-elitedesk-800-g2-sff systemd[1208]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1652.scope - Application launched by gnome-session-binary.

mai 28 23:40:02 cedric-hp-elitedesk-800-g2-sff systemd[1208]: Failed to start app-gnome-im\x2dlaunch-1680.scope - Application launched by gnome-session-binary.

-- Boot b25ae7d87e094eb0b28347957eec32eb --

mai 28 23:10:19 cedric-hp-elitedesk-800-g2-sff systemd[1201]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1362.scope - Application launched by gnome-session-binary.

mai 28 23:10:19 cedric-hp-elitedesk-800-g2-sff systemd[1201]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1355.scope - Application launched by gnome-session-binary.

-- Boot 1d92236222344f12bdce578e1357cae2 --

mai 28 22:33:36 cedric-hp-elitedesk-800-g2-sff systemd[1206]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1361.scope - Application launched by gnome-session-binary.

-- Boot e3d53ffd788e4c3eaf6061c862fb3d7e --

mai 28 22:22:06 cedric-hp-elitedesk-800-g2-sff systemd[1217]: Failed to start app-gnome-xdg\x2duser\x2ddirs-1395.scope - Application launched by gnome-session-binary.

mai 28 22:22:06 cedric-hp-elitedesk-800-g2-sff systemd[1217]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1385.scope - Application launched by gnome-session-binary.

mai 28 22:22:06 cedric-hp-elitedesk-800-g2-sff systemd[1217]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1386.scope - Application launched by gnome-session-binary.

-- Boot d0d59876f92f45c19b1e86a25dfdc1ca --

mai 28 20:58:01 cedric-hp-elitedesk-800-g2-sff sudo[2831]:   cedric : user NOT in sudoers ; TTY=pts/0 ; PWD=/home/cedric ; USER=root ; COMMAND=/usr/bin/ls -l /boot/efi/EFI/debian

mai 28 20:51:55 cedric-hp-elitedesk-800-g2-sff systemd[1210]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1373.scope - Application launched by gnome-session-binary.

mai 28 20:51:55 cedric-hp-elitedesk-800-g2-sff systemd[1210]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1374.scope - Application launched by gnome-session-binary.

Tawal · 11-06-2024 21:50:50

Hello,

Peux-tu donner le retour de :

systemctl --user status gnome-keyring-daemon.service --no-pager -l

Car je suppose qu'il y a un service et un démarrage avec la session (double emploi).

Edit:

$ apt-file show gnome-keyring

gnome-keyring: /etc/xdg/autostart/gnome-keyring-pkcs11.desktop

gnome-keyring: /etc/xdg/autostart/gnome-keyring-secrets.desktop

gnome-keyring: /etc/xdg/autostart/gnome-keyring-ssh.desktop

…

gnome-keyring: /usr/lib/systemd/user/gnome-keyring-daemon.service

gnome-keyring: /usr/lib/systemd/user/gnome-keyring-daemon.socket

…

Dernière modification par Tawal (11-06-2024 22:04:06)

ceric · 12-06-2024 19:51:20

@Tawal, ci-dessous la commande :

systemctl --user status gnome-keyring-daemon.service --no-pager -l

● gnome-keyring-daemon.service - GNOME Keyring daemon

     Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.service; enabled; preset: enabled)

     Active: active (running) since Wed 2024-06-12 20:44:56 CEST; 5min ago

TriggeredBy: ● gnome-keyring-daemon.socket

   Main PID: 1234 (gnome-keyring-d)

      Tasks: 4 (limit: 19018)

     Memory: 5.0M

        CPU: 34ms

     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-keyring-daemon.service

             └─1234 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring

juin 12 20:44:56 cedric-hp-elitedesk-800-g2-sff gnome-keyring-daemon[1234]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring

juin 12 20:44:56 cedric-hp-elitedesk-800-g2-sff systemd[1206]: Started gnome-keyring-daemon.service - GNOME Keyring daemon.

juin 12 20:44:57 cedric-hp-elitedesk-800-g2-sff gnome-keyring-daemon[1234]: The Secret Service was already initialized

juin 12 20:44:57 cedric-hp-elitedesk-800-g2-sff gnome-keyring-d[1234]: The Secret Service was already initialized

juin 12 20:44:57 cedric-hp-elitedesk-800-g2-sff gnome-keyring-d[1234]: The PKCS#11 component was already initialized

juin 12 20:44:57 cedric-hp-elitedesk-800-g2-sff gnome-keyring-daemon[1234]: The PKCS#11 component was already initialized

Pour votre information, je suis en dual boot avec ubuntu 24.04.

Dernière modification par ceric (12-06-2024 19:52:38)

Tawal · 12-06-2024 20:01:11

On voit ceci dans ton retour :

juin 12 20:44:57 cedric-hp-elitedesk-800-g2-sff gnome-keyring-daemon[1234]: The Secret Service was already initialized

juin 12 20:44:57 cedric-hp-elitedesk-800-g2-sff gnome-keyring-d[1234]: The Secret Service was already initialized

juin 12 20:44:57 cedric-hp-elitedesk-800-g2-sff gnome-keyring-d[1234]: The PKCS#11 component was already initialized

juin 12 20:44:57 cedric-hp-elitedesk-800-g2-sff gnome-keyring-daemon[1234]: The PKCS#11 component was already initialized

Je pense que les fichiers .desktop fournis par le paquet gnome-keyring sont en redondance si le service est activé.
Pour moi 2 choix possibles :
- désactiver le service
- enlever les fichiers .desktop

Pour désactiver le service :

systemctl --user stop gnome-keyring-daemon.service

puis

systemctl --user disable gnome-keyring-daemon.service

ceric · 12-06-2024 20:03:40

@Tawal, je ne risque pas de dézinguer mon dual boot en désactivant ce service?
Edit A : Je les ai quand même tenté.

Edit B : Je viens de redémarrer le HP, sans encombres.
Edit C : Souhaites-tu que je ré exécute ta commande précédente?

Dernière modification par ceric (12-06-2024 20:12:38)

Tawal · 12-06-2024 20:23:42

ceric a écrit :

Souhaites-tu que je ré exécute ta commande précédente?

Oui celle-ci pour vérifier que le service est bien désactivé :

systemctl --user status gnome-keyring-daemon.service --no-pager -l

Si oui, alors tu peux vérifier dans les logs du boot en cours si les messages d'erreurs sont apparus ou non.

journalctl -p err -b0 --no-pager

ceric · 12-06-2024 20:28:31

systemctl --user status gnome-keyring-daemon.service --no-pager -l

● gnome-keyring-daemon.service - GNOME Keyring daemon

     Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.service; enabled; preset: enabled)

     Active: active (running) since Wed 2024-06-12 21:07:14 CEST; 20min ago

TriggeredBy: ● gnome-keyring-daemon.socket

   Main PID: 1228 (gnome-keyring-d)

      Tasks: 4 (limit: 19018)

     Memory: 4.9M

        CPU: 41ms

     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-keyring-daemon.service

             └─1228 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring

juin 12 21:07:15 cedric-hp-elitedesk-800-g2-sff gnome-keyring-daemon[1228]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring

juin 12 21:07:14 cedric-hp-elitedesk-800-g2-sff systemd[1197]: Started gnome-keyring-daemon.service - GNOME Keyring daemon.

juin 12 21:07:15 cedric-hp-elitedesk-800-g2-sff gnome-keyring-daemon[1228]: The Secret Service was already initialized

juin 12 21:07:15 cedric-hp-elitedesk-800-g2-sff gnome-keyring-d[1228]: The Secret Service was already initialized

juin 12 21:07:15 cedric-hp-elitedesk-800-g2-sff gnome-keyring-daemon[1228]: The PKCS#11 component was already initialized

juin 12 21:07:15 cedric-hp-elitedesk-800-g2-sff gnome-keyring-d[1228]: The PKCS#11 component was already initialized

Tawal · 12-06-2024 21:03:08

Arff, il faut tout refaire et ajouter la désactivation du socket accompagnant le service.
Donc en user cette suite de commandes :

systemctl --user stop gnome-keyring-daemon.service gnome-keyring-daemon.socket

systemctl --user disable gnome-keyring-daemon.service gnome-keyring-daemon.socket

Puis un redémarrage et une vérification.

ceric · 12-06-2024 21:14:24

systemctl --user status gnome-keyring-daemon.service --no-pager -l

● gnome-keyring-daemon.service - GNOME Keyring daemon

     Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.service; enabled; preset: enabled)

     Active: active (running) since Wed 2024-06-12 22:11:49 CEST; 1min 44s ago

TriggeredBy: ● gnome-keyring-daemon.socket

   Main PID: 1230 (gnome-keyring-d)

      Tasks: 4 (limit: 19018)

     Memory: 5.0M

        CPU: 35ms

     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-keyring-daemon.service

             └─1230 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring

juin 12 22:11:49 cedric-hp-elitedesk-800-g2-sff gnome-keyring-daemon[1230]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring

juin 12 22:11:49 cedric-hp-elitedesk-800-g2-sff systemd[1201]: Started gnome-keyring-daemon.service - GNOME Keyring daemon.

juin 12 22:11:49 cedric-hp-elitedesk-800-g2-sff gnome-keyring-daemon[1230]: The Secret Service was already initialized

juin 12 22:11:49 cedric-hp-elitedesk-800-g2-sff gnome-keyring-d[1230]: The Secret Service was already initialized

juin 12 22:11:49 cedric-hp-elitedesk-800-g2-sff gnome-keyring-daemon[1230]: The PKCS#11 component was already initialized

juin 12 22:11:49 cedric-hp-elitedesk-800-g2-sff gnome-keyring-d[1230]: The PKCS#11 component was already initialized

Tawal · 12-06-2024 21:39:35

Repasse les commandes :

systemctl --user stop gnome-keyring-daemon.service gnome-keyring-daemon.socket

systemctl --user disable gnome-keyring-daemon.service gnome-keyring-daemon.socket

Puis sans redémarrer, vérifie le service :

systemctl --user status gnome-keyring-daemon.service --no-pager -l

Edit:
Donne tous les retours même s'il n'y en a pas merci.

Dernière modification par Tawal (12-06-2024 21:40:17)

ceric · 12-06-2024 21:44:29

@Tawal c'est sympa de te pencher sur mon cas mais je vais m'arrêter là.
J'ai tenté tes dernières commandes au #16 mais la vérification suite à un redémarrage au #17 me font penser que ce n'est pas la peine d'insister.
Mon dual boot fonctionne très bien même si j'ai ces erreurs, je n'ai pas envie de tout casser.

Tawal · 12-06-2024 22:21:36

Oui ce n'est qu'une redondance au démarrage.
Il n'y a rien de grave non plus.
Ton Dual-Boot ne risque absolument rien avec les manipulations que nous avons faites.
Nous ne traitions qu'un service interne à un des 2 systèmes (Debian).
Edit: Et qui plus est un service non vital au système …

Dernière modification par Tawal (12-06-2024 22:23:47)

Debian-facile

#1 31-05-2024 00:19:45

[Clos] Erreurs dans journalctl

#2 31-05-2024 12:21:06

Re : [Clos] Erreurs dans journalctl

#3 31-05-2024 17:02:34

Re : [Clos] Erreurs dans journalctl

#4 31-05-2024 17:10:39

Re : [Clos] Erreurs dans journalctl

#5 11-06-2024 19:55:10

Re : [Clos] Erreurs dans journalctl

#6 11-06-2024 19:58:07

Re : [Clos] Erreurs dans journalctl

#7 11-06-2024 20:12:31

Re : [Clos] Erreurs dans journalctl

#8 11-06-2024 20:18:10

Re : [Clos] Erreurs dans journalctl

#9 11-06-2024 20:20:56

Re : [Clos] Erreurs dans journalctl

#10 11-06-2024 21:50:50

Re : [Clos] Erreurs dans journalctl

#11 12-06-2024 19:51:20

Re : [Clos] Erreurs dans journalctl

#12 12-06-2024 20:01:11

Re : [Clos] Erreurs dans journalctl

#13 12-06-2024 20:03:40

Re : [Clos] Erreurs dans journalctl

#14 12-06-2024 20:23:42

Re : [Clos] Erreurs dans journalctl

#15 12-06-2024 20:28:31

Re : [Clos] Erreurs dans journalctl

#16 12-06-2024 21:03:08

Re : [Clos] Erreurs dans journalctl

#17 12-06-2024 21:14:24

Re : [Clos] Erreurs dans journalctl

#18 12-06-2024 21:39:35

Re : [Clos] Erreurs dans journalctl

#19 12-06-2024 21:44:29

Re : [Clos] Erreurs dans journalctl

#20 12-06-2024 22:21:36

Re : [Clos] Erreurs dans journalctl

Pied de page des forums