All of lore.kernel.org
 help / color / mirror / Atom feed
From: John <zendhetmij@gmail.com>
To: linux-input@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 84921] Logitech Cordless Rumblepad II navigates up until a button is pressed
Date: Sun, 21 Sep 2014 16:53:24 +0200	[thread overview]
Message-ID: <541EE664.5030605@gmail.com> (raw)
In-Reply-To: <bug-84921-112111-Gl7DT4RsEZ@https.bugzilla.kernel.org/>

Hi, I noticed a bug in the drivers of the 'Logitech cordless rumblepad 2' controllers.

When starting SteamOS (debian based) and running steam both my controllers keep navigating up. This disappears when on all connected controllers a button is pressed. Probably because at this moment the controller connects to the receiver and takes over input from the controller. The default settings before getting any controller input seems to be 'navigate up'.

* Expected behaviour
Receiver gives no output to computer until any input from  with controller received

Tested on different setups:
Steam + SteamOS has Bug
Steam + Ubuntu 14.04 has the same bug.
Steam + windows 8 does not give this bug.

Please let me know if there are any questions.


On 21-09-14 16:31, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=84921
>
> --- Comment #1 from Greg Kroah-Hartman <greg@kroah.com> ---
> On Sun, Sep 21, 2014 at 01:51:30PM +0000, bugzilla-daemon@bugzilla.kernel.org
> wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=84921
>>
>>              Bug ID: 84921
>>             Summary: Logitech Cordless Rumblepad II navigates up until a
>>                      button is pressed
> Please send this to the linux-input@vger.kernel.org mailing list.
>


           reply	other threads:[~2014-09-21 14:53 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-84921-112111-Gl7DT4RsEZ@https.bugzilla.kernel.org/>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=541EE664.5030605@gmail.com \
    --to=zendhetmij@gmail.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-input@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.