Quote:
Originally Posted by kovidgoyal
yeah nfs and sqlite dont go well together. You can change the location calibre looks for the database file by editing calibre2.ini
|
Quote:
Couldn't resolve property: linearGradient5167
Traceback (most recent call last):
File "/usr/bin/calibre", line 8, in <module>
load_entry_point('calibre==0.4.83', 'gui_scripts', 'calibre')()
File "build/bdist.linux-i686/egg/calibre/gui2/main.py", line 1346, in main
File "build/bdist.linux-i686/egg/calibre/gui2/main.py", line 72, in __init__
File "build/bdist.linux-i686/egg/calibre/gui2/main.py", line 1254, in read_settings
File "/usr/lib/python2.5/posixpath.py", line 119, in dirname
return split(p)[0]
File "/usr/lib/python2.5/posixpath.py", line 77, in split
i = p.rfind('/') + 1
AttributeError: 'NoneType' object has no attribute 'rfind'
|
That doesn't work for me. If I hand edit the ini I get the message above. If I locate library1.db anywhere outside the root of my home directory I get other artifacts:
Snapshot1.png: library1.db is located in /home/jeff/Documents - the various db fields are misaligned. Resizing calibre does not affect this.
Snapshot2.png: library1.db lives in the root of my home directory, and all is well. Note that library1.db can be a symlink to another location and all is still well.