chromium 22.x no favicons

[MilesAhead]

I'm running a chromium 21.x snap shot. Every time I try to update to one of the new 22.x snap shots, I lose all favicons. Seems to be a recurring problem with chrome browser. The snap shots have been 22.x for awhile now. I'm surprised nobody has picked up on this issue.

Even running Bookmark Sentry to manually load all my bookmarks to check they exist does not refresh the favicons. While the extension is running I can see favicons showing up in the bookmarks. But as soon as I close the browser and open it again, they are all gone.

Really weird.

I did notice a mention of a chrome extension named Bookmarks Favicon Fixer. But all searches end up pointing to dead links.

edit: I filed it as an issue on chromium bug tracker. See what happens.

 

[stevepoolstock]

What'd you expect? It's obviously a beta/alpha build, which means that every build might also have a regression over the previous. You might want to make things easy on you by just going for stability and leaving the newest test builds alone.

It's also very likely that this doesn't occur on every system running that 22.x build. You did the right thing by filing a bug report. The next build might not contain this bug, thanks to you!

 

[MilesAhead]

What'd you expect? It's obviously a beta/alpha build, which means that every build might also have a regression over the previous. You might want to make things easy on you by just going for stability and leaving the newest test builds alone.

It's also very likely that this doesn't occur on every system running that 22.x build. You did the right thing by filing a bug report. The next build might not contain this bug, thanks to you!

Thanks, but I'm familiar with snap shots. I've been using them over a year. Also I've been programming PCs since 1986. I don't really need you to inform me of the obvious, as you point out yourself.

What I expect is that if someone has found a word-around, they may post it. Telling me what I already know has little impact.

The bug was constant across every 22.x version I tried. That's why I posted a bug report.