wine-bugs December 2014

wine-bugs@winehq.org

1 participants
9004 discussions

[Bug 36725] New: Audible Manager crashes immediately on startup
by wine-bugs＠winehq.org 02 Oct '15

02 Oct '15

http://bugs.winehq.org/show_bug.cgi?id=36725 Bug ID: 36725 Summary: Audible Manager crashes immediately on startup Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: torsten.crass(a)eBiology.de Created attachment 48773 --> http://bugs.winehq.org/attachment.cgi?id=48773 Content of "Program Error Details" dialog after Audible Manager crashes The summary says it all ;) It is possible to install audible.com's AudibleManager using their ActiveSetupN.exe installer, but it crashes immediately after launching the actual Manager.exe. It is also not possible to directly fire up the Audible Manager after installation, it also crashes immediately. Manager.exe run fine about half a year ago, though. Best regards -- -- Torsten -- 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 36637] New: wininet/tests/http.c crashes under valgrind
by wine-bugs＠winehq.org 02 Oct '15

02 Oct '15

https://bugs.winehq.org/show_bug.cgi?id=36637 Bug ID: 36637 Summary: wininet/tests/http.c crashes under valgrind Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: wininet Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 48678 --> https://bugs.winehq.org/attachment.cgi?id=48678 valgrind log/backtrace See also bug 36004 for a crash with warn+heap. wine: Unhandled page fault on read access to 0x04760000 at address 0x7bc4d939 (thread 0033), starting debugger... Backtrace: =>0 0x7bc4d939 HEAP_CreateFreeBlock+0xb5(subheap=0x46f0014, ptr=0x4755cb8, size=0xa348) [/home/austin/wine-valgrind/dlls/ntdll/heap.c:591] in ntdll (0x04d0eaa4) 1 0x7bc4dc61 HEAP_ShrinkBlock+0x42(subheap=0x46f0014, pArena=0x4755c88, size=0x28) [/home/austin/wine-valgrind/dlls/ntdll/heap.c:694] in ntdll (0x04d0eac8) 2 0x7bc50f6e RtlAllocateHeap+0x2fb(heap=<couldn't compute location>, flags=<couldn't compute location>, size=<couldn't compute location>) [/home/austin/wine-valgrind/dlls/ntdll/heap.c:1713] in ntdll (0x04d0eb58) 3 0x04d35001 heap_alloc+0x2b(len=0x20) [/home/austin/wine-valgrind/dlls/wininet/internet.h:116] in wininet (0x04d0eb98) 4 0x04d3f383 HttpQueryInfoA+0x13a(hHttpRequest=<couldn't compute location>, dwInfoLevel=<couldn't compute location>, lpBuffer=<couldn't compute location>, lpdwBufferLength=<couldn't compute location>, lpdwIndex=<couldn't compute location>) [/home/austin/wine-valgrind/dlls/wininet/http.c:3934] in wininet (0x04d0ebf8) 5 0x0495e5b8 InternetReadFile_test+0x16ef(flags=0, test=0x49a4780) [/home/austin/wine-valgrind/dlls/wininet/tests/http.c:639] in wininet_test (0x04d0fc98) I'll attach the full log here and file separate bugs for the leaks/etc. -- 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

[Bug 36571] New: valgrind shows some invalid memory use in shell32/tests/path.c
by wine-bugs＠winehq.org 02 Oct '15

02 Oct '15

https://bugs.winehq.org/show_bug.cgi?id=36571 Bug ID: 36571 Summary: valgrind shows some invalid memory use in shell32/tests/path.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==5658== Invalid read of size 1 ==5658== at 0x402EB35: bcmp (vg_replace_strmem.c:965) ==5658== by 0x4ED0EED: is_knownfolder (shellpath.c:3790) ==5658== by 0x4ED1052: foldermanager_GetFolder (shellpath.c:3819) ==5658== by 0x4CDAB24: test_knownFolders (shobjidl.h:16490) ==5658== by 0x4CDE323: func_shellpath (shellpath.c:2660) ==5658== by 0x4D14454: run_test (test.h:584) ==5658== by 0x4D14843: main (test.h:654) ==5658== Address 0x49cc458 is 0 bytes inside a block of size 1,664 free'd ==5658== at 0x7BC4C72C: notify_free (heap.c:263) ==5658== by 0x7BC51071: RtlFreeHeap (heap.c:1762) ==5658== by 0x5B02C4E: IMalloc_fnFree (ifs.c:265) ==5658== by 0x5B0311D: CoTaskMemFree (objidl.h:1242) ==5658== by 0x4CDA857: test_knownFolders (shellpath.c:2164) ==5658== by 0x4CDE323: func_shellpath (shellpath.c:2660) ==5658== by 0x4D14454: run_test (test.h:584) ==5658== by 0x4D14843: main (test.h:654) ==5658== ==5658== Invalid read of size 1 ==5658== at 0x402EB35: bcmp (vg_replace_strmem.c:965) ==5658== by 0x4ED0EED: is_knownfolder (shellpath.c:3790) ==5658== by 0x4ED1052: foldermanager_GetFolder (shellpath.c:3819) ==5658== by 0x4CDAFDC: test_knownFolders (shobjidl.h:16490) ==5658== by 0x4CDE323: func_shellpath (shellpath.c:2660) ==5658== by 0x4D14454: run_test (test.h:584) ==5658== by 0x4D14843: main (test.h:654) ==5658== Address 0x49cc458 is 0 bytes inside a block of size 1,664 free'd ==5658== at 0x7BC4C72C: notify_free (heap.c:263) ==5658== by 0x7BC51071: RtlFreeHeap (heap.c:1762) ==5658== by 0x5B02C4E: IMalloc_fnFree (ifs.c:265) ==5658== by 0x5B0311D: CoTaskMemFree (objidl.h:1242) ==5658== by 0x4CDA857: test_knownFolders (shellpath.c:2164) ==5658== by 0x4CDE323: func_shellpath (shellpath.c:2660) ==5658== by 0x4D14454: run_test (test.h:584) ==5658== by 0x4D14843: main (test.h:654) ==5658== ==5658== Invalid free() / delete / delete[] / realloc() ==5658== at 0x7BC4C72C: notify_free (heap.c:263) ==5658== by 0x7BC51071: RtlFreeHeap (heap.c:1762) ==5658== by 0x4ED0B05: foldermanager_Release (shellpath.c:3710) ==5658== by 0x4CDD44E: test_knownFolders (shobjidl.h:16477) ==5658== by 0x4CDE323: func_shellpath (shellpath.c:2660) ==5658== by 0x4D14454: run_test (test.h:584) ==5658== by 0x4D14843: main (test.h:654) ==5658== Address 0x49cc458 is 0 bytes inside a block of size 1,664 free'd ==5658== at 0x7BC4C72C: notify_free (heap.c:263) ==5658== by 0x7BC51071: RtlFreeHeap (heap.c:1762) ==5658== by 0x5B02C4E: IMalloc_fnFree (ifs.c:265) ==5658== by 0x5B0311D: CoTaskMemFree (objidl.h:1242) ==5658== by 0x4CDA857: test_knownFolders (shellpath.c:2164) ==5658== by 0x4CDE323: func_shellpath (shellpath.c:2660) ==5658== by 0x4D14454: run_test (test.h:584) ==5658== by 0x4D14843: main (test.h:654) ==5658== -- 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 35553] New: Warhammer 40,000: Dawn of War II: does not start, crypt:CertCreateContext dwFlags not implemented
by wine-bugs＠winehq.org 02 Oct '15

02 Oct '15

http://bugs.winehq.org/show_bug.cgi?id=35553 Bug ID: 35553 Summary: Warhammer 40,000: Dawn of War II: does not start, crypt:CertCreateContext dwFlags not implemented Product: Wine Version: 1.7.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com Classification: Unclassified Created attachment 47474 --> http://bugs.winehq.org/attachment.cgi?id=47474 DOW2.EXE, Wine 1.7.12, +loaddll,+crypt I'm trying to get Dawn of War 2 working. There appear to be two obvious issues preventing it running. The first is worked around by using native wintrust and msasn1 DLLs, and restoring backups of content.cat before every program launch (which is Bug 35452). The second issue (exclusive to Dawn of War 2) is what I'm reporting in this ticket. The first bug applies to both Dawn of War 2 and Dawn of War 2: Retribution, but as stated has a work-around. However attempting the same work-around on plain Dawn of War 2 causes us to run into the second problem: trace:crypt:CertCreateContext (0x3, 0x10001, 0xce10000, 5861, 0x00000005, (nil)) fixme:crypt:CertCreateContext dwFlags 0x00000005 not handled fixme:advapi:RegisterTraceGuidsA (0x1bfce70, (nil), {d5b9ac76-d546-4891-bb8c-bfd865e5c7d5}, 3, 0x2142b00, (null), (null), 0x214f850): stub More history attached, in case you need it. Nothing further is printed to the console, but the following command is still running: C:\Program Files\Steam\steamapps\common\Dawn of War 2\dow2.exe -logs It's consuming 100% CPU, and will do so forever until it is manually killed. I have not been successful in any attempt at a work-around for this bug to date. -- 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 32257] New: Castle Story Prototype v0.0.2 crashes when starting new game
by wine-bugs＠winehq.org 30 Sep '15

30 Sep '15

http://bugs.winehq.org/show_bug.cgi?id=32257 Bug #: 32257 Summary: Castle Story Prototype v0.0.2 crashes when starting new game Product: Wine Version: 1.5.17 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: Anxiety35(a)gmail.com Classification: Unclassified Created attachment 42567 --> http://bugs.winehq.org/attachment.cgi?id=42567 Backtrace from castle Story v0.0.2 crash Castle Story Prototype with update 0.0.2 crashes right after clicking a map to start a new game. The icons load on the screen and then it crashes with a page fault. It crashes regardless of the resolution, window, and graphics quality settings. Attached is the crash backtrace. -- 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.

1 9

[Bug 36641] New: valgrind shows an anvalid read in wininet/tests/http.c
by wine-bugs＠winehq.org 30 Sep '15

30 Sep '15

https://bugs.winehq.org/show_bug.cgi?id=36641 Bug ID: 36641 Summary: valgrind shows an anvalid read in wininet/tests/http.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: wininet Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Depends on: 36637 ==32063== Invalid read of size 2 ==32063== at 0x4D3E66E: HTTP_HttpQueryInfoW (http.c:3596) ==32063== by 0x4D3F1B0: HttpQueryInfoW (http.c:3883) ==32063== by 0x4D3F402: HttpQueryInfoA (http.c:3944) ==32063== by 0x495E46B: InternetReadFile_test (http.c:629) ==32063== by 0x497D687: func_http (http.c:5329) ==32063== by 0x4994B90: run_test (test.h:584) ==32063== by 0x4994F7F: main (test.h:654) ==32063== Address 0x471e21e is 0 bytes after a block of size 822 alloc'd ==32063== at 0x7BC4C75D: notify_alloc (heap.c:255) ==32063== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716) ==32063== by 0x4D35000: heap_alloc (internet.h:116) ==32063== by 0x4D3FD2F: HTTP_build_req (http.c:4170) ==32063== by 0x4D36905: build_response_header (http.c:732) ==32063== by 0x4D3E5A4: HTTP_HttpQueryInfoW (http.c:3576) ==32063== by 0x4D3F1B0: HttpQueryInfoW (http.c:3883) ==32063== by 0x4D3F402: HttpQueryInfoA (http.c:3944) ==32063== by 0x495E46B: InternetReadFile_test (http.c:629) ==32063== by 0x497D687: func_http (http.c:5329) ==32063== by 0x4994B90: run_test (test.h:584) ==32063== by 0x4994F7F: main (test.h:654) ==32063== ==32063== Invalid read of size 4 ==32063== at 0x7BC4D939: HEAP_CreateFreeBlock (heap.c:591) ==32063== by 0x7BC4DC60: HEAP_ShrinkBlock (heap.c:694) ==32063== by 0x7BC50F6D: RtlAllocateHeap (heap.c:1713) ==32063== by 0x4D35000: heap_alloc (internet.h:116) ==32063== by 0x4D3F382: HttpQueryInfoA (http.c:3934) ==32063== by 0x495E5B7: InternetReadFile_test (http.c:639) ==32063== by 0x497D6B3: func_http (http.c:5331) ==32063== by 0x4994B90: run_test (test.h:584) ==32063== by 0x4994F7F: main (test.h:654) ==32063== Address 0x4760000 is not stack'd, malloc'd or (recently) free'd ==32063== ==32063== Thread 4: ==32063== Invalid write of size 4 ==32063== at 0x7BC93356: NtQuerySystemTime (time.c:467) ==32063== by 0x7BC8A8FB: NtDelayExecution (sync.c:940) ==32063== by 0x7B876351: SleepEx (sync.c:108) ==32063== by 0x7B87630B: Sleep (sync.c:97) ==32063== by 0x4D358A2: collect_connections_proc (http.c:358) ==32063== by 0x7BC87137: ??? (signal_i386.c:2571) ==32063== by 0x7BC87180: call_thread_func (signal_i386.c:2630) ==32063== by 0x7BC87115: ??? (signal_i386.c:2571) ==32063== by 0x7BC8E560: start_thread (thread.c:428) ==32063== by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so) ==32063== by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so) ==32063== Address 0x658e8bc is on thread 1's stack ==32063== ==32063== Invalid read of size 4 ==32063== at 0x7BC1EB70: __x86.get_pc_thunk.bx (in /home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so) ==32063== by 0x7BC8A8FB: NtDelayExecution (sync.c:940) ==32063== by 0x7B876351: SleepEx (sync.c:108) ==32063== by 0x7B87630B: Sleep (sync.c:97) ==32063== by 0x4D358A2: collect_connections_proc (http.c:358) ==32063== by 0x7BC87137: ??? (signal_i386.c:2571) ==32063== by 0x7BC87180: call_thread_func (signal_i386.c:2630) ==32063== by 0x7BC87115: ??? (signal_i386.c:2571) ==32063== by 0x7BC8E560: start_thread (thread.c:428) ==32063== by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so) ==32063== by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so) ==32063== Address 0x658e8bc is on thread 1's stack ==32063== etc. -- 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 36639] New: gettimeofday() points to unaddressable memory in wininet/tests/http.c (valgrind)
by wine-bugs＠winehq.org 30 Sep '15

30 Sep '15

https://bugs.winehq.org/show_bug.cgi?id=36639 Bug ID: 36639 Summary: gettimeofday() points to unaddressable memory in wininet/tests/http.c (valgrind) Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: wininet Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Depends on: 36637 ==32063== Syscall param gettimeofday(tv) points to unaddressable byte(s) ==32063== at 0x4E90EBD6: gettimeofday (in /usr/lib/libc-2.18.so) ==32063== by 0x7BC93374: NtQuerySystemTime (time.c:470) ==32063== by 0x7BC8A8FB: NtDelayExecution (sync.c:940) ==32063== by 0x7B876351: SleepEx (sync.c:108) ==32063== by 0x7B87630B: Sleep (sync.c:97) ==32063== by 0x4D358A2: collect_connections_proc (http.c:358) ==32063== by 0x7BC87137: ??? (signal_i386.c:2571) ==32063== by 0x7BC87180: call_thread_func (signal_i386.c:2630) ==32063== by 0x7BC87115: ??? (signal_i386.c:2571) ==32063== by 0x7BC8E560: start_thread (thread.c:428) ==32063== by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so) ==32063== by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so) ==32063== Address 0x658e8d8 is on thread 1's stack ==32063== -- 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 4

[Bug 36200] New: crypt32/tests/msg.c test crashes under valgrind
by wine-bugs＠winehq.org 30 Sep '15

30 Sep '15

https://bugs.winehq.org/show_bug.cgi?id=36200 Bug ID: 36200 Summary: crypt32/tests/msg.c test crashes under valgrind 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 Created attachment 48321 --> https://bugs.winehq.org/attachment.cgi?id=48321 terminal output/backtrace Backtrace: =>0 0x00000000 (0x04befba8) 1 0x04c78a0f CryptMsgUpdate+0xa8(hCryptMsg=0x46f24c8, pbData="", cbData=0x4, fFinal=0) [/home/austin/wine-valgrind-known/dlls/crypt32/msg.c:3601] in crypt32 (0x04befbe8) 2 0x0498d49c test_data_msg_update+0x768() [/home/austin/wine-valgrind-known/dlls/crypt32/tests/msg.c:460] in crypt32_test (0x04befc98) 3 0x0498e526 test_data_msg+0xf() [/home/austin/wine-valgrind-known/dlls/crypt32/tests/msg.c:718] in crypt32_test (0x04befca8) 4 0x0499ca90 func_msg+0xc5() [/home/austin/wine-valgrind-known/dlls/crypt32/tests/msg.c:3780] in crypt32_test (0x04befcc8) -- 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 2

[Bug 32547] New: ShowMiiWads: Crashes when installing WADs
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

http://bugs.winehq.org/show_bug.cgi?id=32547 Bug #: 32547 Summary: ShowMiiWads: Crashes when installing WADs Product: Wine Version: 1.5.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: d.schwimer(a)hotmail.com Classification: Unclassified Created attachment 42952 --> http://bugs.winehq.org/attachment.cgi?id=42952 Wine's output following the crash Using a program called ShowMiiWads v1.4: http://wiibrew.org/wiki/ShowMiiWads The program is a sort of utility used to inject WAD files into a NAND backup of a Wii system. Steps to produce issue: 1. Created a "Common Key.bin" file using Tools > Create Common Key and typin '45e'. 2. Selected Options > Change NAND Backup Path, and navigated to the desired folder. 3. Selected View > ShowMiiNand. 4. Right-clicked an item from the list, selected "Install", then "File", then selected a WAD file. 5. Program crashes with attached output. -- 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.

1 5

[Bug 20354] New: Sony Vegas has encountered an Error: 'WIA-Manager could not be initialized'
by wine-bugs＠winehq.org 29 Sep '15

29 Sep '15

http://bugs.winehq.org/show_bug.cgi?id=20354 Summary: Sony Vegas has encountered an Error: 'WIA-Manager could not be initialized' Product: Wine Version: 1.1.31 Platform: PC-x86-64 URL: http://www.sonycreativesoftware.com/vegaspro OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winecreations(a)trashmail.net Created an attachment (id=24107) --> (http://bugs.winehq.org/attachment.cgi?id=24107) Console Output when starting the installed and registered program I am a professional video editor for one of the large studios around. Lately switching to Linux have 'forced' me to use the awesome WINE in order to install Sony Vegas Pro 9. Unfortunately WINE does absolutely not care about the Windows Image Acquisition (WIA). Ths, I only can say that Sony Vegas Pro 9 install absolutely without any errors, and even registration works fine. Right after the start of the program the loading window shows up and is replaced immediately with an error notification: "Sony Vegas has encountered an Error: 'WIA-Manager could not be initialized'". I figured to talk to the people on IRC and post an error log, but even they say that WINE does not care the slightest about the Windows Image Acquisition. I am actually looking forward to see WIA supported as fast as possible. I´ve been talking directly to Sony developers in their forum (complete Thread in German). If you are interested seing the output feel free to visit: http://www.vegasforum.de/sony-vegas-pro-t1878.html THANK YOU for the work you do every day to improve WINE. It is much appreciated. -- 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.

1 38

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 December 2014