pkg: Fail to create /triggers:Bad file descriptor

pkg 2.6.2 on ARM64.

Should I treat the failures below as negligible, or report an issue?

More likely an issue with pkg, or with ports?

I can attach the typescript file to a report.


blah@aarch64:~ % pkg -v
2.5.1
blah@aarch64:~ % pkg upgrade -Fqy
pkg: Insufficient privilege to upgrade packages
blah@aarch64:~ % su -
Password:
root@aarch64:~ # pkg upgrade -Fqy
Conflicts with the existing packages have been found.
One more solver iteration is needed to resolve them.
root@aarch64:~ # date ; pkg upgrade -Fqy
Wed Mar 18 22:45:26 GMT 2026
root@aarch64:~ #

…

[122/122] Extracting xfce4-terminal-1.2.0: 100%
==> Running trigger: shared-mime-info.ucl
==> Running trigger: gtk-update-icon-cache.ucl
pkg: Fail to create /triggers:Bad file descriptor
==> Running trigger: desktop-file-utils.ucl
pkg: Fail to create /triggers:Bad file descriptor
==> Running trigger: glib-schemas.ucl
pkg: Fail to create /triggers:Bad file descriptor
You may need to manually remove /usr/local/etc/pkg.conf if it is no 
longer needed.
You may need to manually remove /var/lib/PackageKit/transactions.db if 
it is no longer needed.
root@aarch64:~ # echo $SHELL
/bin/tcsh
root@aarch64:~ # history 7
    252  22:56   date ; uptime
    253  22:57   bectl create 20260318-2257
    254  22:57   bectl mount 20260318-2257 /tmp/up
    255  22:57   pkg -r /tmp/up upgrade -Fqy
    256  23:03   pkg -r /tmp/up upgrade -U
    257  23:48   echo $SHELL
    258  23:48   history 7
root@aarch64:~ # bectl umount 20260318-2257
root@aarch64:~ # bectl activate -t 20260318-2257
Successfully activated boot environment 20260318-2257 for next boot
root@aarch64:~ # exit
exit

Script done, output file is typescript
root@aarch64:~ #