Frank Dana

On Fedora 42 with Python3.14-rc1 and graphviz 12.2.1, I get a JPEG output from the as-patched `pydot`: ```console $ cd ~/devel/fedora/ $ fedpkg clone pydot $ cd pydot $ fedpkg...

Fails in a `fedpkg --release f43 mockbuild` too. Same failure.

Sonofabitch! It is Graphviz. In a `mock -r fedora-43-x86_64 -n -N --shell` session after a failed build: ```console sh-5.3# cd build/BUILD/pydot-4.0.1-build/pydot-4.0.1 sh-5.3# PYTHONPATH=$(pwd)/src python3.14 ``` ```python >>> import string >>>...

`-Tjpe:cairo:gd` and `-Tjpe:cairo:devil` also produce vaid JPEGs. Presumably GDKPixbuf in F43 is using the new Glycin import/export code? That could be part of the issue. I definitely see that `/lib64/libgdk_pixbuf-2.0.so.0`...

When using `dot -Tjpe:cairo:gdk` in F43, gdkpixbuf attempts to access `/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache` and fails. It exits almost immediately after. On F42, that access is closely followed by the writing of JPEG...

Reported against Fedora's graphviz package at https://bugzilla.redhat.com/show_bug.cgi?id=2395533 I added you to the CC list, @spotaws

And, reported against Graphviz at https://gitlab.com/graphviz/graphviz/-/issues/2732

The only reason `format="png"` isn't affected is because `dot -Tpng` implies `dot -Tpng:cairo:cairo`. Running `dot -Tpng:cairo:gdk` will also produce empty files. I'm guessing any GDKPixbuf-based exporter is affected.

All of which is a long way of saying, this isn't any sort of Pydot bug. I'll keep this open for now to track the resolution of those upstream bugs,...

@spotaws It definitely looks to me like GDKPixbuf's new Rust backend is to blame. I've done a test build of the `graphviz` RPMs with it disabled, and as long as...