Launchpad has imported 12 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=912859.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2013-02-19T21:07:02+00:00 Eric wrote:

I have a Plantronics savi 750-ish headset which plugs in USB and shows
up as a USB audio device.  However, when I lift the headset off of the
cradle, my mouse and gnome starting acting 'fishy'.  Some things the
left mouse button works, some things they don't.  alt+f2 doesn't work.
windows hotkey doesn't work.  cannot change between programs by clicking
other windows.  Sometimes I can click between tabs.  sometimes I can
highlight text on the focus window, but certainly no highlighting of
text on other windows.  etc.  Just fishy.  Disconnecting the headset
from USB resolves the problem.  Below you will find the xorg log and the
dmesg log of connecting, breaking, and disconnecting the device.

CONNECTING:

[ 21307.552] (II) config/udev: Adding input device Plantronics Plantronics Savi 
7xx (/dev/input/js0)
[ 21307.552] (**) Plantronics Plantronics Savi 7xx: Applying InputClass 
"anaconda-keyboard"
[ 21307.552] (II) No input driver specified, ignoring this device.
[ 21307.553] (II) This device may have been added with another device file.
[ 21307.554] (II) config/udev: Adding input device Plantronics Plantronics Savi 
7xx (/dev/input/event16)
[ 21307.554] (**) Plantronics Plantronics Savi 7xx: Applying InputClass "evdev 
keyboard catchall"
[ 21307.554] (**) Plantronics Plantronics Savi 7xx: Applying InputClass 
"anaconda-keyboard"
[ 21307.554] (II) Using input driver 'evdev' for 'Plantronics Plantronics Savi 
7xx'
[ 21307.554] (**) Plantronics Plantronics Savi 7xx: always reports core events
[ 21307.554] (**) evdev: Plantronics Plantronics Savi 7xx: Device: 
"/dev/input/event16"
[ 21307.554] (--) evdev: Plantronics Plantronics Savi 7xx: Vendor 0x47f Product 
0xac01
[ 21307.554] (--) evdev: Plantronics Plantronics Savi 7xx: Found 20 mouse 
buttons
[ 21307.554] (--) evdev: Plantronics Plantronics Savi 7xx: Found absolute axes
[ 21307.555] (--) evdev: Plantronics Plantronics Savi 7xx: Found absolute 
multitouch axes
[ 21307.555] (--) evdev: Plantronics Plantronics Savi 7xx: Found keys
[ 21307.555] (II) evdev: Plantronics Plantronics Savi 7xx: Forcing relative x/y 
axes to exist.
[ 21307.555] (II) evdev: Plantronics Plantronics Savi 7xx: Configuring as mouse
[ 21307.555] (II) evdev: Plantronics Plantronics Savi 7xx: Configuring as 
keyboard
[ 21307.555] (**) evdev: Plantronics Plantronics Savi 7xx: YAxisMapping: 
buttons 4 and 5
[ 21307.555] (**) evdev: Plantronics Plantronics Savi 7xx: EmulateWheelButton: 
4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 21307.555] (**) Option "config_info" 
"udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5.4/2-1.5.4:1.3/input/input21/event16"
[ 21307.555] (II) XINPUT: Adding extended input device "Plantronics Plantronics 
Savi 7xx" (type: KEYBOARD, id 15)
[ 21307.555] (**) Option "xkb_rules" "evdev"
[ 21307.555] (**) Option "xkb_model" "evdev"
[ 21307.556] (**) Option "xkb_layout" "us"
[ 21307.556] (**) Option "xkb_options" "grp:alt_shift_toggle"
[ 21307.556] (II) evdev: Plantronics Plantronics Savi 7xx: initialized for 
absolute axes.
[ 21307.557] (**) Plantronics Plantronics Savi 7xx: (accel) keeping 
acceleration scheme 1
[ 21307.557] (**) Plantronics Plantronics Savi 7xx: (accel) acceleration 
profile 0
[ 21307.557] (**) Plantronics Plantronics Savi 7xx: (accel) acceleration 
factor: 2.000
[ 21307.557] (**) Plantronics Plantronics Savi 7xx: (accel) acceleration 
threshold: 4


[21451.797362] usb 2-1.5.4: new full-speed USB device number 12 using ehci-pci
[21451.889021] usb 2-1.5.4: New USB device found, idVendor=047f, idProduct=ac01
[21451.889029] usb 2-1.5.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[21451.889033] usb 2-1.5.4: Product: Plantronics Savi 7xx
[21451.889037] usb 2-1.5.4: Manufacturer: Plantronics
[21451.913745] ALSA sound/usb/clock.c:237 12:1:1: cannot get freq at ep 0x4
[21451.922377] ALSA sound/usb/clock.c:237 12:2:1: cannot get freq at ep 0x84
[21451.929755] ALSA sound/usb/mixer.c:929 2:0: cannot get min/max values for 
control 2 (id 2)
[21451.929894] ALSA sound/usb/mixer.c:929 2:0: cannot get min/max values for 
control 3 (id 2)
[21451.929996] ALSA sound/usb/mixer.c:929 2:0: cannot get min/max values for 
control 5 (id 2)
[21451.937737] ALSA sound/usb/mixer.c:929 5:0: cannot get min/max values for 
control 2 (id 5)
[21452.113970] input: Plantronics Plantronics Savi 7xx as 
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5.4/2-1.5.4:1.3/input/input22
[21452.122582] hid-generic 0003:047F:AC01.000A: input,hiddev0,hidraw3: USB HID 
v1.11 Device [Plantronics Plantronics Savi 7xx] on usb-0000:00:1d.0-1.5.4/input3
[21452.335863] ALSA sound/usb/clock.c:237 12:1:1: cannot get freq at ep 0x4
[21452.339225] ALSA sound/usb/clock.c:237 12:1:1: cannot get freq at ep 0x4
[21452.350698] ALSA sound/usb/clock.c:237 12:2:1: cannot get freq at ep 0x84
[21452.353688] ALSA sound/usb/clock.c:237 12:2:1: cannot get freq at ep 0x84
[21452.445650] ALSA sound/usb/clock.c:237 12:2:1: cannot get freq at ep 0x84
[21452.448697] ALSA sound/usb/clock.c:237 12:2:1: cannot get freq at ep 0x84
[21452.469973] ALSA sound/usb/clock.c:237 12:1:1: cannot get freq at ep 0x4
[21452.472965] ALSA sound/usb/clock.c:237 12:1:1: cannot get freq at ep 0x4
[21452.521597] ALSA sound/usb/clock.c:237 12:2:1: cannot get freq at ep 0x84
[21452.524613] ALSA sound/usb/clock.c:237 12:2:1: cannot get freq at ep 0x84


BREAKING:

(EE) [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0
(EE) [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0

DISCONNECTIONG:

[ 21365.110] (II) config/udev: removing device Plantronics Plantronics Savi 7xx
[ 21365.128] (II) evdev: Plantronics Plantronics Savi 7xx: Close
[ 21365.128] (II) UnloadModule: "evdev"


[21484.337213] usb 2-1.5.4: USB disconnect, device number 12

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/20

------------------------------------------------------------------------
On 2013-02-21T23:57:30+00:00 Peter wrote:

whoah. this headset actually pretends to be a mouse?

connect the headset, then run evemu-device and evemu-record against the
/dev/input/eventX device file while reproducing the above issue and
attach it here please.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/21

------------------------------------------------------------------------
On 2013-02-26T17:09:01+00:00 Eric wrote:

so I got nothing...   looking in the Xorg.0.log I get:

[229542.305] (II) config/udev: Adding input device Plantronics
Plantronics Savi 7xx (/dev/input/event16)

so I ran:

#evemu-record /dev/input/event16

When I reproduce it just exited...   no output at all

I was simultaneously running:

# evemu-device /dev/input/event16

Which gave one line and exited:

error: could not create device: 0

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/22

------------------------------------------------------------------------
On 2013-02-26T17:12:03+00:00 Eric wrote:

Just managed to get this only running record without device at the same
time:

# evemu-record /dev/input/event16
E: 1361898674.699471 0004 0004 -6291248
E: 1361898674.699471 0001 0112 1
E: 1361898674.699471 0004 0004 -6291326
E: 1361898674.699471 0001 0113 1
E: 1361898674.699471 0004 0004 -6291328
E: 1361898674.699471 0001 0117 1
E: 1361898674.699471 0001 0117 0
E: 1361898674.699471 0004 0004 -6291257
E: 1361898674.699471 0001 011e 1
E: 1361898674.699471 0004 0004 -6291258
E: 1361898674.699471 0001 011f 1
E: 1361898674.699471 0000 0000 0
E: 1361898678.261384 0004 0004 -6291248
E: 1361898678.261384 0001 0112 0
E: 1361898678.261384 0004 0004 -6291328
E: 1361898678.261384 0001 0117 1
E: 1361898678.261384 0001 0117 0
E: 1361898678.261384 0000 0000 0
E: 1361898678.524143 0001 0113 0
E: 1361898678.524146 0001 011e 0
E: 1361898678.524147 0001 011f 0
E: 1361898678.524149 0000 0000 1
error: could not describe device

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/23

------------------------------------------------------------------------
On 2013-02-26T18:26:50+00:00 Eric wrote:

*** Bug 752606 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/24

------------------------------------------------------------------------
On 2013-02-26T19:13:01+00:00 Hubert wrote:

I'm the OR of the dupe above. My device is a USB headset that has volume
buttons in such. See the details in bug 752606. Feel free to ask info if
you need for that device.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/25

------------------------------------------------------------------------
On 2013-02-27T01:10:09+00:00 Peter wrote:

(In reply to comment #2)
> # evemu-device /dev/input/event16

sorry, typo. should've been evemu-describe

evemu-device is what I run here to reproduce it :)

so, evemu-describe once, the output attached here. then evemu-record
while reproducing the bug, same attached here as plain text file please

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/26

------------------------------------------------------------------------
On 2013-03-07T16:49:01+00:00 Eric wrote:

Created attachment 706727
evemu-describe

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/27

------------------------------------------------------------------------
On 2013-03-07T16:49:35+00:00 Eric wrote:

Created attachment 706728
evemu-record taking the headset off the cradle

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/28

------------------------------------------------------------------------
On 2013-03-08T06:35:04+00:00 Peter wrote:

translated into evtest format (human-readable)

Event: time 1362724260.878932, type 4 (EV_MSC), code 4 (MSC_SCAN), value 
ffa000d0
Event: time 1362724260.878932, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1
Event: time 1362724260.878932, type 4 (EV_MSC), code 4 (MSC_SCAN), value 
ffa00082
Event: time 1362724260.878932, type 1 (EV_KEY), code 275 (BTN_SIDE), value 1
Event: time 1362724260.878932, type 4 (EV_MSC), code 4 (MSC_SCAN), value 
ffa00080
Event: time 1362724260.878932, type 1 (EV_KEY), code 279 (BTN_TASK), value 1
Event: time 1362724260.878932, type 1 (EV_KEY), code 279 (BTN_TASK), value 0
Event: time 1362724260.878932, type 4 (EV_MSC), code 4 (MSC_SCAN), value 
ffa000c7
Event: time 1362724260.878932, type 1 (EV_KEY), code 286 (?), value 1
Event: time 1362724260.878932, type 4 (EV_MSC), code 4 (MSC_SCAN), value 
ffa000c6
Event: time 1362724260.878932, type 1 (EV_KEY), code 287 (?), value 1
Event: time 1362724260.878932, -------------- SYN_REPORT ------------

so you can see that it presses both middle and side button (buttons 2 and 8 in 
X) and doesn't release them (presumably it does when you put it back?). That's 
why the button is stuck and things break.

when you disconnect the device X releases all buttons held by that
devices, so that's why normal functionality comes back.

not much we can do here, best thing is to tell X to ignore this device:
https://fedoraproject.org/wiki/Input_device_configuration#Blacklisting_a_device

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/29

------------------------------------------------------------------------
On 2013-12-21T11:32:37+00:00 Fedora wrote:

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/39

------------------------------------------------------------------------
On 2014-02-05T19:18:57+00:00 Fedora wrote:

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/993655/comments/41


** Changed in: xorg-server (Fedora)
       Status: Unknown => Won't Fix

** Changed in: xorg-server (Fedora)
   Importance: Unknown => Undecided

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/993655

Title:
  Unity looses mouse click handler when using enabling USB headset

Status in xorg-server package in Ubuntu:
  Expired
Status in xorg-server package in Debian:
  New
Status in xorg-server package in Fedora:
  Won't Fix

Bug description:
  I have a Plantronics D100 headset.

  When I press the button on the headset to enable it, Unity looses its
  click handler, in that it can not click and drag windows.

  The cursor is visible and moves just fine. I can switch applications
  using Alt+Tab, and I can launch new applications using the keyboard.
  But I cannot close the existing window, or change focus to another
  window by using the mouse.

  The Headset microphone and speaker work just fine!

  Tested this on a laptop and desktop machine. Both running Ubuntu
  12.04.

  The headset I'm using is a Plantronics D100 unit.

  I have had this problem for the past month while on the 12.04 beta release. 
  --- 
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  NonfreeKernelModules: nvidia
  Package: unity 5.10.0-0ubuntu6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Tags:  precise
  Uname: Linux 3.2.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/993655/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to