https://bugs.winehq.org/show_bug.cgi?id=56911
--- Comment #5 from David Bitterlich maxmueller485@web.de --- I don't know if we are talking about the same...
So my question is: The Mono repository you are hosting here on Wine's Gitlab, is it supposed to work on Wine/Windows only, or is it intended to be usable on Linux, too (compiled from source of course)?
The official Mono GitHub repository seems to be dead and in this repository there is atleast a little bit of activity.
So... my issue does happen with Mono on Linux directly without using Mono compiled for Wine. The last official Mono build, based on 2020 6.12.0 branch did not have this issue and commit 60da71f0 seems to have introduced this issue. This commit is included in your Gitlab version of the Mono repository - and I can reproduce this issue with both the latest GitHub version from Mono (6.13) and the latest GitLab version from here (also 6.13).
This Bugzilla tracker is for the Mono project you are hosting on GitLab. I have been able to select Mono as affected product, System.Windows.Forms as affected component, main as the current repository and Linux x86-64 as hardware/os platform. My problem clearly comes from a component of Mono running on Linux x86-64.
In my opinion it is useful to compare mono versions to find out the guilty commit that introduced an issue into a component of mono - atleast if you are developing on the codebase of Mono in all its glory.
Btw when I throw my compilated application to windows, it simply works and I cannot reproduce the issue there... So right click on a PictureBox -> click on the contextMenuItem works and the ContextMenuItemStrip has a SourceControl that is not null.