Right today my favourite development environment JetBrains Rider stopped working after updating to the current 2019.2 version:

JetBrains Toolbox

After starting the application a blank screen (normally with the list of recent projects to open) showed up.

I checked my Windows Box, but it had no problems with the current release. It worked like a charm.

So this was Linux specfic. My workstation runs Fedora 30 and so I started researching. I found out that under X I could set

export _JAVA_AWT_WM_REPARENTING=1

in the current fish session, but that helped only when starting Rider via command console. I noticed that the error was due to JetBrains Rider 2019.2 was running under XWayland in Wayland itself.

So there are a couple of articles on the internet regarding this, mostly related on how to configure systemd to set this variable in the XWayland session for a specific application.

That sounded too complex for me for such a small change.

But then I noticed that JetBrains Rider itself has a configuration file in the current base directory:

JetBrains Rider 2019.2 vmoptions file

That looked like it would work! So I modified it as follows:

_JAVA_AWT_WM_REPARENTING=1 in JetBrains Rider vmoptions file

And then I started Rider like always via Gnome under Wayland:

JetBrains 2019.2 working again under Wayland in Gnome

Violá! I hope you find this information useful!

JetBrains Rider does not start under Fedora 30

Johannes Rest


.NET Architekt und Entwickler


Beitragsnavigation


Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.

17 − drei =