Tag Archives: chrome

Are You a Fan of Google Chrome’s New Look?

Perhaps it’s just me, but I don’t think the look of Google Chrome has altered all that much since it blinked into life in 2009. But that will shortly change. Rumour has it that Google plans to debut a new-look Google Chrome ahead of the browser’s 10th birthday in September. And if you’re a spoiler […]

This post, Are You a Fan of Google Chrome’s New Look?, was written by Joey Sneddon and first appeared on OMG! Ubuntu!.

Read More

Chrome Could Start Using Native Notifications on Linux

google chrome may soon use native linux notificationsGoogle Chrome could soon use native notifications on Linux desktops. A bug report asking for the browser to use a Linux desktop environment’s notification system was filed late last year but recently become active again. Google Chrome (and Chromium) currently use the Chrome Notification API to show alerts from websites, extensions and Chrome Apps on Windows, macOS and Linux. While these […]

This post, Chrome Could Start Using Native Notifications on Linux, was written by Joey Sneddon and first appeared on OMG! Ubuntu!.

Read More

How To Fix The (Annoying) ‘Failed to Fetch’ Chrome apt Error

chrome drops 32bit linux supportGoogle announced plans to discontinue 32-bit Google Chrome for Linux this March, and, bang on cue, it has.

The search engine has pulled 32-bit Chrome builds from the official Chrome repo, which gets added to Ubuntu Software Sources when the app is first installed.

Some 64-bit Ubuntu systems caught in the cross-hairs of the deprecation are now throwing a small, yet very annoying, error when performing an apt update.

The ‘failed to fetch error that appears in the Terminal says:

“Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release Unable to find expected entry ‘main/binary-i386/Packages’ in Release file (Wrong sources.list entry or malformed file)”

Alternatively you may see:

Skipping acquire of configured file ‘main/binary-i386/Packages’ as repository ‘http://dl.google.com/linux/chrome/deb stable InRelease’ doesn’t support architecture ‘i386’

If you do see one of these two errors do not panic. It is easy to fix the ‘failed to fetch’ error and the ‘skipping acquire’ issue. All it requires is 30 seconds and a few simple characters…

‘The fix takes just 30 seconds to perform, then no-more annoying error.’

Fix ‘Failed To Fetch’ Apt Error on Ubuntu

The tip comes to us by way of OMG! Ubuntu! reader Santiago Batista, who explains the situation in his e-mail to us:

“Since Google dropped support for 32-bit Chrome on Linux an error occurs when updating apt in 64-bit systems (with multi arch enabled).

“The solution,” he says, ”is to modify the sources.list file for Chrome.”

But how do you do that?

We can edit the sources.list in a number of different ways. Some of these take place at the command line, others through a GUI.

You may have your own preferred method, but for this walkthrough I will use Gedit.

1. Open a new Terminal window and run the following command (assuming you’re on the Stable Channel, if not, see the featured comment):

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

2. In the text file that opens edit the file so that the line reads:

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

The only addition you need to make is entering the [amd64] architecture after ‘deb’ but preceding the ‘http’. Do not edit or replace any other text in this file.

3. Hit Save. Close the Gedit window.

Now return to the Terminal and refresh your package list by running:

sudo apt-get update

The ‘failed to fetch’ APT error should no longer appear.

This post, How To Fix The (Annoying) ‘Failed to Fetch’ Chrome apt Error, was written by Joey-Elijah Sneddon and first appeared on OMG! Ubuntu!.

Read More

Google Chrome Axes Support for ALL 32-bit Linux Distros

chrome drops linux 32 support

Support for Ubuntu 12.04 LTS is Also Being Retired

Google Chrome is to drop support for all 32-bit Linux distros from March, 2016. 

The change, which brings the platform in line with that of Mac OS X, will apply to all x86 Linux builds, regardless of distribution or version number.

Users affected will still be able to use Chrome after the axe has fallen, but they will no longer receive any updates.

In a double-whammy, March will also see Google Chrome stop supporting Ubuntu 12.04 LTS (which will receive critical and security bug fixes from Canonical until mid 2017).

‘Ubuntu users  are advised to upgrade to a 64-bit version of Ubuntu 14.04 LTS or later’

From this March only 64-bit versions of Ubuntu 14.04 LTS (or later) will receive new versions of the browser from Google .

To run a supported version of Google Chrome Precise users are advised to upgrade to a 64-bit version of Ubuntu 14.04 LTS (or later).

Why Is Google Dropping Support?

The small Google Chrome Linux team can’t support all versions of Ubuntu and other Linux distributions indefinitely. With Linux already a small overall percentile of Chrome’s user base, and 32-bit users amongst that percentage even smaller, something had to give at some point.

The build infrastructure used to package Google Chrome is tasked with making hundreds of binaries each day, and human effort is required to test those binaries for release.

“To provide the best experience for the most-used Linux versions, we will end support for Google Chrome on 32-bit Linux, Ubuntu Precise (12.04), and Debian 7 (wheezy) in early March, 2016,” says Chromium engineer Dirk Pranke.

32-bit ChromiumIs Not Affected

‘Chromium is unaffected by the change. ‘

Many Linux users run Chromium, the open-source basis of Chrome, and so won’t be affected by this change. Google Chrome and Chrome OS builds for 32-bit ARM are similarly unaffected.

For browsers built on Chromium, like Opera, it will be up to them as to whether they continue to offer builds for 32-bit users.

Google says it will ‘keep support for 32-bit build configurations on Linux to support building Chromium’, which  we’re told it will do so for ‘some time to come’.

Do you use Google Chrome on a 32-bit version of Linux? Will you switch to another browser? Perhaps you think this decision is logical. Whatever your view on this decision you can share it in the comments below. 

This post, Google Chrome Axes Support for ALL 32-bit Linux Distros, was written by Joey-Elijah Sneddon and first appeared on OMG! Ubuntu!.

Read More

Happy New Year & Browser and OS stats for 2014

I’d like to wish everyone a happy new year on behalf of the entire LQ team. 2014 has been another great year for LQ and we have quite a few exciting developments in store for 2015, including a major code update that we originally had planned for 2013. A few highlights: LQ ISO recently surpassed 55,000,000 Linux downloads. AndroidQuestions.org and ChromeOSQuestions.org continue to grow. Outside The Questions Network, I think we’ve really hit our stride on Bad Voltage.

As has become tradition, here are the browser and OS statistics for the main LQ site for all of 2014 (2013 stats for comparison).

Chrome 45.34%
Firefox 39.00%
Internet Explorer 8.12%
Safari 4.57%
Opera 1.29%
Android Browser 0.56%

A big change here, as Chrome has finally supplanted Firefox as the most used browser at LQ (and has done so quite handily).

Operating Systems
Windows 52.58%
Linux 32.32%
Macintosh 10.62%
Android 2.42%
iOS 1.44%

Linux usage has remained fairly steady, while OS X usage is now over 10% for the first time ever.

I’d also like to take this time to thank each and every LQ member. You are what make the site great; without you, we simply wouldn’t exist. I’d like to once again thank the LQ mod team, whose continued dedication ensures that things run as smoothly as they do. Don’t forget to vote in the 2014 LinuxQuestions.org Members Choice Awards, which recently opened.


Read More