September 2015 - Wine-Bugs - list.winehq.org

[Bug 32257] New: Castle Story Prototype v0.0.2 crashes when starting new game
by wine-bugs＠winehq.org Sept. 30, 2015

Sept. 30, 2015

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 7520] Lotus Notes display some fonts as normal instead of bold or italic
by wine-bugs＠winehq.org Sept. 30, 2015

Sept. 30, 2015

https://bugs.winehq.org/show_bug.cgi?id=7520 --- Comment #33 from Sagawa <sagawa.aki+winebugs(a)gmail.com> --- Ah, my patch is for pure bitmap fonts by adding FT_GLYPH_FORMAT_BITMAP case in synthesize_bold_glyph. Possibly, I thought it wasn't useful nowadays or encountered difficulties. For embedded bitmaps, it seems to be off-topic. So, I'll reply to your mail in wine-devel. -- 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 0

[Bug 7520] Lotus Notes display some fonts as normal instead of bold or italic
by wine-bugs＠winehq.org Sept. 30, 2015

Sept. 30, 2015

https://bugs.winehq.org/show_bug.cgi?id=7520 --- Comment #32 from Nikolay Sivov <bunglehead(a)gmail.com> --- Sure, I didn't mean pure bitmap fonts by the way, but rather scalable fonts with embedded bitmaps for specific font sizes. -- 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 0

[Bug 7520] Lotus Notes display some fonts as normal instead of bold or italic
by wine-bugs＠winehq.org Sept. 30, 2015

Sept. 30, 2015

https://bugs.winehq.org/show_bug.cgi?id=7520 --- Comment #31 from Sagawa <sagawa.aki+winebugs(a)gmail.com> --- Hi, Nikolay. I have some patchset for bitmap font case at that time, but I forgot to commit them. I'll send patch set. Could you review them? Thanks in advance. -- 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 0

[Bug 7520] Lotus Notes display some fonts as normal instead of bold or italic
by wine-bugs＠winehq.org Sept. 30, 2015

Sept. 30, 2015

https://bugs.winehq.org/show_bug.cgi?id=7520 --- Comment #30 from Nikolay Sivov <bunglehead(a)gmail.com> --- As a follow up on this - https://www.winehq.org/pipermail/wine-patches/2015-September/142625.html. The way emboldening works now in Wine seems questionable to me, especially in a way that we ignore glyph bitmaps entirely and use outlines. -- 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 0

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

Sept. 30, 2015

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 Sept. 30, 2015

Sept. 30, 2015

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 Sept. 30, 2015

Sept. 30, 2015

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 39359] New: No msi progress dialog
by wine-bugs＠winehq.org Sept. 30, 2015

Sept. 30, 2015

https://bugs.winehq.org/show_bug.cgi?id=39359 Bug ID: 39359 Summary: No msi progress dialog Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: computerwhiz02(a)hotmail.com Distribution: --- Created attachment 52455 --> https://bugs.winehq.org/attachment.cgi?id=52455 windows dialog When I install WINE Mono, I don't get a dialog with a progress bar that displays text such as Preparing to install, etc. WINE's implementation seems to be missing this really useful feature. -- 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 32547] New: ShowMiiWads: Crashes when installing WADs
by wine-bugs＠winehq.org Sept. 29, 2015

Sept. 29, 2015

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