I'll preface this by saying I'm not sure if this is an issue with Arch Linux specifically or across all Linux distros. I'm fooling around a bit with the VTE widget, as you probably know they recently changed the VTE ABI from fork_command to spawn_sync. When I try to run the terminal against the default LIBRARY.PATH, libvte2_90.so, I get a complaint about unsatisfied linkage.
If I run nm -D libvte2_90.so, I can see it still has the fork_command function rather then spawn_sync. On Arch Linux, libvte-2.91.so has the spawn_sync command and if I update gtkc.paths.LIBRARY.VTE to use this things work as expected.
I'll preface this by saying I'm not sure if this is an issue with Arch Linux specifically or across all Linux distros. I'm fooling around a bit with the VTE widget, as you probably know they recently changed the VTE ABI from fork_command to spawn_sync. When I try to run the terminal against the default LIBRARY.PATH, libvte2_90.so, I get a complaint about unsatisfied linkage.
If I run nm -D libvte2_90.so, I can see it still has the fork_command function rather then spawn_sync. On Arch Linux, libvte-2.91.so has the spawn_sync command and if I update gtkc.paths.LIBRARY.VTE to use this things work as expected.