Hi, 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.
Right now I don't even now what component to file a bug under because I have no idea what could cause such a behavior. My best guess would be metacity though.
These are the package versions I have installed right now: metacity-2.15.34-1.fc6 gtk2-2.10.2-3.fc6 xorg-x11-server-Xorg-1.1.1-30.fc6 kernel-2.6.17-1.2586.fc6
Regards, Dennis
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. 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.
Confirmed. Nothing more, nothing less. ;)
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. 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.
Confirmed. Nothing more, nothing less. ;)
Filed this under: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=204519
Regards, Dennis
On Tue, Aug 29, 2006 at 09:04:27PM +0200, Dennis Jacobfeuerborn wrote:
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
It may depend on a display driver used. Neither this note nor bugzilla report mention which one is in play. My cursor does not seem to have any problems (radeon driver).
Michal
Michal Jaegermann wrote:
On Tue, Aug 29, 2006 at 09:04:27PM +0200, Dennis Jacobfeuerborn wrote:
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
It may depend on a display driver used. Neither this note nor bugzilla report mention which one is in play. My cursor does not seem to have any problems (radeon driver).
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.
Regards, Dennis
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. ;)
I updated my FC5t2 boot partition yesterday, and about half way through the process, this exact same thing happened. After rebooting (to make sure new kernel worked), I didn't see it again, so it was either an artifact of something changing out from under me during the update, or I just haven't used it enough to see it happen again.
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.
I'm using the radeon driver too.
Well, extra data. Anybody else?
Oh, and maybe you can display on another machine (forwarding X through ssh should be the easiest way)? If yes then are you loosing focus in such situation too?
Michal
On 8/30/06, Michal Jaegermann michal@harddata.com wrote:
On Wed, Aug 30, 2006 at 01:47:50PM +0200, Dennis Jacobfeuerborn wrote:
I'm using the radeon driver too.
Well, extra data. Anybody else?
Oh, and maybe you can display on another machine (forwarding X through ssh should be the easiest way)? If yes then are you loosing focus in such situation too?
Michal
I've noticed this once or twice running the intel driver (i915 chipset) and compiz.
I 'recovered' by logging off and logging back in.
Haven't seen this for a few days.... (also, changed back to i810 driver).
tom
Michal Jaegermann wrote:
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.
I have no doubt that a driver might be involved in this but if it is then it's much more likely to be the input driver rather then the display one.
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
-----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?
Kevin
If you use compiz on gnome, try sunflower http://freshmeat.net/projects/sunflowerapplet/ - -- Get my public GnuPG key from http://keyserver.veridis.com:11371/export?id=-1509369771935935023
Kevin DeKorte wrote:
-----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?
PS/2 keyboard and USB mouse. I'm using metacity on my r300 card because compiz isn't really usable on that card and I only have Gnome installed but the problem also affects non-gnome/gtk apps like Opera.
Regards, Dennis
On Wed, 30 Aug 2006 10:46:55 -0600, 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.
I highly doubt that the display driver is related at all. Key-press events are not recognised at all for the erratically focused window, but for other components of the desktop environment.
Btw, I have not updated my driver for a long time, since the mga driver in FC6 Test is suffering from a very bad DoS.
$ grep exc /etc/yum.repos.d/fedora-development.repo exclude=xorg-x11-drv-mga
There's an open ticket about that which is sort of like /dev/null.
On Wed, 30 Aug 2006 08:50:42 -0400, Tom Horsley 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. ;)
I updated my FC5t2 boot partition yesterday, and about half way through the process, this exact same thing happened. After rebooting (to make sure new kernel worked), I didn't see it again, so it was either an artifact of something changing out from under me during the update, or I just haven't used it enough to see it happen again.
When it happens to me -- and remember, it's key input which is not working in a window then, the mouse pointer is working fine all the time (!) -- I minimise/maximise the window, which usually fixes it.
-
Dennis Jacobfeuerborn -
Kevin DeKorte -
Michael Schwendt -
Michal Jaegermann -
Tom Horsley -
Tom London