I previously posted similiarly under subject
"How to prevent Xnest from using ipv6"
and got no response so decided to re-post under a more informative
subject.

I have been trying to use Xnest in Slackware 10 under KDE but get
errors that prevent me from running Xnest. Does anyone else get this?

When I execute a simple
Xnest :1
I get error messages that seem to be related to Xnest's desire to use
ipv6 which isn't even enabled in Slack 10 AFAIK.

I checked /usr/src/linux/.config and ipv6 is enabled only as a module
but ls modules has nothing.

Maybe something is configured wrong in the source but
I have not been able to find the source for Pat's xnest.
Looked on cdrom 3 and 4 in MANIFEST.

Before I send a message to Pat I want to be sure I'm not doing
something stupid.




This is the Xnest command and error messages:

lba@linda lba $ Xnest :1
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/linda:1
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for
net6
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/,
removing from list!
X connection to :0.0 broken (explicit kill or server shutdown).


From reading of man Xserver, Xnest may be trying to broadcast using
ipv6 which of course does not respond.

I also tried the Xnest from Slackware 9.1 and got the same errors.

I've googled around and there are a few tantalizing hits but in
languages I don't understand!

There is an /etc/X11/xdm/Xserver but I'm not running xdm or Xserver
although kdeinit is running ksmserver and dcopserver, whatever they
do.

Can anyone tell me how to use Xnext and get around the ipv6 problem?

Thanks,
Larry Alkoff

Austin Reed wrote:

>
> Can anyone tell me how to use Xnext and get around the ipv6 problem?

hello,

all i can tell you is when i launch 'Xnest :1' from a konsole in kde, i
have got the same errors you mention about ipv6
-------------------------------------------
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/titan:1
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/,
removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
--------------------------------------------
BUT Xnest runs without problem and display a message like this
-------------------
X connection to :0.0 broken (explicit kill or server shutdown).
------------------------
only when I close Xnest
So your problem seems not related to the ipv6 stuff...

On Fri, 23 Jul 2004 10:58:13 +0200, solsTiCe <zebul666@voila.fr>
wrote:

>Austin Reed wrote:
>
>>
>> Can anyone tell me how to use Xnext and get around the ipv6 problem?
>
>hello,
>
>all i can tell you is when i launch 'Xnest :1' from a konsole in kde, i
>have got the same errors you mention about ipv6
>-------------------------------------------
>_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
>_XSERVTransOpen: transport open failed for inet6/titan:1
>_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
>Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/,
>removing from list!
>Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
>from list!
>--------------------------------------------
>BUT Xnest runs without problem and display a message like this
>-------------------
>X connection to :0.0 broken (explicit kill or server shutdown).
>------------------------
>only when I close Xnest
>So your problem seems not related to the ipv6 stuff...

I agree that the problem is not related to ipv6.
Note that I only get the final error message "X connection to 0:.0
broken" after I cancel the Xnest window using the X in the upper right
corner. It's hidden by the Xnest window until the Xnest window gets
dismissed.

Some questions for you,

1. Are you running Xnest as user or root?
2. When Xnest loads, do you see something that looks like kde or
whatever gui you are using? I only see a momentary white screen, then
a crosshatched screen with no prompts or lettering.
3. I have directories containing both the CID and Speedo fonts but for
some reason they are not being initialized. Do you have any way of
checking what font is being used?

Unfortunately I'm not seeing any error messages related to this in
/var/log.

I wish someone else using Slack 10 would run Xnest :1 and tell us what
happens.

Larry

Austin Reed wrote:


> Some questions for you,
>
> 1. Are you running Xnest as user or root?
USER
> 2. When Xnest loads, do you see something that looks like kde or
> whatever gui you are using? I only see a momentary white screen, then
> a crosshatched screen with no prompts or lettering.
NO
> 3. I have directories containing both the CID and Speedo fonts but for
> some reason they are not being initialized. Do you have any way of
> checking what font is being used?
>
NO

after you have launch Xnest :1
you must also run whichever window manager you like:
for example: fluxbox -display :1

or you could simply run an xterm or whatever application you want with a
command like that:
xterm -display :1

So it seems to me your Xnest is perfectly working but you don't konw how
to use it...
Check the man page :-)
man Xnest !!!!

On Sat, 24 Jul 2004 12:04:05 +0200, solsTiCe <zebul666@voila.fr>
wrote:

>Austin Reed wrote:
>
>
>> Some questions for you,
>>
>> 1. Are you running Xnest as user or root?
>USER
>> 2. When Xnest loads, do you see something that looks like kde or
>> whatever gui you are using? I only see a momentary white screen, then
>> a crosshatched screen with no prompts or lettering.
>NO
>> 3. I have directories containing both the CID and Speedo fonts but for
>> some reason they are not being initialized. Do you have any way of
>> checking what font is being used?
>>
>NO
>
>after you have launch Xnest :1
>you must also run whichever window manager you like:
>for example: fluxbox -display :1

I tried this except that I use display :2 since :1 is in use.
Xnext :2
In another user xterm:
fluxbox -display :2

I get the following error message:
lba@linda lba $ fluxbox -display :2
Warning: Failed to open catalog, using default messages.
Xlib: connection to ":2.0" refused by server
Xlib: No protocol specified

BaseDisplay::BaseDisplay: connection to X server failed.
Fluxbox: Unknown error.

I also tried with xterm and got:
lba@linda lba $ fluxbox -display :2
Warning: Failed to open catalog, using default messages.
Xlib: connection to ":2.0" refused by server
Xlib: No protocol specified

BaseDisplay::BaseDisplay: connection to X server failed.
Fluxbox: Unknown error.

Same error for both but I don't understand what the error is
instructing me to change.

>or you could simply run an xterm or whatever application you want with a
>command like that:
>xterm -display :1

Also tried in another xterm:
xterm -display :2
and got basically the same message.

It appears I'm doing the same wrong thing each time.

>
>So it seems to me your Xnest is perfectly working but you don't konw how
>to use it...
>Check the man page :-)
>man Xnest !!!!

You are quite correct - I evidently don't know how to use Xnest.
I've been studying the man page for both Xnest and Xserver
and trying various things per above without success.

If it worked just once I'd be off to a good start.

Larry Alkoff aka Austin Reed

the only tweak i made of the configuration of the X server launched by
kdm (do you use kdm ?) is to add -nolisten tcp at the end of the only
uncommented line of /opt/kde/share/config/kdm/Xservers

maybe you should investigate to see if /etc/X11/xorg.conf is incorrect
or there is something missing there ??