Libreoffice 7.0 fatal error: Failed to updatefile
by burning from LinuxQuestions.org on (#5AFW0)
So I woke up this morning to find that in entering program names into dmenu, the tab completion options for potential program names no longer display and tab completion doesn't work in dmenu (but does work in the bash shell), i2p wrapper won't start and libreoffice is unable to start due to the following error:
Code:LibreOffice 7.0 - Fatal Error: The application cannot be started.
Failed to updatefile:///home/byron/.config/libreoffice/4/user/extensions/bundled/lastsynchronized /mnt/hd/build/tmp-libreoffice/libreoffice-7.0.3.1/desktop/source/deployment/manager/dp_extensionmanager.cxx:114The three things are all seemingly unrelated but I use the three of them every day and for some reason they all seem to be failing all at the same time of course there may be no link.
Attempting to access the lastsynchonized file outputs that there was a swap file found and that it couldn't be read though this only occurred the 2nd time I tried to access it. The first time it said something about an error and the file appeared empty but the error message disappeared before I could read it.
The only thing I can think that might've had any effect on this or my hard drive was that I used testdisk for the first time to try and (fail to) recover an accidentally deleted file. I was partways through making a copy image of one of my directories before removing the package for testdisk and giving up completely. If it's of any importance I'm using an SSD. Could using testdisk have caused this?
Code:LibreOffice 7.0 - Fatal Error: The application cannot be started.
Failed to updatefile:///home/byron/.config/libreoffice/4/user/extensions/bundled/lastsynchronized /mnt/hd/build/tmp-libreoffice/libreoffice-7.0.3.1/desktop/source/deployment/manager/dp_extensionmanager.cxx:114The three things are all seemingly unrelated but I use the three of them every day and for some reason they all seem to be failing all at the same time of course there may be no link.
Attempting to access the lastsynchonized file outputs that there was a swap file found and that it couldn't be read though this only occurred the 2nd time I tried to access it. The first time it said something about an error and the file appeared empty but the error message disappeared before I could read it.
The only thing I can think that might've had any effect on this or my hard drive was that I used testdisk for the first time to try and (fail to) recover an accidentally deleted file. I was partways through making a copy image of one of my directories before removing the package for testdisk and giving up completely. If it's of any importance I'm using an SSD. Could using testdisk have caused this?