SageTV stops responding when using Remote Desktop Connection

[Durwood]

SageTV stops responding when using Remote Desktop Connection
Sometimes when I connect to my windows machine remotely (from my laptop) if SageTV is currently running (e.g. playing a music playlist), it stops responding as soon as I connect via Remote Desktop Connection. The icon in the taskbar no longer shows the Sage Logo but just shows the default Java application logo. If the Sage GUI is on the page where it shows music visualizations, those continue, but Sage doesn't respond in any way to any input and no longer plays the sound. The only thing I can do is terminate the process. (This is one of the reasons I had so much annoyance with needing to resuming a playlist in the middle, as my earlier post today mentioned.)

[natesneat2000]

I use VNC with Sage just fine, maybe try that.

[mlbdude]

Have you tried running Sage with 3D Acceleration off? With it on it works much like a video game. Don't think Remote Deskotp supports running games.

[Durwood]

Yeah I have 3d acceleration off. Always have.

And RDC is vastly superior to VNC in terms of usability, for many many reasons. One often has to jiggle the mouse over the Sage UI to get repaints with VNC: VNC has always had issues with repainting java-based UIs.

If it happens again I'll see if I can find out if there are any logs that might shed light on this particular bug.

[stanger89]

Ultr@VNC has always worked flawlessly for me with Sage.

[Durwood]

Well, again, that's nice, but RDC is sooooo much nicer. It automatically resizes the desktop (you have to do a lot of trial-and-error resizing with VNC to get it right); when you maximize the screen you can use ALT+TAB to move around (with VNC you have to fish around for hidden windows with your mouse), and if you use Fast User Switching on your remote machine, then VNC often doesn't work at all (just shows a black screen).

I was hoping that upgrading to SP2 would help -- there were a number of bugs with RDC especially when coupled with Fast User Switching: most notoriously, the problem with "leaving sound at remote computer", where the remote Windows machine would think it had no sound card. This made it rather difficult to use Sage to play imported music remotely, for instance. When I upgraded to SP2, those problems went away (as advertised), and I was hoping the Sage-freezing problem would go away with it. Unfortunately, the freezing problem has persisted.

[stanger89]

You might want to submit a support request/bug report, Sage really doesn't like having the resolution changed on it, especially when it's actually running (vs sleep mode). I've seen it to, but I always run 3D Accelleration enabled and I know DX doesn't like things changing on it like that.

[Durwood]

You know I bet that's precisely the problem! The PC Sage is on runs at 1600x1280, but my laptop is 1400 x 1050. And it DOES only seem to happen if I have logged on to the PC directly and then use Remote Desktop Connection later.