So there's definitely something going on in the kernel here. Note that the MSC_SCAN event is missing from this release event but not from the ones that look correct. This is where your events come from, key repeat triggering for 88 seconds. at 89.5 seconds into the recording, volume down was released, ~88 seconds after the volume down press events. The translation here is: at 1.04 seconds into the recording volume down was pressed (100ms after the previous event). The last line of attachment 1259204 indicates that the button may be stuck in the down position. Headset and USB adapter have the latest available firmware.ĭevice: Logitech Logitech G933 Gaming Wireless Headset On-headset volume scroll should work all the time, never scroll to minimum/maximum volume and be ideally in sync with system volume. Wait few seconds or change volume using on-headset scroll Version-Release number of selected component (if applicable):Ģ. This happens even if don't scroll at all, but volume won't change in that case to min/max. You can change volume using standard system tools or headset (but values get desync at this point) and you can control volume on headset and system separately. Few seconds later, if you are still scrolling, volume gets scrolled to minimum/maximum (depends on which direction you are scrolling at the moment) and stops working. Right after connecting the headset, volume setting using headset scroll is working perfectly and in-sync with system volume control. Only Volume control should be handled at the moment on Linux (headset is detected as stereo only, but that's for other bug report). Logitech G933 Gaming Wireless Headset has scroll for volume, 7.1 Surround/Stereo switch and few more.
0 Comments
Leave a Reply. |