# Erreur: ... database disk image is malformed

**URL:** <https://www.debian-fr.org/t/erreur-database-disk-image-is-malformed/92121>\
**Category:** Support Debian\
**Created:** [Mars 10, 2026, 8:47 UTC](https://www.debian-fr.org/t/erreur-database-disk-image-is-malformed/92121 "2026-03-10T08:47:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![josephtux](https://www.debian-fr.org/user_avatar/www.debian-fr.org/josephtux/32/3985_2.png) [@josephtux](https://www.debian-fr.org/u/josephtux)\
**Post date:** [Mars 10, 2026, 8:47 UTC](https://www.debian-fr.org/t/erreur-database-disk-image-is-malformed/92121/1 "2026-03-10T08:47:28Z")

</div>

Bonjour,

En cherchant dans /var/log ce qui pourrait bien expliquer mes problèmes d’impression, je trouve cette série (juste après reboot, puis tentative d’impression)

```
2026-03-10T09:36:46.308109+01:00 Leopard systemd[4850]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 4.
    2026-03-10T09:36:46.308643+01:00 Leopard systemd[4850]: Stopped tracker-miner-fs-3.service - Tracker file system data miner.
    2026-03-10T09:36:46.330425+01:00 Leopard systemd[4850]: Starting tracker-miner-fs-3.service - Tracker file system data miner...
    2026-03-10T09:36:46.346800+01:00 Leopard tracker-miner-f[66663]: Error opening readwrite database: database disk image is malformed
    2026-03-10T09:36:46.346927+01:00 Leopard tracker-miner-f[66663]: tracker_db_interface_create_statement: assertion 'TRACKER_IS_DB_INTERFACE (db_interface)' failed
    2026-03-10T09:36:46.347001+01:00 Leopard tracker-miner-f[66663]: Could not delete '.meta.isrunning': Aucun fichier ou dossier de ce type
    2026-03-10T09:36:46.347110+01:00 Leopard tracker-miner-f[66663]: Could not create store/endpoint: Database version is too old: got version 0, but 27 is needed
    2026-03-10T09:36:46.348724+01:00 Leopard systemd[4850]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
    2026-03-10T09:36:46.348823+01:00 Leopard systemd[4850]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
    2026-03-10T09:36:46.348992+01:00 Leopard systemd[4850]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
    2026-03-10T09:36:46.557197+01:00 Leopard systemd[4850]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 5.
    2026-03-10T09:36:46.559884+01:00 Leopard systemd[4850]: Stopped tracker-miner-fs-3.service - Tracker file system data miner.
    2026-03-10T09:36:46.560038+01:00 Leopard systemd[4850]: tracker-miner-fs-3.service: Start request repeated too quickly.
    2026-03-10T09:36:46.560123+01:00 Leopard systemd[4850]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
    2026-03-10T09:36:46.560194+01:00 Leopard systemd[4850]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.

```

Il s’agit de Bookworm, ainsi partitionné:

```
$lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 1,8T 0 disk 
└─sda1 8:1 0 1,8T 0 part /run/timeshift/1468/backup
                                         /media/eric/Tosh2Tbleu1ext4
sdb 8:16 1 0B 0 disk 
nvme0n1 259:0 0 3,6T 0 disk 
├─nvme0n1p1 259:1 0 333M 0 part /boot/efi
├─nvme0n1p2 259:2 0 59,6G 0 part 
└─nvme0n1p3 259:3 0 3,6T 0 part 
  ├─VG0-Racine 254:0 0 119,8G 0 lvm /
  ├─VG0-Local 254:1 0 46,6G 0 lvm /usr/local
  ├─VG0-Eric 254:2 0 159,8G 0 lvm /home/eric
  ├─VG0-Work 254:3 0 2,1T 0 lvm /home/work
  ├─VG0-swap 254:4 0 125G 0 lvm [SWAP]
  ├─VG0-boot 254:5 0 572M 0 lvm  
  └─VG0-VAR 254:6 0 45,6G 0 lvm /var
nvme1n1 259:4 0 3,6T 0 disk 
└─nvme1n1p2 259:5 0 1G 0 part 

```

La seule ligne rouge de dmesg est (la 2e):

```
[mar. 10 mars 09:28:23 2026] IPv6: ADDRCONF(NETDEV_CHANGE): enp46s0: link becomes ready
[mar. 10 mars 09:28:23 2026] ucsi_acpi USBC000:00: PPM init failed (-110)
[mar. 10 mars 09:28:25 2026] usblp0: removed
```

---

<div class="post-metadata">

**Author:** ![Zargos](https://www.debian-fr.org/user_avatar/www.debian-fr.org/zargos/32/10889_2.png) [@Zargos](https://www.debian-fr.org/u/Zargos)\
**Post date:** [Mars 10, 2026, 9:29 UTC](https://www.debian-fr.org/t/erreur-database-disk-image-is-malformed/92121/2 "2026-03-10T09:29:26Z")

</div>

Comment s’appelle ta file d’impression?  
pour usblp0, c’est normal, il faut que tu utilises cups et non le pilote lui-même. Donc c’est normal que ce soit ‹&nbsp;removed&nbsp;›.  
Pour tracker, ça n’a rien à voir avec l’impression.

---

<div class="post-metadata">

**Author:** ![josephtux](https://www.debian-fr.org/user_avatar/www.debian-fr.org/josephtux/32/3985_2.png) [@josephtux](https://www.debian-fr.org/u/josephtux)\
**Post date:** [Mars 10, 2026, 5:18 UTC](https://www.debian-fr.org/t/erreur-database-disk-image-is-malformed/92121/3 "2026-03-10T17:18:39Z")

</div>

> [@Zargos](#):
>
> Comment s’appelle ta file d’impression?

Comment le savoir? qu’est-ce que «la file d’impression»?

`lpstat` affiche bizarrement en effet Aculaser-CX17-257 alors qu’ici l’imprimante est Samsung-ML-1660-Series.

Mais l’icone de Mate pour la configuration de l’impression a bien pris en compte mon choix de ML-1660-Series

Ce sont les noms que je leur avais donné initialement.