https://bugzilla.novell.com/show_bug.cgi?id=280380 ------- Comment #1 from mvdv@spamcop.net 2007-06-02 21:44 MST ------- Created an attachment (id=143776) --> (https://bugzilla.novell.com/attachment.cgi?id=143776&action=view) nxsetup log this is the console output generated by: nxsetup --install --setup-nomachine-key --clean --purge -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=280380 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |sndirsch@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=280380 mvdv@spamcop.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mvdv@spamcop.net | ------- Comment #4 from mvdv@spamcop.net 2007-06-07 22:16 MST ------- Well that bug report came a day or more after this one right? Who would naturally think to run around deleting passwords from other peoples accounts.... On the x86_64 platform the install script fails for the same reason - the nx account is created locked. I haven't checked whether passwd -u nx fails there too. The FreeNX mail list indicate there is a dsitro (not SuSE) which requires passwd -u nx after the account is created. On my installation of SuSE this workaround doesn't work around the problem. You have to be willing to delete a password for an account you didn't create.... and as a user you really don't know what this account will be doing, etc. I was not a happy camper at that point, so I log a bug report about this - It got rejected. So, this is all apparently either good behavior or the FreeNX group need to be convinced to change how they work their server/client relation. Anyway, until then there seems to be a bug in the FreeNX setup in the SuSE distribution. Is the response to this bug the same... don't bother us - take it to the FreeNX people? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=280380 ------- Comment #6 from mvdv@spamcop.net 2007-06-08 05:23 MST ------- Thanks for testing. I have two more (x86_64) machines I have to install FreeNX on. They are fresh SuSE 10.2 installations. I'll post if they fail in the manner described. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=280380#c8 --- Comment #8 from Mark Van De Vyver 2007-06-26 19:17:10 MST --- Update: I can confirm this error occurs on one i686 and three x86_64 machines. The x86_64 machine are freshly installed with openSUSE 10.2. All machines were installed/setup with the no-machine key. If I add the `passwd -d <user>` as indicated everything works fine. One user has responded the heads-up I posted to freenx-devel list. They indicate this passwd -d <>user> work around solved an issue thay had getting two servers to communicate. Anyway it seems the issue is the failure of 'passwd -u <user>' to unlock the user account. See Bug #281252 which is apparently invalid. I'm sure the FreeNX developers would like to know the 'correct' way to create the user account they require on openSUSE? Hope that helps. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.