Hi,
X starts fine under a user with local administrator rights.
When logged in to the same machine with another user that has no admin rights,
X won't start.
The log indicates that another X were already running, but it's not.
Output on the console is:
giving up.
/bin3/startxwin: Connection
I wonder if the issue is that the less privileged user cannot create a log
file, socket, or similar thing is one of the usual places. This would look like
failure to create a lock file because another user has it open. Either way,
creating the lock file fails.
Regards -- Eliot Moss
Sent via
On 18/02/2011 17:52, Alexander Pokluda wrote:
When I give the -fullscreen argument to XWin using two screens, a
window pops up with the error
InitOutput - Couldn't add screen 1
and
Aborted (core dumped)
is printed in the bash shell.
The following command lines work perfectly:
On 05/03/2011 14:07, Paul Maier wrote:
X starts fine under a user with local administrator rights.
When logged in to the same machine with another user that has no admin rights,
X won't start.
The log indicates that another X were already running, but it's not.
Output on the console is:
On 04/02/2011 17:14, Ken Olum wrote:
From: Jon TURNEY jon.tur...@dronecode.org.uk
Date: Mon, 24 Jan 2011 18:38:36 +
Once I say -wgl, direct rendering no longer works. That is, if I
don't set LIBGL_ALWAYS_INDIRECT, then I get a long (infinite?)
sequence of errors like
On 15/02/2011 13:16, Alexander Pokluda wrote:
I don't have any idea why the XDMCP request packets from XWin would be
dropped by the network either.
What I thought was interesting is that the value of Connection 4 in
the XDMCP REQUEST packet from XWin in the Wireshark trace is
Hi Jon,
great help, yes the problem is related to /tmp/.X11-unix/X0 and /tmp/.X0-lock.
When these files are not present, the underpriviledged user can start X fine.
The situation is now as follows:
SCENARIO 1:
Log in as administrator. Start X.
Reboot PC and log in as normal user.
- The files
