[Bug 343918] New: NX/FreeNX 0.7.1 does not recognize unix-kde session
https://bugzilla.novell.com/show_bug.cgi?id=343918 Summary: NX/FreeNX 0.7.1 does not recognize unix-kde session Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: openSUSE 10.2 Status: NEW Severity: Blocker Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mvdv@spamcop.net QAContact: sndirsch@novell.com Found By: Customer Hi, I have upgraded my local (client i686) and remote (server x86_64) versions of FreeNX and NX using the opensuse repositories: http://download.opensuse.org/repositories/NX/openSUSE_10.2/ client (i686) ------------- FreeNX-0.7.1-2.1 NX3-3.0.0-47.1 nxclient-3.0.0-68 NX-2.1.0-126.1 server (x86_64) --------------- NX-2.1.0-127.1 NX3-3.0.0-47.1 FreeNX-0.7.1-1.1 After this upgrade I find that the 'unix-kde' session is no longer recognized, and I experience the connection/resume problems: I now notice two unexpected behaviors: 1) When I try to open a new connect to a remote machine, instead of the connection I get the "Available sessions" dialog showing: X0 (local), vnc-local, 1920x1200, Running, ----- I have to select 'new' to get a connection. 2) With a new session now established, using fullscreen mode, I usually right click the NX client isonc, then selct "close" on the NX client icon to bring up the disconnect/terminate dialog box. Now, this action opens the NX new-connection dialog on the remote machine.... so it seems I've lost the ability to disconnect. I will attached some of the the client and server files. Any suggestions? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=343918#c1
--- Comment #1 from Mark Van De Vyver
https://bugzilla.novell.com/show_bug.cgi?id=343918#c2
--- Comment #2 from Mark Van De Vyver
https://bugzilla.novell.com/show_bug.cgi?id=343918#c3
Mark Van De Vyver
https://bugzilla.novell.com/show_bug.cgi?id=343918#c4
--- Comment #4 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=343918#c5
--- Comment #5 from Stefan Dirsch
Howvever the following two posts suggest it may be relevant that x86_64 versions of NX are not available? Sure, but there are none in the buildservice. Still not fixed in NX 3.0. See Bug #61220.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=343918#c6
--- Comment #6 from Mark Van De Vyver
I still seem the same behavior, unix-kde session becomes vnc-local session... Set ENABLE_DESKTOP_SHARING=0 in /etc/nxserver/node.conf. I'm going to make this default. It should be possible to use this feature by installing x11vnc
https://bugzilla.novell.com/show_bug.cgi?id=343918#c7
--- Comment #7 from Stefan Dirsch
Regarding Bug #61220 am I right the centOS dist has NX3 compiling/working? Is it possible to use their rpm? I have no idea.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=343918#c8
--- Comment #8 from Stefan Dirsch
2) With a new session now established, using fullscreen mode, I usually right click the NX client isonc, then selct "close" on the NX client icon to bring up the disconnect/terminate dialog box. Now, this action opens the NX new-connection dialog on the remote machine.... so it seems I've lost the ability to disconnect.
"right click the NX client isonc" ? What do you mean with that? I'm not aware of such a feature. I can suspend the session when running it in a window by clicking on the Close-Button of the window. Resuming works fine afterwards. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=343918#c9
--- Comment #9 from Mark Van De Vyver
From comment #7
Thanks I will try ENABLE_DESKTOP_SHARING=0.
From comment #8:
Apologies. That was obtuse of me - you'd need to have dug in the options file to see that I was running the client in full screen mode. With the client NX connection in full-screen mode, the sequence then is (actually it was with FreeNX 0.6 - prior to the upgrade to FreeNX 0.7.1): 1) click on the magic pixel (top right pixel). 2) In the taskbar/panel the NoMachine icon should be visible - right-click on this icon, and then select 'close' 3) The NX client should return to full screen display _and_ display the NX client's terminate/disconnect dialog. Of course the problem I have is that instead of the terminate/disconnect dialog I now actually find the remote machine's instance of the NX connection dialog is started... the remote machine is also used to connect to some other machines on a private network. HTH? Mark -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=343918
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=343918#c10
--- Comment #10 from Stefan Dirsch
1) click on the magic pixel (top right pixel). Never heard of this. Tried this and it resulted in immediately suspending the session (no matter if i right- or left-click). Next time I connect the session is automatically resumed.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=343918#c11
--- Comment #11 from Mark Van De Vyver
https://bugzilla.novell.com/show_bug.cgi?id=343918#c12
--- Comment #12 from Stefan Dirsch
Never heard of this. Tried this and it resulted in immediately suspending the session (no matter if i right- or left-click). And terminates nxclient as well! This must be some nxclient feature/bug I cannot investigate!
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=343918#c13
--- Comment #13 from Stefan Dirsch
Is the NXSERVER Version 1.5.0 the expected number:
rpm -e NX FreeNX rpm -Uvh FreeNX-0.7.1-1.1.x86_64.rpm NX-2.1.0-127.1.i586.rpm
Then when connecting I see in /var/log/nxserver.log:
-- NX SERVER START: - ORIG_COMMAND= HELLO NXSERVER - Version 1.5.0-70 OS (GPL) NX> 105 hello NXCLIENT - Version 1.5.0 NX> 134 Accepted protocol: 1.5.0
At least it's the version which worked for me. ------------------------------------------------------------------- Sun Nov 11 12:14:17 CET 2007 - sndirsch@suse.de - updated to release 0.7.1 * see ANNOUNCE-0.7.1 for more details - nxloadconfig: set NX_VERSION back to 1.5.0-70, since otherwise no connection was possible (upstream changed to 2.1.0-71) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=343918#c14
Stefan Dirsch
participants (1)
-
bugzilla_noreply@novell.com