similar to: Google Chrome

Hi I've installed CentOs 6 successfully, but, Firefox does't lunch. I've downloaded Chrome and when I try to execute "google-chrome &" command, I had command not found. --

Hey All, What's with this? google-chrome-stable-28.0.1500.45-205727.i386 requires libstdc++.so.6(GLIBCXX_3.4.15) : Success - empty transaction I got a software update notice that offered google-chrome, but when I tried to install the update I got a dependency issue. Is this a bug in the package or is it time to give up on Chrome? -- _ ?v? /(_)\ ^ ^ Mark LaPierre

On 10/19/2015 04:11 PM, Richard wrote: > > I was seeing issues like that on centos-7 with a couple of the > recent releases of chrome. What I found was that chrome didn't seem > to be shutting down fully -- leaving a process and the > ".com.google.Chrome..." lock file in /tmp. After cleaning those up > chrome would restart without issue. The release that you're

I tried to install Google Chrome and received the dependencies error. Is Centos too old for the new Chrome or is there an older Chrome version that is compatible? Todd -- Ariste Software Petaluma, CA 94952 http://www.aristesoftware.com

On a centos-7 machine where I was having this issue, updating just chrome from: google-chrome-stable-45.0.2454.101-1.x86_64 to: google-chrome-stable-46.0.2490.71-1.x86_64 seemed to resolve this problem. I realize that the OP is reporting this issue, on C6, with the release I just updated to. By the way, I haven't run into this problem with the versions from their beta release channel.

Has anyone tested installing the newer kernels from elrepo (or somewhere else) in order to keep google-chrome updated beyond version 27? Actually, i assumed a newer kernel would come with a newer glibc but i do not see a newer glibc via elrepo, just newer kernels. hmmm. # yum --disablerepo=* --enablerepo=elrepo* info glibc | grep -i repo only lists my already installed glibc packages from

I've installed Google Chrome using the Richard Lloyd 'install-chrome.sh' script (http://chrome.richardlloyd.org.uk/), and am finding a couple of nagging issues. (Current install is google-chrome-stable-46.0.2490.71-1.x86_64). First, every time I shut down Chrome and start it back up, it whines about not having been shut down "properly." Second, and worse, at start up,

Google Chrome Terms of Service(Google Chrome executable),?BSD?(source code and Chromium executable except chromium 5 beta),BSD License?with proprietary parts (source code and chromium 5 beta executable, as it integrates?Adobe Flash Player?10.1[1])[2] http://en.wikipedia.org/wiki/Google_Chrome in my?interpretation, this means Google Chrome is fully open-source, only the flash player has proprietary

Hi, Is CentOS good for a desktop machine? I have been using Fedora but the whole GNOME 3 debacle has me scrambling for something else. I have a few "minimal" CentOS servers but does anyone here use CentOS on their laptop? Does wireless and suspend work ok? Are there packages for the usual desktop stuff like libreoffice, sylpheed and so on? Machine is Toshiba Portege R935. It's

Hi all. I've updated google-chrome to recent version and it gets unbooted, when I fired google-chrome up I got messages like these: /usr/bin/google-chrome: /lib/libz.so.1: no version information available (required by /usr/bin/google-chrome) /usr/bin/google-chrome: /lib/libz.so.1: no version information available (required by /usr/bin/google-chrome) /opt/google/chrome/chrome:

On Thu, Dec 17, 2015 at 04:28:01PM -0500, Jonathan Billings wrote: > On Thu, Dec 17, 2015 at 08:37:32PM +0000, Richard wrote: > > > > I'm seeing the following banner when I start up google-chrome > > 48-beta (48.0.2564.48 beta (64-bit)) on my 7.2 machines: > > > > This computer will soon stop receiving Google Chrome updates > > because this Linux

I started using chrome on the RHEL7 beta after some firefox hangs - but maybe this behavior is generic. I have the system 'network settings/network proxy' set to use squid on another host for connections out of the private range we use. This proxy requires authentication so I can always tell the first time a browser uses it. However, I can start a chrome connection to gmail and it

> Date: Thursday, December 17, 2015 16:28:01 -0500 > From: Jonathan Billings <billings at negate.org> > > On Thu, Dec 17, 2015 at 08:37:32PM +0000, Richard wrote: >> >> I'm seeing the following banner when I start up google-chrome >> 48-beta (48.0.2564.48 beta (64-bit)) on my 7.2 machines: >> >> This computer will soon stop receiving Google

I'm seeing the following banner when I start up google-chrome 48-beta (48.0.2564.48 beta (64-bit)) on my 7.2 machines: This computer will soon stop receiving Google Chrome updates because this Linux system will no longer be supported. Does this portend a support issue for chrome on centos-7 in a few months when the underlying changes make their way into their -stable (since, as I

I know there is a version for Linux, but using Chrome in wine is solely for testing purposes. Wine is also being run inside a VM (Ubuntu 10.04). This is wine 1.2 configured with the flag --with-gnutls. DLL overrides are for riched 20 and riched 32 (both native, builtin). Chrome is run from the command line with the options --new-http --in-process-plugins used. The display is just fine and the

Current midori builds in mock, I just tried, but the BuildRequires appear to be wrong because not all the extensions are built resulting in not all extensions found in %files section being there. I'll look at the build log and maybe see if there is a way to make it work and file bug report with fix + EPEL build request if I can get it to work. I know it's not chrome, but it is webkit

Hi all, Just recently I started getting the dreaded message about my CentOS 6.7 x64-installation wasn't going to be supported anymore by Google Chrome. "This computer will soon stop receiving Google Chrome updates because this Linux system will no longer be supported." Doing some google searches I found this;

> On Mon, Jan 25, 2016 at 2:18 AM, Sorin Srbu <Sorin.Srbu at orgfarm.uu.se> >> Just recently I started getting the dreaded message about my CentOS 6.7 >> x64-installation wasn't going to be supported anymore by Google Chrome. >> >> "This computer will soon stop receiving Google Chrome updates because this >> Linux system will no longer be

Hello, I've been using webrtc (Jscommunicator) with Asterisk occasionally. Only problem until now which remained was that if dtls_rekey was set to the value other than 0, call hanged up when using chrome after the time where dtls_rekey was set. I suppose that "bad media description" shown in Chrome's window which causes call to fail, has appeared with Chromes newer versions

On Fri, December 18, 2015 7:34 am, Jonathan Billings wrote: > On Thu, Dec 17, 2015 at 09:38:40PM +0000, Richard wrote: >> On the linked-to help page: >> >> <https://support.google.com/chrome/answer/95346> >> >> they show fedora-21[+] as supported. If I remember correctly, >> RHEL/CentOS-7 is based against fedora-19. > > Actually, in two places on