Thank you Stuart, that is very helpful.

Can confirm that, as a workaround, symlinking /etc/ungoogled-chromium to
/etc/chromium AS WELL AS ~/.config/ungoogled-chromium to
~/.config/chromium gets me a working app.


On Thu, 11 Dec 2025 14:21:32 +0000
Stuart Henderson <stu@spacehopper.org> wrote:

> +cc robert
> 
> the last update changed /etc/ungoogled-chromium to /etc/chromium in
> various patches,
> 
> patch-chrome_common_chrome_paths_cc
> patch-sandbox_policy_openbsd_sandbox_openbsd_cc
> 
> iridium is still ok
> 
> 
> On 2025/12/11 14:01, requiem. wrote:
> > Hello ports@,
> > 
> > ungoogled-chromium on -current fails to launch at the moment.
> > It keeps looking for things in /etc/chromium, which, until
> > upgrading to the latest snapshot in ports, did not exist on my
> > system.
> > 
> > On first launch after reboot it said:
> > ```
> > $ ungoogled-chromium 
> > [93213:10566547502000:1211/134843.979021:ERROR:sandbox/policy/openbsd/sandbox_openbsd.cc:282]
> > failed to open /etc/chromium/unveil.main errno: 2
> > ```
> > 
> > So as 
> > /etc/chromium/unveil.main did not exist on my computer,  I created
> > an empty file to see what happens, then it crashes with various
> > other missing bits, see log output below:
> > https://termbin.com/soga
> > Core dump available here:
> > http://0x0.st/KCTp.core
> > 
> > Current setup:
> > ```
> > # sysctl kern.version
> > kern.version=OpenBSD 7.8-current (GENERIC.MP) #145: Wed Dec 10
> > 13:54:02 MST 2025
> > deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > # pkg_info ungoogled-chromium     
> > Information for inst:ungoogled-chromium-143.0.7499.40
> > ```
> >