![]() ![]() Clear enough? BTW, expect kdeartwork 3.5.6-2 soon as the bug report has now been assigned. And to solve that problem, kdeartwork needs to be rebuilt to "let it know" that the screensavers are now in /usr/lib and not in /usr/libexec. Because of that, xscreensavers in KDE wouldn't work anymore. What I said was to rebuild kdeartwork because the new xscreensaver package now puts the screensavers in /usr/lib and not anymore in /usr/libexec. I don't actually understand what you meant. It's also nice to have some sort of check to make sure this only gets called when you are logging. This does not work with lightdm, which is what MX uses. All resources from files in /etc/X11/Xresources are merged with xrdb. xscreensaver and the New Login Button By default, xscreensaver looks for a service called gdmflexiserver to provide a New Login function from within the screensaver, so that a different user than has the screen locked can login. Make sure to also check DISPLAY, and all call xrdb if DISPLAY is set. Client arguments which are not path specifications are passed as arguments to a. Xresources on the CentOS machine, then the only way to do it would be to check on every login, e.g. The kdeartwork needs to be rebuilt as it expects to find the screensavers in /usr/libexec and not in /usr/lib where the screensavers are now actually residing.Īnd what is the reason for making a new package with the only difference that the screensavers being now in another directory? Or why has this be done before kdeartwork is rebuilt? Sorry, i don't see any advantage of this action and so i will stay with version 5.01-2 until i see here that all works fine as before. If this doesn't work for you, because you want to have your. ![]() Packaging bug actually (well technically not.).
0 Comments
Leave a Reply. |