Being a generally untrusting person, I want to be able to try an update
and revert to my previous version if I don't like the new one.
I download and untar the new version (157 in this case).
Start it from within its own separate subdirectory and generate a new profile.
Shut it down.
Copy (cp -raf *) over ALL the contents of the old profile.
Restart and test.
Looked OK, but I didn't want to deal with making it the current version
yet. When I closed 157 and restarted 150 I was told that firefox
wouldnt work with a profile newer than the version and it demanded that
I either quit or make a new profile. I quit. I tried again. Same
thing. 150 worked fine with that profile only half an hour ago.
Tried again: ./firefox from within the FF150 subdirectory. This time
it brought up FF157 with the selected old profile with all my tabs gone.
I find this maddening. Is there a simple explanation? Should I have
done something different? My procedure has been working for decades --
until today :-(
Being a generally untrusting person, I want to be able to try an update
and revert to my previous version if I don't like the new one.
I download and untar the new version (157 in this case).
Start it from within its own separate subdirectory and generate a new profile.
Shut it down.
Copy (cp -raf *) over ALL the contents of the old profile.
Restart and test.
The Real Bev <bashley101@gmail.com> wrote:
Being a generally untrusting person, I want to be able to try an update
and revert to my previous version if I don't like the new one.
I download and untar the new version (157 in this case).
Start it from within its own separate subdirectory and generate a new
profile.
Shut it down.
Copy (cp -raf *) over ALL the contents of the old profile.
Restart and test.
The profile files are usually created relative to the user's home
directory in Linux, not the installation directory, so I'm not sure
what you were copying where.
But note that Firefox might now store
some things under ~/.config and ~/.local rather than ~/.mozilla
since it adopted the "XDG Base Directory Specification":
https://www.phoronix.com/news/Firefox-147-XDG-Base-DirectoryI have always left the previously-current firefox files and associated
I think it only creates the new locations if there's no existing
~/.mozilla directory when it starts up, but maybe you did that at
one point and it switched over to the new paths as a result,
ignoring the old ~/.mozilla directory that you copied back
afterwards?
I download and untar the new version (157 in this case).
Start it from within its own separate subdirectory and generate a new profile.
Shut it down.
Copy (cp -raf *) over ALL the contents of the old profile.
Restart and test.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:13:23 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,449 |