Since I fully resynced with yesterdays rawhide I now regulary lose the cursor/ability to type in *any* application on the desktop. I can still focus a window (ie the title bar changes it's color) but I cannot type anything in the terminal or in gedit. Also when focusing a window I don't get any cursor (in gedit it completely disappears, in the terminal the cursor is displayed as "unfocused" i.e. as an unfilled rectangle). Also the menus can be selected and get highlighted but the actual menu popup doesn't appear. Opera is affected too so this doesn't seem to be limited to gtk2 apps. Risizing a window fixes the problem until it reappears a minute later.

Michael Schwendt wrote: >On Mon, 28 Aug 2006 16:46:08 +0200, Dennis Jacobfeuerborn wrote: > >>Since I fully resynced with yesterdays rawhide I now regulary lose the >>cursor/ability to type in *any* application on the desktop. > >Confirmed. Nothing more, nothing less. ;) > Filed this under: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=204519

>>>> Since I fully resynced with yesterdays rawhide I now regulary lose the >>>> cursor/ability to type in *any* application on the desktop. >>> Confirmed. Nothing more, nothing less. ;)

Michal Jaegermann wrote: >>>On Mon, 28 Aug 2006 16:46:08 +0200, Dennis Jacobfeuerborn wrote: >>> >>>>Since I fully resynced with yesterdays rawhide I now regulary lose the >>>>cursor/ability to type in *any* application on the desktop. > >It may depend on a display driver used. Why would the display driver have anything to do with this?

Visual feedback works just fine when focusing a window it's just as if the client area of that window doesn't receive that focus event anymore.

I'm using the radeon driver too.

On Wed, Aug 30, 2006 at 01:47:50PM +0200, Dennis Jacobfeuerborn wrote: > Michal Jaegermann wrote: >>>> On Mon, 28 Aug 2006 16:46:08 +0200, Dennis Jacobfeuerborn wrote: >>>> >>>>> Since I fully resynced with yesterdays rawhide I now regulary lose the >>>>> cursor/ability to type in *any* application on the desktop. >> It may depend on a display driver used. > Why would the display driver have anything to do with this? Things which are drawn on your graphic display have something, as it happens, to do with your display driver and its configuration. Such driver handles also such details as acceleration, cursors - hardware or software, offscreen video memory, etc... BTW - did you try to see what will happen if you will turn SWcursor option on? By default is off. > Visual feedback > works just fine when focusing a window it's just as if the client area of > that window doesn't receive that focus event anymore. Right. So one possibility is that something is getting confused about locations of these areas but a question is where. An information that something like that is observed only with a particular driver (or maybe even hardware) or is driver independent makes a difference when you are trying to figure it out what happens.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dennis Jacobfeuerborn wrote: > As I found out while I can't input any text when this happens I can > still select text in the window. The selection is displayed with a gray > background though indicating that the windows doesn't have focus. So the > input driver seems to send proper click and drag events and they arrive > at their intended target but the click doesn't seem to result in > focusing the client area. It does focus the window though so the event > does seem to reach the WM but not the app. > > Regards, > Dennis > What kind of inputs are you using? PS/2 Keyboard and mouse or USB? I'm using USB devices on an i915 (using i810 driver) with up to date rawhide and have seen none of the problems you are seeing (gnome with compiz). Perhaps you got a bad upgrade, I had this with nautilus a couple of weeks ago. Maybe a 'yum clean all' and then a 'yum update' will fix your problems. Also, do you get these problems in other environments like XFCE or KDE?