Welcome to awesome bug tracking system.

FS#844 - Awesome does not work with FreeNX

Attached to Project: awesome
Opened by Johannes (vali) - Friday, 12 November 2010, 16:36 GMT
Last edited by Uli Schlachter (psychon) - Thursday, 06 October 2011, 15:58 GMT
Task Type Bug Report
Category Core
Status Closed
Assigned To No-one
Operating System Linux
Severity Low
Priority Normal
Reported Version 3.4.8
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


How to reproduce:

* Install a FreeNX server
* I used this guide:
* Connect to the server with a FreeNX client

Since I have no login manager I used custom session settings on client side:
* 'Run the default X client script on server'
* 'New virtual desktop'

In the server side config file node.conf:

* The !M screen is displayed for a short time, then the session crashes.

I attached the session log file found on server side (/home/user/.nx/cache-unix-desktop/C-*/session).
   session (1.9 KiB)
This task depends upon

Closed by  Uli Schlachter (psychon)
Thursday, 06 October 2011, 15:58 GMT
Reason for closing:  Not a bug
Additional comments about closing:  $ grep nxagent /var/log/*
Oct 6 15:10:48 orzechmac kernel: [ 8793.623211] nxagent[25376]: segfault at 0 ip 00000000004a7c56 sp 00007fff233004d0 error 4 in nxagent[400000+4d1000]

Come back when the NULL pointer dereference in nxagent is fixed.
Comment by Uli Schlachter (psychon) - Friday, 12 November 2010, 16:38 GMT
The log says:

feh ERROR: Can't open X display. It *is* running, yeah?

Did you also report a bug against feh?
Comment by Johannes (vali) - Friday, 12 November 2010, 17:37 GMT
No I did not, but I just disabled the wallpaper_cmd line in the theme to prevent feh from being executed. It's still the same behaviour. I attached the new session log file.
Comment by Uli Schlachter (psychon) - Saturday, 13 November 2010, 13:39 GMT
What I was trying to say is that your setup is broken. Awesome and feh both got a problem connecting to the X server which seems to me like it indicates a problem with your X server and not with awesome.

To me this seems like the FreeNX server dies shortly after awesome started.

For debugging this, you might try to add sth like this in front of the place where awesome is started:

Comment by Johannes (vali) - Saturday, 13 November 2010, 14:31 GMT
FreeNX does work perfectly with other window managers.

I added the output you recommended, any ideas?
   session (7.3 KiB)
Comment by Uli Schlachter (psychon) - Saturday, 13 November 2010, 21:36 GMT
No idea, from this info I'd guess the X server dies and awesome doesn't properly handle this (which I hopefully partly fixed in git).

Can you run some other X client before starting awesome?
E.g. this:

xcalc & sleep 3
Comment by Johannes (vali) - Saturday, 13 November 2010, 22:41 GMT
The X server definitely dies not until awesome is started. E.g. I tried running xterm without any problems. However, as soon as I start awesome the X server crashes.
Comment by Uli Schlachter (psychon) - Sunday, 14 November 2010, 07:39 GMT
Ah, so the X server really crashes?! Why does it crash? Why is it awesome's bug if the X server crashes?
Comment by Michael Lee (mlee) - Sunday, 14 November 2010, 14:55 GMT

I've been having the same problem.

I'm running archlinux (completely up-to-date).
I'm using archlinux-git from aur (also up-to-date).

Note: I also had this issue with awesome 3.4.8 about a month ago and remember getting similar errors (couldn't connect to or open systray). I decided this morning to move back to the git version and see if it was working again.

I did same the things you suggested to Johannes. xcalc does run.

In the attached archive, you'll find:

tmp/nxinfo (my DISPLAY and xdpyinfo)
tmp/awesome-errors (redirect of awesome error output)
bin/ (script to run awesome with the output redirect)
session (nx session file for this run)

Is there anything else you would like me to try?

Comment by Uli Schlachter (psychon) - Sunday, 14 November 2010, 20:51 GMT
All the different backtraces that I have seen point to random places in awesome. All of them more or less suggest that the conncetion to the X server died (which is sth that awesome is quite bad at handling). They don't tell me anything more than that. :(
Comment by Alex (Rooz) - Wednesday, 16 February 2011, 08:59 GMT

I've had the same problem as everyone else. I'm running awesome v3.4.9 with a default configuration (except for some key bindings) and used the same FreeNX guide from the arch linux wiki.

18:08 < Rooz> psychon: i found one of the lines freenx/X/awesome dies on
18:10 < Rooz> i disabled the wibox, then it runs
18:10 < Rooz> but i fails if i do rightclick > popup (default setup)
18:10 < Rooz> *it
18:10 < Rooz> it fails on the line wibox.screen = screen_index
18:10 < Rooz> in
18:16 < Rooz> awesome itselfs runs nicely

Is there anything beyond the wibox.screen line I can check?

Comment by Uli Schlachter (psychon) - Wednesday, 16 February 2011, 09:56 GMT
So in other words, it crashes whenever awesome tries to create a window. Meh?!

You could try adding a line "wibox.visible = false" before the "wibox.screen = ..." line. That would tell us if it crashes when awesome creates a window or when awesome makes a window visible.

Also, google found:

"When troubleshooting, edit /etc/nxserver/node.conf to enable logging to a specific log file, set the log level (NX_LOG_LEVEL=3) and to keep the log files (SESSION_LOG_CLEAN=0). Then look in ~/.nx of the user trying to log in to find out more when in trouble."