I am running Jabref in what was Pop_OS!, which is now “COSMIC” which is “wayland” based I believe. When I try to run Jabref in COSMIC it seems like there are function issues, like using “control + c or v” doesn’t seem to work in Jabref, checked it a few times, so I have to run the machine in the GNOME DE and that still provides X11 capacity, and that seems to run Jabref more cleanly.
COSMIC offers more GUI stuff to play with, but then the fan seems to be louder with it, GNOME is more simple, but then Jabref 6.0 works better. Is this a “known thing” that Jabref isn’t “wayland friendly” or it’s supposed to be, but is taking personal exception for me???
JabRef uses JavaFX for the GUI, which has not been made fully compatible with Wayland yet. This doesn’t mean that JabRef will not run Wayland. It just means that Xwayland is necessary to be installed by you, unless it already comes with your Operating System, which is also mentioned in our FAQ: Linux | JabRef
I have not used Pop-OS before, so I don’t know if they officially support XWayland or not. Apparently they have it in their repos: GitHub - pop-os/xwayland: Backport of https://salsa.debian.org/xorg-team/xwayland/ · GitHub, but if that is part of their current release, I do not know. I would check, if it’s installed on your system and if not, I would ask around in the Pop-OS Forum why it isn’t and if it’s ok to install it or if that will lead to incompatibilities.
Ah, OK, thanks for the explanation, for the most part there were other glitches when I was running wayland that I for the most part don’t run it, but it does look like the “wave of the future” . . . . I had not heard of Xwayland until you mentioned it, that must be the “compromise” effort . . . ???
I’ll have to check it later today when I get back to my Sys76 Pop/COSMIC machine to see if it has installed XWayland or not . . . the more, the merrier, etc. I’ll check back when I have got something adjusted on it . . . .
So a search of synaptic package manager shows I have “xwayland xxxxx” installed, but it was just showing that one package, with only two other packages listed with “xwayland” in the name . . . . So “xwayland” seems to be there, but trying to run that word in the console didn’t launch anything in the “visible” sense . . . .