After upgrading from Debian 10 to Debian 11, I found Evolution crashing
whenever I tried to delete a few messages. Looking at coredumpctl, I noticed
tracker-miner-fs crashing every few minutes, as you mention. I let myself be
distracted by that for a bit, so I dug in with gdb, and found:
#4 0x00007f3955ceca82 in file_tree_lookup (tree=0x7f394400d320,
file=file@entry=0x5644bfbfe2c0,
parent_node=parent_node@entry=0x7fff51069238,
uri_remainder=uri_remainder@entry=0x7fff51069240)
at ../src/libtracker-miner/tracker-file-system.c:259
259 ../src/libtracker-miner/tracker-file-system.c: No such file or
directory.
(gdb) print ptr
$15 = (gchar *) 0x5644bfb3c74f "-expenses"
So I looked around my homedir for that string, and I found
~/Documents/ox-expenses/
Thinking it might be treating the ox- prefix as special (wouldn't know why), I
renamed the dir to oxexpenses. Then tracker-store crashed!
Jan 04 15:36:12 plato tracker-store[873997]: SQLite error: database disk image
is malformed (errno: Success)
Jan 04 15:36:12 plato tracker-store[873997]: SQLite experienced an error with
file:'/home/peter/.cache/tracker/meta.db'. It is either NOT a SQLite database
or it is corrupt or there was an IO error accessing the data. This file has now
been removed and will be recreated on the next start. Shutting down now.
Jan 04 15:36:13 plato systemd-coredump[874163]: Process 873997 (tracker-store)
of user 1000 dumped core.
Stack trace of thread 874001:
#0 0x00007f2214af9ca7
g_log_structured_array (libglib-2.0.so.0 + 0x58ca7)
#1 0x00007f2214afa0b5
g_log_default_handler (libglib-2.0.so.0 + 0x590b5)
#2 0x00007f2214afa309 g_logv
(libglib-2.0.so.0 + 0x59309)
#3 0x00007f2214afa59f g_log
(libglib-2.0.so.0 + 0x5959f)
#4 0x00007f2214c08e83 n/a
(libtracker-data.so + 0x38e83)
#5 0x00007f2214bfe03c n/a
(libtracker-data.so + 0x2e03c)
#6 0x00007f2214c016dc n/a
(libtracker-data.so + 0x316dc)
After that (30 minutes ago now), nothing has crashed - not tracker-miner-fs,
not tracker-store, and, to my surprise, not Evolution either.
I don't have an explanation for what happened here, but perhaps you can try
removing your meta.db (plus meta.db-* in the same dir) to see if it helps?
--
Peter van Dijk
pe...@7bits.nl
