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=50948
Bug ID: 50948
Summary: taskmgr show wrong memory usage unit (GB => MB)
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: limstash.w(a)gmail.com
Distribution: ---
Created attachment 69771
--> https://bugs.winehq.org/attachment.cgi?id=69771
Screenshot
Task manage performance page show wrong memory usage unit, should be GB instead
of MB.
Step to reproduce:
1. wine taskmgr
2. switch to the performance page
$ wine --version
wine-6.5
--
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=52457
Bug ID: 52457
Summary: CNG Encryption Failure (BCryptEncrypt)
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bcrypt
Assignee: wine-bugs(a)winehq.org
Reporter: x256(a)ultra.fyi
Distribution: ---
Created attachment 71746
--> https://bugs.winehq.org/attachment.cgi?id=71746
Demo application (with source code)
The CNG encryption function BCryptEncrypt does not always work properly.
Please see the attached demo application. It encrypts 4 blocks (AES in CBC
mode, test vector from RFC 3602): one BCryptEncrypt call encrypts the first two
blocks, and a second BCryptEncrypt call encrypts the last two blocks. On
Windows, all 4 blocks are encrypted correctly. On Wine, the first two blocks
are encrypted correctly, but the last two blocks are incorrect.
Tested with Wine 5.0.3 and 7.0.0 (winehq-stable) on Kubuntu 21.10 (64-bit).
Thanks!
--
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=51788
Bug ID: 51788
Summary: windowscodecs:wmpformat test_decode() fails in the
ar_MA locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: windowscodecs
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Created attachment 70682
--> https://bugs.winehq.org/attachment.cgi?id=70682
Dump the imagedata content for debugging
windowscodecs:wmpformat test_decode() fails in the ar_MA.UTF-8 locale:
wmpformat.c:149: Test failed: unexpected image data
wmpformat.c:149: Test failed: unexpected image data
wmpformat.c:149: Test failed: unexpected image data
wmpformat.c:149: Test failed: unexpected image data
https://test.winehq.org/data/patterns.html#windowscodecs:wmpformat
Strangely this also happens in other locales like ar_AE.UTF-8, ar_EG.UTF-8,
fa_IR.UTF-8 (Farsi) and ur_IN.UTF-8 (Urdu); but not in other right-to-left
locales like he_IL.UTF-8 (Hebrew) or yi_US.UTF-8 (Yiddish).
I added code to dump the imagedata content and in all failure cases I got the
same value:
wmpformat.c:154: imagedata=6db0fc006db0fc006db0fc006db0fc006db0fc6c
instead of the expected
wmpformat.c:154: imagedata=6db0fc006db0fc006db0fc006db0fc006db0fc00
So it's only the last byte that changes.
Also, while these failures are easily reproducible on the TestBot VMs (debiant2
and my own), I cannot reproduce them on my Debian 11 development machine (I
have the required locales).
In any case a bisect shows that these failures were introduced by the following
commit:
commit 711ce415c01a5e36bde6bb147b5aa3cedc8b35ed
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Thu Sep 2 14:14:25 2021 +0200
gdi32: Store abort proc in DC_ATTR.
Signed-off-by: Jacek Caban <jacek(a)codeweavers.com>
Signed-off-by: Huw Davies <huw(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=46822
Bug ID: 46822
Summary: Edit control in ADL search dialog gets initially not
drawn in DC++ 0.868, regression
Product: Wine
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: dee3shee7aeno4(a)mailinator.com
Distribution: ---
Created attachment 63845
--> https://bugs.winehq.org/attachment.cgi?id=63845
wine-4.3-229-g6d82b2f1ad-with-dadea2d11d78c73ce918d0c130db6dd32d06e6ee-reverted.png
In DC++ 0.868, not connected to a hub,
menu View - ADL search - right click in the upper area - New ...
The created dialog does not draw the Search String edit control properly.
A git bisect led here:
dadea2d11d78c73ce918d0c130db6dd32d06e6ee is the first bad commit
Author: Nikolay Sivov <nsivov(a)codeweavers.com>
Date: Fri Feb 16 14:19:00 2018 +0300
comctl32/edit: Force update on focus change.
That commit was a fix against bug #40002.
Wine 3.2 is the first release containing that commit.
Reverting that commit on top of current git makes the
edit control being drawn correctly.
Download:
https://sourceforge.net/projects/dcplusplus/files/DC%2B%2B%200.868/
--
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=52831
Bug ID: 52831
Summary: Kernel32::GetSystemPowerStatus Returns Invalid Data if
BAT0 is Missing
Product: Wine
Version: 7.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: root(a)kazwolfe.io
Distribution: ---
Created attachment 72224
--> https://bugs.winehq.org/attachment.cgi?id=72224
Output from Wine, MCVE binary, and relevant information.
Currently, it appears as though Kernel32's GetSystemPowerStatus behaves
inconsistently on modern systems and will return garbage or invalid
information.
A precursory glance into this problem seems to be rooted in
dlls/ntdll/unix/system.c#L3447 and `fill_battery_state`. This function only
appears to check for the existence of `/sys/class/power_supply/AC` and
`/sys/class/power_supply/BAT0`, which not all systems necessarily have. For
example, my test computer runs on `AC0` and `BAT1`. A Steam Deck (where this
bug originally was noticed) uses `ACAD` and `BAT1`.
--
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.