Have you tried installing your DAW inside the distrobox?
Have you tried installing your DAW inside the distrobox?
Lonce i DO plug them in, they look like this (seperate screenshot):
Lnothing changed
Lyes, my DAW (reaper) is in the arch distrobox
Lhere is what it shows (using jack)
Laand when trying to change it to alsa it CRASHED
Lthis is great
Li love linux :))):):))):):):):)::)):)):)))
CNot exclusive to Linux unfortunately
Lwdym
CAudio production software tends to crash when changing interface on every OS I'm pretty sure
RThat is some unhinged shit
CI didn't even read it, just thought the title was funny
Lanyways after running
reaper -newinst i get this for devices under alsa:
CHave you searched for other people using your hardware in Linux? If they could do it successfully or not
Lhere's the most insane thing
Lthis worked before i did a reinstall
COf what?
CBazzite to Bazzite?
Lyeah
Lwent from gnome to kde to try to fix some problems
Lit did Not Work
CWhat problems?
Limma be real i don't even remembver
CIf it worked before the reinstall, it might just be something to do with a newer image
CUniversal Blue
Yes it is true for all of them, however I mostly focus on documentation on the Bazzite image which is why it’s here. Desktop images of Bazzite follow the same automatic update style that the main images follow. However, there’s also the -deck images that do not follow this which is why I wanted to differentiate between them. As for pinning, w...
CYou could try rolling back to any image from the last 90 days
CIf you look at the output of
fastfetch you'll have your install(spawn) dateCYou could try a rollback to some number of days before then
Lunrelated but why is there a blinking red unlocked icon next to 
bazzite-deck-gnome:stable CThat means it's an unsigned image I believe
CYou can fix that by rebasing to a signed image
Lwhat does that mean
Lis that secure boot stuff?
CI don't think so, just whether the image itself is signed or not
Lstill confused lol
KIt's not secure boot stuff, I have this, and secure boot is very off.
KLock means you're on a signed image
Kmakes sense.
CI believe you can just run
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:stableCIs that the right command?
Hit means you are on the image you use to rebase from normal fedora to ublue with, as fedora does not have our signing keys.
now that you have our key you can rebase again to our signed image
get the image link and replace the first part before
now that you have our key you can rebase again to our signed image
rpm-ostree status -bget the image link and replace the first part before
ghcr withostree-image-signed:docker://Hbeing on the signed image means the image you get is verified to have come from us.
KIs that.. Are you trying to mc with a controller
Lweird, could it possibly be because i rebased from bazzite to bazzite? lol
LYES
Lthe steam controller is incredible for it tbh
CDid you rebase from GNOME to KDE?
KImmoral.
COr vice-versa?
Hyou grabbed the rebase command from the website that assumes youre on fedoras image (not ublue fedora)
