wine-bugs February 2017

wine-bugs@winehq.org

1 participants
7820 discussions

[Bug 36213] New: valgrind shows some possible leaks under crypt32/tests/sip.c
by wine-bugs＠winehq.org 18 Feb '17

18 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=36213 Bug ID: 36213 Summary: valgrind shows some possible leaks under crypt32/tests/sip.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==23202== 52 bytes in 1 blocks are possibly lost in loss record 111 of 282 ==23202== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==23202== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==23202== by 0x514398B: CryptMemAlloc (main.c:124) ==23202== by 0x51627B5: CRYPT_CacheSIP (sip.c:576) ==23202== by 0x5162B5D: CRYPT_LoadSIP (sip.c:653) ==23202== by 0x5162C60: CryptSIPLoad (sip.c:698) ==23202== by 0x4EA631D: test_SIPLoad (sip.c:357) ==23202== by 0x4EA67BF: func_sip (sip.c:444) ==23202== by 0x4EB7F67: run_test (test.h:584) ==23202== by 0x4EB8356: main (test.h:654) ==23202== -- 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.

1 5

[Bug 36341] New: valgrind shows some possible leaks under crypt32/tests/base64.c
by wine-bugs＠winehq.org 18 Feb '17

18 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=36341 Bug ID: 36341 Summary: valgrind shows some possible leaks under crypt32/tests/base64.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==21036== 2,628 bytes in 73 blocks are possibly lost in loss record 250 of 266 ==21036== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==21036== by 0x4F815DF: CryptMemAlloc (main.c:124) ==21036== by 0x4F92C4B: crypt_oid_init (oid.c:1403) ==21036== by 0x4F811F8: DllMain (main.c:46) ==21036== by 0x4FA5F36: __wine_spec_dll_entry (dll_entry.c:40) ==21036== by 0x7BC53B24: ??? (in /home/austin/wine-valgrind-known/dlls/ntdll/ntdll.dll.so) ==21036== by 0x7BC5644E: MODULE_InitDLL (loader.c:1068) ==21036== by 0x7BC56AE7: process_attach (loader.c:1157) ==21036== by 0x7BC56AB9: process_attach (loader.c:1149) ==21036== by 0x7BC56CEF: attach_process_dlls (loader.c:2769) ==21036== by 0x401BC7C: ??? (in /home/austin/wine-valgrind-known/libs/wine/libwine.so.1.0) ==21036== -- 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.

1 6

[Bug 37399] New: Urban Assault black screen when using software renderer (palette problem)
by wine-bugs＠winehq.org 18 Feb '17

18 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=37399 Bug ID: 37399 Summary: Urban Assault black screen when using software renderer (palette problem) Product: Wine Version: 1.7.28 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: erich.e.hoover(a)gmail.com Depends on: 37307, 37398 Regression SHA1: 9d49b7a9be6d4ed59a69c3453de4eadb0101ea09 Distribution: Ubuntu Once Bug #37307 and Bug #37398 are resolved/worked around then another issue crops up with Urban Assault, apparently a change back in June makes it such that UA cannot load since the surface it's using does not get a palette. The following error occurs repeated on the command line: fixme:d3d:convert_p8_uint_b8g8r8a8_unorm P8 surface loaded without a palette. -- 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.

1 17

[Bug 39910] New: PDF XChange Editor annotations formatting not displayed after saving
by wine-bugs＠winehq.org 18 Feb '17

18 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=39910 Bug ID: 39910 Summary: PDF XChange Editor annotations formatting not displayed after saving Product: Wine Version: 1.7.31 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sadiyumusak(a)gmail.com Distribution: --- PDF Editor is recommended by the Tracker software company as the new and more advanced replacement for their popular product PDF-XChange Viewer. Indeed it offers a number improvements but I suffer from a number of problems, including: a) You can format text entered in comment boxes, etc. and save them, and then they can be displayed in other PDF viewers (except the PDF Editor which created them!) Such text formatting is there to see even in the same version of PDF Editor installed in Windows, but not under WINE. So the cause of the problem is probably is somewhere in WINE. b) If you click outside a newly created, unsaved comment box, the box vanishes immediately and the application crashes. -- 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.

1 3

[Bug 41206] New: Artemis 2.4.0 crashed upon start
by wine-bugs＠winehq.org 18 Feb '17

18 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=41206 Bug ID: 41206 Summary: Artemis 2.4.0 crashed upon start Product: Wine Version: 1.9.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kurthuwig(a)gmail.com Distribution: --- When I run Artemis 2.4.0 (http://artemis.eochu.com/index.php/downloads/) then it crashes with the attached error messages. v2.3.0 worked 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.

1 10

[Bug 36247] New: VHD Attach crushes because of virtdisk.dll missing
by wine-bugs＠winehq.org 18 Feb '17

18 Feb '17

http://bugs.winehq.org/show_bug.cgi?id=36247 Bug ID: 36247 Summary: VHD Attach crushes because of virtdisk.dll missing Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matyapiro31(a)gmail.com VHD Attach is an application to mount .vhd files as hard disks. It depends on virtdisk.dll but wine doesn't include it. I think we can implement it easily by using libvirt? It support VHD file type. -- 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.

1 7

[Bug 36395] New: valgrind shows a possible leak in inetcomm/tests/mimeole.c
by wine-bugs＠winehq.org 18 Feb '17

18 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=36395 Bug ID: 36395 Summary: valgrind shows a possible leak in inetcomm/tests/mimeole.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==17178== 28 bytes in 1 blocks are possibly lost in loss record 154 of 561 ==17178== at 0x7BC508EB: RtlAllocateHeap (heap.c:255) ==17178== by 0x5498BE8: apartment_getclassobject (compobj.c:526) ==17178== by 0x549BFF6: get_inproc_class_object (compobj.c:2894) ==17178== by 0x549ED5F: CoGetClassObject (compobj.c:3032) ==17178== by 0x549F4E7: CoCreateInstance (compobj.c:3197) ==17178== by 0x4AAC50E: func_mimeole (mimeole.c:99) ==17178== by 0x4AAAE6B: main (test.h:584) ==17178== -- 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.

1 5

[Bug 36662] New: valgrind shows a few memory leaks in ws2_32/tests/sock.c
by wine-bugs＠winehq.org 18 Feb '17

18 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=36662 Bug ID: 36662 Summary: valgrind shows a few memory leaks in ws2_32/tests/sock.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==21586== Thread 1 ws2_32_test.exe.so: ==21586== 60 bytes in 1 blocks are possibly lost in loss record 350 of 701 ==21586== at 0x7BC4C6EB: notify_alloc (heap.c:255) ==21586== by 0x7BC50F2F: RtlAllocateHeap (heap.c:1716) ==21586== by 0x50B07F4: WS2_sendto (socket.c:4545) ==21586== by 0x50B0611: WSASend (socket.c:4500) ==21586== by 0x4F6E338: test_send (sock.c:4194) ==21586== by 0x4F7FDB1: func_sock (sock.c:7742) ==21586== by 0x4F80BB1: run_test (test.h:584) ==21586== by 0x4F80FA0: main (test.h:654) ==21586== ==21586== 60 bytes in 1 blocks are possibly lost in loss record 351 of 701 ==21586== at 0x7BC4C6EB: notify_alloc (heap.c:255) ==21586== by 0x7BC50F2F: RtlAllocateHeap (heap.c:1716) ==21586== by 0x50B07F4: WS2_sendto (socket.c:4545) ==21586== by 0x50B0611: WSASend (socket.c:4500) ==21586== by 0x4F6E6AF: test_send (sock.c:4234) ==21586== by 0x4F7FDB1: func_sock (sock.c:7742) ==21586== by 0x4F80BB1: run_test (test.h:584) ==21586== by 0x4F80FA0: main (test.h:654) ==21586== ==21586== 60 bytes in 1 blocks are definitely lost in loss record 352 of 701 ==21586== at 0x7BC4C6EB: notify_alloc (heap.c:255) ==21586== by 0x7BC50F2F: RtlAllocateHeap (heap.c:1716) ==21586== by 0x50B638A: WS2_recv_base (socket.c:6554) ==21586== by 0x50B61D4: WSARecv (socket.c:6522) ==21586== by 0x4F7A61B: test_completion_port (sock.c:6862) ==21586== by 0x4F7FDAC: func_sock (sock.c:7739) ==21586== by 0x4F80BB1: run_test (test.h:584) ==21586== by 0x4F80FA0: main (test.h:654) ==21586== -- 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.

1 9

[Bug 39655] New: Enemy Front crashes almost immediately after launch
by wine-bugs＠winehq.org 18 Feb '17

18 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=39655 Bug ID: 39655 Summary: Enemy Front crashes almost immediately after launch Product: Wine Version: 1.8-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com Distribution: --- Created attachment 52859 --> https://bugs.winehq.org/attachment.cgi?id=52859 enemy_front-1.8-rc1-output.log Debian Jessie amd64 in a 32-bit wineprefix (clean install) under wine 1.8-rc1. The first intro movie to play crashes after about two seconds, when my monitor is set to the native resolution of 2560x1440. Console output attached. Interestingly, if I set the monitor to 1920x1080, the cut scenes don't crash at all and I can make it all the way to the main menu (which also doesn't work, but we can make that another bug). -- 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.

1 13

[Bug 42355] New: Artifacts in GTAIV appear and disappear when driving
by wine-bugs＠winehq.org 18 Feb '17

18 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=42355 Bug ID: 42355 Summary: Artifacts in GTAIV appear and disappear when driving Product: Wine Version: 2.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: b7.10110111(a)gmail.com Distribution: --- Created attachment 57123 --> https://bugs.winehq.org/attachment.cgi?id=57123 Screenshot of the artifact When you enter a car and they try driving, you'll sometimes notice strange artifacts appear. They fade in, then sometimes persist for several frames, and then disappear. See screenshots attached. This is a regression introduced by the following commit. In this version the artifacts appear not too often — I have to play for about a minute until I notice one. In wine-2.0-235-g2dd0fb8 they appear after about 10 seconds of driving in the game. 602a23a60aaab164acb8a2767094d545172ab4cf is the first bad commit commit 602a23a60aaab164acb8a2767094d545172ab4cf Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Fri Jan 27 11:36:31 2017 +0100 wined3d: Just use glBufferSubData() in buffer_direct_upload(). It might seem like a good idea to try to use glMapBufferRange() in buffer_direct_upload(), but it really isn't. The interesting cases for glMapBufferRange() are GL_MAP_INVALIDATE_BUFFER_BIT or GL_MAP_UNSYNCHRONIZED_BIT, but the only way for those to be set here would be for the buffer to be mapped with WINED3D_MAP_DISCARD or WINED3D_MAP_NOOVERWRITE before the buffer object was created. In that case the GPU is obviously not using the buffer object, so glMapBufferRange() doesn't help. On the other hand, if the buffer is currently in use by the application and neither WINED3D_MAP_DISCARD nor WINED3D_MAP_NOOVERWRITE is set, glMapBufferRange() would need to wait for the GPU to finish using the buffer object, while glBufferSubData() may decide not to. Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 259531ef529ef96cbec7388bca99af40efaa9874 3e0b99a8b0fba782ad69ed0a8e00d2a64c363ae3 M dlls -- 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.

1 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs February 2017