[FreeNX-kNX] Black Screen with Mouse Cursor After Successful Auth

[OwN-3m-All]

Also, the windows are only unmovable in a freenx session.

On Fri, Jan 4, 2013 at 8:20 PM, OwN-3m-All <own3mall at gmail.com> wrote:

> I am able to SSH using Putty with the old account just fine.  I just tried
> the xterm command.  Freenx claimed to have established the display, but
> then immediately crashed with nothing on my screen.  So, yes, I am able to
> login locally to both gnome and terminal with that user account.  Freenx
> just won't work anymore for that user since the crash, and I have no idea
> why.  Also, for the new user I created, I am able to get in with freenx and
> see a desktop, but my gnome windows are unmovable and fixed on the
> screen?   I'm guessing I'll need to get X Windows and gnome working
> properly before freenx works like it used to?  Surely someone has seen
> something like this before though?
>
> I've never seen a Linux machine pwn itself when rebooting until my server
> crashed and messed this all up...
>
>
> On Thu, Jan 3, 2013 at 4:17 AM, <chris at ccburton.com> wrote:
>
>>
>> freenx-knx-bounces at kde.org wrote on 03/01/2013 05:32:08:
>>
>>
>> > Hi All,
>> >
>> > My server crashed over the weekend, and I had to clean up the mess
>> > left behind by Xorg and X Server.
>>
>>
>> And thereby hangs a tale . . .
>>
>> > Needless to say, I finally got X  working again, but now, I'm
>> > unable to login via freenx using my typical user account.
>>
>> Hmmm. Just that account. What about other accounts over FreeNX ???
>>
>> Can you log in locally with that account ??
>>
>> > When I do login, the authentication is
>>
>> Right. So you can actually log in . . . .
>>
>> > successful, and I'm just left with a black screen with a mouse
>> > cursor.  I know X is running, as the process ID shows up.
>>
>> . . . but your old X session doesn't start properly anymore.
>>
>> > So, to start, I deleted all gnome cache, deleted all sessions,
>> > restarted the nxserver and freenx-server service, and deleted
>> > stuff in the /tmp/user-orbit folder.  None of that helped.
>> > What's weird is that I created a new user, added the user to the
>> > allowed SSH list, and tried connecting using the same settings.
>> > With the new user, I can get in and see my gnome desktop.
>>
>>
>> so . . .  actually the issue is . .
>>
>> you have an old account which "now won't work" with FreeNX
>>         (i.e. X (nxagent) is starting but gnome isn't)
>> but
>> a new one does work
>> so
>> that means FreeNX is working just fine.
>>
>> so . . .so . . .
>> What about this old account ???
>>
>>
>> ***
>> Does it work OK from a local console login
>>         (i.e gnome starts  . . .it is just broken over NX only)
>> or
>> does it not work locally either
>>         (i.e. the account config has been broken)
>> ***
>>
>> also you can try  . . .
>>
>> Temporarily
>> set the session in nxclient to just
>>         run xterm
>> i.e.
>> in nxclient
>>         <configure>(button)<general>(tab)<desktop>(setting)
>>         set to Unix Custom (drop downs)
>>         <Settings>(button)<Application>(setting)
>>         choose "Run the following command"
>> and enter
>>                  xterm
>> in the box.
>>
>>
>> You should get an xterm window when you connect,
>>          (if it's just gnomish or startx issue)
>>
>> Also, in your connected xterm window .  . .
>> try
>> starting your window manager at the command line e.g enter:-
>>
>>                 metacity &
>>
>> and
>> see if you get a movable window around your xterm.
>>
>> You could also try starting gnome at the command line.
>>
>>
>> >  I'm running Ubuntu 10.04.  I've
>> > looked at countless forum posts where others have had the same
>> > problem and tried everything.  Nothing has fixed it for the main
>> > user account.  I have logging enabled in the nxserver, and no errors
>> > are reported in the nxserver.log or in the session cache files
>> themselves.
>> >
>> > Can anyone suggest anything else I can try or where to start?
>>
>> Well there are any number of things see my Q above
>>
>> BUT
>> the quick fix will be to just set up a new account for yourself.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20130105/0337a582/attachment.html>