[Résolu] Session utilisateur corrompue, reset index tracker impossible

--gilles-- · 25-09-2020 20:16:25

Depuis plusieurs jours j'avais déjà des problèmes quand je déplaçais la fenêtre du Terminal, j'avais des traînées vidéos qui restaient en arrière du déplacement. Cet après-midi, il y a eu éclair de foudre et quasiment tout de suite un tonnerre très fort, par mesure de précaution j'ai ensuite éteint l'ordi. Quand je l'ai rallumé impossible d'aller dans ma session que ce soit en X11 ou en Wayland, cela reste noir avec juste le pointeur et au bout de quelques minutes je retombe sur l'écran de connexion. Je suis connecté avec une autre session utilisateur, mais je n'ai pas la moindre idée de comment diagnostiquer et réparer cette panne limitée à une session.

J'ai tenté un :

debsums --changed

/var/lib/rkhunter/db/mirrors.dat

mais cela m'a donné que les fichiers de mises à jour de rkhunter, donc c'est normal.

J'ai copié des fichiers de ma session qui ne fonctionne pas en graphique via su -, cp chgp et chown vers ma session graphique actuelle avec le Terminal, mais je préférerais que ma session originale refonctionne en graphique.

Suite à la lecture de journalctl -r -p err :

journalctl  -r -p err

sept. 25 20:07:00 commandes-console gdm-launch-environment][7733]: pam_systemd(gdm-launch-environment:session): Failed to release ses>

sept. 25 20:06:52 commandes-console gdm-password][8447]: gkr-pam: unable to locate daemon control file

sept. 25 19:55:04 commandes-console systemd[8127]: Failed to start GNOME Shell on Wayland.

sept. 25 19:53:24 commandes-console gdm-password][8117]: gkr-pam: unable to locate daemon control file

sept. 25 17:25:20 commandes-console gdm-launch-environment][544]: pam_systemd(gdm-launch-environment:session): Failed to release sess>

sept. 25 17:25:11 commandes-console gdm-password][1939]: gkr-pam: unable to locate daemon control file

sept. 25 17:21:49 commandes-console systemd[1639]: Failed to start GNOME Shell on Wayland.

sept. 25 17:20:12 commandes-console gdm-password][1628]: gkr-pam: unable to locate daemon control file

sept. 25 17:19:54 commandes-console systemd[1341]: Failed to start GNOME Shell on Wayland.

sept. 25 17:18:14 commandes-console gdm-password][1331]: gkr-pam: unable to locate daemon control file

sept. 25 17:17:36 commandes-console colord-sane[577]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied

sept. 25 17:17:36 commandes-console colord-sane[577]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied

sept. 25 17:17:36 commandes-console colord-sane[577]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied

sept. 25 17:17:36 commandes-console colord-sane[577]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied

sept. 25 17:17:25 commandes-console /hpfax[589]: [589]: error: Failed to create /var/spool/cups/tmp/.hplip

sept. 25 17:17:18 commandes-console smartd[486]: http://knowledge.seagate.com/articles/en_US/FAQ/213891en

sept. 25 17:17:18 commandes-console smartd[486]: http://knowledge.seagate.com/articles/en_US/FAQ/207931en

sept. 25 17:17:18 commandes-console smartd[486]: see the following Seagate web pages:

sept. 25 17:17:18 commandes-console smartd[486]: Device: /dev/sda [SAT], WARNING: A firmware update for this drive may be available,

sept. 25 17:17:02 commandes-console kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through

sept. 25 17:17:02 commandes-console kernel: sd 6:0:0:0: [sdb] No Caching mode page found

sept. 25 17:17:02 commandes-console kernel: ACPI Error: Aborting method \_SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (202>

sept. 25 17:17:02 commandes-console kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20200528/dswload2-477)

sept. 25 17:17:02 commandes-console kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0._OSC.CAPD], AE_ALREADY_EX>

sept. 25 17:17:02 commandes-console kernel: ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared 5, ACPI requires 4>

sept. 25 17:17:02 commandes-console kernel: acpi LNXCPU:01: Invalid PBLK length [7]

sept. 25 17:17:02 commandes-console kernel: acpi LNXCPU:00: Invalid PBLK length [7]

-- Reboot --

sept. 25 17:15:14 commandes-console systemd[1839]: Failed to start GNOME Shell on X11.

sept. 25 17:13:35 commandes-console gdm-launch-environment][1302]: pam_systemd(gdm-launch-environment:session): Failed to release ses>

sept. 25 17:13:19 commandes-console gdm-password][1830]: gkr-pam: unable to locate daemon control file

sept. 25 17:13:07 commandes-console /hpfax[1767]: [1767]: error: Failed to create /var/spool/cups/tmp/.hplip

sept. 25 17:13:01 commandes-console colord-sane[1560]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied

sept. 25 17:13:01 commandes-console colord-sane[1560]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied

sept. 25 17:13:01 commandes-console colord-sane[1560]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied

sept. 25 17:13:01 commandes-console colord-sane[1560]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied

sept. 25 17:12:56 commandes-console kernel: usb 7-2: device descriptor read/64, error -71

sept. 25 17:12:56 commandes-console kernel: usb usb7-port2: disabled by hub (EMI?), re-enabling...

sept. 25 17:12:54 commandes-console kernel: usb usb7-port2: disabled by hub (EMI?), re-enabling...

sept. 25 17:12:52 commandes-console kernel: usb usb7-port2: disabled by hub (EMI?), re-enabling...

sept. 25 17:12:34 commandes-console smartd[998]: http://knowledge.seagate.com/articles/en_US/FAQ/213891en

sept. 25 17:12:34 commandes-console smartd[998]: http://knowledge.seagate.com/articles/en_US/FAQ/207931en

sept. 25 17:12:34 commandes-console smartd[998]: see the following Seagate web pages:

sept. 25 17:12:34 commandes-console smartd[998]: Device: /dev/sda [SAT], WARNING: A firmware update for this drive may be available,

sept. 25 17:10:54 commandes-console systemd[1]: Failed to start Network Manager.

sept. 25 17:10:54 commandes-console NetworkManager[445]: <error> [1601046654.8307] bus-manager: cannot connect to D-Bus: Impossible d>

sept. 25 17:10:10 commandes-console kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through

sept. 25 17:10:10 commandes-console kernel: sd 6:0:0:0: [sdb] No Caching mode page found

sept. 25 17:10:10 commandes-console kernel: ACPI Error: Aborting method \_SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (202>

sept. 25 17:10:10 commandes-console kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20200528/dswload2-477)

sept. 25 17:10:10 commandes-console kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0._OSC.CAPD], AE_ALREADY_EX>

sept. 25 17:10:10 commandes-console kernel: ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared 5, ACPI requires 4>

sept. 25 17:10:10 commandes-console kernel: acpi LNXCPU:01: Invalid PBLK length [7]

sept. 25 17:10:10 commandes-console kernel: acpi LNXCPU:00: Invalid PBLK length [7]

-- Reboot --

sept. 25 14:46:39 commandes-console systemd[2042]: Failed to start Tracker metadata extractor.

sept. 25 14:44:49 commandes-console systemd[2042]: Failed to start Tracker metadata extractor.

sept. 25 14:42:12 commandes-console systemd[2042]: Failed to start Tracker metadata extractor.

sept. 25 14:40:17 commandes-console systemd[2042]: Failed to start Tracker metadata extractor.

sept. 25 14:39:04 commandes-console systemd[2042]: Failed to start GNOME Shell on X11.

sept. 25 14:38:31 commandes-console systemd[2042]: Failed to start Tracker metadata extractor.

sept. 25 14:37:29 commandes-console systemd[2042]: Failed to start GNOME Shell on X11.

sept. 25 14:36:42 commandes-console systemd[2042]: Failed to start Tracker metadata extractor.

sept. 25 14:35:54 commandes-console systemd[2042]: Failed to start GNOME Shell on X11.

sept. 25 14:34:18 commandes-console systemd[2042]: Failed to start GNOME Shell on X11.

sept. 25 14:32:30 commandes-console gdm-launch-environment][1564]: pam_systemd(gdm-launch-environment:session): Failed to release ses>

sept. 25 14:32:15 commandes-console gdm-password][2032]: gkr-pam: unable to locate daemon control file

sept. 25 14:31:22 commandes-console smartd[1260]: http://knowledge.seagate.com/articles/en_US/FAQ/213891en

sept. 25 14:31:22 commandes-console smartd[1260]: http://knowledge.seagate.com/articles/en_US/FAQ/207931en

sept. 25 14:31:22 commandes-console smartd[1260]: see the following Seagate web pages:

sept. 25 14:31:22 commandes-console smartd[1260]: Device: /dev/sda [SAT], WARNING: A firmware update for this drive may be available,

sept. 25 14:21:07 commandes-console systemd[1]: Failed to start Network Manager.

sept. 25 14:21:07 commandes-console NetworkManager[450]: <error> [1601036467.9060] bus-manager: cannot connect to D-Bus: Impossible d>

sept. 25 14:20:00 commandes-console kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through

sept. 25 14:20:00 commandes-console kernel: sd 6:0:0:0: [sdb] No Caching mode page found

sept. 25 14:20:00 commandes-console kernel: ACPI Error: Aborting method \_SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (202>

sept. 25 14:20:00 commandes-console kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20200528/dswload2-477)

sept. 25 14:20:00 commandes-console kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0._OSC.CAPD], AE_ALREADY_EX>

sept. 25 14:20:00 commandes-console kernel: ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared 5, ACPI requires 4>

sept. 25 14:20:00 commandes-console kernel: acpi LNXCPU:01: Invalid PBLK length [7]

sept. 25 14:20:00 commandes-console kernel: acpi LNXCPU:00: Invalid PBLK length [7]

-- Reboot --

sept. 25 14:19:31 commandes-console systemd[1]: Failed unmounting /tmp.

sept. 25 14:17:15 commandes-console systemd[9257]: Failed to start Tracker metadata extractor.

sept. 25 07:58:17 commandes-console systemd[10671]: Failed to start Tracker metadata extractor.

sept. 25 07:56:53 commandes-console systemd[10671]: Failed to start Tracker metadata database store and lookup manager.

sept. 25 07:56:53 commandes-console systemd[10671]: Failed to start Tracker metadata database store and lookup manager.

sept. 25 07:56:53 commandes-console systemd[10671]: Failed to start Tracker file system data miner.

sept. 25 07:56:53 commandes-console systemd[10671]: Failed to start Tracker file system data miner.

sept. 25 07:56:52 commandes-console systemd[10671]: Failed to start Tracker file system data miner.

sept. 25 07:56:51 commandes-console systemd[10671]: Failed to start Sound Service.

sept. 25 07:56:51 commandes-console systemd[10671]: Failed to start Sound Service.

sept. 25 07:56:50 commandes-console systemd[10671]: Failed to start Sound Service.

sept. 25 07:56:49 commandes-console systemd[10671]: Failed to start Sound Service.

sept. 25 07:56:48 commandes-console systemd[10671]: Failed to start Sound Service.

sept. 25 07:56:48 commandes-console systemd[10671]: Failed to start Sound Service.

sept. 25 07:55:32 commandes-console gdm-launch-environment][8751]: pam_systemd(gdm-launch-environment:session): Failed to release ses>

sept. 25 07:55:18 commandes-console gdm-password][9247]: gkr-pam: unable to locate daemon control file

sept. 25 07:51:44 commandes-console smartd[8421]: http://knowledge.seagate.com/articles/en_US/FAQ/213891en

sept. 25 07:51:44 commandes-console smartd[8421]: http://knowledge.seagate.com/articles/en_US/FAQ/207931en

sept. 25 07:51:44 commandes-console smartd[8421]: see the following Seagate web pages:

sept. 25 07:51:44 commandes-console smartd[8421]: Device: /dev/sda [SAT], WARNING: A firmware update for this drive may be available,

sept. 25 07:36:46 commandes-console systemd[1]: Failed to start Network Manager.

sept. 25 07:36:45 commandes-console NetworkManager[444]: <error> [1601012205.9410] bus-manager: cannot connect to D-Bus: Impossible d>

sept. 25 07:35:35 commandes-console kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through

sept. 25 07:35:35 commandes-console kernel: sd 6:0:0:0: [sdb] No Caching mode page found

sept. 25 07:35:35 commandes-console kernel: ACPI Error: Aborting method \_SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (202>

sept. 25 07:35:35 commandes-console kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20200528/dswload2-477)

sept. 25 07:35:35 commandes-console kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0._OSC.CAPD], AE_ALREADY_EX>

sept. 25 07:35:35 commandes-console kernel: ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared 5, ACPI requires 4>

sept. 25 07:35:35 commandes-console kernel: acpi LNXCPU:01: Invalid PBLK length [7]

sept. 25 07:35:35 commandes-console kernel: acpi LNXCPU:00: Invalid PBLK length [7]

-- Reboot --

J'ai pensé qu'il fallait réindexer la base de données, mais la commande man tracker-store fonctionne, tandis que la commande tracker-store -r ne fonctionne pas. Je sèche, j'apprécirai votre aide. Merci.

Dernière modification par --gilles-- (26-09-2020 12:05:46)

Lunix64 · 25-09-2020 20:34:30

Je suis pas expert, alors je pose juste deux questions comme ça:

Les "acpi error" et "acpi bios error", ça peut pas être une corruption du BIOS ?

Et une nécessité de flasher le bios ou de faire un reset CMOS, ou un restore bios default ?

--gilles-- · 25-09-2020 20:49:13

Non, ces erreurs sont dues à ce que dans les anciens ordis le BIOS était programmé à la va-vite avec pleins d'erreurs et que ceux qui dirigeaient les programmeurs de ces BIOS savaient que les systèmes d'exploitation allaient corriger les effets de ces erreurs. Aujourd'hui, avec les ordis récents ce genre d'erreur de programmation est nettement moins toléré.

D'ailleurs, j'avais déjà ces erreurs acpi avant la panne qui n'est que limitée à un utilisateur, donc aucun rapport.

Debian Alain · 25-09-2020 21:18:46

bonsoir Lunix64

tu utilises gdm ? pour démarrer ta session graphique ?

https://wiki.debian.org/DisplayManager

tu as quoi comme display manager ?

tu as essayé de démarrer en X.org ?

--gilles-- · 26-09-2020 11:56:29

C'était l'occasion ou jamais de tester ses sauvegardes, justement j'en avais une du 16 septembre.

Un peu déçu quand même que les commandes du reset de l'index de la base de données tracker ne fonctionnent plus.

man tracker-reset

tracker-reset(1)                                            User Commands                                            tracker-reset(1)

NAME

       tracker-reset - Reset the index and configuration

SYNOPSIS

       tracker reset [--hard | --soft] [--config] [--file FILE]

DESCRIPTION

       The  reset  command will change either your configuration or index irreversibly and should be used with care. Other than tags,

       actual data (e.g. files) should not be affected by this command.

       The "index" is a link between your content (either locally or remotely) and how it can be found quickly using a number of dif‐

       ferent queries. Under the hood, this is done using a database.

       Removing all data and starting again from the beginning with an empty data set (which is a common use of this command) is done

       by using the hard reset option. This behaves as if Tracker was just installed.

OPTIONS

       -r, --hard

              This kills all processes in the same way that tracker daemon --kill does but it also removes all databases.  Restarting

              tracker-store re-creates the databases.

       -e, --soft

              A  soft  reset  works exactly the same way that --hard does, with the exception that the backup and journal are not re‐

              moved. These are restored when tracker-store is restarted. This command is useful if you have a  corrupt  database  but

              want to reply the journal to restore it to the last known good place.

       -c, --config

              Resets all configuration to its defaults.

       -f, --file FILE

              Resets  all indexed information about FILE, works recursively for directories. Nothing will be done if FILE is not cur‐

              rently indexed.  After deletion, a request to reindex this data will be immediately issued.

SEE ALSO

       tracker-daemon(1).  tracker(1).

GNU                                                         September 2014                                           tracker-reset(1)

~

fonctionne encore, mais la commande elle-même

tracker-reset --soft

ne fonctionne plus.

Si on cherche, effectivement, il n'y a plus que le man :

whereis tracker-reset

tracker-reset: /usr/share/man/man1/tracker-reset.1.gz

Il reste l'indexeur tracker-miner-fs

whereis tracker-miner-fs

tracker-miner-fs: /usr/libexec/tracker-miner-fs /usr/share/man/man1/tracker-miner-fs.1.gz

Mais comme il n'est pas censé effectuer un reset de l'index de la base, j'ai préféré plutôt utiliser la sauvegarde à base de grsync. Grsync que je dois reconfigurer à partir du nouvel utilisateur désormais.

Debian-facile

#1 25-09-2020 20:16:25

[Résolu] Session utilisateur corrompue, reset index tracker impossible

#2 25-09-2020 20:34:30

Re : [Résolu] Session utilisateur corrompue, reset index tracker impossible

#3 25-09-2020 20:49:13

Re : [Résolu] Session utilisateur corrompue, reset index tracker impossible

#4 25-09-2020 21:18:46

Re : [Résolu] Session utilisateur corrompue, reset index tracker impossible

#5 26-09-2020 11:56:29

Re : [Résolu] Session utilisateur corrompue, reset index tracker impossible

Pied de page des forums