Re: Window focus

El 18/09/10 09:35, JPB escribió:
> Le samedi 18 septembre 2010, Alejandro López a écrit :
> 
>> El 14/09/10 17:32, Len Lawrence escribió:
> 
>> > On 14/09/10 13:42, Alejandro López wrote:
> 
>> >> Len Lawrence wrote:
> 
>> >>> On 14/09/10 08:17, Alejandro López wrote:
> 
>> >>>> El 13/09/10 20:48, Barry Jackson escribió:
> 
>> >>>>> On 13/09/10 12:08, Len Lawrence wrote:
> 
>> >>>>>> On 13/09/10 08:47, Alejandro López wrote:
> 
>> >>>>>>> Hi all,
> 
>> >>>>>>>
> 
>> >>>>>>> since a few weeks, I'm facing a problem on my 2010.1. When I click
> 
>> >>>>>>> a window, it doesn't get the focus. The only way for a window to
> 
>> >>>>>>> get the focus is to click on the borders or the top title bar.
> 
>> >>>>>>> This is quite annoying.
> 
>> >>>>>>>
> 
>> >>>>>>> I remember that many years ago there was a configuration
> option for
> 
>> >>>>>>> this, but I failed to find it, if it still exists.
> 
>> >>>>>>>
> 
>> >>>>>>> Any idea about how to solve this?
> 
>> >>>>>>>
> 
>> >>>>>>> TIA,
> 
>> >>>>>>> Alejandro.
> 
>> >>>>>>
> 
>> >>>>>> Yes, I seem to remember there were more choices in the old days. I
> 
>> >>>>>> prefer focus-follows-mouse, which can be selected in GNOME
> 
>> >>>>>> Preferences
> 
>> >>>>>> -> Windows. If that is unchecked windows assume focus wherever
> 
>> >>>>>> they are
> 
>> >>>>>> clicked. Maybe KDE has something similar.
> 
>> >>>>>>
> 
>> >>>>>> Len
> 
>> >>>>>
> 
>> >>>>> Have you tried :-
> 
>> >>>>> Right click window title bar->Configure window behavior->Focus
> 
>> >>>>
> 
>> >>>> I have no "Configure Window Behavior" menu when I right-click on the
> 
>> >>>> title bar. Is this a KDE feature? I'm using GNOME/metacity.
> 
>> >>>
> 
>> >>> Yes, that must be KDE. I don't have it in GNOME either. I
> 
>> >>> occasionally see odd behaviour under GNOME for all sorts of things
> 
>> >>> like the power save stuff going AWOL or the back delete key not
> 
>> >>> working in a terminal all of a sudden but OK in emacs. Usually things
> 
>> >>> right themselves after a reboot (the easiest way if you don't know
> 
>> >>> what is going on). Perhaps logging out and in would help?
> 
>> >>
> 
>> >> I don't know exactly when this problem started, but it's been there
> 
>> >> for some weeks now. In the meantime I rebooted the machine (my
> 
>> >> personal PC, not a server) several times.
> 
>> >
> 
>> > Don't know what to suggest then. I have had a look at the xev output in
> 
>> > a terminal and see the expected events for Click-to-focus and
> 
>> > Sloppy-focus (focus follows mouse); things like Leave and Enter Notify
> 
>> > events and FocusIn and FocusOut events, all at the expected places. If
> 
>> > you try this, stick to small movements near the edges of windows or you
> 
>> > will be swamped by MotionNotify events. If there is some unexpected
> 
>> > behaviour it might mean something to somebody on this list. I know
> 
>> > nothing about the infrastructure of the desktop or X server. One thing
> 
>> > I noted was enter and leave events on moving between the title bar and
> 
>> > the window it decorates.
> 
>> >
> 
>> > Len
> 
>>
> 
>> Sorry for the delay but I've been out for a few days.
> 
>>
> 
>> I tried xev and the results are as expected: wrong. I have the FocusIn and
> 
>> FocusOut events only if I click on the window's border or title bar. If I
> 
>> click inside the window, I just get rwo ButtonPress events with state
> 
>> 0x2030 and 0x2130 (press and release?).
> 
>>
> 
>> I guess there is a configuration problem somewhere, but probaly this
> is not
> 
>> something that can be managed with the GUI.
> 
>>
> 
>> Thanks for your help anyway.
> 
>> Alejandro.
> 
> What about creating a new user and see if the problem is still present ?
> 
> JPB
> 


Thanks for your idea.

I just tried this and nothing changed. The new user has the same problem. So I tried to log-in as another existing  user (root) to
verify is the problem was also present for other existing users, and it is.

I don't know if it has something to do, but about the same time, the keyboard stoped working correctly (not a hardware problem as it
works with Solaris). For instances, Alt+F4 will not close the windows. I discovered that my Sun type 7 keyboard is producing not
just Alt+F4, but Mod2+Mod4+F4.

Alejandro.