[XFree86] Xnest Font Server setting

2008-06-14 Thread Girish Hilage
Hi,

I am trying to connect to XServer using Xnest as follows :

> Xnest :1 -kb -terminate -name -query  -geometry 1280x969
-fp tcp/:7100

but I can only see a blank window which vanishes within a fraction of a
second.
The error I see is : "could not open default font 'fixed'".

Now, if I use,

> Xnest :1 -kb -terminate -name -query 
-geometry 1280x969
-fp 
/usr/X11R6/lib/X11/fonts/cursor/,/usr/X11R6/lib/X11/fonts/arkpandora,/usr/X11R6/lib/X11/fonts/TTF,/usr/X11R6/lib/X11/fonts/misc

then I can successfully connect to X and can see Xnext login window.

Now, if I run the first command again then this time it works fine
without any error.

Is there any reason why it did not work if I tried only
:7100 before specifying all the font paths and it worked
after specifying font paths? Does this have anything to do with caching?

Regards,
Girish



DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.
___
XFree86 mailing list
XFree86@XFree86.Org
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest Font Server setting

2008-05-07 Thread girish_hilage
Hi,

I am trying to connect to XServer using Xnest as follows :

> Xnest :1 -kb -terminate -name -query  -geometry 1280x969 -fp 
> tcp/:7100

but I can only see a blank window which vanishes within a fraction of a second.
The error I see is : "could not open default font 'fixed'".

Now, if I use,

> Xnest :1 -kb -terminate -name -query 
-geometry 1280x969 -fp
/usr/X11R6/lib/X11/fonts/cursor/,/usr/X11R6/lib/X11/fonts/arkpandora,/usr/X11R6/lib/X11/fonts/TTF,/usr/X11R6/lib/X11/fonts/misc

then I can successfully connect to X and can see Xnext login window.

Now, if I run the first command again then this time it works fine without any 
error.

Is there any reason why it did not work if I tried only FONT_SERVER_IP:7100 
before specifying all the font paths and it worked after specifying font paths? 
Does this have anything to do with caching?

Regards,
Girish

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.
___
XFree86 mailing list
XFree86@XFree86.Org
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest Font Server setting

2008-05-06 Thread girish_hilage
Hi,

I am trying to connect to XServer using Xnest as follows :

> Xnest :1 -kb -terminate -name -query  -geometry 1280x969 -fp 
> tcp/:7100

but I can only see a blank window which vanishes within a fraction of a second.
The error I see is : "could not open default font 'fixed'".

Now, if I use,

> Xnest :1 -kb -terminate -name -query 
-geometry 1280x969 -fp
/usr/X11R6/lib/X11/fonts/cursor/,/usr/X11R6/lib/X11/fonts/arkpandora,/usr/X11R6/lib/X11/fonts/TTF,/usr/X11R6/lib/X11/fonts/misc

then I can successfully connect to X and can see Xnext login window.

Now, if I run the first command again then this time it works fine without any 
error.

Is there any reason why it did not work if I tried only FONT_SERVER_IP:7100 
before specifying all the font paths and it worked after specifying font paths? 
Does this have anything to do with caching?

Regards,
Girish

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.
___
XFree86 mailing list
XFree86@XFree86.Org
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest: Linux (Dell) - Solaris (Sun)

2005-02-22 Thread Sami_Abdul
Hi,

I am trying to get Xwindows of our Linux system (running on Dell) on
Solaris box (Sun Blade 100). The 'X' windows turns up, but its dark,
nothing is displayed.
Xnest work fine for our Solaris systems on SunBlade.

Please help.

Thanks
Sami Abdul
Email: [EMAIL PROTECTED]
This email is sent by or on behalf of the named sender identified above. If
you do not wish to receive any email marketing material from this person in
the future, please forward the contents of this email to
[EMAIL PROTECTED] with the word "unsubscribe" in the subject
box. If you do not forward the contents of this email with your
unsubscription then it may not be able to be implemented.  If you wish to
unsubscribe from all central email marketing lists used by our business,
please forward the contents of this email to
[EMAIL PROTECTED] with the message "unsubscribe from all
central email marketing lists" in the subject box.  If you do not forward
the contents of this email with your unsubscription then it may not be able
to be implemented.


The information contained in this email communication may be confidential.
You should only disclose, re-transmit, copy, distribute, act in reliance on
or commercialise the information if you are authorised to do so.  Any views
expressed in this email communication are those of the individual sender,
except where the sender specifically states them to be the views of a
member of the National Australia Bank Group of companies.  Any advice
contained in this e-mail has been prepared without taking into account your
objectives, financial situation or needs. Before acting on any advice in
this e-mail, National Australia Bank Limited recommends that you consider
whether it is appropriate for your circumstances. If this e-mail contains
reference to any financial products, the National recommends you consider
the Product Disclosure Statement (PDS) or other disclosure document  before
making any decisions regarding any products.  The National Australia Bank
Group of companies does not represent, warrant or guarantee that the
integrity of this communication has been maintained nor that the
communication is free of errors, virus or interference.

___
XFree86 mailing list
XFree86@XFree86.Org
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] Xnest and fvwm

2004-12-08 Thread Marc Aurele La France
On Tue, 7 Dec 2004, Benoit Galarneau wrote:
I have a small problem with fvwm. XDMCP is enable on a linux computer
running fvwm windows manager. With Solaris, we start a Xnest connection
with a query to the linux computer.

I log and everything is fine except for a particular application. The
application "menu's item" are not there. I see the menu scrolling down
but the text is not there. Everything else is working, mouse click
(left, middle and right button).

There is no problem without Xnest. When I start a "X :1 -query
Linux_IP", everything is good.
I'll assume the "X" you're refering to here is Solaris's Xsun.
It's possible the application requires backing store and/or save unders to 
operate.  According to our source at least (and X.Org's), Xnest explicitly 
disables both on its screens.  This would be the reason behind the behaviour 
you're seeing if it also occurs under `Xsun :1 -bs -su -query `. 
If so, you would then need to hack Xnest (or the application's) source code 
to change this.

Marc.
+--+---+
|  Marc Aurele La France   |  work:   1-780-492-9310   |
|  Computing and Network Services  |  fax:1-780-492-1729   |
|  352 General Services Building   |  email:  [EMAIL PROTECTED]  |
|  University of Alberta   +---+
|  Edmonton, Alberta   |   |
|  T6G 2H1 | Standard disclaimers apply|
|  CANADA  |   |
+--+---+
XFree86 developer and VP.  ATI driver and X server internals.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest and fvwm

2004-12-07 Thread Benoit Galarneau
Hi everyone,

I have a small problem with fvwm. XDMCP is enable on a linux computer
running fvwm windows manager. With Solaris, we start a Xnest connection
with a query to the linux computer.

I log and everything is fine except for a particular application. The
application "menu's item" are not there. I see the menu scrolling down
but the text is not there. Everything else is working, mouse click
(left, middle and right button).

There is no problem without Xnest. When I start a "X :1 -query
Linux_IP", everything is good.

I want to know if someone experienced something similar or not.

Thx.

Ben

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest and fvwm

2004-12-07 Thread Benoit Galarneau
Hi everyone,

I have a small problem with fvwm. XDMCP is enable on a linux computer
running fvwm windows manager. With Solaris, we start a Xnest connection
with a query to the linux computer.

I log and everything is fine except for a particular application. The
application "menu's items" are not there. I see the menu scrolling down
but the text is not there. Everything else is working, mouse click
(left, middle and right button).

There is no problem without Xnest connection.
When I start a "X :1 -query Linux_IP", everything is good.

I want to know if someone experienced something similar or not.

Thx.

Ben

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] Xnest & nesting servers

2004-02-06 Thread Bob Marcan
jayjwa wrote:
Hello All,

I'm having trouble getting the Xnest server to allow clients access when
running as a second server on the same workstation. (I probably won't do
this in practice, but I'd like to know why it's not allowing access.) One
server starts OK. Then I'll start the second server, Xnest, on another
display like so: Xnest -display :1. It starts fine, I can see it. The man
page for Xnest states now I should be able to run xclients on the Xnest
server, such as: xterm -display :1, and then lauch whatever from there.
This is the part were trouble sets in. The xterm is refused, can't
connect. In the term that I started the Xnest server, I see error
messages:
AUDIT:  Xnest: client 1 rejected from local host
and this repeats each time I try, same results. I changed the display
numbers around but no luck. It seems something is default set overly
protective, but I'm not sure how to stop it, or what it is. It's not
xhost +, because I tried that in desperation. It won't take a
-display tag, either. So now I have a lovely Xnest server with a paranoid
complex that I can't access from the machine that started it (I could
simply kill it off, so I don't see the security in this.) Thanks in
advance for anyone that can help. I'll keep checking the man pages 'till
then :(
-Jay



___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
I'm using this script:
-
#! /bin/sh
HOST="$1"
if [ "$HOST" = "" ]; then HOST="localhost"; fi
SCREEN="$2"
#if [ "$SCREEN" = "" ]; then SCREEN="8"; fi
GEOMETRY="1258x914"
if [ "`echo $HOST | grep tamagoci`" ]; then GEOMETRY="1024x768"; fi
if [ "`uname -n | grep tamagoci`" ]; then GEOMETRY="960x665"; fi
if [ "$SCREEN" = "" ]; then
  TMP=`mktemp /var/tmp/xnest.XX || exit 1`
  OLDSCR=7
  ps -A -o cmd | grep ^Xnest | sort > $TMP
  exec 3< $TMP
  while read <&3 ln; do
SCREEN=`echo "$ln" | awk -F " " '{print $2}'`
SCREEN=`echo "$SCREEN" | awk -F ":" '{print $2}'`
SCREEN=`echo "$SCREEN" | awk -F "." '{print $1}'`
if [ $OLDSCR -le $SCREEN ]; then OLDSCR=$SCREEN; fi
  done
  exec 3<&-
  SCREEN=`expr $OLDSCR + 1`
  rm $TMP
fi
Xnest :${SCREEN}.0 -wm -full -query $HOST -once -geometry $GEOMETRY 
-name "${HOST}.${SCREEN}" &
-

xterm -display localhost:8
works properly
--
 Bob Marcan mailto:[EMAIL PROTECTED]
 Aster^H^H...HermesPlus^H^H^H...S&T
 Slandrova ul. 2   tel:+386 (1) 5895-200
 1000 Ljubljana, Slovenia  http://www.hermes-plus.si
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest & nesting servers

2004-02-05 Thread jayjwa
Hello All,

I'm having trouble getting the Xnest server to allow clients access when
running as a second server on the same workstation. (I probably won't do
this in practice, but I'd like to know why it's not allowing access.) One
server starts OK. Then I'll start the second server, Xnest, on another
display like so: Xnest -display :1. It starts fine, I can see it. The man
page for Xnest states now I should be able to run xclients on the Xnest
server, such as: xterm -display :1, and then lauch whatever from there.
This is the part were trouble sets in. The xterm is refused, can't
connect. In the term that I started the Xnest server, I see error
messages:
AUDIT:  Xnest: client 1 rejected from local host

and this repeats each time I try, same results. I changed the display
numbers around but no luck. It seems something is default set overly
protective, but I'm not sure how to stop it, or what it is. It's not
xhost +, because I tried that in desperation. It won't take a
-display tag, either. So now I have a lovely Xnest server with a paranoid
complex that I can't access from the machine that started it (I could
simply kill it off, so I don't see the security in this.) Thanks in
advance for anyone that can help. I'll keep checking the man pages 'till
then :(

-Jay




___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest and altgr -key

2004-01-07 Thread Kristoff Bonne
Greetings,

My workstation at work is a linux-box running redhat 9 (running
XFree86-4.3.0-2.90.43 and XFree86-Xnest-4.3.0-2.90.43)
I wanted to start to use Xnest to remotely log-in into the other
unix-servers (solaris and linux-boxes).
However, I have a serious problem with the keyboard and -especially- te
"AltGr"-key.
At first, when I tried the "normal" Xnest, the 'remote-session' used a
query-keyboard (the workstation I have has a Belgian azerty-keyboard,
"be-latin1" in linux-speak).
Then, I tried the "-kb" option, I did get the correct keyboard; except
that the 'altGr'-key doesn't work. So, the "|", "@", "#", "¤", "\", ...
and all other characters which are on a key that needs the AltGr-key
doesn't seam to work. I get the same character as I would get if I would
just press only the key. (no shift, no alt, ...)
The "odd" thing is that, if I start "xev" remotely (the X
event-displayer tool); and I press the "AltGr" key in the Xev window;
the tool DOES indicate it has received an event that the key is pressed.
It gives this "... keycode 113 (keysym 0xfe03, ISO_Level3_Shift), ..."
So, the event that "altGr" key is pressed DOES is sent to the other
side; but -for some reason- it is not interpreted in the corret way.
(althou it does say "keycode = 113, ISO_Level3_Shift" and "xmodmap -pm"
does indicate the "ISO_Level3_Shift" as being "modifier 5", both at the
local and the remote side).
As I have this problem on all servers I have (linux and solaris), I
guess the problem is on the local Xnest running on my workstation.
Anybody any idea?

Cheerio! Kr. Bonne.
--
KB905-RIPE   Belgacom  IP networking
(c=be,a=rtt,p=belgacomgroup,s=Bonne,g=Kristoff)  Internet, IP and IP/VPN
[EMAIL PROTECTED] faxbox:   +32 2 2435122
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest and altgr -key

2004-01-07 Thread Kristoff Bonne
Greetings,

My workstation at work is a linux-box running redhat 9 (running 
XFree86-4.3.0-2.90.43 and XFree86-Xnest-4.3.0-2.90.43)

I wanted to start to use Xnest to remotely log-in into the other 
unix-servers (solaris and linux-boxes).
However, I have a serious problem with the keyboard and -especially- te 
"AltGr"-key.

At first, when I tried the "normal" Xnest, the 'remote-session' used a 
query-keyboard (the workstation I have has a Belgian azerty-keyboard, 
"be-latin1" in linux-speak).

Then, I tried the "-kb" option, I did get the correct keyboard; except 
that the 'altGr'-key doesn't work. So, the "|", "@", "#", "¤", "\", ... 
and all other characters which are on a key that needs the AltGr-key 
doesn't seam to work. I get the same character as I would get if I would 
just press only the key. (no shift, no alt, ...)

The "odd" thing is that, if I start "xev" remotely (the X 
event-displayer tool); and I press the "AltGr" key in the Xev window; 
the tool DOES indicate it has received an event that the key is pressed. 
It gives this "... keycode 113 (keysym 0xfe03, ISO_Level3_Shift), ..."

So, the event that "altGr" key is pressed DOES is sent to the other 
side; but -for some reason- it is not interpreted in the corret way. 
(althou it does say "keycode = 113, ISO_Level3_Shift" and "xmodmap -pm" 
does indicate the "ISO_Level3_Shift" as being "modifier 5", both at the 
local and the remote side).

As I have this problem on all servers I have (linux and solaris), I 
guess the problem is on the local Xnest running on my workstation.

Anybody any idea?

Cheerio! Kr. Bonne.
--
KB905-RIPE   Belgacom  IP networking
(c=be,a=rtt,p=belgacomgroup,s=Bonne,g=Kristoff)  Internet, IP and IP/VPN
[EMAIL PROTECTED] faxbox:   +32 2 2435122
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest & xauth

2003-08-14 Thread Hanspeter Roth
Hello,

I have difficulty to use Xnest on some systems. It seems to me it
has something to do with the cookies in .Xauthority. On some systems
these cookies seem to remain after X terminates on others they are
removed. On these systems after launching Xnest on an alternate
display I can't connect a single client nor generate a cookie for
this display. On OpenBSD for example host/unix:0 is remained after
terminting X on display :0. So starting X on :1 allows me to run
Xnest on :0 and then connect clients to :0.
Trying to generate a cookie on a display which isn't already served
also fails.
So how can one use Xnest when there is no cookie for the display
before starting Xnest?

Cheers 
Hanspeter
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest & xauth

2003-08-14 Thread Hanspeter Roth
Hello,

I have difficulty to use Xnest on some systems. It seems to me it
has something to do with the cookies in .Xauthority. On some systems
these cookies seem to remain after X terminates on others they are
removed. On these systems after launching Xnest on an alternate
display I can't connect a single client nor generate a cookie for
this display. On OpenBSD for example host/unix:0 is remained after
terminting X on display :0. So starting X on :1 allows me to run
Xnest on :0 and then connect clients to :0.
Trying to generate a cookie on a display which isn't already served
also fails.
So how can one use Xnest when there is no cookie for the display
before starting Xnest?

Cheers 
Hanspeter
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] Xnest

2003-07-19 Thread Peter \"Firefly\" Lund
On Sun, 20 Jul 2003, shxu1 wrote:

>  Can you tell me how to use Xnest in the redhat linux 8.0? I have
> tried many times.
> It seems Xnest doesn't work properly with redhat linux 8.0.

How does it break?  Got any error output from it, for example?  Can you
tell us how you invoke it?  What you are trying to do?  Etc...

-Peter
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest

2003-07-19 Thread shxu1
Dear Sir,
Can you tell me how to use Xnest in the redhat linux 8.0? I have 
tried many times.
It seems Xnest doesn't work properly with redhat linux 8.0.
 Urgently waiting for your reply, thanks.
   
  Steven.
   


___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest help

2003-06-06 Thread Muralidhar Ganga
Hi,

Running Rehdat 9.0.

Trying to connect to Solaris box using Xnest with the following 
command: 

Xnest :1 -geometry 1024x784+0+0 -indirect 192.168.0.24 &

The Xnest window flickering forever and never stops.

Here is log on the window where Xnest has started:

Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!


Thanks
/Murali

-- 
Muralidhar Ganga <[EMAIL PROTECTED]>

___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Xnest trouble

2003-02-27 Thread Eilmsteiner Reinhard
Hi All!

I'm new to Xnest and wanted to test the thing to get a Xterminal of a
server onto my notebook.

Both machines are running Redhat 8.0, the server is a dual-Xeon machine.

Here's what I do on my notebook:
Xnest :2 -query 192.168.1.66 -ac
Sometimes I get a display and I can put in my username. But shortly
afterwards something goes wrong an I get:
Fatal server error:
XDMCP fatal error: Session declined Maximum number of open sessions from
your host reached.
Most of the times I can't even see the login screen and the error comes
after a short time.

How can I avoid this?

Thx,
Reinhard Eilmsteiner


___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86