Bug 325693 - KSnapshot captures itself in 4.11.2 with fade effect
Summary: KSnapshot captures itself in 4.11.2 with fade effect
Status: RESOLVED DUPLICATE of bug 279615
Alias: None
Product: ksnapshot
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.8.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Richard Moore
URL: http://i.imgur.com/qVG94AG.png
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-06 09:15 UTC by valdikss
Modified: 2013-10-06 11:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description valdikss 2013-10-06 09:15:58 UTC 
KSnapshot started to capture itself after updating to KDE 4.11.2. I suppose that's because fade effect become slower. Without fade effect everything works fine.

Reproducible: Always

Steps to Reproduce:
1. Enable compositing and fade effect
2. Try to make a screenshot
Actual Results:  
KScreen is on the screenshot

Expected Results:  
No KScreen on the screenshot
Comment 1 valdikss 2013-10-06 09:17:08 UTC 
Sorry, not KScreen but KSnapshot.
Comment 2 Jekyll Wu 2013-10-06 09:59:39 UTC 
@Kwin devs, could this be a regression in kwin ?
Comment 3 Thomas Lübking 2013-10-06 10:22:56 UTC 
the fade time was stretched - but it would also be slower with the animation time setting (or a customized effect for closing or the explosion effect or whatever)
https://git.reviewboard.kde.org/r/111798/

i assume ksnapshot operates on a static timeout to dump the screen?
with compositing, we could also just skip the ksnapshot window/s from rendering - I'll look into the screenshot effect.
Comment 4 Christoph Feck 2013-10-06 11:53:33 UTC 

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