Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: slim - Simple Login Manager https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239428 ------- Additional Comments From pertusus@xxxxxxx 2007-06-17 03:23 EST ------- It seems to me that using xinit config files when loggued through slim is wrong. The current practice seems to me to be that xinit is not used when login through a display manager, when login through a display manager something like Xsession is used, that looks into .xsession and not .xinitrc. Moreover it seems to me that the 'generic' Xsession that is used both for kdm and gdm (and wdm, but I am biased here :-) should be used, instead of the one from xdm. This should amounts to adding Requires: xorg-x11-xinit and modify /etc/slim.conf such that the login_cmd is along: login_cmd exec /bin/bash -login /etc/X11/xinit/Xsession %session To reuse the previously used window manager you could do something similar with what I did with wdm, by using a wrapper around /etc/X11/xinit/Xsession, /etc/wdm/Xsession in wdm that stores the previously chosen window manager in $HOME/.wm_style and reuse it when calling /etc/X11/xinit/Xsession. 2 other comments: * with pam support missing, the device special files are not owned by the user loggued in, because pam_console.so is not used. I guess there may be other issues, but this one is a very problematic one. * even if this was solved, the user won't have the right to mount automountable device or do anything else that goes through hal, because of a lack of consolekit handling. However this is also the case for wdm and xdm. Because of the pam issue it isn't that clear to me that this package should go in a stable release, and if it should it should deserve a comment somewhere, an obvious place being the README.fedora -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review