Page 2 of 3
Re: Salix/XFCE as environment for many users
Posted: 20. Jun 2011, 14:04
by witek
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
Posted: 10. Feb 2012, 11:16
by witek
witek 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.
A kind of solution I found at last is adding this line to /etc/X11/app-defaults/XScreenSaver
Code: Select all
*newLoginCommand: gdmflexiserver -l -a -c FLEXI_XSERVER
This add "New Login" options when the screen is locked with xfce screensaver
Re: Salix/XFCE as environment for many users
Posted: 12. Feb 2012, 03:07
by JRD
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
Posted: 12. Feb 2012, 18:55
by witek
JRD wrote:or perhaps make it the default for further version (if it's possible...maybe not without modifying upstream packages)
Exactly what I thought about but was afraid to propose.
Re: Salix/XFCE as environment for many users
Posted: 12. Feb 2012, 18:58
by gapan
witek wrote:JRD wrote:or perhaps make it the default for further version (if it's possible...maybe not without modifying upstream packages)
Exactly what I thought about but was afraid to propose.
Not possible without modifying the slackware package.
Re: Salix/XFCE as environment for many users
Posted: 12. Feb 2012, 19:14
by witek
Re: Salix/XFCE as environment for many users
Posted: 12. Feb 2012, 19:22
by witek
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
Re: Salix/XFCE as environment for many users
Posted: 12. Feb 2012, 20:36
by gapan
witek wrote:And they said, gdmflexiserver is not part of slackware.
Of course.
witek wrote:In such case the maintainer of gdmflexiserver in Salix should include the modified /etc/X11/app-defaults/XScreenSaver in the gdmflexiserver package
No way. Putting xscreensaver configuration in the gdm package doesn't make any sense at all.
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
Ugly. Very ugly. This would get reverted every time you upgrade the xscreesaver package.
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
Posted: 13. Feb 2012, 09:34
by JRD
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.
Re: Salix/XFCE as environment for many users
Posted: 13. Feb 2012, 13:17
by Shador
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?