Bug 161398 - Screensavers missing after upgrading FC3 to FC4 via DVD installer
Screensavers missing after upgrading FC3 to FC4 via DVD installer
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: xscreensaver (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-22 17:06 EDT by Vladimir Kotal
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-24 23:00:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vladimir Kotal 2005-06-22 17:06:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; cs-CZ; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
When upgraded FC3 to FC4 via installer supplied on DVD, all screensavers disappeared.

Version-Release number of selected component (if applicable):
xscreensaver-base-4.21-4

How reproducible:
Always

Steps to Reproduce:
1.upgrade (not reinstall) FC3 to FC4 via installer from DVD disk
2.open screensaver preferences when logged as arbitrary user
3.witness that there are no screensavers listed
  

Actual Results:  all screensavers which were present in previous installed release (FC3) are gone after upgrade to FC4 was performed.

Expected Results:  All screensavers present in FC3 should be preserved after upgrade to FC4.

Additional info:
Comment 1 Vladimir Kotal 2005-06-22 17:23:22 EDT
I have realized that the reason why screensavers were missing was that
xscreensaver-extras RPM disappeared during upgrade process. After installing it
from DVD, the screensavers are present again. (though screensaver settings are lost)
Comment 2 Ray Strode [halfline] 2005-06-24 23:00:13 EDT
Thanks!

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