I may have broken Plots.jl and GR.jl by introducing v0.69.1+1 of GR_jll. In particular, you might see an issue when trying to use any GR plugins. For example, the bug creates an issue when using SVG output within VSCode.
The fix is currently on the master branch of GR.jl. Alternatively, you can downgrade GR_jll to v0.69.1+0 via the following commands.
using Pkg
pkg"add GR_jll#fc933dae4a54c49707193e2dcc7df1e5ef201cab"
A new release of GR.jl should be forthcoming in the next few days.
A new release of GR.jl should be forthcoming in the next few days.
As @t-bltg did, the solution to this is not to tell people to use a master version and wait a few days for a new release, it is to immediately yank the faulty version.
After writing my problems / observations into a new thread (why cannot I include links? See thread “Why can svgplugin.dll not be found? (for PackageCompiler binary, bundled artifacts)” in General Usage), I became aware of this thread here.
It seems somehow related. However, in my case I have the problem with a compiled binary on Windows with PackageCompiler.jl and I am using GR_jll v0.72.10+0
The issue described here (apart from that the description matches exactly what I am experiencing) applies to GR_jll < 0.70 (I read in 0.70 it should have been fixed) and also that the issue arrises when calling the function from a VSCode REPL (not from a compiled binary).
So, is my issue indeed somehow related with this one? And if so, how could I solve this?
It seems like there is a regression bug in 0.72 (I tried 0.73 as well but it does not compile because of Qt6Wayland errors during PackageCompiler execution).
Because 0.70 works without issues. But 0.72 brings this error again for the compiled binary with Package Compiler.