https://bugs.kde.org/show_bug.cgi?id=398443
Bug ID: 398443
Summary: okular sometimes goes into a state where "space" is
recognized for navigation, but not "delete" or
"pageup/pagedown"
Product: okular
Version: 1.5.1
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: frede...@ofb.net
Target Milestone: ---
I've experienced this problem for a while now. Randomly, I'll open a PDF
document, say via a text-based web browser, in Okular. I'll use "space" or the
mouse wheel to navigate down the document. However, when I hit "delete" the
keypress is ignored. Same with "pageup" and "pagedown" - ignored. But if I use
the mouse and click on the document, then it fixes things and I can navigate
with these keys again.
Unfortunately I haven't found a way to reproduce this. It happens every day,
but it may be dependent on a race condition or something because I can't make
it happen on demand. Maybe I am doing a particular thing without realizing it,
e.g. starting to type before the document comes up. Or maybe it only happens on
new documents that Okular hasn't seen before. Usually when I open a document,
all keys work for navigation at startup.
I use the i3 window manager and the w3m web browser. I'm not sure if the bug is
dependent on opening a document with w3m.
I know this isn't much to go on but I wanted to submit here because I'm not
making any progress on getting more information, and I thought maybe somebody
familiar with the code of Okular could say what is happening. It seems that
something is going on related to focus. Is there a focus state where Okular
responds to "space" but not "delete" for navigation?
--
You are receiving this mail because:
You are watching all bug changes.
