The problem is not caused by mono kernel. Just because AMDGPU driver was developed in mono style. i.e. they include the code of all generations in one driver. In monolithic kernel, the developer can develop drivers with "micro" style. e.g. Intel's GPU driver doesn't use mono style, they created a new driver when they changed GPU hardware architecture.
Monolithic kernel is a concept about address space. If all parts of a kernel are running in the same address space, this is a monolithic kernel, otherwise it's a micro kernel.
This problem is about how to split parts, but not how to place parts in memory.
In my opinion, that's because X11 lacks proper abstract for many things like screenshot, screencast, color managerment and etc, so the applications have to use many X11 implementation details to implement these features. It leads to high-coupling code with X11 so move their code to wayland and ensuring it works correctly and is consistent with the old behavior is difficult.
That may be because the hostname can't be resolved.
https://forum.suse.org.cn/t/topic/12280 (Chinese)
https://bugzilla.mozilla.org/show_bug.cgi?id=1296836 (upstream report)
systemd has removed split-usr and unmerged-usr supports since v255.
They doesn't use normal beta channel, and publish a new application named Bitwarden Beta.
https://play.google.com/store/apps/details?id=com.x8bit.bitwarden.beta
Yeah. Bitwarden developed a new android client written by Kotlin to replace old C# client. This new client is in beta testing currently. The old client supports both PascalCase and camelCase but the new client only supports camelCase. And Vaultwarden use PascalCase now, so it's incompatible with new Android client.
So use Fcitx 5 Android instead. It's a open source IME application without requesting any permission except Notification, especially without network permission.
https://github.com/fcitx5-android/fcitx5-android
Hope this Pull Request could be merged soon so I can use it with new Bitwarden native Android client.
More common word in Chinese is 自制 zì zhì. 土法 focuses on "easy to implement with simple tool and material" but 自制 focuses on "do it by yourself".
I use Yubikey 5 NFC and Canokey Pigeon, both works out of box on Linux.
I don't think Sidebery is a great implementation unless the developers fix this bug. It can be reproduced stably and is important for users who opened many tabs and keep them between session.
It's better to integrate Tree Style Tab addon instead. It's not a good idea to re-implement a function which already has a great implementation...
Konsole, because I can use it in editor(Kate), file manager(Dolphin), IDE(KDevelop), standalone window and Quake style window.
Maybe you can do both: physical USIM card, but with eSIM functions. So you can move your profile from one phone to another just by plug out and plug in, and install many profiles on one phone and switch between them. There are some products can do it, such as eSIM.me, esim.5ber.com or https://github.com/estkme-group .
Use a git repo and stow tool. For updating, you only need run git pull (and stow if you create config for a new software). If you modify some config, just git add && git commit && git push.
With this way, you can also record change history of your config.
Oh, my bad. But OpenGL ES 3.1 and Vulkan 1.2 is also not suitable to 2023. Hope the developers can make driver support Vulkan 1.3.
