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=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=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=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.
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=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.
http://bugs.winehq.org/show_bug.cgi?id=36944
Bug ID: 36944
Summary: Hotel Giant 2 crashes frequently
Product: Wine
Version: 1.7.22
Hardware: x86
URL: http://www.fileplanet.com/195342/190000/fileinfo/Hotel
-Giant-2-Demo-%28UK%29
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Created attachment 49051
--> http://bugs.winehq.org/attachment.cgi?id=49051
plain terminal output
The crashes sometimes happen while you're in the menus after starting the game,
but always reproducible when you start a new game (or the tutorial in the demo
version).
When it crashes I can only see the game's own bug reporting window so I can't
get a backtrace.
If I run the game under winedbg the problem is that winedbg doesn't detect the
crash, it's only a bug reporting form that is displayed.
The same problem with Wine 1.2.3/1.4.1/1.6.2/1.7.22
'winetricks wmp9 devenum quartz' doesn't help, they needed to play music and
the intro videos.
Reducing graphical details in the game, disabling audio doesn't help either.
Fedora 20
Nvidia binary drivers 340.24
--
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=36312
Bug ID: 36312
Summary: valgrind shows a couple possible leaks in
oledb32/tests/marshal.c
Product: Wine
Version: 1.7.18
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==8079== 40 bytes in 1 blocks are possibly lost in loss record 255 of 623
==8079== at 0x7BC4C735: notify_alloc (heap.c:255)
==8079== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716)
==8079== by 0x5DA4635: IMalloc_fnAlloc (ifs.c:186)
==8079== by 0x5DA4F50: CoTaskMemAlloc (objidl.h:1236)
==8079== by 0x60FC092: NdrOleAllocate (ndr_ole.c:364)
==8079== by 0x60E3BAC: NdrAllocate (ndr_marshall.c:417)
==8079== by 0x60E97CB: array_read_variance_and_unmarshall
(ndr_marshall.c:2143)
==8079== by 0x60EFB6E: NdrConformantArrayUnmarshall (ndr_marshall.c:3944)
==8079== by 0x60E5B82: PointerUnmarshall (ndr_marshall.c:972)
==8079== by 0x60E775D: NdrPointerUnmarshall (ndr_marshall.c:1572)
==8079== by 0x60E5B82: PointerUnmarshall (ndr_marshall.c:972)
==8079== by 0x60E775D: NdrPointerUnmarshall (ndr_marshall.c:1572)
==8079== by 0x6E533D8: ???
==8079== by 0x6E41ADA: ???
==8079== by 0x497E498: test_IDBProperties (oledb.h:2587)
==8079== by 0x497E861: func_marshal (marshal.c:269)
==8079== by 0x497F65C: run_test (test.h:584)
==8079== by 0x497FA4B: main (test.h:654)
==8663== 48 bytes in 1 blocks are possibly lost in loss record 273 of 623
==8663== at 0x7BC4C735: notify_alloc (heap.c:255)
==8663== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716)
==8663== by 0x59210FA: alloc_bstr (oleaut.c:162)
==8663== by 0x5921490: SysAllocStringLen (oleaut.c:324)
==8663== by 0x59215F2: SysReAllocStringLen (oleaut.c:379)
==8663== by 0x595FE5F: BSTR_UserUnmarshal (usrmarshal.c:175)
==8663== by 0x59614FD: VARIANT_UserUnmarshal (usrmarshal.c:627)
==8663== by 0x6108679: NdrUserMarshalUnmarshall (ndr_marshall.c:4461)
==8663== by 0x610430F: ComplexUnmarshall (ndr_marshall.c:3138)
==8663== by 0x610624F: NdrComplexStructUnmarshall (ndr_marshall.c:3724)
==8663== by 0x610430F: ComplexUnmarshall (ndr_marshall.c:3138)
==8663== by 0x6100E68: array_read_variance_and_unmarshall
(ndr_marshall.c:2267)
==8663== by 0x6107A96: NdrComplexArrayUnmarshall (ndr_marshall.c:4231)
==8663== by 0x60FCB82: PointerUnmarshall (ndr_marshall.c:972)
==8663== by 0x60FDD4D: EmbeddedPointerUnmarshall (ndr_marshall.c:1295)
==8663== by 0x610084B: array_read_variance_and_unmarshall
(ndr_marshall.c:2155)
==8663== by 0x6106B6E: NdrConformantArrayUnmarshall (ndr_marshall.c:3944)
==8663== by 0x60FCB82: PointerUnmarshall (ndr_marshall.c:972)
==8663== by 0x60FE75D: NdrPointerUnmarshall (ndr_marshall.c:1572)
==8663== by 0x60FCB82: PointerUnmarshall (ndr_marshall.c:972)
==8663==
--
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.