When should we expect the baseline mesa-vulkan-drivers to get that patch
for all users of the regular repository? Just so our support agents know
what to tell affected Ubuntu users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Here's what we ended up shipping in our Steam package:
# Valve USB devices
SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0666"
# Steam Controller udev write access
KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess"
# Valve HID devices over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="28de"
Ubuntu users can install Steam without ever installing our package, so I
don't recommend doing that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498655
Title:
Steam Controller support: need read-
If you don't include support for these two PIDs, firmware updates will
not work properly:
D0G_BOOTLOADER_PID = 0x1002,
D0GGLE_BOOTLOADER_PID = 0x1042,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
I believe the second line of the rule Marc attached might be obsolete;
either way, it isn't relevant to the scope of this issue.
Attached a dump of the udev database with both a wired controller and a
wireless receiver for the controller connected.
I'm a little nervous about creating a rule based
It should be enough. Was that always the case in Ubuntu or a recent
change?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498658
Title:
Steam Controller support: need read-write access to /dev/uinp
It also doesn't seem to be the case for me on Ubuntu 15.04:
pgriffais@spaceport:/etc/udev/rules.d$ getfacl /dev/uinput
getfacl: Removing leading '/' from absolute path names
# file: dev/uinput
# owner: root
# group: root
user::rw-
group::rw-
other::---
--
You received this bug notification beca
Public bug reported:
The Steam Controller is about to ship; for native controller support
through the SteamWorks API, keyboard emulation, mouse emulation, having
access to the regular device nodes is enough, but to emulate a game
controller that applications can use through SDL, the user that runs
Public bug reported:
The Steam Controller is about to roll out; for the Steam Controller to
be supported properly by the Steam Client, it needs to be able to read
and write to HID device nodes that have the Valve USB vendor ID. In our
own Steam package 'steam-launcher' [1], this is achieved by a u
