Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Suddenly missing icon shortcuts on new tab page.

  • 12 Mbohovái
  • 1 oguereko ko apañuái
  • 9 Hecha
  • Mbohovái ipaháva cor-el

more options

I just noticed today that my New Tab Page is now displaying an old set of icons (are they called bookmarks?) It might be associated with the recent update to v121, but I have lost several newer pinned icons. The display today is shown in the attached image, and I have drawn a red diagonal through icons that have not appeared on my New Tab Page for some time. I don't have a list or image of the recent ones that are gone missing.

I'm sure I'll eventually find and replace the ones that I lost, but this is just embarrassing for FF, which I use for just about everything.

If there's a way to revert, I'd like to know.

I just noticed today that my New Tab Page is now displaying an '''old''' set of icons (are they called bookmarks?) It might be associated with the recent update to v121, but I have lost several newer pinned icons. The display today is shown in the attached image, and I have drawn a red diagonal through icons that have not appeared on my New Tab Page for some time. I don't have a list or image of the recent ones that are gone missing. I'm sure I'll eventually find and replace the ones that I lost, but this is just embarrassing for FF, which I use for just about everything. If there's a way to revert, I'd like to know.
Mba’erechaha japyhypyre oñondivegua

Opaite Mbohovái (12)

more options

Did you previously had pages pinned to some of the tiles ? Pinned pages are stored in a pref on the about:config page, so if this file gets reset or you lose this pref otherwise, then you lose the pinned tabs and Firefox will fill them from the history.

Changes made manually on the Firefox Home page are stored in prefs that you can find on the about:config page. You can possibly backup the pinned pref to be able to recover pinned tiles. If you use dismiss a lot, then the blocked pref can grow quite large, an alternative is instead using remove from history.

more options

Yes, I had several pinned pages. I have not changed my pinned-page preferences for months, yet now the pinned pages are no longer visible. My prefs.js file lists the pinned pages that I see today--which is an obsolete list--and I have no idea where FF found that old list.

It's pretty clear that FF somehow lost my most recently pinned pages list and replaced it with an old list.

Any ideas on how to recover what I had a couple of days ago? What does it mean, "possibly backup the pinned pref to be able to recover pinned tiles"?

Thanks!

Moambuepyre MyUsernameHere rupive

more options
more options

Thanks for this reference. Unfortunately, I've already checked for other profiles, and the only one with any real data in it is the current one. There is one old profile that is essentially empty (only files are parent.lock, times.json, and cookies.sqlite).

I'm guessing that there is no way to recover these. In the future, I probably should include key FF files like prefs.js in my regular backup so I can recover from issues like this.

Meanwhile, I've mostly rebuilt my New Tab Page from memory and with a little searching on the interwebs. I'm missing a couple of pages, but I'm sure I'll run across them sometime and save them again.

Again, thanks for your help, and have a good day.

more options

No "Old Firefox Data" folder on the desktop as well?

more options

Sorry, no such folder.

more options

Did this happen while signed into a sync account?

more options

Yes, and I did sign in on a different computer a few days ago--one that I hadn't used for months. What is the protocol for syncing in situations like that?

more options

You can exclude pinned tabs from Sync via its services.sync.prefs.sync control pref.

  • about:config => services.sync.prefs.sync.browser.newtabpage.pinned => false
more options

It doesn't seem so simple.

In addition to the setting you cited, I found this boolean value set to true. It remains in bold no matter which value I set, leading me to believe it is a custom value: services.sync.prefs.sync-seen.browser.newtabpage.pinned I left it as I found it (true).

The one you mentioned was set to true. I changed it to false as you suggested: services.sync.prefs.sync.browser.newtabpage.pinned

This appeared at the bottom of the about:config list immediately after I changed the above to false: services.sync.prefs.sync-seen.services.sync.prefs.sync.browser.newtabpage.pinned = true I left it alone for now.

Can you explain these various settings?

Just in case, I saved the current list of pinned icons.

My next step would be to go back to computer #2 and open FF there. If nothing changes on computer #1, I could revert all the settings there and open FF on computer #2 again and expect it to sync.

I'll wait a while, though, to see if you have any additional thoughts based on these other settings.

Thanks!

more options

On computer #1, I just now changed the following setting back to true: services.sync.prefs.sync.browser.newtabpage.pinned

As it was the only setting I had changed, I went to computer #2 and opened a new tab.

The tab icons shown on both computers remained the same (they did not sync).

It makes me wonder whether my original problem was just a rare glitch.

I don't know how sync is really supposed to work, but it seems to me that it shouldn't replace new things with old things--yet that is what it did a couple of weeks ago with the new-tab icons.

For now, I think I'll let this one rest.

more options

The presence of services.sync.prefs.sync-seen.browser.newtabpage.pinned probably means that Firefox has noticed a browser.newtabpage.pinned pref on one of the other devices connected to Sync with its control pref enabled. I don't know if you need to set services.sync.prefs.sync.browser.newtabpage.pinned to false on all devices to disable syncing browser.newtabpage.pinned on all devices, the same for enabling syncing this pref.

See PREF_SYNC_SEEN_PREFIX: