Summary: | KMail perceives cursor location to be vertically offset from where Wacom Bamboo graphic tablet's cursor is visible | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Markus <no-spam-134> |
Component: | UI | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | REPORTED --- | ||
Severity: | grave | CC: | dmatteo002, kde, nate |
Priority: | NOR | ||
Version: | 5.14.2 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Screenshot of KMail offset behavior showing highlighted message NOT under Wacom Bamboo graphic tablet cursor
Kate with selected text showing offset between cursor and selected area |
Description
Markus
2020-07-05 17:01:54 UTC
Created attachment 129921 [details]
Screenshot of KMail offset behavior showing highlighted message NOT under Wacom Bamboo graphic tablet cursor
Are you using X11 or Wayland? (In reply to Nate Graham from comment #2) > Are you using X11 or Wayland? X11 Thank you for your prompt reply! :) (In reply to Nate Graham from comment #2) > Are you using X11 or Wayland? X11 and the NVIDIA accelerated driver Started KMail from KRunner and the problem persists. Started Kontact from KRunner and the problem persists. Then Tested starting KMail from the command line in Konsole with: QT_XCB_TABLET_LEGACY_COORDINATES=1 kontact Problem appears resolved. Tested starting Kontact from the command line in Konsole with: QT_XCB_TABLET_LEGACY_COORDINATES=1 kontact Problem appears resolved. So, I used Application Launcher > Edit Applications to edit the launch commands for KMail and Kontact so that they are preceded with "QT_XCB_TABLET_LEGACY_COORDINATES=1" as shown above. So, now when KMail or Kontact are started from a panel icon, or an icon in the Application Launcher, the problem persists. And When KMail or Kontact are launched from KRunner, the problem appears resolved. I REALLY don't want to use KRunner every time to start KMail or Kontact. I want to be able to start KMail and Kontact from a panel icon as I have for 15+ years. After having used Application Launcher > Edit Applications to edit the launch commands for KMail and Kontact so that they are preceded with "QT_XCB_TABLET_LEGACY_COORDINATES=1" as shown above, I launched Kontact from KRunner, logged out, logged back in and let the session manager start Kontact. The problem persists. I was just going to file a new bug when I found this one. I have a similar problem, but can extend it: - For me it only happens when the display scaling factor is not 100%, e.g. with 125%. Is it the same for you? - But then it happens in all KDE applications, not only KMail. I can see it in Konsole, Kate, Dolphin and many more, so it seems to be a platform problem, not an application problem. - It still happens with openSUSE Tumbleweed using KDE Plasma 5.27.3 and Frameworks 5.104.0. - The offset depends on the position of the application on the screen and is small when it is in the upper left corner and gets larger when it is in the lower right corner. Can you confirm this in your setup? Added an attachment showing this on Kate. The cursor should be at the end of the selection area, but it is somewhere in the middle. Created attachment 157544 [details]
Kate with selected text showing offset between cursor and selected area
(In reply to kde from comment #7) > - For me it only happens when the display scaling factor is not 100%, e.g. > with 125%. Is it the same for you? > - But then it happens in all KDE applications, not only KMail. I can see it > in Konsole, Kate, Dolphin and many more, so it seems to be a platform > problem, not an application problem. > - It still happens with openSUSE Tumbleweed using KDE Plasma 5.27.3 and > Frameworks 5.104.0. > - The offset depends on the position of the application on the screen and is > small when it is in the upper left corner and gets larger when it is in the > lower right corner. > > Can you confirm this in your setup? Can reproduce all of what you described in Arch with KDE Plasma 5.27.4. So it seem a problem with a KDE application (that doesn't happen in firefox, xournal++ for examples) with scaling in X11. Possibly multiplying for the scaling factor an already scaled cursor position. |