Why not use the existing bug, which already has some analysis and possible
solution?
It sounds like the same bug.
Comment 6 and 7 seem to suggest that nothing would happen if a new bug
report were filed, anyway.
--
You received this bug notification because you are a member of Ubuntu-X,
which i
[487553.692] (II) config/udev: Adding input device Plantronics Plantronics
.Audio 646 DSP (/dev/inpu
t/event17)
[487553.692] (**) Plantronics Plantronics .Audio 646 DSP: Applying InputClass
"evdev keyboard catcha
ll"
[487553.692] (**) Plantronics Plantronics .Audio 646 DSP: Applying InputClass
"
gdk_display_get_window_at_pointer() (or more specifically
_gdk_windowing_window_at_pointer) grabs with XGrabServer() before calling
XQueryPointer.
The grab can be broken by switching to a virtual terminal and killing
the app using gdk_display_get_window_at_pointer (or attaching to that
process wit
The bug Damian is seeing has existed for a long time.
It is more likely to occur in the same conditions (short XID range response) as
lead to this bug.
The cause is described here:
http://bugzilla.gnome.org/show_bug.cgi?id=581526
** Bug watch added: GNOME Bug Tracker #581526
http://bugzilla.g
4 matches
Mail list logo