Upon logging in to an x2go gnome session from a remote Windows XP box, I found that the Applications menu would not show up. It would highlight when selected but nothing would drop down.
At first I suspected the client, but after trying different versions on different platforms (XP, Windows 7, Ubuntu) I found that they all exhibited the same problem.
I've verified that x2go has an applications symlink in /etc/x2go pointing to /usr/share/applications and that both are readable.
I can't seem to find any sort of error message in either the system or session logs that might provide a clue as to the cause, even with the log level set to debug.
Nothing else seems to be affected. The System and Places menus appear as they should, I can launch any installed application manually and all I've tried work normally. I can even add launchers to the panel and those will work.
I've also installed nxserver-freenx and verified proper operation using a Windows NX client. The applications menu appears normally if I use nx server/client instead of x2go.
Could x2go actually be looking in the wrong place for the menu?
The issue may affect other WMs but I have no others installed in order to verify this.
Steps to Reproduce:
1. Log in from a remote machine using x2go with a gnome session
2. Attempt to open the applications menu on the panel
No menu appears.
The application menu should drop down.
Gnome 3 I guess? There are comments (mostly on Ubuntu) that the default session with its 3d thingies) could cause a problem like that:
Have you tried with a custom session sarting gnome fallback? (the 2D-only one)
Also it may be worth trying with a new clean user, just in case
The applications symlink in /etc/x2go should not matter, it is only used for the "published applications" session type
Gnome 2.32 actually. I haven't switched to Gnome 3 and don't use any 3D desktop compositing since sessions on this machine are primarily remote.
I did try creating a session with a brand new user, but it exhibited the same issue.
Very old bug report, x2go and nx had numerous releases since then. I am cleaning the bug now, but don't hesitate to reopen if it ever is still a problem in current envs