Bug 496507

Summary:	Spectacle is unable to start and aborts with SIGABRT in OpenCV code
Product:	[Applications] Spectacle	Reporter:	Joern <joern.koerner>
Component:	General	Assignee:	Noah Davis <noahadvs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	kde, nate
Priority:	NOR
Version First Reported In:	24.08.3
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Joern 2024-11-20 18:35:01 UTC

SUMMARY
On Arch Linux spectacle is unable to start and aborts with SIGABRT - at least on this hardware. 
On other Arch installations (hardware) spectacle works as expected.

STEPS TO REPRODUCE
1. run spectacle
2. 
3. 

OBSERVED RESULT
~> spectacle -r
kpipewire_vaapi_logging: VAAPI: Intel iHD driver for Intel(R) Gen Graphics - 24.4.2 () in use for device "/dev/dri/renderD128"
kpipewire_vaapi_logging: VAAPI: entrypoint 6 of profile 14 is not supported by the device "/dev/dri/renderD128"
kpipewire_vaapi_logging: VAAPI: entrypoint 8 of profile 14 is not supported by the device "/dev/dri/renderD128"
kpipewire_vaapi_logging: VAAPI: entrypoint 6 of profile 14 is not supported by the device "/dev/dri/renderD128"
kpipewire_vaapi_logging: VAAPI: entrypoint 8 of profile 14 is not supported by the device "/dev/dri/renderD128"
terminate called after throwing an instance of 'cv::Exception'
  what():  OpenCV(4.10.0) /usr/src/debug/opencv/opencv/modules/core/src/matrix.cpp:808: error: (-215:Assertion failed) 0 <= roi.x && 0 <= roi.width && roi.x + roi.width <= m.cols && 0 <= roi.y && 0 <= roi.height && roi.y + roi.height <= m.rows in function 'Mat'


EXPECTED RESULT
Taking a screenshot

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 31,0 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: Dell Inc.
Product Name: XPS 15 9520
ADDITIONAL INFORMATION

Comment 1 Nate Graham 2024-11-20 20:27:47 UTC

What GPU are you using?

Comment 2 Joern 2024-11-21 17:46:02 UTC

It's an Intel Iris Xe Graphics eligible, Device-Id: 0x46A6, Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] (rev 0c)

The Nvidia GeForce RTX 3050 GPU is completely disabled and unused (too noisy).

Comment 3 Joern 2024-12-17 17:49:48 UTC

Following situation: 
I've two Displays, one Laptop internal 15.6 inch with 3840x2400 and one external 24 inch with 3840x2160 resolution.
Due to the very different display size the external 24in screen has 130% scale and the internal at 220% to match window sizes between displays. Mesa Intel® Iris® Xe Graphics only the Nvidia part is completely disabled via acpi_call.

Now having both displays connected, the internal at 220% scale the external at 130% spectacle crashes with
spectacle
kpipewire_vaapi_logging: VAAPI: Intel iHD driver for Intel(R) Gen Graphics - 24.4.3 () in use for device "/dev/dri/renderD128"
kpipewire_vaapi_logging: VAAPI: entrypoint 6 of profile 14 is not supported by the device "/dev/dri/renderD128"
kpipewire_vaapi_logging: VAAPI: entrypoint 8 of profile 14 is not supported by the device "/dev/dri/renderD128"
kpipewire_vaapi_logging: VAAPI: entrypoint 6 of profile 14 is not supported by the device "/dev/dri/renderD128"
kpipewire_vaapi_logging: VAAPI: entrypoint 8 of profile 14 is not supported by the device "/dev/dri/renderD128"
terminate called after throwing an instance of 'cv::Exception'
  what():  OpenCV(4.10.0) /usr/src/debug/opencv/opencv/modules/core/src/matrix.cpp:808: error: (-215:Assertion failed) 0 <= roi.x && 0 <= roi.width && roi.x + roi.width <= m.cols && 0 <= roi.y && 0 <= roi.height && roi.y + roi.height <= m.rows in function 'Mat'

KCrash: Application 'spectacle' crashing... crashRecursionCounter = 2


Now when setting the scale factor of the external display to 130% (and only exactly 130% as I can say so far) spectacle crashes with the above message. Any other scale factor seems to work.

Comment 4 Nate Graham 2025-03-07 14:48:07 UTC


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