• Steam client version: Mar 22 2017, at 23:45:04
• Distribution: Ubuntu 16.10
• Opted into Steam client beta: No
• Have I checked for system updates: Yes

Steps for reproducing this issue:

1. Launch Steam
2. Connect the Steam Controller
3. Launch a Stream from a Windows machine

A better explanation of the issue

My Steam Controller works fine in desktop mode when Steam is running, works fine in BP, works fine when playing a native game; but when launching a Stream from my Windows machine, no input is sent through to the host. The Host shows the Controller as connected (the notification pops up, the configuration is there), but no inputs go through. While the stream is going, I can use KB+M to control the game, and I can use the Steam Controller in BP and desktop (alt-tabbing using the controller works, for example) - so it's basically just the stream that's not working.
Also, Xbox 360 controllers work with no issues.

The most important thing:

Disconnecting the controller and then reconnecting it whilst the stream is active results in ~0.5 seconds of normal behaviour, after that the controller is dead again. To reiterate: disconnecting then connecting the controller makes it work for 0.5 seconds, then it "dies" again.

Logs:

Parts of the log I thought are relevant to the issue

This is what shows up when I disconnect/connect the controller as mentioned above

What I tried already:

• Updating to 16.10 from 16.04.
• Purging Steam
• Checking udev rules
• Playing wired
  Initially I was on 16.04, and this issue appeared about 2 weeks ago. Today I tried updating to 16.10, purging all Steam related packages, then installing Steam again, but this time also installing the package "steam-devices". This rendered the controller completely dead (so the udev rules the package provides do not do a thing), so I used the rule provided in the official guide, which got me back at square one