wine-bugs December 2014

wine-bugs@winehq.org

1 participants
9006 discussions

[Bug 33719] New: comctl32:propsheet custom window proc test failure
by wine-bugs＠winehq.org 04 Jan '19

04 Jan '19

http://bugs.winehq.org/show_bug.cgi?id=33719 Bug #: 33719 Summary: comctl32:propsheet custom window proc test failure Product: Wine Version: 1.5.19 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified A number of VMs report one of these two related test failures: Elevated privileges (or pre-Vista): propsheet.c:746: Test failed: property sheet with custom window proc: the msg 0x001c was expected, but got msg 0x0047 instead or not elevated privileges: propsheet.c:746: Test failed: property sheet with custom window proc: the msg 0x0046 was expected, but got msg 0x0210 instead They have been seen on the following systems: comctl32 5.81.4968.2500 Windows 2000 Professional SP4 + IE55 (rare ~1/50) comctl32 5.82.3790.3959 Windows 2003 Enterprise Server SP2 + IE8 (rare ~1/50) comctl32 5.82.6002.18305 Windows Vista Home Premium SP2+IE9 comctl32 5.82.7601.17514 Windows 7 Ultimate SP1 64-bit (+IE8) (32-bit tests) comctl32 5.82.7601.17514 Windows 7 Ultimate SP1 64-bit + IE9 (32-bit tests) comctl32 5.82.7601.17514 Windows 7 SP1 (not one of mine) comctl32 5.82.9200.16384 Windows 8 -- 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 12

[Bug 26262] New: No video output in game
by wine-bugs＠winehq.org 01 Jan '19

01 Jan '19

http://bugs.winehq.org/show_bug.cgi?id=26262 Summary: No video output in game Product: Wine Version: 1.3.14 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: torgeriedel(a)gmx.de When trying to play Commandos - Behind Enemy lines, there is no video output. Sound is working. -- 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 25

[Bug 33368] New: WM_DEADCHAR events not sent
by wine-bugs＠winehq.org 31 Dec '18

31 Dec '18

http://bugs.winehq.org/show_bug.cgi?id=33368 Bug #: 33368 Summary: WM_DEADCHAR events not sent Product: Wine Version: 1.5.27 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: sloonz(a)gmail.com Classification: Unclassified Created attachment 44152 --> http://bugs.winehq.org/attachment.cgi?id=44152 Keyboard traces in three different scenarios (Windows, Wine, Wine+patch) XFilterEvent() returns true for events of dead keys, so they are not processed by wine. However, that prevents sending a WM_DEADCHAR event to the application, as it works on Windows. For example, in order to emit a "ê" character in a french keyboard layout, I first have to press ^ (which is a dead key) and then e. Under Windows, this leads to the following sequence of events : KEYDOWN: dead_circumflex DEADCHAR: dead_circumflex KEYDOWN: e CHAR: ê KEYUP: e KEYUP: dead_circumflex Under wine I have only those events : KEYUP: dead_circumflex KEYDOWN: e CHAR: ê Attached patch fixes most of that, with it I get : KEYDOWN: dead_circumflex DEADCHAR: dead_circumflex UP: dead_circumflex KEYDOWN: e CHAR: ê KEYUP: e Note that it’s still slighty different from Windows (KEYUP for dead key is third message on Wine, whereas it is before the last one on Windows), but I don’t see a clean fix for this issue. As for the traces in attachment, contains three traces. The first one is from Spy++ on Windows ; the second is the relevant output of WINEDEBUG=+msg notepad for unpatched wine ; the third one for patched wine. -- 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 6

[Bug 36095] New: valgrind errors in loader when loading a dll
by wine-bugs＠winehq.org 31 Dec '18

31 Dec '18

https://bugs.winehq.org/show_bug.cgi?id=36095 Bug ID: 36095 Summary: valgrind errors in loader when loading a dll Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: major Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Noticed this in most tests, there are at least 3 places. 1: ==11164== 26 bytes in 1 blocks are definitely lost in loss record 57 of 244 ==11164== at 0x7BC4C735: notify_alloc (heap.c:255) ==11164== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11164== by 0x7BC758B6: RtlCreateUnicodeString (rtlstr.c:281) ==11164== by 0x7BC54CF3: alloc_module (loader.c:919) ==11164== by 0x7BC566CB: load_builtin_callback (loader.c:1519) ==11164== by 0x40192DE: __wine_dll_register (loader.c:517) ==11164== by 0x7B88A18B: __wine_spec_init (init.c:35) ==11164== by 0x4E850459: call_init.part.0 (in /usr/lib/ld-2.18.so) ==11164== by 0x4E850593: _dl_init (in /usr/lib/ld-2.18.so) ==11164== by 0x4E854953: dl_open_worker (in /usr/lib/ld-2.18.so) ==11164== by 0x4E850329: _dl_catch_error (in /usr/lib/ld-2.18.so) ==11164== by 0x4E854013: _dl_open (in /usr/lib/ld-2.18.so) ==11164== by 0x4EA25CBB: dlopen_doit (in /usr/lib/libdl-2.18.so) ==11164== by 0x4E850329: _dl_catch_error (in /usr/lib/ld-2.18.so) ==11164== by 0x4EA263CB: _dlerror_run (in /usr/lib/libdl-2.18.so) ==11164== by 0x4EA25D70: dlopen@@GLIBC_2.1 (in /usr/lib/libdl-2.18.so) ==11164== by 0x4019898: wine_dlopen (loader.c:1029) ==11164== by 0x4018C06: dlopen_dll (loader.c:295) ==11164== by 0x4019532: wine_dll_load (loader.c:581) ==11164== by 0x7BC57199: load_builtin_dll (loader.c:1732) ==11164== 2: ==11164== 32 bytes in 1 blocks are possibly lost in loss record 65 of 244 ==11164== at 0x7BC4C735: notify_alloc (heap.c:255) ==11164== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11164== by 0x7BC76348: RtlAnsiStringToUnicodeString (rtlstr.c:689) ==11164== by 0x7BC7595F: RtlCreateUnicodeStringFromAsciiz (rtlstr.c:302) ==11164== by 0x7BC5B407: init_load_order (loadorder.c:252) ==11164== by 0x7BC5B9FB: get_load_order (loadorder.c:440) ==11164== by 0x7BC58099: load_dll (loader.c:2045) ==11164== by 0x7BC585B7: LdrLoadDll (loader.c:2125) ==11164== by 0x7B85A79A: load_library (module.c:933) ==11164== by 0x7B85A908: LoadLibraryExW (module.c:990) ==11164== by 0x7B8649B8: __wine_kernel_init (process.c:1230) ==11164== by 0x7BC5ACA9: __wine_process_init (loader.c:3103) ==11164== by 0x4019864: wine_init (loader.c:952) ==11164== by 0x7BF011AD: main (main.c:237) ==11164== 3: ==11165== 20 bytes in 1 blocks are definitely lost in loss record 14 of 58 ==11165== at 0x7BC4C735: notify_alloc (heap.c:255) ==11165== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11165== by 0x7BC758B6: RtlCreateUnicodeString (rtlstr.c:281) ==11165== by 0x7BC54CF3: alloc_module (loader.c:919) ==11165== by 0x7BC566CB: load_builtin_callback (loader.c:1519) ==11165== by 0x40193D9: wine_dll_set_callback (loader.c:548) ==11165== by 0x7BC5ABA2: __wine_process_init (loader.c:3086) ==11165== by 0x4019864: wine_init (loader.c:952) ==11165== by 0x7BF011AD: main (main.c:237) ==11165== 4: ==11194== 32 bytes in 1 blocks are possibly lost in loss record 66 of 248 ==11194== at 0x7BC4C735: notify_alloc (heap.c:255) ==11194== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11194== by 0x7BC76348: RtlAnsiStringToUnicodeString (rtlstr.c:689) ==11194== by 0x7BC7595F: RtlCreateUnicodeStringFromAsciiz (rtlstr.c:302) ==11194== by 0x7BC5B407: init_load_order (loadorder.c:252) ==11194== by 0x7BC5B9FB: get_load_order (loadorder.c:440) ==11194== by 0x7BC58099: load_dll (loader.c:2045) ==11194== by 0x7BC585B7: LdrLoadDll (loader.c:2125) ==11194== by 0x7B85A79A: load_library (module.c:933) ==11194== by 0x7B85A908: LoadLibraryExW (module.c:990) ==11194== by 0x7B8649B8: __wine_kernel_init (process.c:1230) ==11194== by 0x7BC5ACA9: __wine_process_init (loader.c:3103) ==11194== by 0x4019864: wine_init (loader.c:952) ==11194== by 0x7BF011AD: main (main.c:237) ==11194== (tested running advapi32/security.c) wine-1.7.17-92-ge2bf516 -- 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 17488] New: Animation issues in 4Story
by wine-bugs＠winehq.org 30 Dec '18

30 Dec '18

http://bugs.winehq.org/show_bug.cgi?id=17488 Summary: Animation issues in 4Story Product: Wine Version: 1.1.15 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: killzenator(a)gmail.com Created an attachment (id=19581) --> (http://bugs.winehq.org/attachment.cgi?id=19581) Output of "wine 4Story.exe >> log.txt 2>&1" In 4Story none of the character/npcs have animations, weapons move up and down like their supposed to when you walk, characters stay the same. -- 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 27

[Bug 35603] New: Wine64 build produces extra warning in setupapi comparing to Wine32 build
by wine-bugs＠winehq.org 28 Dec '18

28 Dec '18

http://bugs.winehq.org/show_bug.cgi?id=35603 Bug ID: 35603 Summary: Wine64 build produces extra warning in setupapi comparing to Wine32 build Product: Wine Version: 1.7.12 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: wylda(a)volny.cz Classification: Unclassified Created attachment 47552 --> http://bugs.winehq.org/attachment.cgi?id=47552 64bit build log Similarly to bug 35602, but this time for setupapi: * warning: cast from pointer to integer of different size -- 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 32251] New: ... i dont know
by wine-bugs＠winehq.org 27 Dec '18

27 Dec '18

http://bugs.winehq.org/show_bug.cgi?id=32251 Bug #: 32251 Summary: ... i dont know Product: WineHQ Apps Database Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: appdb-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dandazadiego(a)gmail.com Classification: Unclassified >Runes of magic cant run. I followed the instructions you have given and I'll get up in the middle of the game and update locks. how do I? -- 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 3

[Bug 24963] New: Okad2: Unhandled page fault at address 0x00007f8a during startup
by wine-bugs＠winehq.org 26 Dec '18

26 Dec '18

http://bugs.winehq.org/show_bug.cgi?id=24963 Summary: Okad2: Unhandled page fault at address 0x00007f8a during startup Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: pandolfo(a)gis.net Created an attachment (id=31617) --> (http://bugs.winehq.org/attachment.cgi?id=31617) a description of the page fault plus an annotated backtrace During program startup, Okad2-xx-pd (xx = version) generates an unhandled page fault when loading an icon. The page fault is caused by CreateFileW as it processes the name of the file from the parameter list. The name pointer is 0x00007f8a, which is an address in an unmapped page. This value is also an index into Windows resources, selecting the hourglass icon. What has happened is that the application was attempting to load the hourglass icon and passed in BOTH the Windows resource index and a flag indicating LOADFROMFILE. Wine attempted to load-from-file and looked for the file name through the "name" parameter (0x00007f8a) generating the page fault. Native Windows appears to give the value of the "name" pointer precedence and determines that the "name" parameter is actually a resource number; hence it does not page fault and runs Okad2 normally. Wine *DOES* check the "name" parameter to see if it is a resource index, but several subroutine calls later it forgets this fact and branches based on the LOADFROMFILE bit. The backtrace has been annotated to provide both a description and source lines involved in the decision. This behavior was found in the latest version of Wine for Debian (.1.42) and in a MacOS X version. -- 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 12

[Bug 36587] New: valgrind shows uninitialized memory use in user32/tests/winstation.c
by wine-bugs＠winehq.org 22 Dec '18

22 Dec '18

https://bugs.winehq.org/show_bug.cgi?id=36587 Bug ID: 36587 Summary: valgrind shows uninitialized memory use in user32/tests/winstation.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ../../../tools/runtest -q -P wine -T ../../.. -M user32.dll -p user32_test.exe.so winstation && touch winstation.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 ==25156== Syscall param write(buf) points to uninitialised byte(s) ==25156== at 0x4226CF3: __write_nocancel (syscall-template.S:81) ==25156== by 0x7BC7FD72: send_request (server.c:198) ==25156== by 0x7BC7FF91: wine_server_call (server.c:294) ==25156== by 0x519D2EE: send_hardware_message (message.c:3331) ==25156== by 0x5173BEB: SendInput (input.c:185) ==25156== by 0x4D9FB49: test_inputdesktop (winstation.c:530) ==25156== by 0x4DA2430: func_winstation (winstation.c:939) ==25156== by 0x4DA3978: run_test (test.h:584) ==25156== by 0x4DA3D67: main (test.h:654) ==25156== Address 0x510f6a8 is on thread 1's stack ==25156== Uninitialised value was created by a stack allocation ==25156== at 0x4D9F748: test_inputdesktop (winstation.c:492) ==25156== -- 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 36636] New: valgrind shows an uninitialized write in shell32/tests/appbar.c
by wine-bugs＠winehq.org 22 Dec '18

22 Dec '18

https://bugs.winehq.org/show_bug.cgi?id=36636 Bug ID: 36636 Summary: valgrind shows an uninitialized write in shell32/tests/appbar.c Product: Wine Version: 1.7.19 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 ==20270== Syscall param writev(vector[...]) points to uninitialised byte(s) ==20270== at 0x4E952886: writev (in /usr/lib/libc-2.18.so) ==20270== by 0x7BC7FE6F: send_request (server.c:213) ==20270== by 0x7BC80001: wine_server_call (server.c:294) ==20270== by 0x5254AF8: put_message_in_queue (message.c:3141) ==20270== by 0x5254EA9: send_inter_thread_message (message.c:3209) ==20270== by 0x525518A: send_message (message.c:3277) ==20270== by 0x52555D1: SendMessageTimeoutW (message.c:3414) ==20270== by 0x4D221BC: SHAppBarMessage (appbar.c:142) ==20270== by 0x4A59513: test_setpos (appbar.c:222) ==20270== by 0x4A5ABF9: func_appbar (appbar.c:442) ==20270== by 0x4AB44E4: run_test (test.h:584) ==20270== by 0x4AB48D3: main (test.h:654) ==20270== Address 0x4cdfb20 is on thread 1's stack ==20270== Uninitialised value was created by a stack allocation ==20270== at 0x4A5940F: test_setpos (appbar.c:203) ==20270== -- 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 12

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