http://bugs.winehq.org/show_bug.cgi?id=2116
------- Additional Comments From jonathan(a)ernstfamily.ch 2005-20-10 06:27 -------
Is this bug still here in current Wine or Wine-CVS ? I couldn't find any place
where to download this application.
Thanks for reporting back.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3592
jonathan(a)ernstfamily.ch changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From jonathan(a)ernstfamily.ch 2005-20-10 06:23 -------
This is fixed in current CVS
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3625
jonathan(a)ernstfamily.ch changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |1434
nThis| |
AssignedTo|wine-bugs(a)winehq.org |oliver_stieber(a)yahoo.co.uk
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3570
------- Additional Comments From jonathan(a)ernstfamily.ch 2005-20-10 05:15 -------
Can you try the demo and tell us if you have the same problem with it please ?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3623
------- Additional Comments From gertrudethetramp(a)gmail.com 2005-20-10 04:33 -------
Created an attachment (id=1211)
--> (http://bugs.winehq.org/attachment.cgi?id=1211&action=view)
WINEDEBUG=+relay,+snoop,+seh output, cut to 100 lines around 'seh:'
I had to gzip this as, uncompressed, the file is 17MB in size. I hope this
helps.
For the output without any WINEDEBUG statement, I get numerous errors about
x11drv (which are in bug 3622), an error about a DLL that seems unrelated, and
the message in the first comment.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2561
------- Additional Comments From michael(a)heiming.de 2005-20-10 03:24 -------
IIRC tried this out, but alas there are filename collision, Linux is case
sensitive and it didn't worked out. You were using doze!
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3626
Summary: range checking in numeric edit box behaves badly
Product: Wine
Version: 20050830
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-gui
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rainer.zi(a)web.de
I found the bug with Macromedia Fireworks 2.0.2 (very old version!)
It might be reproducible in any numeric edit box with range checking and a lower
limit higher than 1.
Steps to reproduce bug:
- Open Fireworks
- create a new image
- click on the Text tool, then click anwhere on the image. The text dialog opens.
- enter some text and highlight it (important!)
- double click into the text size box (which should show something like "12") to
highlight the number
- enter "1"
- The Problem: The text size box now shows "4", its minimum value, rather than "1".
This way you cannot simply enter a number like "14". Workaround possible, e.g.
highlight the "2", enter "4".
IMHO the expected behaviour would be to allow the "1" and apply the range
checking in another place, ie. when the user leaves the box or closes the dialog.
In Fireworks, the problem does NOT occur when the text below in the dialog is
not highlited!
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3625
Summary: Railroad tycoon 3 stops with "ERROR deallocating DX
stuff!!" (Vertex refcounting)
Product: Wine
Version: CVS
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: pebl(a)math.ku.dk
I can play the tutorials without problem, but when starting a champaign, a
dialog box pops up and says the error in subject. This is an i18n RT3 message
(and can be googled). RT3 then stops.
Right before showing the messagebox there is ~40
trace:d3d:IDirect3DIndexBuffer8Impl_Release (xxxxxxxx) : ReleaseRef to 0
and
trace:d3d:IDirect3DIndexBuffer8Impl_Release (0x7a72c0d0) : ReleaseRef to 0
trace:d3d:IDirect3DVertexBuffer8Impl_Release (0x7fe97118) : ReleaseRef to 0
trace:d3d:IDirect3DVertexBuffer8Impl_Release (0x7fe97150) : ReleaseRef to 0
trace:d3d:IDirect3DVertexBuffer8Impl_Release (0x7af93028) : ReleaseRef to 0
trace:d3d:IDirect3DVertexBuffer8Impl_Release (0x7fe970e0) : ReleaseRef to 0
trace:d3d:IDirect3DVertexBuffer8Impl_Release (0x7a50cf68) : ReleaseRef to 0
trace:d3d:IDirect3DIndexBuffer8Impl_Release (0x7fe971d8) : ReleaseRef to 0
trace:d3d:IDirect3DIndexBuffer8Impl_Release (0x7b70d590) : ReleaseRef to 0
trace:d3d:IDirect3DVertexBuffer8Impl_Release (0x7fe971a0) : ReleaseRef to 1
trace:dialog:GetDialogBaseUnits base units = 9,16
If I place a breakpoint in the last vertex Release, and return 0 instead of 1,
RT3 continues correctly. If I change the implementation to allways return 0, rt3
also continues. So it seems RT3 checks the return release values.
Grepping for the 0x7fe971a0 pointer shows the list below (and a lot of
IDirect3DVertexBuffer8Impl_Unlock and Lock I have left out). I have no idea
where/how to fixing this.
trace:d3d:IDirect3DDevice8Impl_CreateImageSurface (0x7fe0b2c0) : w(256) h(256)
fmt(21,D3DFMT_A8R8G8B8) surf@0x7fe971a0, surfmem@0x7a630458, 262144 bytes
trace:d3d:IDirect3DDevice8Impl_CreateTexture Created surface level 0 @
0x7fe971a0, memory at 0x7a630458
trace:d3d_surface:IDirect3DSurface8Impl_AddRef (0x7fe971a0) : AddRef from 1
trace:d3d:IDirect3DTexture8Impl_GetSurfaceLevel (0x7a630028) : returning
0x7fe971a0 for level 0
trace:d3d_surface:IDirect3DSurface8Impl_Release (0x7fe971a0) : ReleaseRef to 1
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 5
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 5
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 5
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 5
trace:d3d:IDirect3DTexture8Impl_Release (0x7a630028) : Releasing surface 0x7fe971a0
trace:d3d_surface:IDirect3DSurface8Impl_Release (0x7fe971a0) : ReleaseRef to 0
trace:d3d:IDirect3DDevice8Impl_CreateImageSurface (0x7fe0b2c0) : w(256) h(256)
fmt(21,D3DFMT_A8R8G8B8) surf@0x7fe971a0, surfmem@0x7a630028, 262144 bytes
trace:d3d:IDirect3DDevice8Impl_CreateTexture Created surface level 0 @
0x7fe971a0, memory at 0x7a630028
trace:d3d_surface:IDirect3DSurface8Impl_AddRef (0x7fe971a0) : AddRef from 1
trace:d3d:IDirect3DTexture8Impl_GetSurfaceLevel (0x7fe97240) : returning
0x7fe971a0 for level 0
trace:d3d_surface:IDirect3DSurface8Impl_Release (0x7fe971a0) : ReleaseRef to 1
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 6
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 6
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 6
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 6
trace:d3d:IDirect3DTexture8Impl_Release (0x7fe97240) : Releasing surface 0x7fe971a0
trace:d3d_surface:IDirect3DSurface8Impl_Release (0x7fe971a0) : ReleaseRef to 0
trace:d3d:IDirect3DDevice8Impl_CreateImageSurface (0x7fe0b2c0) : w(256) h(256)
fmt(21,D3DFMT_A8R8G8B8) surf@0x7fe971a0, surfmem@0x7a630028, 262144 bytes
trace:d3d:IDirect3DDevice8Impl_CreateTexture Created surface level 0 @
0x7fe971a0, memory at 0x7a630028
trace:d3d_surface:IDirect3DSurface8Impl_AddRef (0x7fe971a0) : AddRef from 1
trace:d3d:IDirect3DTexture8Impl_GetSurfaceLevel (0x7b703028) : returning
0x7fe971a0 for level 0
trace:d3d_surface:IDirect3DSurface8Impl_Release (0x7fe971a0) : ReleaseRef to 1
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 7
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 7
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 7
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 7
trace:d3d:IDirect3DTexture8Impl_Release (0x7b703028) : Releasing surface 0x7fe971a0
trace:d3d_surface:IDirect3DSurface8Impl_Release (0x7fe971a0) : ReleaseRef to 0
trace:d3d:IDirect3DDevice8Impl_CreateImageSurface (0x7fe0b2c0) : w(256) h(256)
fmt(21,D3DFMT_A8R8G8B8) surf@0x7fe971a0, surfmem@0x7a630028, 262144 bytes
trace:d3d:IDirect3DDevice8Impl_CreateTexture Created surface level 0 @
0x7fe971a0, memory at 0x7a630028
trace:d3d_surface:IDirect3DSurface8Impl_AddRef (0x7fe971a0) : AddRef from 1
trace:d3d:IDirect3DTexture8Impl_GetSurfaceLevel (0x7fe97240) : returning
0x7fe971a0 for level 0
trace:d3d_surface:IDirect3DSurface8Impl_Release (0x7fe971a0) : ReleaseRef to 1
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 8
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 8
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 8
trace:d3d:IDirect3DTexture8Impl_PreLoad Texture 0x7fe971a0 (level 0) given name 8
trace:d3d:IDirect3DTexture8Impl_Release (0x7fe97240) : Releasing surface 0x7fe971a0
trace:d3d_surface:IDirect3DSurface8Impl_Release (0x7fe971a0) : ReleaseRef to 0
trace:d3d:IDirect3DDevice8Impl_CreateVertexBuffer (0x7fe0b2c0) : Size=1560000,
Usage=520, FVF=142, Pool=0 - Memory@0x7a390020, Iface@0x7fe971a0
trace:d3d:IDirect3DDevice8Impl_SetStreamSource (0x7fe0b2c0) : StreamNo: 0,
OldStream ((nil)), NewStream (0x7fe971a0), NewStride 24
trace:d3d:IDirect3DVertexBuffer8Impl_AddRef (0x7fe971a0) : AddRef from 1
trace:d3d:IDirect3DVertexBuffer8Impl_Release (0x7fe971a0) : ReleaseRef to 1
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3623
------- Additional Comments From saulius.krasuckas(a)elst.vtu.lt 2005-20-10 02:01 -------
IMHO "actual crash output" is output you get with WINEDEBUG unset. And to get
XX lines _B_efore seh lines (plus YY lines _A_fter it), while seeing all the
output, you may find usefull these commands:
$ wine ... 2>&1 | tee output.log # directs output both to file and terminal
$ grep -BXX -AYY ':seh:' output.log # matches seh lines
If you would like to _m_atch only the first time, add grep option "-m1". HTH.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.