general/other Linuxulator and Chromium-based browsers at the end of 2026

After updating Vivaldi from vivaldi-stable_8.2.4133.96-1 to vivaldi-stable_8.3.4191.30-1 within an Ubuntu 20.04 LTS environment on a FreeBSD 15.1 (AMD64) host, the browser failed to launch, producing the following errors:

$ /compat/ubuntu/bin/vivaldi[
1106/185141.688277:ERROR:chromium/third_party/crashpad/crashpad/util/linux/ptracer.cc:46] ptrace: Invalid argument (22)
[1106/185141.688392:WARNING:chromium/third_party/crashpad/crashpad/snapshot/linux/process_reader_linux.cc:400] Couldn't initialize main thread. [1106/185141.688492:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[1106/185141.688548:WARNING:chromium/third_party/crashpad/crashpad/snapshot/linux/exception_snapshot_linux.cc:391] thread ID 33734 not found in process
[1106/185141.688615:ERROR:chromium/third_party/crashpad/crashpad/snapshot/linux/process_snapshot_linux.cc:129] thread not found 33734
[1106/185141.689053:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[1106/185141.783628:ERROR:chromium/third_party/crashpad/crashpad/util/linux/ptracer.cc:46] ptrace: Invalid argument (22)
[1106/185141.783668:WARNING:chromium/third_party/crashpad/crashpad/snapshot/linux/process_reader_linux.cc:400] Couldn't initialize main thread.
[1106/185141.783764:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[1106/185141.783784:WARNING:chromium/third_party/crashpad/crashpad/snapshot/linux/exception_snapshot_linux.cc:391] thread ID 33735 not found in process
[1106/185141.783835:ERROR:chromium/third_party/crashpad/crashpad/snapshot/linux/process_snapshot_linux.cc:129] thread not found 33735
[1106/185141.784148:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[1106/185142.333461:ERROR:chromium/third_party/crashpad/crashpad/util/linux/ptracer.cc:46] ptrace: Invalid argument (22)
[1106/185142.333519:WARNING:chromium/third_party/crashpad/crashpad/snapshot/linux/process_reader_linux.cc:400] Couldn't initialize main thread.
[1106/185142.333599:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[1106/185142.333626:WARNING:chromium/third_party/crashpad/crashpad/snapshot/linux/exception_snapshot_linux.cc:391] thread ID 33738 not found in process
[1106/185142.333685:ERROR:chromium/third_party/crashpad/crashpad/snapshot/linux/process_snapshot_linux.cc:129] thread not found 33738
[1106/185142.334197:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[1106/185142.379488:ERROR:chromium/third_party/crashpad/crashpad/util/linux/ptracer.cc:46] ptrace: Invalid argument (22)
[1106/185142.379517:WARNING:chromium/third_party/crashpad/crashpad/snapshot/linux/process_reader_linux.cc:400] Couldn't initialize main thread.
[1106/185142.379578:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[1106/185142.379594:WARNING:chromium/third_party/crashpad/crashpad/snapshot/linux/exception_snapshot_linux.cc:391] thread ID 33721 not found in process
[1106/185142.379714:ERROR:chromium/third_party/crashpad/crashpad/snapshot/linux/process_snapshot_linux.cc:129] thread not found 33721
[1106/185142.380052:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
/compat/ubuntu/bin/vivaldi: line 45: 33721 Trace/breakpoint trap "$HERE/vivaldi" --no-sandbox --test-type --v=0 "$@"

Gemini suggests that this is related to recent changes in Chromium. Could you tell me when a patch for Linuxulator might be expected? Vivaldi is my favorite and primary browser, and it would be a shame if it were stuck on an older version.
 
It looks like a crash handler is crashing? Would be silly to block the browser on that, but I'd try --disable-breakpad or some way of disabling crashpad
 
bonta linuxlator runs on top of rocky linux 9.x by default, what is the behaviour of vivaldi running on that?
Rocky Linux is a bad option for me because I don't like DNF, and besides, it doesn't support my processor (have not x86-64-v2 instructions).

p.s. By the way, the absence of these instructions isn't a problem, since the latest version of Vivaldi runs perfectly fine in VirtualBox. However, it’s not optimal way in VirtualBox, so I’d prefer to use the Linuxulator—previous versions of Vivaldi worked there exactly the same way as the native FreeBSD version of Chromium (including hardware-accelerated 3D and 2D graphics in the browser).

It looks like a crash handler is crashing? Would be silly to block the browser on that, but I'd try --disable-breakpad or some way of disabling crashpad
I tried these options --disable-breakpad --disable-crash-reporter but it didn't help; it still crashes with the same messages.
 
I think this is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289285 Those are fixed in 16-CURRENT and were backported to 15-STABLE.

I also think running a Linux browser on FreeBSD is dangerous because the seccomp sandbox isn't implemented in the Linuxulator.
I’m still a newcomer to desktop FreeBSD (I installed it and started using it as my primary operating system about a year ago). Could you tell me when a backport from STABLE to 15.*-RELEASE might be available?

Also, a second question: does the native build of Chromium use native sandboxing?

I realize it might not be as secure as it could be, but I really like Vivaldi, and since I generally only visit a specific list of sites that I trust, I’m willing to take the risk for now. I’ve written to the Vivaldi team several times asking for native FreeBSD support, but they’ve ignored my emails.
 
I’m still a newcomer to desktop FreeBSD (I installed it and started using it as my primary operating system about a year ago). Could you tell me when a backport from STABLE to 15.*-RELEASE might be available?
With 15.2 going to be released soon.

Also, a second question: does the native build of Chromium use native sandboxing?
Yes.

I realize it might not be as secure as it could be, but I really like Vivaldi, and since I generally only visit a specific list of sites that I trust, I’m willing to take the risk for now. I’ve written to the Vivaldi team several times asking for native FreeBSD support, but they’ve ignored my emails.

I also like Vivaldi because it lets me set the titles for tabs and it's a mild productivity boost for me. But as soon as stock Google Chrome gets this feature, I'll switch. I'm trying not to marry any Chromium-based browser after ditching Brave because they didn't pick up security updates the same day.
 
I think this is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289285 Those are fixed in 16-CURRENT and were backported to 15-STABLE.

I also think running a Linux browser on FreeBSD is dangerous because the seccomp sandbox isn't implemented in the Linuxulator.

No browser on FreeBSD, Linux version or native version, does any sandboxing for security.

The closest we have is stuffing Firefox into Capsicum. But work stalled and is challenging.
 
No browser on FreeBSD, Linux version or native version, does any sandboxing for security.

The closest we have is stuffing Firefox into Capsicum. But work stalled and is challenging.
I checked and you're right. The only sandboxing is for OpenBSD. The real sandboxing is done on OpenBSD with pledge & unveil.

At least FreeBSD is not a Swiss cheese like Linux with hundreds of systems calls available, and unprivileged user namespaces enabled by default.
 
With 15.2 going to be released soon.
Heh, version 15.2 looks a bit daunting for my system, since it includes an update to Plasma 6.8—which has dropped support for X11. I’m using an old Nvidia card, and I’m not ready to give up X11.

Maybe running `pkg lock plasma6-plasma-desktop` before upgrading to 15.2 will help.

I’ve also heard talk about plans to bring the Sonic DE to FreeBSD; I really hope that port actually shows up.
 
Doesn't look like that 15.2 Beta 1 nor 16 Current fixed this problem with Vivaldi 8.3. Vivaldi 8.2 based on Chromium 152 works OK.
 
and were backported to 15-STABLE.
I tried it in 15-Stable, but it still won't launch—though the errors look slightly different now.

# freebsd-version -kru ; sysctl kern.version
15.2-BETA1
15.2-STABLE
15.2-BETA1
kern.version: FreeBSD 15.2-STABLE stable/15-3c6c65bbb258 GENERIC

root@FreeBSD-15:/ # ^D
Zella@FreeBSD-15:/ $ /compat/ubuntu/bin/vivaldi
[1758:100589:1110/104759.814050:ERROR:chromium/device/udev_linux/udev_watcher.cc:51] Failed to initialize a udev monitor.
[1110/104759.876361:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /proc/1769/task/1769/comm: No such file or directory (2)
[1110/104759.876897:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[1110/104759.882573:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[1110/104759.882668:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
[1110/104800.578184:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /proc/1770/task/1770/comm: No such file or directory (2)
[1110/104800.578322:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[1110/104800.578605:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[1110/104800.578652:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
[1758:1758:1110/104800.848999:ERROR:chromium/dbus/object_proxy.cc:572] Failed to call method: org.freedesktop.DBus.Properties.GetAll: object_path= /org/freedesktop/UPower/devices/DisplayDevice: unknown error type:
[1110/104801.509028:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /proc/1773/task/1773/comm: No such file or directory (2)
[1110/104801.509122:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[1110/104801.509436:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[1110/104801.509497:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
[1110/104801.919737:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /proc/1758/task/1758/comm: No such file or directory (2)
[1110/104801.919990:ERROR:chromium/third_party/crashpad/crashpad/util/linux/proc_task_reader.cc:47] format error
[1110/104801.920558:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[1110/104801.920610:ERROR:chromium/third_party/crashpad/crashpad/util/file/file_io_posix.cc:145] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
/compat/ubuntu/bin/vivaldi: line 45: 1758 Trace/breakpoint trap "$HERE/vivaldi" --no-sandbox --test-type --v=0 "$@"

If run it directly rather than via a script, the message "/compat/ubuntu/bin/vivaldi: line 45: 1758 Trace/breakpoint trap" will appear as "Trace/BPT trap" instead.
 
I tried it in 15-Stable, but it still won't launch—though the errors look slightly different now.



If run it directly rather than via a script, the message "/compat/ubuntu/bin/vivaldi: line 45: 1758 Trace/breakpoint trap" will appear as "Trace/BPT trap" instead.
The Linuxulator doesn't support /proc/$pid/task/ I'll check this weekend whether it's worth it.

I'm afraid Vivaldi isn't usable on FreeBSD as is. They should stop virtue-signaling about "sovereign tech" and fully open-source the browser instead. I hope Google "steals" those features so I can go back to plain Google Chrome instead.
 
Back
Top