https://bugs.winehq.org/show_bug.cgi?id=55488
Bug ID: 55488
Summary: Finale 27 doesn't print SMuFL fonts
Product: Wine
Version: 7.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineps.drv
Assignee: wine-bugs(a)winehq.org
Reporter: davech(a)t-online.de
Distribution: ---
Finale 27 doesn't print glyphs from SMuFL fonts (https://www.smufl.org/) which
use glyphs in the Unicode private-use area from E000. Files using legacy fonts
(glyphs in the range 0000-00FF) print correctly, but SMuFL is the standard for
new files.
--
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=55647
Bug ID: 55647
Summary: kernel32:heap - test_GlobalMemoryStatus() gets a bad
ullAvailVirtual value on macOS
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:heap - test_GlobalMemoryStatus() gets a bad ullAvailVirtual value on
macOS:
heap.c:3628: Test failed: got ullAvailVirtual 0x7ffffeb62000
See https://test.winehq.org/data/patterns.html#kernel32:heap
These failures currently are systematic but mysteriously did not happen from
2023-08-23 to 2023-09-18 (except for 2023-08-30, see Remi's rbernon-macos-*
cloud test machines).
--
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=55646
Bug ID: 55646
Summary: USB audio playback no sound
Product: Wine
Version: 8.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bghome(a)gmail.com
Distribution: ---
Created attachment 75184
--> https://bugs.winehq.org/attachment.cgi?id=75184
wine debug output
I'm experimenting with running Rekordbox application with the USB audio
interface DDJ-400.
The application list the device as audio interface, but when selected from the
GUI not able to play audio. All I know is that the USB interface is connected
via WASAPI low level interface.
I went through suggestions on this page https://wiki.winehq.org/Sound. Started
with clean wine prefix directory. Next installed native dsound, directmusic DLL
overrides, but it did not make a difference.
I can see the USB device on the Audio tab of winecfg, even can play and hear
the test sound. But no sound from the application.
I attached the debug output.
Can I get any help what else to check or how to debug the issue further?
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.
https://bugs.winehq.org/show_bug.cgi?id=50577
Bug ID: 50577
Summary: Saya no Uta: hangs on RtlpWaitForCriticalSection
Product: Wine
Version: 6.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: pernegger(a)gmail.com
Distribution: ---
Created attachment 69251
--> https://bugs.winehq.org/attachment.cgi?id=69251
terminal output at default settings
Note: This is about the Japanese "Windows 10 compatible" release, not an
English localised one. There is no demo version, I'm afraid.
The game runs fine--until it hangs at:
012c:err:ntdll:RtlpWaitForCriticalSection section 103971A4 "?" wait timed out
in thread 012c, blocked by 0024, retrying (60 sec)
The hang may happen, after as little as 1 min, sometimes it's 10 min, and I
might have made it 20 min once. When it happens, it does not recover, the
message just repeats every once in a while.
I'm using the Ubuntu packages from the official winehq repo. Originally I tried
with wine-staging 6.0, then I went backwards version by version through
(wine-staging) 5.18, and finally now I'm on (wine-devel) 6.0 for this bug
report. No discernable difference either way. The run in the attached log
happened in a clean prefix (though I admit I may have forgotten to wipe the
prefix between some downgrades).
--
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=54074
Bug ID: 54074
Summary: ws2_32:sock - test_empty_recv() sometimes gets an
ERROR_IO_PENDING error in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ws2_32:sock - test_empty_recv() sometimes gets an ERROR_IO_PENDING error in
Wine:
sock.c:12752: Test failed: got error 997
See https://test.winehq.org/data/patterns.html#ws2_32:sock
This happens about twice per month in the nightly WineTest runs but the first
known instance is on 2022-09-01 on debiant-wow32: there is no record of this
failure happening in the previous 3 months. So it is likely to be caused by
some commit in August.
This is also known to have happened in the GitLab CI environment which impacted
some merge requests (for instance MR!1561 and MR!1485).
--
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=51715
Bug ID: 51715
Summary: crypt32:chain fails on some AMD/Nvidia GPU machines
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: crypt32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
crypt32:chain has the same three failures on a set of Windows machines:
chain.c:3458: Test failed: chainCheck[31]: expected 3 elements, got 4
chain.c:4583: Test failed: simple_chain->cElement = 4
chain.c:4609: Test failed: got string GB, Greater Manchester, Salford, Comodo
CA Limited, AAA Certificate Services, expected US, New Jersey, Jersey City, The
USERTRUST Network, USERTrust RSA Certification Authority
https://test.winehq.org/data/patterns.html#comctl32:header
The only common point is that all these machines have an AMD or Nvidia GPU:
* cw-gtx560 Windows 8.1 Nvidia GTX560 driver 353.82
* cw-gtx560 Windows 10 1507 Nvidia GTX560 driver 391.35
* cw-rx460 Windows 10 1507 AMD RX460 driver 19.11.3
* fgtb-w10pro64 Windows 10 2009 AMD RX550 driver 20.11.3
* fgtb-w10pro64 Windows 10 21H1 AMD RX550 driver 21.8.2
* vn-w10pro Windows 10 21H1 AMD RX570 driver 20.10.35.02
But the failures don't happen whenever there is such a GPU: cw-gtx560-2009 has
the same 391.35 Nvidia driver as cw-gtx560-1507 version and yet does not have
these failures.
--
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=54424
Bug ID: 54424
Summary: user32:edit - test_dbcs_WM_CHAR() fails on Windows in
mixed locales
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:edit - test_dbcs_WM_CHAR() fails on Windows in mixed locales:
edit.c:3407: Test failed: W: got L"\02c6\00ea\201c", expected
L"\4e00\4e8c\4e09"
edit.c:3412: Test failed: W: got "?e\x81gn?O", expected "\x88\xea\x93\xf1\x8eO"
See https://test.winehq.org/data/patterns.html#user32:edit
The failures happen in the w10pro64-mx-MX test configuration. What's special
about it is that it uses a mix of locales:
SystemDefaultLCID 0411
UserDefaultLCID 040c
ThreadLocale 0411
SystemPreferredUILanguages 0412,0409
UserDefaultUILanguage 0412
ThreadUILanguage 0412
Country 231
ACP 932
The failures started happening with the commit that introduced the new tests:
commit cbe3a39b647e029df16faf1dcce2958f1ee418d0
Author: Akihiro Sagawa <sagawa.aki(a)gmail.com>
AuthorDate: Fri Jan 20 23:51:36 2023 +0900
user32/tests: Add DBCS WM_CHAR tests for edit control.
--
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=55405
Bug ID: 55405
Summary: FreeCommander crashing immediately after it starts,
when Windows version is set above Windows XP
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mywine(a)schiermeier-it.de
Distribution: ---
Created attachment 74965
--> https://bugs.winehq.org/attachment.cgi?id=74965
Console log from start of FreeCommander with Windows version set to v10
Installation of FreeCommander 32bit is working without any error.
When it should start it crashes. Depending on the version Windows is set to, it
behaves like this:
Windows XP: works
Windows 7: crash at the start with a stack overflow error, show in a message
box
Windows 10: a window came up and disappears immediately without any message
(box)
Console output for Windows 10 is attached.
--
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=41662
Bug ID: 41662
Summary: Carmageddon (windows 95 version) flickering menus
(possible ddraw issue)
Product: Wine
Version: 1.9.22
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aaronbpaden(a)gmail.com
Distribution: ---
Created attachment 56059
--> https://bugs.winehq.org/attachment.cgi?id=56059
log
AfteCarmageddonr playing a race in Carmadeddon and returning to the menus, the
tops and bottoms of the screen flicker with an image from the last race.
I'm on radeonsi and it could be a driver issue, but from the logs I think it's
a ddraw issue.
It's not a huge problem as far as Carmageddon is concerned, because the menu is
still fully visible and usable.
--
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.