Re: ungoogled-chromium and syspatch 018_pledgepaths

[Achaean]

I'm not doubting the issue, but for the sake of troubleshooting a 
potentially hardware-specific bug...

I have a system with 018_pledgepaths + ungoogled-chromium, and no 
apparent issues with Intel/graphics.

On 3/11/26 5:27 PM, Phil Maker wrote:
G'day,

Oneliner: ungoogled-chromium breaks with syspatch 018_pledgepaths 7.8

After updating with syspatch the other day ungoogled-chromium core dumps
with a cannot access GPU error. Trying to run it with --disable-gpu
has the same problem.

Reverting the patch using syspatch -r and rebooting lets it run again.

So:

1. Does 018_pledgepaths require possibly an upgrade of the port/package?
2. Reinstalling etc didn't change anything.
3. Rebuilding from the original ports failed with a python 3 install error
     but thats probably user error.

This post is mostly for the information of anyone who stumbles
across the problem.

--
Phil Maker <philip.ma...@gmail.com <mailto:philip.ma...@gmail.com>>, 
<p...@gnu.org <mailto:p...@gnu.org>>
  <https://a-star-microgrid.com <https://a-star-microgrid.com>>, 
<https://iesconnect.net <https://iesconnect.net>>
phone: +61 (0) 439 223 469 TZ +9h30m
ALT: remote email: <philmakerph...@gmail.com 
<mailto:philmakerph...@gmail.com>>

--
Tyler Anderson (Achaean)
acha...@sinelabs.ca