Ghee, Ghee Teo-san wrote (03/18/09 08:51 PM): > Takao, > > Does this mean in the future, installation of SUNWgnome-session with > gconf changes which requires system to be rebooted before they will be > picked up?
Pardon, I'm not sure what you ask here ;). This bug is related with the initial boot after OS installation is done. The Initial boot is required by OS installation. Nevada uses postrun scripts to update gconf, desktop caches, icon caches with SMF. If you manually reinstall SUNWgnome-session, I think the postinstall scripts will be run about 5 - 10 minutes and logout/login is enough instead of reboot. fujiwara > > -Ghee > > On 03/18/09 09:35, Takao Fujiwara - Tokyo S/W Center wrote: >> The bug is, GNOME session is not launched correctly when users log into the >> session immediately after the first boot is completed with OS installation. >> >> The postrun check is called by gnome-session but init programs are invoked >> from /usr/dt/config/Xsession.d before gnome-session is launched. >> Then some programs(e.g. gconfd from iiim) run before postrun scripts are >> finished. >> >> My suggestion is the postrun check is moved from gnome-session to >> /usr/dt/config/Xsession.d and /etc/X11/xinit/xinitrc.d script. >> >> gnome-session-03-wait-for-postrun.diff may be removed. >> It may be better to use python scripts instead of zenity. >> postrun-query won't have GUI since it would need LC_MESSAGES=C >> I'll change the translation domain "gnome-session" to "desktop-startup" in >> trunk. >> I think this needs to be fixed in gnome-2-24 too. >> I expect this problem is not happened in Indiana from the root cause because >> postrun is not used in Indiana. >> >> >> > >
