I also experience this issue on Manjaro Linux 21.2rc with SC connected via BLE using both normal and beta branch of Steam (as of 25.12.2021). Funnily enough it only happens when you connect controller for the first time after starting Steam. After reconnecting it works just fine.
After reconnecting it works just fine.
Turning the controller on, then off, then on again also works. (guide_button -> guide_button + Y -> guide_button).
I've found that this issue also affects DualSence controllers so it's neither ubuntu nor SC specific (it might also affect other controller if not all of them). You might miss it if you have hid-playstation module loaded (which is automatically loaded on newer kernels e.g. 5.15 when you connect DualSense controller)
It no longer happens to me with the newest beta branch (1643850988).
It doesn't happen to me anymore either after upgrading.
Closing per the last couple comments.
Nothing extracted yet.
Your system information
Using steam controller with the wireless dongle and default desktop configuration layout (recommended one)
Please describe your issue in as much detail as possible:
Expected behavior: when launching steam client, desktop configuration should be loaded for steam controller.
Actual behavior: when launching steam client, the steam controller's triggers (mouseclicks) stop working. Limiting the functionality of the controller.
To correctly load the configuration a regular mouse needs to be plugged in and, on the gui, click on steam -> settings -> controller -> desktop configuration -> done (sometimes several times). After this the layout loads correctly, but it needs to be redone every time the steam client is launched.
The problem doesn't occur when booting from a windows partition on the same system.
Steps for reproducing this issue: