Qualcomm uses their own Adreno GPUs, they are different from ARM’s Mali which are even worse.

That’s the problem of most general-use languages out there, including “safe” ones like Java or Go. They all require manual synchronization for shared mutable state.

It’s not ready yet.

The protocol for apps/games to make use of it is not yet finalized.

Well it could be that the application uses some Qt functionality that does nothing on Wayland, and the developer may not be aware of that. Though it could be challenging to fix this in a cross-platform way.

BTW those warnings about requestActivate should go away when those apps migrate to Qt 6.

You can report it to developers of an app which prints these warnings. It could be a bug where some functionality doesn’t work as expected on Wayland.

It’s the standard location for all apps (actually it can be overridden by environment variables and ~/.config is the default value). However like many things in the Linux world it’s not enforced. Some apps (especially console utilities) don’t respect it but most use it.

What exactly do you expect users to do when they see “WARNING: what you are doing is unsafe” message? Cause the only outcome I can think of is that they won’t install themes at all.

There is a checkbox with a very confusing name in the task manager applet’s settings that does just that. I can’t remember its name just now (something about separated launchers. It’s “Combine into single button”. Nope, it’s “Keep launchers separate” and it’s indeed needs restart).

Some distros (Fedora at least) have debuginfod integration,meaning that gdb will automatically download debuginfo files. The downside is that it will take a while for download to finish (for the first time at least) since it gets symbols for all linked and loaded libraries recursively, and it will take a few gigabytes in ~/.cache.

It’s arch so it will probably require some manual interaction. Or maybe not. You should always check the arch website before running pacman -Syu.