On 05/01/2026 23:38, ichthyo wrote:
We got some responses on Stackoverflow
Uli Schlachter ⟶ https://stackoverflow.com/a/79860970/444796
See discussion in the Github issue
https://github.com/Yoshimi/yoshimi/issues/243
On 06/01/2026 21:09, ichthyo wrote:
Uli / @psychon joined the discussion in the Github issue:
" I tried to produce something even more stripped down by "reinventing things"
in a single file. I used a generous amount of copy&paste from your stripdown
branch. The result is at https://github.com/psychon/yoshimi-debugging";
Uli made an interesting discovery:
The fact that we are using custom drawing with Cairo at the same time
also in the WidgetPDial seems to "confuse" the caching in FLTK.
Hello Yoshimi-devs,
So now we are in a confusing situation where we need a short-term
workaround and also find a long-term solution suitable for Yoshimi.
To summarise:
- after more than 10 years development, the major desktops
decided to "flip the switch" and enable Wayland by default
- some of our users are now running under Wayland and see
strange behaviour and (initially) even got a SEGFAULT.
- short-term there is the workaround to use XWayland.
But *Warning* we should not assume this is maintained forever.
What issues do we have:
(1) Crash / SEGFAULT at start.
The reason is custom drawing with Cairo in our custom widgets.
Jesper worked out a proper solution, and we have introduced
compile time switches to handle that in all possible variants.
(2) Some distributions do build FLTK 1.4 without the Cairo support.
Notably Arch and derivatives. This breaks our solution for (1)
(3) In one pop-up window we use Cairo to draw one single graph-line
This uncovered two bugs in FTLK 1.4
(4) Our positioning code for pop-up windows is broken under Wayland.
FLTK/Upstream does not have a solution, but seems interested.
But *we* need to *push* for a feature-request IMHO.
(1) could be considered solved
but (2) affects some People: *we* should take initiative and file
a bug with the Arch distributor (no response to my mails thus far)
Regarding (3) the most pragmatic solution is to use FTLK for drawing
in that single case, so to circumvent that problematic situation
But what about (4). Is that a "showstopper" or just a minor annoyance?
It clearly is a missing feature, but it's unlikely it will get fixed
soon, unless we get active and engage into a discussion with the
FLTK people. Who could take care of that?
-- Hermann
PS:
Wayland-Crash-Issues:
https://sourceforge.net/p/yoshimi/bugs/40/
https://github.com/Yoshimi/yoshimi/issues/240
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112199
NOTE: if the Debian bug is not resolved, Yoshimi will drop out
of Debian/Testing in some months into the future.
Discussion / Issue for the pop-ups:
https://github.com/Yoshimi/yoshimi/issues/243
https://stackoverflow.com/questions/79859360/fltk-wayland-x11-custom-drawing-in-a-pop-up-window
FLTK-Issues (yet unsolved)
https://github.com/fltk/fltk/issues/1358
https://github.com/fltk/fltk/issues/1359
_______________________________________________
Yoshimi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
