Thank you for the report.
It does not happen with a single screen!

Hunting around the LxQt site https://lxqt.github.io/ found that the version of this application you cite, screengrab-2.3.0, was updated to Release screengrab 2.4.0 April 2022:
 https://lxqt-project.org/release/2022/04/15/screengrab-2-4-0/

This is already in Cauldron Apr 20 Release 2.4.0, so please report for that version.
If that does not solve it, please raise a bug upstream:
 https://github.com/lxqt/lxqt/issues

CC: (none) => lewyssmith

Hmm...  2.4.0 still hasn't shown up via mcc update...  I'll watch for it.

That was a mistake from Lewis. We only have 2.3 in cauldron. 
@Pierre: it would help our package maintainers if you build the 2.4 from upstream localy on your system and test it. It‘s easy to use the 2.3 src.rpm, exchange the tar.gz file against the 2.4 version, adapt the spec file, build, test.

Created attachment 13294 [details]
build log

I've never dug into package management beyond using it; though I have no problem with tarballs and compiling those...  before now...  ;/

Downloaded 2.4.0 from github.
First compile attempt needed cmake; installed:
    lib64rhash0-1.4.0-2.mga9.x86_64.rpm cmake-3.23.2-1.mga9.x86_64.rpm
which "removed":
    lib64rhash0-1.4.0-2.mga9.x86_64.rpm cmake-3.23.2-1.mga9.x86_64.rpm
***  Is this a bug where the mcc messages report installed, then removed?
     Also happened on each install I did below.

cmake failures:
Qt5LinguistTools missing;
   installed lib64qt5help-devel-5.15.2-10.mga9.x86_64.rpm

KF5WindowSystem missing:
   installed lib64kf5windowsystem-devel-5.93.0-1.mga9.x86_64.rpm

Now get:
  Could not find a configuration file for package "Qt5Xdg" that is compatible
  with requested version "3.9.0".

Searching for qt5xdg; I see:
  lib64qt5xdg-devel
  lib64qt5xdg3
  lib64qt5xdgiconloader3
which are all installed...

Never saw so many build issues before this app; not sure what to do next...

-----------------------------------
This is the last konsole output I get trying to compile:
$ cmake ../
-- XCB[XCB]: Found component XCB
CMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (XCB_XCB)
  does not match the name of the calling package (XCB).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  cmake/FindXCB.cmake:207 (find_package_handle_standard_args)
  cmake/FindXCB.cmake:226 (_xcb_handle_component)
  CMakeLists.txt:32 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- XCB[SHAPE]: Found component SHAPE
CMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (XCB_SHAPE)
  does not match the name of the calling package (XCB).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  cmake/FindXCB.cmake:207 (find_package_handle_standard_args)
  cmake/FindXCB.cmake:226 (_xcb_handle_component)
  CMakeLists.txt:32 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- XCB[XFIXES]: Found component XFIXES
CMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (XCB_XFIXES)
  does not match the name of the calling package (XCB).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  cmake/FindXCB.cmake:207 (find_package_handle_standard_args)
  cmake/FindXCB.cmake:226 (_xcb_handle_component)
  CMakeLists.txt:32 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Build type: Release
-- Install prefix: /usr/local
-- Library path: /usr/local/lib64/screengrab
CMake Deprecation Warning at cmake/LXQtTranslateTs.cmake:59 (cmake_minimum_required):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.
Call Stack (most recent call first):
  CMakeLists.txt:75 (include)


CMake Error at CMakeLists.txt:81 (find_package):
  Could not find a configuration file for package "Qt5Xdg" that is compatible
  with requested version "3.9.0".

  The following configuration files were considered but not accepted:

    /usr/share/cmake/qt5xdg/qt5xdg-config.cmake, version: 3.8.0



-- Configuring incomplete, errors occurred!
See also "/home/pfortin/Downloads/screengrab-2.4.0/build/CMakeFiles/CMakeOutput.log".

Sorry i didn‘t know that you didn‘t build some Mageia packages before.
This week im away from my big machines with several monitors, so i can‘t test. But i have my laptop with building environment with me. So i can only build the package localy for my machine. 

You don‘t need to invoke cmake and stuff yourself when you build packages for Mageia. We have two good wiki articles which explain the building stuff really good. They helped me alot when i started building for myself.
https://wiki.mageia.org/en/Packaging_for_beginners
https://wiki.mageia.org/en/Packagers_RPM_tutorial

I'll try to have a look later this week. Right now, I'm baby-sitting a job that's been running for 41 hours at 100% CPU.  Had to pause it to "zip -mj" the already processed files onto another drive...  Running tight with 64GB RAM, so I have another 64GB on order... I'll do what I can; but it may be a few days...

This has got out of hand.
(In reply to sturmvogel from comment #3)
> That was a mistake from Lewis. We only have 2.3 in cauldron. 
I must have been misled by:
Tue Mar 29 11:23:57 2022 UTC (2 months, 1 week ago) by papoteur
Update to 2.3.0
Wed Apr 20 11:53:33 2022 UTC (7 weeks, 2 days ago) by papoteur
Release 2.4.0
Mon Apr 25 09:35:09 2022 UTC (6 weeks, 4 days ago) by papoteur
SILENT: add the tarball 2.4.0

> @Pierre: it would help our package maintainers if you build the 2.4 from
> upstream localy on your system and test it. It‘s easy to use the 2.3
> src.rpm, exchange the tar.gz file against the 2.4 version, adapt the spec
> file, build, test.
I do not think we should ask busy users to test-build new releases for us. Pierre, it was noble of you to try, but we know you are *very* occupied.
With Cauldron, it is surely normal to ask the packagers to do this. Since Yves seems to have started on this, CC'ing him.

As the source problem is slightly obscure, I doubt that the newest release will fix it. Live in hope. From comment 1:
> If that does not solve it, please raise a bug upstream:
> https://github.com/lxqt/lxqt/issues
still apples.

CC: (none) => yves.brungard_mageia

Hi Lewis!  I apply updates daily -- as soon as I see 2.4.0 or later, I'll update this bug, and open upstream if still present.  Thanks.

Hello,
This is perhaps a problem like this one reported upstream.
https://github.com/lxqt/screengrab/issues/211
I will try to fix the build of 2.4.0, but I don't expect it fixes something.
Pierre, do you apply a scale factor?

No; I don't see anything relating to scale, unless you mean resizing the screengrab window.  Even that doesn't change anything for me.  From my perspective, only the "Window" selection fails to grab a window on primary screen. If I use "Screen Area" and select exactly the window of interest, it works fine.  All I see is what I reported, nothing more... My use is quite simple, take a screenshot, save it, use gimp for all manipulations... HTH

Hi Pierre,
Sorry for not being clear enough. With scaling, I refer to the indication in the refered issue:
> Set the global Qt scale factor to 1.5 in LXQt Session Settings.

I missed that... I have nothing LXQt related installed; only a few libQt packages per ldd...  where can scaling be changed?  Sorry; forgot to include my desktop info:
Operating System: Mageia 9
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
Kernel Version: 5.18.3-server-1.mga9 (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700K
Memory: 62.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT

screengrab 2.4.0 is now in cauldron updates testing.
To know for scaling:
In system settings (Configuration de l'ordinateur)
Affichage et Écran - Configuration de l'affichage - Échelle globale

Never assume a person's linguistics based on their name...  I had to confirm with google translate... :)

Found Global scale with your input; never changed that. I "scaled" my display physically: went from a 16" laptop to a desktop with two 27" monitors... :)

Just tried 2.4.0; problem persists.

Filed report at https://github.com/lxqt/lxqt/issues/2251

In the meantime you can use the standard screenshot tool under Plasma "spectacle". The advantage from this tool is that you can do annotations/markings/simple editing of your screenshots directly without additional external programs.

I know that this is not a final soulution for you as you want to use a Lxqt screenshot tool under Plasma. But until screengrab gets fixed...

Thanks!  Was not aware of this one...  it seems to work fine for grabbing; will check out other features once I have more time.

Fixed upstream per https://github.com/lxqt/lxqt/issues/2251

I'll wait for it to appear in testing or regular updates; I have no time to attempt to build it.

I Pierre,
Sorry for the bad assumption.
I will apply the patch.
Build is running.

Papoteur

Thank you Yves for picking this up; and Pierre for getting a quick fix from upstream.

(In reply to Pierre Fortin from comment #14)
> Never assume a person's linguistics based on their name...  I had to confirm
> with google translate... :)
@papoteur: I made the same 'mistake'...

(In reply to sturmvogel from comment #15)
> In the meantime you can use the standard screenshot tool under Plasma
> "spectacle". The advantage from this tool is that you can do
> annotations/markings/simple editing of your screenshots directly without
> additional external programs.
(In reply to Pierre Fortin from comment #16)
> Thanks!  Was not aware of this one...  it seems to work fine for grabbing;
> will check out other features once I have more time.
@Pierre: This surprises me. As [you] a habitual Plasma user, I found it curious that you were not using it; imagined that with your experimental tendancy, the idea of a Qt utility appealed! I bet spectacle gets installed as standard with Plasma.

@Frank: I did not know about Spectacle's screenshot editing capabilities. That is the great advantage of Flameshot, which is powerful re annotation; but difficult to discover its capabilities, and curiously it does not have a 'window' option, just wholescreen or selected. And as for two monitors, unsure.

@Lewis  I just never found spectacle... Checked mcc, and it's nowhere in any obvious (to me) branches. Searched by name and found it; but its name is not what I would expect for screenshot.  The description says it replaces KSnapshot; but the odds of finding "shot" in descriptions...  :/   I mainly focus on massive data analysis these days -- processed 1.8TB and squeezed out the most important 77M records. This took over 41 hours non-stop. Now have 128GB RAM since yesterday; hope my crunching goes faster now...

Off-topic; but related to crunching:
If LibreOffice Calc allowed me to reconfigure its 1,073,741,824 cells from 1,048,576 rows by 1024 columns to any other Row/Col combination; say 100 columns by 10M rows (same total cells), that would be a HUGE win for me...  :)  Better if I could open 50M rows at 100 columns... B^)

Back to Qt (or any similar technology), my focus is on tools, not their building blocks...  Honestly, I wouldn't know how to get a list of Qt-based tools...   

Most of my efforts lately are Python-based; but the package I'm waiting on, is pgadmin...  :)

Thanks to all for a great distro!!  and your support!

As papoteur is actively dealing with this, assigning to you.

@Pierre
(In reply to Pierre Fortin from comment #17)
> Fixed upstream per https://github.com/lxqt/lxqt/issues/2251
(In reply to papoteur from comment #18)
> I will apply the patch.
> Build is running.
You should get the update automatically from Cauldron. Note the new version number. And please report whether it fixes the specific issue you bugged.

Assignee: bugsquad => yves.brungard_mageia

Sorry; been extremely busy.  This seems to work as expected now. Thanks.

Status: NEW => RESOLVED
Resolution: (none) => FIXED