[TIP] Using xlaunch

[Condex]

Hi there!

I've been testing the trick to run games, but got the same lock as arabis. Card is also a ATI x700 (Acer notebook).

I'm gonna test those links you gave to see if they work...

Condex

[Condex]

I've tried Ubuntu Forum solution, so:

Changed: ServerCmd=/usr/bin/Xgl -br -ac -accel glx:pbuffer -accel xv:pbuffer
To: ServerCmd=/usr/bin/Xgl -br -ac -accel glx:pbuffer -accel xv:fbo -xorgAc

in /usr/kde/3.5/share/config/kdm/kdmrc

Start kdm, login and run:

$ openttd : (SDL game, windowed). Runs bad, problems with colors
$ DISPLAY=:93 openttd : No problem with colors, runs fine.

Now I'm emerging an OpenGL based game... tuxracer

Edit:

-OpenTTD also runs ok in Fullscreen
- $ DISPLAY=:93 tuxracer runs perfect.

I think we got a solution

[truc]

This looks interesting, and I have a few questions:

_ Does this mean, it's now to run possible to run properly an opengl app inside XGL? Or did I misunderstood:
_ Do you launch the game on the same DISPLAY where Xgl is?
_ If so, are you able to make use of the 'extra-keys' of your keyboard?
_ Why 93 in "DISPLAY=:93 ppracer", does XGL on DISPLAY 93? I know the Xorg.93.log, but don't really know anything else?
_ If it's not on the same on the same Display, then, is there a similar trick for 'normal' xorg ?


If it's on the same DISPLAY then, I don't see the point of using xlaunch, otherwise it may be possible to modify xlaunch so that it also works for ATI users a few more questions then:

• Assuming the user is using only Xgl right now (since I don't know yet the answer of my previous questions )
  Is this correct:
  • If Xgl was started with the xorgAc the only thing needed to run 'program' is to launch it with

    Code: Select all

    DISPLAY=:93 program

    else we need to launch it with

    Code: Select all

    LD_PRELOAD=/usr/lib/libGL.so.1.2 program

    (but this last trick doesn't work so well, so warn the user of the other trick)
    right

Thanks in advance.

[Condex]

I'll try to answer your questions, with my "little knowledge"...

If you open a terminal (yakuake in this case) and type: $ps guax, you'll find, among other things this 2 lines:

Code: Select all

root     10622  4.0  5.8  69748 60384 ?        SL   00:46   0:03 /usr/bin/Xgl -br -ac -accel glx:pbuffer -accel xv:fbo -xorgAc -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-QJQMWg
root     10623  2.1  0.8  16416  9032 tty7     SLs+ 00:46   0:02 /usr/bin/Xorg -br -ac vt7 -auth /tmp/.Xgl-auth-GKgB8a -nolisten tcp :93 -terminate

So:

• XGL is running on :0, you launch the game on :93, then it's not running on XGL.
• About "extra keys": I'm having problems to get them running on normal XGL (I think that it's a problem with XORG 7.1). Solved it (really crappy solution) on XGL, but I've not tested them on :93.
• Why 93? It seems that Xorg is running on :93.

I remember trying :93 without -xorgAc and got a hardlock.

I've not used LD_PRELOAD=... to run the games I've tested, just run that DISPLAY=:93 program

Also, I've tested Enemy Territory @ 93 and it runs ok.

Well, I hope someone with more knowledge can expand this info

Condex-

[truc]

thanks Condex for your answers.

That's funny since the guy (in the thread arabis mentionned above) said

this DOES NOT start a new X server so it works on ati cards

But looking at your process(es?), I can see two xservers, one of them is Xgl, while the other is xorg


Anyway, if you don't mind I'd had a few more questions:

• _ Do you always(as soon as you start Xgl) have these two process

  Code: Select all

  root     10622  4.0  5.8  69748 60384 ?        SL   00:46   0:03 /usr/bin/Xgl -br -ac -accel glx:pbuffer -accel xv:fbo -xorgAc -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-QJQMWg
  root     10623  2.1  0.8  16416  9032 tty7     SLs+ 00:46   0:02 /usr/bin/Xorg -br -ac vt7 -auth /tmp/.Xgl-auth-GKgB8a -nolisten tcp :93 -terminate

  Or is it just when you start a game(with DISPLAY=:93 game) ?
  I can see the -terminate option for Xorg:

  -terminate
  causes the server to terminate at server reset, instead of continuing to run

  but I just want to be sure I understand:
  _ When you exit the game, is the xorg process still running? If so do you have something special to do to go back to your desktop ?
  _ Can you switch from inside the game to your desktop? if so, how? ctrl-alt-f7 and ctrl-alt-f(93+7)
  _ Are you using xbindkeys for your multimedia keys or somethings else?

Even if I don't own an ATI card, I suppose I'll can answer some of these questions once I'll get home, but, it's in approximately 2 weeks, and I'm just curious

thanks again;)

[arabis]

Hi!
Here some clues:
first from http://gentoo-wiki.com/HOWTO_XGL/Tips_a ... 2C_etc..29

But.. Remember that at this time Xgl runs on another Xorg server (that usually is :93, but can be another too...) So you can safetly start applications on :93, when they're not supported by Xgl. Just remember three things:

1. Start Xgl with the -xorgAc parameter. This will allow network access (but also remember that this can be unsafe in a non-local network)

Second my pstree:

Code: Select all

eric@ferrari ~ $ pstree
init─┬─acpid
     ├─6*[agetty]
     ├─cgwd
     ├─compiz
     ├─cpufreqd
     ├─cron
     ├─cupsd
     ├─6*[dbus-daemon]
     ├─dbus-launch
     ├─dcopserver
     ├─dhcpcd
     ├─events/0
     ├─gconfd-2
     ├─gdm───gdm─┬─Xgl───Xorg
     │           └─startkde─┬─kwrapper
     │                      └─ssh-agent
     ├─hald───hald-runner─┬─hald-addon-acpi
     │                    ├─hald-addon-keyb
     │                    └─hald-addon-stor
     ├─ifplugd
     ├─ivman
     ├─kaccess
     ├─kded
     ├─kdeinit─┬─artsd
     │         ├─kio_file
     │         ├─klauncher
     │         ├─konsole───bash───pstree
     │         ├─mozilla-launche───firefox-bin───3*[{firefox-bin}]
     │         ├─superkaramba
     │         └─xmms───2*[{xmms}]
     ├─kdesktop
     ├─khelper
     ├─khpsbpkt
     ├─kicker
     ├─kmix
     ├─knodemgrd_0
     ├─knotify
     ├─ksmserver
     ├─ksoftirqd/0
     ├─kswapd0
     ├─kthread─┬─aio/0
     │         ├─kacpid
     │         ├─kblockd/0
     │         ├─kcryptd/0
     │         ├─khubd
     │         ├─kpsmoused
     │         ├─kseriod
     │         ├─ondemand
     │         ├─2*[pdflush]
     │         └─reiserfs/0
     ├─oooqs2─┬─ksysguardd
     │        └─soffice───soffice.bin───3*[{soffice.bin}]
     ├─slmodemd
     ├─syndock───syndaemon
     ├─syslog-ng
     └─udevd

So This means (correct me if I'm wrong) that Xgl runs on top of Xorg. Starting Xgl with the -xorgAc parameter makes you able to start apps on the Xorg running underneat Xgl.
If you look in your /var/log/, you will notice that, as an xgl user, you don't use Xorg.0.log but something like Xorg.93.log or Xorg.94.log (look at your modified time of the file of Xorg.0.log). I use myself Xorg.94.log but I don't know why it's not rather Xorg.93.log.
So I use

Code: Select all

DISPLAY=:94 googleearth 

and it works very well. Ppracer works very well also using this tip. But I get a segfault with doom3-demo. Right now, I don't use a window manager with this, but by if I quit, for example, Googleearth, I just return to my desktop.

[truc]

So inside XGL, in a term,

Code: Select all

echo $DISPLAY

will give you 0 while if you run

Code: Select all

DISPLAY=:94 xterm

and then inside this term you run the same command it would give you 94 right?

When you're 'inside' googleearth, is it fullscreen? Can you go back to your desktop without 'quitting' googleearth ? If so how?

[arabis]

So inside XGL, in a term,

Code: Select all

echo $DISPLAY

will give you 0

It gives ":1.0"

while if you run

Code: Select all

DISPLAY=:94 xterm

and then inside this term you run the same command it would give you 94 right?

Yes: ":94.0"

When you're 'inside' googleearth, is it fullscreen? Can you go back to your desktop without 'quitting' googleearth ? If so how?

Googleearth appears in a window over the desktop. If, previously, by starting Googleearth in Xgl, I set my window size to something smaller than my screen, I will see some part of my Xgl desktop underneat. But I can not bring a window started with xgl in front of the window started with DISPLAY:94.

[truc]

just an idea: let the user choose his own name for the link? so that you can xlaunch ut, if "ut" is the name that the user chooses for the link to /home/blacktiger/games/ut2004/System/ut2004-bin-linux-amd64

Also like this idea because xut2004-bin-linux-amd64 is still much text to write To choose an own command would be great so f.e just xut and game starts *yipie*

Hi again:)

As suggested, you can now with version=20060808 of xlaunch (grab it here ) , you can now chose the name you want xlaunch to use when creating links for a program that doesn't appear in your PATH

• (actually, you can even chose a name for a program that does appear in your path, to achieve this you just need to give the (full|relative)path to the program as an argument to xlaunch when creating links, for example:

  Code: Select all

  xlaunch --addlink ~/scripts /usr/bin/xterm
  We are now going to create 2 links for /usr/bin/xterm, the first will be :
  
  /home/truc/scripts/xterm --> /usr/bin/xterm
  And the second will be:
  /home/truc/scripts/xxterm --> /home/scripts/xlaunch
  
  But you can change 'xterm' to be whatever you want, just enter the name
  you would like to use to launch your program (/usr/bin/xterm ).
  Leave blank to use default one
  blahblah
  
  Created link /home/truc/scripts/blahblah --> /usr/bin/xterm
  Created link /home/truc/scripts/xblahblah --> /home/scripts/xlaunch
  

  then running xblahblah will be the same as running xlaunch xterm
  Well, that's not the point here... And that may look a bit useless..
  anyway..hum..
  
  
  Back to our good'ol example: BlackTiger
  • all you need to do now is,

    Code: Select all

    xlaunch --addlink /home/blacktiger/games/ut2004/System/ut2004-bin-linux-amd64

    And then chose a decent name (ut ) and you're done
    or xlaunch --addlink path/to/writable/directory /home/blacktiger/games/ut2004/System/ut2004-bin-linux-amd64 if you don't have write permission on the directory where xlaunch is stored. (I'm sure you do have it, but eh.. that's an example.. )

If you find something wrong, please tell me!



======

And for ATI users, I'm not sure what to do, it should work now for you with the latest ATI driver, but it seems it doesn't work for everybody. I'm a bit lost, I'll try to look all this more deeply later.

[katanagari]

hi

thanks for the script truc, it works great for me!

I have a suggestion: Running a fullscreen app (ie. stepmania) in a dual monitor machine, the image appears between the two screens. I think it'd be great if xlaunch disables xinerama when it's enabled or, even better, place the window on the correct position.

I tried adding "-xinerama" to the X server's parameters but it appears the following message after a time:

Code: Select all

xplayer@frankie$ ./xlaunch stepmania
xauth:  timeout in locking authority file /root/.xauthlsm8Kq

However, after pressing Ctrl+C, it works. Is there a better way to do what I want?

By the way, English is not my first language (as you can read) so if you can't understand me, please ask.

[CoffeeBuzz]

I've added this to the xgl-coffee overlay under x11-misc/xlaunch
Its keyworded -*

Use at your own risk!

[truc]

thanks for the script truc, it works great for me!

I have a suggestion: Running a fullscreen app (ie. stepmania) in a dual monitor machine, the image appears between the two screens. I think it'd be great if xlaunch disables xinerama when it's enabled or, even better, place the window on the correct position.

I tried adding "-xinerama" to the X server's parameters but it appears the following message after a time:

Code: Select all

xplayer@frankie$ ./xlaunch stepmania
xauth:  timeout in locking authority file /root/.xauthlsm8Kq

Hi, thanks for the suggestion:) , I didn't even think about xinerama users.
Since I don't know xinerama very well, I'd have some questions about.
But first some questions on how you "start X":

• Are you using xdm (or one of its friend) or do you issue startx
  I don't know yet exactly how xdm & Cie work, but I'd like to understand this:

  xplayer@frankie$ ./xlaunch stepmania
  xauth: timeout in locking authority file /root/.xauthlsm8Kq

  It should be /home/your_name/ shouldn't it be?
  • Note : it looks like you're trying to use the XPLAYER feature, for your information, you don't need to su to xplayer before running ./xlaunch stepmania: run it as your normal user ( katanagari ? ), xlaunch will use sudo to launch it as $XPLAYER (see III) d) Using XPLAYER )
  
  
  There's an option for xauth to bypass 'Xauthority lock'. but I'd like to know how you 'start x'
  if you're not using a login manager (xdm, kdm and so on), do you log in as root then su to katanagari, or do you log in directly as katanagari
  In both case, once you're katanagari, can you post the result of :

  Code: Select all

  echo "$HOME --- $XAUTHORITY"

  and

  Code: Select all

   ps aux | grep -i x

  and also:

  Code: Select all

   ps aux | grep -i dm

And for xinerama:

• How do you disable xinerama?
  Assuming I disabled it, on which display/screen()? the application is now supposed to run on?
  EDIT: if we don't disable xinerama, I think it's possible to chose to display weither on screen 0 (eg: DISPLAY:1.0) or on the second screen 1 with DISPLAY=:1.1 ) (or the third screen and so on..)
  This needs a little thinking.
  I will probably have other questions. but that's enough for now

However, after pressing Ctrl+C, it works. Is there a better way to do what I want?

could you also give me the results of:

Code: Select all

ls -l $HOME/.Xauthority
# and 
xauth list

I would be glad if you answered as many questions as you can, thanks again


@CoffeBuzz
Thanks, but for latter versions I suppose I can just pm you?

[katanagari]

I'm here again! (I wasn't at home this time)

I see you have a lot of questions... well, I'll try to help you as much as I can

Are you using xdm (or one of its friend) or do you issue startx

I use gdm (as a good gnome user)

It should be /home/your_name/ shouldn't it be?

Yea.... this happened because I logged to xplayer from root. Running xlaunch from my normal account (yes, it's katanagari) doesn't appear that.

In both case, once you're katanagari, can you post the result of :

Code: Select all

echo "$HOME --- $XAUTHORITY"

OK. Nothing strange here:

Code: Select all

katanagari@frankie ~ $ echo "$HOME --- $XAUTHORITY"
/home/katanagari --- /home/katanagari/.Xauthority

and

Code: Select all

ps aux | grep -i x 

I'll only show the interesting processes:

Code: Select all

katanagari@frankie ~ $ ps axu | grep -i x
root      9351  2.1  8.4  95348 87392 ?        SL   01:41   0:01 /usr/bin/Xgl :1 -br -ac -accel glx:pbuffer -accel xv -auth /var/gdm/:1.Xauth -nolisten tcp vt7
root      9352  1.8  1.3  17764 13996 tty7     SLs+ 01:41   0:00 /usr/bin/Xorg -br vt7 -auth /tmp/.Xgl-auth-cisLiu -nolisten tcp :94 -terminate

and

Code: Select all

ps aux | grep -i dm 

Code: Select all

katanagari@frankie ~ $ ps axu | grep -i dm
root      9346  0.0  0.1   9900  1708 ?        Ss   01:41   0:00 /usr/bin/gdm
root      9347  0.0  0.2  10436  2404 ?        S    01:41   0:00 /usr/bin/gdm
root      9351  1.7  9.3 104988 96840 ?        SL   01:41   0:01 /usr/bin/Xgl :1 -br -ac -accel glx:pbuffer -accel xv -auth /var/gdm/:1.Xauth -nolisten tcp vt7

As you can see, I'm using Xgl and Xorg 7.0. About Xgl's parameters, I followed the Gentoo Wiki's XGL Howto.

How do you disable xinerama?

I disabled it just adding "-xinerama" to the new X server's params.

if we don't disable xinerama, I think it's possible to chose to display weither on screen 0 (eg: DISPLAY:1.0) or on the second screen 1 with DISPLAY=:1.1 ) (or the third screen and so on..)

It seems that X doesn't work this way. I tried launching "DISPLAY=:1.0 xterm" and opens a xterm window, but when I launch "DISPLAY=:1.1 xterm" appears the following message:

Code: Select all

xterm Xt error: Can't open display: :1.1

Maybe if I disable xinerama, I can use "DISPLAY=:1.0" or "DISPLAY=:1.1" to select which Screen to use.

could you also give me the results of:

Code: Select all

ls -l $HOME/.Xauthority
# and
xauth list

The results:

Code: Select all

katanagari@frankie ~ $ ls -l /home/katanagari/.Xauthority
-rw------- 1 katanagari katanagari 170 Aug 20 01:42 /home/katanagari/.Xauthority

katanagari@frankie ~ $ xauth list
frankie/unix:0  MIT-MAGIC-COOKIE-1  12a23568ccf6d34d3e35481a64724a94
frankie/unix:1  MIT-MAGIC-COOKIE-1  f2548fb5c5f9f34eeadfa863c3404c7c
localhost.localdomain/unix:1  MIT-MAGIC-COOKIE-1  f2548fb5c5f9f34eeadfa863c3404c7c

[truc]

thanks!

To be sure I understood you correctly:

now, when launching xlaunch as katanagari, you no longer have the "timout in locking authority" right?
And if you add -xinerama the serverargs, then it kinda works, but you can't choose on which screen you want stepamania to run on, right?

assming you've just started stepania with xlaunch, and with the -xineram option, the game now runs on only one screen? (no longer in the middle of nowhere, :/ )

question: what do you have on the others screen? your desktop? a black screen? ;.

I think I can add the -xinerama option as a default server option, what do you think?

[katanagari]

now, when launching xlaunch as katanagari, you no longer have the "timout in locking authority" right?

right

And if you add -xinerama the serverargs, then it kinda works, but you can't choose on which screen you want stepamania to run on, right?
assming you've just started stepania with xlaunch, and with the -xineram option, the game now runs on only one screen? (no longer in the middle of nowhere, :/ )

Yea, all of that was right The game appears on the first monitor.

question: what do you have on the others screen? your desktop? a black screen? ;.

On the other monitor. the screen turns black.. moreover, the "No signal" dialog appears, so the monitor gets disconnected.
Edit: I noticed that the second screen disconnects only if the app is running in fullscreen mode. However, running a non fullscreen app (ie. xterm), both screens works as usual.

I think I can add the -xinerama option as a default server option, what do you think?

I don't know if this option affects single screen users in some way. If not, I suppose that it'd be OK.

Edit (again): Now It would be cool if we can choose which screen to use... I have to investigate about that (any recommended doc but xorg's manpages?)

[nnd]

Hello, truc!
Thank you for you program. Unfortunately I have some problems...
After doing:

Code: Select all

$xlaunch --addlink /home/nnd/ut2004/System/ut2004-bin-linux-amd64
$xut

I have:

Code: Select all

Starting /home/nnd/scripts/ut on DISPLAY 1
xrdb: Connection refused
xrdb: Can't open display ':1'
xmodmap:  unable to open display ':1'

Could you please help me?

[truc]

nnd
as usual a few questions:

• Does xlaunch /home/nnd/ut2004/System/ut2004-bin-linux-amd64 works ? (launch UT on an other display)

  Code: Select all

  Starting /home/nnd/scripts/ut on DISPLAY 1
  xrdb: Connection refused
  xrdb: Can't open display ':1'
  xmodmap:  unable to open display ':1' 

  Looks like no new Xserver is started
  
  Is there anything interesting in /var/log/Xorg.1.log ?
  
  can you post the output of

  Code: Select all

  ls -l /home/nnd/scripts | grep ut

[nnd]

truc,
xlaunch /home/nnd/ut2004/System/ut2004-bin-linux-amd64 has the same output:

Code: Select all

Starting /home/nnd/ut2004/System/ut2004-bin-linux-amd64 on DISPLAY 1
xrdb: Connection refused
xrdb: Can't open display ':1'
xmodmap:  unable to open display ':1'

I haven't noticed any errors in /var/log/Xorg.1.log

Code: Select all

> ls -l /home/nnd/scripts | grep ut
lrwxrwxrwx 1 nnd users    51 2006-08-21 18:24 ut -> /home/nnd/ut2004/System/ut2004-bin-linux-amd64
lrwxrwxrwx 1 nnd users    30 2006-08-21 18:24 xut -> /home/nnd/scripts/xlaunch

[truc]

@katanagari

• question: what do you have on the others screen? your desktop? a black screen? ;.

  On the other monitor. the screen turns black.. moreover, the "No signal" dialog appears, so the monitor gets disconnected.
  Edit: I noticed that the second screen disconnects only if the app is running in fullscreen mode. However, running a non fullscreen app (ie. xterm), both screens works as usual.

  My point, with this script, was also to have my multimedia keys working inside a fullscreen game. If you remember, in III) c) Making your multimedia keys working , I said since you don't start any window manager on this new DISPLAY, you can put set your game not to be fullscreen (window mode) and it'll look like it's fullscreen.
  I suppose you can do the same, and then you won't have anymore your other screen turning off (and you'll also have your fun keys working )

  I think I can add the -xinerama option as a default server option, what do you think?

  I don't know if this option affects single screen users in some way. If not, I suppose that it'd be OK.

  I tried adding -xinerama to my default server arguments, and I didn't notice any differences. So I think I will keep it inside for the next release (unless someone tells me why I shouldn't )

  Edit (again): Now It would be cool if we can choose which screen to use... I have to investigate about that (any recommended doc but xorg's manpages?)

  That would be great! But I have no good doc in mind right now

@nnd

• Do you have any specific configuration I should be aware of?
  How do you 'startx' , with the good'ol startx command, or with a Display manager like xdm, gdm, kdm (...) ?
  
  Does

  Code: Select all

  xinit /home/nnd/ut2004/System/ut2004-bin-linux-amd64 -- :1

  work?
  (assuming DISPLAY=:1 is free, if it's not, try with :2 and so on..)
  If it doesn't can you copy and paste the output?(run it in a terminal..)
  
  Can you also give the output of

  Code: Select all

  xauth list

thanks

[nnd]

trac,

I'm using no specific configuration, just starting X with kdm.

Code: Select all

xinit /home/nnd/ut2004/System/ut2004-bin-linux-amd64 -- :1

X starts, but then it's terminates because of:

Code: Select all

/home/nnd/ut2004/System/ut2004-bin-linux-amd64: error while loading shared libraries: ./libSDL-1.2.so.0: cannot open shared object file: No such file or directory

The same output is with other displays(:2, :3, etc)
This file is in my ut2004/System dir, I know I have to determine some variable... could you please help me to remember which?

Code: Select all

>xauth list
nnd.progtech.ru:0  MIT-MAGIC-COOKIE-1  b2960394f22ac4f568d0cc98753b059f
[fe80::204:61ff:fea1:70d]:0  MIT-MAGIC-COOKIE-1  b2960394f22ac4f568d0cc98753b059f
nnd/unix:0  MIT-MAGIC-COOKIE-1  1a9117aa7650d2119eb1e70c5a25d487
linux/unix:0  MIT-MAGIC-COOKIE-1  b2960394f22ac4f568d0cc98753b059f
linux/unix:1  MIT-MAGIC-COOKIE-1  286b215351239c996efc436d83de1d2f

[truc]

Code: Select all

/home/nnd/ut2004/System/ut2004-bin-linux-amd64: error while loading shared libraries: ./libSDL-1.2.so.0: cannot open shared object file: No such file or directory

Does

Code: Select all

/home/nnd/ut2004/System/ut2004-bin-linux-amd64

works then? It looks like it doesn't, and it would explain why you don't have any X error.

[nnd]

truc,

Sorry, it was a stupid question... solved it with ln -s /usr/lib64/libSDL-1.2.so.0 ~/ut2004/System/libSDL-1.2.so.0

But now i have the following issue:
I run ut with the xut îê xlaunch /home/nnd/ut2004/System/ut2004-bin-linux-amd64 command.
It opens me a window in the _same_ tty whith the Xglx heading, shows splash and dies with the same output:

Code: Select all

Starting /home/nderkach/ut2004/System/ut2004-bin-linux-amd64 on DISPLAY 3
xrdb: Connection refused
xrdb: Can't open display ':{1,2,3, etc}'

Err, I think I know that is the problem... I tried to run all commands you suggested with sudo, it started ut on the other display but with bad textures(it look like if I start it in Xgl).

So the problem is that my user has no permissions to start X. How to solve it?

[CoffeeBuzz]

@CoffeBuzz
Thanks, but for latter versions I suppose I can just pm you?

Certainly. A PM would be fine, either on this forum or http://forums.xgl-coffee.org/

I try to check back here from time to time but I'm fairly busy these days. Thanks for the work on this script. The ebuild I whipped up is fairly basic, not sure if you've used it but if you have and think something should be changed in the way the package is installed, let me know as well.

[truc]

I will ask again the same questions, does

Code: Select all

/home/nnd/ut2004/System/ut2004-bin-linux-amd64

works now?

if it works, then

• does

  Code: Select all

  xinit /home/nnd/ut2004/System/ut2004-bin-linux-amd64 -- :1

  works ?
  if it doesn't then
  • does

    Code: Select all

    xinit -- :1

    works?
  fi

fi


And

How do you 'startx' , with the good'ol startx command, or with a Display manager like xdm, gdm, kdm (...) ?

thank you

[truc]

truc.
You really do not understand me?
I said I can run all these commands but from root(sudo) because my user do not have permissions to run X and I don't want give them
Thank YOU

I really didn't..
EDIT: oh, looks like you deleted your post


Well, I'd still like to know how to you startx ? do you use the root user to startx? or are you using a display manager?

So your user does not have permissions to run X:(IMO that's a specific configuration I'd like to be aware of), what does this exaclty mean?

Code: Select all

groups your_user

which groups does it belong to?

AFAIK your user doesn't have to be in the video group to be able to startx. So what did you do exactly?

And all this probably explains your ~/Xauthority file (lot of entry).

May I ask why you want such a behaviour?

And to answer to your main question, it's probably possible to play with xauth, have a look here