# Plots.jl, GR.jl broken due to GR\_jll v0.69.1+1

**URL:** <https://discourse.julialang.org/t/plots-jl-gr-jl-broken-due-to-gr-jll-v0-69-1-1/89708>\
**Category:** General Usage\
**Tags:** plotting\
**Created:** [November 3, 2022, 10:33am UTC](https://discourse.julialang.org/t/plots-jl-gr-jl-broken-due-to-gr-jll-v0-69-1-1/89708 "2022-11-03T10:33:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mkitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkitti/32/12459_2.png) [@mkitti](https://discourse.julialang.org/u/mkitti)\
**Post date:** [November 3, 2022, 10:33am UTC](https://discourse.julialang.org/t/plots-jl-gr-jl-broken-due-to-gr-jll-v0-69-1-1/89708/1 "2022-11-03T10:33:55Z")

</div>

Hi all,

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.

> <https://github.com/jheinen/GR.jl/issues/486>
>
> After https://github.com/JuliaPackaging/Yggdrasil/pull/5784, I am encountering t…his issue on Windows with GR\_jll v0.69.1+1:
> 
> \`\`\`
> GKS: svgplugin.dll: can't load library, error 126 (0x7e)
> ERROR: SystemError: opening file "...\\\\jl\_ViZ8T6pmd8.svg": No such file or directory
> \`\`\`
> 
> I can resolve by one of the following. 
> 
> 1. Downgrading GR\_jll to v0.69.1+0
> \`\`\`
> \] add GR\_jll#fc933dae4a54c49707193e2dcc7df1e5ef201cab
> \`\`\`
> 
> 2.
> \`\`\`julia
> using GR\_JLL
> Libdl.dlopen(joinpath(dirname(GR.GRPreferences.GR\_jll.libGR\_path), "svgplugin"))
> \`\`\`
> 
> I'm adding the later to #483

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.

```julia
using Pkg
pkg"add GR_jll#fc933dae4a54c49707193e2dcc7df1e5ef201cab"

```

A new release of GR.jl should be forthcoming in the next few days.

---

<div class="post-metadata">

**Author:** ![t-bltg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/t-bltg/32/25526_2.png) [@t-bltg](https://discourse.julialang.org/u/t-bltg)\
**Post date:** [November 3, 2022, 11:53am UTC](https://discourse.julialang.org/t/plots-jl-gr-jl-broken-due-to-gr-jll-v0-69-1-1/89708/2 "2022-11-03T11:53:37Z")

</div>

`GR_jll 0.69.1+1` yanked in [yank broken `GR_jll` (windows - vscode) by t-bltg · Pull Request #71554 · JuliaRegistries/General · GitHub](https://github.com/JuliaRegistries/General/pull/71554).

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [November 3, 2022, 12:58pm UTC](https://discourse.julialang.org/t/plots-jl-gr-jl-broken-due-to-gr-jll-v0-69-1-1/89708/3 "2022-11-03T12:58:39Z")

</div>

> 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.

---

<div class="post-metadata">

**Author:** ![mkitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkitti/32/12459_2.png) [@mkitti](https://discourse.julialang.org/u/mkitti)\
**Post date:** [November 3, 2022, 1:32pm UTC](https://discourse.julialang.org/t/plots-jl-gr-jl-broken-due-to-gr-jll-v0-69-1-1/89708/4 "2022-11-03T13:32:15Z")

</div>

Yes, of course. Sorry, I did not get the note that it would be a couple days to release until i was asleep.

---

<div class="post-metadata">

**Author:** ![testmax](https://avatars.discourse-cdn.com/v4/letter/t/e47774/32.png) [@testmax](https://discourse.julialang.org/u/testmax)\
**Post date:** [July 18, 2025, 2:44pm UTC](https://discourse.julialang.org/t/plots-jl-gr-jl-broken-due-to-gr-jll-v0-69-1-1/89708/5 "2025-07-18T14:44:08Z")

</div>

Hi there!

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?

---

<div class="post-metadata">

**Author:** ![testmax](https://avatars.discourse-cdn.com/v4/letter/t/e47774/32.png) [@testmax](https://discourse.julialang.org/u/testmax)\
**Post date:** [July 18, 2025, 5:33pm UTC](https://discourse.julialang.org/t/plots-jl-gr-jl-broken-due-to-gr-jll-v0-69-1-1/89708/6 "2025-07-18T17:33:18Z")

</div>

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.

See also here: [Why can svgplugin.dll not be found? (for PackageCompiler binary, bundled artifacts) - #2 by testmax](https://discourse.julialang.org/t/why-can-svgplugin-dll-not-be-found-for-packagecompiler-binary-bundled-artifacts/130848/2)

Edit: Yeah, now links seem to work…