Piero

Results 14 comments of Piero

Hello, I'm using Tuxedo OS (Ubuntu 22.04), and if I use my terminal to connect to a Ubuntu VM with: ssh -X [email protected] when I launch xclock I got this:...

Ok, that's a [known issue](https://github.com/flathub/com.valvesoftware.Steam.Utility.steamtinkerlaunch/issues/110), my bad.

I have not understood, sorry. I closed Steam. Now, I removed SteamTinkerLaunch and ProtonUp-QT. Then, I reinstalled Proton-Up-Qt from FlatHub. Then, from a terminal, I run: flatpak run net.davidotek.pupgui2 ```ProtonUp-Qt...

Hello, I've ... removed Steam and ProtonUp-Qt. I've switched to English on my Laptop. I've installed Steam and ProtonUp-Qt again. I've installed everything from Flatpak. This is what I get:...

Wait, there's more. I've tried to enable via Gnome Software Boxtron: ![Boxtron1](https://github.com/DavidoTek/ProtonUp-Qt/assets/82404704/91aa04fd-694a-4e52-b945-347cebebf74c) The result in Steam: ![Boxtron2](https://github.com/DavidoTek/ProtonUp-Qt/assets/82404704/b06f2e8c-dc00-4a7e-9eea-13d8dca96543) So, I did the same with SteamTinkerLaunch: ![SteamTinkerLaunch1](https://github.com/DavidoTek/ProtonUp-Qt/assets/82404704/64a97358-d35f-4c8a-8025-4dfb0ac7934f) Sigh, the result: ![SteamTinkerLaunch2](https://github.com/DavidoTek/ProtonUp-Qt/assets/82404704/51224c66-80da-491f-bd25-a00cc282091f)

I installed the flatpacks from Gnome Software which prevents me from going to flathub and installing from there. I understand the difference, sure.

I installed from flathub (via Gnome Software) Steam and ProtonUp-Qt and SteamTinkerLaunch, too.

> ProtonUp-Qt currently only supports installing SteamTinkerLaunch if the native (e.g. .deb/AUR) version of Steam is installed, but not if Steam is installed via Flatpak. What? Yesterday, I installed it...

That's incredible. I used Proton to install STL to play in multiplayer with BeamNG.Drive with my son. I tried to use Wine, then I followed [this](https://forum.beammp.com/t/linux-setup-beamng-mp-proton-with-steamtinkerlaunch/688297), but I need to...

So, the issue is still there with the latest Authentik version, 2024.6.0. I used the link from @pythonius21, but I have problems with Websocket "enabled" applications. I'm unable to understand...