I sent this last week and never got a response. I take it, then, that no one has come up with a better workaround than ctrl-alt-f?
Thanks, Steve Bergman
========= In early June, there was an update from freenx 0.4.x to 0.5.x in centosplus. It broke full screen mode for Linux clients. I am aware of the ctrl-alt-f workaround. But I have quite a few users at branch offices who depend on NX and with employee turnover and all, it has been a source of confusion for us. Has anyone come up with a fix so that fullscreen works without crtl-alt-f? I've searched the freenx/knx list and have found no mention of anyone there having problems. Just the centosplus version. I prefer to continue using the CentOS-provided package, though. ==========
Steve Bergman wrote:
I sent this last week and never got a response. I take it, then, that no one has come up with a better workaround than ctrl-alt-f?
Thanks, Steve Bergman
That's pretty much what I guessed, too. I ran into this some time back and asked here on the list. From what I gather, it appears that it only affects the Linux NX client. One guy in my office using the Windows client doesn't have the problem. I did notice that it would come up in full-screen mode when resuming a session that had been in full-screen mode. For me the ctrl-alt-f sequence works find and does not cause any problems with the way I use NX.
Sorry!
Jay Leafey wrote:
From what I gather, it appears that it only affects the Linux NX client.
I can confirm this. I have customers with both Windows and Linux clients on the same server, and only the Linux clients exhibit the problem.
I was unaware that suspended full screen sessions behaved properly. (We don't use resume.)
I guess maybe those are at least helpful clues.
Thanks to you and maze for the responses.
-Steve
On Mon, 2006-07-17 at 10:21 -0500, Steve Bergman wrote:
Jay Leafey wrote:
From what I gather, it appears that it only affects the Linux NX client.
I can confirm this. I have customers with both Windows and Linux clients on the same server, and only the Linux clients exhibit the problem.
I was unaware that suspended full screen sessions behaved properly. (We don't use resume.)
I guess maybe those are at least helpful clues.
Thanks to you and maze for the responses.
-Steve
I am working hard on the sparc port for Niagara right now ...
I noticed that NoMachine has made available a free 2.0 version (limited to a couple connections) ... I need to see if freenx people are upgrading to that base (and removing the limits for connections) and see if that will give us better stuff ... if only there were 48 hours in a day :)
Johnny Hughes wrote:
if only there were 48 hours in aday :)
There's always the night ...
scnr,
Ralph
-
Jay Leafey -
Johnny Hughes -
Ralph Angenendt -
Steve Bergman