opennx-devel Mailing List for OpenNX Client (Page 20)
Status: Beta
Brought to you by:
felfert
You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(6) |
Sep
(26) |
Oct
(9) |
Nov
(1) |
Dec
(2) |
2010 |
Jan
(7) |
Feb
(37) |
Mar
(16) |
Apr
(2) |
May
(3) |
Jun
(3) |
Jul
(5) |
Aug
(9) |
Sep
(2) |
Oct
(37) |
Nov
(5) |
Dec
|
2011 |
Jan
|
Feb
(23) |
Mar
(1) |
Apr
(2) |
May
(12) |
Jun
(3) |
Jul
(2) |
Aug
(20) |
Sep
(3) |
Oct
(3) |
Nov
(5) |
Dec
(15) |
2012 |
Jan
(34) |
Feb
(24) |
Mar
(18) |
Apr
(5) |
May
(2) |
Jun
(10) |
Jul
(11) |
Aug
(12) |
Sep
(12) |
Oct
(3) |
Nov
(5) |
Dec
(6) |
2013 |
Jan
(1) |
Feb
(3) |
Mar
(1) |
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(35) |
Sep
(2) |
Oct
(4) |
Nov
(4) |
Dec
(10) |
2014 |
Jan
(3) |
Feb
(6) |
Mar
|
Apr
(2) |
May
(6) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(8) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: SourceForge.net <no...@so...> - 2009-09-22 21:33:35
|
Bugs item #2864526, was opened at 2009-09-22 21:37 Message generated for change (Comment added) made by felfert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2864526&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Boris Savelev (bsavelev) Assigned to: Nobody/Anonymous (nobody) Summary: 100% load CPU with windows build Initial Comment: after pushing button "Login" process opennx.exe load 100% CPU for a 2-3 min. windows xp sp3. mingw32 linux build with gcc4.4. ---------------------------------------------------------------------- >Comment By: Fritz Elfert (felfert) Date: 2009-09-22 23:33 Message: Do you have made a debug-build (configure option --enable-debug)? If yes, then you can enable tracing by either setting the WXTRACE env variable or starting opennx with --trace=... (See opennx --help for the names of various trace tags). I suggest enabling at least MySession,MyIPC. Then *first* start either sysinternal's debugview or the include tracelog. After that, start opennx and reproduce the error. You should now see trace messages in the trace log, giving a hit about what is going on. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2864526&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-09-22 19:37:29
|
Bugs item #2864526, was opened at 2009-09-22 23:37 Message generated for change (Tracker Item Submitted) made by bsavelev You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2864526&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Boris Savelev (bsavelev) Assigned to: Nobody/Anonymous (nobody) Summary: 100% load CPU with windows build Initial Comment: after pushing button "Login" process opennx.exe load 100% CPU for a 2-3 min. windows xp sp3. mingw32 linux build with gcc4.4. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2864526&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-09-21 22:20:07
|
Bugs item #2863549, was opened at 2009-09-21 17:08 Message generated for change (Comment added) made by felfert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: Sebastian Reitenbach (buzzzzdeeee) Assigned to: Fritz Elfert (felfert) Summary: NX Session doesn't startup: cannot open display Initial Comment: HI, this is a followup to bug #ID: 2844795, I was unable to add a comment, it sent me to a login page, telling me I am already logged in, I also found no button to reopen the other report. First, sorry, I totally missed the first comment/question. Now I tested again, from an OpenSUSE 11.1 client. I was able to login to the server using nxclient-3.2.0-14 I installed on the same machine the rpm: opennx-0.16-292.SuSE11.1 and the login did not worked, the same problem occured that I have from my openbsd client box as mentioned in the other bug report. On the server the following rpm's are installed: rpm -qa | grep -i nx libnxcl-0.9-24.67 FreeNX-0.7.2-29.1 NX-3.2.0-44.1 nxclient-3.2.0-14 libnxcl1-0.9-24.67 The /etc/nxserver/node.conf has the following contents: ENABLE_FORCE_ENCRYPTION="0" DISPLAY_BASE=1000 SESSION_LIMIT=200 SESSION_USER_LIMIT=200 DISPLAY_LIMIT=200 ENABLE_MIRROR_VIA_VNC=1 NX_LOG_LEVEL=7 NX_LOGFILE=/var/log/nxserver.log SESSION_LOG_CLEAN=0 USER_FAKE_HOME=/tmp/$USER-nx ENABLE_AUTORECONNECT="0" ENABLE_AUTORECONNECT_BEFORE_140="1" ENABLE_ROOTLESS_MODE="1" On the server there are 10-20 people working every day using nxclient or knx, or connected from with a thinstation (thinstation.sf.net), which also uses the nxclient. Sebastian ---------------------------------------------------------------------- >Comment By: Fritz Elfert (felfert) Date: 2009-09-22 00:19 Message: The only logical explanation (presuming your server setup being ok) is: Of course, on a unix system, OpenNX has to be started within an environment, where: 1. The DISPLAY env var is already set 2. The X-authorization can successfully proceed Note, that (2) might fail, if you start opennx from within either a screen(1) session or from within a root-shell obtained via something like "su -" I'm going to close this now. Please contact me via email if you are able to reproduce the original behavior. -Fritz ---------------------------------------------------------------------- Comment By: Sebastian Reitenbach (buzzzzdeeee) Date: 2009-09-21 20:00 Message: I have no idea what changed on my openbsd box, but I compiled it again with -x and opennx just worked. Sorry for bothering, but I cannot reproduce. ---------------------------------------------------------------------- Comment By: Fritz Elfert (felfert) Date: 2009-09-21 18:30 Message: Opennx always starts nxssh with the -E option (a special NX-specific option, not available in regular ssh) which disables reading any config files. Therefore neither /etc/ssh/ssh_config nor ~/.ssh/config should affect its behavior. If it does not work, simply have a look into those client-side logs i mentioned. One idea: On your server, you have ENABLE_FORCE_ENCRYPTION="0". OpenNX is not very well tested *without* encryption and it enables that by default for new Sessions. This has several reasons: 1. It's a serious security risk. 2. Disabling encryption requires several ports to be accessible in the direction server -> client which can be confusing if a firewall is in between. 3. With a decent cpu, encryption overhead should be not noticeable. So could it be that you have disabled encryption by any chance? If so, try enabling it. -Fritz BTW: If you have problems using the Tracker's web-gui, just send me a mail ... i prefer mail over web-guis anyway ;-) ---------------------------------------------------------------------- Comment By: Sebastian Reitenbach (buzzzzdeeee) Date: 2009-09-21 17:36 Message: I wanted to provide the logs from the failing session and just retried on the OpenSUSE 11.1 box, and it suddenly just worked... I'll recompile with -x on the OpenBSD box and retry that too, and provide the logs from there. Could it be some client settings on the OpenBSD box causing trouble in the /etc/ssh/ssh_config file? Sebastian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-09-21 18:00:41
|
Bugs item #2863549, was opened at 2009-09-21 17:08 Message generated for change (Settings changed) made by buzzzzdeeee You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Sebastian Reitenbach (buzzzzdeeee) Assigned to: Fritz Elfert (felfert) Summary: NX Session doesn't startup: cannot open display Initial Comment: HI, this is a followup to bug #ID: 2844795, I was unable to add a comment, it sent me to a login page, telling me I am already logged in, I also found no button to reopen the other report. First, sorry, I totally missed the first comment/question. Now I tested again, from an OpenSUSE 11.1 client. I was able to login to the server using nxclient-3.2.0-14 I installed on the same machine the rpm: opennx-0.16-292.SuSE11.1 and the login did not worked, the same problem occured that I have from my openbsd client box as mentioned in the other bug report. On the server the following rpm's are installed: rpm -qa | grep -i nx libnxcl-0.9-24.67 FreeNX-0.7.2-29.1 NX-3.2.0-44.1 nxclient-3.2.0-14 libnxcl1-0.9-24.67 The /etc/nxserver/node.conf has the following contents: ENABLE_FORCE_ENCRYPTION="0" DISPLAY_BASE=1000 SESSION_LIMIT=200 SESSION_USER_LIMIT=200 DISPLAY_LIMIT=200 ENABLE_MIRROR_VIA_VNC=1 NX_LOG_LEVEL=7 NX_LOGFILE=/var/log/nxserver.log SESSION_LOG_CLEAN=0 USER_FAKE_HOME=/tmp/$USER-nx ENABLE_AUTORECONNECT="0" ENABLE_AUTORECONNECT_BEFORE_140="1" ENABLE_ROOTLESS_MODE="1" On the server there are 10-20 people working every day using nxclient or knx, or connected from with a thinstation (thinstation.sf.net), which also uses the nxclient. Sebastian ---------------------------------------------------------------------- >Comment By: Sebastian Reitenbach (buzzzzdeeee) Date: 2009-09-21 20:00 Message: I have no idea what changed on my openbsd box, but I compiled it again with -x and opennx just worked. Sorry for bothering, but I cannot reproduce. ---------------------------------------------------------------------- Comment By: Fritz Elfert (felfert) Date: 2009-09-21 18:30 Message: Opennx always starts nxssh with the -E option (a special NX-specific option, not available in regular ssh) which disables reading any config files. Therefore neither /etc/ssh/ssh_config nor ~/.ssh/config should affect its behavior. If it does not work, simply have a look into those client-side logs i mentioned. One idea: On your server, you have ENABLE_FORCE_ENCRYPTION="0". OpenNX is not very well tested *without* encryption and it enables that by default for new Sessions. This has several reasons: 1. It's a serious security risk. 2. Disabling encryption requires several ports to be accessible in the direction server -> client which can be confusing if a firewall is in between. 3. With a decent cpu, encryption overhead should be not noticeable. So could it be that you have disabled encryption by any chance? If so, try enabling it. -Fritz BTW: If you have problems using the Tracker's web-gui, just send me a mail ... i prefer mail over web-guis anyway ;-) ---------------------------------------------------------------------- Comment By: Sebastian Reitenbach (buzzzzdeeee) Date: 2009-09-21 17:36 Message: I wanted to provide the logs from the failing session and just retried on the OpenSUSE 11.1 box, and it suddenly just worked... I'll recompile with -x on the OpenBSD box and retry that too, and provide the logs from there. Could it be some client settings on the OpenBSD box causing trouble in the /etc/ssh/ssh_config file? Sebastian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-09-21 16:30:24
|
Bugs item #2863549, was opened at 2009-09-21 17:08 Message generated for change (Settings changed) made by felfert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sebastian Reitenbach (buzzzzdeeee) >Assigned to: Fritz Elfert (felfert) Summary: NX Session doesn't startup: cannot open display Initial Comment: HI, this is a followup to bug #ID: 2844795, I was unable to add a comment, it sent me to a login page, telling me I am already logged in, I also found no button to reopen the other report. First, sorry, I totally missed the first comment/question. Now I tested again, from an OpenSUSE 11.1 client. I was able to login to the server using nxclient-3.2.0-14 I installed on the same machine the rpm: opennx-0.16-292.SuSE11.1 and the login did not worked, the same problem occured that I have from my openbsd client box as mentioned in the other bug report. On the server the following rpm's are installed: rpm -qa | grep -i nx libnxcl-0.9-24.67 FreeNX-0.7.2-29.1 NX-3.2.0-44.1 nxclient-3.2.0-14 libnxcl1-0.9-24.67 The /etc/nxserver/node.conf has the following contents: ENABLE_FORCE_ENCRYPTION="0" DISPLAY_BASE=1000 SESSION_LIMIT=200 SESSION_USER_LIMIT=200 DISPLAY_LIMIT=200 ENABLE_MIRROR_VIA_VNC=1 NX_LOG_LEVEL=7 NX_LOGFILE=/var/log/nxserver.log SESSION_LOG_CLEAN=0 USER_FAKE_HOME=/tmp/$USER-nx ENABLE_AUTORECONNECT="0" ENABLE_AUTORECONNECT_BEFORE_140="1" ENABLE_ROOTLESS_MODE="1" On the server there are 10-20 people working every day using nxclient or knx, or connected from with a thinstation (thinstation.sf.net), which also uses the nxclient. Sebastian ---------------------------------------------------------------------- Comment By: Fritz Elfert (felfert) Date: 2009-09-21 18:30 Message: Opennx always starts nxssh with the -E option (a special NX-specific option, not available in regular ssh) which disables reading any config files. Therefore neither /etc/ssh/ssh_config nor ~/.ssh/config should affect its behavior. If it does not work, simply have a look into those client-side logs i mentioned. One idea: On your server, you have ENABLE_FORCE_ENCRYPTION="0". OpenNX is not very well tested *without* encryption and it enables that by default for new Sessions. This has several reasons: 1. It's a serious security risk. 2. Disabling encryption requires several ports to be accessible in the direction server -> client which can be confusing if a firewall is in between. 3. With a decent cpu, encryption overhead should be not noticeable. So could it be that you have disabled encryption by any chance? If so, try enabling it. -Fritz BTW: If you have problems using the Tracker's web-gui, just send me a mail ... i prefer mail over web-guis anyway ;-) ---------------------------------------------------------------------- Comment By: Sebastian Reitenbach (buzzzzdeeee) Date: 2009-09-21 17:36 Message: I wanted to provide the logs from the failing session and just retried on the OpenSUSE 11.1 box, and it suddenly just worked... I'll recompile with -x on the OpenBSD box and retry that too, and provide the logs from there. Could it be some client settings on the OpenBSD box causing trouble in the /etc/ssh/ssh_config file? Sebastian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-09-21 16:30:09
|
Bugs item #2863549, was opened at 2009-09-21 17:08 Message generated for change (Comment added) made by felfert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sebastian Reitenbach (buzzzzdeeee) Assigned to: Nobody/Anonymous (nobody) Summary: NX Session doesn't startup: cannot open display Initial Comment: HI, this is a followup to bug #ID: 2844795, I was unable to add a comment, it sent me to a login page, telling me I am already logged in, I also found no button to reopen the other report. First, sorry, I totally missed the first comment/question. Now I tested again, from an OpenSUSE 11.1 client. I was able to login to the server using nxclient-3.2.0-14 I installed on the same machine the rpm: opennx-0.16-292.SuSE11.1 and the login did not worked, the same problem occured that I have from my openbsd client box as mentioned in the other bug report. On the server the following rpm's are installed: rpm -qa | grep -i nx libnxcl-0.9-24.67 FreeNX-0.7.2-29.1 NX-3.2.0-44.1 nxclient-3.2.0-14 libnxcl1-0.9-24.67 The /etc/nxserver/node.conf has the following contents: ENABLE_FORCE_ENCRYPTION="0" DISPLAY_BASE=1000 SESSION_LIMIT=200 SESSION_USER_LIMIT=200 DISPLAY_LIMIT=200 ENABLE_MIRROR_VIA_VNC=1 NX_LOG_LEVEL=7 NX_LOGFILE=/var/log/nxserver.log SESSION_LOG_CLEAN=0 USER_FAKE_HOME=/tmp/$USER-nx ENABLE_AUTORECONNECT="0" ENABLE_AUTORECONNECT_BEFORE_140="1" ENABLE_ROOTLESS_MODE="1" On the server there are 10-20 people working every day using nxclient or knx, or connected from with a thinstation (thinstation.sf.net), which also uses the nxclient. Sebastian ---------------------------------------------------------------------- >Comment By: Fritz Elfert (felfert) Date: 2009-09-21 18:30 Message: Opennx always starts nxssh with the -E option (a special NX-specific option, not available in regular ssh) which disables reading any config files. Therefore neither /etc/ssh/ssh_config nor ~/.ssh/config should affect its behavior. If it does not work, simply have a look into those client-side logs i mentioned. One idea: On your server, you have ENABLE_FORCE_ENCRYPTION="0". OpenNX is not very well tested *without* encryption and it enables that by default for new Sessions. This has several reasons: 1. It's a serious security risk. 2. Disabling encryption requires several ports to be accessible in the direction server -> client which can be confusing if a firewall is in between. 3. With a decent cpu, encryption overhead should be not noticeable. So could it be that you have disabled encryption by any chance? If so, try enabling it. -Fritz BTW: If you have problems using the Tracker's web-gui, just send me a mail ... i prefer mail over web-guis anyway ;-) ---------------------------------------------------------------------- Comment By: Sebastian Reitenbach (buzzzzdeeee) Date: 2009-09-21 17:36 Message: I wanted to provide the logs from the failing session and just retried on the OpenSUSE 11.1 box, and it suddenly just worked... I'll recompile with -x on the OpenBSD box and retry that too, and provide the logs from there. Could it be some client settings on the OpenBSD box causing trouble in the /etc/ssh/ssh_config file? Sebastian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-09-21 15:36:21
|
Bugs item #2863549, was opened at 2009-09-21 17:08 Message generated for change (Comment added) made by buzzzzdeeee You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sebastian Reitenbach (buzzzzdeeee) Assigned to: Nobody/Anonymous (nobody) Summary: NX Session doesn't startup: cannot open display Initial Comment: HI, this is a followup to bug #ID: 2844795, I was unable to add a comment, it sent me to a login page, telling me I am already logged in, I also found no button to reopen the other report. First, sorry, I totally missed the first comment/question. Now I tested again, from an OpenSUSE 11.1 client. I was able to login to the server using nxclient-3.2.0-14 I installed on the same machine the rpm: opennx-0.16-292.SuSE11.1 and the login did not worked, the same problem occured that I have from my openbsd client box as mentioned in the other bug report. On the server the following rpm's are installed: rpm -qa | grep -i nx libnxcl-0.9-24.67 FreeNX-0.7.2-29.1 NX-3.2.0-44.1 nxclient-3.2.0-14 libnxcl1-0.9-24.67 The /etc/nxserver/node.conf has the following contents: ENABLE_FORCE_ENCRYPTION="0" DISPLAY_BASE=1000 SESSION_LIMIT=200 SESSION_USER_LIMIT=200 DISPLAY_LIMIT=200 ENABLE_MIRROR_VIA_VNC=1 NX_LOG_LEVEL=7 NX_LOGFILE=/var/log/nxserver.log SESSION_LOG_CLEAN=0 USER_FAKE_HOME=/tmp/$USER-nx ENABLE_AUTORECONNECT="0" ENABLE_AUTORECONNECT_BEFORE_140="1" ENABLE_ROOTLESS_MODE="1" On the server there are 10-20 people working every day using nxclient or knx, or connected from with a thinstation (thinstation.sf.net), which also uses the nxclient. Sebastian ---------------------------------------------------------------------- >Comment By: Sebastian Reitenbach (buzzzzdeeee) Date: 2009-09-21 17:36 Message: I wanted to provide the logs from the failing session and just retried on the OpenSUSE 11.1 box, and it suddenly just worked... I'll recompile with -x on the OpenBSD box and retry that too, and provide the logs from there. Could it be some client settings on the OpenBSD box causing trouble in the /etc/ssh/ssh_config file? Sebastian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-09-21 15:08:37
|
Bugs item #2863549, was opened at 2009-09-21 17:08 Message generated for change (Tracker Item Submitted) made by buzzzzdeeee You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sebastian Reitenbach (buzzzzdeeee) Assigned to: Nobody/Anonymous (nobody) Summary: NX Session doesn't startup: cannot open display Initial Comment: HI, this is a followup to bug #ID: 2844795, I was unable to add a comment, it sent me to a login page, telling me I am already logged in, I also found no button to reopen the other report. First, sorry, I totally missed the first comment/question. Now I tested again, from an OpenSUSE 11.1 client. I was able to login to the server using nxclient-3.2.0-14 I installed on the same machine the rpm: opennx-0.16-292.SuSE11.1 and the login did not worked, the same problem occured that I have from my openbsd client box as mentioned in the other bug report. On the server the following rpm's are installed: rpm -qa | grep -i nx libnxcl-0.9-24.67 FreeNX-0.7.2-29.1 NX-3.2.0-44.1 nxclient-3.2.0-14 libnxcl1-0.9-24.67 The /etc/nxserver/node.conf has the following contents: ENABLE_FORCE_ENCRYPTION="0" DISPLAY_BASE=1000 SESSION_LIMIT=200 SESSION_USER_LIMIT=200 DISPLAY_LIMIT=200 ENABLE_MIRROR_VIA_VNC=1 NX_LOG_LEVEL=7 NX_LOGFILE=/var/log/nxserver.log SESSION_LOG_CLEAN=0 USER_FAKE_HOME=/tmp/$USER-nx ENABLE_AUTORECONNECT="0" ENABLE_AUTORECONNECT_BEFORE_140="1" ENABLE_ROOTLESS_MODE="1" On the server there are 10-20 people working every day using nxclient or knx, or connected from with a thinstation (thinstation.sf.net), which also uses the nxclient. Sebastian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2863549&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-09-20 16:19:29
|
Support Requests item #1806724, was opened at 2007-10-03 09:39 Message generated for change (Comment added) made by bsavelev You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910153&aid=1806724&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 8 Private: No Submitted By: quasimotoca (quasimotoca2) Assigned to: Nobody/Anonymous (nobody) Summary: Windows compile problem Initial Comment: Hi Fritz: I'm trying to compile OpenNX release 0.1.4 on a WindowsXP/SP2 machine (with the platform SDK installed). I'm using MS-VC++6 Standard and have built the WxWidget library and added it to VC++6. The compile seems to go fine until it hits MySession.cpp. I receive a number of errors as follows: C:\opennx-0.14\MySession.cpp(1380) : error C2143: syntax error : missing ';' before '{' C:\opennx-0.14\MySession.cpp(1380) : error C2143: syntax error : missing ';' before '{' C:\opennx-0.14\MySession.cpp(1380) : error C2143: syntax error : missing ';' before '{' C:\opennx-0.14\MySession.cpp(1380) : error C2143: syntax error : missing ';' before '{' Your code is syntactically perfect. So I'm thinking this might be VC++ setup related (or my VC++ is too old). When compiling on Windows XP/SP2, which IDE'(s) and steps do you recommend I take to compile successfully? Cheers, Dave Cook ---------------------------------------------------------------------- Comment By: Boris Savelev (bsavelev) Date: 2009-09-20 20:19 Message: i think you need use mingw instead vc++6 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910153&aid=1806724&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-09-18 23:08:16
|
Bugs item #2844795, was opened at 2009-08-26 10:30 Message generated for change (Settings changed) made by felfert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2844795&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Rejected Priority: 5 Private: No Submitted By: Sebastian Reitenbach (buzzzzdeeee) Assigned to: Fritz Elfert (felfert) Summary: NX Session doesn't startup: cannot open display Initial Comment: Hi, I tried a long time to get a NX session working. So I tested the obvious things: The server is an openSUSE 11.1, the client is OpenBSD 4.5/opennx-0.16 ssh -X nxserver; nxnode --agent that worked I got the Black screen with the !M also nxssh -nxadminmode -X user@nxserver konsole was working, I got the remote KDE konsole on my OpenBSD desktop. So I took a look into the code and found in MySession.cpp in line 1663 I changed the line from: nxsshcmd << wxT(" -nx -x -2") to nxsshcmd << wxT(" -nx -X -2") and recompiled. Afterwards the nxsession started to work. Sebastian ---------------------------------------------------------------------- >Comment By: Fritz Elfert (felfert) Date: 2009-09-19 01:08 Message: No further response from submitter. Therefore: closed ---------------------------------------------------------------------- Comment By: Fritz Elfert (felfert) Date: 2009-08-29 00:54 Message: Apparently, your NX Server is completely misconfigured. If you are using -X instead of -x, then you are using regular ssh X11-forwarding, *not* the NX protocol (It works accidently - because nxssh is derived from openssh and that old code is still in there). To use *that*, you wouldn't need NX (or OpenNX) at all. Therefore: The -x (disable X11-Forward) parameter is absolutely correct and intentional. The *normal* way (with X111-Forwarding disabled by -x) is, that the DISPLAY variable is dynamically set up on the server side. What software are you using at the server side? NoMachine's original, FreeNX or neatnx? Also: NX *always* uses a 2-stage login process where the first user is always the "nx" user, then, session parameters are negotiated, and after a second local authentication on the server side, the server-side agent is started, (which - depending on session parameters - in turn starts either a local X-Session or uses rdesktop or xvnc for connecting to some remote machine). Have you tried to connect using the original (NoMachine's) client? I bet, this would not work either with your server setup. Also: To get a clue about what is going wrong, Try connecting with OpenNX (unchanged, with -x) and have a look at ~/.nx/temp/<PID>/{runlog,sshlog} Cheers -Fritz ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2844795&group_id=184662 |
From: Fritz E. <fr...@fr...> - 2009-09-10 02:25:18
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Antoine Martin schrieb: > Hi Fritz, > > (this message was off-list - is this intentional?) Whoops, no. Had it answered in another client which did not automatically reply to the list somehow... > > I agree with your reasoning for using XMing. It makes a lot of sense. > > For similar reasons, I do not understand why nxproxy and nxssh are > merged into one: > * makes it harder to keep ssh up to date > * makes it harder to separate the transport (ssh/tcp) from the actual X > client/server stuff. It is not that bad. The client/server stuff is all in one shared lib: libXcomp.{so,dll,dylib}. nxproxy and nxssh are only thin wrappers around that. > > That said, if that's the way it has to be done, I would still like to > have a go. Do you have any idea what command line I would need to use to > get nxssh to connect to my nxagent tcp endpoint? > I do not want to use any of the NX server-side madness (nxserver, > nxnode, ..), I just want to connect to the TCP port where nxagent is > listening. It should be simple! (and it is on Linux using nxproxy) > Without NX server actually no, as i never tried it *that* way. However, AFAIR at NoMachine they have an archive of shell scripts which should do something similar. It's available at the very bottom of http://www.nomachine.com/sources.php. The direct URL is: http://64.34.161.181/download/3.3.0/sources/nxscripts-3.3.0-1.tar.gz At least, it should give you an idea how all the stuff goes together. Cheers -Fritz > Thanks > Antoine > > > > > > > Fritz Elfert wrote: >> Hi, > >> NXWin is just an ordinary X11-Server (an old XFree server - to be >> exact). There is nothing special about it. The sources are available at >> NoMachine's website. The actual counterpart of the NX-protocol is either >> nxssh (or nxproxy). Since some time now, the whole nxproxy stuff is >> built into nxssh so nxproxy is actually not needed anymore. Both are >> simply X11-Clients which use a local X11-Display. > >> Reason for XMing: > >> It's not cygwin-based. >> It's *much* closer to the current Xorg. >> Performance is better. >> It supports multiple Monitors. > >> Cheers >> -Fritz > >> Antoine Martin schrieb: >>> Hi, >>> I am quite interested in calling NXWin.exe directly from a script rather >>> than through a UI. >>> Where did you find the documentation on NXWin to know what parameters in >>> accepts? Did you just reverse engineer it? Is the source available >>> anywhere that I've missed? >>> What I would like to do is start the nxagent on the server, like so: >>> /usr/bin/nxagent -R :60 >>> Then setup a tunnel from the windows box by hand using Plink.exe: >>> [...] -R 4060:127.0.0.1:5060 >>> Then in theory, I should be able to attach to the session from the >>> windows box by running something like: >>> NXWin.exe :1060 >>> (in the same way that I can do it from the linux box with nxproxy) >>> Right? Am I missing something? >>> At the moment, a window briefly flickers and disappears, no error >>> messages, no information, nothing... >>> I am also a little bit confused by the fact that the website mentions >>> using XMing as an alternative to NXWin, in this case which program would >>> act as the nxproxy for the remote nxagent? >>> Any help would be much appreciated. >>> Thanks >>> Antoine >> - >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >> trial. Simplify your report design, integration and deployment - and >> focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Opennx-devel mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opennx-devel > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKqGN9boM4mAMyprARAsuIAJ9q/77IMWn9YFFXxgEHVOQLyw3wMgCglQJ7 IKl1sXGgnxLLQ8i7Ll6nem0= =KOM6 -----END PGP SIGNATURE----- |
From: Antoine M. <an...@na...> - 2009-09-09 06:59:44
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, I am quite interested in calling NXWin.exe directly from a script rather than through a UI. Where did you find the documentation on NXWin to know what parameters in accepts? Did you just reverse engineer it? Is the source available anywhere that I've missed? What I would like to do is start the nxagent on the server, like so: /usr/bin/nxagent -R :60 Then setup a tunnel from the windows box by hand using Plink.exe: [...] -R 4060:127.0.0.1:5060 Then in theory, I should be able to attach to the session from the windows box by running something like: NXWin.exe :1060 (in the same way that I can do it from the linux box with nxproxy) Right? Am I missing something? At the moment, a window briefly flickers and disappears, no error messages, no information, nothing... I am also a little bit confused by the fact that the website mentions using XMing as an alternative to NXWin, in this case which program would act as the nxproxy for the remote nxagent? Any help would be much appreciated. Thanks Antoine -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREKAAYFAkqnUk8ACgkQGK2zHPGK1rtQbACfXQvEEgaSr+MZuJ0Md/jZwhDS fkAAnjScVID6PU/GJLnDmqKbl+9vbaUp =8kdU -----END PGP SIGNATURE----- |
From: Fritz E. <fr...@fr...> - 2009-08-30 02:23:55
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jo-Erlend Schinstad schrieb: > 2009/8/29 Fritz Elfert <fr...@fr...>: > >> 1. OpenNX would need an option to connect ad-hoc "silently" (without >> showing the initial login dialog). >> 2. One would use a local login-manager, specifically configured to >> startup OpenNX in that new mode (and a WM of course) instead of starting >> up a regular local session. > > > But how would the local GDM know about OpenNX settings, user names and > passwords? GDM does not need to know. *All* settings (including username and password) can be stored in a session config file. (For storing the password, you have to check the "Remember password" in the advanced config dialog.) Finally, you then could invoke OpenNX, specifying the session-config on the command-line like this (This is normally used when a user clicks an OpenNX session icon on his desktop): opennx --session=$HOME/.nx/config/mysession.nxs That provided, you could now configure a custom session type in GDM (or kdm etc.) which simply runs a shell-script containing the above command-line (plus starting a WM - like metacity for example). Of course, with a large number of users, this method is quite cumbersome to manage. If you would tell some more details about your scenario, I probably could elaborate more specifically. For example: Instead of specifying a local path for the .nxs, you could also use an HTTP URL (OpenNX then automatically downloads the config file). With that, you could even generate the config file dynamically on a server using a CGI. The connection to that config server should be secure however ... Cheers -Fritz > > Jo-Erlend Schinstad > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Opennx-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennx-devel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKmeKmboM4mAMyprARAoPiAJ9NQq4903EOktyGCHWi8MBYfAurjACeM+a6 KJ3yTRW/ES++wRfaQB9gb0M= =DOJq -----END PGP SIGNATURE----- |
From: Jo-Erlend S. <joe...@gm...> - 2009-08-29 21:09:58
|
2009/8/29 Fritz Elfert <fr...@fr...>: > 1. OpenNX would need an option to connect ad-hoc "silently" (without > showing the initial login dialog). > 2. One would use a local login-manager, specifically configured to > startup OpenNX in that new mode (and a WM of course) instead of starting > up a regular local session. But how would the local GDM know about OpenNX settings, user names and passwords? Jo-Erlend Schinstad |
From: Fritz E. <fr...@fr...> - 2009-08-29 19:35:35
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hmm, this implies that you have OpenNX running as the *only* app or even as a login manager (not good, since those usually run as root). Furthermore, you would give up the ability of running multiple sessions?! Does not sound very useful to me - or did i got something wrong? My guess of your usage-scenario is that you want something like a kiosked (closed-down) environment (e.g. for some thinclient). If that's the case, this could be done a lot easier: 1. OpenNX would need an option to connect ad-hoc "silently" (without showing the initial login dialog). 2. One would use a local login-manager, specifically configured to startup OpenNX in that new mode (and a WM of course) instead of starting up a regular local session. This would have several advantages: - - Using an existing login manager (like gdm), you could benefit from it's already existing features like skinning etc. - - Inside OpenNX, it would require just a minor change... Cheers -Fritz Jo-Erlend Schinstad schrieb: > Hello everyone. > > Love your product. One thing I've always wanted in nxclient, is the > ability to have > a fullscreen login manager, preferably a beautiful one, like I have on > my console. > And if it could even use a transition between the login screen and the desktop > session, that'd be great. When the user logs in, the desktop is prepared in the > background, and then when it's ready, the login manager would fade into a > screenshot of the prepared desktop and then disappear. Then, when the user > logs out, the login screen would reappear. > > Is this feasible? > > Thanks, > > Jo-Erlend Schinstad > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Opennx-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennx-devel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKmX/zboM4mAMyprARAm3DAJ9G2/SqcIQ9QRABQHfcJbEukGFZmgCfZ0P5 SHxwarhsXiLDLTbkxprTV88= =+G7t -----END PGP SIGNATURE----- |
From: SourceForge.net <no...@so...> - 2009-08-28 22:55:30
|
Bugs item #2844795, was opened at 2009-08-26 10:30 Message generated for change (Settings changed) made by felfert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2844795&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Rejected Priority: 5 Private: No Submitted By: Sebastian Reitenbach (buzzzzdeeee) >Assigned to: Fritz Elfert (felfert) Summary: NX Session doesn't startup: cannot open display Initial Comment: Hi, I tried a long time to get a NX session working. So I tested the obvious things: The server is an openSUSE 11.1, the client is OpenBSD 4.5/opennx-0.16 ssh -X nxserver; nxnode --agent that worked I got the Black screen with the !M also nxssh -nxadminmode -X user@nxserver konsole was working, I got the remote KDE konsole on my OpenBSD desktop. So I took a look into the code and found in MySession.cpp in line 1663 I changed the line from: nxsshcmd << wxT(" -nx -x -2") to nxsshcmd << wxT(" -nx -X -2") and recompiled. Afterwards the nxsession started to work. Sebastian ---------------------------------------------------------------------- >Comment By: Fritz Elfert (felfert) Date: 2009-08-29 00:54 Message: Apparently, your NX Server is completely misconfigured. If you are using -X instead of -x, then you are using regular ssh X11-forwarding, *not* the NX protocol (It works accidently - because nxssh is derived from openssh and that old code is still in there). To use *that*, you wouldn't need NX (or OpenNX) at all. Therefore: The -x (disable X11-Forward) parameter is absolutely correct and intentional. The *normal* way (with X111-Forwarding disabled by -x) is, that the DISPLAY variable is dynamically set up on the server side. What software are you using at the server side? NoMachine's original, FreeNX or neatnx? Also: NX *always* uses a 2-stage login process where the first user is always the "nx" user, then, session parameters are negotiated, and after a second local authentication on the server side, the server-side agent is started, (which - depending on session parameters - in turn starts either a local X-Session or uses rdesktop or xvnc for connecting to some remote machine). Have you tried to connect using the original (NoMachine's) client? I bet, this would not work either with your server setup. Also: To get a clue about what is going wrong, Try connecting with OpenNX (unchanged, with -x) and have a look at ~/.nx/temp/<PID>/{runlog,sshlog} Cheers -Fritz ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2844795&group_id=184662 |
From: Jo-Erlend S. <joe...@gm...> - 2009-08-28 03:24:16
|
Hello everyone. Love your product. One thing I've always wanted in nxclient, is the ability to have a fullscreen login manager, preferably a beautiful one, like I have on my console. And if it could even use a transition between the login screen and the desktop session, that'd be great. When the user logs in, the desktop is prepared in the background, and then when it's ready, the login manager would fade into a screenshot of the prepared desktop and then disappear. Then, when the user logs out, the login screen would reappear. Is this feasible? Thanks, Jo-Erlend Schinstad |
From: SourceForge.net <no...@so...> - 2009-08-26 08:30:11
|
Bugs item #2844795, was opened at 2009-08-26 10:30 Message generated for change (Tracker Item Submitted) made by buzzzzdeeee You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2844795&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sebastian Reitenbach (buzzzzdeeee) Assigned to: Nobody/Anonymous (nobody) Summary: NX Session doesn't startup: cannot open display Initial Comment: Hi, I tried a long time to get a NX session working. So I tested the obvious things: The server is an openSUSE 11.1, the client is OpenBSD 4.5/opennx-0.16 ssh -X nxserver; nxnode --agent that worked I got the Black screen with the !M also nxssh -nxadminmode -X user@nxserver konsole was working, I got the remote KDE konsole on my OpenBSD desktop. So I took a look into the code and found in MySession.cpp in line 1663 I changed the line from: nxsshcmd << wxT(" -nx -x -2") to nxsshcmd << wxT(" -nx -X -2") and recompiled. Afterwards the nxsession started to work. Sebastian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2844795&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-07-30 02:00:34
|
Bugs item #2829183, was opened at 2009-07-29 21:31 Message generated for change (Settings changed) made by felfert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2829183&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Tomas Groth (tgc) >Assigned to: Fritz Elfert (felfert) Summary: Fails to login - defaults to login with key-file? Initial Comment: I'm trying to login to a server, but the login fails with the following error message: "Unexpected termination of nxssh". Running in the console in verbose mode doesn't give any information. But I have a feeling that opennx always tries to login using key-files, and therefore ignores my password, and so fails to login. My "feeling" is based on an error message I got when I hadn't configured the nx-system-folder correctly, giving the following error message: execvp(/home/tgc/opennx/src/opennx/bin/nxssh, -nx, -x, -2, -p, 22, -o, RhostsAuthentication no, -o, PasswordAuthentication no, -o, RSAAuthentication no, -o, RhostsRSAAuthentication no, -o, PubkeyAuthentication yes, -i, /home/tgc/opennx/src/opennx/share/keys/server.id_dsa.key, -B, -E, nx...@te...) failed with error 2! Especially "PasswordAuthentication no" tells me that opennx doesn't do what it is supposed to do... ---------------------------------------------------------------------- >Comment By: Fritz Elfert (felfert) Date: 2009-07-30 04:00 Message: Nope, wrong assumption ... This is how it is supposed to work (NoMachine's client does this as well). NX always uses *two* stages of authentication: 1. Login into the nxserver, *always* using a key (default: NoMachine's well known pubkey, but can be pasted in the advanced config). Also: this is always done as user nx, *not* the user you specify in the login dialog. 2. The actual user/password based login versus nxserver's command-shell *inside* the first connection. What you see (the execvp message) is from stage 1. Error 2 is ENOENT and this means: Your nxssh binary (/home/tgc/opennx/src/opennx/bin/nxssh) could not be found. Apparently, you are trying to run an *uninstalled* opennx from within the source directory. This cannot work without changes. Reason: Just like NoMachine's original, when started for the first time, OpenNX finds out it's own path and sets a config variable "System NX dir" to the parent directory. This makes perfect sense if installed in /usr/NX/bin but fails in your case. Two solutions are possible: 1. remove OpenNX's environment-config file at ~/.opennx, install opennx into /usr/NX/bin, then try again. 2. If you just want to try it out without installing, Start OpenNX, select "Configure", select the "Environment" tab. Correct the "System NX dir" (should point to /usr/NX, or whereever your regular nx env is) entry, klick apply. Please use the mailing list for further help and/or discussion. -Fritz ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2829183&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-07-29 19:31:02
|
Bugs item #2829183, was opened at 2009-07-29 21:31 Message generated for change (Tracker Item Submitted) made by tgc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2829183&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tomas Groth (tgc) Assigned to: Nobody/Anonymous (nobody) Summary: Fails to login - defaults to login with key-file? Initial Comment: I'm trying to login to a server, but the login fails with the following error message: "Unexpected termination of nxssh". Running in the console in verbose mode doesn't give any information. But I have a feeling that opennx always tries to login using key-files, and therefore ignores my password, and so fails to login. My "feeling" is based on an error message I got when I hadn't configured the nx-system-folder correctly, giving the following error message: execvp(/home/tgc/opennx/src/opennx/bin/nxssh, -nx, -x, -2, -p, 22, -o, RhostsAuthentication no, -o, PasswordAuthentication no, -o, RSAAuthentication no, -o, RhostsRSAAuthentication no, -o, PubkeyAuthentication yes, -i, /home/tgc/opennx/src/opennx/share/keys/server.id_dsa.key, -B, -E, nx...@te...) failed with error 2! Especially "PasswordAuthentication no" tells me that opennx doesn't do what it is supposed to do... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2829183&group_id=184662 |
From: SourceForge.net <no...@so...> - 2009-07-28 15:52:30
|
Bugs item #2200927, was opened at 2008-10-27 15:35 Message generated for change (Settings changed) made by felfert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2200927&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Deleted >Resolution: Out of Date Priority: 5 Private: No Submitted By: Fritz Elfert (felfert) Assigned to: Nobody/Anonymous (nobody) Summary: test Initial Comment: testing mail notification from SF tracker ---------------------------------------------------------------------- Comment By: Fritz Elfert (felfert) Date: 2008-10-27 16:01 Message: test3 ---------------------------------------------------------------------- Comment By: Fritz Elfert (felfert) Date: 2008-10-27 15:44 Message: test2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2200927&group_id=184662 |
From: SourceForge.net <no...@so...> - 2008-10-27 15:01:38
|
Bugs item #2200927, was opened at 2008-10-27 15:35 Message generated for change (Comment added) made by felfert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2200927&group_id=184662 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Fritz Elfert (felfert) Assigned to: Nobody/Anonymous (nobody) Summary: test Initial Comment: testing mail notification from SF tracker ---------------------------------------------------------------------- >Comment By: Fritz Elfert (felfert) Date: 2008-10-27 16:01 Message: test3 ---------------------------------------------------------------------- Comment By: Fritz Elfert (felfert) Date: 2008-10-27 15:44 Message: test2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=910152&aid=2200927&group_id=184662 |