https://bugs.winehq.org/show_bug.cgi?id=48912
Bug ID: 48912
Summary: Allow blacklisting unreliable and always new failures
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
A number of tests produce false positives because:
* Either the failure message contains a value that changes with each run (e.g.
an HWND). In some cases these values are really necessary for diagnosis and
moving them to a separate line would make the code quite a bit more complex.
* Or the test fails intermittently and is hard to fix. Sometimes the cause of
the failures may also come from external factors such as bugs in QEmu (for
instance long execution delays causing timeouts).
* Sometimes the intermittent failure is the product of a new Windows version or
configuration, which requires investigating before a fix is found.
In all cases the tests should be fixed eventually, but a solution is needed for
the interim so these tests to not make the TestBot so unreliable that its
results are ignored.
So the goal is to provide a way to blacklist some test failures so they do not
cause a patch to be rejected. Some safeguards are needed to ensure that:
* Failures are not blacklisted lightly. The preference should always be to fix
the test.
* The blacklist does not get so large that it becomes hard to maintain.
* Once a test is fixed the corresponding blacklist entries are removed in a
timely fashion.
* There is still an incentive to fix the tests.
So here is a proposal for implementing this blacklist:
* Each blacklist entry should be associated with a Wine bug describing the
issue. That bug should provide some minimal diagnosis: whether it's a new
Windows behavior, a race condition or some issue that was reported to QEmu.
That would ensure we know why the blacklist entry was added. One could also
check the status of the bug when reviewing the blacklist entries. A closed bug
would be a strong hint that the blacklist entry is no longer needed.
* Rather than blacklisting whole test units, blacklist entries should target
specific test failures via a regular expression. Besides being finer grained
this would be useful for cases like user32:win which has different issues
depending on the locale and where each should be linked to a different bug
(bugs 48815, 48819 and 48820).
* The TestBot should record when each blacklist entry was last used. This
relies on having the above regular expression since without it the TestBot
would not know anything beyond 'the test unit was run and had failures'. Also
the regular expression would only be used against *new* failures. So this would
really record the last time the blacklist entry was actually useful.
An entry that was unused for a long time would be a prime candidate for
reviewing the corresponding bug and for removal. (Note: The blacklist would
also be used on WineTest reports so it would get a chance of matching its
target at least 5 days / week).
* The blacklist entries would only be needed for 'base' test configurations
since they are the only ones wine-devel patches run on.
* There should be a page listing the blacklist entries so developers have a
good starting point to work on them.
* Ideally the blacklist page would also point to the tasks where the blacklist
was last used. Since most of the blacklisted failures are either intermittent
or specific to a given test configuration this would make it easier for
developers to find reports where the failure did happen.
Note that Wine VMs often test multiple configurations per task (e.g. wow32
and wow64, different locales), each producing its own test report. So pointing
at just the task would leave the developer guessing which report should be
looked at. But that may be sufficient guidance.
* (test:unit, testbot-vm) tuples make it impossible to target a specific Wine
test configuration such as a specific locale since they all run on the same VM.
Similarly it would make blacklisting bitness-blind on Windows VMs. If necessary
the tuple could be extended either with the specific mission the blacklist
applies to, or with the basename of the corresponding report (the latter being
easier to use in comparisons). Whether that's practical and worth the effort
remains to be determined. One complication for instance is that this would lead
to more blacklist entries: many 64 bit VMs would need two entries, one for 32
bit tests and one for 64 bit tests.
* Pseudo database schema and sample use:
FailureBlacklists
-----------------
PK Bug 48815
PK TestModule user32
PK TestUnit win
Name 0x738 message
FailureRegExp Test failed: hwnd [0-9A-F]{8,16} message 0738
LastUse 2020-03-27
FailureBlacklistVMs
-------------------
PK Bug 48815
PK TestModule user32
PK TestUnit win
PK VMName Entries for w1064v1709, w1064v1809, etc.
(48815, user32, win, w1064v1709)
(48815, user32, win, w1064v1809)
(48815, user32, win, w1064v1809_2scr)
...
FailureBlacklistUses (optionally)
---------------------------------
PK Bug
PK TestModule
PK TestUnit
PK JobId
PK StepNo
PK TaskNo
(48815, user32, win, 68507, 1, 7)
(48815, user32, win, 68508, 1, 7)
...
--
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=48209
Bug ID: 48209
Summary: Ignore random parts of test failure messages
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The TestBot needs to detect if a patch introduces NEW test failures. To do so
it compares the failure messages with those from reference WineTest runs. But
in some cases part of the message changes from one run to the next, causing the
failure to look new.
Of course in all cases the ideal solution is to fix the test so it does not
fail.
Barring that there are also cases where the varying value is not really useful
(e.g. handle or pointer values) and in that case it should just be removed from
the message.
But there may be cases where knowing the value is still useful. So one solution
would be to tag such values so the TestBot knows it can ignore them when
comparing failure messages. For instance they could be enclosed in double
braces, curly braces, or other.
--
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=53759
Bug ID: 53759
Summary: FPGA Programmer can't open port
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 7Cattac(a)gmail.com
Distribution: ---
Created attachment 73229
--> https://bugs.winehq.org/attachment.cgi?id=73229
output log
I'm trying to use FPGA Programmer
(https://www.fpga-cores.com/software/fpga-programmer/) to broadcast UPD
packages to my FPGA.
Starting it up has no issues, but when it depends a device in the network it
hangs for a couple of minutes and the app runs very slowly.
Trying to upload a .bin takes a long time and gives an error saying "can't open
port", when that happens "010c:fixme:progress:ProgressWindowProc state 2 not
yet handled" is spammed in the logs.
Wine version: Wine-staging 7.18
FPGA Programmer version: 1.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=53758
Bug ID: 53758
Summary: Prototype freezes and crashes after intro/in menu
Product: Wine
Version: 7.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: odecif(a)gmail.com
Distribution: ---
Created attachment 73228
--> https://bugs.winehq.org/attachment.cgi?id=73228
Execution log
After a fresh install from DVD-disc on a clean 64-bit prefix, if I run the game
using "WINEPREFIX=<prefix> wine prototypef.exe" in the games installation
folder, the game start up showing a cinematic of some license-text and the
developers logo and transfers to the games main menu. Here a modal shows with
some information regarding save game and here is when the game freezes.
winetricks dxvk removes said freeze and the game is playable.
GTX 760M
i5-6300HQ
Budgie DE
Manjaro 22
Kernel 5.4.212-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=52689
Bug ID: 52689
Summary: NVCUDA: Daz Studio 4.20 and CUDA SDK11 implementation
Product: Wine-staging
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cybermax(a)dexter.no
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 72031
--> https://bugs.winehq.org/attachment.cgi?id=72031
Series of patches to implement basic SDK11 functionality
Recently DAZ Studio4 updated to 4.20 and the Iray engine also got updated to
the point it requires support for CUDA 11.4
I have worked through a great deal of the issues regarding support for SDK
11.4, aside from the D3D9/10/11 elements that have no equivalent Linux support.
The result is adding a few functions to the nvcuda implementation in
wine-staging. (Attachment with a series of 4 patches).
I have not yet been able to get SDK 11.6 samples to run, as this will (for now)
fail the CUDA runtime validation.. but DAZ Studio 4.20.1 is running fine.
2022-03-17 22:24:11.731 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info :
NVIDIA display driver version: 510.54
2022-03-17 22:24:11.732 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info :
Your NVIDIA driver supports CUDA version up to 11.6; iray requires CUDA version
11.4; all is good.
2022-03-17 22:24:11.732 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info :
Using iray plugin version 5.3, build 349500.7063 n, 18 Jan 2022,
nt-x86-64-vc142.
2022-03-17 22:24:11.768 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info :
CUDA device 0 (NVIDIA GeForce RTX 2070): compute capability 7.5, 7.773 GiB
total, 7.229 GiB available, display attached
I have built and run the main demo samples from the cuda-samples source github,
aswell as 30 some samples in addition to that, compiled with VS2019 and using
the SDK11.4 runtime library.
--
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=53753
Bug ID: 53753
Summary: TikTok Live studio will not run
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: erik(a)dansbo.dk
Distribution: ---
Created attachment 73219
--> https://bugs.winehq.org/attachment.cgi?id=73219
backtrace of error from wine
TikTok Live Studio crashes before even starting up.
--
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=53751
Bug ID: 53751
Summary: RollerCoaster Tycoon 1-2: rename dialog is hidden
behind game screen
Product: Wine
Version: 6.1
Hardware: x86-64
URL: https://archive.org/download/RollerCoasterTycoon2Demos
/RCT2_Demo.exe
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: hverbeet(a)gmail.com
Regression SHA1: 4ce1d7f93a35322d149cbde29d619e2580159a80
Distribution: ---
Created attachment 73216
--> https://bugs.winehq.org/attachment.cgi?id=73216
What it looked like the last time it worked
When you click on an attraction or person in RollerCoaster Tycoon 1 & 2 you can
rename the object. A standard windows text-box should open in the upper-left
corner of the screen letting you input a new name for that object.
This text window is hidden behind the game screen when it is opened thus it is
inaccessible/not usable.
Tried with virtual desktop mode and fullscreen: both have the same issue.
Nothing obvious appears in the terminal.
Last version when it worked: Wine-6.0.
Bisecting revealed commit 4ce1d7f93a35322d149cbde29d619e2580159a80
was the culprit. Can't revert it on current Wine but the rename window appears
properly with the previous commit.
Steps to reproduce in RCT 2 demo:
Start a new game with the left-most icon at the bottom, select either "Crazy
Castle" or "Six Flags Belgium" scenario.
Left-click on an object to open an information window, select the rename icon
(looks like a brownish name-tag). A text-box is opened but it is placed behind
the game screen.
RCT2_Demo.exe (69M)
md5: 2d07a92c72ed5077a933ec9bf395f4d2
Still present in wine-7.18-120-g001665d7354.
Xfwm4 version 4.16.1
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.141.03
OpenGL core profile shading language version string: 4.60 NVIDIA
--
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=53740
Bug ID: 53740
Summary: Space Rangers 2 - Dominators Reloaded (2.0) - stack
overflow error
Product: Wine
Version: 7.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: VladimirVSC(a)yandex.ru
Distribution: ---
Created attachment 73182
--> https://bugs.winehq.org/attachment.cgi?id=73182
Space Rangers 2 Error output
The game doesn't start, saying something about a "stack overflow 1156 bytes" in
thread 0024 (this number is different every time starting the game). The bug is
true for both development 7.18 and stable 7.0 versions.
--
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=6847
auxsvr(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |auxsvr(a)yahoo.com
--
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=53745
Bug ID: 53745
Summary: English letters don't appear in Arabic session
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: moceap(a)hotmail.com
Distribution: ---
Created attachment 73190
--> https://bugs.winehq.org/attachment.cgi?id=73190
bug description
English letters don't appear in Arabic session, see the attachments.
--
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=36103
Bug ID: 36103
Summary: kernel32/tests/loader shows lots of invalid reads in
thread.c
Product: Wine
Version: 1.7.17
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, testcase
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==9219== Invalid read of size 4
==9219== at 0x7BC55D91: MODULE_DllThreadAttach (loader.c:1287)
==9219== by 0x7BC8E3D2: start_thread (thread.c:423)
==9219== by 0x4218F92: start_thread (pthread_create.c:309)
==9219== by 0x431D7ED: clone (clone.S:129)
==9219== Address 0x611eb04 is on thread 1's stack
==9219==
==9219== Invalid read of size 4
==9219== at 0x7BC1EAF3: __x86.get_pc_thunk.bx (in
/home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so)
==9219== by 0x7BC8E3D2: start_thread (thread.c:423)
==9219== by 0x4218F92: start_thread (pthread_create.c:309)
==9219== by 0x431D7ED: clone (clone.S:129)
==9219== Address 0x611eacc is on thread 1's stack
==9219==
there's also one:
==30099== 2,020 bytes in 1 blocks are possibly lost in loss record 225 of 244
==30099== at 0x7BC4C735: notify_alloc (heap.c:255)
==30099== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716)
==30099== by 0x4E07A19: get_tls_data (test.h:244)
==30099== by 0x4E07B03: winetest_set_location (test.h:279)
==30099== by 0x4D836B8: dll_entry_point (loader.c:1433)
==30099== by 0x7BC52FC0: ??? (loader.c:138)
==30099== by 0x7BC555FE: MODULE_InitDLL (loader.c:1068)
==30099== by 0x7BC55DE7: MODULE_DllThreadAttach (loader.c:1281)
==30099== by 0x7BC8E446: start_thread (thread.c:423)
==30099== by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so)
==30099== by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so)
==30099==
--
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=53519
Bug ID: 53519
Summary: kernel32:comm - test_AbortWaitCts() once failed due to
an unexpectedly short wait
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:comm - test_AbortWaitCts() once failed due to an unexpectedly short
wait:
comm.c:1586: Test failed: Unexpected time 171, expected around 500
https://test.winehq.org/data/patterns.html#kernel32:comm
This failure happened on 2022-08-05 on w10pro64-ko-64.
Maybe the system time got changed during the test? (see bug 53516)
--
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=53735
Bug ID: 53735
Summary: Battle.net does not log in, shows error log, in
Bottles
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: richardjecooke(a)pm.me
Distribution: ---
Created attachment 73172
--> https://bugs.winehq.org/attachment.cgi?id=73172
error log
See attachment
--
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=53400
Bug ID: 53400
Summary: wine-gecko 2.47.3 fails to build on host systems with
python 3.11
Product: Wine-gecko
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-gecko-unknown
Assignee: jacek(a)codeweavers.com
Reporter: mike(a)cchtml.com
Distribution: ---
In similar vain as bug 51918 it is that time again. Fedora 37 (Rawhide,
unreleased) has Python 3.11. There are currently two failures I have
encountered. I've patched one.
1. inspect.getargspec() changes in Python 3.11
--- a/python/mach/mach/decorators.py 2022-07-12 08:33:06.000000000 -0500
+++ b/python/mach/mach/decorators.py 2022-07-22 08:55:21.510849725 -0500
@@ -111,7 +111,7 @@
pass_context = False
if inspect.isfunction(cls.__init__):
- spec = inspect.getargspec(cls.__init__)
+ spec = inspect.getfullargspec(cls.__init__)
if len(spec.args) > 2:
msg = 'Mach @CommandProvider class %s implemented incorrectly. ' +
\
2. Setting up the python virtualenv fails.
0:01.29 checking for python3... /usr/bin/python3
0:01.29 Creating Python environment
0:01.31
/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py:10:
DeprecationWarning: The distutils package is deprecated and slated for removal
in Python 3.12. Use setuptools or check PEP 632 for potential alternatives
0:01.31 import distutils.sysconfig
0:01.31
/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py:10:
DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig
instead
0:01.31 import distutils.sysconfig
0:01.34
/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/virtualenv/virtualenv.py:24:
DeprecationWarning: The distutils package is deprecated and slated for removal
in Python 3.12. Use setuptools or check PEP 632 for potential alternatives
0:01.34 import distutils.spawn
0:01.35
/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/virtualenv/virtualenv.py:25:
DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig
instead
0:01.35 import distutils.sysconfig
0:01.37 Using base prefix '/usr'
0:01.37 New python executable in
/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv/bin/python3
0:01.37 Not overwriting existing python script
/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv/bin/python
(you must use
/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv/bin/python3)
0:01.37 ERROR: The executable
/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv/bin/python3
is not functioning
0:01.37 ERROR: It thinks sys.prefix is '/usr' (should be
'/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv')
0:01.37 ERROR: virtualenv is not compatible with this system or executable
0:01.38 Traceback (most recent call last):
0:01.38 File
"/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py",
line 486, in <module>
0:01.38 manager.ensure()
0:01.38 File
"/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py",
line 128, in ensure
0:01.38 return self.build()
0:01.38 ^^^^^^^^^^^^
0:01.38 File
"/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py",
line 382, in build
0:01.38 self.create()
0:01.38 File
"/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py",
line 147, in create
0:01.38 raise Exception(
0:01.38 Exception: Failed to create virtualenv:
/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv
--
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=53734
Bug ID: 53734
Summary: Ghost Master: Laggy/Broken FMV cutscene playback
Product: Wine
Version: 7.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: varrok(a)gmail.com
Distribution: ---
Hi,
The game Ghost Master uses Windows Media Video files for FMV cutscenes (they
lie unprotected in the game files), sadly they don't seem to play properly from
inside of the game, they seem to update a frame after every couple dozen
seconds.
Specs:
Arch Linux 5.18.16-arch1-1
Nvidia GTX 1080 (properitary Nvidia drivers 515.65.01)
What I tried:
- current stable wine version
- current dev wine version = wine-7.18-37-g2a4ec7dafc7
- both 32bit and 64bit wine prefixes
Steps to reproduce:
- Download full game or demo
https://www.moddb.com/games/ghost-master/downloads/ghost-master-demo
- Launch it, in main menu press New Game, it should instantly play the file
sha5a_lo.wmv (demo), though it has issues.
Judging from:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=30222 and
protondb reports, it seems like a common issue with the game
--
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=52493
Bug ID: 52493
Summary: CPU architecture entry on AppDB test reports
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: joseskvolpe(a)gmail.com
Distribution: ---
I've talk about it on the forum
https://forum.winehq.org/viewtopic.php?f=11&t=36163&p=135972#p135972
Today, AppDb only asks us for GPU and GPU driver on the hardware section before
posting data reports. With the adoption of ARM architecture on mainline Windows
and popularization of ARM laptops, more Windows applications will be released
for ARM architecture aswell, some Linux distributions are being ported to ARM
too.
That means, before Wine did had compatibility on other CPU architectures but
Windows applications didn't had it, so tests reports were mostly focused for
x86 architectures and other architectures had 0 guarantee to be supported,
things are about to change today with x64 and ARM becoming supported by
Microsoft.
There's options to emulate x86 and x64 architectures on ARM, even on Windows.
There's Rosetta on MacOS and box86/box64 on GNU/Linux. However, emulators
aren't perfect and CPU architecturse, emulated or natively, are going to imply
in app compatibility and in future test reports. While another application
might work perfect on x86, it might fail or be buggy in ARM both natively or
emulated, even if the application has support to it. To prevent confusion on
the next reports, we'll need to leave CPU architectures in consideration.
¿What do you think about 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=48468
Bug ID: 48468
Summary: Add "Bronze" and "Garbage" top-10 lists to the appdb
landing page
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jonwsb(a)gmail.com
Distribution: ---
The top-10 lists on appdb.winehq.org are a very nice feature of the site. Their
purpose of showing off what popular programs work in wine is very useful to new
users and I think adding the "Bronze" and "Garbage" ratings to the page will
also provide valuable information to new users as well as contributors. For new
users it will give quick access to information on programs they may be planning
on attempting to use with wine. For advanced users and contributors it will be
a useful tool to gauge which programs need high quality testing and possibly
give inspiration for developing patches to improve bronze and garbage rating
entries.
My biggest concern with adding these top-10 lists would be increasing the size
of the page even more than it already is though it will also probably drive
users of the appdb to vote for more applications overall.
--
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=51980
Bug ID: 51980
Summary: Fedora 35 repo link is brokern
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: craig.ziesman(a)gmail.com
Distribution: ---
Trying to add the Fedora 35 repo using ```dnf config-manager --add-repo
https://dl.winehq.org/wine-builds/fedora/35/winehq.repo``` but it returns a 404
status code
--
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=53351
Bug ID: 53351
Summary: Page translation doesn't always work
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jkfloris(a)dds.nl
Distribution: ---
The home page is not translated with the "Change Language" link at the bottom
of the page.
Steps to reproduce
- Open Google Chrome (103.0.5060.114) in incognito mode
- Go to https://www.winehq.org/
- Change the language with the link at the bottom of the page
After this, the home page is still in English instead of the selected language.
It gets even weirder
For example, choose French (Français)
Go to the "Donate" page (This page is in French)
On this page change the language to Dutch
The homepage is now displayed in English again. Select the "Donate" page again.
The page is still in French instead of Dutch.
Go back to the home page and choose "About"
Now this page is in Dutch
--
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=53733
Bug ID: 53733
Summary: Forza Horizon 5 will not boot when using Wine.
Product: Wine
Version: 7.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yottamxt(a)gmail.com
Distribution: ---
Created attachment 73168
--> https://bugs.winehq.org/attachment.cgi?id=73168
The Wine backtrace.
When I try to boot Forza Horizon 5 on my Linux machine (Fedora 36), it shows
the booting splash image, but after a while, it triggers a Wine error which
reports that it had an error and needs to 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=53729
Bug ID: 53729
Summary: Dauntless crashes frequently
Product: Wine
Version: 7.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: galcian79(a)gmail.com
Distribution: ---
Created attachment 73162
--> https://bugs.winehq.org/attachment.cgi?id=73162
wine log from Heroic Games Launcher app.
After a recent update, the game crashes frequently with: "*** stack smashing
detected ***: terminated".
Not sure if it's a game or wine bug.
--
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=32880
Bug #: 32880
Summary: Some Menus not working in Microsoft Money 2005
(version 14)
Product: Wine
Version: 1.5.22
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: junk_2010(a)live.co.uk
Classification: Unclassified
Installed wine 1.5.22 on Ubuntu 12.04.1 (32 bit). Clean install with previous
.wine directory removed.
Program installed ok, this is as with previous versions of wine (1.4.1 and
1.5.19).
Good news. The program started up. Previously (1.4.1 and 1.5.19) it always
crashed. The only way to go any further would have been to install ie6. Not
required today.
When I tried to use the "lower" menu row in the program, the mouse highlighted
the menu names, but nothing happened when pressed. Output in the terminal was
like:
fixme:ieframe:navigate_url Unsupported args (Flags 0x115c430:19;
TargetFrameName 0x115c440:0)
fixme:ieframe:navigate_bsc Navigation canceled
fixme:urlmon:URLMoniker_BindToObject use running object table
fixme:ieframe:ClOleCommandTarget_Exec Unimplemented cmdid 28
fixme:ieframe:object_available Could not get IHlinkTarget interface
fixme:ieframe:ClOleCommandTarget_Exec Unimplemented cmdid 67 of
CGID_ShellDocView
fixme:ieframe:ClOleCommandTarget_Exec Unimplemented cmdid 63 of
CGID_ShellDocView
fixme:ieframe:ClOleCommandTarget_Exec Unimplemented cmdid 84 of
CGID_ShellDocView
fixme:jscript:JScript_SetScriptState unimplemented state 3
fixme:ieframe:ClOleCommandTarget_Exec Unimplemented cmdid 25
fixme:ieframe:ClOleCommandTarget_Exec Unimplemented cmdid 26
When I tried the upper menu row some of these did work. However, the program
crashed when the upper "File" menu was pressed. The terminal output was:
fixme:ieframe:get_location_url semi-stub
fixme:ieframe:get_location_url semi-stub
fixme:imm:ImmDisableIME (-1): stub
fixme:advapi:RegisterEventSourceW ((null),L"Microsoft Money Error Reporting"):
stub
fixme:advapi:ReportEventA
(0xcafe4242,0x0001,0x0000,0x000003e8,(nil),0x0005,0x0000005f,0x60d7e4,0x60d39c):
stub
fixme:advapi:ReportEventW
(0xcafe4242,0x0001,0x0000,0x000003e8,(nil),0x0005,0x0000005f,0x13a060,0x60d39c):
stub
err:eventlog:ReportEventW L"msmoney.exe"
err:eventlog:ReportEventW L"14.0.0.1105"
err:eventlog:ReportEventW L"kernel32.dll"
err:eventlog:ReportEventW L"5.1.2600.2180"
err:eventlog:ReportEventW L"0002bb85"
fixme:advapi:DeregisterEventSource (0xcafe4242) 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=53720
Bug ID: 53720
Summary: Starcraft Remastered:
Product: Wine-staging
Version: 7.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dimich.dmb(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 73151
--> https://bugs.winehq.org/attachment.cgi?id=73151
Wine running Starcraft log
Selecting "Local Area Network" in "Select Connection" causes following message:
"Bonjour is required to search for available LAN".
After selecting "Ok" following message appears: "Failed to activate the Bonjour
service."
Only once i got no messages/errors with wine-staging-7.18 in 10-15 attempts.
Downgrade wine-staging to v7.17 solves the problem. Looks like regression of
https://bugs.winehq.org/show_bug.cgi?id=52335
Starcraft Remastered v1.23.10.11109
Arch Linux, x86_64, kernel 5.19.10-arch1-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=47677
Bug ID: 47677
Summary: Age Of Empires 2 crash before starts an singleplayer
game
Product: Wine
Version: 4.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: franco_952010(a)hotmail.com
Distribution: ---
Created attachment 65131
--> https://bugs.winehq.org/attachment.cgi?id=65131
Age Of Empires 2 1.0c crash
condition:
age of empires: age of king installed with 2.0a patch
age of empires: the conquerors installed
aoc 1.0c patch installed
aoc no-cd applied
userpatch appllied
.
in 4.0.1 didn't happen this...
--
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=53629
Bug ID: 53629
Summary: mixed gdi/dx9 rendering leads to a failure to render
Product: Wine
Version: 7.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
The summary is a guess and probably a wrong one.
wine version is set to 7.15, but it was first observed around 7th Oct 2020.
Anyway, in two games of a single dev (not really an engine, unless in the
home-cooked sense) the games start, show a standard window then fail to render
anything more. Mouse cursor still disappears upon entering the window and
reappears upon leaving.
One is steamid 1289960, other currently pending (there are demos available for
the original, non-steam versions).
Initially I thought it was something like the Diablo problem, even though ddraw
isn't involved, yet there was something about child windows in 'win' channel.
Then I've ran apitrace.
After first Present call, a Reset call is made repeatedly and each time it
fails.
Also of note is the fact that a native d3dx9_31 is required, otherwise a crash
with something looking like a stack corruption ('Unhandled page fault on read
access to CCCCCCCC at address ...') happens immediately.
Potentially of note: the hack makes things work with gl renderer, vulkan is
still broken, though that might be due to the child window bug; gdi renderer
makes things crash immediately with or without the hack.
If reset_enum_callback (in dlls/d3d9/device.c) is made to return D3D_OK in both
Texture and Surface step, things seem to work correctly, but that looks like a
leak-inducing step.
In vulkan case, console is flooded with repeated:
<threadid>:err:d3d:adapter_vk_draw_primitive Failed to apply draw state.
<threadid>:err:d3d:wined3d_context_vk_apply_draw_state Failed to get graphics
pipeline.
--
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.