Brave 1.81.166 doesn't launch under Ubuntu 24.04

[Anonymity]

Description of the issue:Today (September 10, 2025) Livepatch updated Brave to version 1.82.166. Since the update, the browser doesn’t launch. I click on it, the spinner spins for about 30 seconds, then disappears and the browser hasn’t launched. The same thing happened today on my wife’s machine, which also runs Ubuntu 24.04.

Steps to Reproduce (add as many as necessary): Click on the browser icon. Wait 30 seconds. Nothing happens.

Actual Result (gifs and screenshots are welcome!): No screenshots are possible: nothing happens.

Expected result: The browser launches itself.

Reproduces how often: Always.

Operating System and Brave Version(See the About Brave page in the main menu): OS: Ubuntu 24.04. Brave Version 1.82.166

Additional Information: None available.

[dhbarnett]

Same issue here. This is the output from my terminal:

$ brave
/usr/share/libdrm/amdgpu.ids: No such file or directory
/usr/share/libdrm/amdgpu.ids: No such file or directory
[49863:49863:0910/233424.690316:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:197] Failed to connect to Wayland display: No such file or directory (2)
[49863:49863:0910/233424.690340:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
[49863:49863:0910/233424.690401:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.

[FishOfTheNorthStar]

same here, terminal output is identical to dhbarnett’s

i’ve tried some different command line params and environmental variable suggestions the AI came up with but they aren’t having effect. I can get it to at least start and run in some sudo –no-sandbox mode that seems to startup as x11 despite my session being wayland, so it’s visually glitched and doesn’t actually display valid window contents. But maybe it can get a hotfix loaded when it comes down.

I’m running fedora 42

I confirmed the amdgpu.ids file does exist at that location, and doesn’t appear to have any confilcting permissions or ownership with my snapd brave installation

[banjjk]

I have this issue too. I’m not sure what Brave version I have, but I run Ubuntu 22.04 and after I restarted my computer today I found that Brave doesn’t work anymore.

[Benjo]

Exact same issue.

Ubuntu 24.04

Brave version: 1.82.166

[ismamai]

Same issue on ubuntu 24.04. Brave not running after update

[18064:18064:0911/080143.342823:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:197] Failed to connect to Wayland display: No such file or directory (2)
[18064:18064:0911/080143.342879:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
[18064:18064:0911/080143.342906:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.

[FishOfTheNorthStar]

For now I’ve resolved this by uninstalling the snapd install and reinstalling with flatpak. I wasn’t able to migrate my account settings, unfortunately, but it starts up and runs fine.

(note these steps will probably reset all your bookmarks and saved passwords)

sudo snap remove brave
flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
flatpak install flathub com.brave.Browser

[aflores]

The exactly same just happen to me. Is there a way to go back to a previous version?

[peter.robinson]

Under Ubuntu 25.04 same problem.

brave

[32324:32324:0911/104957.984203:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:197] Failed to connect to Wayland display: No such file or directory (2)
[32324:32324:0911/104957.984222:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
[32324:32324:0911/104957.984232:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.

---

sudo strace -u XXXXXXXX -e ‘%net’ -f -D -vv brave --enable-features=UseOzonePlatform -ozone-platform=wayland 2>&1 | grep “$XDG_RUNTIME_DIR”

[pid 31125] connect(6, {sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, 21) = 0

[pid 31125] getpeername(6, {sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, [112 => 21]) = 0

[pid 31125] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“l\2\1\1\v\0\0\0\1\0\0\0=\0\0\0”, iov_len=16}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 16

[pid 31125] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“\6\1s\0\6\0\0\0:1.255\0\0\5\1u\0\1\0\0\0\10\1g\0\1s\0\0”…, iov_len=64}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 64

[pid 31125] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“\6\0\0\0:1.255\0”, iov_len=11}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 11

[pid 31125] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“l\4\1\1\v\0\0\0\2\0\0\0\215\0\0\0”, iov_len=16}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 16

[pid 31125] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“\1\1o\0\25\0\0\0/org/freedesktop/DBus\0\0\0”…, iov_len=144}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 144

[pid 31125] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“\6\0\0\0:1.255\0”, iov_len=11}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 11

[pid 31125] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“l\2\1\1\0\0\0\0\3\0\0\0005\0\0\0”, iov_len=16}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 16

[pid 31125] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“\6\1s\0\6\0\0\0:1.255\0\0\5\1u\0\2\0\0\0\7\1s\0\24\0\0\0”…, iov_len=56}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 56

[pid 31126] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“l\2\1\1’\0\0\0\355B\0\0-\0\0\0”, iov_len=16}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 16

[pid 31126] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“\5\1u\0\3\0\0\0\6\1s\0\6\0\0\0:1.255\0\0\10\1g\0\1o\0\0”…, iov_len=48}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 48

[pid 31126] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“\”\0\0\0/org/freedesktop/systemd1/jo"…, iov_len=39}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 39

[pid 31130] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“l\4\1\1u\0\0\0\364B\0\0\215\0\0\0”, iov_len=16}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 16

[pid 31130] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“\1\1o\0\31\0\0\0/org/freedesktop/systemd”…, iov_len=144}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 144

[pid 31130] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“\220\r\0\0\”\0\0\0/org/freedesktop/systemd"…, iov_len=117}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 117

[pid 31130] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“l\2\1\1\0\0\0\0\4\0\0\0005\0\0\0”, iov_len=16}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 16

[pid 31130] recvmsg(6, {msg_name={sa_family=AF_UNIX, sun_path=“/run/user/1000/bus”}, msg_namelen=112 => 21, msg_iov=[{iov_base=“\6\1s\0\6\0\0\0:1.255\0\0\5\1u\0\4\0\0\0\7\1s\0\24\0\0\0”…, iov_len=56}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 56

[pid 31185] connect(33, {sa_family=AF_UNIX, sun_path=“/run/user/1000/snap.brave/wayland-0”}, 38) = -1 ENOENT (No such file or directory)

[Lefty]

+1

Is there a way to stop my backup machine (this one) updating to latest version which it says it’s going to do when I close this session.

[sigithar]

I tried several methods as workaround.

Reverting to older version
By default Canonical’s Ubuntu snap stores two latest version of snap package, this includes Brave browser.

snap list --all brave

I could revert to older version by using this line.

sudo snap revert brave

The older version works fine on my computer.

Running the latest version of Brave using X11

Since the problem is (probably) about compatibility issue of Brave (Snap package) on Wayland, I tried to run it using X11 from terminal console,

XDG_SESSION_TYPE=x11 brave

or you can just use X11 on Ubuntu in general, but it may interfere with another software.

I don’t know if these two methods will cause another problem or side effect.

It’s just temporary measure while waiting for the problem to get fixed.

[lubricado]

Same problem on both of my computers running Ubuntu after forced Brave update yesterday after session close. Information I can add is that the following six lines under (1) appear in stderr after a fresh reboot and attempt at launching Brave, (2) appears only on the computer with AMD Radeon (the other is Intel integrated), and (3) Wayland init fail is on both, same that others have reported. Thereafter, it’s only (2) + (3) or (3) respectively for each launch attempt, each computer.

(1)
update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0 0): cannot write to “/var/lib/snapd/hostfs/usr/local/share/doc” because it would affect the host in “/var/lib/snapd”

update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot write to “/var/lib/snapd/hostfs/usr/share/gimp/2.0/help” because it would affect the host in “/var/lib/snapd”

update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot write to “/var/lib/snapd/hostfs/usr/share/gtk-doc” because it would affect the host in “/var/lib/snapd”

update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot write to “/var/lib/snapd/hostfs/usr/share/libreoffice/help” because it would affect the host in “/var/lib/snapd”

update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme /usr/share/sphinx_rtd_theme none bind,ro 0 0): cannot write to “/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme” because it would affect the host in “/var/lib/snapd”

update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot write to “/var/lib/snapd/hostfs/usr/share/xubuntu-docs” because it would affect the host in “/var/lib/snapd”

(2)
/usr/share/libdrm/amdgpu.ids: No such file or directory

amdgpu: unknown (family_id, chip_external_rev): (150, 64)

/usr/share/libdrm/amdgpu.ids: No such file or directory

amdgpu: unknown (family_id, chip_external_rev): (150, 64)

(3)
[6371:6371:0910/151349.541805:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:197] Failed to connect to Wayland display: No such file or directory (2)

[6371:6371:0910/151349.542216:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform

[6371:6371:0910/151349.542294:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.

---

Ubuntu 25.04 (Wayland)
KDE Plasma 6.3.4
KDE Frameworks 6.12.0
Qt 6.8.3
Kernel 6.14.0-29-generic (64-bit)

Brave 1.82.166

I verified that /usr/share/libdrm/amdgpu.ids still exists.

[peter.robinson]

When I start from the command line:

$ brave

[20908:20908:0911/121252.761956:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:197] Failed to connect to Wayland display: No such file or directory (2)
[20908:20908:0911/121252.761978:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
[20908:20908:0911/121252.761992:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.

---

in the system log, I see lots of “apparmor“ messages.

[ 3205.362318] kauditd_printk_skb: 30 callbacks suppressed
[ 3205.362321] audit: type=1400 audit(1757587593.547:940): apparmor=“DENIED” operation=“mkdir” class=“file” profile=“snap.brave.brave” name=“/etc/opt/chrome/” pid=25029 comm=“brave” requested_mask=“c” denied_mask=“c” fsuid=1000 ouid=1000
[ 3205.391537] audit: type=1400 audit(1757587593.577:941): apparmor=“DENIED” operation=“mkdir” class=“file” profile=“snap.brave.brave” name=“/etc/opt/chrome/” pid=25040 comm=“brave” requested_mask=“c” denied_mask=“c” fsuid=1000 ouid=1000
[ 3205.391545] audit: type=1400 audit(1757587593.577:942): apparmor=“DENIED” operation=“mkdir” class=“file” profile=“snap.brave.brave” name=“/etc/opt/chrome/” pid=25039 comm=“brave” requested_mask=“c” denied_mask=“c” fsuid=1000 ouid=1000
[ 3205.391655] audit: type=1326 audit(1757587593.577:943): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.brave.brave pid=25039 comm=“brave” exe=“/snap/brave/541/opt/brave.com/brave/brave” sig=0 arch=c000003e syscall=330 compat=0 ip=0x756f7c1eef6b code=0x50000
[ 3205.391659] audit: type=1326 audit(1757587593.577:944): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.brave.brave pid=25040 comm=“brave” exe=“/snap/brave/541/opt/brave.com/brave/brave” sig=0 arch=c000003e syscall=330 compat=0 ip=0x7d938d06bf6b code=0x50000
[ 3205.393864] audit: type=1326 audit(1757587593.579:945): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.brave.brave pid=25029 comm=“brave” exe=“/snap/brave/541/opt/brave.com/brave/brave” sig=0 arch=c000003e syscall=444 compat=0 ip=0x71083570388d code=0x50000

---

So I took the command out of the syslog

• snap/brave/541/opt/brave.com/brave/brave

When I call start the program with this command it works fine.

/snap/brave/541/opt/brave.com/brave/brave
MESA-INTEL: warning: Haswell Vulkan support is incomplete

---

in the system log, I get this

3313.634168] audit: type=1400 audit(1757587701.819:947): apparmor=“AUDIT” operation=“userns_create” class=“namespace” info=“Userns create - transitioning profile” profile=“unconfined” pid=25107 comm=“brave” requested=“userns_create” target=“unprivileged_userns”
[ 3313.634747] audit: type=1400 audit(1757587701.820:948): apparmor=“DENIED” operation=“capable” class=“cap” profile=“unprivileged_userns” pid=25116 comm=“brave” capability=21 capname=“sys_admin”
[ 3313.938312] nouveau 0000:01:00.0: Direct firmware load for nouveau/nve4_fuc084 failed with error -2
[ 3313.938341] nouveau 0000:01:00.0: Direct firmware load for nouveau/nve4_fuc084d failed with error -2
[ 3313.938344] nouveau 0000:01:00.0: msvld: unable to load firmware data
[ 3313.938348] nouveau 0000:01:00.0: msvld: init failed, -19

---

It’s a brand new install of Ubuntu 25.04 (Installed Monday)

[prhasn]

Same issue. Truly unfortunate.

[peter.robinson]

I’m experiencing multiple issues too.

SNAP/Aparmor (bad config?)

My nVidia card (GeForce GTX 760) is older than the hills, Ubuntu stopped supporting the driver. So, I’m in the process of figuring out which compatible one I can find afford without having to sell my eldest to pay for it.

With the GeForce GTX 760 I was able to render videos quickly using accelerated hardware.

---

So, Ubuntu 25.04 is using the “nouveau” driver apparently. According to syslog, this has problems too…

[ 1015.681061] nouveau 0000:01:00.0: msvld: unable to load firmware data
[ 1015.681064] nouveau 0000:01:00.0: msvld: init failed, -19
…
brave[20400]] subc 7 mthd 0000 data 0000906e
[ 1117.483161] nouveau 0000:01:00.0: fifo: fault 00 [READ] at 0000000000000000 engine 00 [GR] client 04 [HUB/FE] reason 02 [PTE] on channel 4 [007f8e0000 brave[20400]]
[ 1117.483166] nouveau 0000:01:00.0: fifo:000000:0004:[brave[20400]] rc scheduled
[ 1117.483168] nouveau 0000:01:00.0: fifo:000000: rc scheduled
[ 1117.483179] nouveau 0000:01:00.0: fifo:000000:0004:0004:[brave[20400]] errored - disabling channel

---

I’ve been using LTS for 10 years. I got too comfortable I guess.

Now I have no more ffmpeg acceleration. I’m going to buy a new machine.

This i7-4770K CPU @ 3.50GHz works brilliantly - I built it about 10 years ago - but SNAP slows down launching anything. So, I’ll probably look for an i9 to replace it. Be cheaper buying a bundle with a good GPU. Pre-built.

This desktop will become a docker virtualization server (i.e. gathering dust in the corner).

[encodeur]

Yes, same issue for me, on ubuntu 24.04

$ brave
[5954:5954:0911/104924.222212:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:197] Failed to connect to Wayland display: No such file or directory (2)
[5954:5954:0911/104924.222278:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
[5954:5954:0911/104924.222323:ERROR:ui/aura/env.cc:257] The platform failed to initialize.  Exiting.

[steeven]

Thank you for reaching out to Brave Support. This is a known issue and we’re working to resolve. Some short-term workarounds can be found below.

https://github.com/brave/brave-browser/issues/49160

If you’re running the snap version, we’ve noticed it does work if you launch via:

snap run brave --ozone-platform=x11

[prhasn]

Thanks. The issue is now resolved.

[Anonymity]

Thank you very much!

[peter.robinson]

@steeven

`` snap run brave --ozone-platform=x11

This works. Thank you so much for your kind time and effort.