Bug 469799

Summary:	Wrong calculation of y-coordination for Rectangular Region outside of KDE in xorg.
Product:	[Applications] Spectacle	Reporter:	raven2cz <tonda.fischer>
Component:	General	Assignee:	Noah Davis <noahadvs>
Status:	RESOLVED UNMAINTAINED
Severity:	grave	CC:	dashonwwIII, kde, nate
Priority:	NOR	Keywords:	X11-only
Version First Reported In:	23.04.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description raven2cz 2023-05-15 11:04:31 UTC

I'm not sure, if it is same as this one Bug 462860. The problem is mainly with y-coordinate about 30 pixels. I tested it on several stations with more WMs, and the bug is present everywhere except KDE.

Since the introduction of the new version of Spectacle with a new GUI, I have been experiencing significant problems with the screen region capture feature. I use Spectacle in Xorg for AwesomeWM, Qtile, and other window managers. My display has a 4K resolution with a DPI setting of 120 in .Xresources.

Description of the problem: When I initiate a window capture operation: Rectangular Region, the entire window appears shifted upwards by approximately 30 pixels compared to the mouse cursor. Consequently, it is not possible to accurately capture the intended area. Similarly, the cursor is also offset from the points used to adjust the highlighted region, and the cursor change for resizing the region is also shifted by 30 pixels. It seems that there is an incorrect calculation of the y-coordinate for Xorg in your implementation.

Comment 1 Noah Davis 2023-10-09 18:24:47 UTC

Have you tried spectacle 23.08?

Comment 2 raven2cz 2023-10-10 12:33:10 UTC

Yes, I have Arch with version 23.08.1. The error still persists in awesomewm. It's been several months now. Thank you very much for being interested in helping me. I really like Spectacle, but it's now very difficult to use like this. Moreover, it's quite laughable. It's specifically about the y-coordinate. It's possible that there are some nuances concerning the top window title, which is apparently naively used in KDE and is done differently elsewhere. These problems weren't there before, but now the whole application is different, so I believe that some important fixes might not have been incorporated that could have been there previously for other WMs.

Comment 3 Dashon 2023-10-10 15:25:09 UTC

I'm also on Arch, this was broken for me at one point as well, but now it works fine. I no longer have the rectangular screenshot region offset anymore

Comment 4 raven2cz 2023-10-11 06:22:03 UTC

I still have this issue on all of my stations and laptops. So, it's not just one local computer. It is necessary to check the code and find the cause. Especially if it occurred elsewhere once, then it's not a coincidence and it won't be due to the version because I use the current one and it still doesn't work.

If KDE applications don't work correctly for other DE/WM, it's an issue and in this case, quite a critical issue, because it's not easy to simply adjust the region and use the sliders.
This could lead to a loss of users for a very good application.

Comment 5 Noah Davis 2023-10-11 14:17:18 UTC

This might already be fixed in 24.02 (unreleased)

Comment 6 raven2cz 2024-03-07 17:13:34 UTC

(In reply to Noah Davis from comment #5)
> This might already be fixed in 24.02 (unreleased)

@Noah Davis So after today, the mentioned release has finally been released. I opened the app....., and? The bug is NOT fixed! What will you need in order to actually fix the bug? In my opinion, it's quite a critical issue because when the window's square is at the bottom, you can't properly scroll down if the y-coordinate is off by that many pixels. Do you want to upload a video? How shall we proceed?

Comment 7 Nate Graham 2025-10-30 19:16:25 UTC

I'm afraid support for X11 is limited and deteriorating. Pretty much all KDE developers have moved to Wayland. I think there's a very low chance of this bug being fixed, if it's still happening.

However feel free to re-open the bug report if you find that the exact same problem is still happening in a Wayland session. Thanks for understanding!