if it is a problem we can work on it, hiding should be possible
if it is a problem we can work on it, hiding should be possible
Hwell i dont own a device which require hhd, but i should be able to fire up RR later today to try in general
Hi know the devs and ceo of the studio so i could probably just pull some strings too and have it fixed in their client if lucky
Ano, its hhd's problem
Ano worries, we just need to hide the usb controller cleanly
Ait will just take some testing...
Aif you know some python and have an xbox controller you can help too
Hwell first we need to know if RR even requires a fix to begin with. devs are controller fanatics so it might even be a non issue
Aif they are fanatics it probably is
Ai assumed the games would be dumb and rely on the kernel for xpad devices, which are the only ones I needed for now
Ai did not expect that they would fish out the xpad usb nodes and read them instead
Hi will ask them if they use libusb for the linux client
Hi know they do on the windows client
Alibusb is not necessarily the problem, plenty of games use libusb. It's whether they decide to use it for xinput controllers too
Hhmm
Hstill will be easier for me to ask them about that
Ayou can test it on your pc by doing chmod 000 the controller event node and seeing if it still works after that in the game
Aor removing it
Dthe default firewalld rules are a bit too permissive if the port range allowed is 1025-65535 for both tcp and udp isn't it? is this how it is directly from RH?
D
Hfedora default, we do not touch that
Dkk ill leave it be
Hessentially we use fedora default on everything that does not impact whatever bazzite/bluefin tries to accomplish 
Di found a reddit post that explains the reason for these default values: https://www.reddit.com/r/Fedora/comments/mv2y01/default_firewall_configuration_question/
Adefault rules on other distros: no firewall
A40000something + is upnp should be open
Dwell... to be fair, distros like endeavouros come with firewall, with strict rules out of the box, was used to having to mess with that
RI'm working on adding 'tuxedo-drivers' to akmods and I have a question - what does 'rpm-ostree cliwrap install-to-root /' line achieve in detail (from build-prep.sh file)? I have a problem in uderstanding its purpose.
Di found a better way to do this
Ntell me
Dlmao wait... its not working 
i thought it was
i thought it wasDi installed toolbox on the host, since all tools get installed in the home directory and automatically added to the PATH, i thought why not just create an ubuntu distrobox, install dotnet, java, whatever on that, and then export rider from within the container again
Dsomething like this (my ubuntu box is named dev-env)
Dnot sure why it isn't working
NDid you install Xorg/X11 in your container?
Doh that's absolutely necessary? D:
Nyeah lmao, otherwise java doesn't know how to output
Doh man you mean this entire time jetbrains apps have been running under xwayland? i never checked
NYeah, they're working on Wayland Support, but right now all Java GUI Apps are running in Xwayland
Dah kk then otherwise your method is the only way haha nvm then
Dbtw why do you have separate home directory for your javabox environment? what's the benefit?
VNot Niklas and not for Java, but I do it with some distroboxes so it's easy to keep a track of the files that they use and it's easy to nuke it all if it goes wrong. Once you start mixing and matching your home directory it can get a little hard to keep track of.
Dah good point...
ROk wifi issue still happening
RAnd now it won't even see my controller
REverything else is going great
ROh and that black screen on boot thing you guys already know
RAnd that weird brightness issue, but that's not really that big a problem
Amaybe i know about that
Ago to gnome power settings and see if there is automatic brightness
Areminder that we need a udev to nuke that on the go too
