Comment 67 for bug 1251281

Revision history for this message
Ryan Tandy (rtandy) wrote :

I tried to verify this, but bug 1416081 blocks testing with tightvncserver and xrdp as well as with x2goserver. Would anyone be willing to upload the patches in that bug to -proposed as well? I will fill in the SRU paperwork shortly. In the mean time, ppa:rtandy/flashback contains the necessary patches for testing.

My testing steps:

- install gnome-session-flashback and tightvncserver,
- (trusty/utopic): install gnome-session-bin from -proposed,
- create ~/.vnc/xstartup with appropriate contents:

(vivid, session managed by gnome-session:)

export XDG_CURRENT_DESKTOP="GNOME-Flashback:Unity"
export STARTUP="gnome-session --session=gnome-flashback-metacity --disable-acceleration-check"
exec /etc/X11/Xsession

(vivid, session managed by upstart:)

export DESKTOP_SESSION=gnome-flashback-metacity
export XDG_CURRENT_DESKTOP="GNOME-Flashback:Unity"
exec /etc/X11/Xsession gnome-session

(trusty/utopic, session managed by gnome-session:)

export STARTUP="gnome-session --session=gnome-flashback --disable-acceleration-check"
exec /etc/X11/Xsession

(trusty/utopic, session managed by upstart:)

export DESKTOP_SESSION=gnome-fallback
export XDG_CURRENT_DESKTOP=Unity
exec /etc/X11/Xsession gnome-session

- chmod +x ~/.vnc/xstartup,
- run vncserver,
- from another host, run vncviewer.

The keyboard problem I mentioned earlier seems to be related to bug 568401 and bug 658723 (but not bug 112955 or bug 112309). Basically Super modifier is always active when connected over VNC (or xrdp, as it uses VNC behind the scenes). FreeNX/X2Go don't seem to have this problem.

With regards to this bug specifically, AFAICT the gnome-session changes in -proposed (supporting the --disable-acceleration-check switch, and applying it to upstart-managed gnome-flashback sessions) are working, but I'd love if a second person would confirm that!