http://bugs.winehq.org/show_bug.cgi?id=30875
Bug #: 30875
Summary: Unable to deselect character blocks in BMFont
Product: Wine
Version: 1.5.6
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dav75uk(a)yahoo.co.uk
Classification: Unclassified
Run BMFont (http://www.angelcode.com/products/bmfont/) and click on some of the
checkboxes to the right to select characters to be included. It is not possible
to uncheck the checkboxes.
Workaround is to unselect one of the characters (click on a character in that
range) which changes the full checked box to a part check box. The part check
box can be unselected.
--
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=52911
Bug ID: 52911
Summary: ole32:moniker fails on Windows in the UTF-8 codepage
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ole32:moniker fails on Windows in the UTF-8 codepage:
moniker.c:2189: Test failed: IsEqual failed with error 0x000001
[...]
https://test.winehq.org/data/patterns.html#ole32:moniker
So the failures happen because moniker1 and moniker2 are always different.
Adding a call to winetest_push_context() shows that the failures all happen for
string 2 which ole32:moniker uses to skip tests on code pages where there are
round-trip issues:
{0xc0, 0xc1, 0xc2, 0xc3, 0xc4, 0xc5, 0xc6, 0xc7, 0xc8, 0xc9, 0xca,
0xcb, 0xcc, 0xcd, 0xce, 0xcf, 0xd0, 0},
[...]
skip("string 2 doesn't round trip in codepage %u\n", GetACP() );
So it looks like the skip fails to trigger for the UTF-8 codepage (or that we
should do something else to make the UTF-8 case work).
--
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=45432
Bug ID: 45432
Summary: Implement Windows Native Firewall Rules for Lightwave
Software Licensing - netfw_rules
Product: Wine
Version: 3.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: newel.anderson(a)gmail.com
Distribution: ---
Created attachment 61753
--> https://bugs.winehq.org/attachment.cgi?id=61753
Terminal logs installing and launching Lightwave under WIne 3.11 in Linux
Lightwave requires Windows Native Firewall Inbound/Outbound Rules in order to
register/activate one's license.
For reference, please see:
https://forum.winehq.org/viewtopic.php?f=8&t=30847&p=116945#p116945 (I'm
wineink)
Towards the end of the above thread I posted terminal output as well as
screenshots. Disabling Windows Firewall, as well as deleting the
inbound/outbound rules in Windows, deactivates my license. Re-enabling the
rules and Windows Firewall reactivates my license. Since this functionality
doesn't exist in Wine, Wine hasn't to my knowledge implemented Windows Native
Firewall Rules, it's impossible to register/activate my legally purchased
license in Wine.
Thank you for your time and consideration.
***Please note, the above applies only to a FULL license of Lightwave. The
trial, which is node-locked, works as designed. Unfortunately, the FULL license
is not node-locked.
--
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=52986
Bug ID: 52986
Summary: d3d9:device - In Wine test_vertex_buffer_read_write()
fails on on cw-rx460
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d9:device - In Wine test_vertex_buffer_read_write() only succeeds on
cw-rx460:
device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 0.
device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 1.
device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 2.
https://test.winehq.org/data/patterns.html#d3d9:device
This is specific to this machine so it seems likely that this is related to the
graphics card / 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.
https://bugs.winehq.org/show_bug.cgi?id=52985
Bug ID: 52985
Summary: d3d9:device - test_reset_fullscreen() gets an
unexpected WM_SIZE message with fvwm
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Created attachment 72354
--> https://bugs.winehq.org/attachment.cgi?id=72354
The TestBot's fvwm configuration
d3d9:device - test_reset_fullscreen() gets an unexpected WM_SIZE message with
fvwm:
device.c:4822: Test failed: Received unexpected WM_SIZE message.
https://test.winehq.org/data/patterns.html#d3d9:device
This failure happens on cw-gtx560, cw-rx460 and debian11 VM which all run
Debian 11 with fvwm, and on debiant VM which runs Debian Testing with fvwm.
But it does not happen on fg-deb64 which runs Debian 11 too, but with KDE's
window manager.
So it is pretty likely that this failure only happens when running fvwm.
--
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=52984
Bug ID: 52984
Summary: d3d8:device - test_cursor_pos() missing a MOUSEMOVE on
cw-gtx560 and cw-rx460
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d8:device - test_cursor_pos() is missing a MOUSEMOVE most of the time on
cw-gtx560 and cw-rx460:
device.c:1324: Test failed: Didn't receive MOUSEMOVE 0 (50, 50).
https://test.winehq.org/data/patterns.html#d3d8:device
This happens almost systematically on cw-gtx560 and cw-rx460 with Windows 10
1709 to 1909 but happens much less frequently with more recent Windows
versions.
Also it never happens in the TestBot VMs running the same Windows versions and
also does not happen on fgtb-w10pro64-rx550.
So it may be related to the set of display modes that the monitor supports
which would explain why the KVM-connected machines are impacted and not the
others.
Or it could be related to the GPU drivers and fgtb-w10pro64-rx550 just got
lucky because it's on a more recent Windows version.
--
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=52935
Bug ID: 52935
Summary: comctl32:tab - test_tab(-1&-3) fails on Windows with
the UTF-8 codepage
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
comctl32:tab's test_tab(-1&-3) fails on Windows with the UTF-8 codepage:
tab.c:591: Testing with default MinWidth
tab.c:579: Test failed: with icon, set size > icon: Expected [51,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [51,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [51,1] got [48,1]
tab.c:579: Test failed: with icon, set size > icon: Expected [54,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [54,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [54,1] got [48,1]
tab.c:579: Test failed: with icon, set size > icon: Expected [57,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [57,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [57,1] got [48,1]
tab.c:579: Test failed: with icon, set size > icon: Expected [60,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [60,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [60,1] got [48,1]
tab.c:579: Test failed: with icon, set size > icon: Expected [63,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [63,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [63,1] got [48,1]
tab.c:579: Test failed: with icon, set size > icon: Expected [66,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [66,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [66,1] got [48,1]
tab.c:593: Testing with MinWidth set to -3
tab.c:579: Test failed: with icon, set size > icon: Expected [51,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [51,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [51,1] got [48,1]
tab.c:579: Test failed: with icon, set size > icon: Expected [54,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [54,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [54,1] got [48,1]
tab.c:579: Test failed: with icon, set size > icon: Expected [57,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [57,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [57,1] got [48,1]
tab.c:579: Test failed: with icon, set size > icon: Expected [60,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [60,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [60,1] got [48,1]
tab.c:579: Test failed: with icon, set size > icon: Expected [63,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [63,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [63,1] got [48,1]
tab.c:579: Test failed: with icon, set size > icon: Expected [66,30] got
[48,30]
tab.c:580: Test failed: with icon, set size < icon: Expected [66,20] got
[48,20]
tab.c:581: Test failed: with icon, min size: Expected [66,1] got [48,1]
https://test.winehq.org/data/patterns.html#comctl32:tab
Hindi + UTF-8 is the only locale where this test fails on Windows at this time.
In particular there is no failure on the standard Hindi locale (English system
locale) so this appears to be specific to UTF-8.
--
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=52939
Bug ID: 52939
Summary: advapi32:registry - test_RegNotifyChangeKeyValue() has
an intermittent failure on all Windows versions
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Created attachment 72312
--> https://bugs.winehq.org/attachment.cgi?id=72312
Loop on test_RegNotifyChangeKeyValue() to reproduce the event failures
advapi32:registry's test_RegNotifyChangeKeyValue() has an intermittent failure
on all Windows versions:
registry.c:3471: Test failed: expected ERROR_SUCCESS, got 6
registry.c:3599: Test failed: expected WAIT_OBJECT_0, got 258
https://test.winehq.org/data/patterns.html#advapi32:registry
The failure is pretty rare so it is likely to cause false positives. The
attached patch makes it possible to systematically reproduce the issue, at
least on my test VM. With the 10000 loops I get 4 to 5 cases with the failure
(so a rate of 0.05%) and a test run still takes under 8 seconds.
--
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=52925
Bug ID: 52925
Summary: usp10:usp10 The wgDefault check fails on Windows in
non-basic locales (Hebrew, Japanese, etc)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: usp10
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
usp10:usp10's wgDefault check in test_ScriptGetFontProperties() fails on some
bitmap fonts in a number of locales:
* Arabic
usp10.c:2591: Test failed: bitmap font System wgDefault 0126, tmDefaultChar
0085
usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 0126, tmDefaultChar
0085
usp10.c:2591: Test failed: bitmap font MS Serif wgDefault 0126, tmDefaultChar
0085
usp10.c:2591: Test failed: bitmap font MS Sans Serif wgDefault 0126,
tmDefaultChar 0085
* Hebrew
usp10.c:2591: Test failed: bitmap font Small Fonts wgDefault 01ac,
tmDefaultChar 0080
* Hindi + UTF-8 (no failure for plain Hindi)
usp10.c:2591: Test failed: bitmap font System wgDefault 00fd, tmDefaultChar
0080
usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 00fd, tmDefaultChar
0080
usp10.c:2591: Test failed: bitmap font Courier wgDefault 00fd, tmDefaultChar
0080
usp10.c:2591: Test failed: bitmap font MS Serif wgDefault 00fd, tmDefaultChar
0080
usp10.c:2591: Test failed: bitmap font MS Sans Serif wgDefault 00fd,
tmDefaultChar 0081
usp10.c:2591: Test failed: bitmap font Small Fonts wgDefault 00fd,
tmDefaultChar 0080
* Japanese
usp10.c:2591: Test failed: bitmap font FixedSys wgDefault 00f0, tmDefaultChar
00a0
usp10.c:2591: Test failed: bitmap font @FixedSys wgDefault 00f0, tmDefaultChar
00a0
* Chinese
usp10.c:2591: Test failed: bitmap font System wgDefault 00ac, tmDefaultChar
0080
usp10.c:2591: Test failed: bitmap font @System wgDefault 00ac, tmDefaultChar
0080
usp10.c:2591: Test failed: bitmap font Terminal wgDefault 00ac, tmDefaultChar
0080
usp10.c:2591: Test failed: bitmap font @Terminal wgDefault 00ac, tmDefaultChar
0080
usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 00ac, tmDefaultChar
0080
usp10.c:2591: Test failed: bitmap font @Fixedsys wgDefault 00ac, tmDefaultChar
0080
https://test.winehq.org/data/patterns.html#usp10:usp10
In each case we get the expected value on Windows with a number of fonts but
there are some exceptions that cause the failures. For a given locale the
exceptions all have the same wgDefault value which means there is probably some
logic to it.
So we either need to come up with a better way to find the expected wgDefault
value, or to radically loosen the test, or to restrict the test to some 'safe'
fonts, or to remove the test entirely.
--
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=52981
Bug ID: 52981
Summary: windows.media.speech:speech - SpeechRecognizer fails
to initializes with elevated privileges
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Most of test_SpeechRecognizer() is skipped when run with elevated privileges:
speech.c:896: SpeechRecognizer default language L"fr-FR".
speech.c:1172: Tests skipped: Could not init SpeechRecognizer with default
language!
https://test.winehq.org/data/patterns.html#windows.media.speech:speech
The involved lines are:
919 hr = RoActivateInstance(hstr, &inspectable);
922 if (hr == S_OK)
...
1170 else if (hr == SPERR_WINRT_INTERNAL_ERROR) /* Not sure when this
triggers. Probably if a language pack is not installed. */
1171 {
1172 win_skip("Could not init SpeechRecognizer with default
language!\n");
An analysis of the test results across Windows versions shows that we see this
SPERR_WINRT_INTERNAL_ERROR on Windows 10 >= 1809:
cw-gtx560-1507 S_OK
cw-rx460-1507 S_OK
w1064v1507 S_OK
w1064v1607 S_OK
cw-gtx560-1709 S_OK
cw-rx460-1709 S_OK
w1064v1709 S_OK
cw-gtx560-1809 skipped
cw-rx460-1809 skipped
w1064v1809 skipped
cw-gtx560-1909 skipped
cw-rx460-1909 skipped
w1064v1909 skipped
w1064v2004 skipped
cw-gtx560-2009 skipped
cw-rx460-2009 skipped
w1064v2009 skipped
cw-gtx560-21h1 skipped
cw-rx460-21h1 skipped
w10pro64-21h1 skipped
cw-gtx560-21h2 skipped
cw-rx460-21h2 skipped
w1064-21h2 skipped
w10pro64-21h2 skipped
So far that looks pretty clear cut: Microsoft changed things around 1809 such
that processes running with elevated privileges cannot / are not allowed to
perform speech recognition. That would mean the test should drop the privileges
so it can run on any platform.
However the test was not skipped in the w10pro64v2004 and w10pro64 (21H1) test
configurations... until they were upgraded.
So this indicates that there may be a way to get this test to work even while
retaining elevated privileges. But how?
To help debug the issue I added two test configurations:
* w10pro64restored
The w10pro64 VM restored from a backup of the pre-2022-05 upgrade VM.
Surprisingly the test still ends up being skipped!
* w10pro64old
Luckily before the upgrade I moved the old VM out of the way. It is now
available as w10pro64old with the exact same live snapshots. Comfortingly the
test is still not skipped, even after waiting some time and rebooting.
That last part indicates there may be something either in the way the TestBot
creates the live snapshots, or in the "WineTestBot VMs" checklist I go through
when preparing the VMs and the cw-* machines (but then the clear 1809 cutoff
point is quite a coincidence).
--
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.