Update manager issue (Chrome related) [SOLVED]

[killer de bug]

Who cares. Chrome is no longer supported. Use Chomium instead

You obviously don't know what you are speaking about...

[3rdtimer]

I respectfully disagree. In the past, I have noticed Chrome's update behavior as demonstrated in the video linked below.

https://www.youtube.com/watch?v=AjrjrhNO-yc

I don't see what the connection is between Mint's Chrome update settings being disabled and Chrome updating itself once it connects to Goggle's servers. Once it connects, if an update is available it does so as per the video. I think the key to a sucessful update is the practice of opening and closing Chrome itself.......not depending on a Mint repository setting.

Am I getting warmer?

[JoeFootball]

I IMO, think it is really dumb that the good people at Mint stopped supporting Chrome...

I'm not sure the Linux Mint team has anything to do with Google's lack of support of 32-bit Chrome.

[JazzAzz]

Who cares. Chrome is no longer supported. Use Chomium instead

You obviously don't know what you are speaking about...

You don't know what you are talking about since I rec'd several pop up message that Chrome was no longer or very soon would no longer be supported, which is why I switched to Chromium. Look it up, Googe it!!!!

[Pjotr]

Who cares. Chrome is no longer supported. Use Chomium instead

You obviously don't know what you are speaking about...

You don't know what you are talking about since I rec'd several pop up message that Chrome was no longer or very soon would no longer be supported, which is why I switched to Chromium. Look it up, Googe it!!!!

No, you do that. Your claim is incorrect.

Only 32-bit Chrome for Linux has been discontinued. Not 64-bit.

[JazzAzz]

You obviously don't know what you are speaking about...

You don't know what you are talking about since I rec'd several pop up message that Chrome was no longer or very soon would no longer be supported, which is why I switched to Chromium. Look it up, Googe it!!!!

No, you do that. Your claim is incorrect.

Only 32-bit Chrome for Linux has been discontinued. Not 64-bit.

Well I was referring to my issue since I started the ,"red x" thread and mine is 32!!

[Pjotr]

Well I was referring to my issue since I started the ,"red x" thread and mine is 32!!

You did not start this thread and 64-bit Chrome users also see the red X. That's a bug for 64-bit Chrome which is harmless but annoying.

[JeremyB]

Well I was referring to my issue since I started the ,"red x" thread and mine is 32!!

You did not start this thread and 64-bit Chrome users also see the red X. That's a bug for 64-bit Chrome which is harmless but annoying.

Only one way to eliminate the red x for 64 bit users with 64 bit google chrome

Code: Select all

sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/etc/apt/sources.list.d/google-chrome.list"
sudo chattr +i /etc/apt/sources.list.d/google-chrome.list

A new google chrome download over writes the sources list and the opt/cron/ file. If google fixes the issue the second command might need to be reversed with

Code: Select all

sudo chattr -i /etc/apt/sources.list.d/google-chrome.list

[JazzAzz]

Well I was referring to my issue since I started the ,"red x" thread and mine is 32!!

You did not start this thread and 64-bit Chrome users also see the red X. That's a bug for 64-bit Chrome which is harmless but annoying.

Pay attention. I did not say THIS THREAD but the, "Red X," thread, viewtopic.php?f=90&t=217785&hilit=update+manager

And I was referring about MY situation, and I mentioned that I have a 32bit machine!!


I am not aware about Google Chromes status concerning 64 bits, although it has been clarified in this thread. Thank-yoiu guys for that.

[killer de bug]

I respectfully disagree. In the past, I have noticed Chrome's update behavior as demonstrated in the video linked below.

https://www.youtube.com/watch?v=AjrjrhNO-yc

I don't see what the connection is between Mint's Chrome update settings being disabled and Chrome updating itself once it connects to Goggle's servers. Once it connects, if an update is available it does so as per the video. I think the key to a sucessful update is the practice of opening and closing Chrome itself.......not depending on a Mint repository setting.

This is not the way it should work. On Linux this feature is disabled. Updating occurs from the repository meaning the address you have disabled.

If your Chrome is really updating this way, you should be worried. It means that the installer has root access. This is really bad. Really really bad for you.

[killer de bug]

Pay attention. I did not say THIS THREAD but the, "Red X," thread, viewtopic.php?f=90&t=217785&hilit=update+manager

Let's focus on this problem. Yours has its own topic.

Back to the 64 bits version of Chrome. Thanks everyone.

[Pjotr]

This should be a permanent solution which doesn't get reverted:

Code: Select all

gksudo gedit /etc/apt/sources.list.d/google-chrome.list

Comment out the existing repo line with a hash tag:

Code: Select all

# deb http://dl.google.com/linux/chrome/deb/ stable main

Save and close.

Then create another list file with a slightly different name, which won't be overwritten because of that name difference:

Code: Select all

gksudo gedit /etc/apt/sources.list.d/chrome.list

Copy/paste this line into it:

Code: Select all

deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main

Save and close.

(slightly improved version of the solution published at Distrowatch: http://distrowatch.com/weekly.php?issue=20160307#news )

But it's probably best to just wait until Google fixes this. After all, it's an innocent bug which doesn't prevent you from getting updates for Google Chrome....

[don250r]

see my post on the other thread: viewtopic.php?f=90&t=217888

[JazzAzz]

Pay attention. I did not say THIS THREAD but the, "Red X," thread, viewtopic.php?f=90&t=217785&hilit=update+manager

Let's focus on this problem. Yours has its own topic.

Back to the 64 bits version of Chrome. Thanks everyone.

Sorry but I am confused. I did get your PM, but I see other threads referenced all the time in here???!!!

I see nothing wrong with this when I or anyone else does it, if it is relevant to the current issue.

Maybe it is best for me to just not post at all, sorry.

[3rdtimer]

killer de bug wrote: This is not the way it should work. On Linux this feature is disabled. Updating occurs from the repository meaning the address you have disabled.

If your Chrome is really updating this way, you should be worried. It means that the installer has root access. This is really bad. Really really bad for you.

Yea.....I see what your saying. In fact I noticed the stable version of Chrome did not update to .87 (the latest) and the "red x" showed up again. So, I re-enabled the Google line in the repository, applied Jeremy B's solution and so far, so good....no "red x". I am to the point of just forgetting about the "red x" as others have suggested and wait for Google to fix it. I have not looked to see if they are getting feedback about it or not.

Thanks for the feedback.