http://bugs.winehq.org/show_bug.cgi?id=35137
Bug ID: 35137
Summary: Hitman: Blood Money demo needs native d3dx9_27
Product: Wine
Version: 1.7.8
Hardware: x86
URL: http://www.gamershell.com/download_13964.shtml
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: wine-bugs(a)winehq.org
Classification: Unclassified
Demo crashes without native d3dx9_36
fixme:d3dx:ID3DXEffectCompilerImpl_CompileEffect iface 0x6fd8e660, flags 0x500,
effect 0x122a56c, error_msgs 0x122a564 stub
and also needs native d3dx9_27 because after intro movie I can't see the main
menu.
--
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=17836
Summary: Motocross Madness 2 crashes at start
Product: Wine
Version: 1.1.17
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
Created an attachment (id=20098)
--> (http://bugs.winehq.org/attachment.cgi?id=20098)
trace and disassembly of crash location
In AppDB, people have reported Motocross Madness 2 (mcm2) crashing in the intro
but nobody had filed a bug yet. The backtrace makes it look like mcm2 crashes
in, or immediately after, quartz.dll or amstream, after accessing ui\events.avi
at the start of the program, after displaying for some seconds the stunt &
warnings picture also known from the demo.
The demo is not affected and proceeds from the intro picture to the menu.
A log extract (+almost-all,-relay,-nls) from around the exception is attached.
The processed file UI/events.avi is an Intel Indeo v5 video. The installer did
not complain that Indeo is mising! Replacing it with a Cinepak avi, with an
empty file, deleting it or installing iv5 still produces crashes at the same
location in mcm2. Same with clicking to skip the intro picture or disabling
quartz.dll.
MCM2 suffers from SafeDisk 1.41.000 protection so it would not run as is in
wine (or rather, it crashes much earlier). I tried 2 different cracks, both
produced the same exception.
--
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=37913
Bug ID: 37913
Summary: Inconsistent rounding behaviour for sprintf
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: christopherwuy(a)gmail.com
Distribution: ---
sample source code and output demonstrating the problem:
#include <iostream>
#include <stdio.h>
using namespace std;
int main()
{
double a;
a = 3.5;
char *tmp = new char(100);
char fmt[18] = " is %.0f";
sprintf(tmp, fmt, a);
cout<<endl<<a<<tmp<<endl<<endl;
a = -4.5;
sprintf(tmp, fmt, a);
cout<<endl<<a<<tmp<<endl<<endl;
a = -0.5;
sprintf(tmp, fmt, a);
cout<<endl<<a<<tmp<<endl<<endl;
a = 2597.625;
printf("%.3f", a);
sprintf(tmp, " is %.2lf", a);
cout<<tmp<<endl<<endl;
}
This code running by wine 's Output is:
3.5 is 4
-4.5 is -4
-0.5 is -0
2597.625 is 2597.62
while windows' output is:
3.5 is 4
-4.5 is -5
-0.5 is -1
2597.625 is 2597.63
It indicated that Wine's sprintf used rounding rule which is Round half to
even, while windows used Round half away from zero.
You can find a detailed discussion of 'similar bug' form
https://sourceware.org/bugzilla/show_bug.cgi?id=4943
--
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=24320
Summary: Unexpected DetectEnvStatus.exe crash with Cisco Quick
VPN Client (QVPN 1.4.1.2)
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ethanfharris(a)gmail.com
Cisco QVPN v1.4.1.2 does not work under Wine. QVPN is used to establish an
IPSec Virtual Private Network tunnel from a client computer to a Cisco
Router/Gateway to facilitate secure communication over the internet.
There appear to be 3 errors when running the Cisco QVPN application under Wine:
(a) an apparent crash / closure of DetectEnvStatus.exe
(b) a failure to resolve a DDNS domain name, and
(c) QVPN is not able to ping the gateway router, and all data transfer over the
VPN fails.
In all cases a popup box appears (see attached screenshot) indicating that
DectectEnvStatus.exe has a serious problem and has closed.
If anyone wants to debug this, I can supply a copy of QVPN, and I can set up a
temporary guest account on my WRVS4400N small business router for testing
purposes. QVPN works fine under Windows Vista SP2, and works fine on a Ununtu
10.04LTS host with a Vista guest running under Oracle VirtualBox. So the QVPN
application itself is OK, and the problem is related somehow to Wine or various
underlying services.
On the attached screenshot the DetectEnvStatus popup appears immediately when I
attempt to connect the VPN. If I use the IP address of the gateway router I am
connecting to in lieu of the DDNS domain name, QVPN will create the VPN, but
the tunnel verification ping test fails and the tunnel will not transmit data,
which is why the "remote gateway not responding" message also appears on the
screenshot. If I specify the DDNS domain name of the remote gateway router,
the VPN tunnel is not established (not shown), suggesting a dynamic DNS
name-to-IP address resolution related problem in Wine.
Any help would be appreciated.
--
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=39881
Bug ID: 39881
Summary: d3dx9_36/tests/mesh.ok: failed on line 4145 Test text
Product: Wine
Version: 1.9.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: litimetal(a)gmail.com
Distribution: ---
Created attachment 53245
--> https://bugs.winehq.org/attachment.cgi?id=53245
terminal_output.txt
run $ make mesh.ok, got
mesh.c:4145: Test failed: Test text ('wine', 1.000000, 0.000000), glyph 4, face
280 normal, result (0, -0, -1), expected (0, 0, 1)
Is this related to bug 28810?
--
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=39712
Bug ID: 39712
Summary: AirDC++: Crash after finishing setup wizard
Product: Wine
Version: 1.8-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: archee(a)tuta.io
Distribution: ---
Created attachment 52965
--> https://bugs.winehq.org/attachment.cgi?id=52965
wine terminal output
In the setup wizard, when it says "The wizard has completed successfully", then
press Cancel (Next doesn't work), now it will show splash screen and then a
dialog "AirDC++ just encountered a fatal bug and should have written
exceptioninfo.txt the same directory as the executable"
Download:
https://github.com/airdcpp/airgit/releases/download/3.00/AirDC_Installer_3.…
$ sha1sum AirDC_Installer_3.00.exe
bdaef50c9388135b9e326ea03118a1254f2ecd82 AirDC_Installer_3.00.exe
--
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=43203
Bug ID: 43203
Summary: Crashing Devil Mac Cry 5
Product: Wine-staging
Version: 2.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tall89(a)mail.ru
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
WINEDEBUG=fixme-all,err+loaddll,err+dll,err+file,err+reg
------ Program jamp.exe ------
err:seh:setup_exception_record stack overflow 1312 bytes in thread 014b eip
7bc68356 esp 01330e10 stack 0x1330000-0x1331000-0x1b30000
--
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=23950
Summary: MPQEdit: Opening a folder results in the wrong error
message
Product: Wine
Version: 1.3.0
Platform: x86
URL: http://zezula.net/download/mpqediten32_beta.zip
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: adys.wh(a)gmail.com
Attachment #30066 showcases the expected error message ("The system cannot find
the path specified"). Instead, running wine mpqedit c:\\ results in "Access
denied" error message.
--
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=42436
Bug ID: 42436
Summary: Wine Wiki: Building Wine - Memory & Address Checkers
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wylda(a)volny.cz
Distribution: ---
I don't know, if anyone tried recently follow wiki link:
https://wiki.winehq.org/Building_Wine#Memory_.26_Address_Checkers
This link mentions "...you only need to pass the -fsanitize=address flag to the
compiler when building"
../wine-source/configure CFLAGS="-g -O1 -fsanitize=address -other-flags"
But this fails soon in make_xftmpl.o: In function fatal_error':
..../tools/make_xftmpl.c:116: undefined reference to
`__asan_option_detect_stack_use_after_return'
..../tools/make_xftmpl.c:116: undefined reference to `__asan_stack_malloc_1'
Passing LIBS="-lasan" to configure fixes this, but build fails anyway at cca
63%:
..../dlls/ntdll/loader.c:2979: undefined reference to `pthread_sigmask'
Per some gentoo wiki:
Some configure scripts test the need of the -lpthread compiler flag by testing
whether the function pthread_create() is available without it. The Address
Sanitizer library (libasan) provides this function. However it does not have a
full pthread implementation, more advanced pthread functions aren't provided.
Therefore the compilation fails. A workaround is to add the -lpthread compiler
flag manually.
Passing LIBS="-lasan -lpthread" to configure fixes this issue, but anyway fails
at the end:
../tools/sfnt2fon/sfnt2fon -o coue1255.fon ../../wine_git_src/fonts/courier.ttf
-d 128 13,1255,8
Makefile:174: recipe for target 'coue1255.fon' failed
==16755==ASan runtime does not come first in initial library list; you should
either link runtime to your application or manually preload it with LD_PRELOAD.
make[1]: *** [coue1255.fon] Error 1
make: *** [fonts] Error 2
Did anyone tried to follow that Wiki? I tried that on Debian Stretch.
Gcc (Debian 6.3.0-6) 6.3.0 20170205
--
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=39380
Bug ID: 39380
Summary: test.winehq.org: Provide a way to know why a report
was rejected
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
When WineTest submits a report that report can get thrown away. Either because
it's too big, because it has too many failures, because too many tests were
skipped or because of other reasons unknown.
The WineTest.exe is never notified of this because the report analysis is run
asynchronously with respect tot he submission process. But annoyingly there is
no way for the submitter to know why the report was rejected even later,
levaing him to guess as to what needs fixing.
One way to plug this hole would be to send an email with the reason to the
address field in the report. But that could probably be abused to send emails
to arbitrary persons.
A very simple alternative would be to create a per-commit text file containing
one line per ignored report with the report's tag, timestamp of when it was
analyzed and the reason why it was ignored.
--
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.