Anyone know how to force x11 for the bazzite for deck os? I think wayland is causing a crash in the
Anyone know how to force x11 for the bazzite for deck os? I think wayland is causing a crash in the new 7 days to die v1 release.
WX11 isn't available in the deck images, it was removed when Fedora 40 was released two months ago. Reason being is that KDE isn't supporting X11 anymore and it will fall away completely when Fedora 41 is released
TUse proton
Tif the native port doesn't like wayland
SLmao, valve is silly and used the open file dialog instead of the save file dialog when you want it export a video so you need to overwrite a file in order to get an mp4 out of it
Fsilly Valve also accidentally running rm -rf /*
WIt's weird that the Proton version running a compatibility layer meant for Windows will out preform the native port for Linux in many cases lol
Wwill there eventually be a bazzite-dx version like bluefin-dx where a bunch of dev tools are preconfigured? or am i the only one interested in that?
Li don't even know where to begin with this
Lfor some reason, when i add extest, it causes this to happen. why
Twin32 is the most stable abi on linux
TThere is but we're waiting on systemd-ext to mature
WGitHub
Similarly to Bluefin-DX, we'd like to ship DX images which come preconfigured with common game development and debugging tools. If you're a developer we'd love to hear what you might fi...
Tbetter to be an extension than another image
Wty all! 
CUsed to be an issue with extest; has been fixed since from my testing
CMaybe some regression with newer packages
Lwhat
Loh wait i'm using the latest release from dec 8
Lshould i just git clone the repo?
CThe latest release is from December 27
Loh yeah, that's all they added
L?
CYes
L
KKdoing this shit yourself is a recipe for disaster, there's a reason bazzite exists @legally defined as sound
Kplease do not ask for support for custom images in #
bazzite
bazziteKit confuses everyone and makes people thing something is broken when it isn't
Lsorry
CHe just didn't push a release to the release page, it's fixed
AI plan for bazzite upd to support extensions
AIf bazzite doesn't use them I will
ASame image with components going to separate layer sets
ASo you can stitch multiple manifests in the end from the same image
WThe advantage would be easy combining multiple extensions?
AI think that sysext will not be a good fit for oci images
AIt's meant to be used with sysupdate
AEssentially systemd ecosystem
AThe benefit is you build the image once , you upload it once, then different users pull different layers
WThat sounds very interesting. So you essentially have a checkbox list of all the features that you want and then you pull the related layers into your own system?
Ayea
Alarge image then use subset of layers
WThat would essentially enable netinstall experience on immutable OSes
Aalso enables offline ISOs that allow you to select from multiple images
Aimagine bazzite being a single 8gb image that you can ship as an offline live iso
Athen it deploys a subset of layers to the host
WYou build some really cool stuff antheas 
WI'm thinking bazzite could essentially become a gaming layer for Bluefin/Aurora
Athe problem with bazzite-upd right now is ostree-rs-ext