On Wed, May 13, 2009 at 06:25:05PM +0300, Marius Gedminas wrote:
On Wed, May 13, 2009 at 10:11:42AM +1000, Peter Hutterer wrote:
On Tue, May 12, 2009 at 04:35:51PM +0300, Marius Gedminas wrote:
Are there any debugging facilities for finding out which X client has
the grab?
I once
On Tue, Jun 09, 2009 at 04:48:06PM +0300, Marius Gedminas wrote:
On Wed, May 13, 2009 at 06:25:05PM +0300, Marius Gedminas wrote:
On Wed, May 13, 2009 at 10:11:42AM +1000, Peter Hutterer wrote:
On Tue, May 12, 2009 at 04:35:51PM +0300, Marius Gedminas wrote:
Are there any debugging
On Wed, May 13, 2009 at 10:11:42AM +1000, Peter Hutterer wrote:
On Tue, May 12, 2009 at 04:35:51PM +0300, Marius Gedminas wrote:
On Tue, May 12, 2009 at 05:57:00PM +1000, Peter Hutterer wrote:
no, actually. this is how input devices work. the physical devices are
abstracted away through
Emanuele Tamponi schrieb:
In data lunedì 11 maggio 2009 14:48:51, walter harms ha scritto:
maybe you can reproduce that with xev ?
does ist happen with other inputs devices also ? keyboard ?
I'll try with xev.
Every mouse device stops working: wireless mouse and builtin trackpad.
On Tue, May 12, 2009 at 09:49:08AM +0200, walter harms wrote:
Emanuele Tamponi schrieb:
In data lunedì 11 maggio 2009 14:48:51, walter harms ha scritto:
maybe you can reproduce that with xev ?
does ist happen with other inputs devices also ? keyboard ?
I'll try with xev.
Every
Peter Hutterer schrieb:
On Tue, May 12, 2009 at 09:49:08AM +0200, walter harms wrote:
Emanuele Tamponi schrieb:
In data lunedì 11 maggio 2009 14:48:51, walter harms ha scritto:
maybe you can reproduce that with xev ?
does ist happen with other inputs devices also ? keyboard ?
I'll try
On Tue, May 12, 2009 at 05:57:00PM +1000, Peter Hutterer wrote:
no, actually. this is how input devices work. the physical devices are
abstracted away through the virtual core pointer. all events go through this
core pointer device, and if an application grabs it then events are no
longer sent
On Tue, May 12, 2009 at 10:11:24AM +0200, walter harms wrote:
Peter Hutterer schrieb:
no, actually. this is how input devices work. the physical devices are
abstracted away through the virtual core pointer. all events go through this
core pointer device, and if an application grabs it then
On Tue, May 12, 2009 at 04:35:51PM +0300, Marius Gedminas wrote:
On Tue, May 12, 2009 at 05:57:00PM +1000, Peter Hutterer wrote:
no, actually. this is how input devices work. the physical devices are
abstracted away through the virtual core pointer. all events go through this
core pointer
maybe you can reproduce that with xev ?
does ist happen with other inputs devices also ? keyboard ?
re,
wh
Emanuele Tamponi schrieb:
In data sabato 9 maggio 2009 18:09:50, Emanuele Tamponi ha scritto:
I exclude the toolkit because it happens on both Qt-based and GTK-based
application...
In data lunedì 11 maggio 2009 22:31:32, Emanuele Tamponi ha scritto:
: In data lunedì 11 maggio 2009 14:48:51, walter harms ha scritto:
maybe you can reproduce that with xev ?
does ist happen with other inputs devices also ? keyboard ?
I've attached it
I'll try with xev.
Every mouse device
Hello,
First of all, my configuration is: KUbuntu 9.04, Xorg 1.6 (KUbuntu default)
with NVidia driver (KUbuntu default), configured with TwinView (Main: 1680x1050
Secondary: 1280x800 (Laptop Display)). Xorg uses HAL to find input devices
(AllowEmptyInput is set to true). I have a Wireless USB
On Sat, May 09, 2009 at 10:42:24AM +0200, Emanuele Tamponi wrote:
Hello,
First of all, my configuration is: KUbuntu 9.04, Xorg 1.6 (KUbuntu default)
with NVidia driver (KUbuntu default), configured with TwinView (Main:
1680x1050
Secondary: 1280x800 (Laptop Display)). Xorg uses HAL to find
In data sabato 9 maggio 2009 12:29:56, Peter Hutterer ha scritto:
we've seen this in Fedora as well (that's on server 1.5) but not been able
yet to find the actual source of the bug. so far, it indicates a
misbehaving client, but we haven't managed to find that one either.
In data sabato 9 maggio 2009 18:09:50, Emanuele Tamponi ha scritto:
I exclude the toolkit because it happens on both Qt-based and GTK-based
application... I'll try to install compiz or some other window manager and
replace KWin, I'll let you know if the problem goes away.
Tried with wm2, same
15 matches
Mail list logo