Comment 7 for bug 1954954

    Hey, sorry for the second post on the same day, but I decided to look for the supposed "zeitgeist.conf" ( see previous post ), on my own, scanning the system, and found that it doesn't exist. My intention was to do a copy.bkp type backup, and when it breaks again, instead of doing Purge & Reinstall, I'd just try to reinstall the original settings to see if it finally works... And I'd send a copy of it NOW, for you be able to verify that it wasn't some failure of the Diodon NO MINT installation that corrupted the settings and created some critical failure. My hypothesis was that some such failure would be moving the supposed "zeitgeist.conf" to some strange folder or place. But to keep things simple, it wasn't like that, because there isn't a "zeitgeist.conf", as I've seen. I was even disappointed.

    But, on the other hand, my scan found several broken zeitgeist files, which I hope will give you useful hints. Here they are, with their respective paths:

/run/user/1000/systemd/units/invocation:zeitgeist.service
/run/user/1000/systemd/units/invocation:zeitgeist-fts.service
/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0

It caught my attention that two of the broken ones are systemd files. It feels like a much deeper flaw than I expected. I tried to copy these broken ones to a folder, before Blechbit disappears with them. But it seems that of two, only the path is left. Only libzeitgeist-2.0.so.0 was left.