steam-devices
distrobox
steam-devices | distrobox | |
---|---|---|
24 | 402 | |
132 | 8,976 | |
3.8% | - | |
0.9 | 9.6 | |
3 months ago | 4 days ago | |
Shell | ||
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
steam-devices
-
What is the point of Steam Linux runtime if in a clean opensuse install XCOM2, Dota Underlords or Artifact for example the game not work even using that
if you mean this ( https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules ) in /etc/udev/rules.d , yes i did
- Silverblue and Gaming!
-
how to give a app (like Steam) access to /dev/hidraw* devices?
Create an udev rule for the device, you can copy the rule for your device from here.
-
Proton Controller Support or just Spelunky?
I am attempting to play Spelunky with a controller but I am not having any luck. Spelunky has a platinum rating on protondb and runs as expected. I am in a flatpak and I did install the udev rules from valve if any of that makes a difference. My controller works fine in native games.
-
How has your experience with Silverblue/Kinoite been?
I solved the problem by copying the 60-steam-input.rules file to the folder: /etc/udev/rules.d
-
how to install controller drivers / steam-devices package?
this is their Github: https://github.com/ValveSoftware/steam-devices
-
Writing udev rule for nintendo switch pro controller
steam maintains udev rules for controllers that might help: https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules
-
PS4 Fightstick not recognized by Fedora/Steam
Here is my open PR for the hori alpha for reference: https://github.com/ValveSoftware/steam-devices/pull/42/files
-
Anyone tried gaming/development on silverblue?
To use a controller with the Steam flatpak, you need to layer the steam-devices package from RPM Fusion, or download the udev rules from upstream and install them to /etc/udev/rules.d/ (which is what I did).
-
An X11 Apologist Tries Wayland
> The effort you need to go through to actually use these depends on how your distribution handles the file permissions of /dev/uinput. Some of them have it as root:input, in which case you just need to usermod -a -G input and then relog to get it working. Others have it as root:root so you either need to go do some reconfigurations to change its permissions or live with running the software using it as root.
There's a trick to that. The TL;DR is "install the steam-devices package or similar" (https://github.com/ValveSoftware/steam-devices/), which adds the following udev rule (and others, but this is the relevant one):
# Steam Controller udev write access
distrobox
-
Windows 11 now comes with its own adware
Regarding the stability issue on a dev machine - you may be interested in playing with one of the immutable-os distros, such as SilverBlue (fedora based).
The high-level take-away is you can't break your actual OS since it's root filesystem is read-only, and you use "pet" containers (on docker, podman, whatever) to do your work in. Applications are either sandboxed via Flatpak, or installed/run inside your pet containers. If your pet container dies, you cry about it for a moment, and when you're ready you get a new one - your actual os and other containers remain unaffected.
I use distrobox[1] to create/run the pet containers.
[1] https://github.com/89luca89/distrobox
-
Tools for Linux Distro Hoppers
Distrobox is a tool that enables us to try Linux distro CLI, including their package manager. This requires a containerization tool (e.g., Docker). In Windows, this can be achieved using WSL (Windows Subsystem for Linux)
- Distrobox: Use any Linux distribution inside your terminal
-
Fedora Atomic Desktops
I use containerized versions of things, ubuntu and chainguard images mostly.
You can always create containers with init if that's how you want to do that though. Some distros publish images that come that way: https://github.com/89luca89/distrobox/blob/main/docs/useful_...
-
Raspberry Pi is manufacturing 70K Raspberry Pi 5s per week
https://news.ycombinator.com/item?id=38505448 ... https://github.com/89luca89/distrobox/blob/main/docs/useful_...
-
Operating System?
Yes, you can do that but I've seen others use something like distrobox to run linux inside of SteamOS: https://github.com/89luca89/distrobox/blob/main/docs/posts/steamdeck_guide.md
-
How much will I screw up my system after installing Merkuro Calendar (KDE Akonadi application), formerly called Kalendar, on GNOME?
For such cases you might use something like this: https://github.com/89luca89/distrobox
-
Battery consumption of using remote development with WSL2?
Btw #3: Depending on what the user is trying to accomplish, e.g. maybe to make WSL(2) itself more of a "subsystem" than a "container engine", using something like Distrobox or nsbox.dev can be a good idea (along with Docker or Podman in Distrobox's case; the other one uses systemd-nspawn).
-
Cannot run containers with Distrobox
1. Find here in "Containers Distros" section the distro image that you want to install ("Toolbox" versions are better because they are configured for Distrobox) and get it URL: https://distrobox.it/compatibility/#containers-distros 2. Use that URL to create Distrobox: distrobox create -i registry.fedoraproject.org/fedora-toolbox:39 -n fedora_1_39 3. Enter Distrobox fedora_1_39: distrobox enter fedora_1_39 4. You are already in Distrobox console. Look at the name in console, it should be include the container name. 5. To exit Distrobox: exit 6. If you run: distrobox list you will see all distroboxes on the system. You will also see that distrobox that we exited is still running. 7. To stop distrobox use commands: distrobox stop fedora_1_39
- In-depth Distrobox tutorial/ or video?
What are some alternatives?
com.valvesoftware.Steam
toolbox - Tool for interactive command line environments on Linux
Simple-ArchLinux-Install-Guide - Archlinux manual and automated simple installation UEFI with GRUB,GUI,NVIDIA,AMD,User Space with all popular Desktop Environments.
wsl-distrod - Distrod is a meta-distro for WSL 2 which installs Ubuntu, Arch, Debian, Gentoo, etc. with systemd in a minute for you. Distrod also has built-in auto-start feature on Windows startup and port forwarding ability.
game-devices-udev
docker-android - Android in docker solution with noVNC supported and video recording
bluez - Main BlueZ tree
flatpak - Linux application sandboxing and distribution framework
protonup - Install and Update Proton-GE
rustdesk - An open-source remote desktop, and alternative to TeamViewer.
steam-for-linux - Issue tracking for the Steam for Linux beta client
toolbox-vscode - Toolbox Visual Studio Code integration