VNot really unless you put them on an external drive or SD card
Ri'm installing libreoffice
Rhave you ever heard of meld, it's a diff tool
TI’m on testing currently but can’t upgrade or switch back to stable due to an issue with containers-policy.json specifying a default of insecureAcceptAnything. I assume this issue is known since it’s from 8/7, anyone know the workaround?
Ji understand that. my issues seems to be two back buttons on the LeGo are always binding to A and B. No matter if i turn back buttons off in Steam Input if change them to different buttons i get two keys registered for one button press.
ADid you have them as that in windows?
ADid you install legion go remapper
ADepends on the testing variabt
JYes i did and im dual booting. i have not
T:testing
AIt was an issue a couple days ago
AI need to know if it's the last 2-3 days
AIf you're on a build from 4 days ago that's where that bug was
A@nickname uhh why there are no users and exec in btrfs mount option in automount docs lol
AYes to? No to?
Jim attempting to go back into windows and unbind them within Legion Space to see if that works
ADid you set them to that in windows?
JYes
AAnd the factory reset did not work?
JNo
ADammit lenovo
JLMAO
TWell it’s at testing-v3.6-40.20240807.01 on the machine but my rpm-ostree is set to :testing so always pulling in the latest but obviously if it’s something in that image preventing it from working properly…yeah
Rtried and failed to set up my printer
Rnot fooling with it right now tho
Task @HikariKnight
Ti think he edited that
AThere was a bug with the policy when we turned on the update optimization
Krpm-ostree update
AIt did bit get applied
KAnd then post the log
ABut you can rebase to unverified and back
AHe posted a pic it's that
JThat fixed it. unbinding within windows. how that effects my linux partition you got me
AThe controllers are programmed
AIt stays in linuxbtoo
JAh makes sense. Thanks for all your help appreciate it.
Trpm-ostree update
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:testing
error: Preparing import: Fetching manifest: containers-policy.json specifies a default of
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:testing
error: Preparing import: Fetching manifest: containers-policy.json specifies a default of
insecureAcceptAnything; refusing usageKYep, you'll need to manually edit a file to fix that
AWell that's why testing is testing lmao
KMain was never affected, only testing
AJust rebase to unverified and back
KI'll get you the file you need soon
KThat might also work
AAnd you'll get the new policy
TI get the same on rebase
TSadly
A@Kyle Gospo if you find out why initramfs changes hash when you rebuild the docker image you can drop another 100mb
TYeah that’s why it’s testing, I don’t mind. I noticed it was continually trying to update from Steam and then I was like ok I better go look.
