Has the bug already been filed somewhere? The only thing I've found through Google is this report on the Evince mailing list.
]]>Can someone confirm this?
EDIT:
Alright, I must also add that one needs to place the mouse over the evince window upon closing the dialog. I guess the moment you close the dialog, evince is forced to realise it is focussed (and thus work correctly again).
Seems like evince doesn't like the way tiling window managers handle their focus-related stuff.
EDIT 2:
Alright, when closing the 'open file' dialog with <ESC>, I need exactly (no more and no less) 2 times.
However, when closing the dialog with <Ctrl-Shift-C> (or whatever key you have assigned to closing a client), then it's the thing with the mouse.
It's weird because if I have several evince-windows open, some of them start ignoring keystrokes, whereas others (on the same tag) still work correctly.
]]>I have evince open, change to another tag, change back, evince doesn't take key presses anymore. This doesn't happen every time, but at least 50%.
I'm not sure where to go with this bug either...
]]>I'm trying to get someone else to reproduce this bug before reporting it on some bug-tracker. Though I wouldn't be sure where to report TBH.
Basically, I can trace it to having the Awesome window manager (stable from AUR, currently 3.4.9) with using Evince 3.0 from Gnome 3. In addition any web-browser (I'm using chromium).
1. Open a PDF in Evince and scroll with the arrow-keys.
2. Change to a different work-space running Chromium (or any other browser, not consistent with other applications, but possibly any other application using arrow keys as a scroll mechanism) and click with the left mouse-button on a link or anywhere on a page (focus).
3. Switch workspace back to Evince and try to scroll the PDF using arrow keys, which will not work.
It is consistent as described above, and it is really annoying as the only way to solve it is to unfocus and refocus the Evince window.
Generally this is not a problem, but it has interrupted my work-flow on several occasions and is one of those things I can't believe happen when upgrading to a newer version. I assume the problem is closely related to GTK3 as well, but I can't say who to blame, so unless I can get someone to reproduce this, I can't say if I'm doing something wrong or there is a subtle bug somewhere.
Note: I was able to reproduce this on my second laptop, however the laptop has the exact same configuration (1 to 1) as my other machine.
Thanks.
m.
]]>