jdefed
October 7, 2025, 3:25pm
1
Troubleshooting technical issues is much easier when both the user and support agent practice clear communication. For this reason, we have provided the template below for you to fill out with information about your issue. Please provide as much detail as possible so we can most efficiently resolve your problem.
Delete the any text above the line separator below before posting
Description of the issue:
How can this issue be reproduced?
just open the browser
the mouse and all keystroke freeze, have to restate pc
if i force version 1.81.137 the above is not an issue. works as it should
Expected result:pc locks up
Brave Version( check About Brave):1.83.109 locks up pc, pc runs correctly on version 1.81.137
Additional Information:firefox works without issues, it seems to want to change text size before it locks
If you launch the browser with --disable-features=WaylandWpColorManagerV1 do you see an improved experience?
1 Like
jdefed
October 7, 2025, 6:33pm
3
Hi, I am using wayland as the windowing system in ubuntu. Not sure how to disable the line you said. Do you disable it in ubuntu before launching brave or when brave browser opens. I would not have time to do it in the browser as the mouse pointer stops working immediately.
jdefed
October 7, 2025, 6:34pm
4
Do I type that in terminal then ok then it will launch brave?
jdefed
October 7, 2025, 6:59pm
5
Tried running command in terminal, said command not found
Ah, are you using the full command?
brave-browser --disable-features=WaylandWpColorManagerV1
jdefed
October 8, 2025, 12:29pm
7
I wasnt using “brave browser” in the command. I will have to update brave and then try it later today. Ill let you know
thanks
jdefed
October 9, 2025, 1:15pm
8
Hi, did some experimenting today. The problem is actually from ver. 1.83.137 to 1.83.166. I tried ver. 112 which came out today. The page loaded further in its process but still locked up. I could see the whole page layout and it either changed page resolution or made the text smaller. One thing of note is in ubuntu settings under accessibility I have large text on.
Thanks
jim
Did you attempt with the above command?
Do you see the issue with Accessibility settings set to Default?
Thanks!
jdefed
October 9, 2025, 1:45pm
10
The above command does not work, I have not tried yet with accessibility off yet
jdefed
October 9, 2025, 2:17pm
11
Turned accessibility setting to default, no difference. Above command does not work. Most of the time it locks up at the keyring page.
jim
jdefed
October 18, 2025, 1:48pm
12
Hi
Just tried version 118 of brave and it still locks up the pc. When I reboot the pc, ubuntu goes through a recovery mode where its doing something with inodes which I dont understand.
jdefed
October 23, 2025, 1:30pm
13
I just reinstalled brave browser using ver.1.83.120, same result. Whole pc locks up, I have to restart it. Everything works until I launch brave, most times I get paste the keyring then immediately locks up. I reverted back to 1.81.137 using synaptic package manager and everything works as it should. I have another pc running brave with the same ver. of ubuntu, but has different hardware and that one runs ver 1.83.118 without any problems. Any help here?
Evan123
October 23, 2025, 3:28pm
14
This could be related to the open issue below.
opened 03:39AM - 06 Oct 25 UTC
crash
release/blocking
OS/Linux
Chromium/waiting upstream
gpu/driver
OS/Desktop
Chromium/reported upstream
### Description
After a recent update, Brave has become unusable in a native Wa… yland session on my multi-monitor setup. The browser launches, but it immediately crashes with a "trace trap (core dumped)" error when I try to drag the window from one monitor to another. This issue seems identical to what is described in #49862.
Previously, I had a perfectly stable experience by using the "Preferred Ozone platform" flag in brave://flags, setting it to "Wayland". This method for enabling native Wayland support has been discussed in issues like #25074. Since the update, this flag has been removed.
Crucially, the problem is not just the missing flag. Even when trying to force the Wayland backend via the command line with 'brave --ozone-platform=wayland', the browser still crashes when moved between monitors. The only stable ways to use the browser are either by launching it from the terminal with '--ozone-platform=x11', or by manually creating a configuration file at '~/.config/brave-flags.conf' to force the flags on every launch.
Although workarounds exist (using command-line flags or a configuration file), I believe it's important to file this report because it represents a significant regression in user experience for Linux users on Wayland. Therefore, I am requesting a fix for the native Wayland mode so it doesn't crash in a multi-monitor environment, and ideally the restoration of a user-friendly, persistent setting like the "Preferred Ozone platform" flag.
### Steps to reproduce
1. Use a Linux system with a Wayland session and at least two monitors.
2. Launch Brave in its default Wayland mode (e.g., from the application menu or by running 'brave').
3. Drag the Brave window from one monitor to the other. The browser will crash.
4. Relaunch Brave from the terminal with the command: 'brave -enable-features=UseOzonePlatform -ozone-platform=wayland
5. Drag the Brave window from one monitor to the other again. The browser will crash again.
### Actual result
The browser crashes whenever its window is moved between monitors under a native Wayland session (both default and when forced with --ozone-platform=wayland). The only stable way to run the browser is by forcing it into XWayland compatibility mode via configuration.
### Expected result
The browser should run stably in a native Wayland session and allow its window to be moved between monitors without crashing. This functionality worked correctly in previous versions when the native Wayland mode was enabled via brave://flags.
### Reproduces how often
Easily reproduced
### Brave version (brave://version info)
Brave 1.83.109 Chromium: 141.0.7390.55 (Official Build) (64-bit)
Revision 6c9b7bdded46e59d445cb0c067bff9f3bcd8fdd0
OS Linux
JavaScript V8 14.1.146.11
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36
Command Line /opt/brave-bin/brave --enable-features=UseOzonePlatform --ozone-platform=wayland --disable-domain-reliability --enable-dom-distiller --enable-distillability-service --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --lso-url=https://no-thanks.invalid --variations-server-url=https://variations.brave.com/seed --variations-insecure-server-url=https://variations.brave.com/seed --flag-switches-begin --flag-switches-end --component-updater=url-source=https://go-updater.brave.com/extensions --render-node-override=/dev/dri/renderD128
Executable Path /opt/brave-bin/brave
Profile Path /home/gustavos/.config/BraveSoftware/Brave-Browser/Default
Variations Seed Type Null
Command-line Variations eyJkaXNhYmxlLWZlYXR1cmVzIjoiRXllRHJvcHBlciIsImVuYWJsZS1mZWF0...
Active Variations SeedFileTrial:Default
### Channel information
- [x] release (stable)
- [ ] beta
- [ ] nightly
### Reproducibility
- [x] with Brave Shields disabled
- [x] with Brave Rewards disabled
- [ ] in the latest version of Chrome
### Miscellaneous information
My goal is to run Brave in its native Wayland mode to take advantage of features like fractional scaling and better touchpad gestures. However, this is currently not possible due to the crash on multi-monitor setups. The only stable option is to fall back to XWayland, which unfortunately means losing these Wayland-specific benefits.
#### Workaround (Persistent Configuration)
For users who do not want to launch Brave from the terminal every time, a persistent workaround is to create or edit the file ~/.config/brave-flags.conf.
To force the stable X11 backend, add the following lines to the file:
```
--enable-features=UseOzonePlatform
--ozone-platform=x11
```
#### Terminal Logs
#### With wayland (not works)
```
~/.config/hypr ❯ brave -enable-features=UseOzonePlatform -ozone-platform=wayland 00:32
(brave:72649): Gtk-WARNING **: 00:32:51.336: Theme parsing error: gtk.css:6691:68: Invalid name of pseudo-class
[72649:72649:1006/003251.602915:ERROR:chrome/browser/ui/views/user_education/impl/browser_user_education_interface_impl.cc:154] Attempting to show IPH IPH_DiscardRing before browser initialization complete; IPH will not be shown.
[72649:72649:1006/003251.630195:ERROR:ui/ozone/platform/wayland/host/wayland_wp_image_description.cc:219] Incomplete image description info from compositor.
[72649:72649:1006/003251.630244:ERROR:ui/ozone/platform/wayland/host/wayland_wp_image_description.cc:219] Incomplete image description info from compositor.
[72649:72649:1006/003251.887210:ERROR:components/sharing_message/sharing_service.cc:297] Device registration failed with fatal error
[72649:72649:1006/003252.073301:ERROR:ui/ozone/platform/wayland/host/wayland_wp_image_description.cc:219] Incomplete image description info from compositor.
[72649:72649:1006/003252.073337:ERROR:ui/ozone/platform/wayland/host/wayland_wp_image_description.cc:219] Incomplete image description info from compositor.
[72649:72649:1006/003252.889586:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland: wl_display#1: error 0: invalid object 75
[1006/003252.898002:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[1006/003252.898891:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[1] 72649 trace trap (core dumped) brave -enable-features=UseOzonePlatform -ozone-platform=wayland
```
#### With x11 (works)
```
~/.config/hypr ❯ brave -enable-features=UseOzonePlatform -ozone-platform=x11 00:32
(brave:73200): Gtk-WARNING **: 00:32:57.315: Theme parsing error: gtk.css:6691:68: Invalid name of pseudo-class
[73200:73200:1006/003257.582332:ERROR:chrome/browser/ui/views/user_education/impl/browser_user_education_interface_impl.cc:154] Attempting to show IPH IPH_DiscardRing before browser initialization complete; IPH will not be shown.
[73200:73200:1006/003257.890896:ERROR:components/sharing_message/sharing_service.cc:297] Device registration failed with fatal error
[73200:73200:1006/003429.262972:ERROR:ui/gfx/x/atom_cache.cc:232] Add chromium/from-privileged to kAtomsToCache
```
Current work-around is to start the browser with --disable-features=WaylandWpColorManagerV1 (avoids having to use --disable-gpu)
Thanks!
jdefed
October 24, 2025, 3:33pm
15
I disabled hardware acceleration and now it will work on 1.83.120. Will this be fixed in the future?
jdefed
October 24, 2025, 3:46pm
16
I have 2 pcs with different hardware but the same software ubuntu 22.04 lts. One will run brave with hardware acceleration on and one needs acceleration off.
jdefed
October 31, 2025, 3:35pm
17
Updated to 1.84.132, still cannot run my desktop ubuntu pc with hardware acceleration on. It completely locks up ubuntu, have to restart the computer.