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=53008
Bug ID: 53008
Summary: When playing civilizatin2, winevdm crash
Product: Wine
Version: 7.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: clabbe.montjoie(a)gmail.com
Distribution: ---
Created attachment 72378
--> https://bugs.winehq.org/attachment.cgi?id=72378
backtrace of winevdm
When playing civilization 2, game menu start, but after some time, game crash.
I am sure that it worked before, but i need some time digging backup to find
which version of wine I used.
--
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=22448
Summary: Scrabble installer for Windows 3.1 crashes immediately
Product: Wine
Version: 1.1.43
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: RandomAccountName(a)mail.com
Created an attachment (id=27495)
--> (http://bugs.winehq.org/attachment.cgi?id=27495)
Crash log
Trying to launch the installer for the Windows 3.1 version of Scrabble results
in an immediate crash in winevdm. The same crash occurs in all Wine versions I
tested (the oldest being 0.9.33).
--
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=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=58326
Bug ID: 58326
Summary: SetupDiGetClassDevs does not enumerate USB devices
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: setupapi
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)3v1n0.net
Distribution: ---
Created attachment 78694
--> http://bugs.winehq.org/attachment.cgi?id=78694
Example device enumerator
In order to enumerate the USB devices in the system, a window application is
expected
(https://github.com/microsoft/Windows-driver-samples/blob/main/usb/usbview/e…)
to use SetupDiGetClassDevs with the `GUID_DEVINTERFACE_USB_DEVICE` GUID,
however this returns nothing in WINE.
Running a simpler example (attached) of the enumerator that extends to all the
device types, I get in fact:
```
Device info is 0x7ffffe8d4760
Device info Date is 1 {4D36E96E-E325-11CE-BFC1-08002BE10318}
Device desc name is Generic Non-PnP Monitor
Device driver name is {4D36E96E-E325-11CE-BFC1-08002BE10318}\0000
Failed at 186
Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}
Device desc name is Wine HID device
Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0003
Failed at 186
Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}
Device desc name is Wine HID device
Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0002
Failed at 186
Device info Date is 1 {4D36E968-E325-11CE-BFC1-08002BE10318}
Device desc name is Wine Adapter
Device driver name is {4D36E968-E325-11CE-BFC1-08002BE10318}\0000
Failed at 186
Device info Date is 1 {4D36E97D-E325-11CE-BFC1-08002BE10318}
Device desc name is Wine HID bus driver
Device driver name is {4D36E97D-E325-11CE-BFC1-08002BE10318}\0000
Failed at 186
Device info Date is 1 {4D36E97D-E325-11CE-BFC1-08002BE10318}
Device desc name is Wine USB bus driver
Device driver name is {4D36E97D-E325-11CE-BFC1-08002BE10318}\0001
Failed at 186
Device info Date is 1 {00000000-0000-0000-0000-000000000000}
Failed at 159
Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}
Device desc name is Wine HID compatible device
Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0000
Failed at 186
Device info Date is 1 {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}
Device desc name is Wine HID compatible device
Device driver name is {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}\0001
Failed at 186
Device info Date is 0 {00000000-0000-0000-0000-000000000000}
```
While under a windows VM the same code also returns (for example):
Device info Date is 1 {CA3E7AB9-B4C3-4AE6-8251-579EF933890F}
Device desc name is
USB Video Device
Device driver name is
{ca3e7ab9-b4c3-4ae6-8251-579ef933890f}\0001
As per this it's not possible to find out the device ID that it could be used
via `WinUsb_Initialize(deviceHandle, &winusbHandle)` (even though this doesn't
seem to work even passing an hardcoded path).
--
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.