https://bugs.winehq.org/show_bug.cgi?id=51489
Bug ID: 51489
Summary: Monopoly (2012) crashes after rolling dice
Product: Wine
Version: 6.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nonononoki(a)gmail.com
Distribution: ---
Created attachment 70324
--> https://bugs.winehq.org/attachment.cgi?id=70324
Terminal output
The app crashes every time when casting the dices, otherwise it seems to work
fine.
Note: The game is has been removed from the Steam store, but can still be
downloaded if you have bought it.
--
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=50695
Bug ID: 50695
Summary: Roots Magic Version 8 Not Connecting Keypad
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: felix-bearden(a)felixlovesliz.com
Distribution: ---
Beta testing of Roots Magic Version 8, all versions.
Using "Uninstall" the product appears to install correctly. At startup Roots
Magic asks for license confirmation then proceeds to selection of Licensed
System and free system. Selecting Licensed System brings up window to enter
name and key. Clicking in the Name box results in the disappearance of the
cursor and entering the name is not possible. Cancel takes to an error message
but details are not available. This error not on Windows 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.
https://bugs.winehq.org/show_bug.cgi?id=697
jeremiahpwilson(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeremiahpwilson(a)yahoo.com
--- Comment #14 from jeremiahpwilson(a)yahoo.com ---
Is this still an issue with Wine 6.13?
--
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=425
jeremiahpwilson(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeremiahpwilson(a)yahoo.com
--- Comment #44 from jeremiahpwilson(a)yahoo.com ---
Is this still an issue with Wine 6.13?
--
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=230
jeremiahpwilson(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeremiahpwilson(a)yahoo.com
--- Comment #20 from jeremiahpwilson(a)yahoo.com ---
Is this still an issue with Wine 6.13?
--
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=124
jeremiahpwilson(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeremiahpwilson(a)yahoo.com
--- Comment #25 from jeremiahpwilson(a)yahoo.com ---
Is this bug still relevant with Wine 6.13?
--
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=52
jeremiahpwilson(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeremiahpwilson(a)yahoo.com
--- Comment #43 from jeremiahpwilson(a)yahoo.com ---
Can this bug be closed?
--
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=51494
Bug ID: 51494
Summary: Dead Rising 3 makes system unresponsive after launch
Product: Wine
Version: 6.13
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 70334
--> https://bugs.winehq.org/attachment.cgi?id=70334
+d3d11
On first loading screen CPU & GPU fans become crazy.
0180:err:ntdll:RtlpWaitForCriticalSection section 000000014192CEE8 "?" wait
timed out in thread 0180, blocked by 0178, retrying (60 sec)
Before launch strongly recommend prepare wineserver -k command.
--
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=51371
Bug ID: 51371
Summary: Too many fonts slows down kernel32:heap! (caused by
gdi32)
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
In fact having too many fonts slows down the startup of any process that loads
gdi32 (or user32), which is to say essentially every process.
This hits kernel32:heap quite hard because it starts many subprocesses for its
tests. Here's a list of the worst hit tests:
Base Full set of fonts (see bug 51367)
kernel32:heap <1s 13s
comctl32:status <1s 13s
reg.exe:add 3s 17s
regedit.exe:regedit 14s 54s
shell32:shlexec 13s 29s
But it's not just these tests being impacted, it's every one of the 720 test
units, resulting in a full WineTest run taking an extra 9 minutes (on my box,
more on the TestBot's debiant2).
The reason for the slowdown seems similar to the dwrite:font case (bug 51367)
but on the gdi32 side. In particular each process issues quite a lot of these
messages (OPENTYPE_PLATFORM_MAC case iirc) which may or may not be related:
0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
--
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=51367
Bug ID: 51367
Summary: Major dwrite:analyzer, dwrite:layout and dwrite:font
slowdown when adding (CJK) fonts
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: dwrite
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Created attachment 70223
--> https://bugs.winehq.org/attachment.cgi?id=70223
Command and fonts for Debian's locales
Adding fonts causes major slowdowns in dwrite:analyzer, dwrite:layout and
dwrite:font when running in Wine. On my test VM I get the following run times:
Base Full set
dwrite:analyzer <1s 50s
dwrite:layout ~1s 46s
dwrite:font ~2s 85s
On the TestBot's debiant2 VM dwrite:font actually runs in about 118 seconds
with the full set of fonts; which is why it times out about 6% of the time:
https://test.winehq.org/data/patterns.html#dwrite:font
The base set of font packages is:
fonts-dejavu-core
fonts-freefont-ttf
fonts-liberation
fonts-quicksand
The problem is that the base set produces unreadable text when running in a
Chinese, Japanese or Korean locale: all translated strings are replaced with a
set of black squares (surprisingly ar_MA, he_IL, hi_HI are ok). That does not
seem to impact the test results but it does not feel right either. At a minimum
if Debian says a given set of fonts are needed for a locale we should test the
said locale with that set of fonts.
So the full set of fonts was created by installing the font packages for all of
Debian's locale task packages and this is what debiant2 has. See
apt_wine_locales() in wt-install-dev [1]. For reference I attached the
corresponding set of packages.
The run time increase is not concentrated in one specific test_xxx() function
that would iterate over all the fonts. All test_xxx() functions take longer to
run. Even the test_CreateFontFromLOGFONT() run time increased to ~17s (iirc).
Yet it does not look like it's doing all that much.
To speed things up I modified dwrite:font to use multiple threads using the
same approach as d3d10core:d3d10core. However even with 8 threads that only
gained about 4 seconds out of 118s: each individual test function just took
longer.
Is that because of lots of global locking?
Or because each test adds/removes fonts forcing all the other threads to do
many rescans?
Are all fonts reloaded and analyzed despite most fonts not having changed?
[1] https://github.com/fgouget/wt-daily/blob/master/wt-install-dev#L556
--
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.