brave-browser: windows not opening/pages not rendering when `--ozone-platform-hint=wayland`
Update: To fix run it with the following flag: --ozone-platform=wayland
Description
The Brave Nightly version on Arch Linux running Hyprland with AMD does not render anything.
The window opens and react to input (opening a new window opens it, but nothing renders)
Steps to Reproduce
- Run
brave-browser-nightly
Actual result:
❮ brave-browser-nightly
[46910:46910:0411/084925.135712:ERROR:chrome_browser_cloud_management_controller.cc(161)] Cloud management controller initialization aborted asCBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the officialGoogle Chrome build.
[46910:46910:0411/084925.156727:ERROR:content_settings_pref.cc(406)] Invalid pattern strings: https://w=149,h=149:443,*
[46910:46910:0411/084935.197642:ERROR:sharing_service.cc(221)] Device registration failed with fatal error
Expected result:
On Brave stable:
Reproduces how often:
No steps to reproduce
Brave version (brave://version info)
Brave | 1.66.74 Chromium: 124.0.6367.29 (Official Build) nightly (64-bit)
Revision | 43c41a798003efcabf0d292cb2a5efdcc633857b
OS | Linux
JavaScript | V8 12.4.254.8
User Agent | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
Command Line | /opt/brave.com/brave-nightly/brave --disable-domain-reliability --enable-dom-distiller --enable-distillability-service --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --sync-url=https://sync-v2.brave.com/v2 --lso-url=https://no-thanks.invalid --variations-server-url=https://variations.brave.com/seed --variations-insecure-server-url=https://variations.brave.com/seed --enable-features --disable-features --flag-switches-begin --ozone-platform-hint=auto --enable-features=OverlayScrollbar --flag-switches-end --component-updater=url-source=https://go-updater.brave.com/extensions --ozone-platform=wayland
Executable Path | /opt/brave.com/brave-nightly/brave
Profile Path | /home/vdawg/.config/BraveSoftware/Brave-Browser-Nightly/Default
Active Variations | AllowCertainClientHintsStudy:EnabledBraveAdblockExperimentalListDefaultStudy:EnabledBraveAdblockMobileNotificationsListDefault:EnabledBraveAdsNewTabPageAdsStudy:EnabledBraveAdsSiteVisitStudy:EnabledBraveAdsTextClassificationPageProbabilitiesStudy:EnabledBraveAggressiveModeRetirementExperiment:DisabledBraveAutoTranslateStudy:AutoTranslateDisabledBraveDebounceStudy:EnabledBraveForgetFirstPartyStorage:EnabledBraveGoogleSignInPermissionStudy:EnabledBraveHorizontalTabsUpdateEnabledStudy:EnabledBraveHttpsByDefaultRolloutStudy:EnabledBraveLocalhostAccessPermissionStudy:EnabledBraveP3AConstellationEnabled:EnabledBraveP3ATypicalJSONDeprecationEnabled:EnabledBraveRequestOTRTabRolloutStudy:EnabledBraveRewardsAllowSelfCustodyProvidersStudy:EnabledBraveRewardsWebUiPanelStudy:EnabledBraveScreenFingerprintingBlockerStudy:EnabledBraveSearchAdStudy:EnabledBraveWebViewRoundedCornersStudy:EnabledClampPlatformVersionClientHint:DisabledCookieListDefaultStudy:EnabledCosmeticFilteringChildFramesStudy:EnabledDefault1pBlockingStudy:DisabledDefaultBraveCommandsStudy:EnabledDefaultBraveOmniboxMoreHistoryStudy:EnabledDisableReduceLanguage:EnabledEphemeralStorageStudy:EnabledHangWatcher:DefaultPartitionedCookies:EnabledPrivateNetworkAccessKillswitch:Disabled_PrivateNetworkAccessKillSwitchUseWritePixelsYUV:Disabled_UseWritePixelsYUVUserActivityStudy:Triggers
Version/Channel Information:
- Can you reproduce this issue with the current release? No
- Can you reproduce this issue with the beta channel? I dont know
- Can you reproduce this issue with the nightly channel? Yes
Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? I dont know
- Does the issue resolve itself when disabling Brave Rewards? I dont know
- Is the issue reproducible on the latest version of Chrome? I dont know
Miscellaneous Information:
About this issue
- Original URL
- State: closed
- Created 3 months ago
- Reactions: 2
- Comments: 19 (3 by maintainers)
Closing as the above has been resolved via https://github.com/brave/brave-core/pull/23166 👍
Chromium has merged a fix which addresses the issue for me. Hopefully we can get that into a release soon.
This is a Chromium upstream issue: https://issues.chromium.org/issues/329678163
To fix this issue, the user must run Brave through the command line with
--ozone-platform=waylandflag, or edit the desktop file with the flag.A bit easier is just changing the 3 there to 0, but it started looking blurry and I don’t like this “workaround”.
I can confirm on
Brave Browser 124.1.65.114if the version numbers matter.Starred in hopes of them counting that as a 👍🏻 and prioritising.
Thanks, this actually works for me. I would just add that
--ozone-platform=waylandis a different flag from--ozone-platform-hint=waylandwhich alone won’t be enough as when I first read your comment, I thought they were the same.It’s not rendering anything on Brave stable now. Ozone set to Wayland.
Verified with
Reproduced the issue:
Verified fixed:
The above requires
1.65.116or higher for1.65.xverification 👍Note on switching back: I used the flags/experiments page to change this, which is unavailable if nothing is drawing. To fix it I edited
$HOME/.config/BraveSoftware/Brave-Browser-Nightly/Local Stateto remove the ozone hit string from the experiments array.If that’s too difficult, you can delete the whole profile directory. 😦
I can reproduce with 1.67.11 Chromium: 124.0.6367.29 (Official Build) nightly (64-bit) on Fedora 39 x86_64, gnome desktop with intel Xe graphics. It works fine with
ozone-platform-hintset to default, but I get nothing drawn at all with it set towayland. Ozone Platform in brave://gpu defaults tox11on my system.So switching back to x11 is likely a work around for problematic releases.
I have the same issue with chromium