| View previous topic :: View next topic |
| Author |
Message |
DingbatCA Guru


Joined: 07 Jul 2004 Posts: 318 Location: Portland Or
|
Posted: Wed May 23, 2007 11:20 pm Post subject: Looking to set DMX up, and failing. |
|
|
Two systems. My workstation and laptop. I want the workstation (192.168.1.100) to be the master, and I want the laptop (192.168.1.103) to just be a screen. Will add other "screens" later
On the workstation I run | Code: | | /usr/bin/Xdmx :1 -display workstation:0 -display laptop:0 +xinerama |
But I get an error "(Fatal Error) dmx: dmxOpenDisplay: Unable to open display 192.168.1.100:0"
on the laptop I run | Code: | | /usr/bin/Xdmx :1 -display laptop:0 +xinerama |
But I get the same error.
What am I missing! I am feeling very dumb here. |
|
| Back to top |
|
 |
JeliJami Veteran


Joined: 17 Jan 2006 Posts: 1086 Location: Belgium
|
Posted: Thu May 24, 2007 10:55 am Post subject: |
|
|
You should not get an error running
| Code: | | Xdmx :1 -display :0 |
If you use ip-addresses (or host names), make sure that the X servers are running with tcp listening on, and make sure you don't have any firewall rules blocking anything _________________ Unanswered Post Initiative | Search | FAQ
Former username: davjel |
|
| Back to top |
|
 |
DingbatCA Guru


Joined: 07 Jul 2004 Posts: 318 Location: Portland Or
|
Posted: Thu May 24, 2007 3:52 pm Post subject: |
|
|
The single command works. | Code: | | Xdmx :1 -display :0 |
Run that on my laptop and it goes into client mode. I can check to see it is setup with nmap. I can see that port 6001 is open: | Code: | nmap 192.168.1.103
Starting Nmap 4.20 ( http://insecure.org ) at 2007-05-24 08:49 PDT
Interesting ports on 192.168.1.103:
Not shown: 1694 closed ports
PORT STATE SERVICE
22/tcp open ssh
111/tcp open rpcbind
6001/tcp open X11:1
MAC Address: XX:XX:XX:XX:XX:XX (Intel Corporate) |
From my workstation I run: | Code: | #Xdmx :1 -display 192.168.1.103:0 +xinerama
(II) dmx: Generation: 1
(II) dmx: DMX version: 1.2.20040630 (DMX Project)
(II) dmx: DMX Build OS: Linux 2.6.21-gentoo x86_64 ()
(II) dmx: DMX Build Compiler: gcc 3.4.6
(II) dmx: DMX Execution OS: Linux 2.6.21-gentoo #1 SMP PREEMPT Tue May 1 21:24:16 PDT 2007
(II) dmx: DMX Execution Host: deadsparc
(II) dmx: MAXSCREENS: 16
(II) dmx: Using configuration from command line
(II) dmx: Added 192.168.1.103:0 at 0 0
(Fatal Error) dmx: dmxOpenDisplay: Unable to open display 192.168.1.103:0 |
But, as you can see, I am not able to connect. No firewalls turned on. What step am i missing? |
|
| Back to top |
|
 |
JeliJami Veteran


Joined: 17 Jan 2006 Posts: 1086 Location: Belgium
|
Posted: Thu May 24, 2007 3:58 pm Post subject: |
|
|
| DingbatCA wrote: | | Code: | nmap 192.168.1.103
6001/tcp open X11:1
|
From my workstation I run: | Code: | #Xdmx :1 -display 192.168.1.103:0 +xinerama
(Fatal Error) dmx: dmxOpenDisplay: Unable to open display 192.168.1.103:0 |
|
try it with 192.168.1.03:1
port where X listens on: 6000+displaynumber _________________ Unanswered Post Initiative | Search | FAQ
Former username: davjel |
|
| Back to top |
|
 |
DingbatCA Guru


Joined: 07 Jul 2004 Posts: 318 Location: Portland Or
|
Posted: Thu May 24, 2007 4:08 pm Post subject: |
|
|
From my desktop...
| Code: |
Xdmx :1 -display 192.168.1.103:1 +xinerama
(II) dmx: Generation: 1
(II) dmx: DMX version: 1.2.20040630 (DMX Project)
(II) dmx: DMX Build OS: Linux 2.6.21-gentoo x86_64 ()
(II) dmx: DMX Build Compiler: gcc 3.4.6
(II) dmx: DMX Execution OS: Linux 2.6.21-gentoo #1 SMP PREEMPT Tue May 1 21:24:16 PDT 2007
(II) dmx: DMX Execution Host: deadsparc
(II) dmx: MAXSCREENS: 16
(II) dmx: Using configuration from command line
(II) dmx: Added 192.168.1.103:1 at 0 0
Xlib: connection to "192.168.1.103:1.0" refused by server
Xlib: No protocol specified
(Fatal Error) dmx: dmxOpenDisplay: Unable to open display 192.168.1.103:1
|
|
|
| Back to top |
|
 |
JeliJami Veteran


Joined: 17 Jan 2006 Posts: 1086 Location: Belgium
|
Posted: Fri May 25, 2007 7:12 am Post subject: |
|
|
I think i misread your previous post
is there an X server running on the laptop?
is it listening on tcp/6000? (for display :0)
check the X process with
it probably runs with -nolisten tcp _________________ Unanswered Post Initiative | Search | FAQ
Former username: davjel |
|
| Back to top |
|
 |
DingbatCA Guru


Joined: 07 Jul 2004 Posts: 318 Location: Portland Or
|
Posted: Fri May 25, 2007 7:44 am Post subject: |
|
|
ok, here is the feed back, and I think I see the problem
| Code: | # ps -fp $(pgrep X)
UID PID PPID C STIME TTY STAT TIME CMD
root 7616 7615 0 00:38 tty7 S<s+ 0:00 X :0 -nolisten tcp -br -auth /root/.serverauth.7599 -deferglyphs 16
root 7662 7650 0 00:39 pts/1 S+ 0:00 Xdmx :1 -display :0
|
Would it be the "-nolisten"? And how do I get rid of that!? |
|
| Back to top |
|
 |
JeliJami Veteran


Joined: 17 Jan 2006 Posts: 1086 Location: Belgium
|
Posted: Fri May 25, 2007 8:25 am Post subject: |
|
|
| DingbatCA wrote: | ok, here is the feed back, and I think I see the problem
| Code: | # ps -fp $(pgrep X)
UID PID PPID C STIME TTY STAT TIME CMD
root 7616 7615 0 00:38 tty7 S<s+ 0:00 X :0 -nolisten tcp -br -auth /root/.serverauth.7599 -deferglyphs 16
root 7662 7650 0 00:39 pts/1 S+ 0:00 Xdmx :1 -display :0
|
Would it be the "-nolisten"? And how do I get rid of that!? |
It certainly is (see my first reply)!
I'm using xdm and I can control the X servers xdm starts in the file /etc/X11/xdm/Xservers. _________________ Unanswered Post Initiative | Search | FAQ
Former username: davjel |
|
| Back to top |
|
 |
DingbatCA Guru


Joined: 07 Jul 2004 Posts: 318 Location: Portland Or
|
Posted: Fri May 25, 2007 4:09 pm Post subject: |
|
|
Found how to load X with out the -nolisten option, on the client.
Dont forget to do an xhost + IP_of_master.
So then, on the master I run
| Code: | | Xdmx :1 -display 192.168.1.103:0 +xinerama -input :0 |
And I get a DMX console window, not a new screen. I can move the mouse around in this window, and it works, but how do I get it as a new desktop, and not an application? |
|
| Back to top |
|
 |
Sadako Advocate


Joined: 05 Aug 2004 Posts: 3753 Location: sleeping in the bathtub
|
Posted: Sat May 26, 2007 1:00 am Post subject: |
|
|
I haven't used it in a couple of months, but here is the command I used to start dmx;
| Code: | | XSESSION=fluxbox startx -- /usr/bin/Xdmx :2 -display 127.0.0.1:1 -display 192.168.1.4:1 -ignorebadfontpaths |
The main part here is the "-- /usr/bin/dmx", which makes the startx script(s) use Xdmx rather than the usual X server.
Of course, you can use anything within /etc/X11/Sessions/ as your "XSESSION", or use another method to have the server start what you want,
but I'm lazy and find this to be the easiest way.
One thing I feel I should share from my experiences, although it might not apply to you,
is that in order to be able to drag windows from one display to another you must have xinerama support in the window manager being used
(via USE=xinerama, which is typically enabled by default IIRC), and you must have
| Code: | | Option "Xinerama" "true" | in the ServerFlags section of xorg.conf on each machine you wish to use.
You should be able to set it up so that xinerama is only enabled in a certain layout, and then pass that layout to the startx command via the -layout option (xinerama disables DRI on one of my systems).
Edit: I should point that in the example command above, I started the "host" X servers as display :1 on both machines, and the xdmx display on :2.
Mostly this is because I was still running my regular session on :0 while experimenting, but also because I discovered the -nolisten option only seemed to apply to :0,
and this seemed less hassle that editing the start up scripts which would just get replaced the next time xorg-server was emerged.
I don't know how much of this is actually necessary, though. _________________ "You have to invite me in" |
|
| Back to top |
|
 |
DingbatCA Guru


Joined: 07 Jul 2004 Posts: 318 Location: Portland Or
|
Posted: Sat May 26, 2007 4:42 am Post subject: |
|
|
Thank you Hopeless. Command works. But I had to add the local system with xhost. I can get every thing running with raw X sessions. That is good progress! But the problem is KDE and -nolisten. First problem was finding where that option is set. It took some hunting but I found it.
| Code: | | /usr/kde/3.5/share/config/kdm/kdmrc |
And the -nolisten option is stored in:
| Code: | | ServerArgsLocal=-nolisten tcp |
But when I remove the -nolisten option kdm does not start.
Any ideas? |
|
| Back to top |
|
 |
Sadako Advocate


Joined: 05 Aug 2004 Posts: 3753 Location: sleeping in the bathtub
|
Posted: Sat May 26, 2007 5:57 am Post subject: |
|
|
| DingbatCA wrote: | But when I remove the -nolisten option kdm does not start.
Any ideas? | Sorry, not a kde user.
Only thing I have to ask is, when you say you remove the -nolisten option, do you just remove "-nolisten", or "-nolisten tcp"?
It sounds to me like you're just removing -nolisten, but tcp is an argument to the -nolisten flag, as in "don't listen for tcp traffic".
Sorry if I misunderstand you, and even if I happen to be right, I wouldn't think something as simple as this would stop kde from starting up.
Are there no error reports or logs as to why it failed to start? _________________ "You have to invite me in" |
|
| Back to top |
|
 |
DingbatCA Guru


Joined: 07 Jul 2004 Posts: 318 Location: Portland Or
|
Posted: Sat May 26, 2007 6:56 am Post subject: |
|
|
from X --help
| Code: | | -nolisten string don't listen on protocol |
I feel very dumb... Will test it in the morning. |
|
| Back to top |
|
 |
Sadako Advocate


Joined: 05 Aug 2004 Posts: 3753 Location: sleeping in the bathtub
|
Posted: Sat May 26, 2007 12:26 pm Post subject: |
|
|
| DingbatCA wrote: | from X --help
| Code: | | -nolisten string don't listen on protocol |
I feel very dumb... Will test it in the morning. |
Good luck with it. _________________ "You have to invite me in" |
|
| Back to top |
|
 |
DingbatCA Guru


Joined: 07 Jul 2004 Posts: 318 Location: Portland Or
|
Posted: Sun May 27, 2007 2:31 am Post subject: |
|
|
Well, I have Xdmx running. How do I get KDE, Gnome, or TWM to load after I have Xdmx running?
This just causes an error, with any XSESSION i choose. twm, gnome ,kde-3.5...... And yes I have all parts updated for my system.
| Code: | | XSESSION=twm startx -- /usr/bin/Xdmx :2 -display 127.0.0.1:1 -display 192.168.1.4:1 -ignorebadfontpaths |
But a raw X session and this works, but I have no environment when I do so.
| Code: | | Xdmx :2 -display 127.0.0.1:1 -display 192.168.1.4:1 -ignorebadfontpaths |
|
|
| Back to top |
|
 |
JeliJami Veteran


Joined: 17 Jan 2006 Posts: 1086 Location: Belgium
|
Posted: Sun May 27, 2007 10:32 am Post subject: |
|
|
the startkde command takes a display argument:
| Code: | | $ startkde -display :2 |
does that work? _________________ Unanswered Post Initiative | Search | FAQ
Former username: davjel |
|
| Back to top |
|
 |
DingbatCA Guru


Joined: 07 Jul 2004 Posts: 318 Location: Portland Or
|
Posted: Sun May 27, 2007 6:54 pm Post subject: |
|
|
No luck. Here is my current order of operations.
That starts up X.
| Code: | #xhost + 127.0.0.1
#/usr/bin/Xdmx :2 -display 127.0.0.1:0 -display 192.168.1.103:0 -ignorebadfontpaths +xinerama |
Every thing comes on-line at this point and I can drag the mouse across both screens. But, how to I lunch an application into this environment? I tried the:
| Code: | | startkde -display :2 |
And had no luck. So currently I am starting xdmx on just my desktop trying to figure out how to lunch an application into that environment, like xterm, or something that simple. `xterm -display :2` I will go for the big stuff like kdm when I can get the little things working. Any more ideas out there? |
|
| Back to top |
|
 |
Sadako Advocate


Joined: 05 Aug 2004 Posts: 3753 Location: sleeping in the bathtub
|
Posted: Sun May 27, 2007 11:38 pm Post subject: |
|
|
| DingbatCA wrote: | Well, I have Xdmx running. How do I get KDE, Gnome, or TWM to load after I have Xdmx running?
This just causes an error, with any XSESSION i choose. twm, gnome ,kde-3.5...... And yes I have all parts updated for my system.
| Code: | | XSESSION=twm startx -- /usr/bin/Xdmx :2 -display 127.0.0.1:1 -display 192.168.1.4:1 -ignorebadfontpaths |
But a raw X session and this works, but I have no environment when I do so.
| Code: | | Xdmx :2 -display 127.0.0.1:1 -display 192.168.1.4:1 -ignorebadfontpaths |
| It only occured to me a couple of minutes ago while watching tv, but tvm is not a valid value for the XSESSION variable.
The XSESSION variable uses one of the scripts in /etc/X11/Sessions/, so for twm you would use XSESSION=Xsession, and for kde you would use something like XSESSION=kde-3.5 (I'm not sure, as I don't have kde installed at the moment, but I know it is versioned, see what you have in the Sessions directory).
Anyway, the command should work without the XSESSION at the start, it would just use your default session as defined in /etc/rc.conf.
I doubt something as simple as this would stop everyting working, but I thought I should point it out just in case.
Edit: note they are also case sensitive. _________________ "You have to invite me in" |
|
| Back to top |
|
 |
Pegasus87 Guru

Joined: 09 Sep 2004 Posts: 367
|
Posted: Mon May 28, 2007 12:29 pm Post subject: |
|
|
I've just the same problems here....
My situation:
Desktop PC with IP 192.168.2.17 und Laptop with IP 192.168.2.20, both running KDE und I'm logged in as normal user.
On Laptop I run | Code: | | Xdmx :1 -display :0 | as normal user and get a grey display with a X-mouse.
Well, on Desktop I'm running now | Code: | | Xdmx :2 -display 127.0.0.1:0 -display 192.168.2.20:0 +xinerama -input :0 | as normal user and now I have a wonderfull grey display to with a mouse that I can move from from one display to the other one. Great!
But now i want to run KDE...
| Code: | | XSESSION=fluxbox startx -- /usr/bin/Xdmx :2 -display 127.0.0.1:0 -display 192.168.2.20:0 +xinerama -input :0 | (or XSESSION=kde-3.5.5) brings me the same as without setting the XSESSION variable or running startx...... what I'm doing wrong? |
|
| Back to top |
|
 |
Pegasus87 Guru

Joined: 09 Sep 2004 Posts: 367
|
Posted: Mon May 28, 2007 5:32 pm Post subject: |
|
|
Now it works..... ok, not all:
I started Xdmx with | Code: | | Xdmx :2 -display 127.0.0.1:0 -display 192.168.2.20:0 +xinerama -input :0 -ignorebadfontpath | and run in another term this | Code: | | sleep 5 && DISPLAY=:2 startkde |
The screen loads quiet more than once, but after that I get an KDE Desktop. Of course its the second session of kde and I get a lot of errors (e.g. firefox is already running). An there is another problem: The keyboard doesn't work!!
How do I close the old KDE session and how can I get my Keyboard working??
Here is the log of Xdmx:
| Code: | (**) dmx: dmxErrorHandler: BadName (named color or font does not exist)
(**) dmx: Major opcode: 152 (RENDER)
(**) dmx: Minor opcode: 30 (RenderSetPictureFilter)
(**) dmx: ResourceID: 0x3015934
(**) dmx: Failed serial number: 7821087
(**) dmx: Current serial number: 7821427
(**) dmx: dmxErrorHandler: BadName (named color or font does not exist)
(**) dmx: Major opcode: 152 (RENDER)
(**) dmx: Minor opcode: 30 (RenderSetPictureFilter)
(**) dmx: ResourceID: 0x3015949
(**) dmx: Failed serial number: 7821181
(**) dmx: Current serial number: 7821427
(**) dmx: dmxErrorHandler: BadName (named color or font does not exist)
(**) dmx: Major opcode: 152 (RENDER)
(**) dmx: Minor opcode: 30 (RenderSetPictureFilter)
(**) dmx: ResourceID: 0x3015958
(**) dmx: Failed serial number: 7821251
(**) dmx: Current serial number: 7821427
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
(II) dmx: Generation: 9
(II) dmx: DMX version: 1.2.20040630 (DMX Project)
(II) dmx: MAXSCREENS: 16
(II) dmx: Using configuration from command line
(II) dmx: Added 127.0.0.1:0 at 0 0
(II) dmx: Added 192.168.2.20:0 right of 127.0.0.1:0
(II) dmx[o0/127.0.0.1:0]: No Xdmx server running on backend
(II) dmx[o0/127.0.0.1:0]: Name of display: 127.0.0.1:0.0
(II) dmx[o0/127.0.0.1:0]: Version number: 11.0
(II) dmx[o0/127.0.0.1:0]: Vendor string: The X.Org Foundation
(II) dmx[o0/127.0.0.1:0]: Vendor release: 70200000
(II) dmx[o0/127.0.0.1:0]: Dimensions: 1280x1024 pixels
(II) dmx[o0/127.0.0.1:0]: 7 depths on screen 0: 24,1,4,8,15,16,32
(II) dmx[o0/127.0.0.1:0]: Depth of root window: 24 planes (24)
(II) dmx[o0/127.0.0.1:0]: Number of colormaps: 1 min, 1 max
(II) dmx[o0/127.0.0.1:0]: Options: backing-store no, save-unders no
(II) dmx[o0/127.0.0.1:0]: Window Manager running: yes
(**) dmx[o0/127.0.0.1:0]: Window manager running -- colormaps not supported
(II) dmx[o0/127.0.0.1:0]: 1280x1024+0+0 on 1280x1024 at depth=24, bpp=32
(II) dmx[o0/127.0.0.1:0]: 0x23 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff *
(II) dmx[o0/127.0.0.1:0]: 0x24 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x25 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x26 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x27 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x28 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x29 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x2a DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(**) dmx[o1/192.168.2.20:0]: Xdmx:schlepptop:1,0 also running on 192.168.2.20:0
(II) dmx[o1/192.168.2.20:0]: Name of display: 192.168.2.20:0.0
(II) dmx[o1/192.168.2.20:0]: Version number: 11.0
(II) dmx[o1/192.168.2.20:0]: Vendor string: The X.Org Foundation
(II) dmx[o1/192.168.2.20:0]: Vendor release: 70101000
(II) dmx[o1/192.168.2.20:0]: Dimensions: 1024x768 pixels
(II) dmx[o1/192.168.2.20:0]: 7 depths on screen 0: 24,1,4,8,15,16,32
(II) dmx[o1/192.168.2.20:0]: Depth of root window: 24 planes (24)
(II) dmx[o1/192.168.2.20:0]: Number of colormaps: 1 min, 1 max
(II) dmx[o1/192.168.2.20:0]: Options: backing-store no, save-unders no
(II) dmx[o1/192.168.2.20:0]: Window Manager running: yes
(**) dmx[o1/192.168.2.20:0]: Window manager running -- colormaps not supported
(II) dmx[o1/192.168.2.20:0]: 1024x768+0+0 on 1024x768 at depth=24, bpp=32
(II) dmx[o1/192.168.2.20:0]: 0x23 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff *
(II) dmx[o1/192.168.2.20:0]: 0x24 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x25 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x26 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x27 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x28 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x29 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x2a DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x43 TrueColor 32b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: DPMS 1.1 (on, enabled, 3600 3600 7200)
(II) dmx[o1/192.168.2.20:0]: DPMS 1.1 (on, enabled, 0 0 0)
(..) dmx: On 192.168.2.20:0/60817418: Xdmx:schlepptop:1,0
(II) dmx[o0/127.0.0.1:0]: (request) s=1280x1024+0+0 r=1280x1024+0+0 @0,0 (0) (be=1280x1024 depth=24 bpp=32)
(II) dmx[o1/192.168.2.20:0]: (request) s=1024x768+0+0 r=1024x768+0+0 @0,0 (1) (be=1024x768 depth=24 bpp=32)
(II) dmx[o0/127.0.0.1:0]: s=1280x1024+0+0 r=1280x1024+0+0 @0,0 (be=1280x1024 depth=24 bpp=32)
(II) dmx[o1/192.168.2.20:0]: s=1024x768+0+0 r=1024x768+0+0 @1280,0 (be=1024x768 depth=24 bpp=32)
(II) dmx: Using old bounding box (2304x1024) instead of new (2304x1024)
(II) dmx: XSync batching with 100 ms interval
(II) dmx: Shadow framebuffer support disabled
(II) dmx[i0/:0]: Using backend input from :0
(II) dmx[i0/:0]: Locating devices on :0 (XInputExtension version 1.3)
(II) dmx[i0/:0]: 0 Keyboard1 XKeyboard
(II) dmx[i0/:0]: 1 Mouse1 XPointer
(II) dmx[i0/:0]: Added backend-mou as pointer device called Mouse0 [core]
(II) dmx[i0/:0]: Added backend-kbd as keyboard device called Keyboard0 [core]
(II) dmx[i0/:0]: Using Keyboard0 and Mouse0 as true core devices
(II) dmx[i0/:0]: XKEYBOARD: keycodes = xfree86+aliases(qwertz)
(II) dmx[i0/:0]: XKEYBOARD: symbols = pc(pc105)+de
(II) dmx[i0/:0]: XKEYBOARD: geometry = (null)
(II) dmx[i0/:0]: XKEYBOARD: From device: xfree86 pc(pc105)+de
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Could not init font path element /usr/share/fonts/OTF, removing from list!
(II) dmx: ===== Start of Summary =====
(II) dmx: 2 screens configured with Xinerama (2304 1024)
(II) dmx: 8 visuals at depth 24:
(II) dmx: 0x23 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x24 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x25 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x26 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x27 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x28 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x29 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x2a DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0 visuals at depth 1:
(II) dmx: 0 visuals at depth 4:
(II) dmx: 0 visuals at depth 8:
(II) dmx: 0 visuals at depth 15:
(II) dmx: 0 visuals at depth 16:
(II) dmx: 0 visuals at depth 32:
(II) dmx: 2 devices:
(II) dmx: Id Name Classes
(II) dmx: 0 Mouse0 val btn fb/ptr [i0/:0/id1=Mouse1] core
(II) dmx: 1 Keyboard0 key foc fb/kbd [i0/:0/id0=Keyboard1] core
(II) dmx: ===== End of Summary =====
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
(II) dmx: Generation: 10
(II) dmx: DMX version: 1.2.20040630 (DMX Project)
(II) dmx: MAXSCREENS: 16
(II) dmx: Using configuration from command line
(II) dmx: Added 127.0.0.1:0 at 0 0
(II) dmx: Added 192.168.2.20:0 right of 127.0.0.1:0
(II) dmx[o0/127.0.0.1:0]: No Xdmx server running on backend
(II) dmx[o0/127.0.0.1:0]: Name of display: 127.0.0.1:0.0
(II) dmx[o0/127.0.0.1:0]: Version number: 11.0
(II) dmx[o0/127.0.0.1:0]: Vendor string: The X.Org Foundation
(II) dmx[o0/127.0.0.1:0]: Vendor release: 70200000
(II) dmx[o0/127.0.0.1:0]: Dimensions: 1280x1024 pixels
(II) dmx[o0/127.0.0.1:0]: 7 depths on screen 0: 24,1,4,8,15,16,32
(II) dmx[o0/127.0.0.1:0]: Depth of root window: 24 planes (24)
(II) dmx[o0/127.0.0.1:0]: Number of colormaps: 1 min, 1 max
(II) dmx[o0/127.0.0.1:0]: Options: backing-store no, save-unders no
(II) dmx[o0/127.0.0.1:0]: Window Manager running: yes
(**) dmx[o0/127.0.0.1:0]: Window manager running -- colormaps not supported
(II) dmx[o0/127.0.0.1:0]: 1280x1024+0+0 on 1280x1024 at depth=24, bpp=32
(II) dmx[o0/127.0.0.1:0]: 0x23 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff *
(II) dmx[o0/127.0.0.1:0]: 0x24 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x25 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x26 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x27 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x28 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x29 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: 0x2a DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(**) dmx[o1/192.168.2.20:0]: Xdmx:schlepptop:1,0 also running on 192.168.2.20:0
(II) dmx[o1/192.168.2.20:0]: Name of display: 192.168.2.20:0.0
(II) dmx[o1/192.168.2.20:0]: Version number: 11.0
(II) dmx[o1/192.168.2.20:0]: Vendor string: The X.Org Foundation
(II) dmx[o1/192.168.2.20:0]: Vendor release: 70101000
(II) dmx[o1/192.168.2.20:0]: Dimensions: 1024x768 pixels
(II) dmx[o1/192.168.2.20:0]: 7 depths on screen 0: 24,1,4,8,15,16,32
(II) dmx[o1/192.168.2.20:0]: Depth of root window: 24 planes (24)
(II) dmx[o1/192.168.2.20:0]: Number of colormaps: 1 min, 1 max
(II) dmx[o1/192.168.2.20:0]: Options: backing-store no, save-unders no
(II) dmx[o1/192.168.2.20:0]: Window Manager running: yes
(**) dmx[o1/192.168.2.20:0]: Window manager running -- colormaps not supported
(II) dmx[o1/192.168.2.20:0]: 1024x768+0+0 on 1024x768 at depth=24, bpp=32
(II) dmx[o1/192.168.2.20:0]: 0x23 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff *
(II) dmx[o1/192.168.2.20:0]: 0x24 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x25 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x26 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x27 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x28 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x29 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x2a DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o1/192.168.2.20:0]: 0x43 TrueColor 32b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx[o0/127.0.0.1:0]: DPMS 1.1 (on, enabled, 3600 3600 7200)
(II) dmx[o1/192.168.2.20:0]: DPMS 1.1 (on, enabled, 0 0 0)
(..) dmx: On 192.168.2.20:0/60817418: Xdmx:schlepptop:1,0
(II) dmx[o0/127.0.0.1:0]: (request) s=1280x1024+0+0 r=1280x1024+0+0 @0,0 (0) (be=1280x1024 depth=24 bpp=32)
(II) dmx[o1/192.168.2.20:0]: (request) s=1024x768+0+0 r=1024x768+0+0 @0,0 (1) (be=1024x768 depth=24 bpp=32)
(II) dmx[o0/127.0.0.1:0]: s=1280x1024+0+0 r=1280x1024+0+0 @0,0 (be=1280x1024 depth=24 bpp=32)
(II) dmx[o1/192.168.2.20:0]: s=1024x768+0+0 r=1024x768+0+0 @1280,0 (be=1024x768 depth=24 bpp=32)
(II) dmx: Using old bounding box (2304x1024) instead of new (2304x1024)
(II) dmx: XSync batching with 100 ms interval
(II) dmx: Shadow framebuffer support disabled
(II) dmx[i0/:0]: Using backend input from :0
(II) dmx[i0/:0]: Locating devices on :0 (XInputExtension version 1.3)
(II) dmx[i0/:0]: 0 Keyboard1 XKeyboard
(II) dmx[i0/:0]: 1 Mouse1 XPointer
(II) dmx[i0/:0]: Added backend-mou as pointer device called Mouse0 [core]
(II) dmx[i0/:0]: Added backend-kbd as keyboard device called Keyboard0 [core]
(II) dmx[i0/:0]: Using Keyboard0 and Mouse0 as true core devices
(II) dmx[i0/:0]: XKEYBOARD: keycodes = xfree86+aliases(qwertz)
(II) dmx[i0/:0]: XKEYBOARD: symbols = pc(pc105)+de
(II) dmx[i0/:0]: XKEYBOARD: geometry = (null)
(II) dmx[i0/:0]: XKEYBOARD: From device: xfree86 pc(pc105)+de
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Could not init font path element /usr/share/fonts/OTF, removing from list!
(II) dmx: ===== Start of Summary =====
(II) dmx: 2 screens configured with Xinerama (2304 1024)
(II) dmx: 8 visuals at depth 24:
(II) dmx: 0x23 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x24 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x25 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x26 TrueColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x27 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x28 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x29 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0x2a DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff
(II) dmx: 0 visuals at depth 1:
(II) dmx: 0 visuals at depth 4:
(II) dmx: 0 visuals at depth 8:
(II) dmx: 0 visuals at depth 15:
(II) dmx: 0 visuals at depth 16:
(II) dmx: 0 visuals at depth 32:
(II) dmx: 2 devices:
(II) dmx: Id Name Classes
(II) dmx: 0 Mouse0 val btn fb/ptr [i0/:0/id1=Mouse1] core
(II) dmx: 1 Keyboard0 key foc fb/kbd [i0/:0/id0=Keyboard1] core
(II) dmx: ===== End of Summary =====
(II) dmx[i0/:0]: Keyboard busy, waiting
(II) dmx[i0/:0]: Keyboard busy, waiting
(II) dmx[i0/:0]: Keyboard busy, waiting
(II) dmx[i0/:0]: Keyboard busy, waiting
(II) dmx[i0/:0]: Keyboard busy, waiting
(II) dmx[i0/:0]: Keyboard busy, waiting
(II) dmx[i0/:0]: Keyboard busy, waiting
(II) dmx[i0/:0]: Keyboard busy, waiting
(II) dmx[i0/:0]: Keyboard busy, waiting
(II) dmx[i0/:0]: Keyboard busy, waiting
(II) dmx[i0/:0]: Keyboard busy, waiting
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing. |
And here from startkde:
| Code: |
xset: bad font path element (#102), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
xset: bad font path element (#102), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
xset: bad font path element (#102), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
startkde: Starting up...
kbuildsycoca running...
Couldn't interpret _XKB_RULES_NAMES property
Use defaults: rules - 'xorg' model - 'pc101' layout - 'us'
Xlib: extension "XFree86-VidModeExtension" missing on display ":2.0".
Xlib: extension "XFree86-VidModeExtension" missing on display ":2.0".
Xlib: extension "XFree86-VidModeExtension" missing on display ":2.0". |
|
|
| Back to top |
|
 |
DingbatCA Guru


Joined: 07 Jul 2004 Posts: 318 Location: Portland Or
|
Posted: Mon May 28, 2007 6:03 pm Post subject: |
|
|
I truly think we are trying to do way to much. If we can get an xterm running, we can get KDE to work. I also found that for testing a single system does just fine. Just to save some time and headache.
| Code: | | Xdmx :2 -display 127.0.0.1:0 |
|
|
| Back to top |
|
 |
Pegasus87 Guru

Joined: 09 Sep 2004 Posts: 367
|
Posted: Mon May 28, 2007 7:41 pm Post subject: |
|
|
I found the problem with the not working keyboard. It was the lineakd for my shortcut keys on the board... without this daemon, all is running greatfully.
Only the problem that the old kde session isn't closed before running a new is is still there..... i'll working on that. I think the old kdeinit have to be closed or so. One way to kill the old session have to be found because it reduces the performance if there are running two kde sessions. |
|
| Back to top |
|
 |
Justin Buser n00b

Joined: 29 Apr 2012 Posts: 1
|
Posted: Sun Apr 29, 2012 1:23 am Post subject: |
|
|
| Sadako wrote: | | DingbatCA wrote: | But when I remove the -nolisten option kdm does not start.
Any ideas? | Sorry, not a kde user.
Only thing I have to ask is, when you say you remove the -nolisten option, do you just remove "-nolisten", or "-nolisten tcp"?
It sounds to me like you're just removing -nolisten, but tcp is an argument to the -nolisten flag, as in "don't listen for tcp traffic".
|
ServerArgsLocal has a default value if it's not set so if he is simply commenting out that line the -nolisten tcp would still be applied.
Additionally being a KDE user has nothing to do with having a basic understanding of how X11 works, which it seems not many people participating in this thread have. I would highly recommend the lot of you do a lot more reading and a lot less blind fumbling about before you all end up having to reinstall Linux. |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|