On Mon, Mar 3, 2008 at 3:12 AM, Frans Pop <[EMAIL PROTECTED]> wrote: > > After upgrading to this version of xscreensaver I noticed that the KDE > controlcenter module used to configure the screensaver now lists a > number of screensavers that no longer work. > > Apparently the list of available screensavers does not get updated. > > The reason seems to be that the following file is still installed: > /usr/share/applnk/System/ScreenSavers/phosphor.desktop > This file is installed by the package kscreensaver-xsavers. >
Thanks for your report. Several hacks have been moved to the xscreensaver-data-extra (and xscreensaver-gl-extra) package. Just install that package and the broken kscreensaver will work fine again. > > Evidently the package split should have been coordinated with packages > depending on xscreensaver. > We don't expect any major problems. All the files are practically the same, just in two packages. We could choose to drag in both packages during the upgrade, but chose to do user education instead, to make the future better. Sorry, personally I know nothing about kscreensaver-xsavers. I will be pleased to work together with you to make it work properly. Believe me, the reason for the package split is exactly to make things easier for third-party screensaver infrastructures (like gnome-screensaver and kscreensaver), so that they can use xscreensaver hacks without the user having xscreensaver installed. The split in -extra is currently the only way to split between safe, recommended hacks and those who often can cause problems. > > >From this point of view the package split can be said to break existing > installations, which is a release critical issue. This BR is necessary > to prevent the new xscreensaver to migrate to testing until the required > coordination has taken place and depending packages have been updated. > Apparantly, the package split exposes a weakness in the kscreensaver package. Does it have a list of screensaver hacks hardcoded? Your mentioning of its /usr/share/applnk/System/ScreenSavers/phosphor.desktop file sounds a bit like this. It should be made to dynamically deal with the available screensavers in /usr/share/applications/screensavers. Also other packages might drop .desktop files in there if they have something suitable as a screensaver. IMO, only the package shipping a hack should also ship a .desktop for it, whether in /usr/share/applnk/System/ScreenSavers or /usr/share/applications/screensavers. Anyway, the .desktop files should have a TryExec entry to check for the existence of the hack binary. Maybe you just need to update the relevant .desktop files. Without knowing kscreensaver much, I think the best solution would be to stop kscreensaver from shipping .desktop files and rather let it look for the desktop files installed by other packages. On the short term, just let kscreensaver depend on xscreensaver-data-extra, but remove the dependency later once kscreensaver is fixed properly. Cheers, Tormod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
