Bug 320400 - Persistent image of ksnapshot window in the snapshot
Summary: Persistent image of ksnapshot window in the snapshot
Status: RESOLVED DUPLICATE of bug 279615
Alias: None
Product: ksnapshot
Classification: Applications
Component: general (show other bugs)
Version: 0.8.2
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Richard Moore
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-28 20:56 UTC by Romain Diss
Modified: 2013-12-23 19:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Snapshot exemple (179.04 KB, image/png)
2013-05-28 21:05 UTC, Romain Diss 		Details
Snapshot with contrast modified and persistent image revealed. (78.74 KB, image/png)
2013-05-28 21:07 UTC, Romain Diss 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Romain Diss 2013-05-28 20:56:09 UTC 
When I take a snaphot, a persistent image of the ksnapshot window remains in the snapshot. It is not noticeable unless  you edit the snapshot (with gimp for exemple) and set the brightness to the min and the contrast to the max.

This can cause confidentiality problems.

Reproducible: Always

Steps to Reproduce:
1. Launch ksnapshot
2. Take a snapshot
3. Edit the snapshot in gimp and set the brightness to the min and contrast to the max.
Actual Results:  
A persistent image of the ksnapshot window appears.

Expected Results:  
The persistent image of the ksnapshot window should not appear in the snapshot.
Comment 1 Romain Diss 2013-05-28 21:05:00 UTC 
Created attachment 80140 [details]
Snapshot exemple

Exemple of a snapshot with a persistent image of the ksnapshot window. To see it, edit the image and set brightness to the min and contrast to the max.
Comment 2 Romain Diss 2013-05-28 21:07:50 UTC 
Created attachment 80141 [details]
Snapshot with contrast modified and persistent image revealed.

Persistent image obtained by adjusting contrast and brightness in attachment 80140 [details].
Comment 3 Christoph Feck 2013-12-23 19:16:07 UTC 

*** This bug has been marked as a duplicate of bug 279615 ***