https://bugs.winehq.org/show_bug.cgi?id=45960
Bug ID: 45960
Summary: Editpad Lite 7 siaplay empty boxes instead of text in
some menus
Product: Wine
Version: 3.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shagooserver(a)gmail.com
Distribution: ---
Created attachment 62507
--> https://bugs.winehq.org/attachment.cgi?id=62507
screenshot of problem
When trying to set the default font, the drop-down screen offers many
selections of empty boxes rather than text, see the attachment.
This screen is accessed by:
1/ Options>Configure File Type
2/ On the Editor Options tab click the Edit button next to the "Default text
layout" drop-down box
3/ in the Text Layout Configuration Window click the down arrow to the right of
of the large drop down box to select fonts in the 2nd-from-last left hand
window pane called Main Font.
The installer is here: https://www.editpadlite.com/download.html
This may be the same issue as bug 45959 which I also submitted, I do not have
sufficient knowledge to make that judgement.
My system:
Kubuntu 18.04.01
Wine version 3.17
--
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=44503
Bug ID: 44503
Summary: Failed install of Corel PSP X6
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: neil.ray(a)usa.com
Distribution: ---
Created attachment 60460
--> https://bugs.winehq.org/attachment.cgi?id=60460
Failed install of Corel PSP X6
Attempted to install, via wine, Corel Paint Shop Pro X6. Encountered a fatal
error and was unable to continue. Backtrace log attached. My OS is Linux Mint
18.3 on a 32bit machine.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=28126
Summary: Big Race USA Demo: menu animations and music too fast
Product: Wine
Version: 1.3.26
Platform: x86-64
URL: http://games.softpedia.com/get/Games-Demo/Pro-Pinball-
Big-Race-USA-Demo.shtml
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: asb(a)asbradbury.org
Created an attachment (id=36038)
--> (http://bugs.winehq.org/attachment.cgi?id=36038)
bigraceusademo.exe on wine 1.3.26 (no debug channels)
In the Big Race USA Demo (or the full Big Race USA game as sold by gog.com),
the menu animations (blinking of text and spinning of icons) move far too fast.
Additionally, the game music and sound effects are incredibly fast and
'crackly'. I mention both issues as it seems likely they have the same root
cause. My CPU is an i5-750 at 2.67Ghz (presumably this problem may not occur on
something much slower like an Atom).
Workaround: Use cpulimit on the bigraceusademo.exe process. Turning on a noisy
enough debug channel will also slow the process down enough that the sound
problem will go away.
To reproduce, just install the linked demo, run bigraceusademo.exe and observe
the rapidly spinning menu items and corrupted audio output.
$ sha1sum bigrace.zip
fd5cbfc5da9dd29a010cb02a1f847a753a65c2b2 bigrace.zip
The demo and full game both work perfectly in Win 7 x64 on the same hardware.
I tested in wine 1.0.1, 1.2.3, 1.3.26 and some versions in between. The problem
was less pronounced in 1.0.1 (likely due to worse overall performance).
I'll attach the output from 1.3.26, though the only relevant line appears to be
the following, which seems to be a likely culprit for the problem:
fixme:ddraw:ddraw7_WaitForVerticalBlank iface 0x1557b0, flags 0x1, event (nil)
stub!
--
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=47229
Bug ID: 47229
Summary: gog.com - The Void: crashes when entering two game
locations
Product: Wine
Version: 4.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dron2065(a)rambler.ru
Distribution: ---
Created attachment 64501
--> https://bugs.winehq.org/attachment.cgi?id=64501
Output log of wine before crashing
Video game The Void (GOG edittion) crashes with "Unhandled page fault on read
access to 0x00000000 at address 0x1953eb7" in the same locations every time.
It's make finish game impossible. There are at least two problem places at
game.
See more in attachment log.
--
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=47720
Bug ID: 47720
Summary: eac3to performance issues
Product: Wine
Version: 4.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shagooserver(a)gmail.com
Distribution: ---
Created attachment 65192
--> https://bugs.winehq.org/attachment.cgi?id=65192
wine version
eac3to used to work well a year ago but now has a few issues which need to be
addressed not least of which is it takes 4 times longer to demux than it does
when run under windows. Also the lossless check seems not to be done and
certainly is not reported. A number of warnings which are generated apparently
needlessly. I have attached screen shots from under wine and under windows
which will show clearly the issues.
--
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=51312
Bug ID: 51312
Summary: dxgi:dxgi: Wrong screen mode order on AMD GPUs
(cw-rx460)
Product: Wine
Version: 6.10
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
dxgi:dxgi gets failures of the form:
https://test.winehq.org/data/patterns.html#dxgi:dxgi
dxgi.c:1460: Test failed: Mode 3: Modes should have been sorted, refresh rate
59.940060 < 85.000000.
dxgi.c:1460: Test failed: Mode 22: Modes should have been sorted, refresh rate
59.940060 < 85.000000.
dxgi.c:1460: Test failed: Mode 55: Modes should have been sorted, refresh rate
59.940060 < 75.000000.
* These failures happen on all available Windows versions (8.1 to 10 2009).
* They also happen regardless of the Radeon driver version: 19.11.3 to 21.4.1.
* They don't happen on machines with any other GPU (cw-gtx560 and QEmu VMs).
* They also happen systematically so are not probably caused by a threading
issue.
* So this really looks like a Radeon-specific behavior.
The failing test was introduced by the following commit:
commit eb2028fa90c41d3b7b8b4f924cd86059c5ba1e0d
Author: Andrew Eikum <aeikum(a)codeweavers.com>
AuthorDate: Mon Oct 28 16:59:18 2019 +0330
dxgi: Sort reported output modes.
Sekiro: Shadows Die Twice depends on this for its mode switching.
Signed-off-by: Andrew Eikum <aeikum(a)codeweavers.com>
Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
Does the application crash on Windows machines with an AMD GPU?
Or does the Radeon driver return the wrong order only on some GPUs?
If the application does not crash maybe our order specification is a bit too
strict?
Given that an application depends on this we probably want Wine to respect the
ordering.
Just add a broken()?
--
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=50368
Bug ID: 50368
Summary: DragonAge Origins Launcher doesn't toggle music status
Product: Wine
Version: 6.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: winmm&mci
Assignee: wine-bugs(a)winehq.org
Reporter: lorenzofer(a)live.it
Distribution: ArchLinux
Until recently the Dragon Age Origins Launcher didn't work at all becouse bug
#44185 that was recently fixed.
However now, the laucnehr start, it play correctly the music but the toggle
button to disable/enable the music doesn't work.
This is the flow of what seems the issue:
0164:trace:mci:mciSendStringW (L"pause all", 0074EE48, 100, 00000000)
0164:trace:mci:mciSendStringW verb=L"pause" on dev=L"all"; offset=4
0164:trace:mci:mciSendStringW [-1, MCI_PAUSE, 00000000, 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000]
0164:fixme:mci:MCI_SendCommand unhandled MCI_ALL_DEVICE_ID
0164:trace:mci:mciSendStringW => 117
wine isn't handling correctly the MCI_ALL_DEVICE_ID case in cases others then
closing the device.
This affect just the launcher (the game should work properly if not regressed
recently, still didn't try) so low priority, but other programs may be
affected.
--
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=51217
Bug ID: 51217
Summary: RtlWow64IsWowGuestMachineSupported() check fails on
w1064v1607 for the 32-bit ntdll:info
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
ntdll:info has a failure on w1064v1607 (Windows 10 64-bit version 1607 running
the 32-bit tests):
https://test.winehq.org/data/patterns.html#ntdll:info
info.c:3024: Test failed: wrong result 0
This is a check of the RtlWow64IsWowGuestMachineSupported() result.
The commit that introduced this check is:
commit 4f8ede8e7665328a2a3ccd303875e239bf443512
Author: Alexandre Julliard <julliard(a)winehq.org>
AuthorDate: Thu Apr 29 17:15:15 2021 +0200
ntdll: Implement RtlWow64IsWowGuestMachineSupported().
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=51078
Bug ID: 51078
Summary: mshtml:events hangs on Windows 10 1709
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: mshtml
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Created attachment 69941
--> https://bugs.winehq.org/attachment.cgi?id=69941
Patch to more reliably reproduce the hang
mshtml:events sometimes hangs on Windows 10 1709:
http://winetest.dolphin/data/patterns.html#mshtml:events
For some reason this only happens on Windows 1709 (the reports say this is
mshtml 11.0.16299.309).
The test proceeds all the way to the end but then does not exit because the
mshtml component still has threads running:
VSyncHelper
Internet Explorer_Hidden
MSCTFIME UI
Commenting out the test_focus() run gets rid of the hangs.
Also running the test with WINETEST_INTERACTIVE=1 greatly increases the
probability of getting a hang. I attached a patch that does that and can be
used to reproduce the hang on the TestBot's w1064v1709 VM.
So this is clearly related to focus.
--
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=39659
Bug ID: 39659
Summary: comctl32:button test gets unexpected WM_CANCELMODE on
my Windows 8 laptop
Product: Wine
Version: 1.8-rc1
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Created attachment 52866
--> https://bugs.winehq.org/attachment.cgi?id=52866
log of test failure
Test report:
https://test.winehq.org/data/1d19eb15d4abfdd14dccc5ac05b83c0ee1a1ace1/win8_…
Message tests calling SetFocus() on a button fail on my Windows 8 machine,
because they get a WM_CANCELMODE message they weren't expecting. I have no idea
what's special about my setup. It doesn't matter if I run the test stand-alone
or with the full test suite, or if I run it as a dedicated user with a default
configuration.
--
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.