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(a)winehq.org
Reporter: ncguilbeault(a)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!
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51537
Bug ID: 51537
Summary: Mouse does not work in civilization VI
Product: Wine
Version: 6.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: voker57(a)gmail.com
Distribution: ---
Created attachment 70376
--> https://bugs.winehq.org/attachment.cgi?id=70376
complete log
Mouse does not work in Sid Meier's Civilization VI, menu loads but it is not
possible to do anything further.
This comment https://bugs.winehq.org/show_bug.cgi?id=49315#c9 suggests a cause
of this bug.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58227
Bug ID: 58227
Summary: xEdit require ITextRange::MoveEnd support for
tomCharFormat
Product: Wine
Version: 10.7
Hardware: x86-64
URL: https://github.com/TES5Edit/TES5Edit
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: lorenzofer(a)live.it
Distribution: ---
When loading xEdit 4.1.5j(editor and viewer for Bethesda games and mods,
application is also called tes4edit, tes5edit ,etc depending on the game mod)
the program try to show a changelog of the application version.
With wine the application give a Not Implemented Error and while the changelog
is shown the Table of Content is empty.
The application is using RichEdit controls trought the msftedit.dll, using
native dll workaround this issue.
The application is using ITextRange::MoveEnd to have a range of the editor
containing the full text with bold and bigger text (the paragraph titles of the
changelog)
Turn out msftedit on windows don't rely on riched20 like wine dll does. The
error was a bit confusing at first and using native riched20 wasn't a solution
(actually was breaking the entire widget).
Before discovering the msftedit workaround I tried to make a crude
implementaton that while do works, opening the application in winxp
compatibility mode give the same TOC then using native msftedit (but there is a
slight difference when using windows 10 mode), it's abysmally slow (20-30
seconds to create the TOC)
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58226
Bug ID: 58226
Summary: Warnings and notes when compiling from source on Arch
Linux (GCC 15.1.1 20250425)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: joni.hilger(a)yahoo.de
Distribution: ---
Created attachment 78547
--> http://bugs.winehq.org/attachment.cgi?id=78547
Full log of the build (gzip because of size)
Hi,
when compiling wine from up to date sources (taken from Gitlab today
2025-05-13)
I get a few warnings (see wine-build-full.log.gz)
This is how I build it:
CFLAGS="-march=native -O3 -pipe -fno-plt -fexceptions \
-Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security \
-fstack-clash-protection -fcf-protection -ffat-lto-objects"
CXXFLAGS="$CFLAGS -Wp,-D_GLIBCXX_ASSERTIONS"
LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now \
-Wl,-z,pack-relative-relocs"
# Apply flags for cross-compilation
export CROSSCFLAGS="-O2 -pipe -g"
export CROSSCXXFLAGS="-O2 -pipe -g"
export CROSSLDFLAGS="-Wl,-O1"
../wine/configure \
--prefix=/usr \
--libdir=/usr/lib \
--with-x \
--with-wayland \
--with-gstreamer \
--enable-win64
make
../wine/configure \
--prefix=/usr \
--libdir=/usr/lib \
--with-x \
--with-wayland \
--with-gstreamer \
--with-wine64="$srcdir/$pkgname-64-build"
make
Made the following greps to have more focused logs (thought it might help):
grep -C 5 "note: " wine-build-full.log > wine-build-grepped-notes.log
grep -C 5 "warning: " wine-build-full.log > wine-build-grepped-warnings.log
(full log is called wine-build-full.log.gz)
Thank you for your help!
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=17124
Summary: MSYS installer doesn't pop up cmd window?
Product: Wine
Version: 1.1.13
Platform: Other
URL: http://www.mingw.org/wiki/msys
OS/Version: other
Status: NEW
Keywords: download, Installer, source
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
When install msys, it floods the terminal with:
This is a post install process that will try to normalize betweenyour MinGW
install if any as well as your previous MSYS installs if any. I don't have any
traps as aborts will not hurt anything.Do you wish to continue with the post
install? [yn ] pi.sh: [: ==: unary operator expectedDo you have MinGW
installed? [yn ] pi.sh: [: ==: unary operator expectedWhen you install MinGW I
suggest you install it to C:/mingw(replace C: with the drive of your choice).
Then create an/etc/fstab file with a line that has a value similar to:C:/mingw
/mingwPress ENTER to continue Normalizing your MSYS environment.You
have script /bin/awkYou have script /bin/cmdYou have script /bin/echoYou have
script /bin/egrepYou have script /bin/exYou have script /bin/fgrepYou have
script /bin/printfYou have script /bin/pwdYou have script /bin/rviYou have
script /bin/rviewYou have script /bin/rvimYou have script /bin/viYou have
script /bin/viewMinGW-1.1 has a version of make.exe within it's bin/
directory.Please be sure to rename this file to mingw32-make.exe once youve
echo installed MinGW-1.1 because it\s very deficient in function.Press ENTER to
continue.C:\msys\1.0\postinstall>pause
Press Return key to continue:
Towards the end. It looks like something that should be in a cmd prompt
(haven't tested on windows yet). The line endings are also wrong, but that's
another bug.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=15949
Summary: MSYS does not integrate with MinGW install correctly
Product: Wine
Version: 1.1.8
Platform: Other
OS/Version: other
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jeffz(a)jeffz.name
Installing MSYS after MinGW on windows sets things up so that the existing
MinGW install integrates with MSYS, whereby /mingw from the MSYS shell points
to the MinGW install.
First download:
wget
http://downloads.sourceforge.net/mingw/MinGW-5.1.4.exe?modtime=1209244789&b…
run MinGW-5.1.4.exe with all defaults.
Second download:
wget
http://downloads.sourceforge.net/mingw/MSYS-1.0.10.exe?modtime=1079444447&b…
run wineconsole cmd (required because Wine doesn't launch a console window like
windows does)
MSYS-1.0.10.exe
Answer the defaults to the prompted questions on the console window before the
installer finishes (it pauses there)
wine cmd /c c:\msys\1.0\msys.bat
Typing 'gcc' in the msys terminal echos "sh: gcc: command not found", whereas
on windows it says gcc.exe: no input files.
On windows within msys, `ls /mingw` lists the contents of C:\mingw, on Wine
/mingw is empty.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54567
Bug ID: 54567
Summary: comdlg32: Find/Replace: Flags became invalid after
EN_KILLFOCUS.
Product: Wine
Version: 8.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: katayama.hirofumi.mz(a)gmail.com
Distribution: ---
Created attachment 74109
--> https://bugs.winehq.org/attachment.cgi?id=74109
the patch to fix this bug
The flags value became invalid after EN_KILLFOCUS.
It caused a bug that FR_DOWN is cleared when the user set focus to edt1 and
close the find/replace dialog.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56093
Bug ID: 56093
Summary: msys/pacman: fails with "fixup_mmaps_after_fork:
VirtualQueryEx failed"
Product: Wine
Version: 9.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Updating a msys2 installation via "pacman -Suy" fails in below way.
This is a result of the parent process doing a DuplicateHandle with
PROCESS_QUERY_LIMITED_INFORMATION and inheriting this to the forked process.
This fork tries to recreate the mappings of the parent but fails
the VirtualQueryEx call with this inherited handle of the parent process.
It does fail because in wine it leads to a call to get_process_from_handle
with PROCESS_QUERY_INFORMATION which the handle was not created with.
msys2 does intentionally use PROCESS_QUERY_LIMITED_INFORMATION instead
of PROCESS_QUERY_INFORMATION with DuplicateHandle on windows 8.1 and up.
wine bash.exe --login
pacman -Suy
0 [main] pacman 1051 fixup_mmaps_after_fork: VirtualQueryEx failed for
MAP_PRIVATE address 0x6FFFFFFF0000, Win32 error 5
562 [main] pacman 1051 C:\msys64\usr\bin\pacman.exe: *** fatal error in
forked process - recreate_mmaps_after_fork_failed
In the parent process:
https://github.com/msys2/msys2-runtime/blob/msys2-3.4.10/winsup/cygwin/sigp…
In the child process:
https://github.com/msys2/msys2-runtime/blob/msys2-3.4.10/winsup/cygwin/mm/m…
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56925
Bug ID: 56925
Summary: msys2-64/cygwin64: unlink of read-only file fails
Product: Wine
Version: 9.12
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Created attachment 76744
--> https://bugs.winehq.org/attachment.cgi?id=76744
A few notes and backtraces in wine and cygwin.
In another attempt to check the state of msys2 or cygwin I found following
issue trying to update a msys2-64 installation:
# LANG=C pacman -Suy
:: Synchronizing package databases...
...
warning: could not remove lock file /var/lib/pacman/db.lck
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
...
A simpler version to reproduce is this:
rm -f test.txt
LANG=C wine cmd
echo test > test.txt
attrib +r test.txt
c:\msys64\usr\bin\rm.exe -f -v test.txt
Returns:
/usr/bin/rm: cannot remove 'test.txt': Permission denied
This tests were done with a wine tree including patches for this bugs:
52105
55138
53574
54995
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58225
Bug ID: 58225
Summary: Using winecfg to change a Desktop Integration setting
and applying throws a "pack_message msg 14
(WM_ERASEBKGND) not supported yet" fixme.
Product: Wine
Version: 10.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: reelix(a)gmail.com
Distribution: ---
1.) Launch winecfg
2.) Navigate to the "Desktop Integration" tab
3.) Alter any setting (Eg: Theme, WinRT Theme, Font Size)
4.) Hit Apply
5.) Notice the fixme message in the Console
00f8:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
Whilst I normally wouldn't create a bug report for a specific fixme, a fixme
appearing in the winecfg tool itself is rather unusual, and far easier to
navigate.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.