Bug 255686

Summary:	Okular cannot scroll using keyboard after screen turns back on after suspend
Product:	[Applications] okular	Reporter:	eric948470
Component:	general	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	creichert07, jordonwii
Priority:	NOR
Version:	0.10.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description eric948470 2010-10-30 19:21:31 UTC

Version:           0.10.2 (using KDE 4.5.2) 
OS:                Linux

Okular doesn't respond to the arrow keys or page up/down after the screen turns back on after turning off to save power.

Reproducible: Always

Steps to Reproduce:
1. Open a pdf file
2. Suspend machine
3. Log back in
4. Try to scroll the pdf file using the keyboard

Actual Results:  
Okular is unresponsive to keyboard commands. But scrolling using mouse works.

Expected Results:  
Okular should be responsive to keyboard commands just as before suspension.

OS: Linux (i686) release 2.6.32-25-generic
Compiler: cc

Comment 1 Pino Toscano 2010-10-31 01:16:10 UTC

> Okular is unresponsive to keyboard commands. But scrolling using mouse works.

Even if you click once with the mouse over the page view?

Comment 2 eric948470 2010-10-31 05:02:20 UTC

Yes. After I click once over the page view the keyboard remains unresponsive. Even if I try after scrolling with the mouse, it remains unresponsive.

I just did some more tests. Okular is completely unresponsive to the keyboard, not just for the scrolling keys. Keyboard shortcuts don't work.

And this happens only when Okular is the 'active' program when I suspend the computer, meaning it is the one highlighted on the taskbar and the one that takes keyboard commands. After logging in again, if I make another program active (click on it on the taskbar) and then make Okular active again, Okular is responsive to the keyboard. If I minimize Okular, click on the desktop, and then make Okular active again (click on Okular on the taskbar), it is responsive to the keyboard. If I have another program as the active program when the machine is suspended, it does not happen.

It happens not only when I manually suspend the machine, but also when the machine puts itself to sleep to save power. That's when I first noticed it.

Comment 3 Christopher Reichert 2011-07-12 05:08:43 UTC

I tried to recreate this bug by following the outlined steps and I cannot. It has been a while since this bug was submitted. Do you still have the same errors? Are you on a newer version of Okular?

Comment 4 jordonwii 2012-01-06 04:34:17 UTC

I'm also unable to reproduce in Okular 0.13.3. Is it possible this bug is related specifically to the computer hardware?

Comment 5 eric948470 2012-01-06 05:17:06 UTC

I have changed my computer after that, and haven't encountered it afterwards. So it's most probably related to the specific hardware.

Thanks for looking in to this.