Description of problem: The spec file for gnome-screensaver neglects to utilize $1 and $2 in the %triggerun sections. It also overwrites any existing .desktop files upon upgrade/reinstall. Also, there is a patch from ubantu that allows gnome-screensaver to correctly identify the gl visual for gl screensavers that has not been included in the spec. Version-Release number of selected component (if applicable): gnome-screensaver-2.14.2-1 How reproducible: examine gnome-screensaver.spec... install gnome screensaver, or attempt to run a gl-extras screenhack. Actual results: /usr/share/gnome-screensaver/themes contains none of the .desktop files for xscreensaver*extras screenhacks due to %triggerun removing them as quickly as it installed them in the %triggerin section. manually installing the .desktop files with the migrate-xscreensaver script populates the approproate desktop files, however any attempt to run a gl screensaver on a system using DRI results in a very nasty flicker effect because the default visual chosen by gnome-screensaver is the first returned; and that's not the correct visual on many DRI systems. Expected results: gnome screensaver is able to run gl screenhacks, correctly installes the .desktop files if xscreensaver-extras and/or xscreensaver-gl-extras is installed. .desktop files for xscreensaver-extras and/or xscreensaver-gl-extras should be removed when gnome-screensaver, xscreensaver-extras, or xscreensaver-gl-extras are removed. Additional info: All of the above is corrected in the .src.rpm I've attached to to this bug. The spec is commented; I won't have my feelings hurt if the ubantu patch is prettied up (hunk-offsets corrected, I was too lazy to type recountdiff)
Created attachment 132114 [details] Would use a patch, but it just seemed easier to provide the src.rpm includes ubantu "thow_shall_not_flicker" and "no_flicker" patches. and corrects the %trigger* sections (also uncommented the ac/am)
Hi, We no longer support Fedora Core 5 and I am currently trying to get my open bug count down to a more manageable state. I'm going to close this bug as WONTFIX. If this issue is still a concern for you, would you mind trying to reproduce on a supported version of Fedora and reopening? (this is a mass message)