From: Pedro C. <ped...@gm...> - 2021-09-14 18:07:59
|
Thanks for the support. Im my distro I have installed both gtk2 and gtk3 development packages. The command I issue to start jedit is the following: --------- java -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true -Djdk.gtk.version=2 -jar ./jedit.jar --------- So it starts with all the options the usual start script and also the option requiring for gtk version 2 .. On Tue, Sep 14, 2021 at 2:11 PM Jesse Pavel <jp...@al...> wrote: > > Hi Pedro, > > The "[xcb]" errors apparently are caused by GTK v2/3 issues. > Java 11 uses GTK3 by default, I believe. > You can force gtk2 usage via "-Djdk.gtk.version=2" on the command-line. > > Jesse > > > On Tue, Sep 14, 2021 at 5:14 AM Pedro Coelho <ped...@gm...> wrote: >> >> First and foremost thanks for the fast reply. >> I'm using OpenSuSE Leap latest version with installed openJDK 11 >> java --version >> openjdk 11.0.12 2021-07-20 >> OpenJDK Runtime Environment (build 11.0.12+7-suse-3.59.1-x8664) >> OpenJDK 64-Bit Server VM (build 11.0.12+7-suse-3.59.1-x8664, mixed mode) >> >> I was able to start jedit once the option -noplugins. >> After that it also gave the same error. >> Then I decided to Clean my ~/.jedit/ directory since that could >> indeed be the problem because I always save use this same /home and >> all folder even after all jedit upgrades ... since the first versions >> ... :) >> So I backed up the .jedit directory and removed all files >> Now I get and even more serious error: >> ------------------------------------------------------ >> ~/bin/jedit -noplugins >> [xcb] Unknown sequence number while processing reply >> [xcb] Most likely this is a multi-threaded client and XInitThreads has >> not been called >> [xcb] Aborting, sorry about that. >> java: xcb_io.c:727: _XReply: Assertion `!xcb_xlib_threads_sequence_lost' failed. >> Aborted (core dumped) >> ------------------------------------------------------ >> the same error occurs if I simply exceute the jedit command with or >> without the reference to load plugins or not. >> Is there something wrong with my setup ? >> regards. >> >> On Mon, Sep 13, 2021 at 11:34 PM Dale Anson <da...@da...> wrote: >> > >> > Yeah, it's getting stuck on parsing the killring.xml (KILLRING not killing!). That happens before plugins are loaded, so it's not a plugin issue. You can just delete the killring.xml file, jEdit will make a new one for you. >> >> >> -- >> ----------------------------------------------- >> jEdit Users' List >> jEd...@li... >> https://lists.sourceforge.net/lists/listinfo/jedit-users |