Session is not initialised properly when selecting non-default window manager

Bug #234407 reported by Francis Giraldeau
8
Affects Status Importance Assigned to Milestone
LTSP5
Fix Released
Undecided
Unassigned
ldm (Fedora)
Fix Released
Low
ldm (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Hardy by gcc

Bug Description

Binary package hint: ldm

Either by using LDM_SESSION in lts.conf or selecting within the ldm greeter the window manager to use, the session is not initialized properly. The reason is that Xsession is not executed, and many scripts in /etc/X11/Xsession.d/ are not sourced. Usualy, the x-window-manager (kdestart) is exec'ed by Xsession. Actualy, the x-window-manager is launched directly.

Here is an example of the command line started on the server when using non-default KDE desktop :

/usr/bin/ssh -X -t -S /var/run/ldm_socket_vt7_10.145.3.230 -l demo 10.145.3.230 LTSP_CLIENT=10.145.1.17 LC_ALL=fr_CA.UTF-8 LANGUAGE=fr_CA.UTF-8 LANG=fr_CA.UTF-8 DISPLAY=10.145.1.17:6 PULSE_SERVER=tcp:10.145.1.17:4713 ESPEAKER=10.145.1.17:16001 /usr/bin/startkde ; /usr/sbin/ltspfsmounter all cleanup ; kill -1 ${PPID}

Xsession is not a standard script, so we should look to see how other distros are handling it. Under Ubuntu, saving the window manager in the home directory can be an option.

Revision history for this message
In , Warren (warren-redhat-bugs) wrote :

Currently ldm only launches a desktop session through the Xsession script if you
let it use the default desktop. If you manually pick a different session (like
/usr/bin/gnome-session) it will run it directly, bypassing important stuff that
happens in /etc/X11/xinit/xinitrc.d.

ldm must learn how to run all sessions through Xsession.

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Changed in ldm:
status: Unknown → In Progress
Revision history for this message
Oliver Grawert (ogra) wrote :

Xsession has the possibility to call the x-session-manager as option, since currently all participating distros (ubuntu,debian,gentoo, suse, fedora atm) use Xsession to start their desktops i dont see a reason to change that .... we discussed upstream to fix the call for custom sessions in general by prefixing the call to the binary with the Xsession script as it should be (so all Xsession.d scripts actually take effect) instead of calling things like gnome-session or startkde directly. this change will be in intrepid.

What do you mean by "saving the window manager in the home directory" ?

Revision history for this message
Francis Giraldeau (francis-giraldeau) wrote :

This is a feature request, it's not related to the actual bug. Sorry for the noise.

Revision history for this message
Oliver Grawert (ogra) wrote :

i wasnt complaining :) but would still be curious what you meant by
"saving the window manager in the home directory" ...
do you want to copy the binary ?

Revision history for this message
Francis Giraldeau (francis-giraldeau) wrote :

Thanks for your interest. LDM doesn't save and use the last choice of the user. The user has to select at each login the window manager he wants if it's not the server's default. In contrast, GDM asks the user if he wants to make the selected window manager the default, or use it only once. The information is saved in ~/.dmrc. LDM could use the same file and behavior.

Revision history for this message
Oliver Grawert (ogra) wrote :

right, thats exactly what's planned since aeons (with focus on the default language though, which ~/.dmrc can carry as well), but nobody came around to write an ldm rc.d script for it yet.

Revision history for this message
In , Warren (warren-redhat-bugs) wrote :

This was fixed a long time ago

Revision history for this message
Ryan Niebur (ryan52) wrote :

this was already fixed.

Changed in ldm:
status: New → Fix Released
Revision history for this message
gcc (chris+ubuntu-qwirx) wrote :

Ryan, please could you be a bit more specific? Fixed in hardy updates, intrepid or later? Package and version that was fixed?

Revision history for this message
Oliver Grawert (ogra) wrote :

fixed in upstream commit 911, which was released in version 2.0.13

Changed in ltsp:
status: New → Fix Released
Revision history for this message
Ryan Niebur (ryan52) wrote :

this was fixed in version 1.0.13, so intrepid and later has it.

Thanks,
Ryan

Revision history for this message
Oliver Grawert (ogra) wrote :

intrepid shipped with version 2.0.14, so it was fixed in intrepid

Changed in ldm:
status: In Progress → Fix Released
Changed in ldm (Fedora):
importance: Unknown → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.