Hi all...

During my research, I saw a thread here concerning this issue and I would agree that at least part of the problem may be a bug in Chrome and Chromium for Linux. I had a look at the Google certificate in question (GeoTrust Global CA) and, if I remember correctly, it was issued February 1st of this year and expires on April 26th. You really can't get any newer than that and I didn't really see any difference between it and the certificate I have on my Windows machine. I doubt I would get anything updated, certificate wise, even if I did figure out how to flush out all of them out and start over. It might be worth filing a bug report over this (for Chromium) but I'm not sure if I'll do that. I might even run a live copy of Lubuntu 16.04 (64 bit) later on just to see what happens in it.

For now, I'll hold off marking this as "SOLVED" while I still continue to work on this and in case anyone else wants to offer any suggestions.

Regards...

UPDATE: Fascinating, captain. I just tried out Lubuntu 16.04 (64 bit) on a live session and downloaded Chromium version 49 (an older version than what I have installed) and Chrome version 56 and everything works perfectly. Same Google certificate as far as I can tell. I guess TB0ne's suggestion of upgrading the OS looks like what will be needed, although this doesn't make any real sense and I would like to get this working correctly on my current copy of Lubuntu, if at all possible....

Regards...

"Doesn't make any real sense"???? Seriously?

You are using OLD SOFTWARE, including OLD CRYPTOGRAPHIC LIBRARIES; why does the inability of old software to run new security strike you as not making sense, even when you ran a newer version and didn't have the problem??

Correct.

Because on 16.04 I ran an older version of the Chromium browser and it worked fine. So then is it safe to assume that the cryptographic libraries you mentioned are OS based and not browser based?

Regards...

Cannot imagine how it doesn't make sense, despite it being explained to you multiple times, and you seeing EVIDENCE of this with your own eyes. Not quite sure exactly what else you need for it to make sense.
That is quite obvious isn't it??? You changed OS and it worked...that narrows it down, doesn't it??? Browsers are applications that run on an OS, and are obviously dependent ON the OS to function.

AGAIN Either remove whatever is preventing you from flushing your certificates from your browser, or update your OS. Those are you two options. Nothing else we can really tell you if you can't understand either of those solutions to your problem.

Hi...

Thank you again for your help.

Regards...

If this were my machine I would try to reset the router, firewall, clear certificates, cache and etc.
IF you are not able to get into the security settings it's most likely because:

From the page gradinaruvasile posted.

IF upgrading Chrome under your Lubuntu 14.04 doesn't help than something is most certainly not right.

Since Chrome works well for you under Lubuntu 16.04 I recommend installing Lubuntu 16.04.

-::-I was running Ubuntu 14.04 and Xubuntu 14.04 and started having all kinds of issue's. Applications failed to launch or took a long time to lauch, VLC didn't work and FF took entirely too long to launch.-::-

Upon performing a fresh installation of Xubuntu 16.04 everything was stable and ran exceptionally well.

http://serverfault.com/questions/279...omes-ssl-cache

Looks like others are having the same issue or similar to yours.
http://stackoverflow.com/questions/4...rects-to-https

I don't use Chrome. Sorry I don't know that much about it.
Try looking the the Google Chrome Help Forum.

https://productforums.google.com/for...#!forum/chrome

Are you getting an error when you launch Chrome from the cmd-line?

As others daid before, you might look at the openssl version you have on your system. Openssl is used by most programs that use some kind of encryption as a backend (this probably includes certificate processing). Newer Openssl versions have certain functions working differently.

Hi...

Thank you for your post and help.

I upgraded Chromium to the most recent available in the repositories but that didn't make a difference.

Yes, that's certainly a possibility. I was just hoping to be able hold off having to reinstall (and redo) all my programs, files, settings and configurations until it was absolutely necessary.

I did find this page and looked through it but it looked more complicated (and easy to mess up) than I wanted to get into.

Not a problem.

No, that actually works fine.

Regards...

1 members found this post helpful.

Hi...

Thank you, I actually did look into this and upgraded this to the newest version available in the repositories but unfortunately, it didn't help.

Regards...

That's completely understandable brother.

Maybe over the course you could be able to backup your system in order to perform a fresh installation of 16.04.

-::-It appears that you are nearing the 'absolutely necessary' stage.-::-

If you're dreading the installer I'd be happy to help you.

Are you in a dual boot with another Linux os?
If so, gparted is your friend.

That's one thing I try to keep up on, I've had too many hard drive failures!

Thank you but that's probably one of the easiest parts for me.

No, it's only 14.04 so far.

Regards...

This makes sense because Chrome version 56 is considered to be a stable and supported release. The former version you cite, 46, is discontinued https://en.wikipedia.org/wiki/Google...ersion_history. Note also that the version of Chrome you're citing post dates Lubuntu 14.04 by 2 or more years. Have you kept up with updates for Lubuntu along with upgrading Chrome? Bottom line is you either keep up with updates, or you choose to not. Installing newer software onto an older distribution will eventually lead towards these types of problems. Not the end of the world, but you should not expect things to continue to work always and forever.

You can reinstall Lubuntu default 14.04 and upgrade it with all updates which do not upgrade the distribution, as long as they provide updates and support for the release. Once they stop, they stop.

I do not recommend installing Chrome up to the latest version until you review the documentation and research whether or not a particular release of Chrome is tested and suitable for that version of Lubuntu.

This is a classical situation where you're trying to merge an old OS with newer software. This can be done, however in some cases there may be problems.

Hi...

Thank you for your reply.

I'm using the 32 bit version of Lubuntu 14.04 so version 49 of Chrome is as high as I can go, hence why I didn't upgrade beyond 46. Version 49 also came with the annoying yellow banner warning users that 32 bit support was ending and I didn't want to put up with that. I originally installed a 32 bit version of Lubuntu because, in the past, I found that certain programs worked better in a native 32 bit environment but I see that my days of being able to do that are drawing to a close and that using 64 bit operating systems will be a necessity.

As TB0ne indicated as well, upgrading to a newer version of Lubuntu will most likely be the only solution to this.

Regards...

it's probably rejecting you by having detected your a file shark.

fully uninstall. that means all dependancies. re-install. if that don't work use a "real OS" that compiles firefox from scratch without allot of headaches or build failures. it should be working then.

if not: then perhaps your authentication libraries are used by firefox and have become changed (ie, openssl). unfortunately, there are so many auth mechs these days (not just openssl: tens or hundreds of knotted auth libs PLUS kernel auth support PLUS hardware auth support)

back up from this problem: don't get so close it swallows you. try the version of firefox (chrome flavor) that last worked first.