Izimpendulo zakamuva ze-Favicon icons seem scrambledhttps://support.mozilla.org/zu/questions/12619062019-11-15T11:59:50-08:00Yeah. I had this problem for a long time. I ran some queries on the sqlite tables, and tried the sug2019-11-15T11:59:50-08:00nroosehttps://support.mozilla.org/zu/questions/1261906#answer-1266943<p>Yeah. I had this problem for a long time. I ran some queries on the sqlite tables, and tried the suggestion in other places to delete specific or all of the favicon rows before finally just removing the file. To me it looked like the ids in the tables before I deleted the file were just too high for them to work. One of them was 47,357,795,150,914. Seems like that is 10x the limit for unsigned 16 bit integer. Another column had numbers like 4,176,269,289, which is very close to that unsigned 16 bit max as well. So perhaps some part of the code that uses them are munging that number and getting the wrong icon. I have no idea how they got that high. This is definitely a bug in Firefox. Please fix it.
</p>I had a similar problem but less global than RexSmith70's. I had just two wrong favicons, for Google2019-09-22T05:23:28-07:00AmateurHistorianhttps://support.mozilla.org/zu/questions/1261906#answer-1254147<p>I had a similar problem but less global than RexSmith70's. I had just two wrong favicons, for Google Docs and Google Drive. Verify Integrity didn't do anything, but deleting favicons.sqlite fixed the problem. Thanks, cor-el.
</p>In order - I tried clicking the "Verify Integrity" button - and no fix.
Next - I renamed the favicon2019-06-14T07:29:09-07:00RexSmith70https://support.mozilla.org/zu/questions/1261906#answer-1230446<p>In order - I tried clicking the "Verify Integrity" button - and no fix.
Next - I renamed the favicons.splite file - (I renamed to OLD.favicons.splite ) that seems to have fixed things. As I go back to sites in my menus - it recaptures the current favicon files from the sites and displays correctly, now.
</p><p>Thank you!
</p>Could be a problem with the favicons.sqlite in the profile folder that stores favicons.
If you use S2019-06-13T06:19:52-07:00cor-elhttps://support.mozilla.org/zu/questions/1261906#answer-1230090<p>Could be a problem with the favicons.sqlite in the profile folder that stores favicons.
</p><p>If you use Sync then best is to disconnect Sync temporarily during troubleshooting.
</p><p>You can check for problems with the <b>places.sqlite</b> and <b>favicons.sqlite</b> files in the Firefox profile folder.
</p>
<ul><li>use "Verify Integrity" button on the "Help -&gt; Troubleshooting Information" (about:support) page
</li></ul>
<p>In case errors are reported with "Verify Integrity" close and restart Firefox and retry.
</p><p>If "Verify Integrity" cannot repair the favicon database then try to remove favicons.sqlite in the profile folder with Firefox closed.
You need to visit (click) a bookmark to make Firefox retrieve the favicon.
If this didn't help then rename/remove places.sqlite as well.
Firefox will rebuild places.sqlite and restore the bookmarks from a recent JSON backup in the bookmarkbackups folder.
</p>
<ul><li>keep a backup copy of places.sqlite in case a new places.sqlite database has to be created
</li></ul>
<p>You can use the button on the "Help -&gt; Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the <b>about:profiles</b> page.
</p>
<ul><li>Help -&gt; Troubleshooting Information -&gt; Profile Directory:<br>Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder
</li><li><a href="http://kb.mozillazine.org/Profile_folder_-_Firefox" rel="nofollow">http://kb.mozillazine.org/Profile_folder_-_Firefox</a>
</li></ul>
<p>See also:
</p>
<ul><li><a href="https://support.mozilla.org/en-US/kb/Bookmarks+not+saved#w_fix-the-bookmarks-file" rel="nofollow">https://support.mozilla.org/en-US/kb/Bookmarks+not+saved#w_fix-the-bookmarks-file</a>
</li><li><a href="https://support.mozilla.org/en-US/kb/fix-bookmarks-and-history-will-not-be-functional" rel="nofollow">https://support.mozilla.org/en-US/kb/fix-bookmarks-and-history-will-not-be-functional</a>
</li></ul>