Calibre won't start: Linux

[JeffElkins]

Running from the command line I get: Couldn't resolve property: linearGradient5167 - AFAIK I'm running the most current version, my linux is Kubuntu 8.04.

[kovidgoyal]

How did you install calibre?

[JeffElkins]

Originally Posted by kovidgoyal

How did you install calibre?

Via the directions on your web site:

sudo apt-get install  python-setuptools python-imaging  libqt4-core libqt4-gui \
python-qt4 python-mechanize imagemagick \
xdg-utils python-dbus python-lxml help2man
sudo easy_install -U calibre 
sudo calibre_postinstall

[kovidgoyal]

there are actually several sets of directions

Well the linearGradient maessage is just a warning about a malformed SVG file and can be ignored. When you launch calibre is there any CPU/disk activity ?

Can you run calibre-debug and other command line tools?

[JeffElkins]

Originally Posted by kovidgoyal

there are actually several sets of directions

Well the linearGradient maessage is just a warning about a malformed SVG file and can be ignored. When you launch calibre is there any CPU/disk activity ?

Can you run calibre-debug and other command line tools?

Traceback (most recent call last):
File "/usr/bin/calibre-debug", line 8, in <module>
load_entry_point('calibre==0.4.83', 'console_scripts', 'calibre-debug')()
File "build/bdist.linux-i686/egg/calibre/debug.py", line 58, in main
ImportError: No module named IPython.Shell

The console tools seem to run fine and calibre itself was running fine as of yesterday. I did have a power failure that rebooted my network, but nothing else was effected.

btw: .calibre_calibre GUI.lock is created.

[kovidgoyal]

install ipython as well

[JeffElkins]

Originally Posted by kovidgoyal

install ipython as well

I did so. running calibre-debug now drops me to a debug console.

In [1]:

[kovidgoyal]

What does

calibre-debug -c "from calibre.gui2.main import main; main()"

do?

[JeffElkins]

Originally Posted by kovidgoyal

What does

calibre-debug -c "from calibre.gui2.main import main; main()"

do?

Nothing. I see the
"Couldn't resolve property: linearGradient5167" message, but calibre never starts. I gave it about 5 minutes. Top doesn't reveal anything especially interesting. Just for chuckles I did a calibre reinstall w/o effect.

[kovidgoyal]

Hmm weird. Uninstall calibre and try the binary install.

[JeffElkins]

Originally Posted by kovidgoyal

Hmm weird. Uninstall calibre and try the binary install.

Well, I'm not thrilled with that answer (installation via the command line is so durn convenient) but I'll do it. what's the uninstall procedure for a easy_install installation?

[JeffElkins]

Never mind, it's sorted out. After about 15 minutes, calibre returned the message "sqlite3.OperationalError: database is locked" My database in ~/library1.db is a symlink to the 'real' db on an nfs volume. Apparently my power failure left a lock file existing somewhere that I need to find and nuke. I copied the actual library1.db file to my home directory and calibre started fine.

[kovidgoyal]

Originally Posted by JeffElkins

Well, I'm not thrilled with that answer (installation via the command line is so durn convenient) but I'll do it. what's the uninstall procedure for a easy_install installation?

The other installation method is also via the commandline

[JeffElkins]

Originally Posted by kovidgoyal

The other installation method is also via the commandline

Well, yes

sudo python -c "import urllib2; exec urllib2.urlopen('http://calibre.kovidgoyal.net/download_linux_binary_installer').read(); main()"

is command line , but

sudo easy_install -U calibre 
sudo calibre_postinstall

after checking for new dependencies is very convenient. I keep it in a /usr/local/bin/ script for easy upgrades. Anyway, this sqlite locked database is a real bore. Apparently, sqlite uses fcntl() to lock databases and nfs has problems with this. The database remains locked no matter what I do. I have been able to copy it so another location and access it, so my data is safe, but when calibre attempts to access it from it's original location on the nfs drive it's no go.

[kovidgoyal]

yeah nfs and sqlite dont go well together. You can change the location calibre looks for the database file by editing calibre2.ini