Quote:
Originally Posted by BetterRed
Given most people don't have this problem then its probably something in the existing calibre data rather than the calibre V2.0 install; something that V2.0/Qt5 is 'misinterpreting'
Has anyone with this problem tried accessing their libraries with a vanilla configuration folder - eg via fresh windows portable install.
If the problem doesn't manifest then its presumably something awry in the config data, if the problem is manifest then its presumably something awry in the database(s) - probably in the preferences table(s).
If the former then I would try renaming gui.json and gui.py to gui.*.save and see what happens, if that 'fixes' it then I would... er - offer to send the gui.*.save files to Kovid.
If the latter I would... er - offer to send the database to Kovid.
BR
|
I did send my metadata.db file. The thing is, because it only happens on a database switch when it does happen, I would think there's nothing wrong with the actual databases.