i didnt blame bazzite, i did indeed blame the installer 🤨
i didnt blame bazzite, i did indeed blame the installer 
Pkde nvidia
Hoh right, forgot there is opentabletdriver in just 
my bad
my badPI clicked on the Steam shortcut on the desktop, and nothing happened
Htry run
bazzite-steam from the terminal, see what that spits out and also try a killall -9 steam and then run bazzite-steam again if it just takes you back to the promptPok
Hlet that finish
Pok, I was able to get into Steam, but I closed it and tried to open it again, the error persists
Hcheck and see if the desktop shortcut is correct then if opening from the terminal works each time
PRunning the command through the terminal works fine
PExec=/usr/bin/bazzite-steam %U
EYeah, same thing here.
Hok no idea why it does not work then 
PWould you have the correct link for the latest iso?
Pbecause I installed an old version and updated to this one
Bsteam honestly needs global launch options
Bgetting tired of putting
gamemoderun obs-gamecapture %command% for every single game
KYou can use system76-scheduler to remove the need for gamemoderun
Boh wait
Bhow would i do this?
KAnd then for VK capture it's actually recommended to use the environment arg which you can just add to steam itself
KThen you only need the command line option for opengl games
KBy virtue of it being enabled and existing it's already doing what game mode does automatically
KYou simply don't need it
IDoes system76-scheduler also prevent sleep while a game is running?
I wouldn't mind it, but my vram clocks aren't restored when resuming with a game running, so I have to close and restart it.
I wouldn't mind it, but my vram clocks aren't restored when resuming with a game running, so I have to close and restart it.
KIt doesn't, but you can accomplish that with other methods of course. I use espresso extension for Gnome which does that
ISo since I'm using kde, is there any downside to just continuing to use gamemoderun?
KJust have it set up to prevent sleep anytime a full screen application is open
I(And also, any ideas about the vram clocks? >_>)
KNone
Hshould not have affected it
IOh, tangentially related note. I'm muddling through moving my audio setup from kXaudio drivers on Windows (Basically a patchbay with native dsp plugins and virtual devices) to Pipewire, and it's pretty great.
I'm using Carla to host plugins and route, but some connections are not restored on reload and if Carla is minimized, I get audio dropouts. Not minimizing it works, but is there some way to launch the flatpak with the priority a game would have?
I'm using Carla to host plugins and route, but some connections are not restored on reload and if Carla is minimized, I get audio dropouts. Not minimizing it works, but is there some way to launch the flatpak with the priority a game would have?
PI reinstalled using a more current version, it solved the problem
Hodd
Hglad it works though
JTo follow up on this issue of Prompt not showing any containers on initial start-up, on a fresh reboot of bazzite-deck-gnome:testing, I opened Prompt and saw no containers listed. I closed it and opened it again, still no containers listed. I ran
podman ps --all on the command line, then closed it and opened it again, and now there are containers listed.
FWhat's the difference between espresso & caffeine in usage?
KMakes sense, this works for me but I have services that run in Distrobox on boot, might need to make a service to ensure podman starts at boot
Hobviously will need the same on kde
A@KyleGospo @nickname thanks for the help the other day, my laptop is been great so far, fresh windows install and linux really makes shit hardware like intel and nvidia shine
Pthere are a lot of us. none of my issues are actually due to the distro, but rather vaapi ffmpeg + amdgpu still being borked
Jit would be useful to file this bug with prompt, it's annoying to have to start up a container or interact with it instead of just entering it
JI'm unsure if it happens when installed as a Flatpak versus a hosted binary like it is in bazzite.
JI have the same problem in the flatpak
JI'll trace it more before I file an issue on the Prompt gitlab. I want to understand why the
podman ps that's executed by prompt-agent doesn't work.JAside from this minor issue, actually using Prompt has been a great improvement to the QoL with using Silverblue/ublue/bazzite. I can drop some of the scripts I was using to launch Terminals that start in different containers and it's much less of a hassle.
Jcan you add them to the thread on discourse so we can have them handy? links would be awesome so people can check it out
Jalso if someone bothered to script something up it might be worth just having prompt do it
Tprobably not no. especially if you're on
latest after updatingTdo you have integrated graphics as well as a dedicated GPU?
