I can only repeat how I solve this problem.

When I'm affected by the 0PL problem I start the shell, change to user root and start qspot from the /opt/qspot/bin directory.

Then you can see that the 0PL problem still exists but qspot does something on the shell you can't see in the GUI. Only, and really only, when the shell becomes silent and qspot does not do anything anymore I close via the shell with ctrl-c.

I do that as often as needed. After several times the local storage and XMLs are fixed and qspot starts ok with all playlists.

The important thing is to not close qspot before the shell becomes silent and qspot finished all it's tasks.

Bye,

Martin