[BUG] plotting with GR hangs after update

[AndiMD]

Details

Plotting command hangs, seemingly idle (no network or CPU activity). Same happens when using GR directly.

julia> using Plots

julia> Plots.plot(rand(5)) # hangs
^C^C^C^C^C^CWARNING: Force throwing a SIGINT
Error showing value of type Plots.Plot{Plots.GRBackend}:
ERROR: InterruptException:
Stacktrace:
 [1] setcharheight(::Float64) at /home/andi/.julia/packages/GR/Atztx/src/GR.jl:1395
 [2] gr_set_font(::Plots.Font, ::Plots.Subplot{Plots.GRBackend}; halign::Symbol, valign::Symbol, color::RGB{FixedPointNumbers.Normed{UInt8,8}}, rotation::Int64) at /home/andi/.julia/packages/Plots/u8HRI/src/backends/gr.jl:384
 [3] gr_set_xticks_font(::Plots.Subplot{Plots.GRBackend}) at /home/andi/.julia/packages/Plots/u8HRI/src/backends/gr.jl:684
 [4] _update_min_padding!(::Plots.Subplot{Plots.GRBackend}) at /home/andi/.julia/packages/Plots/u8HRI/src/backends/gr.jl:896
 [5] iterate at ./generator.jl:47 [inlined]
 [6] _collect(::Array{AbstractLayout,2}, ::Base.Generator{Array{AbstractLayout,2},typeof(Plots._update_min_padding!)}, ::Base.EltypeUnknown, ::Base.HasShape{2}) at ./array.jl:678
 [7] collect_similar(::Array{AbstractLayout,2}, ::Base.Generator{Array{AbstractLayout,2},typeof(Plots._update_min_padding!)}) at ./array.jl:607
 [8] map(::Function, ::Array{AbstractLayout,2}) at ./abstractarray.jl:2072
 [9] _update_min_padding!(::Plots.GridLayout) at /home/andi/.julia/packages/Plots/u8HRI/src/layouts.jl:310
 [10] prepare_output(::Plots.Plot{Plots.GRBackend}) at /home/andi/.julia/packages/Plots/u8HRI/src/plot.jl:184
 [11] display(::Plots.PlotsDisplay, ::Plots.Plot{Plots.GRBackend}) at /home/andi/.julia/packages/Plots/u8HRI/src/output.jl:149
 [12] display(::Any) at ./multimedia.jl:323
 [13] #invokelatest#1 at ./essentials.jl:712 [inlined]
 [14] invokelatest at ./essentials.jl:711 [inlined]
 [15] print_response(::IO, ::Any, ::Bool, ::Bool, ::Any) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/REPL/src/REPL.jl:161
 [16] print_response(::REPL.AbstractREPL, ::Any, ::Bool, ::Bool) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/REPL/src/REPL.jl:146
 [17] (::REPL.var"#do_respond#38"{Bool,REPL.var"#48#57"{REPL.LineEditREPL,REPL.REPLHistoryProvider},REPL.LineEditREPL,REPL.LineEdit.Prompt})(::Any, ::Any, ::Any) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/REPL/src/REPL.jl:729
 [18] #invokelatest#1 at ./essentials.jl:712 [inlined]
 [19] invokelatest at ./essentials.jl:711 [inlined]
 [20] run_interface(::REPL.Terminals.TextTerminal, ::REPL.LineEdit.ModalInterface, ::REPL.LineEdit.MIState) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/REPL/src/LineEdit.jl:2354
 [21] run_frontend(::REPL.LineEditREPL, ::REPL.REPLBackendRef) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/REPL/src/REPL.jl:1055
 [22] run_repl(::REPL.AbstractREPL, ::Any) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/REPL/src/REPL.jl:206
 [23] (::Base.var"#764#766"{Bool,Bool,Bool,Bool})(::Module) at ./client.jl:383
 [24] #invokelatest#1 at ./essentials.jl:712 [inlined]
 [25] invokelatest at ./essentials.jl:711 [inlined]
 [26] run_main_repl(::Bool, ::Bool, ::Bool, ::Bool, ::Bool) at ./client.jl:367
 [27] exec_options(::Base.JLOptions) at ./client.jl:305
 [28] _start() at ./client.jl:484

Backends

This bug occurs on ( insert x below )

Backend	yes	no	untested
gr (default)	x
pyplot		x
plotly			x
plotlyjs			x
pgfplotsx			x
inspectdr			x

Versions

Plots v1.4.4
GR v0.50.1 (works with v.0.48.0)

Julia Version 1.4.2
Commit 44fa15b150* (2020-05-23 18:35 UTC)
Platform Info:
  OS: Linux (x86_64-pc-linux-gnu)
  CPU: Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-8.0.1 (ORCJIT, skylake)
Environment:
  JULIA_EDITOR = vim
  JULIA_NUM_THREADS = 4

[BeastyBlacksmith]

Is that from within the terminal or some IDE?

[AndiMD]

Occurs in terminal (standard KDE Konsole). I seem to always get the same stacktrace with Ctrl+C, at setcharheight(::Float64)

[AndiMD]

I did some more tests, after which I got it to work. If somebody has similar issues: It appears that downgrading Mesa 19.3 to Mesa 19.2.8 (=default on Ubuntu 18.04) fixed this issue.