Chrome is out of date in MX-23.2 Xfce [Solved]

[Mauser]

You should be able to uncheck the solve checkmark on post 16

Before when I still had a problem I didn't see any check at that time when the title said Solved even though I didn't mark it Solved at that time. I have since fixed the problem with my computer which is why I now put a check on #16 to mark it as solved. Something weird happen on the forum that caused that problem.

[richb]

I unchecked when you stated you did not mark it Solved.

[j2mcgreg]

@Mauser
I notice that your main repository is the R.I.T. mirror. I've had similar problems to what you have reported here in the past when using that mirror, so I suggest that you switch to the Salt Lake City mirror instead.

[DukeComposed]

tmp says: Owner: root(root) Access: Read&Write
Group: Mauser Access: Read&Write
Others Access: Read
It won't let me change the file permissions because it refuses to let me open the File System as root because there is no such option. :mad:

I'm a little surprised that there's no option for "Open root Thunar here" when you right-click on something in Thunar: empty space in the display panel, or on one of the directories in the sidebar. I suspect that the "Others: Read" access may have been causing problems. Even though "sudo" runs commands as the system superuser, the superuser can invoke programs as other accounts. I have an "_apt" user account in /etc/passwd and, I'm just spitballing here, I bet apt, dpkg, and Synaptic use that account to run package management actions, like, for instance, creating temporary files in /tmp to validate signing keys when checking for updates.

[DukeComposed]

@Mauser
I notice that your main repository is the R.I.T. mirror. I've had similar problems to what you have reported here in the past when using that mirror, so I suggest that you switch to the Salt Lake City mirror instead.

MX Repo Manager has an option to choose the fastest mirror from among a list of repos. I'm not sure there's an easy way to disable any of the repos on that list. The best thing I've found if you want to block any specific mirror, even if it could end up being the fastest option in MX Repo Manager, is to manually edit /usr/share/mx-repo-list/repos.txt.

[j2mcgreg]

@DukeComposed wrote:

MX Repo Manager has an option to choose the fastest mirror from among a list of repos. I'm not sure there's an easy way to disable any of the repos on that list. The best thing I've found if you want to block any specific mirror, even if it could end up being the fastest option in MX Repo Manager, is to manually edit /usr/share/mx-repo-list/repos.txt.

In this case, reliability is a more important factor than speed. When a user first installs MX, the main repository is selected automatically by geographical proximity; IE the closer a user is to a mirror, the faster, in theory, his / her connection should be, but this doesn't take into account the actual number of hops it takes for a request to make the return trip (user --> repository --> user). It also doesn't consider whether mirrors located at universities and colleges see their reliability suffer in the interval between one term ending and a new one beginning , and a myriad of other human and physical factors. If the OP does switch his main repo to SLC, he might experience an imperceptible speed loss, but that would be compensated by his not having to repeat actions when an update is not available in a timely fashion or the requested package isn't available yet.

[dolphin_oracle]

switching repo will do nothing for the google-chrome issue that started this thread. lets keep on target here please. the issue is not the repo, its local. Mauser has chosen not to share what he did to fix the issue, so this issue is done.

[j2mcgreg]

switching repo will do nothing for the google-chrome issue that started this thread. lets keep on target here please. the issue is not the repo, its local. Mauser has chosen not to share what he did to fix the issue, so this issue is done.

It does actually, Both @Eadwine Rose and I got the updated version of Chrome prior to the OP posting his issue. The most logical answer for this anomaly is that the OP's main repo is out of sync.