From 9cad3fcc971f50ad7e53a7be3746d751639976b5 Mon Sep 17 00:00:00 2001 From: Laszlo Agocs Date: Thu, 21 Sep 2023 14:03:47 +0200 Subject: [PATCH] kms: Print the screen virtual position in the logs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It is impossible to see otherwise what is going on. What's worse, it prints the screen geometry (that does not include the virtual desktop adjustment), which is incredibly confusing. Change-Id: Ie67a4d8110a0b5c9cb75e6290f06c857a980d2c8 Pick-to: 6.6 Reviewed-by: Christian Strømme --- src/platformsupport/kmsconvenience/qkmsdevice.cpp | 1 + 1 file changed, 1 insertion(+) diff --git a/src/platformsupport/kmsconvenience/qkmsdevice.cpp b/src/platformsupport/kmsconvenience/qkmsdevice.cpp index 89b6df605b8..421e9f05c02 100644 --- a/src/platformsupport/kmsconvenience/qkmsdevice.cpp +++ b/src/platformsupport/kmsconvenience/qkmsdevice.cpp @@ -716,6 +716,7 @@ void QKmsDevice::createScreens() // virtualIndex. This is not only handy but also required since for instance // evdevtouch relies on it when performing touch device - screen mapping. if (!m_screenConfig->separateScreens()) { + qCDebug(qLcKmsDebug) << " virtual position is" << virtualPos; siblings.append(s); virtualPositions.append(virtualPos); if (orderedScreen.vinfo.isPrimary)