Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 244448 - Upgrade to Fedora 7 still points to Fedora Core 6 folder
Upgrade to Fedora 7 still points to Fedora Core 6 folder
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Gecko Maintainer
Depends On:
  Show dependency treegraph
Reported: 2007-06-15 14:42 EDT by Peter Ennis
Modified: 2007-11-30 17:12 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-15 15:48:16 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 Peter Ennis 2007-06-15 14:42:20 EDT
Description of problem:

I did a yum upgrade from FC6->FC7.
It worked well - even though the recommendation
to do this is "don't". Good job!
(My system would not boot from a USB External DVD
so I went this route.)

The folder list in Firefox shows:

Release Notes
Fedora Project
Fedora Weekly News
Community Support
Fedora Core 6
Red Hat Magazine

Should the Fedora Core 6 be Fedora 7
and point to the new files?

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Ignacio Vazquez-Abrams 2007-06-15 14:57:26 EDT
Do you see this problem on a fresh Firefox profile? Use "firefox
-ProfileManager" to create and start a new profile.
Comment 2 Christopher Aillon 2007-06-15 15:48:16 EDT
Bookmarks are a one time thing.  Once you have a bookmarks file, they are never
overwritten.  So, you started firefox, got the FC6 bookmarks, and then they stay
the same on upgrading.  Can't really do anything about this...
Comment 3 Peter Ennis 2007-06-15 16:46:38 EDT
firefox -ProfileManager
fixes it.

Thanks :)

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