Vincent Lefevre

I did not see this message, grrr... Here's the stack trace: #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x00007f60d833ea84 in g_cond_wait_impl (cond=0x55a694e3ab80, mutex=0x55a694e3ab78) at ../../../glib/gthread-posix.c:1007 #2 g_cond_wait (cond=cond@entry=0x55a694e3ab80, mutex=mutex@entry=0x55a694e3ab78) at ../../../glib/gthread.c:1665 #3 0x00007f60d77a42e3 in pango_fc_patterns_get_font_pattern (pats=0x55a694e3ab70, i=0, prepare=<synthetic pointer>) at ../pango/pangofc-fontmap.c:1136...

maxima.el triggers a warning about deprecated positional arguments to define-minor-mode

So, a simple command to reproduce the issue: echo 'set terminal wxt; plot x' | gnuplot -persist

This problem actually appears even without FVWM's ManualPlacement, i.e. if the window is displayed immediately. So I suppose that it is likely to occur with other window managers.

I've identified the "problematic" commit in Pango: https://gitlab.gnome.org/GNOME/pango/-/commit/89442dae443eba2aa0f0a526b4d6d39c0c9b13c6 The commit message is Just use a single fontconfig thread In ac4d8f2964299d14046cb, we switched from using GTask to using explicit threading for our fontconfig calls, since GTask assumes a mainloop and leaks memory otherwise. But now we are creating a new thread for every single fontconfig call, which is a bit excessive. As a compromise, create a single fontconfig...

Actually, the problem also occurs with gnuplot 5. It has actually appeared with the 1.52 pango library: downgrading the pango packages to 1.51 makes the problem disappear, both with gnuplot 5 and 6. Now, I don't know whether this is a bug in pango or a bug in gnuplot that is triggered only with the new version of pango (for instance, it might be possible that pango 1.52 is faster than 1.51, making the problem appear, since it seems to be a race condition).

With wxt, "gnuplot -persist" hangs if gnuplot cannot draw before stdin is closed

I can't see any reference to doc2web in gnuplot 5.4.4. Do you mean that it will be in the next gnuplot release? (This is actually a way to make the issue disappear.)