https://bugs.winehq.org/show_bug.cgi?id=36241
Bug ID: 36241
Summary: valgrind shows a leak in comdlg32/tests/printdlg.c
Product: Wine
Version: 1.7.18
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: minor
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==26461== 92 bytes in 1 blocks are definitely lost in loss record 584 of 1,024
==26461== at 0x7BC4C735: notify_alloc (heap.c:255)
==26461== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716)
==26461== by 0x496B93F: test_PrintDlgExW (printdlg.c:391)
==26461== by 0x496CA1E: func_printdlg (printdlg.c:642)
==26461== by 0x496D820: run_test (test.h:584)
==26461== by 0x496DC0F: main (test.h:654)
==26461==
--
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=14666
Summary: [wined3d] volume/volumetex locking implementation
Product: Wine
Version: CVS/GIT
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquid.acid(a)gmx.net
Hi there,
this bug should be sort of a "metabug" for fixing the locking behaviour of
volume and volumetexture objects in D3D (version 8 and 9 currently, because 7
and below doesn't have/support volumes).
I already wrote some patches and testcases to fix/illustrate the problem, but
they were rejected on wine-patches. The main problem that the problem should be
adressed much lower in wined3d.
I now post all my current patches here, so other people can take a look.
Some things what are currently not implemented:
(1) locking of volume/volumetex objects always succeeds althoug it shouldn't
- specifying to large lockboxes should fail for example
- some volumes are not lockable at all
(2) creating volumes/volumetextures always succeeds, usage and pool types are
not checked
Only a few things the patches should adress.
I intend on working on this, but I need a bit more input about why and where to
fix this exactly.
Attaching patches now...
Also adding Stefan Dösinger, Henri Verbeet, Alexander Dorofeyev and Roderick
Colenbrander to CC (sry guys *g*, but I'm sure you know where my stuff should
go).
I currently have these DX SDK docs on my system:
version 9, 8, 7 and 6
(someone asked me if I got the 7 SDK)
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=23340
Summary: Winscard : test program : unimplemented function
winscard.dll.SCardIsValidContext and
winscard.dll.SCardReleaseContext
Product: Wine
Version: 1.2-rc3
Platform: x86
URL: http://www.linuxunderground.be/compteco/winscard_test.
zip
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: vincent.hardy.be(a)gmail.com
Created an attachment (id=29078)
--> (http://bugs.winehq.org/attachment.cgi?id=29078)
console output PCSCTest.exe
start wine PCSCTest.exe in Zip test program
--
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=6866
--- Comment #19 from Padrah Zoltan <zoltan.padrah(a)gmail.com> ---
I've tried to reproduce this issue on Xubuntu 14.04, in Virtualbox, with the
wine PPA added to Xubuntu. Wine version has been 1.7.31.
I couldn't reproduce the original graphical corruption anymore. I've tried
clicking around/switching desktops/moving the windows around, both in desktop
mode and also in normal application mode, but CircuitMaker 2000's window has
been correctly repainting, expect one obscure case:
When the window of CircuitMaker 2000 is partially outside in the left direction
of the virtual desktop, then dragging a different window over the virtual
desktop of wine causes graphical corruption on the left part of CircuitMaker
2000's window, at the left part. I'm attaching the screenshot and the terminal
output of wine running CircuitMaker 2000.
Interacting with CircuitMaker 2000's window removes the graphical corruption,
either on some parts of the window (clicking inside) or on the whole window
(moving the window).
Note about the attachment's description: apparently there has been a copy-paste
error, the actual command has been:
$ wine cirmaker.exe &> log.txt
--
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=6866
--- Comment #18 from Padrah Zoltan <zoltan.padrah(a)gmail.com> ---
Created attachment 50092
--> https://bugs.winehq.org/attachment.cgi?id=50092
terminal output from wine 1.7.31
Command has been:
$ wine cker.exe &> log.txt
--
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=6866
--- Comment #17 from Padrah Zoltan <zoltan.padrah(a)gmail.com> ---
Created attachment 50091
--> https://bugs.winehq.org/attachment.cgi?id=50091
Screenshot showing the graphical corruption with wine 1.7.31
The terminal window has been dragged over CircuitMaker 2000's window (in wine's
virtual desktop), first vertially over the left part, and then to the right.
note that only a limited part of the window is filled with garbage, and not
all.
--
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=36943
Bug ID: 36943
Summary: Unhandled exception: page fault on write access to
0x00000014 in 32-bit code (0xb75a101e)
Product: Wine
Version: 0.9.59.
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: james_200122(a)yahoo.com
this error causes a register dump and this in return closes the program or
freezes up the computer
--
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=22910
Summary: Age of Empires III 1.1.3: Unhandled exception: page
fault on write access....
Product: Wine
Version: 1.2-rc1
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gaming4jc2(a)yahoo.com
Created an attachment (id=28342)
--> (http://bugs.winehq.org/attachment.cgi?id=28342)
Unhandled page fault on write access to 0x000078b8 at address 0x1c78c2 (thread
0009), starting debugger...
Attached is the log. This affects all versions best I can tell, NoCD and
official CD included. This version was patched to latest 1.1.3 and a NoCD exe
applied.
FYI: I followed instructions from the WineAppDB and dumped 3 discs properly
into one folder and execute, install was perfect. If it matters this is also
from the "Complete Collection". :)
--
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=9043
Bruno Jesus <00cpxxx(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #20 from Bruno Jesus <00cpxxx(a)gmail.com> ---
(In reply to Bruno Jesus from comment #19)
> (In reply to zippy from comment #18)
> > InDesign CS starts cleanly in wine 1.7.31, no workaround needed :)
>
> Resolving fixed, thanks for testing.
--
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.