On Sat, 19 Jul 2025 20:29:19 +0200, Michael Joy <michaeljo...@protonmail.com> wrote: > > Did a sysupgrade yesterday and since then I can't open ungoogled-chromium > or kitty. I'm not at all worried about kitty but I use > ungoogled-chromium as my primary browser. I've attached dmesg.boot and the > terminal output while trying to open ungoogled-chromium. I've done another > sysupgrade about half an hour ago that didn't help. Ruled out an i3 issue > as it's the same on CWM. Please reach out if there is more information I > can provide or any action I can take. >
I see following issues: ungoogled-chromium:/usr/X11R6/lib/libpciaccess.so.2.1: undefined symbol '__stderr' ungoogled-chromium:/usr/lib/libc++abi.so.8.0: undefined symbol '__stderr' ungoogled-chromium:/usr/lib/libc++.so.11.0: undefined symbol '__stdin' ungoogled-chromium:/usr/lib/libc++.so.11.0: undefined symbol '__stdout' that suggest that your packages and base is out of sync after so-called the opaque stdio earthquake. Here two options: 1. wait until new packages is here, amd64 I think should be soon; 2. rollback to snapshot before the opaque stdio earthquake. For (2) I guess https://openbsd.cs.toronto.edu/archive/2025-07-16/ should be safe guess. -- wbr, Kirill
