Bug 399234 - Compositing breaks system tray functionality in programs running under Wine Staging
Summary: Compositing breaks system tray functionality in programs running under Wine S...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: XembedSNIProxy (show other bugs)
Version: master
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
: 399125 402920 411502 418831 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-09-30 06:01 UTC by Guilherme Silva
Modified: 2022-06-30 12:33 UTC (History)
20 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.17.1


Attachments
Calculate first clickable point, from the top-left (5.42 KB, patch)
2019-07-25 16:06 UTC, Konrad Materka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Guilherme Silva 2018-09-30 06:01:36 UTC
SUMMARY
Any program running under Wine Staging that uses the system tray will not work properly when you right/left mouse click that program's icon.

STEPS TO REPRODUCE
1. Enable KWin compositing;
2. Download this test program (SHA-1: 63ae606aee64259091e7f82436d4ecdf3a6e9047): https://www.nirsoft.net/utils/tflash210.zip
3. Run the .exe with Wine Staging; (vanilla Wine will _not_ work!)

OBSERVED RESULT
Interacting with the blue round icon that was added to the system tray does absolutely nothing, i.e. the context menu won't show up after you right click it. Left clicking is supposed to change the icon to a different one, but it doesn't.

EXPECTED RESULT
The context menu window should pop-up after you right click the program's icon in system tray and left clicking it should change the icon.

SOFTWARE VERSIONS
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
There's a silly workaround to this:

1. Disable compositing (Alt+Shift+F12);
2. Run the desired program with Wine Staging;
3. Enable compositing again (Alt+Shift+F12);
4. Right/left clicking the tray icon works as expected now.

I've reported this to the Wine Staging team as well (relevant details here: https://bugs.winehq.org/show_bug.cgi?id=45899). In my tests on virtual machines using different desktop environments (MATE, Cinnamon, XFCE), KDE was the only one in which I was able to reproduce this bug. A Wine Staging developer then suggested me to report it to you guys.

Thank you!
Comment 1 gbr 2018-09-30 06:27:20 UTC
*** Bug 399125 has been marked as a duplicate of this bug. ***
Comment 2 Kai Uwe Broulik 2018-10-01 07:19:34 UTC
What happens if you quit xembedsniproxy?
Comment 3 hexchain 2018-10-01 09:27:31 UTC
If I kill xembedsniproxy, a small wine tray window containing the icon of the wine application appears.
Comment 4 Kai Uwe Broulik 2018-10-01 11:00:12 UTC
It seems Wine staging sets a window mask on the SNI depending on the icon. Since the icon is a circle, our emulated mouse click at the top left of the window ends up "clicking through".
Comment 5 Zeb Figura 2018-11-14 04:19:52 UTC
(In reply to Kai Uwe Broulik from comment #4)
> It seems Wine staging sets a window mask on the SNI depending on the icon.
> Since the icon is a circle, our emulated mouse click at the top left of the
> window ends up "clicking through".

Is this something that can/should be fixed on the KDE end?
Comment 6 Kai Uwe Broulik 2019-01-09 14:45:50 UTC
*** Bug 402920 has been marked as a duplicate of this bug. ***
Comment 7 kerozoli 2019-01-17 20:05:05 UTC
I could repro this issue (and the "silly" workaround) with blizzard client on wine staging and latest KDE Neon (Plasma 5.14.5, Frameworks:5.54 qt:5.11.2)
Thanks
Comment 8 Solerman Kaplon 2019-01-28 13:23:34 UTC
Looks like using stable wine 4.0 and not staging works. So wine-staging bug then?
Comment 9 kerozoli 2019-02-01 12:40:45 UTC
(In reply to Solerman Kaplon from comment #8)
> Looks like using stable wine 4.0 and not staging works. So wine-staging bug
> then?

Not sure because other desktops with composition works wit the same wine-staging (e.g. Gnome)
Comment 10 fresa 2019-02-17 06:42:04 UTC
fedora 29 kde 5.13.5 same problem with wine version>3.16
Comment 11 Tom Englund 2019-03-02 14:56:45 UTC
still happends with plasma 5.15.2 and wine staging 4.2 on archlinux
Comment 12 Konrad Materka 2019-07-19 21:03:07 UTC
I found few interesting things but I need a help from a more experienced developer.


1. Kai Uwe Broulik was right:
<< It seems Wine staging sets a window mask on the SNI depending on the icon. Since the icon is a circle, our emulated mouse click at the top left of the window ends up "clicking through".>>

He is right. In the file sniproxy.cpp (https://github.com/KDE/plasma-workspace/blob/master/xembed-sni-proxy/sniproxy.cpp), whhen I added:
  configVals[0] -= clientGeom->width / 2;
  configVals[1] -= clientGeom->height / 2;
before line 491:
  xcb_configure_window(c, m_containerWid, XCB_CONFIG_WINDOW_X | XCB_CONFIG_WINDOW_Y, configVals);
context menu appeared. Now it clicks in the middle of the tray icon limiting a problem of transparent icons.

2. That was half of the success. The second issue is very tricky, I was not able to find satisfying workaround. Right click sends 2 "ContextMenu" signals, not one. As a result two clicks are emulated.
First signal is send on mouse down event.
Second signal is send on mouse up event or after around 1 second, depending on which is earlier.
For some reason wine doe not like that. Menu appears but it's not possible to click anything. I found two ugly workarounds:
2.1 Right click and hold mouse button. When menu appears, before 1 second passes, quickly move mouse pointer outside of icon area. This prevents second event (mouse up) and second emulated click to be send.
2.2 Add "QThread::sleep(10);" somewhere in the "sendClick" function. 10 miliseconds is enough, but this is ugly as hell and very unreliable - sometimes menu appears, sometimes after few seconds. Anyway, maybe this will give a clue and help someone to find correct fix.
Comment 13 Zeb Figura 2019-07-19 21:11:41 UTC
(In reply to Konrad Materka from comment #12)
> 1. Kai Uwe Broulik was right:
> << It seems Wine staging sets a window mask on the SNI depending on the
> icon. Since the icon is a circle, our emulated mouse click at the top left
> of the window ends up "clicking through".>>
> 
> He is right. In the file sniproxy.cpp
> (https://github.com/KDE/plasma-workspace/blob/master/xembed-sni-proxy/
> sniproxy.cpp), whhen I added:
>   configVals[0] -= clientGeom->width / 2;
>   configVals[1] -= clientGeom->height / 2;
> before line 491:
>   xcb_configure_window(c, m_containerWid, XCB_CONFIG_WINDOW_X |
> XCB_CONFIG_WINDOW_Y, configVals);
> context menu appeared. Now it clicks in the middle of the tray icon limiting
> a problem of transparent icons.

Not that I've touched KDE, ever, or know anything about these components, but it strikes me as the sort of thing where that kind of mouse click shouldn't be emulated at all, at least, not if the icon mask can't be depended on to cover the top left pixel (or, indeed, any given pixel).
Comment 14 Solerman Kaplon 2019-07-20 12:08:48 UTC
Testing the example program and also other non-rectangular icons on windows 10, the click works anywhere, not just in the visible icon. It seems there isn't any non-rectangular mask applied
Comment 15 Solerman Kaplon 2019-07-20 12:14:32 UTC
I think the correct fix would be to grab the x/y where the mouse was clicked and send it straight to wine so they handle the mask themselves. Maybe some client-to-absolute -> absolute-to-client translation might be needed
Comment 16 Konrad Materka 2019-07-25 15:52:30 UTC
@Solerman, yes that would be the best solution but it is not that easy to get relative coordinate (if it is even possible).

I found a workaround, I'm working on the patch.


BTW, Wine bug is here:
https://bugs.winehq.org/show_bug.cgi?id=45899
Comment 17 Konrad Materka 2019-07-25 16:06:49 UTC
Created attachment 121728 [details]
Calculate first clickable point, from the top-left

Wine is using XWindow Shape Extension for transparent tray icons. We need to find first clickable point starting from top-left. This patch adds this feature.
Comment 18 Konrad Materka 2019-07-26 19:22:07 UTC
Review request:
https://phabricator.kde.org/D22767
Comment 19 David Edmundson 2019-08-28 14:12:10 UTC
Git commit 989a7759a969c7b4dd677e5e1944d849a72450fa by David Edmundson, on behalf of Konrad Materka.
Committed on 28/08/2019 at 14:11.
Pushed by davidedmundson into branch 'master'.

Calculate first clickable point, from the top-left

Summary:
Wine is using XWindow Shape Extension for transparent tray icons.
We need to find first clickable point starting from top-left.

Test Plan:
Bug fix test:
1. Enable KWin compositing;
2. Download this test program (SHA-1: 63ae606aee64259091e7f82436d4ecdf3a6e9047): https://www.nirsoft.net/utils/tflash210.zip
3. Run the .exe with Wine **Staging**
4. Right click on the icon
5. Context menu should show

Regression test:
1. Run XChat
2. Right click
3. Context menu should show in the same place as without patch

Reviewers: davidedmundson, #plasma_workspaces

Reviewed By: davidedmundson, #plasma_workspaces

Subscribers: davidedmundson, plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D22767

M  +52   -6    xembed-sni-proxy/sniproxy.cpp
M  +2    -0    xembed-sni-proxy/sniproxy.h

https://commits.kde.org/plasma-workspace/989a7759a969c7b4dd677e5e1944d849a72450fa
Comment 20 kerozoli 2019-08-29 17:29:08 UTC
I just tested the fix with battle.net (running on staging wine) and it works.
Thanks
Comment 21 Nate Graham 2019-09-03 20:20:54 UTC
*** Bug 411502 has been marked as a duplicate of this bug. ***
Comment 22 Coty Ternes 2019-10-31 01:25:37 UTC
I've been having this problem for a bit, and went through the same steps to reproduce and am getting this issue currently. I can take the same steps to work around it luckily.

Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.1
KDE Frameworks Version: 5.63.0
Qt Version: 5.13.1
Kernel Version: 5.3.7-2-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz
Memory: 15.6 GiB of RAM
Comment 23 Konrad Materka 2019-10-31 08:42:15 UTC
(In reply to Coty Ternes from comment #22)
> I've been having this problem for a bit, and went through the same steps to
> reproduce and am getting this issue currently. I can take the same steps to
> work around it luckily.
Can you share more details and exact steps to reproduce? Which application? Wine version? Can you test application mentioned in the first comment (https://www.nirsoft.net/utils/tflash210.zip)?
Comment 24 Coty Ternes 2019-11-01 01:28:15 UTC
(In reply to Konrad Materka from comment #23)
> (In reply to Coty Ternes from comment #22)
> > I've been having this problem for a bit, and went through the same steps to
> > reproduce and am getting this issue currently. I can take the same steps to
> > work around it luckily.
> Can you share more details and exact steps to reproduce? Which application?
> Wine version? Can you test application mentioned in the first comment
> (https://www.nirsoft.net/utils/tflash210.zip)?

I have compositing enabled, open an .exe and try to interact with it's system tray icon, but nothing happens. I just tested with that tflash download and the issue is present. If I start it while compositing is disabled then I can interact with the icon.
I am having this issue with my Roboform password manager as well as various cryptocurrency wallets. I only use the Windows versions of some of the wallets because some cryptos only have Ubuntu optimized packages for their Linux build.
Wine version is 4.18-1. Just realized that I'm not using the staging version though which is what this bug is directed towards. Missed that detail because all the behavior for producing this bug and working around it is exactly the same.
Comment 25 Konrad Materka 2019-11-03 10:38:18 UTC
(In reply to Coty Ternes from comment #24)
> I have compositing enabled, open an .exe and try to interact with it's
> system tray icon, but nothing happens. I just tested with that tflash
> download and the issue is present. If I start it while compositing is
> disabled then I can interact with the icon.
I need some logs to get rough idea what is happening. Can you:
1. kill xembedsniproxy
2. run xembedsniproxy in terminal, with logging enabled:
QT_LOGGING_RULES="*kde*=true" xembedsniproxy
3. run tflash.exe (with compositing enabled)
4. click it few times (left and right click)
5. kill tflash.exe, disable compositor, repeat steps 4 and 5
6. Send me the logs (console output)

> Wine version is 4.18-1. Just realized that I'm not using the staging version
This bug was about Staging version only, but let's check you problem to.
Comment 26 Konrad Materka 2019-11-28 17:55:33 UTC
Coty Ternes, can you provide answers to the questions from the comment above?
Comment 27 Eliphas 2019-11-28 19:15:07 UTC
Hi, I came here because I have the same problem but maybe not same versions as the bug. As your last request for feedback has 20+ days, Maybe some feedback from my system can help you.

KDE neon Testing Edition 18.04 fully updated
wine-development 3.6-1

eliphas@T410:~$ QT_LOGGING_RULES="*kde*=true" xembedsniproxy
kde.xembedsniproxy: starting
kde.xembedsniproxy: Manager selection claimed
org.kde.kwindowsystem: Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemX11Plugin.so" for platform "xcb"

XXX Starting wine tflash.exe with compositing enabled, icon is round blue with an "F"

kde.xembedsniproxy: trying to dock window  65011722
kde.xembedsniproxy: adding damage watch for  65011722
kde.xembedsniproxy: Received click 1 with passed x*y 1158 1582
kde.xembedsniproxy: Click point: QPoint(4,4)
kde.xembedsniproxy: Received click 3 with passed x*y 1158 1582
kde.xembedsniproxy: Click point: QPoint(4,4)
kde.xembedsniproxy: trying to undock window  65011722

XXX Ended wine with ^C, start again with compositing disabled, icon is only a square

kde.xembedsniproxy: trying to dock window  65011720
kde.xembedsniproxy: adding damage watch for  65011720
kde.xembedsniproxy: Received click 1 with passed x*y 1156 1583
kde.xembedsniproxy: Received click 3 with passed x*y 1156 1583
kde.xembedsniproxy: Resizing window 65011720 "" from w*h QSize(-1, -1)
kde.xembedsniproxy: Skip NULL image returned from xcb_image_get() for 65011720 ""
kde.xembedsniproxy: No xembed icon for 65011720 ""
kde.xembedsniproxy: trying to undock window  65011720
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 730, resource id: 65011720, major code: 25 (SendEvent), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 731, resource id: 65011720, major code: 12 (ConfigureWindow), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 152 (Unknown), sequence: 741, resource id: 33554441, major code: 143 (Unknown), minor code: 3

XXX Ended with right click context menu and exit
Comment 28 Konrad Materka 2019-11-28 22:02:14 UTC
Hi Eliphas,

You are using very old Wine version, uninstall it and install from:
https://wiki.winehq.org/Ubuntu

Can you explain what does it mean "I have the same problem"? I assume that with compositor enabled clicks are not working and click are working with compositor disabled?

From logs I can see that clicks are sent... The coordinates are strange - is your monitor rotated?

I will try to add one more fix in Plasma 5.17.4, can you retest then?
Comment 29 Eliphas 2019-11-28 22:21:25 UTC
(In reply to Konrad Materka from comment #28)
> Hi Eliphas,
> 
> You are using very old Wine version, uninstall it and install from:
> https://wiki.winehq.org/Ubuntu

I am using the wine-development from default stable LTS, when I tried to install the winehq staging it wanted some dependency from another repo (libfaudio0 from SDL I think) and I wanted to stay "stable" if you may have wanted me to do more tests with this version because that bug looks like the same and affecting the mainstream LTS (with not-so-mainstream KDE from Neon Testing Edition). Will enable the repos and retest.

> Can you explain what does it mean "I have the same problem"? I assume that
> with compositor enabled clicks are not working and click are working with
> compositor disabled?

Yes, exactly. Turning composite off before a wine program launch makes the systray icon work.

> From logs I can see that clicks are sent... The coordinates are strange - is
> your monitor rotated?

Oh sorry about that. Yes, I have a 1440x900 in normal mode (where the kde taskbar/systray are) and a 900x1600 rotated on the right side.

> I will try to add one more fix in Plasma 5.17.4, can you retest then?

Sure, will install wine-staging from winehq and will disable secondary monitor when testing. Can retest it in about 12hs on that machine (will refresh pkgs and reboot before the test).
Comment 30 Konrad Materka 2019-11-28 22:59:14 UTC
(In reply to Eliphas from comment #29)
> I am using the wine-development from default stable LTS, when I tried to
> install the winehq staging it wanted some dependency from another repo
> (libfaudio0 from SDL I think)
Oh, I remember! Yes, you need to install libfaudio0 first. Unfortunately Ubuntu 18.04 does not have it, I just installed deb packages manually, both i386 and amd64 are required.
Anyway, I tested with wine-development, no difference on my computer so most probably it is not related to Wine version. The original report was for Wine Staging, but your problem is different.

> > From logs I can see that clicks are sent... The coordinates are strange - is
> > your monitor rotated?
> 
> Oh sorry about that. Yes, I have a 1440x900 in normal mode (where the kde
> taskbar/systray are) and a 900x1600 rotated on the right side.

I was not able to reproduce, but maybe it is somehow related to multi-monitor setup?
Click coordinates are: x:1156, y:1583 (where (0,0) is in the top-left corner).
x:1156 seems fine, it is less than 1440. But y:1583 is weird, definitely more than 900 from the first screen, more likely it is a coordinate from the second screen. Is it possible that these two overlap? Can you share output from: "kscreen-doctor -o" command?
Can you retest (with logs enabled) with second screen disabled, different panel locations etc? Just to get some use case when it is working and when not. This will probably mess with your setup and layout, sorry for that. To fix this I really need to reproduce it locally and without detailed information I can only guess.
Comment 31 Eliphas 2019-11-29 13:22:56 UTC
(In reply to Konrad Materka from comment #30)
> Anyway, I tested with wine-development, no difference on my computer so most
> probably it is not related to Wine version. The original report was for Wine
> Staging, but your problem is different.

> I was not able to reproduce, but maybe it is somehow related to
> multi-monitor setup?

Was that exactly! Thank you for the nudge in the right direction!

> Click coordinates are: x:1156, y:1583 (where (0,0) is in the top-left
> corner).
> x:1156 seems fine, it is less than 1440. But y:1583 is weird, definitely
> more than 900 from the first screen, more likely it is a coordinate from the
> second screen. Is it possible that these two overlap? Can you share output
> from: "kscreen-doctor -o" command?
> Can you retest (with logs enabled) with second screen disabled, different
> panel locations etc? Just to get some use case when it is working and when
> not. This will probably mess with your setup and layout, sorry for that. To
> fix this I really need to reproduce it locally and without detailed
> information I can only guess.

The logs where more of the same with only the coordinates changing. But one thing that I missed before: the FIRST click gets through! I noted that the "F" changed in the first, but the other clicks are all misses.

Secondary on my normal setup:

kde.xembedsniproxy: Received click 1 with passed x*y 2754 883 WORKS!
kde.xembedsniproxy: Click point: QPoint(4,4)
kde.xembedsniproxy: Received click 1 with passed x*y 2754 883
kde.xembedsniproxy: Click point: QPoint(4,4)
kde.xembedsniproxy: Received click 3 with passed x*y 2754 883
kde.xembedsniproxy: Click point: QPoint(4,4)
kde.xembedsniproxy: trying to undock window  92274698

After disabling secondary

kde.xembedsniproxy: trying to dock window  92274698
kde.xembedsniproxy: adding damage watch for  92274698
kde.xembedsniproxy: Received click 1 with passed x*y 1154 885
kde.xembedsniproxy: Click point: QPoint(4,4)
kde.xembedsniproxy: Received click 1 with passed x*y 1154 885
kde.xembedsniproxy: Click point: QPoint(4,4)
kde.xembedsniproxy: Received click 1 with passed x*y 1154 885
kde.xembedsniproxy: Click point: QPoint(4,4)

The top (0,0) of the secondary monitor is not in the same horizon as the primary, that is the problem. When I test with only primary monitor, or secondary-just-right (1440x900+1600x900) or even just put the secondary top left just left (the 0,901px is 0,0 secondary) the systray works fine.

When secondary is put on the left side (1600x900+1440x900) the problem occurs again.

The primary is always the 1440x900 laptop screen.

This is the output of kscreen-doctor with my default setup (1440x900+900x1600). 

Output: 65 LVDS-1 enabled connected primary Panel Modes: 100:1024x576@120 101:1024x576@60 102:1024x576@60 103:960x600@120 104:960x600@120 105:960x540@120 106:960x540@120 107:960x540@60 108:960x540@60 109:800x600@120 110:800x600@60 111:800x600@56 112:840x525@120 113:840x525@120 114:864x486@60 115:864x486@60 116:800x512@120 117:700x525@120 118:800x450@120 119:800x450@120 120:640x512@120 121:720x450@120 122:700x450@120 123:700x450@120 124:640x480@120 125:640x480@60 126:720x405@60 127:720x405@59 128:684x384@120 129:684x384@120 130:680x384@120 131:680x384@120 132:640x400@120 133:640x400@120 134:576x432@120 135:640x360@120 136:640x360@120 137:640x360@60 138:640x360@59 139:512x384@120 140:512x288@120 141:512x288@120 142:480x270@119 143:480x270@120 144:400x300@121 145:400x300@113 146:432x243@120 147:432x243@119 148:320x240@120 149:360x202@119 150:360x202@118 151:320x180@120 152:320x180@119 74:1440x900@60*! 75:1440x900@50 76:1440x900@60 77:1400x900@60 78:1400x900@60 79:1440x810@120 80:1440x810@120 81:1368x768@60 82:1368x768@60 83:1360x768@60 84:1360x768@60 85:1280x800@120 86:1280x800@120 87:1280x800@60 88:1280x800@60 89:1152x864@60 90:1280x720@120 91:1280x720@120 92:1280x720@60 93:1280x720@60 94:1024x768@120 95:1024x768@60 96:960x720@120 97:928x696@120 98:896x672@120 99:1024x576@120 Geometry: 0,700 1440x900 Scale: 1 Rotation: 1 primary
Output: 66 VGA-1 disabled disconnected  VGA Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1
Output: 67 HDMI-1 disabled disconnected  HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1
Output: 68 DP-1 disabled disconnected  DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1
Output: 69 HDMI-2 enabled connected  HDMI Modes: 110:800x600@60 111:800x600@56 125:640x480@60 153:1600x900@60*! 154:1280x1024@60 155:1440x900@60 156:1152x864@75 157:1024x768@75 158:832x624@75 159:800x600@75 160:640x480@75 161:720x400@70 95:1024x768@60 Geometry: 1440,0 900x1600 Scale: 1 Rotation: 8
Output: 70 HDMI-3 disabled disconnected  HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1
Output: 71 DP-2 disabled disconnected  DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1
Output: 72 DP-3 disabled disconnected  DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1

Anyway, now that this proved to be unrelated with the initial title this should be in another bug right?
Comment 32 Konrad Materka 2019-11-29 18:37:34 UTC
> Anyway, now that this proved to be unrelated with the initial title this
> should be in another bug right?

Yes, please file a separate report, we will continue there.
One note before doing so: I noticed that left click works but icon is not refreshed. This should be fixed in 5.17.4 (BUG 356937). To be sure just use right click (or left click and then right click - it will refresh the icon).
Comment 33 Konrad Materka 2019-11-29 18:42:53 UTC
BTW, I hoped that kscreen-doctor output will tell me everything but it is too complicated :) Can you share a screenshot of your monitors configuration? The one when it is not working (I guess it is when monitor is rotated).
Is the rotation done in the configuration or automatically by the hardware?
Comment 34 Eliphas 2019-11-29 20:23:32 UTC
Hi! Added screenshot on bug #414667, thank you.
Layout and rotation are done by the Display Configuration app.
Comment 35 Wolfgang Bauer 2020-03-15 12:07:09 UTC
*** Bug 418831 has been marked as a duplicate of this bug. ***