Alexander Klein wrote: > Am 22.06.2016 um 22:32 schrieb Aaron Sloman: > > > Today, after about 150 days without rebooting, I decided it was time > > to update everything, including kernel, and reboot. > > > > I am pleased to report that this seems to have fixed the keyboard > > input focus problem on both my fedora 22 machines (desktop and > > laptop), tested on firefox, opera and google-chrome. > > > Hi Aaron, > > I take it that you didn't log out and back in again, either, did you? > > It's not at all impossible that some components outside of the kernel > can't take advantage of updated libraries they're linked to, unless > they're actually restarted and let the old version go.
Hi Alexander. Yes you are right, though I failed to mention (a) that I upgraded the OS including kernel more frequently on the laptop than on the desktop machine (my main work engine). (b) that on both machines I re-started firefox from time to time, making use of its ability to get back all previously open tabs and windows (except for those opened in 'private browsing' windows. In both cases every time I restarted firefox all the windows at first allowed me to type into address bars. But sometimes one of the windows would not allow this, even when I started new tabs. So I could have keyboard input working in one firefox window but not another. On the desktop machine I have to kill and restart Firefox every few days because it seems to have a serious garbage-collection/bloat problem as shown by 'top', with accompanying slowness. (I have a total of 8GB main memory on that machine, 4GB on the laptop.) After restarting FF, keyboard input normally works for a while. But after a while one of the windows won't accept keyboard input. (The time varies and does not seem to be connected with memory bloat.) What I have now found was that my report that updating kernel and rebooting had cured the problem was premature. After a few days the problem returned: one or two windows refuse keyboard input while others don't. However switching to a different workspace and back always fixes the problem. But the plot thickens: I have also found that by editing one of the buttons on the 'Bookmarks' toolbar I can restore keyboard input. E.g. right-click on button, select 'Properties' and do something in name or location field then close. After that text input works in the address bar. It doesn't require the entry to be changed permanently. I have not yet tested whether merely opening the properties menu and closing it will suffice. I'll have to wait till the problem recurs before I test that. So there are two things that restore input focus to a browser window: move to another workspace and back, and opening and editing a bookmark properties menu! Merely opening a new tab doesn't restore focus. I have not tried that on any other browser: neither opera nor google chrome (neither of which is used much) has shown the focus problem since I last rebooted. Aaron http://www.cs.bham.ac.uk/~axs
