Ehh well fuck me.
Fixed the bloody issue after an hour. For the record, insync, the bug wasn't your fault and all previous instances of it were out of date by now.
Aallll right! So everybody who comes here with this bug better listen up and if a friendly mod could pin this on this thread or something, that would be splendid.
What goes wrong?
The issue is not with insync as said above, but with
nemo-python by the looks of it.
nemo-python is pretty much the extension meant to load other extensions and since a few years now, it seems to have broken compatibility with a bunch of systems for some reason.
How to fix it?
First of all, you need to run
nemo in your terminal. You want to see what specific error it is spitting out as you will need to correct it depending on the output.
You should get a bunch of errors but the most important one is this:
(nemo:13704): Nemo-Python-WARNING **: g_module_open libpython failed: /usr/lib/i386-linux-gnu//libpython2.7.so.1.0: cannot open shared object file: No such file or directory
ImportError: could not import gobject (error was: '/usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python2.7.so.0: undefined symbol: _Py_ZeroStruct')
Let me bring your attention to the path that fails /usr/lib/i386-linux-gnu/libpython2.7.so.1.0. Yours may differ.
Now you want to find where the actual
libpython is stored. I'm not sure how to find it, but chances are, it will be in
/usr/lib/ibpython2.7.so.1.0. Once again, it may differ. Check if it exists before anything.
So then you want to symlink them. Change the following command as needed.
ln -s /usr/lib/libpython2.7.so.1.0 /usr/lib/i386-linux-gnu/libpython2.7.so.1.0
OH no! It says that the directory doesn't exist!
Worry not! You just need to create it in that case.
mkdir /usr/lib/i386-linux-gnu and the re-run the command.