Continued absurd Linux problems: If I run in Wayland,...

mcc

Continued absurd Linux problems:

If I run in Wayland,
and run Chrome,
my custom .XCompose file is ignored.

Chrome on X11 does not have this problem,
Wayland apps other than Chrome do not have a problem,
if I use default XCompose sequences instead of custom XCompose there is no problem.

It's just this one combination of things.

Checking the Chromium bug tracker I find variations of this bug repeatedly filed, then closed, as far back as 2015 and as recently as 2021, closed as "fixed".

Like 16 Jun 2023 at 18:59 | Open on mastodon.social

3 comments

mcc

So I'm sitting here trying to figure out how to tell if a particular app is running in Wayland or XWayland.

This is the answer I get off Stack Overflow. I'm thinking… No. No, that's too silly. It can't be the best way.

I keep researching. It's the best way.

You run xeyes.

Wayland has security that keeps windows from knowing about mouse events in other windows. XWayland doesn't.

Xeyes will track your cursor whenever you're over an XWayland window, then stop if you pass over anything else.

1 16 Jun 2023 at 19:33 | Open on mastodon.social

Dr. Quadragon ❌

@mcc I think we have a new philosophical razor in our toolbox that applies to computing:

The silliest way to do something is almost always the best one.

1 17 Jun 2023 at 3:27 | Open on mastodon.ml

Sergey Bugaev

@drq @mcc fun fact: I *think* I was the first one to come up with the idea of using xeyes for this (or at least to publish the idea) — those stack overflow answers all reference my old post on Medium

17 Jun 2023 at 6:02 | Open on floss.social