hello. where’s the documentations how to use the containers? i was looking a bit in the possiblities and came to borders, podman does just temporal containers, gemini did confirm me that. toolbox would eventually work but how do i make a aurora stable release same releaseversion as the host in toolbox? when i start making a toolbox container it makes me a fedora 40 container. it’s not that bad on my Intel Arc A750 OC R7 9700X to have fedora core in fedora kinoite, but fedora 40 runs dnf not dnf5. i have some problems with that. how do i use ephermal and what services run with it? podman seems to have problems when i want to use ephermal, toolbox does work, but fedora 40 does have problems with it. also how is the virtualisation problem solved on aurora 41 kinoite with fedora 40 core toolbox and ephermal, i have tons of JS offscreen problems, some system instructions just vanish in the terminal. is it possible to configure the toolbox, i need a configuration which improves directx12 systems to work and another toolbox which supports intel arc drivers as for bottles. bottles doesn’t really run and crashes on exe installations
also what’s the best solution to get xdg and xcb system wide functional? with ephermal use case and not??
java included in the equasion
This is like 28 questions with very few details. lol
You mention your GPU, and bottles, and DirectX12, so it sounds like it’s gaming related.
Maybe you should start with Bazzite, which is all set up for gaming, instead of Aurora, and go from there.
yeah that’s a bad boomer recommendation, that doesn’t help anywhere. i talked about JS offscreen problems. the issue problematic on that is very specific, that’s a real and dangerous problem. but that’s not wrong, bazzite has better container and toolbox support than other distributions. in the case virtualisationprocesses and communication can’t be bugfixed and configured right with read access rights settings and the virtualisation helper systems crash on portation and transfer of administration rights, it’s definetly true that bazzit has a higher chance that toolbox does work on configuration and transmission layer better than other systems, which helps massively with the DirectX12 problematic the systems have from pinging to wine directly, which uses wine staging sometimes, which is a 64bit system, which compat asks for synchronisation data on moz 32bit debuglevel while the libpthread and glib bibliothek is sending empty JS containers which communicate with the display. it’s problematic when that happens before the proton container is asked and the game already started in wine, prepared for proton which runs a proton container and runs before, without soda converter in empty and false settings since proton usually does talk to wine stable or wine core. but i didn’t found out yet to correct the wine call ups already. setting wine from wine staging to wine wow64 would help, but lots of processors are incompatible to compute wine wow64, also another JS problem. and that doesn’t change the read access write problems between program, proton container, wine and the administration sets between the linux kernel and all these..
Find somewhere else to get help.