Under the Linux Wayland environment, users will occasionally encounter various input method problems. Electron is one of the hardest hit areas. vscode depends on Electron and Chromium as well.

I have been using Labwc, a Wayland window manager, for a long time. At first, I used it in the Ubuntu environment of the company's computer. Later, I assembled a mini host and switched to using it under Arch. Overall, I have almost created a desktop environment that suits me, which is much more controllable than using behemoths such as Gnome and KDE directly. For example, pressing Win + Enter can pop up the terminal at any time, and Win + H can hide it. It's so cool that my efficiency has soared.

Due to a change in work, my previous Linux computer was handed over to the company. I have been using a Macbook pro in the past few weeks, and I cannot define various settings myself, so the efficiency has dropped significantly.

Since abandoning Gnome, I have been using the labwc window manager, plus some other core desktop components, to create my own desktop environment. The advantage is that you can control everything yourself, but the disadvantage is that you have to build everything yourself. This process is a bit similar to the video on Douyin where I rub my car with my hands. It is quite enjoyable and at the same time it can deepen my understanding of what a desktop environment is.

Recently working with labwc, I gradually found some small problems. I will record them here for the convenience of future generations.