Brian Cameron wrote: > > Ghee: > >> It seems my previous attempt to make session dbus to launch in >> Xsession.[jds|tjds] >> failed when user's uses csh. The fix now is to save a copy of user's >> SHELL and >> always ask dbus-launch to return its DBUS_SESSION_BUS_ADDRESS in ksh >> compatible format. and the restore user's SHELL value after that. > > Could you explain why it failed with csh? Is there not a fix we could > make in dbus-launch itself to make it work with csh? If so, such a fix > seems like it would be cleaner and would be more likely to go upstream. In my previous attempt to launch dbus session in /usr/dt/config/Xsession.[jds|tjds] which is a ksh syntax file. I use the line dbus-launch --exit-with-session -auto-syntax
which works when the use's SHELL is not csh. However, when the user has csh as his default shell, dbus-launch returns the environment variables in csh syntax hence it is ignored by ksh scripts. Consequently, user can't login because no dbus session to communicate with. My fix now is to save the user's SHELL value in ksh syntax, get the dbus dession info in ksh format, export it. Restore the SHELL value to the user's environment. So it works regardless of what shell the user is defaulted to. Does gdm uses the Xsession.jds files to start up dbus in the community? If it does, I believe you can pick up the scripts and let it upstream. As far as I know though dtlogin actually own /usr/dt/config/Xsession.jds so there is no upstream to go to. -Ghee > > Brian
