Nabble - freenx-knx

Re: Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-27T04:29:15Z

Marcelo Boveto Shima <marceloshima@...> wrote on 26/11/2009 02:02:20: > Hi, > > I can see two possible causes: > 1 - /var/lib/nxserver/db/running/ should be empty after the reboot. > $nxserver --cleanup should clean the directory

It should be emptied ( unless you use OpenSuse, who don't bother with
all the clean-up service nonsense )

. . . but if it isn't cleaned out, then anything for that user should be
listed to ask about a re-connection.

Also I think he tried all this last time.

> 2 - Ports needed by the four session are been used. Set the > DISPLAY_BASE=(last display value + 10) on /etc/nxserver/node.conf.

That's a good idea.

However, the logic tests for that in a loop . . . and automatically increments
SESS_DISPLAY

# Check if there is already an agent running on that display on that host
let AGENT_DISPLAY=$SESS_DISPLAY+6000
if $COMMAND_NETCAT -z "$SERVER_HOST" $AGENT_DISPLAY 2>/dev/null
then
log 2 "Warning: Stray nxagent without .nX$SESS_DISPLAY-lock found on host:port $SERVER_HOST:$AGENT_DISPLAY."
let SESS_DISPLAY=$SESS_DISPLAY+1
continue
fi

# Now check for the other enabled services

let SAMBA_DISPLAY=$SESS_DISPLAY+3000
if [ "$(getparam 'samba')" = 1 ] && $COMMAND_NETCAT -z "$SERVER_HOST" $SAMBA_DISPLAY
then
log 2 "Warning: Skipping $SERVER_HOST:$AGENT_DISPLAY as samba port is not free."
let SESS_DISPLAY=$SESS_DISPLAY+1
continue
fi

let MEDIA_DISPLAY=$SESS_DISPLAY+7000
if [ "$(getparam 'media')" = 1 ] && $COMMAND_NETCAT -z "$SERVER_HOST" $MEDIA_DISPLAY
then
log 2 "Warning: Skipping $SERVER_HOST:$AGENT_DISPLAY as media port is not free."
let SESS_DISPLAY=$SESS_DISPLAY+1
continue
fi

let CUPS_DISPLAY=$SESS_DISPLAY+9000
if [ "$(getparam 'cups')" = 1 ] && $COMMAND_NETCAT -z "$SERVER_HOST" $CUPS_DISPLAY
then
log 2 "Warning: Skipping $SERVER_HOST:$AGENT_DISPLAY as cups port is not free."
let SESS_DISPLAY=$SESS_DISPLAY+1
continue
fi

If it hasn't continued (round the loop again), then it breaks ( out of the loop ) here

> > Hope this helps. > Regards. > > Marcelo > > > > > [root@winwinwinwin yossarian]# cat > > /home/yossarian/.nx/F-C- > winwinwinwin-1000-2EEE03F57CDE5A5295F5B8E24F656371/session > > $DISPLAY is not set or cannot connect to the X server. > > > > xrdb: No such file or directory xrdb: Can't open display ':1000' $DISPLAY is > > not set or cannot connect to the X server.

This comes from nxnode, so we've got quite a way along . . .

> >>> > >>> > >>> NX> 148 Server capacity: not reached for user: yossarian > >>> NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1" > >>> --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" > >>> --composite="1" --media="0" --session="Gateway" --type="unix-kde" > >>> --geometry="1280x976" --client="linux" --keyboard="pc105/gb" > >>> --screeninfo="1280x976x24+render" > >>> > >>> NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0) > >>> NX> 700 Session id: gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE > >>> NX> 705 Session display: 1000 > >>> NX> 703 Session type: unix-kde > >>> NX> 701 Proxy cookie: 8b4424fcb9928f98bad143bae200b63b > >>> NX> 702 Proxy IP: 127.0.0.1 > >>> NX> 706 Agent cookie: 8b4424fcb9928f98bad143bae200b63b > >>> NX> 704 Session cache: unix-kde > >>> NX> 707 SSL tunneling: 1 > >>> NX> 105 /opt/NX/bin/nxserver: line 1531: 2161 Terminated sleep > >>> $AGENT_STARTUP_TIMEOUT > >> > >> no agent > >>

By line 1531 now it should have written . . . .

/opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}

> >> > >> > >>> NX> 596 Session startup failed. > >>> NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set > >>> SESSION_LOG_CLEAN=0 in node.conf and investigate > >>> > >> "/home/yossarian/.nx/F-C-gtfo-1000- > ED28A41DC35814F52C6DE05FDE72D8AE/session". > >> > >> Did you do this ?? What did it say ?? > >> > >>> You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent > >> to > >>> test the basic functionality. Session log follows: > >>> Can't open > >>> /opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}: No > >> such > >>> file or directory.

But it isn't there . . .

> >>> mv: cannot stat > >>> `/opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}': No > >>> such file or directory > >>> NX> 1006 Session status: closed > >>> NX> 280 Exiting on signal: 15 > >>> > >>> ==================================== > >>> > >>> > >>> > > > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > >http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ> > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/> > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx> ________________________________________________________________
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Force new NX Session without getting the Session Chooser

2009-11-26T15:43:29Z

On Tue, 24 Nov 2009 10:30:10 +0100
Florian Schmidt <fschmidt@...> wrote:

> Hi,
>
> I am interested in forcing a new session for a user by just changing the
> session file. So even when a user has connected and working sessions I want
> to create a session file to force a new session without getting the session
> chooser (where you than also can reconnect old sessions)
>

Florian, do you mean to never give users a persistent session (not being
able to suspend/resume) and always give them a new session - even
if they have one running?

If this is what you want, you can achieve this by setting in the node.conf
file on the server (typically found here: /etc/nxserver/node.conf):
DISABLE_PERSISTENT_SESSION="all"
(you can change "all" to a group of users, or a list of users if you want
it only to be enforced for some users.)

When your users log out, it will take about 30 secs until they're session
is killed/removed.

> I checked the source of nxserver but I haven't found anything there to allow
> such a behavior. Does anyone knows if this is possible or of this could be
> patched in the source and if so maybe even how?
>

I would take a look into what the node.conf file provides of settings and
possibilities, I think this is possible to achieve (look at the Quickstart
guide to FreeNX, or FAQ, for explaination for the settings/directives).
Also look at 'nxacl' tool which gives another set of admin control of the users
and their sessions. You can find more information about it at the FAQ (look
at the bottom of this mail).

//Terje
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Assistance compiling FreeNX on OpenSolaris

2009-11-26T14:31:00Z

First of all, that is not an error, it is a header identifying the compiler. Usually this is caused by missing or incorrect parameters likely due to the fact that the configure script fails to identify whether one of the parameters are acceptable for the Solaris compiler or not. Also, I don't think Sun Solaris is one of the tested grounds for freenx, and gcc is the only compiler I have ever used to build it with. Do you have gcc on Solaris? It would be worth it to try to get gcc to work instead. If not, maybe someone here that knows Solaris can offer to help you with this. I find it strange that your primary compiler is in /opt as well, this is usually not the case, but I am unfamiliar with Solaris.

If you want to force another compiler you can try

export CC=[path to compiler]

That will change the default compiler path in the environment. At least it works for me anyways. Again, Solaris is different so I'm not sure I can help a whole lot. Is there a reason you are using Solaris?

Alex Smith (K4RNT) wrote:

I've tried following the directions and it compiles fine, until I try
to compile freenx itself, where it tries to use /opt/SUNWspro/bin as
the compiler (in reality this is the directory that the compiler is
housed in). I've tried multiple times modifying the Makefile, but it
constantly gives this error.

OpenSolaris Development snv_127 X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 06 November 2009

SunOS excelsior 5.11 snv_127 i86pc i386 i86pc Solaris

Let me know if there's any other information you need. Thanks in advance!
--
" ' With the first link, the chain is forged. The first speech
censured, the first thought forbidden, the first freedom denied,
chains us all irrevocably.' Those words were uttered by Judge Aaron
Satie as wisdom and warning... The first time any man's freedom is
trodden on we’re all damaged." - Jean-Luc Picard, quoting Judge Aaron
Satie, Star Trek: TNG episode "The Drumhead"
- Alex Smith (K4RNT)
- Murfreesboro/Nashville, Tennessee USA
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Solved "evdev" keyboard mapping issues.

2009-11-26T14:05:41Z

Thank you for your post Troban. We will test your patch to see if it needs revision and submit it to the freenx-team ppa for inclusion testing for an upcoming bug fix release. I don't think there is a problem with your patch. I just need to make sure we haven't left out another area in nxnode that could use this change as well.

Troban Trumsko wrote:

After upgrading my desktop linux to openSuSE 11.2, I got problems with the keyboard mapping, when logging to a freeNX server. (The most obvious symptom were the broken arrow keys).

It turned out, that openSuSE uses the "AutoAddDevices" option by default.

A workaround on the client side was to use the "AutoAddDevices off" option in the "local" xorg.conf:

Section "ServerFlags"
# Uncomment the following option to reenable kbd/mouse driver input sections.
# Otherwise evdev driver is used.
Option "AutoAddDevices" "off"
Option "AllowMouseOpenFail" "on"
EndSection

However, nomachine claimed to have fixed this problem since the beginning of this year:
http://web01.nomachine.com/tr/view.php?id=TR11F02129

Nevertheless even using a recent version of nxagent with the freenx-server did not solve the problem. It turned out, that nxagent needs the "client" option to be passed to work around the "evdev" problem.

A small change in the nxnode script fixed the problem:
@@ -1246,7 +1246,7 @@

umask 0077

cat << EOF > "$USER_FAKE_HOME/.nx/C-$sess_id/options"

-${keyboard:+keyboard=$keyboard,}${kbtype:+kbtype=$kbtype,}${kbload:+kbload=$kbload,}${keymap:+keymap=$keymap,}${resize:+resize=$resize,}${CACHE}${IMAGES}${PACK}link=$link,nodelay=$nodelay,type=$realtype,cleanup=0,${ACCEPT}cookie=$proxy_cookie,id=$sess_id,samba=$samba,media=$media${sync:+,sync=$sync}${cups:+,cups=$cups}${keybd:+,keybd=$keybd}${aux:+,aux=$aux}${http:+,http=$http}${rdpcolors:+,rdpcolors=$rdpcolors}${rdpcache:+,rdpcache=$rdpcache}${fullscreen:+,fullscreen=1}${clipboard:+,clipboard=$clipboard}${menu:+,menu=$menu}:$display

+${keyboard:+keyboard=$keyboard,}${client:+client=$client,}${kbtype:+kbtype=$kbtype,}${kbload:+kbload=$kbload,}${keymap:+keymap=$keymap,}${resize:+resize=$resize,}${CACHE}${IMAGES}${PACK}link=$link,nodelay=$nodelay,type=$realtype,cleanup=0,${ACCEPT}cookie=$proxy_cookie,id=$sess_id,samba=$samba,media=$media${sync:+,sync=$sync}${cups:+,cups=$cups}${keybd:+,keybd=$keybd}${aux:+,aux=$aux}${http:+,http=$http}${rdpcolors:+,rdpcolors=$rdpcolors}${rdpcache:+,rdpcache=$rdpcache}${fullscreen:+,fullscreen=1}${clipboard:+,clipboard=$clipboard}${menu:+,menu=$menu}:$display

EOF

umask $OLD_UMASK

I hope this might help you as well.

Cheers, Troban.

The problem occurs, if the X-server on the client machine uses the
evdev keyboard driver. In principle this problem is fixed in 'nxagent'
within the 3.3.0 series. However it turns out, that using a recent
(>3.3.0-11) nxagent is not enough to solve the problem. To work
properly, the "client" option has to be passed to nxagent. This can
easily be done by fixing the 'nxnode' script:

@@ -1246,7 +1246,7 @@

umask 0077

cat << EOF > "$USER_FAKE_HOME/.nx/C-$sess_id/options"

-${keyboard:+keyboard=$keyboard,}${kbtype:+kbtype=$kbtype,}${kbload:+kbload=$kbload,}${keymap:+keymap=$keymap,}${resize:+resize=$resize,}${CACHE}${IMAGES}${PACK}link=$link,nodelay=$nodelay,type=$realtype,cleanup=0,${ACCEPT}cookie=$proxy_cookie,id=$sess_id,samba=$samba,media=$media${sync:+,sync=$sync}${cups:+,cups=$cups}${keybd:+,keybd=$keybd}${aux:+,aux=$aux}${http:+,http=$http}${rdpcolors:+,rdpcolors=$rdpcolors}${rdpcache:+,rdpcache=$rdpcache}${fullscreen:+,fullscreen=1}${clipboard:+,clipboard=$clipboard}${menu:+,menu=$menu}:$display

+${keyboard:+keyboard=$keyboard,}${client:+client=$client,}${kbtype:+kbtype=$kbtype,}${kbload:+kbload=$kbload,}${keymap:+keymap=$keymap,}${resize:+resize=$resize,}${CACHE}${IMAGES}${PACK}link=$link,nodelay=$nodelay,type=$realtype,cleanup=0,${ACCEPT}cookie=$proxy_cookie,id=$sess_id,samba=$samba,media=$media${sync:+,sync=$sync}${cups:+,cups=$cups}${keybd:+,keybd=$keybd}${aux:+,aux=$aux}${http:+,http=$http}${rdpcolors:+,rdpcolors=$rdpcolors}${rdpcache:+,rdpcache=$rdpcache}${fullscreen:+,fullscreen=1}${clipboard:+,clipboard=$clipboard}${menu:+,menu=$menu}:$display

EOF

umask $OLD_UMASK

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-26T13:43:24Z

Sorry to sound like a broken record. The correct path is /opt/NX/var/db

Oops need to correct Marcelo on paths though. Your path is /opt/NX/db

Jeremy Wilkins wrote:

I agree with Marcelo. It sounds like it is a db file/port conflict. Try these and report back.

Marcelo Boveto Shima wrote:

Hi,

I can see two possible causes:
1 - /var/lib/nxserver/db/running/ should be empty after the reboot.
$nxserver --cleanup should clean the directory
2 - Ports needed by the four session are been used. Set the
DISPLAY_BASE=(last display value + 10) on /etc/nxserver/node.conf.

Hope this helps.
Regards.

Marcelo

On Wed, Nov 25, 2009 at 4:53 PM, yossarianuk <morgancoxuk@gmail.com> wrote:
>
> Hi.
>
> 100% sure it is not fsck'ing ...
>
> For a start I can always ssh , it also doesn't matter how long I leave it -
> I can leave it hours and the result will be the same - fail 4 times, then
> success...
>
> After setting SESSION_LOG_CLEAN=0 I have seen the following
>
> [root@winwinwinwin yossarian]# cat
> /home/yossarian/.nx/F-C-winwinwinwin-1000-2EEE03F57CDE5A5295F5B8E24F656371/session
> $DISPLAY is not set or cannot connect to the X server.
>
> xrdb: No such file or directory xrdb: Can't open display ':1000' $DISPLAY is
> not set or cannot connect to the X server.
>
> After the 4th attempt it works fine ???
>
>
>
>
>
> ChrisB-6 wrote:
>>
>> yossarianuk <morgancoxuk@gmail.com> wrote on 23/11/2009 17:29:56:
>>
>>>
>>> Hi.
>>>
>>> This issue has been going on for at least 4-6 months now...
>>>
>>> I am running latest freenx on archlinux (686)
>>>
>>> It works absolutely fine, until I reboot.
>>>
>>> Then every single time I have to try to login (and fail) 3 times, then
>> on
>>> the 4th login to works, then anyone can login - freenx will then be 100%
>>> fine until the next reboot.
>>
>>
>> Are you sure you aren't waiting for fsck etc to finish ??
>>
>>>
>>> Can anyone think of ANYTHING I can do to stop this happening ??? It is
>>> really annoying,
>>>
>>> I did raise a post about this several months ago, I followed advice at
>> the
>>> end, it still happens.
>>>
>>> (old post : http://markmail.org/message/44j3xah7v6hzlezv )
>>>
>>> Here is an example fail.
>>>
>>> ====================================
>>> Display Type Session ID Options Depth
>>> Screen Status Session Name
>>> ------- ---------------- -------------------------------- -------- -----
>>> -------------- ----------- ------------------------------
>>>
>>>
>>> NX> 148 Server capacity: not reached for user: yossarian
>>> NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1"
>>> --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
>>> --composite="1" --media="0" --session="Gateway" --type="unix-kde"
>>> --geometry="1280x976" --client="linux" --keyboard="pc105/gb"
>>> --screeninfo="1280x976x24+render"
>>>
>>> NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
>>> NX> 700 Session id: gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE
>>> NX> 705 Session display: 1000
>>> NX> 703 Session type: unix-kde
>>> NX> 701 Proxy cookie: 8b4424fcb9928f98bad143bae200b63b
>>> NX> 702 Proxy IP: 127.0.0.1
>>> NX> 706 Agent cookie: 8b4424fcb9928f98bad143bae200b63b
>>> NX> 704 Session cache: unix-kde
>>> NX> 707 SSL tunneling: 1
>>> NX> 105 /opt/NX/bin/nxserver: line 1531: 2161 Terminated sleep
>>> $AGENT_STARTUP_TIMEOUT
>>
>> no agent
>>
>>
>>
>>> NX> 596 Session startup failed.
>>> NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
>>> SESSION_LOG_CLEAN=0 in node.conf and investigate
>>>
>> "/home/yossarian/.nx/F-C-gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE/session".
>>
>> Did you do this ?? What did it say ??
>>
>>> You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent
>> to
>>> test the basic functionality. Session log follows:
>>> Can't open
>>> /opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}: No
>> such
>>> file or directory.
>>> mv: cannot stat
>>> `/opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}': No
>>> such file or directory
>>> NX> 1006 Session status: closed
>>> NX> 280 Exiting on signal: 15
>>>
>>> ====================================
>>>
>>>
>>>
>>> --
>>> View this message in context: http://old.nabble.com/Arch-Linux---
>>> After-reboot-have-to-login-4-times-to-work-------%28every-single-
>>> time%29-tp26482511p26482511.html
>>> Sent from the freenx-knx mailing list archive at Nabble.com.
>>>
>>> ________________________________________________________________
>>> Were you helped on this list with your FreeNX problem?
>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>>
>>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>>
>>> Don't forget to check the NX Knowledge Base:
>>> http://www.nomachine.com/kb/
>>>
>>> ________________________________________________________________
>>> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>> ________________________________________________________________
>>
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
>
> --
> View this message in context: http://old.nabble.com/Arch-Linux---After-reboot-have-to-login-4-times-to-work-------%28every-single-time%29-tp26482511p26518302.html
> Sent from the freenx-knx mailing list archive at Nabble.com.
>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-26T13:42:07Z

Oops need to correct Marcelo on paths though. Your path is /opt/NX/db

I agree with Marcelo. It sounds like it is a db file/port conflict. Try these and report back.

Marcelo Boveto Shima wrote:

Hi,

I can see two possible causes:
1 - /var/lib/nxserver/db/running/ should be empty after the reboot.
$nxserver --cleanup should clean the directory
2 - Ports needed by the four session are been used. Set the
DISPLAY_BASE=(last display value + 10) on /etc/nxserver/node.conf.

Hope this helps.
Regards.

Marcelo

On Wed, Nov 25, 2009 at 4:53 PM, yossarianuk <morgancoxuk@gmail.com> wrote:
>
> Hi.
>
> 100% sure it is not fsck'ing ...
>
> For a start I can always ssh , it also doesn't matter how long I leave it -
> I can leave it hours and the result will be the same - fail 4 times, then
> success...
>
> After setting SESSION_LOG_CLEAN=0 I have seen the following
>
> [root@winwinwinwin yossarian]# cat
> /home/yossarian/.nx/F-C-winwinwinwin-1000-2EEE03F57CDE5A5295F5B8E24F656371/session
> $DISPLAY is not set or cannot connect to the X server.
>
> xrdb: No such file or directory xrdb: Can't open display ':1000' $DISPLAY is
> not set or cannot connect to the X server.
>
> After the 4th attempt it works fine ???
>
>
>
>
>
> ChrisB-6 wrote:
>>
>> yossarianuk <morgancoxuk@gmail.com> wrote on 23/11/2009 17:29:56:
>>
>>>
>>> Hi.
>>>
>>> This issue has been going on for at least 4-6 months now...
>>>
>>> I am running latest freenx on archlinux (686)
>>>
>>> It works absolutely fine, until I reboot.
>>>
>>> Then every single time I have to try to login (and fail) 3 times, then
>> on
>>> the 4th login to works, then anyone can login - freenx will then be 100%
>>> fine until the next reboot.
>>
>>
>> Are you sure you aren't waiting for fsck etc to finish ??
>>
>>>
>>> Can anyone think of ANYTHING I can do to stop this happening ??? It is
>>> really annoying,
>>>
>>> I did raise a post about this several months ago, I followed advice at
>> the
>>> end, it still happens.
>>>
>>> (old post : http://markmail.org/message/44j3xah7v6hzlezv )
>>>
>>> Here is an example fail.
>>>
>>> ====================================
>>> Display Type Session ID Options Depth
>>> Screen Status Session Name
>>> ------- ---------------- -------------------------------- -------- -----
>>> -------------- ----------- ------------------------------
>>>
>>>
>>> NX> 148 Server capacity: not reached for user: yossarian
>>> NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1"
>>> --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
>>> --composite="1" --media="0" --session="Gateway" --type="unix-kde"
>>> --geometry="1280x976" --client="linux" --keyboard="pc105/gb"
>>> --screeninfo="1280x976x24+render"
>>>
>>> NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
>>> NX> 700 Session id: gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE
>>> NX> 705 Session display: 1000
>>> NX> 703 Session type: unix-kde
>>> NX> 701 Proxy cookie: 8b4424fcb9928f98bad143bae200b63b
>>> NX> 702 Proxy IP: 127.0.0.1
>>> NX> 706 Agent cookie: 8b4424fcb9928f98bad143bae200b63b
>>> NX> 704 Session cache: unix-kde
>>> NX> 707 SSL tunneling: 1
>>> NX> 105 /opt/NX/bin/nxserver: line 1531: 2161 Terminated sleep
>>> $AGENT_STARTUP_TIMEOUT
>>
>> no agent
>>
>>
>>
>>> NX> 596 Session startup failed.
>>> NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
>>> SESSION_LOG_CLEAN=0 in node.conf and investigate
>>>
>> "/home/yossarian/.nx/F-C-gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE/session".
>>
>> Did you do this ?? What did it say ??
>>
>>> You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent
>> to
>>> test the basic functionality. Session log follows:
>>> Can't open
>>> /opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}: No
>> such
>>> file or directory.
>>> mv: cannot stat
>>> `/opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}': No
>>> such file or directory
>>> NX> 1006 Session status: closed
>>> NX> 280 Exiting on signal: 15
>>>
>>> ====================================
>>>
>>>
>>>
>>> --
>>> View this message in context: http://old.nabble.com/Arch-Linux---
>>> After-reboot-have-to-login-4-times-to-work-------%28every-single-
>>> time%29-tp26482511p26482511.html
>>> Sent from the freenx-knx mailing list archive at Nabble.com.
>>>
>>> ________________________________________________________________
>>> Were you helped on this list with your FreeNX problem?
>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>>
>>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>>
>>> Don't forget to check the NX Knowledge Base:
>>> http://www.nomachine.com/kb/
>>>
>>> ________________________________________________________________
>>> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>> ________________________________________________________________
>>
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
>
> --
> View this message in context: http://old.nabble.com/Arch-Linux---After-reboot-have-to-login-4-times-to-work-------%28every-single-time%29-tp26482511p26518302.html
> Sent from the freenx-knx mailing list archive at Nabble.com.
>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-26T13:39:33Z

I agree with Marcelo. It sounds like it is a db file/port conflict. Try these and report back.

Marcelo Boveto Shima wrote:

Hi,

I can see two possible causes:
1 - /var/lib/nxserver/db/running/ should be empty after the reboot.
$nxserver --cleanup should clean the directory
2 - Ports needed by the four session are been used. Set the
DISPLAY_BASE=(last display value + 10) on /etc/nxserver/node.conf.

Hope this helps.
Regards.

Marcelo

On Wed, Nov 25, 2009 at 4:53 PM, yossarianuk <morgancoxuk@gmail.com> wrote:
>
> Hi.
>
> 100% sure it is not fsck'ing ...
>
> For a start I can always ssh , it also doesn't matter how long I leave it -
> I can leave it hours and the result will be the same - fail 4 times, then
> success...
>
> After setting SESSION_LOG_CLEAN=0 I have seen the following
>
> [root@winwinwinwin yossarian]# cat
> /home/yossarian/.nx/F-C-winwinwinwin-1000-2EEE03F57CDE5A5295F5B8E24F656371/session
> $DISPLAY is not set or cannot connect to the X server.
>
> xrdb: No such file or directory xrdb: Can't open display ':1000' $DISPLAY is
> not set or cannot connect to the X server.
>
> After the 4th attempt it works fine ???
>
>
>
>
>
> ChrisB-6 wrote:
>>
>> yossarianuk <morgancoxuk@gmail.com> wrote on 23/11/2009 17:29:56:
>>
>>>
>>> Hi.
>>>
>>> This issue has been going on for at least 4-6 months now...
>>>
>>> I am running latest freenx on archlinux (686)
>>>
>>> It works absolutely fine, until I reboot.
>>>
>>> Then every single time I have to try to login (and fail) 3 times, then
>> on
>>> the 4th login to works, then anyone can login - freenx will then be 100%
>>> fine until the next reboot.
>>
>>
>> Are you sure you aren't waiting for fsck etc to finish ??
>>
>>>
>>> Can anyone think of ANYTHING I can do to stop this happening ??? It is
>>> really annoying,
>>>
>>> I did raise a post about this several months ago, I followed advice at
>> the
>>> end, it still happens.
>>>
>>> (old post : http://markmail.org/message/44j3xah7v6hzlezv )
>>>
>>> Here is an example fail.
>>>
>>> ====================================
>>> Display Type Session ID Options Depth
>>> Screen Status Session Name
>>> ------- ---------------- -------------------------------- -------- -----
>>> -------------- ----------- ------------------------------
>>>
>>>
>>> NX> 148 Server capacity: not reached for user: yossarian
>>> NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1"
>>> --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
>>> --composite="1" --media="0" --session="Gateway" --type="unix-kde"
>>> --geometry="1280x976" --client="linux" --keyboard="pc105/gb"
>>> --screeninfo="1280x976x24+render"
>>>
>>> NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
>>> NX> 700 Session id: gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE
>>> NX> 705 Session display: 1000
>>> NX> 703 Session type: unix-kde
>>> NX> 701 Proxy cookie: 8b4424fcb9928f98bad143bae200b63b
>>> NX> 702 Proxy IP: 127.0.0.1
>>> NX> 706 Agent cookie: 8b4424fcb9928f98bad143bae200b63b
>>> NX> 704 Session cache: unix-kde
>>> NX> 707 SSL tunneling: 1
>>> NX> 105 /opt/NX/bin/nxserver: line 1531: 2161 Terminated sleep
>>> $AGENT_STARTUP_TIMEOUT
>>
>> no agent
>>
>>
>>
>>> NX> 596 Session startup failed.
>>> NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
>>> SESSION_LOG_CLEAN=0 in node.conf and investigate
>>>
>> "/home/yossarian/.nx/F-C-gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE/session".
>>
>> Did you do this ?? What did it say ??
>>
>>> You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent
>> to
>>> test the basic functionality. Session log follows:
>>> Can't open
>>> /opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}: No
>> such
>>> file or directory.
>>> mv: cannot stat
>>> `/opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}': No
>>> such file or directory
>>> NX> 1006 Session status: closed
>>> NX> 280 Exiting on signal: 15
>>>
>>> ====================================
>>>
>>>
>>>
>>> --
>>> View this message in context: http://old.nabble.com/Arch-Linux---
>>> After-reboot-have-to-login-4-times-to-work-------%28every-single-
>>> time%29-tp26482511p26482511.html
>>> Sent from the freenx-knx mailing list archive at Nabble.com.
>>>
>>> ________________________________________________________________
>>> Were you helped on this list with your FreeNX problem?
>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>>
>>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>>
>>> Don't forget to check the NX Knowledge Base:
>>> http://www.nomachine.com/kb/
>>>
>>> ________________________________________________________________
>>> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>> ________________________________________________________________
>>
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
>
> --
> View this message in context: http://old.nabble.com/Arch-Linux---After-reboot-have-to-login-4-times-to-work-------%28every-single-time%29-tp26482511p26518302.html
> Sent from the freenx-knx mailing list archive at Nabble.com.
>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-26T09:39:15Z

Clive Eisen <clive@...> wrote on 25/11/2009 20:18:45: > Have a look in > /tmp/.X11-unix/ > > you may find three dead sessions in there >

nxserver looks for already existing sockets . . . .

while [ -e /tmp/.X$SESS_DISPLAY-lock -o -e "/tmp/.nX$SESS_DISPLAY-lock" -o -e "/tmp/.X11-unix/X$SESS_DISPLAY" ]
do
let SESS_DISPLAY=$SESS_DISPLAY+1
done

> > On 25 Nov 2009, at 18:53, yossarianuk wrote: > > > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > >http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ> > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/> > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx> ________________________________________________________________
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-26T06:39:48Z

yossarianuk schrieb:
> It works absolutely fine, until I reboot.
>
> Then every single time I have to try to login (and fail) 3 times, then on
> the 4th login to works, then anyone can login - freenx will then be 100%
> fine until the next reboot.

I don't have a solution for you, but i can confirm that you are not
alone with this. I'm running Suse 11.0

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Printing and sharing issue

2009-11-26T04:13:08Z

Hi Chris,

Thanks for your reply.

Turn on trace in at the top of /usr/lib/cups/backend/nxsmb
by removing the # from
#set -x -v
Find the printer's full URI by looking for
DeviceURI nxsmb:
in /home/user/.nx/C-machine-port-session/cups/printers.conf

As THE CONNECTED NX user, at a command prompt on the NX server enter
export DEVICE_URI=nxsmb://user-name:password@...
or whatever you found in printers.conf
Make a small test text file, then in the SAME SESSION, run : -
/usr/lib/cups/backend/nxsmb 1 1 1 1 your-text-test-file.txt

The problem was, /usr/lib/libnxredir.so.0 didn't have the permission. Now both printing and file-sharing is working fine.

SAMBA_MOUNT_SHARE_PROTOCOL="both"

Thanks,
Vivek

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-25T18:02:20Z

Hi,

I can see two possible causes:
1 - /var/lib/nxserver/db/running/ should be empty after the reboot.
$nxserver --cleanup should clean the directory
2 - Ports needed by the four session are been used. Set the
DISPLAY_BASE=(last display value + 10) on /etc/nxserver/node.conf.

Hope this helps.
Regards.

Marcelo

On Wed, Nov 25, 2009 at 4:53 PM, yossarianuk <morgancoxuk@...> wrote:

>
> Hi.
>
> 100% sure it is not fsck'ing ...
>
> For a start I can always ssh , it also doesn't matter how long I leave it -
> I can leave it hours and the result will be the same - fail 4 times, then
> success...
>
> After setting SESSION_LOG_CLEAN=0 I have seen the following
>
> [root@winwinwinwin yossarian]# cat
> /home/yossarian/.nx/F-C-winwinwinwin-1000-2EEE03F57CDE5A5295F5B8E24F656371/session
> $DISPLAY is not set or cannot connect to the X server.
>
> xrdb: No such file or directory xrdb: Can't open display ':1000' $DISPLAY is
> not set or cannot connect to the X server.
>
> After the 4th attempt it works fine ???
>
>
>
>
>
> ChrisB-6 wrote:
>>
>> yossarianuk <morgancoxuk@...> wrote on 23/11/2009 17:29:56:
>>
>>>
>>> Hi.
>>>
>>> This issue has been going on for at least 4-6 months now...
>>>
>>> I am running latest freenx on archlinux (686)
>>>
>>> It works absolutely fine, until I reboot.
>>>
>>> Then every single time I have to try to login (and fail) 3 times, then
>> on
>>> the 4th login to works, then anyone can login - freenx will then be 100%
>>> fine until the next reboot.
>>
>>
>> Are you sure you aren't waiting for fsck etc to finish ??
>>
>>>
>>> Can anyone think of ANYTHING I can do to stop this happening ??? It is
>>> really annoying,
>>>
>>> I did raise a post about this several months ago, I followed advice at
>> the
>>> end, it still happens.
>>>
>>> (old post : http://markmail.org/message/44j3xah7v6hzlezv )
>>>
>>> Here is an example fail.
>>>
>>> ====================================
>>> Display Type Session ID Options Depth
>>> Screen Status Session Name
>>> ------- ---------------- -------------------------------- -------- -----
>>> -------------- ----------- ------------------------------
>>>
>>>
>>> NX> 148 Server capacity: not reached for user: yossarian
>>> NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1"
>>> --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
>>> --composite="1" --media="0" --session="Gateway" --type="unix-kde"
>>> --geometry="1280x976" --client="linux" --keyboard="pc105/gb"
>>> --screeninfo="1280x976x24+render"
>>>
>>> NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
>>> NX> 700 Session id: gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE
>>> NX> 705 Session display: 1000
>>> NX> 703 Session type: unix-kde
>>> NX> 701 Proxy cookie: 8b4424fcb9928f98bad143bae200b63b
>>> NX> 702 Proxy IP: 127.0.0.1
>>> NX> 706 Agent cookie: 8b4424fcb9928f98bad143bae200b63b
>>> NX> 704 Session cache: unix-kde
>>> NX> 707 SSL tunneling: 1
>>> NX> 105 /opt/NX/bin/nxserver: line 1531: 2161 Terminated sleep
>>> $AGENT_STARTUP_TIMEOUT
>>
>> no agent
>>
>>
>>
>>> NX> 596 Session startup failed.
>>> NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
>>> SESSION_LOG_CLEAN=0 in node.conf and investigate
>>>
>> "/home/yossarian/.nx/F-C-gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE/session".
>>
>> Did you do this ?? What did it say ??
>>
>>> You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent
>> to
>>> test the basic functionality. Session log follows:
>>> Can't open
>>> /opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}: No
>> such
>>> file or directory.
>>> mv: cannot stat
>>> `/opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}': No
>>> such file or directory
>>> NX> 1006 Session status: closed
>>> NX> 280 Exiting on signal: 15
>>>
>>> ====================================
>>>
>>>
>>>
>>> --
>>> View this message in context: http://old.nabble.com/Arch-Linux---
>>> After-reboot-have-to-login-4-times-to-work-------%28every-single-
>>> time%29-tp26482511p26482511.html
>>> Sent from the freenx-knx mailing list archive at Nabble.com.
>>>
>>> ________________________________________________________________
>>> Were you helped on this list with your FreeNX problem?
>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>>
>>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>>
>>> Don't forget to check the NX Knowledge Base:
>>> http://www.nomachine.com/kb/
>>>
>>> ________________________________________________________________
>>> FreeNX-kNX mailing list --- FreeNX-kNX@...
>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>> ________________________________________________________________
>>
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>> FreeNX-kNX mailing list --- FreeNX-kNX@...
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
>
> --
> View this message in context: http://old.nabble.com/Arch-Linux---After-reboot-have-to-login-4-times-to-work-------%28every-single-time%29-tp26482511p26518302.html
> Sent from the freenx-knx mailing list archive at Nabble.com.
>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@...
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-25T12:18:45Z

Have a look in
/tmp/.X11-unix/

you may find three dead sessions in there

On 25 Nov 2009, at 18:53, yossarianuk wrote:

>
>
> Hi.
>
> 100% sure it is not fsck'ing ...
>
> For a start I can always ssh , it also doesn't matter how long I leave it -
> I can leave it hours and the result will be the same - fail 4 times, then
> success...
>
> After setting SESSION_LOG_CLEAN=0 I have seen the following
>
> [root@winwinwinwin yossarian]# cat
> /home/yossarian/.nx/F-C-winwinwinwin-1000-2EEE03F57CDE5A5295F5B8E24F656371/session
> $DISPLAY is not set or cannot connect to the X server.
>
> xrdb: No such file or directory xrdb: Can't open display ':1000' $DISPLAY is
> not set or cannot connect to the X server.
>
> After the 4th attempt it works fine ???
>
>
>
>
>
> ChrisB-6 wrote:
>>
>> yossarianuk <morgancoxuk@...> wrote on 23/11/2009 17:29:56:
>>
>>>
>>> Hi.
>>>
>>> This issue has been going on for at least 4-6 months now...
>>>
>>> I am running latest freenx on archlinux (686)
>>>
>>> It works absolutely fine, until I reboot.
>>>
>>> Then every single time I have to try to login (and fail) 3 times, then
>> on
>>> the 4th login to works, then anyone can login - freenx will then be 100%
>>> fine until the next reboot.
>>
>>
>> Are you sure you aren't waiting for fsck etc to finish ??
>>
>>>
>>> Can anyone think of ANYTHING I can do to stop this happening ??? It is
>>> really annoying,
>>>
>>> I did raise a post about this several months ago, I followed advice at
>> the
>>> end, it still happens.
>>>
>>> (old post : http://markmail.org/message/44j3xah7v6hzlezv )
>>>
>>> Here is an example fail.
>>>
>>> ====================================
>>> Display Type Session ID Options Depth
>>> Screen Status Session Name
>>> ------- ---------------- -------------------------------- -------- -----
>>> -------------- ----------- ------------------------------
>>>
>>>
>>> NX> 148 Server capacity: not reached for user: yossarian
>>> NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1"
>>> --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
>>> --composite="1" --media="0" --session="Gateway" --type="unix-kde"
>>> --geometry="1280x976" --client="linux" --keyboard="pc105/gb"
>>> --screeninfo="1280x976x24+render"
>>>
>>> NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
>>> NX> 700 Session id: gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE
>>> NX> 705 Session display: 1000
>>> NX> 703 Session type: unix-kde
>>> NX> 701 Proxy cookie: 8b4424fcb9928f98bad143bae200b63b
>>> NX> 702 Proxy IP: 127.0.0.1
>>> NX> 706 Agent cookie: 8b4424fcb9928f98bad143bae200b63b
>>> NX> 704 Session cache: unix-kde
>>> NX> 707 SSL tunneling: 1
>>> NX> 105 /opt/NX/bin/nxserver: line 1531: 2161 Terminated sleep
>>> $AGENT_STARTUP_TIMEOUT
>>
>> no agent
>>
>>
>>
>>> NX> 596 Session startup failed.
>>> NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
>>> SESSION_LOG_CLEAN=0 in node.conf and investigate
>>>
>> "/home/yossarian/.nx/F-C-gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE/session".
>>
>> Did you do this ?? What did it say ??
>>
>>> You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent
>> to
>>> test the basic functionality. Session log follows:
>>> Can't open
>>> /opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}: No
>> such
>>> file or directory.
>>> mv: cannot stat
>>> `/opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}': No
>>> such file or directory
>>> NX> 1006 Session status: closed
>>> NX> 280 Exiting on signal: 15
>>>
>>> ====================================
>>>
>>>
>>>
>>> --
>>> View this message in context: http://old.nabble.com/Arch-Linux---
>>> After-reboot-have-to-login-4-times-to-work-------%28every-single-
>>> time%29-tp26482511p26482511.html
>>> Sent from the freenx-knx mailing list archive at Nabble.com.
>>>
>>> ________________________________________________________________
>>> Were you helped on this list with your FreeNX problem?
>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>>
>>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>>
>>> Don't forget to check the NX Knowledge Base:
>>> http://www.nomachine.com/kb/
>>>
>>> ________________________________________________________________
>>> FreeNX-kNX mailing list --- FreeNX-kNX@...
>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>> ________________________________________________________________
>>
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>> FreeNX-kNX mailing list --- FreeNX-kNX@...
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
>
> --
> View this message in context: http://old.nabble.com/Arch-Linux---After-reboot-have-to-login-4-times-to-work-------%28every-single-time%29-tp26482511p26518302.html
> Sent from the freenx-knx mailing list archive at Nabble.com.
>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@...
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________

Re: Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-25T11:13:26Z

yossarianuk <morgancoxuk@...> wrote on 25/11/2009 18:53:31: > > Hi. > > 100% sure it is not fsck'ing ... > > For a start I can always ssh , it also doesn't matter how long I leave it - > I can leave it hours and the result will be the same - fail 4 times, then > success... > > After setting SESSION_LOG_CLEAN=0 I have seen the following >
There should be lots more detail in the logs. Did you try setting these in
/etc/nxserver/node.conf then looking for complaints ???

NX_LOG_LEVEL=6
NX_LOG_SECURE=1
# Before turning logging on, please make sure that NX_LOGFILE iswriteable for the "nx" user
NX_LOGFILE=/var/log/nxserver.log # You can put this anywhere convenient

> [root@winwinwinwin yossarian]# cat > /home/yossarian/.nx/F-C- > winwinwinwin-1000-2EEE03F57CDE5A5295F5B8E24F656371/session > $DISPLAY is not set or cannot connect to the X server. > > xrdb: No such file or directory xrdb: Can't open display ':1000' $DISPLAY is > not set or cannot connect to the X server. > > After the 4th attempt it works fine ??? > >

So there is no time factor???

If you login once, fail then wait 10 mis, does it work the second time ??

Are the failed sessions still there or do they disappear ??

> > > > > -- > View this message in context:http://old.nabble.com/Arch-Linux---> After-reboot-have-to-login-4-times-to-work-------%28every-single- > time%29-tp26482511p26518302.html > Sent from the freenx-knx mailing list archive at Nabble.com. > > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > >http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ> > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/> > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx> ________________________________________________________________
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-25T10:53:30Z

Hi.

100% sure it is not fsck'ing ...

For a start I can always ssh , it also doesn't matter how long I leave it - I can leave it hours and the result will be the same - fail 4 times, then success...

After setting SESSION_LOG_CLEAN=0 I have seen the following

[root@winwinwinwin yossarian]# cat /home/yossarian/.nx/F-C-winwinwinwin-1000-2EEE03F57CDE5A5295F5B8E24F656371/session $DISPLAY is not set or cannot connect to the X server.

xrdb: No such file or directory xrdb: Can't open display ':1000' $DISPLAY is not set or cannot connect to the X server.

After the 4th attempt it works fine ???

ChrisB-6 wrote:

yossarianuk <morgancoxuk@gmail.com> wrote on 23/11/2009 17:29:56:

>
> Hi.
>
> This issue has been going on for at least 4-6 months now...
>
> I am running latest freenx on archlinux (686)
>
> It works absolutely fine, until I reboot.
>
> Then every single time I have to try to login (and fail) 3 times, then
on
> the 4th login to works, then anyone can login - freenx will then be 100%
> fine until the next reboot.

Are you sure you aren't waiting for fsck etc to finish ??

>
> Can anyone think of ANYTHING I can do to stop this happening ??? It is
> really annoying,
>
> I did raise a post about this several months ago, I followed advice at
the
> end, it still happens.
>
> (old post : http://markmail.org/message/44j3xah7v6hzlezv )
>
> Here is an example fail.
>
> ====================================
> Display Type Session ID Options Depth
> Screen Status Session Name
> ------- ---------------- -------------------------------- -------- -----
> -------------- ----------- ------------------------------
>
>
> NX> 148 Server capacity: not reached for user: yossarian
> NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1"
> --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
> --composite="1" --media="0" --session="Gateway" --type="unix-kde"
> --geometry="1280x976" --client="linux" --keyboard="pc105/gb"
> --screeninfo="1280x976x24+render"
>
> NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
> NX> 700 Session id: gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE
> NX> 705 Session display: 1000
> NX> 703 Session type: unix-kde
> NX> 701 Proxy cookie: 8b4424fcb9928f98bad143bae200b63b
> NX> 702 Proxy IP: 127.0.0.1
> NX> 706 Agent cookie: 8b4424fcb9928f98bad143bae200b63b
> NX> 704 Session cache: unix-kde
> NX> 707 SSL tunneling: 1
> NX> 105 /opt/NX/bin/nxserver: line 1531: 2161 Terminated sleep
> $AGENT_STARTUP_TIMEOUT

no agent

> NX> 596 Session startup failed.
> NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
> SESSION_LOG_CLEAN=0 in node.conf and investigate
>
"/home/yossarian/.nx/F-C-gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE/session".

Did you do this ?? What did it say ??

> You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent
to
> test the basic functionality. Session log follows:
> Can't open
> /opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}: No
such
> file or directory.
> mv: cannot stat
> `/opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}': No
> such file or directory
> NX> 1006 Session status: closed
> NX> 280 Exiting on signal: 15
>
> ====================================
>
>
>
> --
> View this message in context: http://old.nabble.com/Arch-Linux---
> After-reboot-have-to-login-4-times-to-work-------%28every-single-
> time%29-tp26482511p26482511.html
> Sent from the freenx-knx mailing list archive at Nabble.com.
>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
>
http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-25T08:25:29Z

yossarianuk <morgancoxuk@...> wrote on 23/11/2009 17:29:56: > > Hi. > > This issue has been going on for at least 4-6 months now... > > I am running latest freenx on archlinux (686) > > It works absolutely fine, until I reboot. > > Then every single time I have to try to login (and fail) 3 times, then on > the 4th login to works, then anyone can login - freenx will then be 100% > fine until the next reboot.

Are you sure you aren't waiting for fsck etc to finish ??
> > Can anyone think of ANYTHING I can do to stop this happening ??? It is > really annoying, > > I did raise a post about this several months ago, I followed advice at the > end, it still happens. > > (old post :http://markmail.org/message/44j3xah7v6hzlezv) > > Here is an example fail. > > ==================================== > Display Type Session ID Options Depth > Screen Status Session Name > ------- ---------------- -------------------------------- -------- ----- > -------------- ----------- ------------------------------ > > > NX> 148 Server capacity: not reached for user: yossarian > NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1" > --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" > --composite="1" --media="0" --session="Gateway" --type="unix-kde" > --geometry="1280x976" --client="linux" --keyboard="pc105/gb" > --screeninfo="1280x976x24+render" > > NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0) > NX> 700 Session id: gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE > NX> 705 Session display: 1000 > NX> 703 Session type: unix-kde > NX> 701 Proxy cookie: 8b4424fcb9928f98bad143bae200b63b > NX> 702 Proxy IP: 127.0.0.1 > NX> 706 Agent cookie: 8b4424fcb9928f98bad143bae200b63b > NX> 704 Session cache: unix-kde > NX> 707 SSL tunneling: 1 > NX> 105 /opt/NX/bin/nxserver: line 1531: 2161 Terminated sleep > $AGENT_STARTUP_TIMEOUT
no agent

> NX> 596 Session startup failed. > NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set > SESSION_LOG_CLEAN=0 in node.conf and investigate > "/home/yossarian/.nx/F-C-gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE/session".
Did you do this ?? What did it say ??

> You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent to > test the basic functionality. Session log follows: > Can't open > /opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}: No such > file or directory. > mv: cannot stat > `/opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}': No > such file or directory > NX> 1006 Session status: closed > NX> 280 Exiting on signal: 15 > > ==================================== > > > > -- > View this message in context:http://old.nabble.com/Arch-Linux---> After-reboot-have-to-login-4-times-to-work-------%28every-single- > time%29-tp26482511p26482511.html > Sent from the freenx-knx mailing list archive at Nabble.com. > > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > >http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ> > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/> > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx> ________________________________________________________________
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Force new NX Session without getting the Session Chooser

2009-11-25T08:21:48Z

Florian Schmidt <fschmidt@...> wrote on 24/11/2009 09:30:10: > Hi, > > I am interested in forcing a new session for a user by just changing > the session file.

D'you mean (re)moving it ??

So even when a user has connected and working > sessions I want to create a session file to force a new session

Create a session file to force a new session ??

Don't you mean (re)move ??

> without getting the session chooser (where you than also can > reconnect old sessions) > > I checked the source of nxserver but I haven't found anything there > to allow such a behavior. Does anyone knows if this is possible or > of this could be patched in the source and if so maybe even how?
To clear up old sessions, you would need to move the session files
somewhere and modify the cleanup.

If the same account logs on several times, you will get issues if
you use OpenOffice, firefox etc,

> > Cheers, > Florian________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > >http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ> > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/> > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx> ________________________________________________________________
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Printing and sharing issue

2009-11-25T08:15:50Z

Vivek <vivek@...> wrote on 24/11/2009 14:40:19: > > E [24/Nov/2009:19:07:27 +0530] [Job 1] Connection failed: > NT_STATUS_BAD_NETWORK_NAME

Might be a number of things

Turn on trace in at the top of /usr/lib/cups/backend/nxsmb

by removing the # from

#set -x -v

Find the printer's full URI by looking for

DeviceURI nxsmb:

in /home/user/.nx/C-machine-port-session/cups/printers.conf

As THE CONNECTED NX user, at a command prompt on the NX server enter

export DEVICE_URI=nxsmb://user-name:password@...:port/cifs/HP

or whatever you found in printers.conf

Make a small test text file, then in the SAME SESSION, run : -

/usr/lib/cups/backend/nxsmb 1 1 1 1 your-text-test-file.txt

> but we are able to ping the windows client from Ubuntu server using hostname. >
Not down the tunnel tho'

> Server - Ubuntu 9.04 > Client - Windows XP - SP2 (nomachine's client) (AVG anti-virus is running)
sp2 ????

If this doesn't work, next we may need to check you aren't connecting
via the LAN instead of the ssh tunnel.

What firewall restrictions are there on the Windows Workstation
regarding the MS File/Print Server process with cifs ?

Can localhost connect ?????

> > Thanks, > VIvek > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > >http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ> > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/> > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx> ________________________________________________________________
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

place entries instead of shortcuts (like ctrl+alt+t) in the kde-menu

2009-11-25T08:11:04Z

Hi !

Is it possible to place entries in the kde-menu instead of using shortcuts
like
ctrl + alt + t (strg + alt + t)
ctrl + alt + f (strg + alt + f)

?

Bye
Olaf
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Printing and sharing issue

2009-11-25T04:30:39Z

Hi,

apparmour is not running...

Thanks,
Vivek

Marcelo Boveto Shima wrote:

> Hi,
>
> Maybe apparmour is blocking the connection.
> Try deactivating it and test.
>
> Regards,
> Marcelo
>
> On Tue, Nov 24, 2009 at 12:40 PM, Vivek <vivek@...> wrote:
>
>> Hello Chris,
>>
>> Thanks for your reply.
>>
>> I have patched the /usr/lib/cups/backend/nxsmb script that you had
>> mentioned.
>>
>> and set SAMBA_MOUNT_SHARE_PROTOCOL="cifs" or
>> SAMBA_MOUNT_SHARE_PROTOCOL="both" , printing is not working but file-sharing
>> is working fine.
>>
>> On the nxsession,
>>
>> printer device uri = nxsmb://127.0.0.1:4000/cifs/HP
>>
>> After clicking the 'Printing Test Page', the following process were
>> starting,
>>
>> #ps aux|grep cups
>> vivek 6594 0.0 0.0 5416 2364 ? S< 18:52 0:00 HP 1 vivek
>> Test Page 1 job-uuid=urn:uuid:ca694775-8e64-3257-7f56-1e3b843f57bc
>> /home/vivek/.nx/C-tsrv-co-1000-0394C5E4B62F543CFCFF0D1434A8C5BE/cups/spool/d00001-001
>> vivek 6595 0.0 0.0 8376 2560 ? S< 18:52 0:00
>> /usr/lib/cups/backend//smb 1 vivek Test Page 1
>> job-uuid=urn:uuid:ca694775-8e64-3257-7f56-1e3b843f57bc
>>
>> In the ~home/.nx/C-SESSIONID/cups/error_log,
>>
>> E [24/Nov/2009:19:07:27 +0530] [Job 1] Connection failed:
>> NT_STATUS_BAD_NETWORK_NAME
>> E [24/Nov/2009:19:07:27 +0530] [Job 1] Unable to connect to CIFS host, will
>> retry in 60 seconds...
>>
>> but we are able to ping the windows client from Ubuntu server using
>> hostname.
>>
>> Server - Ubuntu 9.04
>> Client - Windows XP - SP2 (nomachine's client) (AVG anti-virus is running)
>>
>> Thanks,
>> VIvek
>>
>> chris@... wrote:
>>
>> Vivek <vivek@...> wrote on 17/11/2009 14:10:58:
>>
>>
>>> Hi All,
>>>
>>> If any of you is using both printer and file sharing feature on
>>> Windows client, please share your configurations here..
>>>
>>> I am using,
>>>
>>> Server - Ubuntu 9.04
>>> Client - Windows XP professional
>>>
>> Uses cifs by default.
>>
>>
>>
>>> ~vivek
>>>
>>> Vivek wrote:
>>> Hi,
>>>
>>> Server - Ubuntu 9.04
>>> Client - Windows
>>>
>>> I am not able to use both printing and mounting at a time. If
>>> SAMBA_MOUNT_SHARE_PROTOCOL="smbfs",
>>>
>> If you like. Both would be better.
>>
>>
>>> Printing works. But unable to mount windows shares. Error " failed
>>> to mount. mount error. error(112) Host is down ".
>>>
>>> If SAMBA_MOUNT_SHARE_PROTOCOL="both" or
>>> SAMBA_MOUNT_SHARE_PROTOCOL="cifs", we are unable to mount the
>>>
>> With XP both=cifs
>>
>>
>>
>>> windows sharing. but printing not works..
>>>
>> I think we need to guess you meant the mount works but printing doesn't.
>>
>>
>> Did you patch /usr/lib/cups/backend/nxsmb ??
>>
>>
>> --- /usr/lib/cups/backend/nxsmb 2009-10-03 16:26:24.000000000 +0100
>> +++ /usr/lib/cups/backend/nxsmb.patched 2009-10-03 17:22:54.000000000 +0100
>> @@ -18,6 +18,9 @@
>> PROTOCOL=$(echo $DEVICE_URI | cut -d/ -f4)
>> PRINTER=$(echo $DEVICE_URI | cut -d/ -f5)
>>
>> +## patch to rewrite nxsmb:// as smb:// to make it acceptable to smbspool
>> +DEVICE_URI=$(echo $DEVICE_URI | sed "s|nxsmb://|smb://|g" )
>> +
>> if [ -z "$PRINTER" ] # old style setup
>> then
>> echo "Warning: Not using nxredir library. The DEVICE_URI is not in
>> the right format."
>>
>>
>>
>>
>>
>>> In the /home/user/.nx/C-**/cups/error_log, " unable to connect cifs
>>> host, will try in 60 seconds ".
>>>
>>> Is any workaround there ?
>>>
>>> Thanks in advance.
>>>
>>> Regards,
>>> Vivek
>>>
>>>
>>> ________________________________________________________________
>>> Were you helped on this list with your FreeNX problem?
>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>>
>>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>>
>>> Don't forget to check the NX Knowledge Base:
>>> http://www.nomachine.com/kb/
>>>
>>> ________________________________________________________________
>>> FreeNX-kNX mailing list --- FreeNX-kNX@...
>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>> ________________________________________________________________
>>> ________________________________________________________________
>>> Were you helped on this list with your FreeNX problem?
>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>>
>>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>>
>>> Don't forget to check the NX Knowledge Base:
>>> http://www.nomachine.com/kb/
>>>
>>> ________________________________________________________________
>>> FreeNX-kNX mailing list --- FreeNX-kNX@...
>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>> ________________________________________________________________
>>>
>> ________________________________
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>> FreeNX-kNX mailing list --- FreeNX-kNX@...
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>> FreeNX-kNX mailing list --- FreeNX-kNX@...
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
>>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@...
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
>
>

Re: Printing and sharing issue

2009-11-24T07:44:09Z

Hi,

Maybe apparmour is blocking the connection.
Try deactivating it and test.

Regards,
Marcelo

On Tue, Nov 24, 2009 at 12:40 PM, Vivek <vivek@...> wrote:

> Hello Chris,
>
> Thanks for your reply.
>
> I have patched the /usr/lib/cups/backend/nxsmb script that you had
> mentioned.
>
> and set SAMBA_MOUNT_SHARE_PROTOCOL="cifs" or
> SAMBA_MOUNT_SHARE_PROTOCOL="both" , printing is not working but file-sharing
> is working fine.
>
> On the nxsession,
>
> printer device uri = nxsmb://127.0.0.1:4000/cifs/HP
>
> After clicking the 'Printing Test Page', the following process were
> starting,
>
> #ps aux|grep cups
> vivek 6594 0.0 0.0 5416 2364 ? S< 18:52 0:00 HP 1 vivek
> Test Page 1 job-uuid=urn:uuid:ca694775-8e64-3257-7f56-1e3b843f57bc
> /home/vivek/.nx/C-tsrv-co-1000-0394C5E4B62F543CFCFF0D1434A8C5BE/cups/spool/d00001-001
> vivek 6595 0.0 0.0 8376 2560 ? S< 18:52 0:00
> /usr/lib/cups/backend//smb 1 vivek Test Page 1
> job-uuid=urn:uuid:ca694775-8e64-3257-7f56-1e3b843f57bc
>
> In the ~home/.nx/C-SESSIONID/cups/error_log,
>
> E [24/Nov/2009:19:07:27 +0530] [Job 1] Connection failed:
> NT_STATUS_BAD_NETWORK_NAME
> E [24/Nov/2009:19:07:27 +0530] [Job 1] Unable to connect to CIFS host, will
> retry in 60 seconds...
>
> but we are able to ping the windows client from Ubuntu server using
> hostname.
>
> Server - Ubuntu 9.04
> Client - Windows XP - SP2 (nomachine's client) (AVG anti-virus is running)
>
> Thanks,
> VIvek
>
> chris@... wrote:
>
> Vivek <vivek@...> wrote on 17/11/2009 14:10:58:
>
>> Hi All,
>>
>> If any of you is using both printer and file sharing feature on
>> Windows client, please share your configurations here..
>>
>> I am using,
>>
>> Server - Ubuntu 9.04
>> Client - Windows XP professional
>
> Uses cifs by default.
>
>
>>
>>
>> ~vivek
>>
>> Vivek wrote:
>> Hi,
>>
>> Server - Ubuntu 9.04
>> Client - Windows
>>
>> I am not able to use both printing and mounting at a time. If
>> SAMBA_MOUNT_SHARE_PROTOCOL="smbfs",
>
> If you like. Both would be better.
>
>>
>> Printing works. But unable to mount windows shares. Error " failed
>> to mount. mount error. error(112) Host is down ".
>>
>> If SAMBA_MOUNT_SHARE_PROTOCOL="both" or
>> SAMBA_MOUNT_SHARE_PROTOCOL="cifs", we are unable to mount the
>
> With XP both=cifs
>
>
>> windows sharing. but printing not works..
>
>
> I think we need to guess you meant the mount works but printing doesn't.
>
>
> Did you patch /usr/lib/cups/backend/nxsmb ??
>
>
> --- /usr/lib/cups/backend/nxsmb 2009-10-03 16:26:24.000000000 +0100
> +++ /usr/lib/cups/backend/nxsmb.patched 2009-10-03 17:22:54.000000000 +0100
> @@ -18,6 +18,9 @@
> PROTOCOL=$(echo $DEVICE_URI | cut -d/ -f4)
> PRINTER=$(echo $DEVICE_URI | cut -d/ -f5)
>
> +## patch to rewrite nxsmb:// as smb:// to make it acceptable to smbspool
> +DEVICE_URI=$(echo $DEVICE_URI | sed "s|nxsmb://|smb://|g" )
> +
> if [ -z "$PRINTER" ] # old style setup
> then
> echo "Warning: Not using nxredir library. The DEVICE_URI is not in
> the right format."
>
>
>
>
>>
>> In the /home/user/.nx/C-**/cups/error_log, " unable to connect cifs
>> host, will try in 60 seconds ".
>>
>> Is any workaround there ?
>>
>> Thanks in advance.
>>
>> Regards,
>> Vivek
>>
>>
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>> FreeNX-kNX mailing list --- FreeNX-kNX@...
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>
>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>>
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>> FreeNX-kNX mailing list --- FreeNX-kNX@...
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>
> ________________________________
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@...
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@...
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>

Re: Printing and sharing issue

2009-11-24T06:40:19Z

Hello Chris,

Thanks for your reply.

I have patched the /usr/lib/cups/backend/nxsmb script that you had mentioned.

and set SAMBA_MOUNT_SHARE_PROTOCOL="cifs" or SAMBA_MOUNT_SHARE_PROTOCOL="both" , printing is not working but file-sharing is working fine.

On the nxsession,

printer device uri = nxsmb://127.0.0.1:4000/cifs/HP

After clicking the 'Printing Test Page', the following process were starting,

#ps aux|grep cups
vivek 6594 0.0 0.0 5416 2364 ? S< 18:52 0:00 HP 1 vivek Test Page 1 job-uuid=urn:uuid:ca694775-8e64-3257-7f56-1e3b843f57bc /home/vivek/.nx/C-tsrv-co-1000-0394C5E4B62F543CFCFF0D1434A8C5BE/cups/spool/d00001-001
vivek 6595 0.0 0.0 8376 2560 ? S< 18:52 0:00 /usr/lib/cups/backend//smb 1 vivek Test Page 1 job-uuid=urn:uuid:ca694775-8e64-3257-7f56-1e3b843f57bc

In the ~home/.nx/C-SESSIONID/cups/error_log,

E [24/Nov/2009:19:07:27 +0530] [Job 1] Connection failed: NT_STATUS_BAD_NETWORK_NAME
E [24/Nov/2009:19:07:27 +0530] [Job 1] Unable to connect to CIFS host, will retry in 60 seconds...

but we are able to ping the windows client from Ubuntu server using hostname.

Server - Ubuntu 9.04
Client - Windows XP - SP2 (nomachine's client) (AVG anti-virus is running)

Thanks,
VIvek

chris@... wrote:

Vivek vivek@... wrote on 17/11/2009 14:10:58: > Hi All, > > If any of you is using both printer and file sharing feature on > Windows client, please share your configurations here.. > > I am using, > > Server - Ubuntu 9.04 > Client - Windows XP professional

Uses cifs by default.

> > > ~vivek > > Vivek wrote:
> Hi, > > Server - Ubuntu 9.04 > Client - Windows > > I am not able to use both printing and mounting at a time. If > SAMBA_MOUNT_SHARE_PROTOCOL="smbfs",
If you like. Both would be better.

> > Printing works. But unable to mount windows shares. Error " failed > to mount. mount error. error(112) Host is down ". > > If SAMBA_MOUNT_SHARE_PROTOCOL="both" or > SAMBA_MOUNT_SHARE_PROTOCOL="cifs", we are unable to mount the
With XP both=cifs

> windows sharing. but printing not works..

I think we need to guess you meant the mount works but printing doesn't.

Did you patch /usr/lib/cups/backend/nxsmb ??

--- /usr/lib/cups/backend/nxsmb 2009-10-03 16:26:24.000000000 +0100
+++ /usr/lib/cups/backend/nxsmb.patched 2009-10-03 17:22:54.000000000 +0100
@@ -18,6 +18,9 @@
PROTOCOL=$(echo $DEVICE_URI | cut -d/ -f4)
PRINTER=$(echo $DEVICE_URI | cut -d/ -f5)

+## patch to rewrite nxsmb:// as smb:// to make it acceptable to smbspool
+DEVICE_URI=$(echo $DEVICE_URI | sed "s|nxsmb://|smb://|g" )
+
if [ -z "$PRINTER" ] # old style setup
then
echo "Warning: Not using nxredir library. The DEVICE_URI is not in the right format."

> > In the /home/user/.nx/C-**/cups/error_log, " unable to connect cifs > host, will try in 60 seconds ". > > Is any workaround there ? > > Thanks in advance. > > Regards, > Vivek
> > > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > >http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ> > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/> > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx> ________________________________________________________________ > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > >http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ> > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/> > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx> ________________________________________________________________
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
  
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX@...
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Force new NX Session without getting the Session Chooser

2009-11-24T01:30:10Z

Hi,

I am interested in forcing a new session for a user by just changing the session file. So even when a user has connected and working sessions I want to create a session file to force a new session without getting the session chooser (where you than also can reconnect old sessions)

I checked the source of nxserver but I haven't found anything there to allow such a behavior. Does anyone knows if this is possible or of this could be patched in the source and if so maybe even how?

Cheers,
Florian

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Arch Linux - After reboot have to login 4 times to work ????? (every single time)

2009-11-23T09:29:55Z

Hi.

This issue has been going on for at least 4-6 months now...

I am running latest freenx on archlinux (686)

It works absolutely fine, until I reboot.

Then every single time I have to try to login (and fail) 3 times, then on the 4th login to works, then anyone can login - freenx will then be 100% fine until the next reboot.

Can anyone think of ANYTHING I can do to stop this happening ??? It is really annoying,

I did raise a post about this several months ago, I followed advice at the end, it still happens.

(old post : http://markmail.org/message/44j3xah7v6hzlezv )

Here is an example fail.

====================================
Display Type Session ID Options Depth Screen Status Session Name
------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------

NX> 148 Server capacity: not reached for user: yossarian
NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="Gateway" --type="unix-kde" --geometry="1280x976" --client="linux" --keyboard="pc105/gb" --screeninfo="1280x976x24+render"

NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 700 Session id: gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE
NX> 705 Session display: 1000
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 8b4424fcb9928f98bad143bae200b63b
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 8b4424fcb9928f98bad143bae200b63b
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 1
NX> 105 /opt/NX/bin/nxserver: line 1531: 2161 Terminated sleep $AGENT_STARTUP_TIMEOUT
NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/yossarian/.nx/F-C-gtfo-1000-ED28A41DC35814F52C6DE05FDE72D8AE/session". You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent to test the basic functionality. Session log follows:
Can't open /opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}: No such file or directory.
mv: cannot stat `/opt/NX/var/db/running/sessionId{ED28A41DC35814F52C6DE05FDE72D8AE}': No such file or directory
NX> 1006 Session status: closed
NX> 280 Exiting on signal: 15

====================================

Re: Some problems with my FreeNX configuration

2009-11-22T09:47:02Z

Alain Lemerre <alain.lemerre@...> wrote on 21/11/2009 08:37:05:

> Hi,
>
> For the problem of launching OpenOffice on the server screen.
>
> The problem occurs if OpenOffice if already running in the session
> on the server.
>
You will get SOME issues if the SAME user logs in to two sessions.

This is mainly to do with two sessions trying to control config files
caches, or trying to re-open a file from a previous session which
is actually still running.

Mostly you won't notice, but bear in mind that quite a bit of software
expects only to be run in one instance (for each particular user).

> For example, I open a session on the server with my account, I
> launched OpenOffice. From a laptop with NX client and the same
> account, I open a OpenOffice session: the OpenOffice window opens on

Hmmm, well . . .

> the server. I close all OpenOffice sessions and this time the
> OpenOffice displays on the laptop.

Right

>
> Regards,
>

> 2009/11/20 Alain Lemerre <alain.lemerre@...>
> Hi,
>
> I followed your advice:

My advice was to use 0.7.3 ;--)

>
> I don't have error message. But the first time I launch swriter it
> works. But the next launches, swriter main Window display on the
> screen of the server.
>

?? You mean two remote sessions and the second appears on the server console ??

Please explain a little more fully if this is different from above.

>
> I don't want to go back to 0.7.3 librairies because I want to
> benefit from Marcelo Boveto Shima patches. I used before 0.7.4
> without problems.

Oh. Did something break ???

And what difference is there between this time and before ??

>
> Regards
>

For ye record, OOTB FreeNX 0.7.3 puts "libXrender.so.1.2" in

APPLICATION_LIBRARY_PRELOAD

Which means that newer versions of the libraries have to put a link in
from all previous subversions to the latest (sub)version

ie. libXrender.so -> libXrender.so.1.2.2 # good
libXrender.so.1 -> libXrender.so.1.2.2 #good
libXrender.so.1.2 -> libXrender.so.1.2.2 # oh-oh, not a soname

rather than ( more properly ) the soname, else there will be a missing library.

Presumably FreeNX functionality was dependent upon the differences between
libXrender.so.1 and libXrender.so.1.2

Now normally, the difference from lib.so.1 to lib.so.1.1 should be just a bug
fix rather than a version change (based on interface/functionality.)

If lib.so.3 won't replace lib.so.2 then lib.so.2 needs to be kept despite version
changes,

The config checker can of course check for subversions, and helpfully tell
you that you need to upgrade your library, but it shouldn't demand a specific
file name.
ie.
you can demand lib.so.1.2 or above, but you shouldn't bail out if
lib.so.1.3 exists instead of lib.so.1.2.

If your code will only work with unsupported lib.so.1.2 then you and
your userbase have a problem until you can either manage your own
out of date libraries or bring your code up to date with the latest library

This means that a happier practice is to demand

lib.so.x
rather than

lib.so.x.y
which means you only need links from

lib.so.x -> lib.so.latest.subversion
not lots of links all over the show

lib.so.x -> lib.so.latest.subversion
lib.so.x.1 -> lib.so.latest.subversion
lib.so.x.1.1 -> lib.so.latest.subversion
lib.so.x.1.2 -> lib.so.latest.subversion

And ironically, FreeNX's version of the libraries, NX4U.tar.gz
follows this more correct practice, presumably straight from
NoMachine and doesn't have the link, so won't work
out of the box with freenx-server-0.7.3.tar.gz

-rwxr-xr-x ff/users 10192 2008-04-02 16:08 NX4U/lib/libXrandr.so.2.0
lrwxrwxrwx ff/users 0 2008-08-23 13:11 NX4U/lib/libXrender.so -> libXrender.so.1.2.2
lrwxrwxrwx ff/users 0 2008-08-23 13:11 NX4U/lib/libXrender.so.1 -> libXrender.so.1.2.2
-rwxr-xr-x ff/users 32000 2008-04-02 16:08 NX4U/lib/libXrender.so.1.2.2

Checking a couple of distros, which I've been looking at recently

Opensuse FreeNX-0.7.3-4.1.src.rpm and
fedora freenx-server-0.7.3-15.fc11.i586.rpm

both changed their APPLICATION_LIBRARY_PRELOAD
to libXrender.so.1, whereas the ubuntu one I looked at

freenx-server_0.7.3+teambzr104-0ubuntu1~karmic1_i386.deb

didn't and kept libXrender.so.1.2, presumably they changed their
version of NoMachines libraries.

There isn't much consistency between distros as to where the librarys
are kept either, but of course thats pure distro stuff !!!

Shows how dependent we are on the distros to test things.

Anyway, I expect Fabian et al. put their lives on hold writing all this stuff
so I hope everyone is duly grateful.

Alain, all your libraries seem to be in /usr/NX/lib

This is the default for the Nomachine client, so you
may find an issue over libXcomp.so which is in both
the Server and Client Libraries.

and

I notice that your libX11.so.6.2 & libXrender.so.1.2.2 are both
10 x the size of mine from Suse!!

-rwxr-xr-x 1 root root 10172494 2009-11-11 14:00 libX11.so.6.2*
-rwxr-xr-x 1 root root 406531 2009-11-11 14:03 libXrender.so.1.2.2*
vs
-rwxr-xr-x 1 root root 1158270 2009-05-29 16:46 libX11.so.6.2
-rwxr-xr-x 1 root root 42998 2009-05-29 16:47 libXrender.so.1.2.2

Where did you get your libraries from ?? You compiled them I suppose.
Did you strip them, or are you busy debugging ??

> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@...
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Some problems with my FreeNX configuration

2009-11-21T00:37:05Z

Hi,

For the problem of launching OpenOffice on the server screen.

The problem occurs if OpenOffice if already running in the session on the server.

For example, I open a session on the server with my account, I launched OpenOffice. From a laptop with NX client and the same account, I open a OpenOffice session: the OpenOffice window opens on the server. I close all OpenOffice sessions and this time the OpenOffice displays on the laptop.

Regards,

2009/11/20 Alain Lemerre <alain.lemerre@...>

Hi,

I followed your advice:

total 12072
drwxr-xr-x 2 root root     4096 2009-11-20 23:35 ./
drwxr-xr-x 7 root root     4096 2009-11-12 06:45 ../
lrwxrwxrwx 1 root root       13 2009-11-11 14:16 libX11.so -> libX11.so.6.2*
lrwxrwxrwx 1 root root       13 2009-11-11 14:16 libX11.so.6 -> libX11.so.6.2*
-rwxr-xr-x 1 root root 10172494 2009-11-11 14:00 libX11.so.6.2*
lrwxrwxrwx 1 root root       17 2009-11-11 14:17 libXcomp.so -> libXcomp.so.3.4.0*
lrwxrwxrwx 1 root root       17 2009-11-11 14:17 libXcomp.so.3 -> libXcomp.so.3.4.0*
-rwxr-xr-x 1 root root 1086485 2009-11-11 13:53 libXcomp.so.3.4.0*
lrwxrwxrwx 1 root root       20 2009-11-11 14:17 libXcompext.so -> libXcompext.so.3.4.0*
lrwxrwxrwx 1 root root       20 2009-11-11 14:17 libXcompext.so.3 -> libXcompext.so.3.4.0*
-rwxr-xr-x 1 root root    65871 2009-11-11 14:00 libXcompext.so.3.4.0*
lrwxrwxrwx 1 root root       21 2009-11-11 14:17 libXcompshad.so -> libXcompshad.so.3.4.0*
lrwxrwxrwx 1 root root       21 2009-11-11 14:17 libXcompshad.so.3 -> libXcompshad.so.3.4.0*
-rwxr-xr-x 1 root root    54856 2009-11-11 14:06 libXcompshad.so.3.4.0*
lrwxrwxrwx 1 root root       14 2009-11-11 14:16 libXext.so -> libXext.so.6.4*
lrwxrwxrwx 1 root root       14 2009-11-11 14:16 libXext.so.6 -> libXext.so.6.4*
-rwxr-xr-x 1 root root   542333 2009-11-11 14:01 libXext.so.6.4*
lrwxrwxrwx 1 root root       19 2009-11-11 14:16 libXrender.so -> libXrender.so.1.2.2*
lrwxrwxrwx 1 root root       19 2009-11-11 14:16 libXrender.so.1 -> libXrender.so.1.2.2*
lrwxrwxrwx 1 root root       19 2009-11-20 23:35 libXrender.so.1.2 -> libXrender.so.1.2.2*
-rwxr-xr-x 1 root root   406531 2009-11-11 14:03 libXrender.so.1.2.2*
-rwxr-xr-x 1 root root     7674 2009-11-12 06:43 libnxredir.so.0*

I don't have error message. But the first time I launch swriter it works. But the next launches, swriter main Window display on the screen of the server.

I don't want to go back to 0.7.3 librairies because I want to benefit from Marcelo Boveto Shima patches. I used before 0.7.4 without problems.

Regards

2009/11/20 chris burton <ccburton2004@...>

From: Alain Lemerre <alain.lemerre@...>
To: User Support for FreeNX Server and kNX Client <freenx-knx@...>
Sent: Fri, 20 November, 2009 6:20:50
Subject: [FreeNX-kNX] Some problems with my FreeNX configuration

>My configuration: Slackware 13.0 FreeNX SVN 0.7.4

SVN. You expect it to just work ???

>First of all, when I do a "nxloadconfig --check" I get this input:

>Warning: Invalid value "APPLICATION_LIBRARY_PRELOAD=
>/usr/NX/lib/libX11.so.6.2:
>/usr/NX/lib/libXext.so.6.4:
>/usr/NX/lib/libXcomp.so:
>/usr/NX/lib/libXcompext.so:
>/usr/NX/lib/libXrender.so.1.2"

>. /usr/NX/lib/libXrender.so.1.2 could not be found.

Yup Seems clear enough !!

>Users will not be able to run a single application in non-rootless mode.

>In my /usr/NX/lib directory the following libs are installed:
>libX11.so@          libXcompext.so.3@       libXext.so.6.4*
>libX11.so.6@        libXcompext.so.3.4.0*   libXrender.so@
>libX11.so.6.2*      libXcompshad.so@        libXrender.so.1@
>libXcomp.so@        libXcompshad.so.3@      libXrender.so.1.2.2*

Can you see libXrender.so.1.2 here ???

>libXcomp.so.3@      libXcompshad.so.3.4.0* libnxredir.so.0*
>libXcomp.so.3.4.0* libXext.so@
>libXcompext.so@     libXext.so.6@

Try as "root"

cd /usr/NX/lib

ln -s /libXrender.so.1.2 libXrender.so.1.2.2

That might get rid of the error message and it might work, thoigh you seem to be out of phase with your libraries

If it doesn't work try adding : -

ln -s /libXrender.so libXrender.so.1.2.2

You would be better using 0.7.3 though I think !!

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: resize (screen resolution) a resumed session

2009-11-20T22:50:31Z

Hi

Nobody has any idea?

Where are the shortcuts (like strg+alt+f, strg+alt+t) configure, where
are they saved, at which place and software? Freenx, nomachine-client,
or kde, or somewhere else?

Bye
Olaf

Sent from iPhone

Am 13.11.2009 um 17:19 schrieb olaf <olaf-linux@...>:

> Hi !
>
> Resume a suspend 1280x1024 session on an other computer with
> installed OS +
> nxClient-software and a screen with 1024x768 will show me only a
> snippet/cut-
> out of the 1280x1024.
> In this case strg+alt+f resize the nx-session-window and set the
> resolution
> to 1024x768 (or other wishes).
>
> But how can I do this on a real thinclient, which is booting over
> pxe in a
> full-screen-mode? (pxe -> thinstation-image -> nxclient )
> strg+alt+f does not work there, so I can not resize the session.
>
> Bye
> Olaf
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@...
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________

Re: Some problems with my FreeNX configuration

2009-11-20T14:54:32Z

Hi,

I followed your advice:

total 12072
drwxr-xr-x 2 root root     4096 2009-11-20 23:35 ./
drwxr-xr-x 7 root root     4096 2009-11-12 06:45 ../
lrwxrwxrwx 1 root root       13 2009-11-11 14:16 libX11.so -> libX11.so.6.2*
lrwxrwxrwx 1 root root       13 2009-11-11 14:16 libX11.so.6 -> libX11.so.6.2*
-rwxr-xr-x 1 root root 10172494 2009-11-11 14:00 libX11.so.6.2*
lrwxrwxrwx 1 root root       17 2009-11-11 14:17 libXcomp.so -> libXcomp.so.3.4.0*
lrwxrwxrwx 1 root root       17 2009-11-11 14:17 libXcomp.so.3 -> libXcomp.so.3.4.0*
-rwxr-xr-x 1 root root 1086485 2009-11-11 13:53 libXcomp.so.3.4.0*
lrwxrwxrwx 1 root root       20 2009-11-11 14:17 libXcompext.so -> libXcompext.so.3.4.0*
lrwxrwxrwx 1 root root       20 2009-11-11 14:17 libXcompext.so.3 -> libXcompext.so.3.4.0*
-rwxr-xr-x 1 root root    65871 2009-11-11 14:00 libXcompext.so.3.4.0*
lrwxrwxrwx 1 root root       21 2009-11-11 14:17 libXcompshad.so -> libXcompshad.so.3.4.0*
lrwxrwxrwx 1 root root       21 2009-11-11 14:17 libXcompshad.so.3 -> libXcompshad.so.3.4.0*
-rwxr-xr-x 1 root root    54856 2009-11-11 14:06 libXcompshad.so.3.4.0*
lrwxrwxrwx 1 root root       14 2009-11-11 14:16 libXext.so -> libXext.so.6.4*
lrwxrwxrwx 1 root root       14 2009-11-11 14:16 libXext.so.6 -> libXext.so.6.4*
-rwxr-xr-x 1 root root   542333 2009-11-11 14:01 libXext.so.6.4*
lrwxrwxrwx 1 root root       19 2009-11-11 14:16 libXrender.so -> libXrender.so.1.2.2*
lrwxrwxrwx 1 root root       19 2009-11-11 14:16 libXrender.so.1 -> libXrender.so.1.2.2*
lrwxrwxrwx 1 root root       19 2009-11-20 23:35 libXrender.so.1.2 -> libXrender.so.1.2.2*
-rwxr-xr-x 1 root root   406531 2009-11-11 14:03 libXrender.so.1.2.2*
-rwxr-xr-x 1 root root     7674 2009-11-12 06:43 libnxredir.so.0*

I don't have error message. But the first time I launch swriter it works. But the next launches, swriter main Window display on the screen of the server.

I don't want to go back to 0.7.3 librairies because I want to benefit from Marcelo Boveto Shima patches. I used before 0.7.4 without problems.

Regards

2009/11/20 chris burton <ccburton2004@...>

From: Alain Lemerre <alain.lemerre@...>
To: User Support for FreeNX Server and kNX Client <freenx-knx@...>
Sent: Fri, 20 November, 2009 6:20:50
Subject: [FreeNX-kNX] Some problems with my FreeNX configuration

>My configuration: Slackware 13.0 FreeNX SVN 0.7.4

SVN. You expect it to just work ???

>First of all, when I do a "nxloadconfig --check" I get this input:

>Warning: Invalid value "APPLICATION_LIBRARY_PRELOAD=
>/usr/NX/lib/libX11.so.6.2:
>/usr/NX/lib/libXext.so.6.4:
>/usr/NX/lib/libXcomp.so:
>/usr/NX/lib/libXcompext.so:
>/usr/NX/lib/libXrender.so.1.2"

>. /usr/NX/lib/libXrender.so.1.2 could not be found.

Yup Seems clear enough !!

>Users will not be able to run a single application in non-rootless mode.

>In my /usr/NX/lib directory the following libs are installed:
>libX11.so@          libXcompext.so.3@       libXext.so.6.4*
>libX11.so.6@        libXcompext.so.3.4.0*   libXrender.so@
>libX11.so.6.2*      libXcompshad.so@        libXrender.so.1@
>libXcomp.so@        libXcompshad.so.3@      libXrender.so.1.2.2*

Can you see libXrender.so.1.2 here ???

>libXcomp.so.3@      libXcompshad.so.3.4.0* libnxredir.so.0*
>libXcomp.so.3.4.0* libXext.so@
>libXcompext.so@     libXext.so.6@

Try as "root"

cd /usr/NX/lib

ln -s /libXrender.so.1.2 libXrender.so.1.2.2

That might get rid of the error message and it might work, thoigh you seem to be out of phase with your libraries

If it doesn't work try adding : -

ln -s /libXrender.so libXrender.so.1.2.2

You would be better using 0.7.3 though I think !!

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

FreeNX and PulseAudio on Ubuntu

2009-11-20T08:45:46Z

Traditionally the node.conf file was setup to use ESD sound in linux.

However, in Ubuntu the default is now PulseAudio. Although PulseAudio
is supposed to be a drop in replacement for ESD I'm wondering what differences in
configuration of FREENX may need to be done.

For instance in NODE.CONF

# FreeNX with ENABLE_ESD_PRELOAD="1" will automatically try to setup

# the sound with the help of the esd media helper.

# Currently ESD will be used just by the Windows NX Client.

# Be sure that $ESD_BIN_PRELOAD is in your path, does exist and work

# before enabling this directive.

ENABLE_ESD_PRELOAD="1"

ESD_BIN_PRELOAD="esddsp"

FreeNX and PulseAudio on Ubuntu

2009-11-20T08:30:08Z

# FreeNX with ENABLE_ESD_PRELOAD="1" will automatically try to setup

# the sound with the help of the esd media helper.

# Currently ESD will be used just by the Windows NX Client.

# Be sure that $ESD_BIN_PRELOAD is in your path, does exist and work

# before enabling this directive.

ENABLE_ESD_PRELOAD="1"

ESD_BIN_PRELOAD="esddsp"

Should I be substituing "esddsp" with "padsp" for PulseAudio?

ESD_BIN_PRELOAD="padsp"

I've also tried to follow some of the writeups for the "perfect pulseaudio" setup to go along with
this but I am curious how others do it.

Brian

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Some problems with my FreeNX configuration

2009-11-20T04:36:16Z

From: Alain Lemerre <alain.lemerre@...> To: User Support for FreeNX Server and kNX Client <freenx-knx@...> Sent: Fri, 20 November, 2009 6:20:50 Subject: [FreeNX-kNX] Some problems with my FreeNX configuration
>My configuration: Slackware 13.0 FreeNX SVN 0.7.4 SVN. You expect it to just work ??? >First of all, when I do a "nxloadconfig --check" I get this input: >Warning: Invalid value "APPLICATION_LIBRARY_PRELOAD= >/usr/NX/lib/libX11.so.6.2: >/usr/NX/lib/libXext.so.6.4: >/usr/NX/lib/libXcomp.so: >/usr/NX/lib/libXcompext.so: >/usr/NX/lib/libXrender.so.1.2" >. /usr/NX/lib/libXrender.so.1.2 could not be found. Yup Seems clear enough !! >Users will not be able to run a single application in non-rootless mode. >In my /usr/NX/lib directory the following libs are installed: >libX11.so@ libXcompext.so.3@ libXext.so.6.4* >libX11.so.6@ libXcompext.so.3.4.0* libXrender.so@ >libX11.so.6.2* libXcompshad.so@ libXrender.so.1@ >libXcomp.so@ libXcompshad.so.3@ libXrender.so.1.2.2* Can you see libXrender.so.1.2 here ??? >libXcomp.so.3@ libXcompshad.so.3.4.0* libnxredir.so.0* >libXcomp.so.3.4.0* libXext.so@ >libXcompext.so@ libXext.so.6@ Try as "root" cd /usr/NX/lib ln -s /libXrender.so.1.2 libXrender.so.1.2.2 That might get rid of the error message and it might work, thoigh you seem to be out of phase with your libraries If it doesn't work try adding : - ln -s /libXrender.so libXrender.so.1.2.2 You would be better using 0.7.3 though I think !!
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Printing and sharing issue

2009-11-20T04:19:24Z

Vivek <vivek@...> wrote on 17/11/2009 14:10:58: > Hi All, > > If any of you is using both printer and file sharing feature on > Windows client, please share your configurations here.. > > I am using, > > Server - Ubuntu 9.04 > Client - Windows XP professional

Uses cifs by default.

> > > ~vivek > > Vivek wrote:
> Hi, > > Server - Ubuntu 9.04 > Client - Windows > > I am not able to use both printing and mounting at a time. If > SAMBA_MOUNT_SHARE_PROTOCOL="smbfs",
If you like. Both would be better.

> > Printing works. But unable to mount windows shares. Error " failed > to mount. mount error. error(112) Host is down ". > > If SAMBA_MOUNT_SHARE_PROTOCOL="both" or > SAMBA_MOUNT_SHARE_PROTOCOL="cifs", we are unable to mount the
With XP both=cifs

> windows sharing. but printing not works..

I think we need to guess you meant the mount works but printing doesn't.

Did you patch /usr/lib/cups/backend/nxsmb ??

--- /usr/lib/cups/backend/nxsmb 2009-10-03 16:26:24.000000000 +0100
+++ /usr/lib/cups/backend/nxsmb.patched 2009-10-03 17:22:54.000000000 +0100
@@ -18,6 +18,9 @@
PROTOCOL=$(echo $DEVICE_URI | cut -d/ -f4)
PRINTER=$(echo $DEVICE_URI | cut -d/ -f5)

+## patch to rewrite nxsmb:// as smb:// to make it acceptable to smbspool
+DEVICE_URI=$(echo $DEVICE_URI | sed "s|nxsmb://|smb://|g" )
+
if [ -z "$PRINTER" ] # old style setup
then
echo "Warning: Not using nxredir library. The DEVICE_URI is not in the right format."

> > In the /home/user/.nx/C-**/cups/error_log, " unable to connect cifs > host, will try in 60 seconds ". > > Is any workaround there ? > > Thanks in advance. > > Regards, > Vivek
> > > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > >http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ> > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/> > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx> ________________________________________________________________ > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > >http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ> > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/> > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx> ________________________________________________________________
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Re: Some problems with my FreeNX configuration

2009-11-20T04:04:33Z

From: Alain Lemerre <alain.lemerre@...>
To: User Support for FreeNX Server and kNX Client <freenx-knx@...>
Sent: Fri, 20 November, 2009 6:20:50
Subject: [FreeNX-kNX] Some problems with my FreeNX configuration

>My configuration: Slackware 13.0 FreeNX SVN 0.7.4

SVN. You expect it to just work ???

>First of all, when I do a "nxloadconfig --check" I get this input:

>Warning: Invalid value "APPLICATION_LIBRARY_PRELOAD=
>/usr/NX/lib/libX11.so.6.2:
>/usr/NX/lib/libXext.so.6.4:
>/usr/NX/lib/libXcomp.so:
>/usr/NX/lib/libXcompext.so:
>/usr/NX/lib/libXrender.so.1.2"

>. /usr/NX/lib/libXrender.so.1.2 could not be found.

Yup Seems clear enough !!

>Users will not be able to run a single application in non-rootless mode.

>In my /usr/NX/lib directory the following libs are installed:
>libX11.so@          libXcompext.so.3@       libXext.so.6.4*
>libX11.so.6@        libXcompext.so.3.4.0*   libXrender.so@
>libX11.so.6.2*      libXcompshad.so@        libXrender.so.1@
>libXcomp.so@        libXcompshad.so.3@      libXrender.so.1.2.2*

Can you see libXrender.so.1.2 here ???

>libXcomp.so.3@      libXcompshad.so.3.4.0* libnxredir.so.0*
>libXcomp.so.3.4.0* libXext.so@
>libXcompext.so@     libXext.so.6@

Try as "root"

cd /usr/NX/lib

ln -s /libXrender.so.1.2 libXrender.so.1.2.2

That might get rid of the error message and it might work, thoigh you seem to be out of phase with your libraries

If it doesn't work try adding : -

ln -s /libXrender.so libXrender.so.1.2.2

You would be better using 0.7.3 though I think !!

Re: Guest connections

2009-11-20T03:42:53Z

Most of the code is ready on the launchpad freenx-team bzr.
I already made it work with a modified version of gdm-guest-session.

Take a look at:
http://bazaar.launchpad.net/%7Efreenx-team/freenx-server/teambzr/revision/82
http://bazaar.launchpad.net/%7Efreenx-team/freenx-server/teambzr/revision/83
http://bazaar.launchpad.net/%7Efreenx-team/freenx-server/teambzr/revision/84

You should enable it:
ENABLE_GUEST_LOGIN="1"

Create a suid nxnode with the guest uid:
COMMAND_GUEST_LOGIN="/usr/lib/nx/guest/nxnode"

And create the script that starts the session:
COMMAND_GUEST_X_SESSION="/usr/share/gdm/guest-session/Xsession custom"

I think thats it. But not sure.

Hope this helps
Regards.

On Mon, Nov 16, 2009 at 6:33 AM, Alain Lemerre <alain.lemerre@...> wrote:

> Hi all,
>
> Does somebody knows if the guest connection mode (available in commercial
> Nomachine NX Server) is available in FreeNX?
>
> Regards,
>
> Alain
>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@...
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>

Re: Guest connections

2009-11-19T22:23:56Z

Thanks Steven,

I was talking about the check box "Login as a guest user" in the NX Client.

Are talking about the same thing?

Regards

2009/11/20 Steven James Drinnan <steven@...>

Probably possible,

I had a play with guest accounts,

1. I created a new user (guest) using the add user program
2. Changed the SE-Linux of that user to guest_r policy.
3. Removed the password that a had to enter (su passwd -d guest)

Now I had a guest account, but the policy does not allow for remote
connection. And from what I read this is preferable as enabling remote
access could lead attacks from outside. Even tried with a password.

The only way around it would be to create a new policy for SE_linux, but
that is beyond my knowledge.

Any others have an idea.

On Mon, 2009-11-16 at 09:33 +0100, Alain Lemerre wrote:
> Hi all,
>
> Does somebody knows if the guest connection mode (available in
> commercial Nomachine NX Server) is available in FreeNX?
>
> Regards,
>
> Alain

> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@...
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________

Some problems with my FreeNX configuration

2009-11-19T22:20:50Z

Hi everybody,

I am currently working to configure some applications for my users and I have some strange things.

My configuration: Slackware 13.0 FreeNX SVN 0.7.4 with Marcelo Boveto Shima patches. Lastest Nomachine components (3.4)

First of all, when I do a "nxloadconfig --check" I get this input:

Warning: Invalid value "APPLICATION_LIBRARY_PRELOAD=/usr/NX/lib/libX11.so.6.2:/usr/NX/lib/libXext.so.6.4:/usr/NX/lib/libXcomp.so:/usr/NX/lib/libXcompext.so:/usr/NX/lib/libXrender.so.1.2". /usr/NX/lib/libXrender.so.1.2 could not be found. Users will not be able to run a single application in non-rootless mode.

In my /usr/NX/lib directory the following libs are installed:
libX11.so@          libXcompext.so.3@       libXext.so.6.4*
libX11.so.6@        libXcompext.so.3.4.0*   libXrender.so@
libX11.so.6.2*      libXcompshad.so@        libXrender.so.1@
libXcomp.so@        libXcompshad.so.3@      libXrender.so.1.2.2*
libXcomp.so.3@      libXcompshad.so.3.4.0* libnxredir.so.0*
libXcomp.so.3.4.0* libXext.so@
libXcompext.so@     libXext.so.6@

1. If I lanch a full KDE Session, everything works fine

2. If I launch a GIMP session, it works fine except that the session doesn't close well and the NX Client get stuck to "connecting to GIMP". I need to launch the GIMP session a second time and it works.

3. If I launch a OpenOffice Swriter session, Open Office is displayed on the server display not on the client

Do you know if these 2 different problems are linked to the warning issued by nxloadconfig? Do you know any workaround?

Thanks a lot for your help.

Alain

________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/

________________________________________________________________
FreeNX-kNX mailing list --- FreeNX-kNX@...
https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________