Bug 169108 - avoid duplicate screensaver preferences
avoid duplicate screensaver preferences
Product: Fedora
Classification: Fedora
Component: redhat-menus (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
: 169109 (view as bug list)
Depends On:
Blocks: FC5Target
  Show dependency treegraph
Reported: 2005-09-22 23:06 EDT by Matthias Clasen
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-26 16:28:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matthias Clasen 2005-09-22 23:06:40 EDT
We need to find a way to show only the preferences menu entry for the
screensaver that is running, either xscreensaver or gnome-screensaver,
not both.
Comment 1 Mark McLoughlin 2005-09-26 10:42:43 EDT
*** Bug 169109 has been marked as a duplicate of this bug. ***
Comment 2 Mark McLoughlin 2005-09-26 11:11:57 EDT
Discussed briefly on irc, decided to add a
<MergeDir>/etc/xdg/menus/screensaver-properties-hack/</MergeDir> after the
<Include> in preferences.menu

gnome-screensaver would then install a .menu file in that dir containing
something like:

Comment 3 Ray Strode [halfline] 2005-09-26 16:28:06 EDT
Should be fixed in tomorrow's rawhide.
Comment 4 Mark McLoughlin 2005-09-27 03:09:53 EDT
Ray: I wouldn't use the preferences-merged dir - that already gets merged in at
a different point, so any .menu files will get merged in twice from there at
different points and could really confuse things.
Comment 5 Ray Strode [halfline] 2005-09-27 11:28:52 EDT
okay this should be fixed tomorrow.

I ended up with the name preferences-post-merged.  In retrospect it's not the
best choice because we would run into a similiar problem if we ever introduced
to a file called preferences-post.menu, but we can change it later if we need to.

Note You need to log in before you can comment on or make changes to this bug.