Brave can't open ubuntu.com page

[wooque]

Description

Brave can't open ubuntu.com page. I can see page flashing for a fraction of a second before I get "Can't open this page" error

Steps to Reproduce

1. Open ubuntu.com

Actual result:

Can't open this page error

Expected result:

Page opens normally

Reproduces how often:

Easily reproduced

Brave version (brave://version info)

Brave	1.50.121 Chromium: 112.0.5615.138 (Official Build) (64-bit)
Revision	2258f2fcaeb07bc95c992b7ca47f0b43ead9865c-refs/branch-heads/5615@{#1282}
OS	Linux

Version/Channel Information:

• Can you reproduce this issue with the current release? Yes
• Can you reproduce this issue with the beta channel? /
• Can you reproduce this issue with the nightly channel? /

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields? No
• Does the issue resolve itself when disabling Brave Rewards? No
• Is the issue reproducible on the latest version of Chrome? No

Miscellaneous Information:

[tocic]

After the upgrade to Version 1.50.121 Chromium: 112.0.5615.138 I'm getting the same message for GitHub and GitLab too. Ctrl+F5 helps. Downgrading to Version 1.50.119 Chromium: 112.0.5615.121 also helps.

[pitsi]

I just got this message when browsing a forum. Then I tested ubuntu.com and gitlab and it happens there as well. Thankfully it does not happen on github. Ctrl + f5 (= forced refresh without using the browser's cache) did not help at all here :(

---edit
Terminal output when ubuntu.com fails to open

$ brave-browser
[1859:1859:0420/084637.366145:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[1894:1894:0420/084637.487918:ERROR:gpu_memory_buffer_support_x11.cc(49)] dri3 extension not supported.
[1859:2012:0420/084638.077075:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1859:2012:0420/084638.077380:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1859:2012:0420/084638.077639:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1859:1876:0420/084638.282585:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018
[1859:1859:0420/084638.764500:ERROR:interface_endpoint_client.cc(695)] Message 0 rejected by interface blink.mojom.WidgetHost

Moreover, sometimes this sigill error comes up instead of the one on the forementioned screenshot

and dev tools (= one thing that would help troubleshooting) says "devtools was disconnected from the page. once page is reloaded, devtools will automatically reconnect".

Sigh... I will probably downgrade to 1.50.119 by afternoon or tomorrow, when I will be fed up with all those issues.

[kjozwiak]

Firstly, I would like to apologies to anyone who's experiencing the above issues and appreciate all the reports and information. It looks like 112.0.5615.138 is causing issues on Linux and we suspect it might be due to https://bugs.chromium.org/p/chromium/issues/detail?id=1434194. What usually happens is when we get a chromium bump as per https://chromereleases.googleblog.com/2023/04/stable-channel-update-for-desktop_18.html, we update all our branches and then push the release on the targeted platforms. So for 112.0.5615.138, both macOS & Windows were targeted. The update mentions that a Linux update will be coming soon. However, when we usually get bumps with zero-day vulnerabilities, we try to update all of our platforms ASAP. So we ended up pushing 112.0.5615.138 on Linux as well to help protect our users. However, in hindsight, we probably should have waited.

We're preparing a new update that will basically bump the version from 1.50.121 and revert users to 1.50.119 which was using 112.0.5615.121. We've received a bunch of confirmations spanning various threads on both reddit and GitHub that reverting to 112.0.5615.121 fixes the issues. We've also took a look at the difference between 112.0.5615.138 & 112.0.5615.121 and see nothing that would cause any issues when reverting. We should have an update available within ~2-3hrs. In the meantime, I would advice Linux users not to update to 112.0.5615.138 and wait for the next chromium bump.

We'll also update the various Brave communication channels including reddit and http://community.brave.com to let users know what happened and let them know that an update is on the way that should restore functionality back to normal.

Quick Update: Looks like 112.0.5615.165 has been pushed out on Linux at 100% as per https://chromiumdash.appspot.com/releases?platform=Linux. We're preparing builds with 112.0.5615.165 as we speak. We also have the build that reverts to 112.0.5615.121 running in case 112.0.5615.165 doesn't fix the issues. However, as it was pushed out to 100% of the Chrome user base, this should address the issue as well. Ether way, we'll hopefully have an update within a few hours.

[wooque]

@kjozwiak 112.0.5615.165 is already released for Linux, I don't know why they wrote it's coming, I just checked Chrome on my machine and it's on version 112.0.5615.165, There are no crashes there.

[kjozwiak]

@kjozwiak 112.0.5615.165 is already released for Linux, I don't know why they wrote it's coming, I just checked Chrome on my machine and it's on version 112.0.5615.165, There are no crashes there.

Thanks! Just noticed it via https://chromiumdash.appspot.com/releases?platform=Linux. We're preparing an update ASAP.

[wooque]

Version 1.50.125 Chromium: 112.0.5615.165 fixed the issue 👍

[kjozwiak]

Version 1.50.125 Chromium: 112.0.5615.165 fixed the issue 👍

awesome, thanks for the confirmation @wooque . Wanted to update the issue but you beat me it :) So we pushed out 1.50.125 Chromium: 112.0.5615.165 which should fix the issue for everyone. If you were having issues, please let us know if the above release fixed your issue. Can also download the deb files manually via https://github.com/brave/brave-browser/releases/tag/v1.50.125. Just for some context, the above was fixed by 112.0.5615.165.