https://bugs.winehq.org/show_bug.cgi?id=53455
Bug ID: 53455
Summary: shell32:recyclebin - test_query_recyclebin() gets
unexpected recyclebin size in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
shell32:recyclebin - test_query_recyclebin() gets unexpected recyclebin size:
recyclebin.c:79: Test failed: Expected recycle bin to have 0x22 bytes
recyclebin.c:80: Test failed: Expected recycle bin to have 0x1 items
https://test.winehq.org/data/patterns.html#shell32:recyclebin
The expected size in bytes can also be 0x20 or 0x21 which can cause false
positives.
--
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=53003
Bug ID: 53003
Summary: XM6 TypeG: some MIDI note-on messages aren't sent to
MIDI devices (MIDI running status isn't supported in
the MIDI mapper)
Product: Wine
Version: 7.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winmm&mci
Assignee: wine-bugs(a)winehq.org
Reporter: sagawa.aki+winebugs(a)gmail.com
Distribution: Ubuntu
Created attachment 72371
--> https://bugs.winehq.org/attachment.cgi?id=72371
minimal reproducible example
XM6 TypeG[1] is a SHARP X68000 Emulator.
When I use STed2[2] inside XM6 TypeG, some MIDI note-on messages aren't sent to
MIDI devices (e.g. Timidity++).
@honda_ken, an original reporter on Twitter, tweeted XM6 TypeG sounds strange
on Wine. He also informed me that Wine outputs the following message on his
console:
0338:fixme:midi:modData ooch 3c
0338:fixme:midi:modData ooch 403e
0338:fixme:midi:modData ooch 3e
0338:fixme:midi:modData ooch 4040
0338:fixme:midi:modData ooch 40
0338:fixme:midi:modData ooch 4041
0338:fixme:midi:modData ooch 41
0338:fixme:midi:modData ooch 4043
0338:fixme:midi:modData ooch 43
I setup XM6 TypeG environment on my PC and I can reproduce the issue.
Preparing the environment is a bit difficult, I wrote a minimal reproducible
example (shortmsg.c).
Steps to reproduce:
1. Compile the source code.
% i686-w64-mingw32-gcc -o shortmsg.exe shortmsg.c -lwinmm
2. Setup your favorite MIDI device, e.g. Timidity++.
% timidity -iA &
3. Run the executable (argument -1 means we use the MIDI mapper).
% wine shortmsg.exe -1
Expected result:
We can hear the piano voice, C, D, E and F.
Actual result:
We can hear the piano voice, only C.
[1] http://retropc.net/pi/xm6/index.html
[2] http://retropc.net/x68000/software/sound/rc/sted2/
--
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=52841
Bug ID: 52841
Summary: leverless arcade controller SOCD cleaning regression
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: namtsui(a)gmail.com
Distribution: ---
Created attachment 72236
--> https://bugs.winehq.org/attachment.cgi?id=72236
fix
downstream bug: https://github.com/ValveSoftware/Proton/issues/5527
There is a regression in wine SDL. I tested wine 7.0 using Linux 5.17.2. I
think this is the commit to blame:
https://github.com/wine-mirror/wine/commit/9cf1e8353cf05af1009e3e5d40b62f0e…
See the file: wine-7.0/dlls/winebus.sys/bus_sdl.c
https://github.com/wine-mirror/wine/blob/6d4ec1255acceec7152ed98764ee29991a…
Leverless arcade controllers have all-buttons. One such controller is the
hitbox controller from the company hitbox. It has four directional buttons
mapped to DPAD. It has simultaneous opposite cardinal direction (SOCD)
cleaning. If you hold down + up, it should output up. If you hold left + right,
it should output nothing at all (neutral).
I added print statements. See the attached fix.
In clip 1, I demonstrate SDL2 events when down and up are held simultaneously
during a jump for a while:
hold down (DOWN press event)
hold up (DOWN release event. UP press event.)
hold both for a while
release all (UP release event. DOWN release event.)
[1] https://clips.twitch.tv/PlausibleSparklingButterJonCarnage-1nJQjUmS_kATb5Y6
In clip 2 the actual bug is shown.
hold down (DOWN press event)
press up (DOWN release event. UP press event.)
steps 1 to 2 were demonstrated in clip 1.
release up (DOWN press event. UP release event.)
keep holding down
[2] https://clips.twitch.tv/FunnyPlayfulClintmullinsArgieB8-p3pUOVQuS-eA8oqi
The UP release event at the end in step 3 causes the axis to be reset to 0.
This ignores the DOWN press event immediately preceding it.
Clip 3 shows after the proposed fix is applied.
[3] https://clips.twitch.tv/RacyNeighborlyCookiePeteZaroll-2wwLnflwjAa3ZlFz
--
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=52686
Bug ID: 52686
Summary: DateAdd not implemented
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: sergey.bychkow(a)gmail.com
Created attachment 72024
--> https://bugs.winehq.org/attachment.cgi?id=72024
Sample script
A call to DateAdd function breaks VBScript.
Sample (testdateadd.vbs):
1> aDateFrom = Now
2> MsgBox "Now: " & aDateFrom
3> aDateFrom = DateAdd("h", 1, aDateFrom)
4> MsgBox "+1h: " & aDateFrom
$ wine wscript testdateadd.vbs
Line 2 shows MsgBox, but line 4 does not execute.
Errors (error.log):
0009:fixme:variant:get_date_format ignoring flags 10
0009:fixme:vbscript:Global_DateAdd
0009:fixme:wscript:ActiveScriptSite_OnScriptError ()
--
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=53005
Bug ID: 53005
Summary: quartz:systemclock Fails after timeGetTime() wraps
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Created attachment 72373
--> https://bugs.winehq.org/attachment.cgi?id=72373
Use GetTickCount64() instead of timeGetTime() in quartz:systemclock
quartz:systemclock fails on fg-deb64:
systemclock.c:186: Test failed: Got timestamps 43062836670000, 113163710000,
43062836670000.
https://test.winehq.org/data/patterns.html#quartz:systemclock
The issue is that timeGetTime() wrapped after 49.71 days (2^32 milliseconds) of
uptime, causing it to no longer match the values returned by
IReferenceClock_GetTime().
The test started using timeGetTime() in the commit below:
commit bf5b35f19b841e6352c32ca7c6671d9172636871
Author: Zebediah Figura <zfigura(a)codeweavers.com>
AuthorDate: Thu Oct 21 12:41:11 2021 -0500
quartz: Use the performance counter for the system clock.
Native probably uses timeGetTime() as a source. That doesn't actually match
the
performance counter on Windows, but it does on Wine, and accessing the
counter
directly is slightly more efficient anyway.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51684
Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
The commit made two changes:
GetTickCount*() -> timeGetTime() in the test
GetTickCount64() -> QueryPerformanceCounter() in SystemClockImpl_GetTime()
Before this commit the test was failing on Windows because the GetTickCount*()
values and SystemClockImpl_GetTime() were a bit out of sync. So while switching
to GetTickCount64() in the test fixes the issue in Wine and does not seem to
cause failures on Windows it's not clear that this is correct either.
It would also be nice to see what happens to this test on Windows after 49.7
days of uptime.
--
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=52534
Bug ID: 52534
Summary: ListView: multi select never sends LVN_ODSTATECHANGED
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: winehq-bugs(a)angelohaller.com
Distribution: ---
When using a ListView in virtual mode (LVS_OWNERDATA) and selecting multiple
rows (holding down shift and selecting) the message code LVN_ODSTATECHANGED is
never sent.
Looking through the wine source, there is definitely code present sending
LVN_ODSTATECHANGED, this however never reaches the application and hence is a
bug.
Running the same application in Windows 7 will however send the
LVN_ODSTATECHANGED code.
This seems to be true for ALL programs using LVS_OWNERDATA and supporting multi
select.
This is an issue that arose working on
https://github.com/libui-ng/libui-ng/pull/73
A nicer example to reproduce would be from the `Windows classic samples`. I
forked the official Microsoft repo to add some debug printing:
1. Clone https://github.com/szanni/Windows-classic-samples
2. Change to directory Samples/Win7Samples/winui/controls/common/vlistvw
3. Build VListVw (I cross compile via `x86_64-w64-mingw32-gcc VListVw.c
-lcomctl32` but using the vcproj should work too?) or use the test binary a.exe
(linked at the bottom)
4. Run the resulting .exe
5. Select a cell (should print `LVN_ITEMCHANGED`)
6. Hold down `shift` and select a cell a few rows down below.
On Windows 7 step 6. triggers the message `LVN_ODSTATECHANGED` to be emitted
(as can be seen in the debug print statements). wine however never sends this
message.
This is contrary to the documentation provided in
https://docs.microsoft.com/en-us/windows/win32/controls/lvn-itemchanged#rem…
and behavior developers rely on.
Test binary:
https://github.com/szanni/Windows-classic-samples/blob/main/Samples/Win7Sam…
--
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=49285
Bug ID: 49285
Summary: PNotesPortable crashes inside kernel32
Product: Wine
Version: 5.9
Hardware: x86
URL: https://download3.portableapps.com/portableapps/PNotes
Portable/PNotesPortable_9.3.0.paf.exe?20190321
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
Yet another one:
Hi, a user tested some portable apps on forum:
https://forum.winehq.org/viewtopic.php?f=2&t=33957
When you right-click on the taskbar icon, and then choose "Exit" it crashes.
00c4:Call KERNEL32.WritePrivateProfileStructW(00494d5c L"hotkeys",0031c6f4
L"10001",00000000,00000040,004f0310
L"Z:\\media\\louis\\aqqa\\PNotesPortable\\Data\\settings\\Note
s.ini") ret=0043456f
00c4:trace:seh:raise_exception code=c0000005 flags=0 addr=0x7b64e9f5
ip=7b64e9f5 tid=00c4
-->crash
So looks like it crashes inside WritePrivateProfileStructW ??
sha1sum PNotesPortable_9.3.0.paf.exe
2df27f55e3b43c889a5e7c68684e8acbaef9498f PNotesPortable_9.3.0.paf.exe
--
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=47375
Bug ID: 47375
Summary: Photoshop C 2018 crashes on unimplemented function
msvcr120.dll.?_Schedule@_StructuredTaskCollection@deta
ils@Concurrency@@QEAAXPEAV_UnrealizedChore@23@@Z
Product: Wine
Version: 4.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: winepala(a)tradermail.info
Distribution: ---
Created attachment 64711
--> https://bugs.winehq.org/attachment.cgi?id=64711
wine output
Photoshop CC 2018 crashes on an unimplemented function after using the Color
Range tool to make a selection.
wine: Call from 0x7b4560f6 to unimplemented function
msvcr120.dll.?_Schedule@_StructuredTaskCollection@details@Concurrency@@QEAAXPEAV_UnrealizedChore@23@@Z,
aborting
--
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=53310
Bug ID: 53310
Summary: Roblox Fails With HttpSendRequest
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: goldstar611(a)hotmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 72687
--> https://bugs.winehq.org/attachment.cgi?id=72687
Partial debug log created using WINEDEBUG=+winhttp,+wininet
Roblox fails to launch experiences after a 15-20 second delay and displays
"An error occurred while starting Roblox Details HttpSendRequest failed (..)
Error: An error occurred in the secure channel support"
Googling this will reveal some old instructions to install libgnutls but this
is already installed on my system.
I upgraded this morning to
- wine-staging 7.12~buster-1
- wine-staging-amd64 7.12~buster-1
- wine-staging-i386:i386 7.12~buster-1
from "deb https://dl.winehq.org/wine-builds/debian/ buster main"
Downgrading these packages to 7.11~buster-1 allows Roblox to launch experiences
again.
--
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.