On 09/11/2025 10:38, Lorenzo Sutton wrote:
On 07/11/2025 19:17, Lorenzo Sutton wrote:
Hi Hermann,
On 06/11/2025 20:11, ichthyo wrote:
On 04/11/2025 16:27, ichthyo wrote:
- the crash happens under Wayland / Gnome, immediately at the point
when the main UI is created (the splash screen still displays)
On 06/11/2025 18:52, Lorenzo Sutton wrote:
Not sure if this is helpful...
Hello Lorenzo,
yes, such a test is indeed very helpful,
as there are some differences in the usage of Wayland
under KDE Plasma vs Gnome.
On Manjaro with KDE Plasma running a Wayland session I am able to
start and play with Yoshimi (just compiled from git), albeit with
the slider issue reported a while back [1]
just to confirm: can you try to start yoshimi from the terminal
and explicitly request that yoshimi uses the Wayland backend?
This can be done with the following command line:
FLTK_BACKEND=wayland yoshimi
Running that command in a Wayland does start yoshimi correctly, but...
I was suspicious and followed the advice in the Arch Wiki and it seems
that even in that case actually yoshimi might be running via xwayland.
I tested this by installing extramaus and as far as I understand if
the red cursor moves in the window it is running as xwayland [1]. I
also tested using xprop which does spit out stuff when clicking on the
yoshimi window:
https://wiki.archlinux.org/title/Wayland#Detect_Xwayland_applications
So it seems on my system (or KDE Plasma in general?) yoshimi is
running with Xwayland even if FLTK_BACKEND is set to wayland? :/
I also tested wayland-only applications and they do run in the wayland
session.
I also found this post from more than one year ago which mentions
FLTK_BACKEND and Kde/plasma, but I haven't figured out if / what this
is relevant.
https://www.fltk.org/newsgroups.php?s0+gfltk.coredev+v22172+T
Unfortunately I don't think we can prove that wayland works on KDE,
well at least not strictly, as for some reason it is using xwayland
under KDE even when in a wayland session. :-(
Let me know if I could test something else.
I did another test (not sure if useful).
I booted into a live KDE Neon iso, which I guess is one of the 'most
KDE' distros around /_and_ /runs wayland by default. Installed yoshimi
from its repositories and, again yoshimi started fine, _but_ as what
seems to be an xwayland application.
I also did another test: I run Fluid [1] (which I guess is 'as FLTK as
it gets...') in a wayland session, and again it seems to be running as
xwayland
So the theme would seem to be that on KDE Plasma FLTK is run as
Xwayland? Not sure were this could be confirmed, maybe somewhere KDE if
that is useful.
Quickly reporting about another test I did yesterday: I started an
Ubuntu live - the one currently available (24.04.3-desktop). It seems,
like many live distros, that it defaults to x11 in live mode, so I
set-up and enabled wayland (as reported by $XDG_SESSION_TYPE) and,
again, yoshimi happily starts and plays. And, again, it is using xwayland!
The whole wayland situation is really confusing to me at this point, as
I even tried 'removing' x11 on that Ubuntu live (with admittedly little
knowledge or information on if/how that would actually be possible), and
ended up with a semi-broken system. That is also because there are
probably many intricacies with GNOME (and GDM) which I don't know much
about not having used Gnome since Gnome 2 (sic!)
Hope this testing can somewhat be helpful :)
Lorenzo
_______________________________________________
Yoshimi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
