Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
finottiOffline
Post subject: [mostly SOLVED] problem running two X sessions  PostPosted: 14.02.2011, 11:02



Joined: 2010-09-12
Posts: 293

Status: Offline
Hi,

I now have problems running two session of X in parallel. One is started from KDM, the other from going to a VT and typing "startx -- :1".

This has always worked before. I use KDE as the main one and fluxbox as the second one. Fluxbox does start, but I have no background and cannot start any programs (with the mouse nor with my keyborad shortcuts).

Here is some info:
      Code:

debian[~]$ infobash -v3
Host/Kernel/OS  "debian" running Linux 2.6.37-0.slh.21-aptosid-amd64 x86_64 [ aptosid 2010-02 Îá¿ÏÎµÏ - kde-full - (201009132215) ]
CPU Info        (1) Intel Core2 Duo E8400 @ 6144 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 2999.604 MHz ]
                (2) Intel Core2 Duo E8400 @ 6144 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 2999.604 MHz ]
Videocard       nVidia G86 [GeForce 8500 GT]  X.Org 1.9.4  [ 1280x1024@50.0hz ]
Network cards   nVidia MCP55
                nVidia MCP55
Processes 148 | Uptime 34min | Memory 951.8/8005.8MB | HDD ST3500320AS,WDC WD1500ADFD-0,WDC WD1001FALS-0,ST31000528AS Size 2650GB (33%used) | GLX Renderer GeForce 8500 GT/PCI/SSE2 | GLX Version 3.3.0 NVIDIA 260.19.36 | Client Shell | Infobash v3.34


You can see errors below. (I am not running Virtial Box, BTW.)
      Code:

test[~]% cat .xsession-errors
Xsession: X session started for test at Mon Feb 14 05:30:32 EST 2011
/etc/X11/Xsession.d/98vboxadd-xclient: line 43: /usr/bin/VBoxClient: No such file or directory
/etc/X11/Xsession.d/98vboxadd-xclient: line 44: /usr/bin/VBoxClient: No such file or directory
/etc/X11/Xsession.d/98vboxadd-xclient: line 46: /usr/bin/VBoxClient: No such file or directory
/etc/X11/Xsession.d/98vboxadd-xclient: line 48: /usr/bin/VBoxClient: No such file or directory
xmodmap:  unable to open file '/home/test/.Xmodmap' for reading
xmodmap:  1 error encountered, aborting.
Failed to read: session.styleOverlay
Setting default value
Failed to read: session.screen0.maxIgnoreIncrement
Setting default value
Failed to read: session.screen0.maxDisableMove
Setting default value
Failed to read: session.screen0.maxDisableResize
Setting default value
Failed to read: session.screen0.defaultDeco
Setting default value
Failed to read: session.screen0.noFocusWhileTypingDelay
Setting default value
Failed to read: session.screen0.tooltipDelay
Setting default value
Failed to read: session.screen0.allowRemoteActions
Setting default value
Failed to read: session.screen0.clientMenu.usePixmap
Setting default value
Failed to read: session.screen0.tabs.maxOver
Setting default value
Failed to read: session.screen0.tabs.intitlebar
Setting default value
Failed to read: session.styleOverlay
Setting default value
Failed to read: session.screen0.maxIgnoreIncrement
Setting default value
Failed to read: session.screen0.maxDisableMove
Setting default value
Failed to read: session.screen0.maxDisableResize
Setting default value
Failed to read: session.screen0.defaultDeco
Setting default value
Failed to read: session.screen0.noFocusWhileTypingDelay
Setting default value
Failed to read: session.screen0.tooltipDelay
Setting default value
Failed to read: session.screen0.allowRemoteActions
Setting default value
Failed to read: session.screen0.clientMenu.usePixmap
Setting default value
Failed to read: session.screen0.tabs.maxOver
Setting default value
Failed to read: session.screen0.tabs.intitlebar
Setting default value
Failed to read: session.styleOverlay
Setting default value
Failed to read: session.screen0.maxIgnoreIncrement
Setting default value
Failed to read: session.screen0.maxDisableMove
Setting default value
Failed to read: session.screen0.maxDisableResize
Setting default value
Failed to read: session.screen0.defaultDeco
Setting default value
Failed to read: session.screen0.noFocusWhileTypingDelay
Setting default value
Failed to read: session.screen0.tooltipDelay
Setting default value
Failed to read: session.screen0.allowRemoteActions
Setting default value
Failed to read: session.screen0.clientMenu.usePixmap
Setting default value
Failed to read: session.screen0.tabs.maxOver
Setting default value
Failed to read: session.screen0.tabs.intitlebar
Setting default value
Failed to read: session.screen0.slit.acceptKdeDockapps
Setting default value
Failed to read: session.screen0.titlebar.left
Setting default value
Failed to read: session.screen0.titlebar.right
Setting default value
NOTE: child process received `Goodbye', closing down
WARNING: waitpid failed pid:4653 errno:10: file ../../../ipc/chromium/src/base/process_util_posix.cc, line 237
WARNING: waitpid failed pid:4653 errno:10: file ../../../ipc/chromium/src/base/process_util_posix.cc, line 237
WARNING: Failed to deliver SIGKILL to 4653!(3).: file ../../../ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc, line 162


And, if necessary, Xorg.0.log can be found at http://www.math.utk.edu/~finotti/misc/Xorg.0.log.

Any help would be appreciated...

Luis

[Edit] P.S.: starting fluxbox alone for the same user from KDM works fine.


Last edited by finotti on 15.02.2011, 19:23; edited 1 time in total
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: RE: problem running two X sessions  PostPosted: 15.02.2011, 02:47



Joined: 2010-09-12
Posts: 293

Status: Offline
I assume no one has an idea of what is the problem. Could someone check if it is possible to do it? At least I would know if it is a problem with my systems (my laptop has the same problem), which might help to find the problem...

Thanks,

Luis
 
 View user's profile Send private message  
Reply with quote Back to top
muchan
Post subject: RE: problem running two X sessions  PostPosted: 15.02.2011, 11:55
Moderator


Joined: 2010-09-11
Posts: 468

At least, you can check startx --:0 and --:1 from init 3, (kdm not running yet)
and know if problem is startx itself, or starting X as second instance.
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: Re: RE: problem running two X sessions  PostPosted: 15.02.2011, 19:22



Joined: 2010-09-12
Posts: 293

Status: Offline
      muchan wrote:
At least, you can check startx --:0 and --:1 from init 3, (kdm not running yet)
and know if problem is startx itself, or starting X as second instance.


Thank you very much muchan for your recommendation. It did help. I found out I could not run fluxbox with --:1 even if no other X session was running. Running KDE worked fine.

I realized that the problem is that fluxbox is now trying to use DISPLAY :0 even when running in :1...

After trying many things, what worked was to change my ".xsessions" to
      Code:

#!/bin/sh
DISPLAY=":1.0" startfluxbox

(Added the DISPLAY part.)

So, it will only work with "startx -- :1", which is not ideal, but I can live with it. There is certainly something wrong here, as it should not be necessary to tell fluxbox which is the display...

Thanks for your help,

Luis
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio