Google Reverses Decision to Drop Chrome 128 Support for Ubuntu 18.04 LTS After Community Backlash

Google Reverses Decision to Drop Chrome 128 Support for Ubuntu 18.04 LTS After Community Backlash

Google Chrome version 128, which was released on Wednesday, initially did not function properly on Ubuntu Linux 18.04 LTS "Bionic Beaver" without user intervention. Google's initial stance was not to address the issue, leaving many users in a difficult situation.

Google Reverses Decision to Drop Chrome 128 Support for Ubuntu 18.04 LTS After Community Backlash
Google Reverses Decision to Drop Chrome 128 Support for Ubuntu 18.04 LTS After Community Backlash
Image credit: Ubuntu 

Community Concerns Prompt Google to Reverse Course

Following complaints from the community and inquiries from The Register, Google decided to change its plans. A Google spokesperson stated, "We recognize we caught some in the ecosystem off guard by this, and have decided to reverse the change and maintain support for Ubuntu 18.04. We will publish a build that restores compatibility next week. We do plan to drop support for 18.04 in the future, but will be sure to provide additional notice ahead of any changes."


The Initial Problem: Chrome 128 Breaks on Ubuntu 18.04

The issue with Chrome 128 was first highlighted by technology and policy advocate Lauren Weinstein in a post on Mastodon. He noted that Chrome Stable 128 would not update via apt on Ubuntu 18.04 due to the libgcc-s1 system shared library being less than version 4.2. Although standard support for Ubuntu 18.04 ended on May 31, 2023, long-term support (LTS) is available until 2028, which should have ensured compatibility.


Google's Original Response: No Fix Planned

Initially, Google intended to obsolete Chrome on Ubuntu 18.04, as indicated by a post on the Chromium bug tracker that referenced Weinstein's concerns. The post stated, "Yes, this is intentional," and explained that maintaining support for such an old system limited their ability to use newer features unavailable on those systems. Consequently, the bug report was marked as "Won't Fix."


The Risks of Workarounds: User Concerns

Weinstein pointed out that while there are workarounds available, tampering with system libraries could risk rendering the system unbootable. He also criticized Google's approach, highlighting that Google's own actions, such as continuing to update Chrome for Windows 7 long after its end-of-life (EOL), contradicted the argument that Chrome should die when the OS goes EOL. He emphasized that not being able to update Chrome presents serious security concerns.


Google's Final Decision: Compatibility Will Be Restored

Due to the outcry from users and the risks involved, Google has committed to releasing a build that will restore compatibility with Ubuntu 18.04 next week. This reversal provides some relief to users relying on the extended support for Ubuntu 18.04. However, Google has clarified that support for this older OS will eventually be phased out, but with proper notice to avoid such abrupt disruptions in the future.


Temporary Solutions: A Risky Fix

For users who cannot wait for Google's official fix, Weinstein has offered a workaround to update Chrome 127 to 128. However, he cautions that this solution comes with no guarantees, and users should proceed at their own risk.

This situation highlights the challenges of maintaining compatibility for older operating systems while continuing to innovate and integrate new features in software development. Google's decision to temporarily maintain support for Ubuntu 18.04 reflects the importance of user feedback in shaping product support policies.

Post a Comment

0 Comments