http://bugs.winehq.org/show_bug.cgi?id=14495
Summary: NVIDIA Dawn Demo Fails to run
Product: Wine
Version: 1.1.1
Platform: PC
URL: http://www.nzone.com/object/nzone_dawndemo_home.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cwadge(a)gmail.com
Created an attachment (id=14820)
--> (http://bugs.winehq.org/attachment.cgi?id=14820)
Debug Verbosity
NVIDIA's "Dawn" graphical demo crashes on execution with the following messageL
wine: Unhandled page fault on read access to 0x00000044 at address 0x406609
(thread 0009), starting debugger...
More verbose debugging is attached as a text file.
--
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=40631
Bug ID: 40631
Summary: Denuvo support
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: roman(a)hargrave.info
Distribution: ---
It should be looked in to whether it is possible to support applications using
`Denuvo` copy protection without any effort from the publisher of
aforementioned copy protection.
--
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=41166
Bug ID: 41166
Summary: World of Warcraft Legion 7.0.3 OpenGL Artifacting
Product: Wine-staging
Version: 1.9.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: liam(a)lpmdesigns.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Hello,
So I have gotten World of Warcraft running perfectly well in wine-staging
1.9.16. In fact, the performance is excellent at 4k with my GTX 1070.
However, there is some nasty graphical glitches/artifacting going on.
I contacted Blizzard, and they said that it's a Wine problem, not with their
OpenGL implementation.
I made a video of the issue: https://www.youtube.com/watch?v=UHOmLNZ2ejY
What I expect to happen:
- For World of Warcraft to run in OpenGL without said graphical glitches
What did happen:
- Again, I was very surprised from the performance. So if the game can be run
without these glitches, I am as good as golden.
- As a side note, running in Directx 9 does not have these issues, but the
performance is quite worse.
Hoe to reproduce:
- I have a GTX 1070 using proprietary drivers, tested the 367.35 and 370 beta.I
presume this would happen with AMD and other GPU's.
- Launch WoW with patch 7.0.3, and make sure OpenGL is the selected API.
I don't know what logs I could attach, so please let me know if you need any
and I will attach.
--
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=42364
Bug ID: 42364
Summary: Very low texture resolution in Trackmania Nations
Forever / United (Regression)
Product: Wine
Version: 2.0
Hardware: x86
URL: http://files.trackmaniaforever.com/tmnationsforever_se
tup.exe
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: michael(a)fds-team.de
CC: joseph.kucia(a)gmail.com
Regression SHA1: 90909951154e1d663bebc134263b4025eacbdabd
Distribution: Debian
Created attachment 57141
--> https://bugs.winehq.org/attachment.cgi?id=57141
ddraw log
I tested Trackmania Nations Forever and noticed that many of the textures have
a very low resolution. Even the small time display (top bar in main menu /
in-game) seems blurred. Since I could not remember having such problems the
last time I tested the application, I did a bisect and found the guilty commit:
commit 90909951154e1d663bebc134263b4025eacbdabd
Author: Józef Kucia <jkucia(a)codeweavers.com>
Date: Mon Jan 2 10:44:38 2017 +0100
ddraw: Subtract framebuffer size from reported available video memory.
Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com>
Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
The game uses ddraw only to detect the available memory while the actual
drawing is done using d3d9. See attachment for a +ddraw log. The test was done
on a Geforce GTX 660 with 2GB VRAM and 1280x1024 as desktop resolution.
--
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=43379
Bug ID: 43379
Summary: valgrind shows an invalid read in
dlls/ntdll/tests/file.c
Product: Wine
Version: 2.12
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase, valgrind
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: ---
==30466== Invalid read of size 1
==30466== at 0x7BCAD43B: virtual_check_buffer_for_write (virtual.c:1718)
==30466== by 0x7BC48F48: NtReadFile (file.c:854)
==30466== by 0x4A47FDE: test_read_write (file.c:3504)
==30466== by 0x4A4DEE9: func_file (file.c:4288)
==30466== by 0x4AA25B4: run_test (test.h:603)
==30466== by 0x4AA2A13: main (test.h:687)
==30466== Address 0xdeadbeef is on thread 1's stack
==30466==
--
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=43748
Bug ID: 43748
Summary: Dead or Alive Last Round ntdll crash on Wine newer
than 1.8.7 under Linux, but not in OS X
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: tod.jackson(a)gmail.com
Distribution: ---
Created attachment 59244
--> https://bugs.winehq.org/attachment.cgi?id=59244
staging-2.17 console/debug output
I got Dead or Alive Last Round (free on Steam) working without issues under OS
X, with multiple Wine versions tested: 2.0.2, 2.13, 2.16-staging. However,
under Linux, no version of Wine newer than 1.8.7 even proceeds beyond a brief
white window.
I attached a log with the default debug settings, please let me know what
further to enable as I'm not sure what the issue is.
--
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=44113
Bug ID: 44113
Summary: World of Tanks(WoT) crashes on AMD GPU the moment
entering hangar starting version 0.9.20.1.3 of WoT
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: HASH.DuOrden(a)gmail.com
Distribution: ---
Created attachment 59834
--> https://bugs.winehq.org/attachment.cgi?id=59834
wine ./WorldOfTanks.exe -clientGraphicsAPI d3d9 &>./WorldOfTanks.log
Starting with WoT version 0.9.20.1.3 game now crashes right after entering the
hangar.
It happens only with AMD GPU, I have couple of PC's, one with AMD/ATI Radeon RX
460 and nVidia GeForce GTX 570, it works on nVidia but crashes on AMD/ATI.
It happened without Me updating anything so I'm assuming it is something
WarGaming changed some thing in the WoT.
I am currently on Gentoo profile 13 and wine-staging-2.19,
gentoo-sources-4.13.4.
I tried with kernel versions gentoo-sources-4.13.4 to gentoo-sources-4.13.10
and wine-staging-2.19 to wine-staging-2.21 without any success, with staging
enabled and not, with gcc-5.4.0.
I've tried to re-download the game on clean prefix, WinXP and Win7 installing
or not d3dx9_36, xact_jun2010, msvcp110/msvcr110, msvcp140/msvcr140, no change.
Without sound or not.
I am currently rebuilding my system with gcc-6.4.0, gcc version 5.4.0 was not a
problem before, but now I simply do not know what to do!
P.S.: All this is on RU region.
--
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=44287
Bug ID: 44287
Summary: Possible access to unintended variable in
"wine/dlls/gdi32/freetype.c" line 2349
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: petrum(a)gmail.com
Distribution: ---
While experimenting with a CodeSonar plugin we develop, we noticed a
potential bug in file "wine/dlls/gdi32/freetype.c" line 2349 function
map_font_family
Family *family = find_family_from_any_name(repl);
if (family != NULL)
{
Family *new_family = HeapAlloc(GetProcessHeap(), 0, sizeof(*new_family));
if (new_family != NULL)
{
TRACE("mapping %s to %s\n", debugstr_w(repl), debugstr_w(orig));
new_family->FamilyName = strdupW(orig);
new_family->EnglishName = NULL;
list_init(&new_family->faces);
new_family->replacement = &family->faces; //HERE
list_add_tail(&font_list, &new_family->entry);
return TRUE;
}
}
Shouldn't new_family be used (instead of family) at the mentioned position?
Thanks,
Petru Florin Mihancea
--
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=44290
Bug ID: 44290
Summary: Possible access to unintended field in
"wine/dlls/winmm/mmio.c" line 788
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winmm&mci
Assignee: wine-bugs(a)winehq.org
Reporter: petrum(a)gmail.com
Distribution: ---
While experimenting with a CodeSonar plugin we develop, we noticed a
potential bug in file "wine/dlls/winmm/mmio.c"" line 788 function mmioRead
size = MMIO_GrabNextBuffer(wm, TRUE);
if (size <= 0) break;
if (size > cch) size = cch;
memcpy(pch, wm->info.pchBuffer, size);
wm->info.pchNext += size; //HERE
pch += size;
cch -= size;
count += size;
Shouldn't wm->info.pchBuffer be incremented at the mentioned line (instead of
wm->info.pchNext)?
Thanks,
Petru Florin Mihancea
--
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=44293
Bug ID: 44293
Summary: Possible access to unintended field in
"wine/tools/widl/header.c" line 1292
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: petrum(a)gmail.com
Distribution: ---
While experimenting with a CodeSonar plugin we develop, we noticed a
potential bug in file "wine/tools/widl/header.c" line 1292, function
write_locals
write_type_decl_left(fp, type_function_get_rettype(func->type));
fprintf(fp, " __RPC_STUB %s_%s_Stub(\n", iface->name, get_name(m)); //HERE
write_args(fp, type_get_function_args(func->type), iface->name, 1, TRUE);
fprintf(fp, ")");
Shouldn't func be used instead of m in the mentioned line? The lines around
that line both make use of func and it is not clear why m is in use in line
1292.
Thanks,
Petru Florin Mihancea
--
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.