Hello,
I am unsure where to ask/what to do.
My situation: I have a server machine running multiple virtual linux hosts. One of these contains a vncserver (call this host vnc). Another contains my calibre library (call thsi host nas). Unfortunately the server is located quite far from where I sit now and thus the connection with the database is quite slow (I wait 5-10 sec if I click on a book before calibre is responsible again). Thus I want to do the management of the ebook database via VNC (tightvnc at the moment). Due to some other considerations I have a virtual host with more computational power (call it work).
I now start calibre on the tightvncserver either from vnc locally or via ssh X11 forwarding from work. Both ways I get the same behaviour: The keymapping get's messed up. If I type "abcdef" I get "asdfgh" which is the home line of my keyboard! Any other program I tried (gnome-terminal, gedit,...) had the correct mapping.
If I start calibre on either vnc or work ssh via X11 forwarding to my desktop machine the keymap is correct but the program is much too slow to work with it (even slower than exporting the folder via NFS and running calibre locally).
From all the tests I did I guess that calibre tries to be smart about the keymaps but fails in the case of vnc.
The only output I get from calibre are:
Quote:
Qt: XKEYBOARD extension not present on the X server.
Could not initialize OpenGL for RasterGLSurface, reverting to RasterSurface.
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
Exception in thread Thread-5:
Traceback (most recent call last):
File "threading.py", line 810, in __bootstrap_inner
File "site-packages/calibre/gui2/device.py", line 401, in run
File "site-packages/calibre/gui2/device.py", line 263, in detect_device
File "site-packages/calibre/devices/scanner.py", line 325, in scan
File "site-packages/calibre/devices/scanner.py", line 179, in __call__
RuntimeError: DeviceScanner requires the /sys filesystem to work.
|
Maybe any of you guys has had a similar issue or knows the problem (plus ideally a workaround).
If not it would be nice to know how to reach the developers of the quit nice program to submit a bug report if needed.
Chris