Bug 2025120

Summary: Homepage is reset to opens start.fedoraproject.org
Product: [Fedora] Fedora Reporter: Andrew Barchuk <andrew>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: erack, gecko-bugs-nobody, jhorak, kai-engert-fedora, klaas, kurobeats, pjasicek, rhughes, rstrode, sandmann, stransky
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-30 18:30:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrew Barchuk 2021-11-19 23:17:55 UTC 
Description of problem:

Whenever I change the homepage it's being reset to the default value of opens start.fedoraproject.org after a while.

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


How reproducible:


Steps to Reproduce:
1. Open about:preferences
2. New Windows and Tabs -> Homepage and new windows: change to Firefox Home (Default)
3. Start Firefox after a couple of days.

Actual results: start.fedoraproject.org is opened


Expected results: see the deafult Firefo homepage


Additional info: -
Comment 1 Phil Coulson 2021-11-21 07:27:44 UTC 
I have noticed this will occur on update, that is, no matter what I have set in Firefox in Settings > General > Homepage and new windows, after an update it is set to start.fedoraproject.org

Can I point out I have been willingly ignoring this bug since at least Fedora 32 (before that I forget) but came to create a bug report (same as Andrew has) because of the update to 94.0. My suggestion is to not replace user preferences with package defaults, it creates a negative experience for the user.
Comment 2 Martin Stransky 2021-11-22 07:56:00 UTC 
Dupe of Bug 2020436 ?
Comment 3 Andrew Barchuk 2021-11-30 18:30:31 UTC 
It does look like in my case also the issue is only happening once a package update is installed. I will close this one as a duplicate of the bug Martin referred.

*** This bug has been marked as a duplicate of bug 2020436 ***