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=53401
Bug ID: 53401
Summary: regedit does not import .reg files
Product: Wine-staging
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ToddAndMargo(a)zoho.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 72794
--> https://bugs.winehq.org/attachment.cgi?id=72794
.reg file that won't import
Fedora 36
Wine 7.12-1
Regedit
$ env WINEPREFIX="/home/todd/.wine.test" wine regedit &
--> Registry
--> Import Registry File
Does not actually import ./reg files, but says it has successfully done so.
--
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=33302
Bug #: 33302
Summary: [regedit] text gets cut away
Product: Wine
Version: 1.4.1
Platform: x86
OS/Version: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fiziologus(a)gmail.com
Classification: Unclassified
Created attachment 44055
--> http://bugs.winehq.org/attachment.cgi?id=44055
screenshot with bug
regedit don't show about 4 char on the right side in edit dialog window if
value is multiline.
It's simulated bug 26365 (Geneforge 1)
--
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=58333
Bug ID: 58333
Summary: Lotus Freelance Graphics 2.1 reports a C runtime error
and exits
Product: Wine
Version: 10.9
Hardware: x86-64
URL: https://archive.org/download/lotussmartsuiterelease3.1
forwindows/Lotus%20SmartSuite%20Release%203.1%20for%20
Windows.zip
OS: Linux
Status: NEW
Keywords: download, win16
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: Ubuntu
Created attachment 78706
--> http://bugs.winehq.org/attachment.cgi?id=78706
Screenshot
Lotus Freelance Graphics 2.1 reports a C runtime error and either exits or
hangs.
Installed with an earlier version of Wine to work around Bug 58329. Tested with
many version of Wine up to latest git (wine-10.9-62-g68bd146ae55).
$ wine 'c:\LOTSUITE\FLW\FLW.EXE'
0134:err:local:LOCAL_GetBlock not enough space in local heap 0b07 for 124 bytes
After many hours messing around I discovered that this was due to me adding a
single environment variable, such as WINEDEBUG=+server for example. Apparently
this was just enough to "break the donkey's back".
However, my environment variables aren't particularly large.
$ true | xargs --show-limits
Your environment variables take up 2260 bytes
POSIX upper limit on argument length (this system): 2092844
POSIX smallest allowable upper limit on argument length (all systems): 4096
Maximum length of command we could actually use: 2090584
Size of command buffer we are actually using: 131072
An +all trace (because I didn't know where to start) shows that Wine's
environment variables only come to around 3K, which also doesn't seem a lot.
I wanted to trace get_startup_info() but setting WINEDEBUG=+ntdll or +server
simply triggers the bug.
To prove... nothing I added 100 large variables and winevdm sat churning away
for five minutes before I got bored and stopped it.
0130:err:sync:RtlpWaitForCriticalSection section 78F049E0
"dlls/krnl386.exe16/syslevel.c: Win16Mutex" wait timed out in thread 0130,
blocked by 0134, retrying (60 sec)
0134:trace:local:LOCAL_PrintHeap Local Heap ds=0b07 first=f2c0 last=fff4
items=5
0134:trace:local:LOCAL_PrintHeap f2c0: prev=f2c0 next=f2cc type=1
0134:trace:local:LOCAL_PrintHeap size=12 free_prev=f2c0 free_next=ff80
0134:trace:local:LOCAL_PrintHeap f2cc: prev=f2c0 next=f2fc type=1
0134:trace:local:LOCAL_PrintHeap f2fc: prev=f2cc next=ff80 type=1
0134:trace:local:LOCAL_PrintHeap ff80: prev=f2fc next=fff4 type=0
0134:trace:local:LOCAL_PrintHeap size=116 free_prev=f2c0 free_next=fff4
0134:trace:local:LOCAL_PrintHeap fff4: prev=ff80 next=fff4 type=0
0134:trace:local:LOCAL_PrintHeap size=12 free_prev=ff80 free_next=fff4
0134:err:local:LOCAL_GetBlock not enough space in local heap 0b07 for 124 bytes
“Does this mirror the behaviour seen on Windows?”
I'll have to come back to that.
--
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=57820
Bug ID: 57820
Summary: Cannot drag and drop files into apps with the Wayland
driver enabled
Product: Wine
Version: 10.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: agarplayerarlon(a)gmail.com
Distribution: ---
Created attachment 78030
--> https://bugs.winehq.org/attachment.cgi?id=78030
Video of the issue
As the title says I cannot drag and drop files into applications when using the
Wayland driver, I've only tested FL Studio and when I try to drag and drop a
file inside it, an "x" symbol appears to the cursor and doesen't let me drop
the file into the application.
I've attached a video of the issue.
Also using the x11 driver, drag and drop works fine.
--
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=57367
Bug ID: 57367
Summary: DLNest crash due to unimplemented function
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: l12436.tw(a)gmail.com
Distribution: ---
DLNest new 2.0 version use dotnet and shown following message
Unimplemented function ntdll.dll.NtCreateWaitCompletionPacket called at address
00006FFFFFC5F038 (thread 0140), starting debugger...
which is seems like unimplemented in wine
--
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=58331
Bug ID: 58331
Summary: Wait cursor does not display
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: rikul(a)inbox.ru
Distribution: ---
Created attachment 78705
--> http://bugs.winehq.org/attachment.cgi?id=78705
Example
Starting from Wine version 9.0, the waiting cursor no longer appears when
attempting to set it to indicate a long-running operation in MFC applications
or other programs. The issue appears to have started after the commit on June
13, 2023.
Steps to Reproduce:
1. Run the attached simple MFC application.
2. Click the button "Start Long Operation"
Expected Result:
The waiting cursor should appear for the duration of the 3-second sleep.
Actual Result:
The waiting cursor does not appear during the Sleep call. The cursor remains
the default arrow.
Example Application:
The example application has been attached. It uses the most basic
implementation of the CWaitCursor class, as described in the official Microsoft
documentation:
https://learn.microsoft.com/en-us/cpp/mfc/reference/cwaitcursor-class?view=…
Regression Commit:
The issue seems to have started with the commits made on June 13, 2023:
https://github.com/wine-mirror/wine/commits/master/dlls?author=rbernon&sinc…
Notes:
This issue does not occur in Windows, where the waiting cursor appears as
expected.
Environment:
Wine version: 9.0+ (possibly Wine 8.x, but not 8.0)
Operating System: RHEL 7.9, RHEL 8.10
--
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=58334
Bug ID: 58334
Summary: ShowStopper crashes on unimplemented function
ntdll.dll.RtlQueryProcessHeapInformation
Product: Wine
Version: 10.9
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Steps to reproduce:
1. Run `wine ShowStopper.exe`
2. Click "Run Checks"
$ sha256sum ShowStopper1.0.0.1.zip
18707678dea01fecc3e1de1dacb66a1e9e134261de15d7f7190f3aee41edea77
--
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=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.
http://bugs.winehq.org/show_bug.cgi?id=19662
Summary: Lotus Freelance Graphics 2.1 hangs at the splash
screen
Product: Wine
Version: 1.1.27
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: win16
Severity: normal
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
Created an attachment (id=22946)
--> (http://bugs.winehq.org/attachment.cgi?id=22946)
Wine 1.1.27 +relay +seh +tid
Lotus Freelance Graphics 2.1 hangs at the splash screen and has to be killed.
Console output:
fixme:hook:SetWindowsHookEx16 System-global hooks (3) broken in Win16
fixme:ole:OleRegisterServer16 (FLWPresentation,...): stub
fixme:toolhelp:InterruptUnRegister16 (0000), stub.
--
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=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.
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.
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.
http://bugs.winehq.org/show_bug.cgi?id=58327
Bug ID: 58327
Summary: Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R.
Anomaly when using a scope
Product: Wine
Version: 10.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: tactica.os4(a)gmail.com
Distribution: ---
Created attachment 78695
--> http://bugs.winehq.org/attachment.cgi?id=78695
Savegame to easily trigger the crash
East of the Yanov station in Jupiter, looking down the scope of your weapon
will crash d3d11 if you look East while you are at a specific location:
---snip---
Assertion failed!
Program:
Z:\home\tactica\Downloads\Anomaly\Anomaly-1.5.3-Full.2\bin\AnomalyDX11.exe
File:dlls/d3d11/inputlayout.c
Line: 416
Expression: "iface->lpVtbl == &d3d11_input_layout_vtbl"
---snip---
(note: the quoted text above was typed manually)
How to reproduce:
1. Download and unpack STALKER Anomaly. It doesn't require any installation.
2. Unpack the attached savegame files into /appdata/savedgames/ in the game
directory.
3. Use winecfg to install d3d11 as override for Wine.
3. Start the game running /bin/AnomalyDX11.exe
4. After the main menu opens, load the provided savegame.
5. Once in the game proper, simply click RMB to use the scope of your weapon
while looking at those ruined vehicles
The crash does not happen if:
a) You run AnomalyDX9.exe instead
b) You move the camera to point elsewhere before using the scope, say 90
degrees to your right or left
c) You use the shotgun instead (press 2), which doesn't have a long range scope
attached
c) You load the same savegame on 64-bit Windows 7 and play there, using exactly
the same visual settings (I double checked that)
This using 64-bit (only) Wine 10.9 on Void Linux (x86-64) with the stock AMDGPU
driver.
--
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=58325
Bug ID: 58325
Summary: wined3d swapchain use-after-free
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: yshuiv7(a)gmail.com
Distribution: ---
Releasing the swapchain brings us to wined3d_swapchain_cleanup, which destroys
the front/back buffer textures.
Texture destruction is async, happening on the device's command stream. This
means these textures can be destroyed way after the swapchain itself. But we
did set `texture->swapchain` to `NULL` before queuing their destruction, so
that bit is fine.
The problem is in texture_resource_unload. Here we try to acquire the context,
which goes adapter_gl_acquire_context -> wined3d_context_gl_acquire ->
wined3d_context_gl_activate -> wined3d_context_gl_update_window. And here we
try to access `context_gl->c.swapchain->win_handle`, which unfortunately points
to the swapchain that was just freed.
I am unsure what's the fix for this. Do we hold a refcount of the swapchain in
the context? Do we clear `context->swapchain` when a swapchain is being freed?
Should we release the front/back buffer synchronously? Or something else?
--
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=57230
Bug ID: 57230
Summary: F.E.A.R Combat black screen at startup due to out of
memory error
Product: Wine
Version: 9.18
Hardware: x86-64
URL: https://web.archive.org/web/20240924151800/https://www
.fear-community.eu/files/fear_combat_202_community_ful
l_multilang_beta3.exe
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lingm+winebz(a)posteo.org
Distribution: ArchLinux
Created attachment 77147
--> https://bugs.winehq.org/attachment.cgi?id=77147
Wine 9.18 startup oom
This might be a duplicate of bug 55593, but the messages are a bit different
and it happens at program startup and not at starting a new game. Not to
mention that there might be a relevant difference between F.E.A.R and F.E.A.R
Combat.
F.E.A.R Combat is the multiplayer part of F.E.A.R, which was released freely
back in 2006. The official lobby server, download, and key generation were shut
down years ago, but are being kept alive by the community.
You can get all you need at
https://www.fear-community.eu/#update_fear_combat_sec2. I've also mirrored the
installer to archive.org and added that link in the URL field.
Getting a key requires a free registration with just an email address. If that
turns out to be a problem, I'm happy to share mine privately.
> $ du -h fear_combat_202_community_full_multilang_beta3.exe
> 2,0G fear_combat_202_community_full_multilang_beta3.exe
> $ md5sum fear_combat_202_community_full_multilang_beta3.exe
> dd38096e5bf31641a757c233718803f8 fear_combat_202_community_full_multilang_beta3.exe
For reproduction simply start FEARMP.exe. You should see a low resolution black
screen and messages like these in the console:
> 0024:err:d3dx:d3dx_pool_sync_shared_parameter Out of memory.
> 0024:fixme:d3dx:d3dx9_effect_init_from_binary Failed to parse effect.
> wine: Unhandled page fault on read access to 8075000D at address 7BB05298 (thread 0024), starting debugger...
--
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.