http://bugs.winehq.org/show_bug.cgi?id=58211
Bug ID: 58211 Summary: Bonsai-Rx Application Crashes Due to TREEVIEW_DoSelectItem Assertion Product: Wine Version: 10.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs@winehq.org Reporter: ncguilbeault@gmail.com Distribution: ---
Created attachment 78524 --> http://bugs.winehq.org/attachment.cgi?id=78524 Crash log when launching Bonsai main editor or package manager
Hi there, and thank you for all the amazing work on Wine!
I'm a relatively new user and have encountered an issue when running a Windows application called Bonsai-Rx under Wine. Bonsai-Rx is a C#/.NET-based application widely used in neuroscience research. Traditionally, Bonsai running on Linux has relied on Mono, but I’m exploring the possibility of running Bonsai using Wine instead.
System Details: Wine version: Built from source (latest master, 10.7) using Shared-WoW64 instructions Bonsai version: Installed from official site (latest, 2.8.5): https://bonsai-rx.org/docs/articles/installation.html Wine prefix setup: .NET Framework 4.8 installed via winetricks -q dotnet48 System: Ubuntu 24.04, x86_64, kernel 6.8.0-59-generic
The Issue: Bonsai installs and launches correctly. The welcome menu displays, but selecting any option that would launch the main editor window or the package manager (e.g., New File, Open File, Manage Packages, etc.) causes the application to crash due to an assertion in the function:
`TREEVIEW_DoSelectItem(TREEVIEW_INFO *infoPtr, INT action, HTREEITEM newSelect, INT cause)`
Observations: If I comment out the assertion line in the above function and rebuild Wine, Bonsai functionality works as expected.
I’ve tested several native DLL overrides (comctl32, comdlg32, vcrun6) without success.
The issue persists in multiple Wine versions (10.3 through 10.7).
Questions: What are the implications of removing this assertion in TREEVIEW_DoSelectItem?
Could this point to a misbehaviour in Bonsai, or is it a Wine edge case that should be handled more gracefully?
Is there a better workaround or fix for ensuring compatibility with this application?
I’ve attached the full error stack trace for reference. Any guidance or insights would be greatly appreciated.
Thanks again for your time and your excellent work!