 Notes |
(0001809)
damjan (reporter)
2005-04-29 17:54
|
To me it does not look like a font path problem.
I belive you tried it to run under a non-root account and you don\'t have access rights to /tmp/.X11-directoy.
I put a note in postinstall script and in /opt/csw/etc/vncservers file.
# Non-root users must have read/write permissions
# on /tmp/.X11-unix to be able
# to run VNC server (e.g.: chmod 01777 /tmp/.X11-unix)
On Linux and some other systems, these ACL flags are default. On Solaris only root has rw permissions. I guess, becuase their Xsun is run as root via dtlogin.
I could put that chmod command in postinstall script, but I don\'t think it is a good idea. Some would think it is a security problem, that\'s why I give a note, that for non-root users, some permissions have to be adjusted.
Let me know if it works for you and I am open for suggestions how to inform user better. |
|
(0003311)
james (reporter)
2006-03-19 17:31
|
What is the status of this bug? |
|
(0003315)
damjan (reporter)
2006-03-20 05:02
|
It works if users follow the manual. It you run Xvnc as root, you don\'t need to do anything. It works. If you want to start Xvnc as a normal user you need to follow the instructions which are given in postinstall and
/opt/csw/etc/vncservers file.
Solaris default permissions do now allow Xservers to run as non-root users (that is differnet to e.g. Linux or AIX). I don\'t think blastwave package should change any permissions. All I can do is, to write these instruction on a more visible place. |
|
(0007004)
maciej (manager)
2009-11-18 09:34
|
It's indeed the case that users don't have the permission to write to /tmp/.X11-unix. Here's what truss is saying about vncserver:
7653: so_socket(1, 2, 0, "", 1) = 4
7653: umask(0) = 022
7653: mkdir("/tmp/.X11-unix", 01777) Err#17 EEXIST
7653: unlink("/tmp/.X11-unix/X1") Err#2 ENOENT
7653: bind(4, 0xFFBFF770, 19, 3) Err#13 EACCES
maciej@build8st [build8st]:~ > touch /tmp/.X11-unix/foo
touch: /tmp/.X11-unix/foo cannot create
maciej@build8st [build8st]:~ > ls -ld /tmp/.X11-unix
drwxrwxr-x 2 root root 176 Jul 13 23:31 /tmp/.X11-unix
I agree that the vncserver package should not change any file permissions in the filesystem, but I also see that the error message from vncserver is not really helpful. I don't have a good idea how to change this error message: wrap vncserver in a script? It doesn't sound elegant, but it would probably work. |
|
(0007012)
maciej (manager)
2009-11-18 23:07
|
vncserver-1.3.10,REV=2009.11.18 wraps the vncserver script into something that tests if /tmp/.X11-unix is writable by the world or by the current user and displays a helpful error message when not.
Updated package is in testing. |
|
(0007014)
maciej (manager)
2009-11-19 00:53
|
Testing it on Solaris 8:
maciej@build8st [build8st]:~ > vncserver
The /tmp/.X11-unix directory is not world-writable. This is a known issue on
Solaris 8. If you need to run vncserver as a regular user, you need to make
this file writable by your user (e.g. world-writable).
sudo chmod o+w /tmp/.X11-unix
For more information, see:
http://www.opencsw.org/mantis/view.php?id=942 [^]
On Solaris 10 it runs as expected. |
|
(0007017)
maciej (manager)
2009-11-21 20:26
|
Found a problem with running the wrapper on Solaris 10:
maciej@vsol01 ~ $ vncserver :1
find: stat() error /tmp/.X11-unix: No such file or directory
The /tmp/.X11-unix directory is not world-writable. This is a known issue on
Solaris 8. If you need to run vncserver as a regular user, you need to make
this file writable by your user (e.g. world-writable).
sudo chmod o+w /tmp/.X11-unix
For more information, see:
http://www.opencsw.org/mantis/view.php?id=942 [^]
maciej@vsol01 ~ $ ls -l /tmp/.X11-unix
gls: /tmp/.X11-unix: No such file or directory |
|
(0007073)
maciej (manager)
2009-12-08 20:05
|
Fixed, closing the bug. |
|
(0008946)
skayser (administrator)
2011-03-28 10:50
|
On multi-user systems like Sun Ray installtions, administrators might not want to grant world-write permissions on /tmp/.X11-unix.
There's also the less invasive possibility for users to start vncserver with the "-nolisten local" option which skips the unix domain socket listener creation. I'll attach a patch to the wrapper script which also points out and honours this possibility. |
|
vncserver-also-use-nolisten.diff [^] (1,218 bytes) 2011-03-28 10:50 
