MobileRead Forums - View Single Post - Calibre on Slackware from Windows using Xming

elMoco · 08-13-2017, 05:48 AM

Hi all,

I've been using a Windows laptop as a terminal form my Linux server for several years. I have installed Xming and everithing seems to work fine.

But lately Calibre doesn´t work.

It used to work fine untile few weeks ago, but now I am geting this message all the time:

Code:

jesusm@liet:~/log$ (export DISPLAY=192.168.1.39:0.0 & calibre)
failed to get the current screen resources
QXcbConnection: XCB error: 170 (Unknown), sequence: 170, resource id: 90, major code: 146 (Unknown), minor code: 20
The X11 connection broke: I/O error (code 1)
XIO:  fatal IO error 2 (No existe el fichero o el directorio) on X server "192.168.1.39:0"
      after 349 requests (349 known processed) with 0 events remaining.
jesusm@liet:~/log$

Yes, I know it seems that the problem is with the X server, but any other application works fine. using exactly the same command to run. SO I think that maybe it is a problem with some new Calibre update.

Any idea?

Thanks
JM

08-13-2017, 05:48 AM	#1
elMoco Member Posts: 14 Karma: 10 Join Date: May 2012 Device: Kindle Paperwhite	Calibre on Slackware from Windows using Xming Hi all, I've been using a Windows laptop as a terminal form my Linux server for several years. I have installed Xming and everithing seems to work fine. But lately Calibre doesn´t work. It used to work fine untile few weeks ago, but now I am geting this message all the time: Code: jesusm@liet:~/log$ (export DISPLAY=192.168.1.39:0.0 & calibre) failed to get the current screen resources QXcbConnection: XCB error: 170 (Unknown), sequence: 170, resource id: 90, major code: 146 (Unknown), minor code: 20 The X11 connection broke: I/O error (code 1) XIO: fatal IO error 2 (No existe el fichero o el directorio) on X server "192.168.1.39:0" after 349 requests (349 known processed) with 0 events remaining. jesusm@liet:~/log$ Yes, I know it seems that the problem is with the X server, but any other application works fine. using exactly the same command to run. SO I think that maybe it is a problem with some new Calibre update. Any idea? Thanks JM