I can't make gamemode run on the bazzitte-arch distrobox, any ideas why this could be?
I can't make gamemode run on the bazzitte-arch distrobox, any ideas why this could be?
Tferal's game mode or gamescope-session game mode?
Jferal's
Talright.. im not sure if you added it and did all the steps in the container
Tlet me check something real quick
JI installed it myself because it didn't come with the distrobox
Tdid you install it in the container?
Jyes
Jand also on the host just in case
Jafter seeing that it didn't work
JI can't run gamescope either btw xD
Twhat GPU do you have?
Tidk if that matters if the container works in general
Tim not too sure. this is kyle's project. maybe open an issue in the github issue tracker or ask directly in #
bazzite or #bazzite-help but specify it's the bazzite-arch container
bazzite or #bazzite-help but specify it's the bazzite-arch containerTbazzite doesnt really use this container anymore
Twe have those packages as part of the image now
Tbut i understand it's still maintained for other OSes
Ti just realized this was #
ublue-dev (sorry everyone)
ublue-dev (sorry everyone)
Byep, do please take bazzite support questions over to #bazzite-help etc... thanks!
but no worries, it does happen
but no worries, it does happen
Jsorry, done
J@M2 so today I used the bluefin container in anger for some work stuff, just some spelunking I had to do in git, etc.
Jand I'm like, shocked at how much better this is for people than when I started out. The new terminal with a theme you like, all your stuff ready to go, knowing you can pull any container on the internet and just get what you want.
Jand it's all nice and managed for me
J@M2 what are the oneshots for in the toolboxes repo
JI found something and I'm wondering if I've come to the same conclusion as you
MThe one-shots are just the generic use a distrobox assemble file instead of a quadlet
MThat wolfi might become my go to container if they keep these updates going?
Jyes, I recently have come to this conclusion.
JBefore I was like "yeah, maybe? probably?"
Jnow I'm like, yep.
JAnyway, there's a setting in distrobox.ini:
start_now=trueJI turned that on and what it does is run the extra packages stuff too
MCheck the ini files. I have that there
Jah ok
Jso in practice, if the machine is running that'll fire off once a night
MIt does a distrobox enter immediately but exits once done with no login shell. That's the only pain for it right now
MIf you want it to fire once a night yeah. Just have a systemd timer instead of an install section
Jthat seems better than the "I can't use my terminal for the first 3 minutes on boot" part we had before right?
MOh yes.
MBasically hide ir
JI was thinking of just doing "add a just assemble to ublue-os's steps"
Jok y ini looks like this but I have pull=true
Jif it's set to false how does it update?
Jbut like I think we can just ship a config for it
MYou have to manually pull the new image.
Here's what I'm thinking.
That will attempt to pull new image if available. Then assemble. Assemble can be set to pull=false but still get new image.
Enters container to fire off the relink
Here's what I'm thinking.
That will attempt to pull new image if available. Then assemble. Assemble can be set to pull=false but still get new image.
Enters container to fire off the relink
JI now fully understand!
Hwhat i have done for the distrobox refactor, i made 2 ini files
1 for generic distro boxes
1 for applications (brew, obs, etc)
1 for generic distro boxes
1 for applications (brew, obs, etc)
JYes! Let's do this!
KAnyone fairly well versed in dbus?
J@M2 yeah I think we should just do this because even we didn't need to link we'd need all this scaffolding anyway, so might as well set it up and then we'll be better off in the long term
Jaka, let's not block on brew linking so that we can get people playing with them for as long as we can.