Closed sweethuman closed 2 years ago
I'm not sure how, but the cache db for the copy of onedriver mounted via the systemd unit is corrupted somehow, it's trying to seek in an increment of 2147483647, the highest value a signed int32 can go.
Not sure how this happened, but this is an easy fix. The reason the onedriver ~/OneDrive
command works is it has a different DB. Either copy over the working onedriver.db to the account (cp ~/.cache/onedriver/onedriver.db ~/.cache/onedriver/home-sweethuman-OneDrive/onedriver.db`) or just delete the drive from the GUI and readd it. Both of these steps will purge the bad db and start fresh with the existing one that's good (1st option) or a new one (2nd option). Feel free to make a backup of the old db beforehand if you want.
I keep getting this error when I access the ondriver folder, regardless if I started the onerdriver using systemd or GUI. Onedriver info:
If i start it like this:
onedriver ~/OneDrive/
it works without crashing. It just says that the keys are expired, reauthenticating and i can see and read the folder contents without a problem.