Bug 699106 - ksnapshot silently fails to snapshot window
Summary: ksnapshot silently fails to snapshot window
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kdegraphics
Version: 15
Hardware: i686
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-23 07:02 UTC by Robin Green
Modified: 2012-07-22 07:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-22 07:41:20 UTC
Type: ---


Attachments (Terms of Use)

Description Robin Green 2011-04-23 07:02:06 UTC
Description of problem:
When ksnapshot starts up, it successfully takes a screenshot. However, if you then try to take a screenshot of a specific window, the captured image remains the same as the previous screenshot.

Version-Release number of selected component (if applicable):
kdegraphics-4.6.2-1.fc15.i686

How reproducible:
Always

Steps to Reproduce:
1. ksnapshot
2. Set capture mode to "Window under cursor"
3. Set snapshot delay to "No delay"
4. Unset "include window decorations" and "include mouse pointer"
5. Click "Take a New Snapshot" button
6. Click on a window
  
Actual results:
KSnapshot reappears, but nothing has changed - the screenshot is the same as before

Expected results:
Should display screenshot of specified window, without any other windows, decorations or plasma

Comment 1 Kevin Kofler 2011-04-23 11:45:46 UTC
* What graphics driver?
* What window manager?
* Is compositing ("desktop effects") enabled?

I cannot reproduce this with kdegraphics-4.6.2-1.fc14.i686.

Comment 2 Robin Green 2011-04-23 12:47:30 UTC
(In reply to comment #1)
> * What graphics driver?

intel

> * What window manager?

kwin

> * Is compositing ("desktop effects") enabled?

Yes

Comment 3 Robin Green 2012-07-22 07:41:20 UTC
Can't reproduce any longer on Fedora 17 (admittedly, on different hardware).


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