When running "yum update" on monday, oct 22, I get the following conflicts:
Transaction Check Error: file /etc/nxserver/node.conf.sample from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxkeygen from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxloadconfig from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxnode from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxprint from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxserver from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos file /usr/bin/nxsetup from install of freenx-0.7.1-1.el5.centos conflicts with file from package freenx-0.6.0-12.el5.centos
Known?
Regards
Joachim Backes wrote: ...
Known?
...
Is you system x86_64, then:
http://lists.centos.org/pipermail/centos/2007-October/088311.html
else try if using another mirror helps.
Mogens
Mogens Kjaer wrote:
Joachim Backes wrote: ...
Known?
...
Is you system x86_64, then:
http://lists.centos.org/pipermail/centos/2007-October/088311.html
else try if using another mirror helps.
Mogens
Mogens,
thank you for your reply, but I did this already before sending an email to the centos mailing list. Now when starting the nxclient on my workstation, I get a message presenting some dead "available sessions" which cannot be resumed. Only clicking "New" in this prompt will continue with opening a session.
This happens on each nxclient start.
Regards
Joachim Backes wrote:
Mogens Kjaer wrote:
Joachim Backes wrote: ...
Known?
...
Is you system x86_64, then:
http://lists.centos.org/pipermail/centos/2007-October/088311.html
else try if using another mirror helps.
thank you for your reply, but I did this already before sending an email to the centos mailing list. Now when starting the nxclient on my workstation, I get a message presenting some dead "available sessions" which cannot be resumed.
This happens on each nxclient start.
The dead sessions, except the one that says X0 (local), are probably just leftovers in this directory:
/var/lib/nxserver/db/running/
You can make sure all your current NX sessions are exited on the server, then go to that directory (/var/lib/nxserver/db/running/) and if there are files in there, remove them (or back them up to another directory if you want to be extremely cautious :D ). Also look in /var/lib/nxserver/db/failed. The older versions of freenx tended to leave connections there after they were dead, but not show them to the client.
The X0 (local) session shows up all the time, but can only be connected to IF you are sharing your desktop via VNC. Most of the time, this will not be the case, so just ignore it.
Only clicking "New" in this prompt will continue with opening a session.
Do these new sessions behave properly for you (can you disconnect and reconnect to them properly from the same client)?
Thanks, Johnny Hughes
Johnny Hughes wrote:
Joachim Backes wrote:
Mogens Kjaer wrote:
Joachim Backes wrote: ...
Known?
...
Is you system x86_64, then:
http://lists.centos.org/pipermail/centos/2007-October/088311.html
else try if using another mirror helps.
thank you for your reply, but I did this already before sending an email to the centos mailing list. Now when starting the nxclient on my workstation, I get a message presenting some dead "available sessions" which cannot be resumed.
This happens on each nxclient start.
The dead sessions, except the one that says X0 (local), are probably just leftovers in this directory:
/var/lib/nxserver/db/running/
This dir is empty! And no session is/was running.
You can make sure all your current NX sessions are exited on the server, then go to that directory (/var/lib/nxserver/db/running/) and if there are files in there, remove them (or back them up to another directory if you want to be extremely cautious :D ). Also look in /var/lib/nxserver/db/failed.
Is empty too.
The older versions of freenx tended to
leave connections there after they were dead, but not show them to the client.
The X0 (local) session shows up all the time, but can only be connected to IF you are sharing your desktop via VNC. Most of the time, this will not be the case, so just ignore it.
Only clicking "New" in this prompt will continue with opening a session.
Do these new sessions behave properly for you (can you disconnect and reconnect to them properly from the same client)?
These new sessions behave properly.
Additionally, I had no problems with the previous NX version.
Regards
Joachim Backes
Thanks, Johnny Hughes
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Joachim Backes wrote:
Johnny Hughes wrote:
Joachim Backes wrote:
Mogens Kjaer wrote:
Joachim Backes wrote: ...
Known?
...
Is you system x86_64, then:
http://lists.centos.org/pipermail/centos/2007-October/088311.html
else try if using another mirror helps.
thank you for your reply, but I did this already before sending an email to the centos mailing list. Now when starting the nxclient on my workstation, I get a message presenting some dead "available sessions" which cannot be resumed.
This happens on each nxclient start.
The dead sessions, except the one that says X0 (local), are probably just leftovers in this directory:
/var/lib/nxserver/db/running/
This dir is empty! And no session is/was running.
You can make sure all your current NX sessions are exited on the server, then go to that directory (/var/lib/nxserver/db/running/) and if there are files in there, remove them (or back them up to another directory if you want to be extremely cautious :D ). Also look in /var/lib/nxserver/db/failed.
Is empty too.
Maybe you have these in the NoMachine client's location instead:
/usr/NX/var/db/
failed and running directories ... the entries you want to delete will look something like this:
sessionId{03288000FC8EE2D8DBE68D29F8D417CA}
<snip>
Thanks, Johnny Hughes
Johnny Hughes wrote:
Joachim Backes wrote:
Johnny Hughes wrote:
Joachim Backes wrote:
Mogens Kjaer wrote:
Joachim Backes wrote: ...
Known?
...
Is you system x86_64, then:
http://lists.centos.org/pipermail/centos/2007-October/088311.html
else try if using another mirror helps.
thank you for your reply, but I did this already before sending an email to the centos mailing list. Now when starting the nxclient on my workstation, I get a message presenting some dead "available sessions" which cannot be resumed.
This happens on each nxclient start.
The dead sessions, except the one that says X0 (local), are probably just leftovers in this directory:
/var/lib/nxserver/db/running/
This dir is empty! And no session is/was running.
You can make sure all your current NX sessions are exited on the server, then go to that directory (/var/lib/nxserver/db/running/) and if there are files in there, remove them (or back them up to another directory if you want to be extremely cautious :D ). Also look in /var/lib/nxserver/db/failed.
Is empty too.
Maybe you have these in the NoMachine client's location instead:
/usr/NX/var/db/
failed and running directories ... the entries you want to delete will look something like this:
sessionId{03288000FC8EE2D8DBE68D29F8D417CA}
I found such entries, but deleting them was not helpful.
Still getting the prompt I have attached.
Regards
Joachim Backes
<snip>
Thanks, Johnny Hughes
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Joachim Backes wrote:
Johnny Hughes wrote:
Joachim Backes wrote:
Johnny Hughes wrote:
Joachim Backes wrote:
Mogens Kjaer wrote:
Joachim Backes wrote: ... > Known? ...
Is you system x86_64, then:
http://lists.centos.org/pipermail/centos/2007-October/088311.html
else try if using another mirror helps.
thank you for your reply, but I did this already before sending an email to the centos mailing list. Now when starting the nxclient on my workstation, I get a message presenting some dead "available sessions" which cannot be resumed.
This happens on each nxclient start.
The dead sessions, except the one that says X0 (local), are probably just leftovers in this directory:
/var/lib/nxserver/db/running/
This dir is empty! And no session is/was running.
You can make sure all your current NX sessions are exited on the server, then go to that directory (/var/lib/nxserver/db/running/) and if there are files in there, remove them (or back them up to another directory if you want to be extremely cautious :D ). Also look in /var/lib/nxserver/db/failed.
Is empty too.
Maybe you have these in the NoMachine client's location instead:
/usr/NX/var/db/
failed and running directories ... the entries you want to delete will look something like this:
sessionId{03288000FC8EE2D8DBE68D29F8D417CA}
I found such entries, but deleting them was not helpful.
Still getting the prompt I have attached.
Right ... that one connection is the "X0 (local)" connection, that is your "normal local desktop" shared.
You will normally not be able to connect to that, and it can be ignored. (Unless you are logged in and have set vino to share your :0 desktop)
Johnny Hughes wrote:
Joachim Backes wrote:
Johnny Hughes wrote:
Joachim Backes wrote:
Johnny Hughes wrote:
Joachim Backes wrote:
Mogens Kjaer wrote: > Joachim Backes wrote: > ... >> Known? > ... > > Is you system x86_64, then: > > http://lists.centos.org/pipermail/centos/2007-October/088311.html > > else try if using another mirror helps. thank you for your reply, but I did this already before sending an email to the centos mailing list. Now when starting the nxclient on my workstation, I get a message presenting some dead "available sessions" which cannot be resumed.
This happens on each nxclient start.
The dead sessions, except the one that says X0 (local), are probably just leftovers in this directory:
/var/lib/nxserver/db/running/
This dir is empty! And no session is/was running.
You can make sure all your current NX sessions are exited on the server, then go to that directory (/var/lib/nxserver/db/running/) and if there are files in there, remove them (or back them up to another directory if you want to be extremely cautious :D ). Also look in /var/lib/nxserver/db/failed.
Is empty too.
Maybe you have these in the NoMachine client's location instead:
/usr/NX/var/db/
failed and running directories ... the entries you want to delete will look something like this:
sessionId{03288000FC8EE2D8DBE68D29F8D417CA}
I found such entries, but deleting them was not helpful.
Still getting the prompt I have attached.
Right ... that one connection is the "X0 (local)" connection, that is your "normal local desktop" shared.
You will normally not be able to connect to that, and it can be ignored. (Unless you are logged in and have set vino to share your :0 desktop)
Hi Johnny,
thank you for the explanation. Clicking in this additional prompt (which now appears each time) on the "New" button seems be the only solution.
Regards
Joachim Backes
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Johnny Hughes wrote:
Right ... that one connection is the "X0 (local)" connection, that is your "normal local desktop" shared.
You will normally not be able to connect to that, and it can be ignored. (Unless you are logged in and have set vino to share your :0 desktop)
I thought the current version from NX was able to share the console session too. Does anyone know if that is planned for freenx?
Les Mikesell wrote:
Johnny Hughes wrote:
Right ... that one connection is the "X0 (local)" connection, that is your "normal local desktop" shared.
You will normally not be able to connect to that, and it can be ignored. (Unless you are logged in and have set vino to share your :0 desktop)
I thought the current version from NX was able to share the console session too. Does anyone know if that is planned for freenx?
NX-3 can ... freenx-0.7.x can't.
The next "Major" version of freenx (ie, 0.8.0 not 0.7.2 ... may be named something other than freenx, possibly X++) is supposed to incorporate all nx-3 features.
Good reading on this list:
http://mail.kde.org/pipermail/freenx-knx/
Thanks, Johnny Hughes
Jan Falkenhagen wrote:
Right ... that one connection is the "X0 (local)" connection, that is your "normal local desktop" shared.
is there any way to get rid of this session? it keeps confusing my colleagues, so it would be very nice if it could be convinced to disappear.
You can turn it off by copying the file /etc/nxserver/node.conf.sample to /etc/nxserver/node.conf editing the following features:
#ENABLE_MIRROR_VIA_VNC=1
#ENABLE_DESKTOP_SHARING=1
and set to:
ENABLE_MIRROR_VIA_VNC=0
ENABLE_DESKTOP_SHARING=0
That should make it disappear.
Thanks, Johnny Hughes
-
Jan Falkenhagen -
Joachim Backes -
Johnny Hughes -
Les Mikesell -
Mogens Kjaer