specifically, the back buttons are not separately bindable in Steam
specifically, the back buttons are not separately bindable in Steam
Hyeah this is because steam input offer no way to bind them, valve focuses only on the 1st party controllers with extended functionality (or its just that there is no "proper" way to remap the back buttons on other controllers without reverse engineering every single one of them, which valve wont do)
RJust to add on to this, if MTPDeck doesn't work yet, how do you guys usually back up your things from the Deck?
Hits called yafti and yes it is
TGitHub
This application is responsible for installing Flatpaks on first boot after a user finishes installation. It is intended as a replacement for custom zenity dialogs. - GitHub - ublue-os/yafti: This ...
KNot yet, I use a USB drive
KMight work next update on testing branch
RIs there an ETA on that?
ROr is it a while out? Just seeing if I should wait or not.
TDoes anyone know how to set Bluetooth to turn on automatically after switching to desktop mode from boot
VIs the bazzite loading screen supposed to be sideways?
Aif your device's display is a portrait one it will be
Ais Miraclecast (open source Miracast) installed on Bazzite out of the box?
VI thought that'd be changed for Deck
Ahm, i'm not sure what orientation the actual deck's display is. i never ran anything but steamos when i had it
VIt's a vertical display rotated in software
Vso i wanted to install bazzite on my desktop but when i try to boot from my usb (made with fedora media writer) it gives an error saying "image unsupported" and boots right back to windows
Aanyone see really slow network transfer speeds? everything says i'm connecting at 1Gbps+ wifi-wise, but i'm getting transfer speeds around 1Mbps, even to the lan (i'm on a lenovo legion go)
KNope, should be normal for you at least once everything is configured. Possible it's DeckHD related
VThat's what I was thinking
KCan always use a stock sb/Kinoite installer and then rebase
Hgo into the USB root and navigate to
that should fix the
EFI/fedora/grubx64.efiEFI/BOOT/grubx64.efiBOOTX64.EFIthat should fix the
image not supported@KyleGospo ^ thats also some workaround for you to add to your list of tricks too, as if they get that error, stock atomic fedora might also get the same issue
Ainteresting, it's working fine now. no reboot or anything. of note, this was behaving this way for all net traffic from my device, even from my server on my lan it was crawling. attended a work meeting and now i'm seeing 0.5Gbps. 
VIt was something stupid to fix tbh i just used legacy boot for the usb and it booted immediatly
Hyeah but from experience some installers will install the system in the mode the system was booted from
legacy --> bios/mbr install
uefi --> uefi install
legacy --> bios/mbr install
uefi --> uefi install
Hand lets not forget some laptops have legacy mode completely ripped out now
VI wanted to install efi mode but i couldn't for the life of it enter that efi partition on my usb
EDesktop images (sans NVIDIA, probably needs a rebuild) are updated. Deck images are not atm. Will take a closer look in about half an hour
E@KyleGospo removing kmods from an image might not be possible. We'd need something like cliwrap install-to-root but for removals (maybe it works both ways?)
KThat's fine, we can pull that out. I need to adjust which ones are installed against fsync anyway
ESounds good
Vwaydroid service nnot working
KDid you turn off SE linux?
Vset to permissive and rebooted
Vnvm it didnt change
BI want to say no. It's not something I've come across in use, or seen in a feature list.
VHow can I change the Res of waydroid/Weston?
K/etc/default
KThere's a Waydroid launcher file in thrre
KWhich holds the resolution
KAmong other things
VCool thanks :)
VWaydroid just needs a command iirc
KIt's because we also have to change the resolution of the wrapping Weston
KSo this handles that
KBetter than it being hard coded
KOr guessed from the current display config
VYeah I know, works fine tho.
VMaybe put that on the docs @nickname
VThat file already exists in the efi folder, the fedora folder however does not exist
