http://bugs.winehq.org/show_bug.cgi?id=15829
Summary: 1000net installer crashes after selecting install button
Product: Wine
Version: 1.1.7
Platform: PC
URL: http://the1000.mail333.com/1000net.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: arethusa26(a)gmail.com
Created an attachment (id=16958)
--> (http://bugs.winehq.org/attachment.cgi?id=16958)
1000net.exe relay and win traces
With today's Git (wine-1.1.7-75-ga900f5e), after selecting the English button
in the language selection screen, then selecting install, the installer
crashes. An excerpt of the backtrace:
err:dialog:EndDialog got invalid window handle ((nil)); buggy app !?
err:dialog:EndDialog got invalid window handle (0x10028); buggy app !?
wine: Unhandled page fault on read access to 0x00000085 at address 0x7eb76faa
(thread 0009), starting debugger...
...
Backtrace:
=>1 0x7eb76faa WIN_CreateWindowEx+0x195a(cs=0x32fe3c, className=0x32fc3c,
flags=32) [/home/andrew/wine-git/dlls/user32/win.c:1235] in user32 (0x0032fc10)
2 0x7eb77ccd CreateWindowExA+0xbd(exStyle=0, className="RARiSFXWindow",
windowName="", style=13565952, x=0, y=0, width=0, height=0, parent=(nil),
menu=(nil), instance=0x400000, data=(nil))
[/home/andrew/wine-git/dlls/user32/win.c:1388] in user32 (0x0032fe70)
...
Relay traces are attached.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=15807
Summary: Unhandled exception 0xc000000d when editing HTML
Product: Wine
Version: 1.1.7
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nikolaj(a)sheller.dk
To reproduce:
The program can be downloaded here (in this case V3.0 (Build 1024)):
http://www.testlog.com/download.htm
Run on: Wine 1.1.7 on ubuntu 8.04 64bit.
1) Install and run TestLog
2) Click continue to accept 90 day evaluation
3) Load sample database
4) In tree structure choose "Test Cases->BASE->BASE_001"
5) Double click BASE_001
6) Click on one of the ellipses (...)
7) Window closes and problem has been reproduced
fixme:shdocvw:ClOleCommandTarget_Exec (0x13510c)->((null) 21 2 (nil) (nil))
fixme:mshtml:HTMLDocument_get_designMode (0x1408828)->(0x33f138)
wine: Unhandled exception 0xc000000d at address 0x7bca0023:0x00454add (thread
0024), starting debugger...
Process of pid=0023 has terminated
Installing internet explorer 7 did not solve the problem.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=15786
Summary: FEAR 1.08: GL errors in D3D8 mode
Product: Wine
Version: 1.1.7
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquid.acid(a)gmx.net
CC: hverbeet(a)gmail.com
Hardware: NV35
Driver: nvidia-drivers-173.14.12-r1
The game is set up to use DX8 shaders.
The issue: Lots of GL errors on the console:.
fixme:d3d_shader:shader_glsl_select >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION
(0x502) from glUseProgramObjectARB @ glsl_shader.c / 3501
I can confirm that INVALID_OPERATION is really produced by
glUseProgramObjectARB and not by some GL call before it.
The reason why the call fails is this error that appears earlier:
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #184:
"(21) : error C7011: implicit cast from \"vec4\" to \"vec3\"\n"
I extracted the GLSL shader source of the faulty program:
#version 120
#extension GL_ARB_texture_rectangle : enable
uniform vec4 PC[8];
uniform sampler2D Psampler0;
uniform sampler2D Psampler1;
uniform sampler2D Psampler2;
uniform samplerCube Psampler3;
vec4 T0 = gl_TexCoord[0];
vec4 T1 = gl_TexCoord[1];
vec4 T2 = gl_TexCoord[2];
vec4 T3 = gl_TexCoord[3];
vec4 R0;
vec4 R1;
vec4 tmp0;
vec4 tmp1;
uniform vec4 PLC1;
void main() {
T0.xyzw = (texture2D(Psampler0, T0.xy).xyzw);
T1.xyzw = (texture2D(Psampler1, T1.xy).xyzw);
T2.xyzw = (texture2DProj(Psampler2, T2.xyw).xyzw);
T3.xyzw = (textureCube(Psampler3, T3.xyzw).xyzw);
R0.xyzw = (vec4(dot((2.0 * (T1.xyz - 0.5)), (2.0 * (T3.xyz - 0.5)))));
R0.xyzw = clamp(R0.xyzw, 0.0, 1.0);
R0.w = (R0.w * R0.w);
R0.w = (R0.w * R0.w);
R1.xyz = (T2.www * PC[0].xyz);
R0.w = (R0.w * R0.w);
R1.xyz = (T0.xyz * R1.xyz);
R0.xyz = (R0.www * R1.xyz);
R0.w = (PLC1.w);
gl_FragColor = R0;
float Fog = clamp(gl_FogFragCoord * gl_Fog.start + gl_Fog.end, 0.0, 1.0);
gl_FragColor.xyz = mix(gl_Fog.color.xyz, gl_FragColor.xyz, Fog);
}
----------------------------------------------------------------------------
Like the GLSL compiler already reports, the issue is in line 21:
T3.xyzw = (textureCube(Psampler3, T3.xyzw).xyzw);
textureCube expects a vec3 type as second parameter.
The problem seems to originate from pshader_glsl_tex (in glsl_shader.c) where
the GLSL source is constructed.
Checking the content of mask before
mask |= sample_function.coord_mask;
reveals that the shader compilation only fails when mask is non-zero (at least
in my case). So if it fails it always has a hex value of 80000.
shader_glsl_get_sample_function works correctly.
The WINED3DSP_WRITEMASK_3 mask is set in the "hex_version <
WINED3DPS_VERSION(1,4)" if-branch, through the WINED3DTTFF_DISABLE case.
With the help of Roderick I found the original D3D asm:
ps_1_1
//CTAB
def c1 = 0.000000, 0.000000, 0.000000, 1.000000
tex t0
tex t1
tex t2
tex t3
dp3_sat r0, t1_bx2, t3_bx2
mul r0.a, r0.a, r0.a
mul r0.a, r0.a, r0.a
+mul r1.rgb, t2.a, c0
mul r0.a, r0.a, r0.a
+mul r1.rgb, t0, r1
mul r0.rgb, r0.a, r1
+mov r0.a, c1.a
----------------------------------------------------------------------------
He suspects that the issue originates from dp3_sat.
Adding a "if (sampler_type == WINED3DSTT_CUBE) maks=0;" before "mask |=
sample_function.coord_mask;" fixes the compilation error and also the GL errors
for me.
Adding Henri Verbeet to CC since he designed this part of the code (according
to Stefan Dösinger).
Greets,
Tobias
--
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.
http://bugs.winehq.org/show_bug.cgi?id=15757
Summary: Address bar is not updated when navigating through
directories in 7-zip 4.60 beta
Product: Wine
Version: 1.1.7
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: arethusa26(a)gmail.com
With 1.1.7, when navigating through directories in the 7-zip 4.60 beta, the
corresponding address bar does not get updated, as it should be on Windows. No
relevant terminal output was noted.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=15756
Summary: Inline file rename text box does not disappear
appropriately
Product: Wine
Version: 1.1.7
Platform: PC
URL: http://downloads.sourceforge.net/sevenzip/7z460.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: arethusa26(a)gmail.com
With 1.1.7, when I click on a file list icon's text area, a rename dialog box
appears. When I click on an area outside the box, however, it does not
disappear as it would on Windows. This is most evident when clicking the Up
directory button, for which the rename text box does not disappear in this
case. No terminal output was noted.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=15725
Summary: calendar sizing incorrect in Paf5
Product: Wine
Version: 1.1.6
Platform: PC
URL: http://ftp.ldscatalog.com/PAF5AllLangs.exe
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cjstimpson(a)utwire.net
The calendar doesn't fit well in the date calculator dialog in Paf 5.2 (Tools
-> Date Calculator). If I increase the font size under Tools -> Preferences ->
Fonts, large portions of the calendar can get clipped off.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=15692
Summary: Apps crash with FontLink settings since Wine 1.1.6
Product: Wine
Version: 1.1.6
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: critical
Priority: P1
Component: gdi32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hzhrong(a)gmail.com
CC: dmitry(a)codeweavers.com
Created an attachment (id=16757)
--> (http://bugs.winehq.org/attachment.cgi?id=16757)
backtrace
Steps:
1. Setup the following FontLink registry:
[Software\\Microsoft\\Windows NT\\CurrentVersion\\FontLink\\SystemLink]
1208451304
"MS Sans Serif"=str(7):"simsun.ttc,SimSun\0gulim.ttc,Gulim\0msgothic.ttc,MS UI
Gothic\0mingliu.ttc,PMingLiU\0"
"Tahoma"=str(7):"simsun.ttc,SimSun\0gulim.ttc,Gulim\0msgothic.ttc,MS UI
Gothic\0mingliu.ttc,PMingLiU\0"
Ensure you have these fonts: simsun.ttc, gulim.ttc, etc. or change the values
with proper font name. This gets the CJK fonts display properly.
2. Run winecfg, change Menu Text font to Tahoma 8:
3. Run notepad on zh_CN.UTF-8:
$ LANG=zh_CN.UTF-8 ./wine programs/notepad/notepad.exe.so
wine: Unhandled page fault on read access to 0x0016885c at address 0x7e493aca
(thread 0009), starting debugger...
WineDbg starting on pid 0008
Unhandled exception: page fault on read access to 0x0016885c in 32-bit code
(0x7e493aca).
See attached bt.txt.
A regression testing shows the following commit:
$ git bisect bad
f898547b77a091132aefa1967887f5e640819bd4 is first bad commit
commit f898547b77a091132aefa1967887f5e640819bd4
Author: Dmitry Timoshkov <dmitry(a)codeweavers.com>
Date: Thu Oct 9 10:23:46 2008 +0900
gdi32: Remove the code which bypasses the DC transformation checks.
If it's absolutely required to check the child list first, that should be
done inside of find_in_cache using the same comparisons as done there.
:040000 040000 f6d197d72781f0a4a0779de50f53830c51a2fece
e5d6801025e9abc050184265743782b9ffc1522b M dlls
--
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.
http://bugs.winehq.org/show_bug.cgi?id=15691
Summary: Page fault while editing RichText
Product: Wine
Version: 1.0.1
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: richedit
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nikolaj(a)sheller.dk
Created an attachment (id=16756)
--> (http://bugs.winehq.org/attachment.cgi?id=16756)
back trace of crash
Working with a program called "TestLog" i often get the following crash while
editing RichText:
Unhandled exception: page fault on write access to 0x00000020 in 32-bit code
(0x7dec88e0)
Backtrace:
=>1 0x7dec88e0 ME_MarkForPainting+0x10() in riched20 (0x003293a4)
This is seen on Ubuntu 8.10 64bit with wine 1.0.1-0ubuntu1.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=14983
Summary: CM2000 Graphics slowed down !
Product: Wine
Version: 1.1.3
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: brodo(a)o2.pl
Serious graphical performance degradation in Wine 1.1.3 while using schematic
section of the Circuitmaker2000 (cirmaker.exe).
Refreshing screen takes 2-5 seconds compared to appr. 0.5s as always.
The Pcb section of Circuitmaker2000 seems unaffected.
Tested on 2 different laptops with different graphic controllers with the same
(slowing down) result.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=14774
Summary: Max Payne 2: PP effects flood console with GL errors
(ORM=fbo)
Product: Wine
Version: 1.1.1
Platform: PC-x86-64
URL: http://www.rockstargames.com/maxpayne2/mp2_downloads.htm
l
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquid.acid(a)gmx.net
CC: hverbeet(a)gmail.com
Hi there,
this is a regression introduced between wine-1.1.0 and wine-1.1.1, bisecting
turns up these commits:
[2d4d18b59dc26b8aee04553671b942071d9213b9] wined3d: Delay render target
activation.
[4f77c29bcf58a88cea8fb833f770aa107960b34e] wined3d: Track depth stencil
location per-surface.
Actually I had to do two bisects, one separate for the glReadBuffer error, and
one for the two other messages.
Affected game: Max Payne 2 (demo)
Wine settings:
OffscreenRenderingMode=fbo
UseGLSL=disabled
Ingame settings:
PostProcessingEffects=medium
PixelShaderSkins=off
Hardware: nVidia Geforce FX 5900
Drivers: nvidia-drivers-173.14.09
GL errors only show up when PP effects are used in the game. There are two
types:
(a) bullettime, using a sepia tone filter
(b) cutscenes, using a motion blur filter
GL errors depend on whether (a) or (b) is currently active:
For (a) I get these GL errors:
(*) fixme:d3d_surface:read_from_framebuffer_texture >>>>>>>>>>>>>>>>>
GL_INVALID_ENUM (0x500) from glReadBuffer @ surface.c / 913
(**) fixme:d3d_shader:shader_arb_deselect_depth_blt >>>>>>>>>>>>>>>>>
GL_INVALID_OPERATION (0x502) from glBindProgramARB(GL_VERTEX_PROGRAM_ARB,
vertexShader->prgId); @ arb_program_shader.c / 1832
And for (b) those:
(*) fixme:d3d_surface:read_from_framebuffer_texture >>>>>>>>>>>>>>>>>
GL_INVALID_ENUM (0x500) from glReadBuffer @ surface.c / 913
(***) fixme:d3d_shader:shader_arb_deselect_depth_blt >>>>>>>>>>>>>>>>>
GL_INVALID_OPERATION (0x502) from glDisable(GL_VERTEX_PROGRAM_ARB) @
arb_program_shader.c / 1840
Note that the errors don't show up with ORM=backbuffer.
This are essentially three errors, I marked them each with asteriks. Notice
that the (*) GL error happens in both "modes".
During bisecting I noticed that the (*) GL error was introduced a different
commit than the (**)/(***) (which are introduced by one and the same commit).
For testing both wine versions (1.1.0 and 1.1.1) the sourcecode was patched
with
http://source.winehq.org/git/wine.git/?a=commit;h=2583975ec799527cebc323891…,
to not hit the slow driver fallback. Wine did only use ARB_tex_rect for NP2
textures then.
This can also be achieved by commenting out the ARB_tex_npot extension line in
wined3d/directx.c
The GL errors still show up with wine git master (last commit:
b572170da5f35a80c6bb07ab8ebcda7a854f27f), there with an additional GL error:
fixme:d3d:apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from
glDrawBuffers() @ context.c / 1064
However this one (the "draw buffers" one) should be fixed in latest git.
The (*) GL error is introduced by the commit:
[2d4d18b59dc26b8aee04553671b942071d9213b9] wined3d: Delay render target
activation.
(Adding Stefan Dösinger to CC)
The (**) and (***) GL error is introduced by the commit:
[4f77c29bcf58a88cea8fb833f770aa107960b34e] wined3d: Track depth stencil
location per-surface.
(Adding Henri Verbeet to CC)
--
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.