Bug 500029 - never-ending ksnapshot
Summary: never-ending ksnapshot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kdegraphics
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-10 09:42 UTC by Michal Hlavinka
Modified: 2009-05-11 07:24 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-10 09:51:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Hlavinka 2009-05-10 09:42:36 UTC
Description of problem:
when I press PrtScr, it calls ksnapshost and makes one screenshot. When I hit it several times, it produces several screenshots. Problem occurs, when I hold the key for (even very short) time, it starts calling ksnapshot again and again... For PrtScr holded about 1 sec, I got more than 60 ksnapshots and still continuing...

Version-Release number of selected component (if applicable):
kde 4.2.3
qt 4.5.1

How reproducible:
always

Steps to Reproduce:
1.hold prtscr for some (even short) time 
2.
3.
  
Actual results:
ksnapshot called again and again and again...

Expected results:
limited number of ksnapshots

Additional info:

Comment 1 Kevin Kofler 2009-05-10 09:51:03 UTC
Sorry, that's just how keyboard repeat works, not much ksnapshot can do there.

Comment 2 Michal Hlavinka 2009-05-11 07:24:54 UTC
Yes, I know, ksnapshot should be called more than once, but when I hold PrtScr for just one second, it's called more than 60 times (and keep going). But when I hold for example 'a' for the same time, it's printed only 5 times. In my opinion, key buffer is filled too fast. Just if I press PrtScr little bit slower (pushed just little bit longer than key repeat delay), it doesn't seem to stop calling ksnapshot (more than 60 times doesn't mean "something about 65 times" but "after more than 60 ksnapshots, I've killed it").


Note You need to log in before you can comment on or make changes to this bug.