Re: LyX GUI unresponsive over ssh

2016-09-01 Thread Pavel Sanda
Boylan, Ross wrote: > It seems the GUI is just incredibly slow, taking maybe 30 to 60 seconds to > respond to an event. That includes even trivial operations like clicking > somewhere and having the cursor appear. In the interim I see continuous > network activity at about 265KiB/s. I am usin

Re: LyX GUI unresponsive over ssh

2016-08-27 Thread Jean-Marc Lasgouttes
Le 26/08/2016 à 22:36, Boylan, Ross a écrit : I'm surprised; I thought the point of X was to avoid pushing bitmaps around. Yes, it used to be the case. Nowadays it is a bit different, I think. JMarc

Re: LyX GUI unresponsive over ssh

2016-08-26 Thread Scott Kostyshak
On Fri, Aug 26, 2016 at 03:11:48PM +0200, Jean-Marc Lasgouttes wrote: > Le 26/08/2016 à 00:30, Boylan, Ross a écrit : > > It seems the GUI is just incredibly slow, taking maybe 30 to 60 > > seconds to respond to an event. That includes even trivial > > operations like clicking somewhere and having

Re: LyX GUI unresponsive over ssh

2016-08-26 Thread Jean-Marc Lasgouttes
Le 26/08/2016 à 00:30, Boylan, Ross a écrit : It seems the GUI is just incredibly slow, taking maybe 30 to 60 seconds to respond to an event. That includes even trivial operations like clicking somewhere and having the cursor appear. In the interim I see continuous network activity at about 265

Re: LyX GUI unresponsive over ssh

2016-08-25 Thread Steve Litt
On Thu, 25 Aug 2016 22:30:44 + "Boylan, Ross" wrote: > It seems the GUI is just incredibly slow, taking maybe 30 to 60 > seconds to respond to an event. That includes even trivial > operations like clicking somewhere and having the cursor appear. In > the interim I see continuous network ac

RE: LyX GUI unresponsive over ssh

2016-08-25 Thread Boylan, Ross
It seems the GUI is just incredibly slow, taking maybe 30 to 60 seconds to respond to an event. That includes even trivial operations like clicking somewhere and having the cursor appear. In the interim I see continuous network activity at about 265KiB/s. Perhaps this is some problem with fo