Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 198459 - net-misc/nxserver-freenx-0.7.1 won't allow nxclient-3.0 to connect anymore
Summary: net-misc/nxserver-freenx-0.7.1 won't allow nxclient-3.0 to connect anymore
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo NX Server project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-08 15:07 UTC by Olliver Schinagl
Modified: 2007-12-03 22:54 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olliver Schinagl 2007-11-08 15:07:40 UTC
After upgradeing from nxserver-freenx-0.7.0-r1 to 0.7.1 my client (net-misc/nxclient-3.0.0-r4) refuses to connect to the server (sig 15 i read in the detailed logs)

rolling back to nxserver-freenx-0.7.0-r1 makes it all work normally.

I haven't tried killing my session, upgrading and starting a new one, but creating a new one (whilst keeping the old one) also doesn't seem to work.

Reproducible: Always

Steps to Reproduce:
Comment 1 Bernard Cafarelli gentoo-dev 2007-11-10 00:22:22 UTC
Strange, that combination (3.0.0-r4 client, 0.7.1 server) is what I mostly tested on, and it works fine for me...

Do you have nxclient installed on the server? Which type of session do you run (gnome, kde, floating window, ...), is "Disable encryption of all traffic" enabled/disabled?

Comment 2 Bruno Redondi 2007-11-28 09:44:19 UTC
maybe it's related to bug #198927.

Do You have ENABLE_2_0_0_BACKEND=1 in your node.conf?
Comment 3 Bernard Cafarelli gentoo-dev 2007-12-03 20:04:36 UTC
If this is the problem, it should be fixed with nxserver-0.7.1-r1?

Please reopen if the problem is still there after updating to this version
Comment 4 Olliver Schinagl 2007-12-03 22:54:44 UTC
It wasn't, i had both 3.0 and 2.0 enabled, no go.

I'll try -r1 when i see it coming bye and re-open if needed.