Document the usage of MOZ_ENABLE_WAYLAND=0 in README to use systray-x under Wayland #200
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since version 128, Thunderbird uses Wayland by default. To get the
systray-x
addon working properly under Arch on Sway with Thunderbird 128, I had to useenv MOZ_ENABLE_WAYLAND=0 thunderbird
(instead ofenv GDK_BACKEND=x11 thunderbird
, see this comment).To be honest, it seems DE/Compositor specific (somehow). For instance,
env GDK_BACKEND=x11 thunderbird
still works in KDE, but doesn't seem to work anymore in Sway (with Thunderbird 128+ at least, it was working fine with previous version of Thunderbird though).Regardless, I think it doesn't hurt documenting
env MOZ_ENABLE_WAYLAND=0 thunderbird
in the README in case people face the same issue I got on Sway with Thunderbird 128+.I also removed the
AUR
mention for the "Alternative install" in the Arch section as it is not about an AUR package but an official Arch package from the [extra] repository.