Summary: | www-client/mozilla-firefox-2.0.0.1 asks twice for master password | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jaak Ristioja <jaak> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | VERIFIED INVALID | ||
Severity: | normal | CC: | kccricket |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jaak Ristioja
2007-01-11 19:09:33 UTC
There are way to migrate your passwd/bookmarks/etc to a new profile ... You should read a bit more about how mozilla works before filing bugs with us. This is not a problem with out build it is an issue with upstream breaking compatibility with profiles from older versions. (In reply to comment #1) > There are way to migrate your passwd/bookmarks/etc to a new profile ... You > should read a bit more about how mozilla works before filing bugs with us. > This is not a problem with out build it is an issue with upstream breaking > compatibility with profiles from older versions. Sorry, I didn't know I had to know something most regular firefox-users don't know to file a bug. I searched this bugzilla, I searched the mozilla bugzilla. I think it would be a bit much to ask users to do a research project on firefox before filing a bug. This is still a bug as firefox is expected to work properly after an upgrade. At minimum, a notice to the ebuild, stating that profiles might break due to the upgrade, would be nice. (including references to documentation on how to migrate your profile to the new firefox) :) The current notice states: "Before filing any bugs, please move or remove ~/.mozilla and test with a clean profile directory.". If you read my first post, you will see, that I did indeed test this with a clean profile before filing this bug. :D Anyway, something like this would do: "An upgrade to version #.# might break users' profiles. If you experience any issues, please test with a clean profile directory. In case the problem disappears see the Firefox Users Profile Migration Guide at $URI on how to migrate your profile. If you still experience the issue, please file a bug." Please correct this issue. Thanks :) I fail to see how this is an upstream issue when this behavior does not occur with www-client/mozilla-firefox-bin-2.0.0.1. As I know you're well aware, migrating to a new profile is not a fix for this bug, just a workaround. Hasn't occured in recent 2.0.0.* versions. However I'm still using a migrated profile. Closing. |