| Summary: | okular sometimes goes into a state where "space" is recognized for navigation, but not "delete" or "pageup/pagedown" | ||
|---|---|---|---|
| Product: | [Applications] okular | Reporter: | Frederick Eaton <frederik> |
| Component: | general | Assignee: | Okular developers <okular-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | aacid, frederik, nate |
| Priority: | NOR | ||
| Version First Reported In: | 1.5.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Frederick Eaton
2018-09-10 00:38:10 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... > 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?
Yes indeed, that does the trick. Thank you. I must have missed it before. 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! 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! 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! |