Bug 272664

Summary:	KSnapshot 0.8.2 can't take snapshot when Capture mode set to Window Under Cursor
Product:	[Applications] ksnapshot	Reporter:	archit3x <foss.linux>
Component:	general	Assignee:	Richard Moore <rich>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	adaptee, awck, foss.linux
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description archit3x 2011-05-07 01:31:17 UTC

Version:           unspecified
OS:                Linux

Every I try to take new snapshot in Window Under Cursor Mode KSnapshot can't do it.

Reproducible: Always

Steps to Reproduce:
- Open KSnapshot, set Capture Mode to Window Under Cursor
- Snapshot delay : 4 seconds
- Include Window Decoration : yes
- Include Mouse Pointer : no
- Take New Snapshot

Actual Results:  
Nothing. KSnapshot just diplayed previous captured object

Expected Results:  
KSnapshot can take new snapshot with Window Under Cursor mode and change snapshot preview to current captured object.

OS : Archlinux
KDE : 4.6.3
KSnapshot : 0.8.2
Desktop Effect : yes
Kipi-plugins : yes

Comment 1 archit3x 2011-05-07 01:36:48 UTC

While I disable Desktop Effects, KSnapshot work normaly (can capture with Window Under Cursor mode)

Comment 2 Alex Krauss 2011-12-05 18:09:22 UTC

I can confirm this issue and also that it doesn't exist when Desktop Effects are disabled.

OS : Debian Sid (Aptosid)
KDE : 4.6.5
KSnapshot : 0.8.2
Desktop Effect : yes
Kipi-plugins : yes

Kernel     Linux 3.1-4.slh.1-aptosid-amd64 x86_64
CPU Info   4x Intel Core i5-2500K @ 6144 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 3301.000 MHz ]                  
Videocard  Intel 2nd Generation Core Processor Family Integrated Graphics Controller X.Org 1.11.2.901  [ 1280x1024@60.0hz ]
Processes 277 | Uptime 21:58 | Memory 2756.3/7900.0MB | HDD WDC WD3200AAKS-0 Size 324GB (28%used)

Comment 3 Alex Krauss 2011-12-05 18:48:20 UTC

Disabling just the "Screenshot" desktop effect works around this issue.

Comment 4 Jekyll Wu 2012-03-09 08:13:17 UTC


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