Mario:
It sounds like you already figured out the more common gotchas. You
need to run gnome-session with dbus-launch, and the need to set
GTK_IM_MODULE.
I'd recommend that you carefully review how the startup scripts work
in Solaris. They work as follows
- the login program runs
- /usr/dt/config/Xsession.jds which runs
- /usr/dt/bin/Xsession which runs
- /usr/dt/config/Xsession2.jds which runs
- /usr/dt/config/Xinitrc.jds which runs
- gnome-session
You'll notice the following:
- Xsession.jds starts up the session with dbus-launch and ssh-agent.
- Xsession does a lot of things you probably want to do
- Calls "set +a"
- sets up many globals the session probably needs like LANG, SHELL,
TERM, OPENWINHOME, etc.
- Sets up your font paths
- sources your desktop profile
- sources scripts in DT_XSESSION_DIR (which you probably want to also
do)
- probably other things I miss at first glance
- Xsession2.jds calls xmbind
- Xinitrc.jds sets up some specific GNOME environment variables
You probably want your standalone startx script to do as much of this
stuff as makes sense, if you want things to work well.
> Because it's geekier and because I'd like my laptop not always to start
> with X, I figured I try creating a startx script. So far, it kind of works.
Brian
