| 21 Nov 2025 |
 uep | i guess I can also try just the gtk patch against current unstable | 10:23:12 |
 Vladimír Čunát | But it looks OK on Hydra:
https://hydra.nixos.org/build/313850824#tabs-buildsteps | 10:23:19 |
 K900 | Flaky presumably? | 10:23:34 |
| Vladimír Čunát | That's just a while ago, before the gtk4 bump. | 10:23:33 |
| uep | possibly, I'm rerunnig | 10:24:03 |
| K900 | I'm building a webkitgtk | 10:24:57 |
| uep | error: Cannot build '/nix/store/c4flivqdyqarf44pfxzj96z8gghb9jg6-gtksourceview-5.18.0.drv'.
Reason: builder failed with exit code 1.
Output paths:
/nix/store/gcd6mpxw24n90prlnh6l73pk60v85ksz-gtksourceview-5.18.0-dev
/nix/store/pz80sfrpla7s52qwbjqqmw386fl6i3l5-gtksourceview-5.18.0
/nix/store/s71x0nqy1fx0574i6gz4vjizmrzid9gg-gtksourceview-5.18.0-devdoc
Last 25 log lines:
> /var/cache/fontconfig
>
> Fontconfig error: No writable cache directories
> /homeless-shelter/.cache/fontconfig
> /var/cache/fontconfig
>
> Fontconfig error: No writable cache directories
> /homeless-shelter/.cache/fontconfig
> /var/cache/fontconfig
>
> Fontconfig error: No writable cache directories
> /homeless-shelter/.cache/fontconfig
> /var/cache/fontconfig
>
>
>
> Summary of Failures:
>
> 26/26 test-language-specs TIMEOUT 30.52s killed by signal 15 SIGTERM
> | 10:25:51 |
| uep | ugh | 10:25:57 |
| K900 | Oh great | 10:34:45 |
| K900 | Most of the blast is actually just zenity -> ffmpeg -> oof | 10:34:54 |
| K900 | * Most of the blast is actually just zenity -> sdl -> ffmpeg -> oof | 10:35:17 |
| uep | gjs fails too | 10:38:00 |
| K900 | That one built here | 10:38:35 |
| K900 | Oh no I'm building qtwebengine too | 10:39:34 |
| K900 | I guess that makes sense | 10:39:37 |
| K900 | Given ffmpeg | 10:39:40 |
| uep | ❯ nix flake update --override-input nixpkgs github:k900/nixpkgs/gtk-4.20.3 nixpkgs
| 10:40:01 |
| uep | I just did this.. guess i'll try the patch against current unstable instead | 10:40:30 |
| K900 | All that stuff should be cached on next | 10:42:38 |
| K900 | So whatever rebuilds you're getting are from the gtk update | 10:42:47 |
| K900 | Sadly | 10:42:47 |
| K900 | Maybe just try running less builds at a time | 10:42:58 |
| K900 | They tend to be weirdly timing sensitive | 10:43:06 |
| uep | it's trying a lot in parallel.. 36c/72t makes it greedy i guess | 10:44:15 |
| uep | nah, gjs blows up every time | 10:56:35 |
| uep | > Gjs-Message: 10:54:41.636: Profiler started
> Gjs-Message: 10:54:41.636: Profiler stopped
> Trace/breakpoint trap (core dumped)
> Trace/breakpoint trap (core dumped)
>
> (gjs-console:2804): Gjs-CRITICAL **: 10:54:42.406: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
> The offending callback was destroy(), a vfunc.
> == Stack trace for context 0x5555555b36c0 ==
> Gjs-Message: 10:54:42.497: Wrote coverage statistics to /build/gjs-1.86.0/build/coverage.lcov
> Trace/breakpoint trap (core dumped)
| 10:57:45 |
| uep | yuck | 10:57:47 |
| uep | going to try building just staging-next first | 11:01:15 |
| Vladimír Čunát | You're atop staging-next now? | 11:02:06 |
| Vladimír Čunát | So the gjs build is this one?
/nix/store/p8qi0c1z1mv0x67pwd9p0s64y4dsma9z-gjs-1.86.0.drv
| 11:02:16 |
