[indiana-discuss] unable to export my x application displays

[Bryan Boone]

I was just trying to do what I can normally do in Linux.
 From KDE, Gnome. etc, rlogin to my login hp server, export the display 
back to my Solaris session, then run an xterm (originating from the hp 
login server) and have it display locally.

Seems odd that I have to fiddle with it in 2 places.
1) If I was a Solaris admin, then svccfg would be 2nd nature
2) If I was a Linux _and_ Gnome admin, I would have known about custom.conf

As it was, I had to run my universal translater ;)
Now if only I knew how to solve the:

font "'-*-*-*-*-*-*-*-12-*-*-*-*-*-*'" doesn't exist
      (database entry for "font" in widget ".menu")
      invoked from within
"menubutton .menu -text "$options(sdsenv)" -menu .menu.m -relief raised"

some apps give when trying to display locally...
Can it be fixed with a font? configuration file edit? svccfg?

-Bryan

Richard Elling wrote:
> Bryan Boone wrote:
>> Got it... (Yahoo)
>>
>> I'm not sure if it requires the
>>    svccfg -s x11-server setprop options/tcp_listen=true
>>
> 
> This is documented in the Example section of the Xserver(1)
> man page.  What this does is allow a remote X client to direct
> the display at your server (screen) via TCP.
> 
>> But after doing that and adding:
>>
>> DisallowTCP=false
>>
>> to /etc/X11/gdm/custom.conf
>>
> 
> This just sets up the GNOME Display Manager (gdm) to
> allow X login screen for remote servers.
> 
>> I can export the display back to my OpenSolaris session.
>>
>> Does it require both being set?  I don't know.  I just know that after
>> doing the first, it didn't work.  Doing the second, then I could export
>> the display to my session.
>>
> 
> It depends on what you were trying to do.  With the former,
> your application can send its display to your server.  With
> the latter, you can login to the remote machine via the
> graphical screen.
>  -- richard
> 
>