Is Wayland matured on Ubuntu

On Ubuntu 22.04, for the sake of Waydroid, I gave Wayland a try. Without knowledge of the root causes of the following issues, I'd just hold on for a while before switching. 

1. Chrome/VS Code fonts are blurry, once display scaling is enabled. 
2. Chrome and Prospect Mail blink often during rendering. 
3. Laggy mouse/windows dragging sometimes.

Is it caused by Nvidia GPU compatibility? 

Ubuntu tools to use outlook

1. Evolution needs ews plugin installed to use outlook.com emails for enterprises 2. https://github.com/abraunegg/onedrive, deb installed from Suse build repo works great.

Ubuntu and Bluetooth Call

Here is a note for Ubuntu install. Bluetooth A2DP and HDP modes were always messed up by default, i.e., I can't really use Bluetooth microphone to make teams/zoom call. Seems replacing PulseAudio with Pipewire/wireplumber solve the problem smoothly. Refer to here.

Ludashi scores

Didn't know Huawei Mate30 is so powerful, almost same with Lenovo AMD 5600G Desktop.

Slow Ubuntu Bootup Troubleshooting

To analyze the reasons slowing down Ubuntu bootup, please use systemd-analyze cmd. 

systemd-analyze time
Startup finished in 5.027s (kernel) + 11.220s (userspace) = 16.247s
graphical.target reached after 11.194s in userspace
To sort modules by time taken during boot, use
systemd-analyze blame
We can see snap modules took quite long to load. But snap are loading in parallel and doesn't block others. We can see critical path:
systemd-analyze critical-chain
graphical.target @11.194s
For me, removing a USB card reader helps, due to BIOS/UEFI?

docker compose to remote host

# setup

ssh -nNT -L /tmp/socket.remote:/var/run/docker.sock user@remote.example.com &

export TUNNEL_PID=$!

export DOCKER_HOST=unix:///tmp/socket.remote

# use docker, docker-compose here

docker-compose…

# shutdown and cleanup of the socket

kill $TUNNEL_PID

rm -f /tmp/socket.remote

CLI tool to manage Ubuntu network

Seems Ubuntu@WSL2 has problem on DNS. I need to use nmtui to manual configure DNS server time to time.

Run snap in WSL2

To use snap in WSL2, we need systemd enabled, following instruction at https://github.com/diddledan/ubuntu-wsl2-systemd-script/. However after enabling systemd using the script, visual studio code can't open terminal anymore. There will be a fix. Before you receive the fix, there is a workaround, to change the last several lines of to:
else
exec /usr/bin/nsenter -t "$SYSTEMD_PID" -a /bin/login -p -f "$SUDO_USER"
fi
My MobaXterm also can't open WSL session. Not sure whether it is caused by above scripts. A workaround is to change default shell to cmd/powershell and run bash from there. To run GUI apps from WSL, we could use vcxsrv/x410 or MobaXterm. vcxsrv is more bugful though. Due to WSL is using different network interfaces, we can set DISPLAY by adding the line to ~/.bashrc: export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):0.0