Device doesn't Authorize

[V3-lo]

Description

I tried using ALVR on Linux (Manjaro) using a USB cable that used to work perfectly on Windows with Oculus Link, but when I tried it on Linux with ALVR, the device didn't want to Authorize.

General Troubleshooting

I have tried multiple things, and I did find somewhat of a solution:
What didn't work: I tried using the nightly and had the same problem, reenabling developer settings, disabling USB debugging and revoking USB authorizations.
I wanted to see if it was a problem with ALVR or with the device, so I tried using Sidequest to see if it would show the authorization request and I was surprised that it did, but I wanted to see if it would happen again, so I restart my computer and the quest, and then it stopped working, and Sidequest gave me an error that something went wrong as it couldn't get the authorizations even though I did always allowed,

The solution:
After many tests, I found out that you shouldn't always allow it and that you need to try to install ALVR from the computer and it will fail after that, open Sidequest, and it will send the authorization request and then you will be able to install it from the computer and connect to your computer using a cable

Environment

VR Device - Quest 2 running the latest version
Computer - Manjaro Linux

Hardware

I have a Pastebin for my hardware already
https://pastebin.com/HUrNxDTM

Installation

ALVR Version:
V21.0.0.dev01+nightly.2025.01.18-17 (18 and 17)
V20.12.0

ALVR Settings File:
I'm not sure where the file is supposed to be, but I cleared the settings and turned on the wired connection.

SteamVR Version:
version 2.8.8

Install Type:
This is the link to the version I'm using https://github.com/alvr-org/ALVR/releases/latest/download/alvr_launcher_linux.tar.gz

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):
PRETTY_NAME="Manjaro Linux"

[The-personified-devil]

I really don't know how that would happen (adb does the authorization internally, alvr has no hand in it), but when I've had adb act up restarting and replugging stuff has always fixed it.