Hacker News Reader

Comment by lol768 | Hacker News Reader

Been great to see apps slowly getting more native Wayland support.

I'm looking forward to Java/Swing hopefully gaining support too via Project Wakefield.

Why are all these projects names based on Boston area towns? (Wayland, Weston, Wakefield…)

I think the story is that an X developer was driving from Weston to Wayland when he had a lightbulb moment concerning how to radically simplify the graphics stack.

I grew up in the Boston area, but I didn't make this connection! Wakefield borders where I grew up, but I don't recall the others being super nearby (maybe they're south of Boston, since I'm not as familiar with that area, or maybe they're further west and I have an overly narrow idea of what "near Boston"means due to being so close)

I think it started with Weston and Wayland:

"Høgsberg had the inspiration for Wayland while driving through the town of Wayland in Massachusetts, which gave the display server its name. Weston, the Wayland compositor, is named after a neighbouring town in the same state"

http://www.h-online.com/open/features/Wayland-Beyond-X-14320...

(As someone who lived in one of those towns it's always amused me when it comes up.)

Same, using jetbrains products in sway is currently a big mess. But i didn't hear much from Wakefield anymore, is it being actively developed?

Yes, it is. Last news I heard is that they will implement the protocol themselves. Seems weird to me. They already support Gtk 3, why not use that? The biggest conceptual roadblock is `java.awt.Robot` because Wayland restricts moving pointers and taking screenshots.

I use Manjaro with Gnome on Wayland. No issues there with Intellij. Works fine. I think the issue might be with Sway?

In general I'm not having a lot of issues with Wayland. At least not more than usual amount of "just tweak this file over there and it's fine" stuff you have with Linux in general. There's just an endless amount of libraries that need to be aligned with each other. It's one of the reasons I use an arch based distribution so that at least I'm not dealing with stuff that was fixed months/years ago.

The largest issue is that it looks extremely blurry on 4k- not like the usual “1080p upscaled” more like 720p upscaled and not aligned with the pixels at all.

Works perfectly fine on 1080p, which was the majority of where I spend my time on Linux, until recently.

The problem is, that jetbrains runs under xwayland. This means under the hood it still runs under xorg. On 4k monitors you probably want to scale your GUI and thats where the problems arise. It looks completely blurry and has a resolution of 1920x1080 but on a 4k monitor.

I have never had issues on Sway with Jetbrains products. Maybe I don't use them enough.

There is a quickfix for most of the problems, just set one ENV variable:

> export _JAVA_AWT_WM_NONREPARENTING=1

This env variable is already in my /etc/environment. This makes the jetbrains products at least usable, but my problem is the blurryness on my 4k monitors.

FYI /etc/environment might not be the best place

https://superuser.com/a/664236

Regardless, JetBrains products works fine on my 4k monitors, so it is possible. There is something different between our systems.

Your jetbrains products are not blurry in sway? Do you scale your output on the 4k monitors?

Not blurry at all, at least with GoLand or PyCharm. No scaling, haven't tested with scaling to be fair.

Output DP-3 'Goldstar Company Ltd LG HDR 4K' (focused)

  Current mode: 3840x2160 @ 59.997 Hz

  Position: 0,0

  Scale factor: 1.000000

  Scale filter: nearest

  Subpixel hinting: unknown

  Transform: 270

  Workspace: 5

  Max render time: off

  Adaptive sync: disabled

  Available modes:

Scaling is the whole problem, that is why it is so blurry. I can't read anything on my 4k monitor without scaling enabled and scaling works way better on wayland than on x.org that is why i switched. And because scaling on x.org doesn't work great, jetbrains products are blurry. I kind of hoped you had a secret weapon that could work around it.

You can leave native scaling as 1, and instead scale Jetbrains settings (font etc.) without making it blurry.

Maybe that is the secret weapon…

Reply on news.ycombinator.com