RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1661696 - Newly created firefox profiles, no longer copy files from /usr/lib64/firefox/browser/defaults/profile.
Summary: Newly created firefox profiles, no longer copy files from /usr/lib64/firefox/...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firefox
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Martin Stransky
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-22 08:49 UTC by Vishal Pakolu
Modified: 2019-01-04 13:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-04 13:44:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vishal Pakolu 2018-12-22 08:49:50 UTC
Description of problem:

Newly created firefox profiles, no longer copy files from /usr/lib64/firefox/browser/defaults/profile.

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

working with firefox-45.7.0-2.el7_3 but fails with firefox-52.1.0-2.el7_3 and above.

Steps to Reproduce:

1) As user a 'usera' create a blank firefox profile by wiping out the .mozilla directory.

2) As user a 'usera' start firefox

3) Created some bookmarks
=> this should create an places.sqlite file under the newly created .mozilla directory.

4) As root copy this file to /usr/lib64/firefox/browser/defaults/profile

5) As root under /usr/lib64/firefox/browser/defaults/profile/ directory create a file with name xulstore.json with following contents

{"chrome://browser/content/browser.xul":{"navigator-toolbox":{"iconsize":"small"},"PersonalToolbar":{"collapsed":"false"}}}

6) As userb create a blank firefox profile by wiping out the .mozilla directory

7) As userb start firefox.

=> Userb should now have the same bookmarks as those created under usera.  The bookmarks should also be visible.



Actual results:

userb is not getting same bookmarks. 


Expected results:

Userb should now have the same bookmarks as those created under usera.  The bookmarks should also be visible.

Additional info:

Similar to issue in -> https://bugzilla.mozilla.org/show_bug.cgi?id=1269706

Comment 3 Martin Stransky 2019-01-04 13:42:06 UTC
Sorry, this mechanism has been deprecated long ago in Firefox 46 and can't be used any more. You need to copy the requested data to user profile by hand or by some script.

Also there's a fleetcomander project which aims to configure Firefox profile for large deployment - but I don't know how far is this project now.

Comment 4 Martin Stransky 2019-01-04 13:44:14 UTC
There's nothing we can do on the Firefox side.


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