[LL-user]

Fair enough, Jerry. You've got enough on your plate.
Let's just all help together to deal with these posts...

[JmaCWQ]

I think people getting confused is the reason so many posts & new threads are appearing about the issue.
People who aren't savvy of these things may not understand that a thread title referring to fixing Google Chrome is actually a fix for their updates failing.
People also may not understand that even though they've never had Chrome installed, they still need to run the fix.
Perhaps rename this thread, or highlight another thread/post to something like "Fix error couldn't fetch the package cache information lists when updating" and explain clearly in the first post that the fix needs to be run regardless if you've installed Chrome or not.
Maybe would clarify things a little and help prevent confusion, which may lead to less repeat posts/threads appearing on the same subject?

Just my two cents  8)

[valtam]

That is a good idea, however, the horse has already bolted and all our social media links, and existing forum links already point to this thread.

[avj]

Perhaps it would be a good idea to make a new forum section for announcing security/bug fixes to help draw attention to the fix.  Just a thought.

[JmaCWQ]

No worries Jerry, the main reason I mentioned it is because I've had a few people contact me saying "but we've never installed Google Chrome" or "we don't want to use Google Chrome" etc. etc...
Once it's explained it doesn't matter if Chrome is installed or not, the fix needs to be run so updates work correctly, everything is ok.
I was thinking even maybe an edit to this thread's first post to include that little snippet of info would be helpful.
Then those that aren't sure can see it clearly written there so they know without having to ask.

[paul1149]

That is a good idea, however, the horse has already bolted and all our social media links, and existing forum links already point to this thread.

You don't have to change the URL, Just change the notice to read "UPDATE ERRORS? Check out THIS thread". Like others, I saw the reference to Chrome and concluded the thread had nothing to do with my particular problem.  (Still haven't solved the problem. - correction, the problem is now solved! Hallelujah!)

[valtam]

New section - https://mityer.khdlhfjijfrupr.tk/forums/security-bug-fixes/

[marcos]

Help please
in my have
"dl.google.com/linux/talkplugin/deb/ stable main "

already I tried everything and I am still with this problem

[torreydale]

Uninstall Google Talk Browser Plugin using Lite Software.  (Menu > System > Lite Software)


If the above doesn't fix your problem, consider the following:
1) Go to your Menu.
2) Search for (ie. type in) Software & Updates.
3) Uncheck the selection for "dl.google.com/linux/talkplugin/deb/ stable main"

[N4RPS]

I take it chromium 32 bit is all OK- i.e not "back door" vulnerable??

Hello!

Chromium is OK, but doean't have the Widevine plugin, so I need Chrome to do Netflix without the netflix-desktop hack. Therefore, I keep a copy of 32-bit Chrome around, but I only use it to watch Netflix. Besides, I don't do anything critical, like finances, on that machine anyway.

The Arch and Slackware communties have had the Widevine plugin working in Chromium for some time, but it still hasn't made its way to the 'buntus yet. It's just as well they discontinued Linux 32-bit Chrome, I suppose.

On a 32-bit machine, or on any machine with under 4GB of RAM, Netflix seems to struggle anyway. It's gotten so bad that as of late, I've used PlayOn with the Windoze box to record the stuff for offline viewing...

73 DE N4RPS
Rob