Google Chrome: The check's in the mail

Having installed and then embarked on (what I thought would be) an exciting odyssey to configure two Linux distros on different partitions on the same laptop, and, upon having successfully resolved the initial challenges, such as finding the correct video driver, I find that I now look to the more subtler hiccups that seem to appear just as I am wrapping up the previous ones.

This particular stone in my shoe comes in the form of Google Chrome browser's infamous waiting for cache error.  It has invariably been described as a bug, but upon further investigation, I don't think that is accurate. Let me explain.

First off, if you don't know what cache is, then this entire article (as well as the title) will be completely lost on you.  Cache is basically a repository of temporary internet files.  It exists because back in the days when we accessed the internet via a dial up connection and paid through the nose for the privilege of obtaining very slow speeds (Hey, exactly like today!) cache was necessary so that our internet pages would load a little more quickly.  Cache is still necessary today, however, since our connections have improved (somewhat) it is no longer important to have a gargantuan sized cache file. Enter the Google Chrome browser.

The Problem

Once my attention was diverted from the fundamental configurations of my Linux distros, I noticed when I was browsing the web that the connection would often falter.  Of course, a certain amount of congestion is standard today given that everyone and his momma is online AND streaming bandwidth-sucking media AND the providers are all too happy to throttle your connection thanks to the lapdog tendencies of the FCC to its corporate masters.  (You didn't actually think that because you paid for the highest priced tier of internet access from one of only two providers (cable & DSL) in any given American market that you would actually get it, did you?) 


What I found was that this problem has been plaguing the Chrome browser dating back to 2009.  And while there have been fixes various & sunder , the silence from Google on the matter has been deafening. You'll not find a resolution on Google Groups, but, instead, you will find page after page of complaints about the issue.  But then this was to be expected.  You see, Google makes its money from advertising, and, if your cache size is gargantuan, and users are unable to set the size (unlike other browsers) then Google's business model is golden.  The browser reads your cache, makes note of where you've been and serves up all the appropriate ads accordingly. 

Were you conducting some research on self-publishing your novel?  Great!  Google will gladly display ads directing you to everything from publishing houses to agents. Were you then also searching for a homeopathic cure for that bothersome wart that has been squatting at the base of your index finger?  Fantastic!  Google will also cream itself to display wart-curing medicines and laser treatment centers for your viewing enjoyment.  

The Symptoms

When the connection was delayed, I noticed in the bottom left hand corner of the browser the words, "waiting for cache" and so decided to check it out further.  Essentially, the freeze is generated because Chrome's cache size is colossal by design. According to the httpCache page, cache is 33124585, or approximately 31 gigabytes.  Thirty one gigs is quite large to have to consult with for each and every click of the mouse when browsing the web. Imagine plugging in a thumb drive that size (which you can purchase relatively inexpensively) and with each internet URL you access, the connection must first scan the drive before it will load.  This is exactly the situation with Chrome. No wonder the browser sits there spinning.

It's not in Google's best interest to allow the user to adjust the cache size of Chrome, so you're stuck with the problem.  Don't wait for a fix because it won't be forthcoming any time soon.  Sure, you can use Mozilla, which has recently joined the ranks of the undead, ass kissing, sychophants of the Big Entertainment cartel, but let's face it, if you're using Chrome, it's because you like being able to log into the browser and have all of your bookmarks, extensions and other customizations available at your fingertips and not tied to any one device. 

The Resolution

Chrome flags

Ostensibly, in Windows, you could try this fix, but I haven't noticed any substantive result that wasn't achieved by installing the Click&Clean extension.  Note:  The extension is rather tedious as you must flush the cache respository manually each time.  And while it would be nice to think that Linux has the answer, the fact is, it does not.  At least not an obvious one. 

Linux has tricks that Windows users can only imagine, but trying to get help is like asking for a loan from a bank.  My experience with those who participate in Ubuntu Forums has varied from indifference to contempt.   The impression I have is that it seems to exist for the sole purpose of expressing condescension and disdain towards the person asking a question.  Unless, of course, you are properly reverential and metaphorically toss roses at the feet of the Venerated Ones. Perhaps then, you, worthless worm shall be acknowledged. 

While this group of self-important twits shall remain nameless, the fact is, a great majority of the so called moderators don't even know their ass from a hole in the ground, but as is typical of certain personalities exhibiting narcissistic tendencies, once they have a title (such as forum moderator), they then go tripping on it. In fact, I think that all forum moderators (particularly in the Linux world) should be given the title of Mr. Pink by default until it is decided by popular vote that they are not channeling their inner asshole.

If you didn't know, Mr. Pink was a character in Tarantino's Reservoir Dogs (1992) movie. He was the cheapskate who refused to pitch in a $1.00 tip for the waitress, and, his 'tude pretty much exemplifies some of the illustrious global Linux Community's demeanor towards anyone who doesn't know as much as they do.

©2014 Greensleeves and GreensleevesBikinIt.  Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited.  Excerpts and links may be used, provided that full and clear credit is giving to Greensleevs and GreensleevesBikinIt with appropriate and specific direction to the original content.

Linux: Video Adapter Blues

Having previously configged a beater laptop with the ability to triple boot, and, having enjoyed satisfaction oozing from pores while simultaneously thanking the Linux gods, it would only follow reason that now comes the tweaking, or, if you prefer, the tinkering.  After all, why the hell else would you have been interested in Linux in the first place if not to muck about?

But given that two of the three OSs on this laptop are fresh installs, the sum total of the tweaking has been limited to finding & installing the correct drivers, particularly for the video adapter, which, to my knowledge, has traditionally been a problem for Linux distros mostly because the video adapter manufacturers (such as nvidia) didn't want to play ball and acknowledge that (gasp/shock) consumers would actually want to use an alternative OS to Microsoft Windows, and, therefore, did not bother with providing its pain in the ass proprietary drivers to be even a little bit compatible with open source. As a result, open source had to code its own video drivers which did not always work.  In fact, back in 2005, I once spent 80 hours (yes, I logged my time) attempting to find the correct video driver for yet another beater Dell laptop in order to get Mepis and/or Kubuntu to render correctly.  I searched and spent hours upon hours trying various suggestions offered by the global Linux Community, but in the final analysis, it was a spectacular failure. The experience left me very frustrated and wanting to toss the computer through a window. Fast forward nine years and here we are today with similar frustrations caused by the damnable video adapter.

As previously mentioned, the hardware on this box is legacy, so finding drivers can be somewhat of a challenge, but on the other hand, what I've determined is that the age of the hardware and the search for the correct drivers for it seems to be six of one, half a dozen of the other in that don't go thinking that just because you may have a brand spanking new $3k laptop that finding and installing the appropriate video adapter will be a cakewalk. (Hint:  It may not necessarily be so.)  Conversely, just because you may have a legacy video adapter (in my case) don't assume either Linux (or the video adapter manufacturer) has an open source version for it.  Do you see the conundrum here?

My particular situation is thusly - Although I have previously determined that in order for successful video playback to occur, I would need to install Nvidia's legacy drivers.  After a few days of struggling with choppy video, I did just that.  And it worked out but only because the manufacturer had such drivers available.  The problem now is do I want to take the plunge and install the updates?

You may be wondering why I would hesitate, after all, you as a Windows user (most likely) would ask why not?  The answer is because sometimes, newer is not always better.  And in Linux, this is especially the case.  Sometimes you just have to be happy with what you've got.  If it works, then why fix what is not broken? While I tend to agree, it's not that cut & dried for me. You see, my Linux Mint partition is the Cinnamon edition desktop, specifically, version 1.4.0.  (the latest is 2.x). Cinnamon is to Linux Mint what Unity is to Ubuntu.  I don't actually have aspirations of upgrading to the latest/greatest version of Cinnamon simply because it probably wouldn't render correctly (if at all) on this box anyway, particularly given the legacy hardware.  However, I would like to upgrade Cinnamon to (at the very least) v. 1.6, or, if possible, even v. 1.8.  That way I would be able to take advantage of the improvements in those editions.  I want to use desklets, in particular, but v.1.4.0 does not support such a feature.

What to do...what to do...

I suppose I can bite the bullet and just install, but then I would run into (gasp/shock) the desktop possibly not booting up and the last thing I want to do is screw around with having to fix it.  Note here, I say this as if I would know how to do so off the top of my head. (I don't.)  A screw up caused by an incorrect/incompatible video adapter driver would entail some research how to fix it and I'm just not very keen on having to do such a thing.

Yes, well, that's what the users forum is for, eh?

Not so fast.

Although the Linux Community is famous for the breadth of issues posted and solved, and is used as a selling point for installing/learning Linux, I have personally found that the problems I have posted specific to my system seem to mystify the illustrious Community.  In fact, I have determined that while I am by no means a Linux Guru, I seem to be the only one who can resolve my system's issue(s) because when I post, the questions usually go unanswered, or, if answered, are done in a half-assed manner and/or contain incorrect information and/or are delivered with unmistakable contempt. So much for that whole The global Linux Community is there to help you sentiment.

So allow me to include the following disclaimer -you, dear audience, should know that if you're going to opt to use a Linux distro, altho you've got the esteemed above referenced Community to turn to for help (allegedly) as in life, you are, largely on your own when it comes to certain situations.

©2014 Greensleeves and GreensleevesBikinIt.  Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited.  Excerpts and links may be used, provided that full and clear credit is giving to Greensleevs and GreensleevesBikinIt with appropriate and specific direction to the original content.