http://bugs.winehq.org/show_bug.cgi?id=30666
Bug #: 30666
Summary: MPEG movie does not play in Capitalism 2 demo
Product: Wine
Version: 1.5.4
Platform: x86
URL: http://www.cnwcentral.com/capitalism-2/demo.shtml
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winegstreamer
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jeremielapuree(a)yahoo.fr
Classification: Unclassified
Created attachment 40144
--> http://bugs.winehq.org/attachment.cgi?id=40144
console output
While playing intro movie of Capitalism 2 demo, one can hear the sound, but
video is playing.
--
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=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=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=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.
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.
http://bugs.winehq.org/show_bug.cgi?id=35478
Bug ID: 35478
Summary: dsdmo.dll not implemented and not available to install
via winetricks.
Product: Wine
Version: 1.7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: sov.info(a)mail.ru
Classification: Unclassified
This componets essential for running some games - Silent Hill 4 & 3 (footstep
sounds).
--
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.