https://bugs.winehq.org/show_bug.cgi?id=55242
Bug ID: 55242
Summary: iperf 2.0.8 will not quit with CTRL+C
Product: Wine
Version: 8.12
Hardware: x86-64
URL: https://web.archive.org/web/20190523161058/https://ipe
rf.fr/download/windows/iperf-2.0.8-win32.zip
OS: Linux
Status: NEW
Keywords: download, source
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: Ubuntu
When iperf is run in dual mode it will not exit after hitting CTRL+C.
$ wine iperf.exe -c 127.0.0.1 -d -t 1 -P 5
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
connect failed: Connection refused
------------------------------------------------------------
connect failed: Connection refused
Server listening on TCP port 5001
TCP window size: 128 KByte (default)
------------------------------------------------------------
connect failed: Connection refused
------------------------------------------------------------
Client connecting to 127.0.0.1, TCP port 5001
connect failed: Connection refused
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[264] local 127.0.0.1 port 5001 connected with 127.0.0.1 port 53058
^CWaiting for server threads to complete. Interrupt again to force quit.
Pressing CTRL+C has no effect and the app has to be SIGKILLed.
$ sha1sum iperf-2.0.8-win32.zip
f312bf6ab7de3b1921cae7f4953aed0ce6b17afa iperf-2.0.8-win32.zip
iperf -s will exit with CTRL+C though. It also doesn't produce any "connection
failed" messages.
Source: https://iperf.fr/download/source/iperf-2.0.8-source.tar.gz
--
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=19661
Summary: Lotus Approach 3.1 causes a page fault on load
Product: Wine
Version: 1.1.27
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: win16
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
Created an attachment (id=22944)
--> (http://bugs.winehq.org/attachment.cgi?id=22944)
Wine 1.1.27 console output
Lotus Approach 3.1 causes a page fault on loading and has to be killed.
--
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=44476
Bug ID: 44476
Summary: winevdm crash during wizardry gold install
Product: Wine
Version: 2.0.3
Hardware: x86
OS: NetBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stanton_arch(a)mail.com
Created attachment 60426
--> https://bugs.winehq.org/attachment.cgi?id=60426
backtrace of crash
I'm trying to install wizardry gold and wine is crashing almost immediately
with apparent winevdm.exe errors.
I have the CD and copied it to my disk drive and tried running "wine
SETUP.EXE". I'm using NetBSD i386.
I also tried using wine 1.6.2 which failed also. It didn't crashed but seemed
to just hang.
--
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=53892
Bug ID: 53892
Summary: Page fault when attempting to run Calmira 3.3
Product: Wine
Version: 7.20
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: dos
Assignee: wine-bugs(a)winehq.org
Reporter: hjlinq(a)gmail.com
Distribution: ---
Created attachment 73435
--> https://bugs.winehq.org/attachment.cgi?id=73435
dump produced after the "winevdm.exe has encountered a serious error" message
WineVDM page faults when attempting to run the Calmira 3.3 setup program.
System: Fresh install of alpine-extended-3.16.2-x86.iso
Hardware: Virtualbox
To replicate:
1. Install Alpine linux (setup-alpine)
(Important: must be the x86 version since musl-libc doesn't support multilib)
2. In "/etc/apk/repositories",
uncomment the edge/main and edge/community repositories
and comment out both v3.16 repositories
3. apk -alU upgrade
4. setup-xorg-base
5. apk add xinit xterm xfce4 wine
6. echo "exec winecfg" > .xinitrc
7. startx
8. in the "Graphics" tab, check "Emulate a virtual desktop", click "Apply" and
"Ok"
9. echo "exec wine explorer" > .xinitrc
10. wget http://www.calmira.de/downloads/files/erwin/c33setup.exe
11. startx
12. navigate to c33setup.exe using wine explorer and double-click on the
installer
--
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=56593
Bug ID: 56593
Summary: The program winevdm.exe has encountered a serious
problem ...
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rquint(a)rain2.org
Distribution: ---
Using Wine 9.0 on a fresh install of Ubuntu 24.04 OED.EXE (The Oxford English
Dictionary version 1.14) was running without problems until this morning when
it crashed with the message "The program winevdm.exe has encountered a serious
problem needs to close." I am still able to run other old apps under Wine. I
have tried removing and reinstalling Wine and the OED with no change. I'm
attaching the details as "backtrace.txt"
--
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=49405
Bug ID: 49405
Summary: winevdm has encountered a serious problem
Product: Wine
Version: 5.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rquint(a)rain2.org
Distribution: ---
Created attachment 67480
--> https://bugs.winehq.org/attachment.cgi?id=67480
backtrace.txt generated by WINE
Please bear with this long discursive report.
I'm trying to run the CD-ROM version of the OED (Oxford English Dictionary), an
old Windows 3.1 app, under WINE.
Currently I have it running successfully on
Ubuntu 18.04
rquint@Maria-Agnesi:~$ uname -a
Linux Maria-Agnesi 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
rquint@Maria-Agnesi:~$ wine --version
wine-3.0 (Ubuntu 3.0-1ubuntu1)
Ubuntu 19.10
rquint@Cosmic-Box:~$ uname -a
Linux Cosmic-Box 5.3.0-59-generic #53-Ubuntu SMP Wed Jun 3 15:52:15 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
rquint@Cosmic-Box:~$ wine --version
wine-4.0.2 (Ubuntu 4.0.2-1)
and
Ubuntu 20.04
rquint@Twenty4:~$ uname -a
Linux Twenty4 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
rquint@Twenty4:~$ wine --version
wine-5.0 (Ubuntu 5.0-3ubuntu1)
On a second Ubuntu 20.04 installation the OED crashes
rquint@disco-box:~/.wine/drive_c/Program Files/OED$ uname -a
Linux disco-box 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
rquint@disco-box:~/.wine/drive_c/Program Files/OED$ wine --version
wine-5.0 (Ubuntu 5.0-3ubuntu1)
I'm attaching the backtrace.txt generated when it crashes as
backtrace.txt.disco-box. Also, it may be significant that when I first ran the
app on Twenty4, an almost identical backtrace.txt was generated, but despite
the usual definition of insanity, I tried starting it several times and after
three or four attempts it ran without problems.
--
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=56946
Bug ID: 56946
Summary: Include fixes for mmsystem.dll16 and user.dll16 from
WineVDM project
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: contact(a)jaybmusic.net
Distribution: ---
Hello!
I need to get old 16-bit software editors running on Linux / MacOS.
The programs in question:
https://www.jaybmusic.net/Downloads/X5D-Editor.zip (Korg SE05 Editor for
X5/D/R)
https://www.jaybmusic.net/Downloads/SED-02W.zip (Korg NS5R Editor)
The problems:
MIDI Out works with no issues. As soon as you open MIDI In it shows a "Not
Enough Memory" error.
The error log says:
00e0:fixme:winmm:MMSYSTDRV_Message NIY: no conversion yet 16->32 kind=1 msg=57
I reported this to the WineVDM project and they included a fix for the
mmsystem.dll16 code:
https://github.com/otya128/winevdm/pull/547/files
Another issue already fixed is linked to the GUI of the NS5R Editor where
window elements overlap and cause the program to crash eventually. This has
also been fixed in the user.dll16 code:
https://github.com/otya128/winevdm/pull/1239/files
Please merge these fixes into the official wine code so we can use these pieces
of old MIDI software properly. Thank you.
--
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=58301
Bug ID: 58301
Summary: SendInput(MOUSEEVENTF_MOVE) does nothing
Product: Wine
Version: 10.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: mornickmylo(a)gmail.com
Distribution: ---
I'm creating a game mod and I need to move cursor pointer with gamepad. I use
SendInput(MOUSEEVENTF_MOVE) to simulate mouse movement. It's working just fine
on Windows, but in Wine this call does nothing. I've created a simple example
app that moves cursor pointer upon keyboard events, and again, it works in
Windows but not in Wine.
I had a guess that this may be related to my system, not Wine, but ydotool
works correctly and moves mouse as expected.
I also checked if applications receive WM_MOUSEMOVE events when SendInput is
called, and it works too. But the pointer is not moving.
I've looked at Wine sources and found nothing related to uinput or XTest. Is
there any purpose behind this?
--
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=58332
Bug ID: 58332
Summary: ntdll: Session shared memory gets mapped with
MAP_PRIVATE, which causes rr-debugger to fail.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Debugging Wine with rr-debugger allows to record whole wine process trees,
and debug later different processes, e.g. wineserver and the .exe process,
debug early startup or exception code, debug in reverse and multiple times.
Therefore I asked for inclusion of [1] "spurious short writes",
which got accepted at 2025-04-25. Thank you very much for it.
Unfortunately short after it I found there is still an issue,
which was a few months not there.
So I started bisecting and arrived at [2] d9d012965de,
"ntdll: Always map files as writable and adjust permissions.",
committed at 2025-03-25.
Unfortuntately this can not be cleanly reverted at current git,
but with three more commits reverted it makes a wine tree,
which can be used with rr-debugger [2].
I could reduce the changes of this 4 commits to a few lines which,
are also able to produce a wine tree usable with rr-debugger [3].
This patch is only changing behaviour once for each
.exe process, when the session shared memory gets mapped in
via the fd received from wineserver.
With unmodified Wine this is currently done with a MAP_PRIVATE flag,
which turns out is currently just mapping the file content
into the process, but does not receive the updates from wineserver.
To investigate if this can be fixed in rr I opened [4].
Unfortunately this would be expected to create a overall slowdown for rr.
Therefore I wonder if this change was intentional,
to map the session shared memory with mmap(MAP_PRIVATE)?
When looking at virtual_map_user_shared_data the shared memory
gets mapped with mmap(MAP_SHARED).
Would something like [3] be acceptable for inclusion?
Kind regards,
Bernhard
[1] https://gitlab.winehq.org/wine/wine/-/commit/cd197f8588b
[2] https://gitlab.winehq.org/wine/wine/-/commit/07160a23fa2https://gitlab.winehq.org/wine/wine/-/commit/9e006e94c9chttps://gitlab.winehq.org/wine/wine/-/commit/8fd49c4d8e9https://gitlab.winehq.org/wine/wine/-/commit/d9d012965de
[3] https://gitlab.winehq.org/bernhardu/wine/-/commit/658e56801a7
[4] https://github.com/rr-debugger/rr/issues/3972
--
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.