http://bugs.winehq.org/show_bug.cgi?id=15883
Summary: When the Linux version of SDL_mixer is installed,
programs in Qb64 fail to compile (c++ compilation
failed).
Product: Wine
Version: 1.1.7
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: samanddeanus(a)yahoo.com
When the Linux version of SDL_mixer is installed, programs in Qb64 fail to
compile (c++ compilation failed).
--
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=42329
Bug ID: 42329
Summary: Hellgate London Multiplayer: disconnect on specific
actions
Product: Wine
Version: 2.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Kakarott2003(a)yahoo.de
Distribution: ---
Created attachment 57080
--> https://bugs.winehq.org/attachment.cgi?id=57080
log 1: disconnect on jump
With london2038.com (http://www.hellgateaus.info/forum/server-reboot/) there is
a new server for running Hellgate London in multiplayer.
The windows people can play find.
The most things I can do to.
Like:
- connect to the server
- create and choose a character
- enter stations and tunnels
- chat
- talk to npcs
- walk around
So far so good.
But when I do certain actions I get disconnected.
Like jumping. When I jump, sometimes on the first jump, sometimes later.
Everytime I shoot when I'm in the dungeon (can't shoot in stations).
I tried first with wine-2.0-rc6, then staging.
Tried earlier versions.
Tried some winetricks dlls.
Now with wine-staging-2.0.
Also made a thread on there forum
(http://www.hellgateaus.info/forum/support/hgl-on-linux-with-wine/)
Funny part:
Tried on another PC. Same Debian 64bit. Same wine from repos.
First it disconnected like always.
Then, I don't know what I did, it stayed connected.
I tried to reproduce it but couldn't. Changed wine version. (Of-course always
deleting wine-prefix.)
Nothing. It stayed connected (most times). While on the other machine it always
disconnects.
Tried same debian packages (probably just little different versions) on both
machines. Same /proc-net-TCP-settings.
No change.
Same network with via cable on same switch.
No change.
While staying connected I could see:
- doing nothing ping was around 150ms
- doing something the ping rose (saw times up around 100000ms...) until
standing and waiting, then it would fall normal again
- lots of tcp packages flowing in wireshark while actions were happening
Not really playable. But it stays connected. Somehow...
Now I made logs with
+accel,+actxprxy,+advapi,+animate,+chain,+comboex,+commctrl,+commdlg,+context,+cred,+crypt,+cryptasn,+cryptnet,+datetime,+dpa,+dsa,+eventlog,+handle,+header,+heap,+hotkey,+icmp,+imagelist,+ipaddress,+iphlpapi,+listview,+lsa,+monthcal,+mpr,+mscoree,+nativefont,+netapi32,+netbios,+ntlm,+ole,+oleacc,+olemalloc,+olepicture,+olerelay,+pager,+progress,+propsheet,+rebar,+reg,+rpc,+schannel,+secur32,+service,+statusbar,+storage,+syslink,+tab,+theme_button,+theme_scroll,+theming,+themingcombo,+toolbar,+tooltips,+trackbar,+treeview,+typelib,+updown,+userenv,+variant,+wbemprox,+winediag,+wininet,+winsock,+winspool,+wmi
Hope somebody can help.
--
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=5159
joaopa <jeremielapuree(a)yahoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeremielapuree(a)yahoo.fr
--- Comment #66 from joaopa <jeremielapuree(a)yahoo.fr> ---
Does the bug still occur with wine-4.2?
--
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=37965
Bug ID: 37965
Summary: Dead Space 3 sometimes fails to load checkpoints that
are not save points
Product: Wine
Version: 1.7.35
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: abolte(a)systemsaviour.com
Distribution: ---
Dead Space 3 autosaves the game, and there is no manual save option. While
checkpoints in the game are frequent, save points only occur every few
checkpoints. In theory, this means your character can die at any time without
major consequence. However quitting the game and loading it again may involve
replaying maybe 10+ minutes depending specifically where the death occurred.
Unfortunately, it seems that death in areas where the previous checkpoint was
not a save point causes the checkpoint to fail loading properly - resulting in
an instant death before the game even draws your character to the screen. This
results in a death/respawn loop that only ends when you bring up the in-game
main menu and select the option to exit the game, losing progress in the
process.
It is also noteworthy that the mouse cursor disappears from the game menu until
the option to end the current game is selected - presumably another side-effect
of the aforementioned bug. Re-loading the most recent save point gets the game
running normally again (until the next time it is triggered).
There is a video posted of this behaviour here:
https://www.youtube.com/watch?v=KDWbnrcx4Gc
While this behaviour was not reported in the Dead Space 3 AppDB entries, I
suspect this is the sort of thing that can easily go unnoticed without a
complete playthrough under Wine (which I just did) - particularly since I don't
think I even died during the first half of the game. I first encountered this
in Chapter 13, but it could be an issue in other chapters. I vaguely recall
seeing it later in the game somewhere.
The game was cracked to work around what I suspect is a variant of bug #34517
(only without an alternative work-around here). To rule out the crack being the
issue causing this behaviour, I copied the entire game directory and my save
game to a real Windows installation, where the bug could not be reproduced.
Observed on 1.7.35 with 8e9e4a6 reverted due to it producing a regression
(which I'll report separately momentarily).
--
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=42097
Bug ID: 42097
Summary: The Vanishing of Ethan Carter disabling Light Shafts
cause to graphic corrupt
Product: Wine
Version: 2.0-rc3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 56610
--> https://bugs.winehq.org/attachment.cgi?id=56610
light shafts disabled
It makes a layer effect.
--
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=34080
Bug #: 34080
Summary: Half-life 2 : Ammo doesn't display when loading game
Product: Wine
Version: 1.6-rc5
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: scrimekiler(a)yahoo.fr
Classification: Unclassified
Created attachment 45307
--> http://bugs.winehq.org/attachment.cgi?id=45307
loaded game showing the bug
When I load a game, I can't see how much ammo is left on a weapon.
A workaround : changing video mode fullscreen/windowed then going back to the
previous one and then ammo display correctly.
--
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=38400
Bug ID: 38400
Summary: Files fail to save and open in BDCraft Cubik Lite/Pro
Product: Wine
Version: 1.7.40
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexjvanderpotwebdesign(a)gmail.com
Distribution: ---
Created attachment 51253
--> https://bugs.winehq.org/attachment.cgi?id=51253
Backtrace from "export json" attempt
File saving and opening fails in BDCraft Cubik in both the Pro and Lite
versions. This makes the program effectively useless in Wine as you can not
import/export models. A backtrace from a save attempt is attached.
--
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=46651
Bug ID: 46651
Summary: winegcc does not accept additional flags
Product: Wine
Version: 4.1
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mrx(a)hcc.im
Created attachment 63573
--> https://bugs.winehq.org/attachment.cgi?id=63573
log
As macOS 10.14 SDK does not provide 32-bit libraries anymore, one possible way
to compile wine is to get an earlier SDK and use `-isysroot` switch to make
compiler use correct SDK path. (Getting a complete Xcode and using
`xcode-select` should be possible but takes too much disk space. Stripped down
macOS SDK and toolchain could save several GBs)
However, when compiling wine, `winegcc` does not pass any flag to underlying
`cc`, so wine dlls that link to macOS frameworks won't find the correct SDK to
link to.
There is a log below which is one of the failing dll. Command line is given by
`make`. The 10.13 SDK is at
`/Users/MrX/Developer13/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk`,
and different ways trying to pass the `-isysroot` switch such as environment
variable and appending desired switch all failed.
I've tried to manually build the file using command line given by `winegcc -v`
with `-isysroot` appended and I could get the desired .so file.
--
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=46611
Bug ID: 46611
Summary: Readiris 17 fails to load when d2d1 is enabled:
fixme:d2d:d2d_factory_CreateGeometryGroup iface
Product: Wine
Version: 4.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: tinywrkbee(a)gmail.com
Distribution: ---
Created attachment 63511
--> https://bugs.winehq.org/attachment.cgi?id=63511
d2d1 enabled, application crashes
App: Readiris 17, latest trial version, can be downloaded freely from
http://www.irislink.com/EN-IL/c1760/Readiris-17---Trial-version--PDF-Softwa…
Wine: 4.1, WINEARCH=win32, Window 7, winetricks riched20 msxml6.
Behavior:
Installation finished successfully but application failing to load.
After disabling d2d1 the application loads correctly.
See attachments for output with d2d1 (failing) and output without.
0009:fixme:d2d:d2d_factory_CreateGeometryGroup iface 0x76ef8e0, fill_mode 0x1,
geometries 0x8c71df0, geometry_count 2, group 0x323634 stub!
--
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=36382
Bug ID: 36382
Summary: valgrind shows a possible leak in in
ddraw/tests/ddraw7.c
Product: Wine
Version: 1.7.18
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==5480== 28 bytes in 1 blocks are possibly lost in loss record 259 of 953
==5480== at 0x7BC508EB: RtlAllocateHeap (heap.c:255)
==5480== by 0x61B3BE8: apartment_getclassobject (compobj.c:526)
==5480== by 0x61B6FF6: get_inproc_class_object (compobj.c:2894)
==5480== by 0x61B9D5F: CoGetClassObject (compobj.c:3032)
==5480== by 0x61BA4E7: CoCreateInstance (compobj.c:3197)
==5480== by 0x515764C: func_ddraw7 (ddraw7.c:2911)
==5480== by 0x50CC30B: main (test.h:584)
==5480==
--
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=36381
Bug ID: 36381
Summary: valgrind shows a couple possible leaks in in
ddraw/tests/ddraw2.c
Product: Wine
Version: 1.7.18
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==5342== 28 bytes in 1 blocks are possibly lost in loss record 255 of 1,003
==5342== at 0x7BC508EB: RtlAllocateHeap (heap.c:255)
==5342== by 0x6288BE8: apartment_getclassobject (compobj.c:526)
==5342== by 0x628BFF6: get_inproc_class_object (compobj.c:2894)
==5342== by 0x628ED5F: CoGetClassObject (compobj.c:3032)
==5342== by 0x628F4E7: CoCreateInstance (compobj.c:3197)
==5342== by 0x51134ED: func_ddraw2 (ddraw2.c:3061)
==5342== by 0x50CC30B: main (test.h:584)
==5342==
==5342== 92 bytes in 1 blocks are possibly lost in loss record 515 of 1,003
==5342== at 0x7BC508EB: RtlAllocateHeap (heap.c:255)
==5342== by 0x4ABE069: d3d3_CreateViewport (ddraw.c:3941)
==5342== by 0x4ABE1EE: d3d2_CreateViewport (ddraw.c:3962)
==5342== by 0x510969B: create_viewport.constprop.3 (ddraw2.c:268)
==5342== by 0x510B50F: test_lighting_interface_versions (ddraw2.c:3407)
==5342== by 0x5113DEB: func_ddraw2 (ddraw2.c:6421)
==5342== by 0x50CC30B: main (test.h:584)
==5342==
--
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=36349
Bug ID: 36349
Summary: valgrind shows a few leaks in d3d9/tests/stateblock.c
Product: Wine
Version: 1.7.17
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==4967== 148 bytes in 1 blocks are possibly lost in loss record 548 of 819
==4967== at 0x40087BA: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==4967== by 0x72216AF: ??? (in /usr/lib/libdrm_intel.so.1.0.0)
==4967== by 0x721C294: drm_intel_bo_alloc (in
/usr/lib/libdrm_intel.so.1.0.0)
==4967== by 0x6F2A251: ??? (in /usr/lib/dri/i965_dri.so)
==4967== by 0x6F2A84B: ??? (in /usr/lib/dri/i965_dri.so)
==4967== by 0x6F5F6DB: ??? (in /usr/lib/dri/i965_dri.so)
==4967== by 0x6EEE9B4: ??? (in /usr/lib/dri/i965_dri.so)
==4967== by 0x6918B9B: ??? (in /usr/lib/libGL.so.1.2.0)
==4967== by 0x68E82F4: ??? (in /usr/lib/libGL.so.1.2.0)
==4967== by 0x6034DF2: create_glxcontext.isra.0 (opengl.c:1254)
==4967== by 0x6035127: X11DRV_wglCreateContextAttribsARB (opengl.c:2071)
==4967== by 0x5459C29: wglCreateContextAttribsARB (wgl.c:268)
==4967== by 0x4FB39D8: context_create (context.c:1543)
==4967== by 0x5049866: wined3d_swapchain_create (swapchain.c:914)
==4967== by 0x4F58F1F: d3d9_swapchain_create (swapchain.c:333)
==4967== by 0x4F53348: d3d9_device_CreateAdditionalSwapChain (device.c:504)
==4967== by 0x4A878DC: switch_render_target (stateblock.c:187)
==4967== by 0x4A89C94: execute_test_chain (stateblock.c:141)
==4967== by 0x4A8A9BE: test_state_management (stateblock.c:457)
==4967== by 0x4ADCD4C: run_test (test.h:584)
==4967==
--
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=38021
Bug ID: 38021
Summary: ntdll:load_dll doesn't check for correct dll ARCH
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: patrick1804(a)web.de
Distribution: ---
Problem 1:
ntdll:load_dll doesn't check if the found DLL has the wrong arch.
For example: 64bit application want's to load xinput1_3.dll.
There's a 32bit xinput1_3.dll in the same folder.
Expected behavior:
It should ignore this dll, instead of trying to open it.
Problem 2:
ntdll:load_dll doesn't check other locations for this DLL once a matching one
has been found, even when it has the wrong arch and couldn't be loaded.
For example: 64bit application want's to load xinput1_3.dll.
There's a 32bit xinput1_3.dll in the same folder.
It tries to open the file and fails. It doesn't check other folders like
System32.
The application doesn't start.
Expected behavior:
load_dll looks for 64bit xinput1_3.dll in system32 and starts.
--
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=36267
Bug ID: 36267
Summary: valgrind shows an invalid read in ddraw/tests/ddraw4.c
Product: Wine
Version: 1.7.18
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==4973== Invalid read of size 4
==4973== at 0x50CE7C7: update_heap_entry (glsl_shader.c:905)
==4973== by 0x50CE900: shader_glsl_update_float_vertex_constants
(glsl_shader.c:939)
==4973== by 0x50AAEEE: wined3d_device_set_vs_consts_f (device.c:2297)
==4973== by 0x5137052: wined3d_stateblock_apply (stateblock.c:957)
==4973== by 0x498F1ED: ddraw_set_cooperative_level (ddraw.c:951)
==4973== by 0x498F69F: ddraw4_SetCooperativeLevel (ddraw.c:1019)
==4973== by 0x4CA8A97: test_coop_level_create_device_window (ddraw4.c:678)
==4973== by 0x4CCC1E5: func_ddraw4 (ddraw4.c:7300)
==4973== by 0x4D1E890: run_test (test.h:584)
==4973== by 0x4D1EC7F: main (test.h:654)
==4973== Address 0xb458000 is 42,896 bytes inside a block of size 65,544
alloc'd
==4973== at 0x7BC4C735: notify_alloc (heap.c:255)
==4973== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716)
==4973== by 0x50DF534: constant_heap_init (glsl_shader.c:6409)
==4973== by 0x50DF8FB: shader_glsl_alloc (glsl_shader.c:6478)
==4973== by 0x50A5691: wined3d_device_init_3d (device.c:882)
==4973== by 0x498E381: ddraw_attach_d3d_device (ddraw.c:591)
==4973== by 0x498E5B9: ddraw_create_swapchain (ddraw.c:634)
==4973== by 0x498F124: ddraw_set_cooperative_level (ddraw.c:934)
==4973== by 0x498F69F: ddraw4_SetCooperativeLevel (ddraw.c:1019)
==4973== by 0x4CA8A97: test_coop_level_create_device_window (ddraw4.c:678)
==4973== by 0x4CCC1E5: func_ddraw4 (ddraw4.c:7300)
==4973== by 0x4D1E890: run_test (test.h:584)
==4973== by 0x4D1EC7F: main (test.h:654)
==4973==
--
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=36261
Bug ID: 36261
Summary: valgrind shows a use after free in
ddraw/tests/ddraw4.c
Product: Wine
Version: 1.7.18
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==29500== Invalid write of size 4
==29500== at 0x498B288: d3d_device_inner_Release (device.c:319)
==29500== by 0x498B45B: d3d_device3_Release (device.c:345)
==29500== by 0x4C6844D: test_process_vertices (ddraw4.c:624)
==29500== by 0x4C8C1E0: func_ddraw4 (ddraw4.c:7299)
==29500== by 0x4CDE890: run_test (test.h:584)
==29500== by 0x4CDEC7F: main (test.h:654)
==29500== Address 0x47a4dc8 is 112 bytes inside a block of size 160 free'd
==29500== at 0x7BC4C782: notify_free (heap.c:263)
==29500== by 0x7BC510C7: RtlFreeHeap (heap.c:1762)
==29500== by 0x497D9F9: ddraw_destroy (ddraw.c:441)
==29500== by 0x497DC0C: ddraw4_Release (ddraw.c:472)
==29500== by 0x49A3B99: ddraw_surface_release_iface (surface.c:552)
==29500== by 0x49A3D41: ddraw_surface4_Release (surface.c:611)
==29500== by 0x498B229: d3d_device_inner_Release (device.c:316)
==29500== by 0x498B45B: d3d_device3_Release (device.c:345)
==29500== by 0x4C6844D: test_process_vertices (ddraw4.c:624)
==29500== by 0x4C8C1E0: func_ddraw4 (ddraw4.c:7299)
==29500== by 0x4CDE890: run_test (test.h:584)
==29500== by 0x4CDEC7F: main (test.h:654)
==29500==
--
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=46617
Bug ID: 46617
Summary: Far Cry v1.40 locks up on the loading screen
Product: Wine
Version: 4.1
Hardware: x86
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: 1867b095a0e48ff8619457c703f69b5acc715ede
Distribution: ---
Created attachment 63519
--> https://bugs.winehq.org/attachment.cgi?id=63519
plain terminal output
This was tested with GOG.com version (the game is already patched to the latest
1.4 version). The game was set up to use the default Direct3D renderer
(selecting the OpenGL renderer resulted in an early crash on start for me).
I couldn't reproduce the problem with the original demo version.
The game loads up to the main menu properly, but it hangs with 100% CPU usage
on the loading screen when I'm trying to start a new game or load a previously
saved game.
Reverting the following commit fixes the problem for me:
commit 1867b095a0e48ff8619457c703f69b5acc715ede
Author: Zebediah Figura <z.figura12(a)gmail.com>
Date: Wed Feb 6 19:38:28 2019 -0600
wined3d: Store stream state in the wined3d_stateblock_state structure.
Please let me know what debug channels would be of help.
wine-4.1-108-gf7b3120991
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 415.22.05
--
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=41168
Bug ID: 41168
Summary: Test Drive Unlimited Crash before entry main menu
Product: Wine
Version: 1.9.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mrdeathjr28(a)yahoo.es
Distribution: ---
Created attachment 55397
--> https://bugs.winehq.org/attachment.cgi?id=55397
backtrace-testdriveunlimited
test drive unlimited crash before entry main menu, exactly when eden cinematic
finish
System Specs
Nvidia Drivers 370.23 (run package from nvidia drivers homepage)
Xubuntu 16.04 64Bit - Kernel 4.4.0-36 generic (ubuntu mainline) - CPUFreq:
Performance
CPU: INTEL Pentium G3258 (Haswell 22nm) 4.1Ghz + Artic Cooling Alpine 11 Plus
MEMORY: 8GB DDR3 1333 (2x4) Patriot value (dual channel: 21.3 gb/s)
GPU: Zotac Nvidia Geforce GT630 (GK208 28nm: 384 Shaders / 8 ROPS) Zone Edition
Passive Cooling 2GB DDR3 1800Mhz 64Bit (14.4Gb/s)
MAINBOARD: MSI H81M E33
--
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=45312
Bug ID: 45312
Summary: AC Syndicate needs bcrypt algorythm/functions
(ECDH_P256, BCryptGenerateKeyPair,
BCryptFinalizeKeyPair)
Product: Wine
Version: 3.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bcrypt
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
Distribution: Gentoo
Assassin's Creed : Syndicate crashes when the game wants to access to the main
menu. Precisely after the Intro video (Nvidia, Ubisoft video) and the screen
with the message which say "Press any key to continue".
This issue exists only when you launch the game with UPlay on Online Mode.
If UPlay is on Offline mode (no cloud save, success etc...), you can to access
to the main menu without problem.
----------
1- When the game crashes, i have these line in my output console :
"0108:fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"ECDH_P256" not
supported"
I created a hack to add the support of ECDH_P256 (see attached files)
2- With my 1st hack with ECDH_P256 support, the game still crashes but for an
other reason. This time, i have error line about a bcrypt function not
implemented : BCryptGenerateKeyPair
I created a hack to implement this function (see attached files)
3- With my both latest patches, the game continu to crash at the same place.
Now it crashes because a second function for bcrypt is not implemented :
BCryptFinalizeKeyPair
I created a hack to implement this function (see attached files)
----------
With my 3 workaround, the crash is gone and i can to access to the main menu
with UPlay on Online mode after pressing a key.
Now, i don't know if my workaround are correct to send these files to
wine-patches or if someone prefer to implement completly these
functions/algorythm.
Thanks,
Maxime
--
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=36348
Bug ID: 36348
Summary: valgrind shows a couple leaks in d3d9/tests/d3d9ex.c
Product: Wine
Version: 1.7.17
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==3976== 16 bytes in 1 blocks are definitely lost in loss record 396 of 1,973
==3976== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255)
==3976== by 0x4F58C13: Direct3DCreate9Ex (d3d9_main.c:63)
==3976== by 0x4A557EB: create_device.constprop.1 (d3d9ex.c:59)
==3976== by 0x4A55992: test_reset (d3d9ex.c:684)
==3976== by 0x4A5A5CB: func_d3d9ex (d3d9ex.c:1218)
==3976== by 0x4ADCD4C: run_test (test.h:584)
==3976== by 0x4ADD13B: main (test.h:654)
==3976==
==3976== 12,068 bytes in 1 blocks are definitely lost in loss record 1,915 of
1,973
==3976== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255)
==3976== by 0x506F901: wined3d_create (wined3d_main.c:95)
==3976== by 0x4F654AE: d3d9_init (directx.c:647)
==3976== by 0x4F58C30: Direct3DCreate9Ex (d3d9_main.c:66)
==3976== by 0x4A557EB: create_device.constprop.1 (d3d9ex.c:59)
==3976== by 0x4A55992: test_reset (d3d9ex.c:684)
==3976== by 0x4A5A5CB: func_d3d9ex (d3d9ex.c:1218)
==3976== by 0x4ADCD4C: run_test (test.h:584)
==3976== by 0x4ADD13B: main (test.h:654)
==3976==
--
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=36621
Bug ID: 36621
Summary: valgrind shows several definite leaks in
ddraw/tests/ddraw1.c
Product: Wine
Version: 1.7.18
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==13886== 20 bytes in 1 blocks are definitely lost in loss record 205 of 1,033
==13886== at 0x7BC4C75D: notify_alloc (heap.c:255)
==13886== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716)
==13886== by 0x4B90A4B: DirectDrawCreateClipper (ddraw.c:3274)
==13886== by 0x4B90C0D: ddraw7_CreateClipper (ddraw.c:3309)
==13886== by 0x4B90E50: ddraw1_CreateClipper (ddraw.c:3342)
==13886== by 0x4A6BA13: create_device (ddraw1.c:286)
==13886== by 0x4A6E659: test_coop_level_d3d_state (ddraw1.c:788)
==13886== by 0x4A87307: func_ddraw1 (ddraw1.c:5488)
==13886== by 0x4B24F84: run_test (test.h:584)
==13886== by 0x4B25373: main (test.h:654)
==13886==
==13886== 20 bytes in 1 blocks are definitely lost in loss record 206 of 1,033
==13886== at 0x7BC4C75D: notify_alloc (heap.c:255)
==13886== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716)
==13886== by 0x4B90A4B: DirectDrawCreateClipper (ddraw.c:3274)
==13886== by 0x4B90C0D: ddraw7_CreateClipper (ddraw.c:3309)
==13886== by 0x4B90E50: ddraw1_CreateClipper (ddraw.c:3342)
==13886== by 0x4A6BA13: create_device (ddraw1.c:286)
==13886== by 0x4A6ED15: test_surface_interface_mismatch (ddraw1.c:860)
==13886== by 0x4A8730C: func_ddraw1 (ddraw1.c:5489)
==13886== by 0x4B24F84: run_test (test.h:584)
==13886== by 0x4B25373: main (test.h:654)
==13886==
etc.
and one case of:
==13516== 4,096 bytes in 1 blocks are definitely lost in loss record 1,473 of
1,516
==13516== at 0x72E66F1: ??? (in /usr/lib/libdrm_intel.so.1.0.0)
==13516== by 0x72E2378: drm_intel_bo_map (in /usr/lib/libdrm_intel.so.1.0.0)
==13516== by 0x6EF6DC2: ??? (in /usr/lib/dri/i965_dri.so)
==13516== by 0x6EF8594: ??? (in /usr/lib/dri/i965_dri.so)
==13516== by 0x6EFECCD: ??? (in /usr/lib/dri/i965_dri.so)
==13516== by 0x6D2D411: ??? (in /usr/lib/dri/i965_dri.so)
==13516== by 0x6F0189E: ??? (in /usr/lib/dri/i965_dri.so)
==13516== by 0x6D16339: ??? (in /usr/lib/dri/i965_dri.so)
==13516== by 0x6D1A9E9: ??? (in /usr/lib/dri/i965_dri.so)
==13516== by 0x68D1C95: glTexSubImage2D (in /usr/lib/libGL.so.1.2.0)
==13516== by 0x510FE80: surface_upload_data (surface.c:1641)
==13516== by 0x511D054: surface_load_texture (surface.c:4861)
==13516== by 0x511D52E: surface_load_location (surface.c:4954)
==13516== by 0x5111C25: surface_load (surface.c:2150)
==13516== by 0x51294DA: texture2d_sub_resource_load (texture.c:730)
==13516== by 0x5128AE8: wined3d_texture_load (texture.c:539)
==13516== by 0x50558C7: arbfp_blit_surface (arb_program_shader.c:7653)
==13516== by 0x5121910: wined3d_surface_blt (surface.c:6060)
==13516== by 0x4A9646C: ddraw_surface_blt_clipped (surface.c:1387)
==13516== by 0x4A96CCA: ddraw_surface7_Blt (surface.c:1543)
==13516==
--
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=36340
Bug ID: 36340
Summary: valgrind shows several warnings in
ddraw/tests/ddraw2.c
Product: Wine
Version: 1.7.18
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
==20452== Conditional jump or move depends on uninitialised value(s)
==20452== at 0x5842378: GetRegionData (region.c:889)
==20452== by 0x4E726BE: ddraw_clipper_GetClipList (clipper.c:213)
==20452== by 0x4EA05EE: ddraw_surface7_Blt (surface.c:1429)
==20452== by 0x4EA1FE6: ddraw_surface1_Blt (surface.c:1597)
==20452== by 0x4D9776E: test_clipper_blt (ddraw2.c:647)
==20452== by 0x4DA7C8E: func_ddraw2 (ddraw2.c:6398)
==20452== by 0x4E1C6DC: run_test (test.h:584)
==20452== by 0x4E1CACB: main (test.h:654)
==20452== Uninitialised value was created by a stack allocation
==20452== at 0x4EA0411: ddraw_surface7_Blt (surface.c:1503)
==20452==
and several leaks, e.g.,:
==20664== 20 bytes in 1 blocks are definitely lost in loss record 208 of 1,043
==20664== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255)
==20664== by 0x4E8EA7E: DirectDrawCreateClipper (ddraw.c:3274)
==20664== by 0x4E8EC42: ddraw7_CreateClipper (ddraw.c:3309)
==20664== by 0x4E8ED9F: ddraw2_CreateClipper (ddraw.c:3331)
==20664== by 0x4DA6CBC: test_clipper_blt (ddraw2.c:565)
==20664== by 0x4DB7C8E: func_ddraw2 (ddraw2.c:6398)
==20664== by 0x4E2C6DC: run_test (test.h:584)
==20664== by 0x4E2CACB: main (test.h:654)
==20664==
--
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=46208
Bug ID: 46208
Summary: Elite Dangerous is unstable in wine-devel
Product: Wine
Version: 3.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: brendan(a)redmandi.com
Distribution: ---
When using wine-devel v3.21, Elite Dangerous is unstable and will usually
freeze before finishing the opening video (but will sometimes get as far as
shader compilation).
When attaching a debugger, it looks like all processes are waiting for an
event.
The program needs to be killed with a 'kill -9'.
The workaround is to run Elite with 'taskset -c 0', but it also appears to
progress further if you run with 'WINEDEBUG=+relay'.
This leads me to believe the issue is one of timing (as opposed to
multi-threading).
When using wine-staging v3.21, Elite has no such problems and runs perfectly.
A git bi-sect led me to find that the reason for this was a single patch:
https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-fute…
Applying just this patch to wine-devel v3.21 results in the game running fine.
--
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=46618
Bug ID: 46618
Summary: Far Cry v1.40 locks up when changing screen resolution
or anti-aliasing level
Product: Wine
Version: 4.1
Hardware: x86
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: cc88fb0b691efd771cf43045dccbe9c5b7bc9993
Distribution: ---
Created attachment 63520
--> https://bugs.winehq.org/attachment.cgi?id=63520
plain terminal output
Just like with bug #46617, I tested this bug with the GOG.com version. Unable
to reproduce with the demo version.
The game freezes with high CPU usage when I'm trying to change screen
resolution or anti-aliasing level in the Video Options menu.
According to my testing this was caused by
commit cc88fb0b691efd771cf43045dccbe9c5b7bc9993
Author: Zebediah Figura <z.figura12(a)gmail.com>
Date: Wed Feb 6 19:38:25 2019 -0600
wined3d: Store the index buffer in the wined3d_stateblock_state structure.
The patch can't be reverted cleanly, but the problem doesn't exist with the
previous commit.
wine-4.1-108-gf7b3120991
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 415.22.05
--
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.