Salix/XFCE as environment for many users
Re: Salix/XFCE as environment for many users
Thanks Shador. Your trick is working. Pitty however that Salix doesn`t have full-fledged GDM with face-selector (as Fedora or Ubuntu) allowing to switch between logged users.
Re: Salix/XFCE as environment for many users
A kind of solution I found at last is adding this line to /etc/X11/app-defaults/XScreenSaverwitek wrote:Thanks Shador. Your trick is working. Pitty however that Salix doesn`t have full-fledged GDM with face-selector (as Fedora or Ubuntu) allowing to switch between logged users.
Code: Select all
*newLoginCommand: gdmflexiserver -l -a -c FLEXI_XSERVER
Re: Salix/XFCE as environment for many users
Usefull ! I need to put this on the wiki....or perhaps make it the default for further version (if it's possible...maybe not without modifying upstream packages)

Re: Salix/XFCE as environment for many users
Exactly what I thought about but was afraid to propose.JRD wrote:or perhaps make it the default for further version (if it's possible...maybe not without modifying upstream packages)
Re: Salix/XFCE as environment for many users
Not possible without modifying the slackware package.witek wrote:Exactly what I thought about but was afraid to propose.JRD wrote:or perhaps make it the default for further version (if it's possible...maybe not without modifying upstream packages)
Re: Salix/XFCE as environment for many users
I`ve just proposed it on the Slackware forum:
http://www.linuxquestions.org/questions ... ost4600668
http://www.linuxquestions.org/questions ... ost4600668
Re: Salix/XFCE as environment for many users
And they said, gdmflexiserver is not part of slackware. In such case the maintainer of gdmflexiserver in Salix should include the modified /etc/X11/app-defaults/XScreenSaver in the gdmflexiserver package or maybe just make the install script to add this line (like this?) :
echo "*newLoginCommand: gdmflexiserver -l -a -c FLEXI_XSERVER" >> /etc/X11/app-defaults/XScreenSaver
echo "*newLoginCommand: gdmflexiserver -l -a -c FLEXI_XSERVER" >> /etc/X11/app-defaults/XScreenSaver
Re: Salix/XFCE as environment for many users
Of course.witek wrote:And they said, gdmflexiserver is not part of slackware.
No way. Putting xscreensaver configuration in the gdm package doesn't make any sense at all.witek wrote:In such case the maintainer of gdmflexiserver in Salix should include the modified /etc/X11/app-defaults/XScreenSaver in the gdmflexiserver package
Ugly. Very ugly. This would get reverted every time you upgrade the xscreesaver package.witek wrote:or maybe just make the install script to add this line (like this?) :
echo "*newLoginCommand: gdmflexiserver -l -a -c FLEXI_XSERVER" >> /etc/X11/app-defaults/XScreenSaver
The only way to do it properly is to rebuild the xscreensaver package. And I don't think we should do that. And least I won't do that, I don't think it's important enough to justify rebuilding the package. Give me solutions that involve having less things to maintain, not more. A wiki page should be enough.
Re: Salix/XFCE as environment for many users
It could be just done at starting, the /etc/rc.d/rc.something, like /etc/rc.d/rc.xscreensavergdm which checks if gdmflexiserver is avaialble, if xscreensaver is available, then, using a variable posistionned to "yes" or "no" it will sed-add or sed-remove the mentionned line.
This way, it is simple, easy, and non-obstrusive.
This way, it is simple, easy, and non-obstrusive.

Re: Salix/XFCE as environment for many users
Sorry, but this solution seems even much worse and also hacky to me.
Imagine a user who installed gdm and xscreensaver. Now the script would update his settings, but only when he reboots, so there are situations where those changes are not reflected. So that makes it hacky in my view.
To top it off now imagine a user who doesn't want this functionality. He removes the setting and everything works as expected. Now he reboots and the script resets it again. Nobody would guess there's some script being run during startup that claims to know what he wants. Very very bad imho.
I can see just no solution without reasoning with upstream. Even replacing the package introduces at one hand an unnecessary maintenance overhead, but even worse diverges us from Slackware. If we start doing that, where to draw the line?
Imagine a user who installed gdm and xscreensaver. Now the script would update his settings, but only when he reboots, so there are situations where those changes are not reflected. So that makes it hacky in my view.
To top it off now imagine a user who doesn't want this functionality. He removes the setting and everything works as expected. Now he reboots and the script resets it again. Nobody would guess there's some script being run during startup that claims to know what he wants. Very very bad imho.
I can see just no solution without reasoning with upstream. Even replacing the package introduces at one hand an unnecessary maintenance overhead, but even worse diverges us from Slackware. If we start doing that, where to draw the line?