"Neal A. Lucier" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > "Neal A. Lucier" <[EMAIL PROTECTED]> wrote:
> >
> >> I added
> >> Utmhscreen*enableAutoLaunch: false
> >> to the end of my .Xdefaults and utmhscreen still launches on login.
> >>
> >> How do I get utmhscreen to stop running? This is SRSS 3.0 Solaris 9 SPARC.
> >
> > Did that resource ever make it into your X Resource manager settings?
> > What does 'xrdb -query | grep -i utmhscreen' say?
>
> bers ~ % xrdb -query | grep -i utmhscreen
> Utmhscreen*enableAutoLaunch: false
>
> > What kind of desktop (CDE, Gnome, ...) are you logging in to?
>
> GNOME 2.0.2 in Solaris release 12/03.
>
> The utmhscreen appears to launch even before gnome-session starts.
> I see the two little windows before the Nautilus splash screen
> appears.
Right, utmhscreen gets launched from Xsession.d/0100.SUNWut long
before the session-specific session manager runs. And that's the
problem. This turns out to be bug 4495992. The deal is that
/usr/dt/bin/Xsession only partly initialises the X Resource Manager
database before it runs Xsession.d scripts. It loads system-defined
resources but does not load user-defined resources. This means that
your .Xdefaults file doesn't get read and loaded until after
utmhscreen has already been launched, so resources defined in your
.Xdefaults don't influence utmhscreen's behaviour. The CDE team
has refused to fix this bug because they deem it "too risky" to
change Xsession's historical behaviour.
You can work around this by explicitly loading your .Xdefaults
from within your $HOME/.dtprofile, which gets source'd by Xsession
before it executes the Xsession/.d scripts. Add this:
/usr/dt/bin/dtsession_res -merge -xdefaults
to your $HOME/.dtprofile. Or just use:
/usr/openwin/bin/xrdb -merge $HOME/.Xdefaults
if you don't have any per-$DISPLAY #ifdefs in your .Xdefaults.
If you want to do anything fancy, like test for the existence of
$HOME/.Xdefaults, then be aware that Xsession is a 'ksh' script
so .dtprofile (which gets source'd into Xsession) must also use
'ksh' syntax.
As an admin you can make this change system-wide by adding the
Utmhscreen resource definition to the system resource definitions
(which are loaded before $HOME/.dtprofile is sourced and can
therefore be overridden by $HOME/.dtprofile) or by creating a new
Xsession.d script that runs early in the Xsession.d sequence (which
happens after $HOME/.dtprofile has been sourced and can therefore
override $HOME/.dtprofile, so be careful if you want to leave your
users with the option to control this behaviour).
OttoM.
__
ottomeister
Disclaimer: These are my opinions. I do not speak for my employer.
--
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
