[Bug 506160] [NEW] xstartup apps not run when starting vnc server
Tpugliese
thomas.pugliese at gmail.com
Mon Jan 11 21:53:55 UTC 2010
Public bug reported:
After I start vnc using vncserver, when I connect, the screen is empty.
No window manager or apps have started. In past releases, the gnome-
session would start. Here is my system info.
Description: Ubuntu 9.10
Release: 9.10
tightvncserver:
Installed: 1.3.9-4
Candidate: 1.3.9-4
Version table:
*** 1.3.9-4 0
500 http://mirrors.xmission.com karmic/universe Packages
100 /var/lib/dpkg/status
This is the command line output:
thomas at bitbucket:~$ vncserver
Found /usr/share/tightvnc-java for http connections.
New 'X' desktop is bitbucket:1
Starting applications specified in /home/thomas/.vnc/xstartup
Log file is /home/thomas/.vnc/bitbucket:1.log
Here are the contents of the log file:
thomas at bitbucket:~$ cat .vnc/bitbucket\:1.log
11/01/10 15:35:26 Xvnc version TightVNC-1.3.9
11/01/10 15:35:26 Copyright (C) 2000-2007 TightVNC Group
11/01/10 15:35:26 Copyright (C) 1999 AT&T Laboratories Cambridge
11/01/10 15:35:26 All Rights Reserved.
11/01/10 15:35:26 See http://www.tightvnc.com/ for information on TightVNC
11/01/10 15:35:26 Desktop name 'X' (bitbucket:1)
11/01/10 15:35:26 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
11/01/10 15:35:26 Listening for VNC connections on TCP port 5901
11/01/10 15:35:26 Listening for HTTP connections on TCP port 5801
11/01/10 15:35:26 URL http://bitbucket:5801
Invalid MIT-MAGIC-COOKIE-1 keyxrdb: Can't open display ':1'
Invalid MIT-MAGIC-COOKIE-1 keyxsetroot: unable to open display ':1'
The "Invalid MIT-MAGIC-COOKIE-1" messages led me to believe that the xauth authorities were not being set correctly. The problem appears to be caused by the fact that /usr/bin/vncserver calls xauth to add $host:$displayNumber and $host/unix:$displayNumber as display entries that can connect to the server but further down the file, the DISPLAY environment variable is set to :1 when using unix domain sockets (which it does). Because DISPLAY is set to :1 but only $host:1 is allowed to connect, the apps in ~/.vnc/xstartup cannot run. I worked around this problem by changing this line in /usr/bin/vncserver
$ENV{DISPLAY}= ":$displayNumber";
to
$ENV{DISPLAY}= "$host:$displayNumber";
Now the startup apps run and I get my gnome session. Unforntunately, all
the keys are mapped incorrectly so it is unusable. This already appears
to be a known issue
https://bugs.launchpad.net/ubuntu/+source/tightvnc/+bug/237362
** Affects: tightvnc (Ubuntu)
Importance: Undecided
Status: New
--
xstartup apps not run when starting vnc server
https://bugs.launchpad.net/bugs/506160
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
More information about the universe-bugs
mailing list