http://bugs.winehq.org/show_bug.cgi?id=25985
Summary: AmiBroker crashes when using colour palette
Product: Wine
Version: 1.0.1
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: softcont(a)optusnet.com.au
Created an attachment (id=33123)
--> (http://bugs.winehq.org/attachment.cgi?id=33123)
Output from "C:>" prompt and from AmiBroker itself for wine 1.0.1 & 1.3.12
under Debian AMD64 "squeeze"
There is more than one way to make it crash. The easiest is:
1. Download AmiBroker (v5.30 right now) from:
http://amibroker.com/download.html (for v 5.30 it is:
http://www.amibroker.com/bin/AmiBroker530.exe) to ".wine/drive_c". Copy 2
dll's: mfc42.dll & msvcp60.dll to ".wine/drive_c/windows/system32". Run "wine
cmd"
2. From the "C:>" prompt install AmiBroker in the default location (C:\Program
Files\AmiBroker) by executing AmiBroker530.exe
3. Change directory to C:\Program Files\AmiBroker
4. Run AmiBroker (type broker and press <enter> at the prompt) - it should show
a chart for "^DJI(Daily)"
5. Click with the right mouse button on the chart pane (there are 3 chart panes
- I clicked on the top one) and from the popup context menu that appears select
item "Parameters"
6. A "Properties of Price" dialog box appears (the title may vary depending on
which panel the right mouse click occurs)
7. Click on any "Color" item (i.e. with the label "Color")
8. A simple color palette popup window appears
9. Click on the "More" button of the simple color palette - a more detailed
color dialog box appears
10. Click on the "Cancel" button of the detailed color dialog box
The program crashes (the whole application needs eventually be killed from
Linux)
Another way to crash it is (after step 7 - i.e. without pressing its "More"
button) click on the (parent) "Properties of Price" dialog box - the simple
color palette does not close (it does under native Windows). Then one by one
close all the AmiBroker windows (notice that the simple color palette stays
open). This should eventually crash the application (pressing <Esc> button also
does the trick).
I also tested it under 1.3.12 environment (files attached) with the same
result. However, I felt a bit lost when compiling and installing the wine
environment. I have two systems: Debian amd64 (squeeze) and Debian 32-bit
(lenny). The crash occurs on both of them.
--
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=29008
Bug #: 29008
Summary: Age of Wonders fails to run because of a floating
point error
Product: Wine
Version: 1.3.32
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: stefan(a)codeweavers.com
Classification: Unclassified
Age of Wonders does not start because of a floating point exception during
wined3d initialization. This is a regression caused by this patch:
7b0ba5153f3e42f31b922e5eb997d5e1d0cb44d4 is the first bad commit
commit 7b0ba5153f3e42f31b922e5eb997d5e1d0cb44d4
Author: Matteo Bruni <mbruni(a)codeweavers.com>
Date: Thu Nov 3 15:26:36 2011 +0100
wined3d: Test more thoroughly for post-pixelshader blending support, try on
more texture formats.
This problem happens is quite complicated: Before initializing DirectDraw, the
game changes the FPU control word and removes the FPCW$INVALID flag(0x0001),
among others. During wined3d initialization wined3d tests if WINED3DFMT_UYVY is
FBO attachable, which is true because we emulate it with GL_LUMINANCE_ALPHA.
After that the new code added by the patch tries to draw to it, which
apparently generates a NaN somewhere, and since the game disallowed them an
exception is raised. The full FPU control word that is set when
DirectDrawCreate is called is 0x1372.
The game pops up an error dialog and tries to initialize DirectDraw again, and
is stuck in a loop from this point on. It isn't even necessary to install the
game to reproduce this issue, the aowsetup.exe program on the CD has the same
crash.
The problem is not related to WINED3DFMT_UYVY per se, the other luminance-alpha
formats like WINED3DFMT_YUY2, WINED3DFMT_L8A8 and WINED3DFMT_L4A4 affected as
well.
My GPU driver is the Nvidia binary driver, version 290.06, on a GeForce 9600M
GPU. A while ago this driver didn't support luminance-alpha fbo attachments,
apparently this changed somewhen.
--
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=33473
Bug #: 33473
Summary: Key DACL prevents creation of registry keys.
Product: Wine
Version: 1.5.29
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: wineserver
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: julliard(a)winehq.org
CC: ehoover(a)mines.edu
Classification: Unclassified
Regression SHA1: 04cd764d7688c59f88c19b25d5c6baea75a15ba1
The key DACL introduced by commit 04cd764d7688c59f88c19b25d5c6baea75a15ba1
breaks creation of registry keys in installers. Tested with the Xtreme 5
Graphic Designer installer from bug 14713:
http://store.downloadcrew.com/p28537-magix_xtreme_photo__graphic_designer_5.
err:msi:ITERATE_WriteRegistryValues Could not create key
L"Software\\MAGIX\\Foto_Manager_10\\MsiKeyPath"
err:msi:ITERATE_Actions Execution halted, action L"WriteRegistryValues"
returned 1627
Creation of the MAGIX subkey fails with access denied because of the DACL.
--
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=5535
Jay <jaynobyl(a)gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|jaynobyl(a)gmx.de |
--
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=8490
Daniel Jelinski <djelinski1(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djelinski1(a)gmail.com
--- Comment #21 from Daniel Jelinski <djelinski1(a)gmail.com> 2013-08-31 14:17:20 CDT ---
The original issue (cropped title) was fixed before 1.2, as per comment 19.
Some issues from that comment are still present in 1.7.1:
- the window should have some size constraints - currently it is possible to
shrink it until all elements are hidden
- when resizing the window, the label area is not properly invalidated before
redrawing
Also the dialog abuses some comctl32 APIs - with native comctl32 from
winetricks there is another bug: when creating a folder in a folder which
initially had no subfolders, the new folder is not displayed.
--
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=2082
--- Comment #123 from Saulius K. <saulius2(a)gmail.com> 2013-08-30 23:22:47 CDT ---
(In reply to comment #122)
>
> Fantastic!
>
> I managed to find an apparently patched ddraw.dll from a years old tarball
Please stop. Workarounds has nothing to do with fixing bugs. So these talks
belongs to AppDB. Thank you:)
--
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=2082
--- Comment #122 from kerryhall(a)gmail.com 2013-08-30 16:39:36 CDT ---
(In reply to comment #119)
> Someone correct me if I'm wrong, but I believe the bug has been known for a
> *long* time, but nobody has thought of a way to fix it that won't break other
> apps. And for some weird reason wine still doesn't want to do something
> Microsoft themselves do, that is have specific fixes for particular apps -
> which would make this easy.
>
> A friend of mine, however, has created a ddraw.dll replacement that seems to
> work for the games I own that are affected by the problem (admittedly it was
> created entirely for these games). As far as I remember, it works by wrapping
> certain calls, so it's not something that will become outdated. I'll talk to
> him again about releasing it.
Fantastic!
I managed to find an apparently patched ddraw.dll from a years old tarball that
was sitting on my system the last time I encountered this issue, but after
putting it into ~/.wine/drive_c/windows/system32 I still had the same issue. If
I could get a tarball from you with a tested ddraw.dll, (plus correct
instructions, not sure if I'm just supposed to put it into system32) that would
be awesome.
Cheers!
--
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=22136
Summary: Starcraft II - poor fps in windowed mode
Product: Wine
Version: 1.1.41
Platform: x86-64
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
In wine, roughly 6-8 fps, and terminal is filled with:
err:d3d:state_colorwrite (WINED3DRS_COLORWRITEENABLE1/2/3,0,0,0) not yet
implemented. Missing of cap D3DPMISCCAPS_INDEPENDENTWRITEMASKS wasn't honored?
err:d3d:state_colorwrite (WINED3DRS_COLORWRITEENABLE1/2/3,0,0,0) not yet
implemented. Missing of cap D3DPMISCCAPS_INDEPENDENTWRITEMASKS wasn't honored?
err:d3d:state_colorwrite (WINED3DRS_COLORWRITEENABLE1/2/3,0,0,0) not yet
implemented. Missing of cap D3DPMISCCAPS_INDEPENDENTWRITEMASKS wasn't honored?
err:d3d:state_colorwrite (WINED3DRS_COLORWRITEENABLE1/2/3,0,0,0) not yet
implemented. Missing of cap D3DPMISCCAPS_INDEPENDENTWRITEMASKS wasn't honored?
err:d3d:state_colorwrite (WINED3DRS_COLORWRITEENABLE1/2/3,0,0,0) not yet
implemented. Missing of cap D3DPMISCCAPS_INDEPENDENTWRITEMASKS wasn't honored?
in windows, I consistently get 50, even with a lot of characters on screen.
--
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=26077
Summary: setupapi/misc tests show a memory leak in
winemenubuilder?
Product: Wine
Version: 1.3.13
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: minor
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
24 bytes in 3 blocks are definitely lost
at notify_alloc (heap.c:254)
by RtlAllocateHeap (heap.c:1701)
by CreatePropertyBag2 (propertybag.c:143)
by PngEncoder_CreateNewFrame (pngformat.c:1376)
by convert_to_native_icon (winemenubuilder.c:423)
by platform_write_icon (winemenubuilder.c:1068)
by extract_icon (winemenubuilder.c:1100)
by InvokeShellLinker (winemenubuilder.c:2590)
by Process_Link (winemenubuilder.c:2965)
by wWinMain (winemenubuilder.c:3418)
by wmain (exe_wmain.c:50)
by __wine_spec_exe_wentry (exe_wentry.c:36)
by ??? (process.c:1034)
by start_process (process.c:1086)
by ??? (signal_i386.c:2473)
by call_thread_entry_point (signal_i386.c:2499)
by start_process (loader.c:2606)
by ??? (port.c:60)
--
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.