Bug 398443 - okular sometimes goes into a state where "space" is recognized for navigation, but not "delete" or "pageup/pagedown"
Summary: okular sometimes goes into a state where "space" is recognized for navigation...
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 1.5.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-10 00:38 UTC by Frederick Eaton
Modified: 2023-02-17 03:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frederick Eaton 2018-09-10 00:38:10 UTC
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?
Comment 1 Frederick Eaton 2018-09-11 19:43:36 UTC
I realized on further observation that this seems related to Okular's on-demand loading of PDF data. Sometimes when Okular is open in a tab, I can cause it to enter a bad-focus state just by scrolling down in a recently-opened document. In other words, it'll be in a state where "space" and "delete" both work; then I press "space" several times and Okular pauses a second while loading the next page, and then I find that it no longer recognizes "delete" to scroll up... and I have to use the mouse button to restore focus.

So you can probably ignore the information about my window manager, and certainly my web browser, in the initial report; the bug can be triggered entirely within Okular.

By the way how do I get a list of bugs I've submitted? The "My Requests" link in the header doesn't show anything...
Comment 2 Albert Astals Cid 2018-11-21 22:27:07 UTC
> By the way how do I get a list of bugs I've submitted? The "My Requests" link in the header doesn't show anything...

Do you have a "My bugs" on the footer?
Comment 3 Frederick Eaton 2018-11-22 01:29:19 UTC
Yes indeed, that does the trick. Thank you. I must have missed it before.
Comment 4 Justin Zobel 2023-01-18 02:41:08 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-02-02 05:01:23 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-02-17 03:48:56 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!