May 2014 - Wine-Bugs - list.winehq.org

[Bug 29273] New: delphi application crash at start when windows are created on x86-64 system only
by wine-bugs＠winehq.org June 10, 2014

June 10, 2014

http://bugs.winehq.org/show_bug.cgi?id=29273 Bug #: 29273 Summary: delphi application crash at start when windows are created on x86-64 system only Product: Wine Version: 1.2.2 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: mzens(a)gmx.de Classification: Unclassified Created attachment 37858 --> http://bugs.winehq.org/attachment.cgi?id=37858 executable The 32bit application crashes somewhere in the delphi initialization code at start-up in versions 1.2.2 and 1.3.34. This happens only on the Ubuntu 10.04 x86-64 system. On a x86-32 machine it runs fine in version 1.2.2 . -- 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 10

[Bug 36474] New: Wine doesn't respect the systemd attach to seat
by wine-bugs＠winehq.org June 5, 2014

June 5, 2014

http://bugs.winehq.org/show_bug.cgi?id=36474 Bug ID: 36474 Summary: Wine doesn't respect the systemd attach to seat Product: Wine Version: 1.7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: debian(a)jkfloris.demon.nl I have a working systemd multiseat setup. seat0 has a keyboard and a mouse attached. Seat1 has also two usb joysticks. But when I run `wine control` on seat0 the game controller menu shows the joysticks from seat1 and the buttons and axis are working. -- 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 36238] New: comctl32/tests/propsheet.c fails under valgrind
by wine-bugs＠winehq.org June 5, 2014

June 5, 2014

https://bugs.winehq.org/show_bug.cgi?id=36238 Bug ID: 36238 Summary: comctl32/tests/propsheet.c fails under valgrind Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ../../../tools/runtest -q -P wine -T ../../.. -M comctl32.dll -p comctl32_test.exe.so propsheet && touch propsheet.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 propsheet.c:548: Test failed: The Add button has not been pressed! make: *** [propsheet.ok] Error 1 see bug 36236 for a leak in that file, and bug 33719 for failing on some windows vms. -- 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 20545] New: memory leak in MMDRV_Init on exit?
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

http://bugs.winehq.org/show_bug.cgi?id=20545 Summary: memory leak in MMDRV_Init on exit? Product: Wine Version: 1.1.32 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: winmm&mci AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com On several Chromium tests (having nothing to do with multimedia?), valgrind is reporting a leak in winmm: 56 bytes in 1 blocks are possibly lost in loss record 464 of 1,033 at notify_alloc (heap.c:214) by RtlAllocateHeap (heap.c:1421) by MMDRV_InitPerType (lolvldrv.c:419) by MMDRV_Install (lolvldrv.c:510) by MMDRV_Init (lolvldrv.c:561) by DllMain (winmm.c:184) by __wine_spec_dll_entry (dll_entry.c:40) by ??? (in /home/dank/wine-git/dlls/ntdll/ntdll.dll.so) by MODULE_InitDLL (loader.c:982) by process_attach (loader.c:1071) by process_attach (loader.c:1063) by attach_process_dlls (loader.c:2440) This doesn't happen terribly often, is there something that occasionally prevents freeing on unload? -- 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 36558] New: valgrind shows a definite leak in comctl32/tests/treeview.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36558 Bug ID: 36558 Summary: valgrind shows a definite leak in comctl32/tests/treeview.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==26061== 140 bytes in 1 blocks are definitely lost in loss record 620 of 921 ==26061== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==26061== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==26061== by 0x4FE3841: ImageListImpl_CreateInstance (imagelist.c:3697) ==26061== by 0x4FDC1EA: ImageList_Create (imagelist.c:772) ==26061== by 0x505A37F: TREEVIEW_InitCheckboxes (treeview.c:2954) ==26061== by 0x505A6A5: TREEVIEW_Paint (treeview.c:3013) ==26061== by 0x5060D32: TREEVIEW_WindowProc (treeview.c:5817) ==26061== by 0x538D4F5: ??? (winproc.c:173) ==26061== by 0x538D66A: call_window_proc (winproc.c:244) ==26061== by 0x538E858: WINPROC_CallProcAtoW (winproc.c:603) ==26061== by 0x538FA49: CallWindowProcA (winproc.c:961) ==26061== by 0x4D435DF: TreeviewWndProc (treeview.c:315) ==26061== by 0x538D4F5: ??? (winproc.c:173) ==26061== by 0x538D66A: call_window_proc (winproc.c:244) ==26061== by 0x538F8B9: WINPROC_call_window (winproc.c:909) ==26061== by 0x5350859: DispatchMessageA (message.c:3948) ==26061== by 0x4D4B261: test_TVS_CHECKBOXES (treeview.c:1943) ==26061== by 0x4D4C651: func_treeview (treeview.c:2228) ==26061== by 0x4D51DB9: run_test (test.h:584) ==26061== by 0x4D521A8: main (test.h:654) ==26061== -- 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 36582] New: valgrind shows a definite leak in user32/tests/dialog.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36582 Bug ID: 36582 Summary: valgrind shows a definite leak in user32/tests/dialog.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 ==26259== 28 bytes in 1 blocks are definitely lost in loss record 237 of 760 ==26259== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==26259== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==26259== by 0x5154EB8: DIALOG_get_info (defdlg.c:342) ==26259== by 0x5154F60: DefDlgProcA (defdlg.c:369) ==26259== by 0x4CCFD69: test_WM_NEXTDLGCTL (dialog.c:606) ==26259== by 0x4CD3173: func_dialog (dialog.c:1434) ==26259== by 0x4DA3978: run_test (test.h:584) ==26259== by 0x4DA3D67: main (test.h:654) ==26259== -- 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 1

[Bug 36330] New: valgrind shows a couple leak in secur32/tests/schannel.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36330 Bug ID: 36330 Summary: valgrind shows a couple leak in secur32/tests/schannel.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==16588== 8 bytes in 1 blocks are definitely lost in loss record 10 of 297 ==16588== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==16588== by 0x5ADC1F3: ??? ==16588== by 0x5ADCAC8: ??? ==16588== by 0x4D7D019: test_communication (schannel.c:696) ==16588== by 0x4D7E737: func_schannel (schannel.c:907) ==16588== by 0x4D805BC: run_test (test.h:584) ==16588== by 0x4D809AB: main (test.h:654) ==16588== ==16588== 11,108 bytes in 146 blocks are possibly lost in loss record 293 of 297 ==16588== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==16588== by 0x4FA85DF: CryptMemAlloc (main.c:124) ==16588== by 0x4FB9D32: crypt_oid_init (oid.c:1431) ==16588== by 0x4FA81F8: DllMain (main.c:46) ==16588== by 0x4FCCF36: __wine_spec_dll_entry (dll_entry.c:40) ==16588== by 0x7BC53B24: ??? (in /home/austin/wine-valgrind-known/dlls/ntdll/ntdll.dll.so) ==16588== by 0x7BC5644E: MODULE_InitDLL (loader.c:1068) ==16588== by 0x7BC56AE7: process_attach (loader.c:1157) ==16588== by 0x7BC596E6: LdrLoadDll (loader.c:2129) ==16588== by 0x7B8581FE: load_library (module.c:933) ==16588== by 0x7B8582C9: LoadLibraryExW (module.c:990) ==16588== by 0x7B8583E0: LoadLibraryExA (module.c:970) ==16588== by 0x7B85844C: LoadLibraryA (module.c:1022) ==16588== by 0x4D7E4B0: func_schannel (schannel.c:122) ==16588== by 0x4D805BC: run_test (test.h:584) ==16588== by 0x4D809AB: main (test.h:654) ==16588== -- 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 36286] New: valgrind shows an invalid read in ieframe/tests/ie.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36286 Bug ID: 36286 Summary: valgrind shows an invalid read in ieframe/tests/ie.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==17071== Invalid read of size 4 ==17071== at 0x400AD40: memcpy (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==17071== by 0x5A80552: xbuf_add (tmarshal.c:107) ==17071== by 0x5A82737: serialize_param (tmarshal.c:704) ==17071== by 0x5A82FB3: serialize_param (tmarshal.c:809) ==17071== by 0x5A88EB1: TMStubImpl_Invoke (tmarshal.c:2118) ==17071== by 0x50AD280: RPC_ExecuteCall (objidl.h:9086) ==17071== by 0x506C1ED: apartment_wndproc (compobj.c:1460) ==17071== by 0x54D8509: ??? (winproc.c:173) ==17071== by 0x54D867E: call_window_proc (winproc.c:244) ==17071== by 0x54DA817: WINPROC_call_window (winproc.c:900) ==17071== by 0x549BBE4: DispatchMessageW (message.c:4019) ==17071== by 0x4D26F60: IEWinMain (iexplore.c:1061) ==17071== by 0x475EA34: wWinMain (main.c:84) ==17071== by 0x475ED21: wmain (exe_wmain.c:51) ==17071== by 0x475EBFC: __wine_spec_exe_wentry (exe_wentry.c:36) ==17071== by 0x7B864247: ??? (process.c:1045) ==17071== by 0x7B864394: start_process (process.c:1097) ==17071== by 0x7BC87087: ??? (signal_i386.c:2571) ==17071== by 0x7BC870D0: call_thread_func (signal_i386.c:2630) ==17071== by 0x7BC87065: ??? (signal_i386.c:2571) ==17071== Address 0x47f42c8 is 16 bytes after a recently re-allocated block of size 208 alloc'd ==17071== at 0x7BC4C735: notify_alloc (heap.c:255) ==17071== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==17071== by 0x7B84586B: HeapAlloc (heap.c:271) ==17071== by 0x7B845A92: GlobalAlloc (heap.c:364) ==17071== by 0x7B846ECF: LocalAlloc (heap.c:967) ==17071== by 0x63A0A16: Alloc (comctl32undoc.c:74) ==17071== by 0x63F9DF0: REBAR_InsertBandT (rebar.c:2518) ==17071== by 0x63FD2C3: REBAR_WindowProc (rebar.c:3633) ==17071== by 0x54D8509: ??? (winproc.c:173) ==17071== by 0x54D867E: call_window_proc (winproc.c:244) ==17071== by 0x54DA817: WINPROC_call_window (winproc.c:900) ==17071== by 0x54971BC: call_window_proc (message.c:2223) ==17071== by 0x549A05A: send_message (message.c:3260) ==17071== by 0x549A678: SendMessageW (message.c:3454) ==17071== by 0x4D252BC: create_rebar (iexplore.c:492) ==17071== by 0x4D25371: iewnd_OnCreate (iexplore.c:506) ==17071== by 0x4D25B93: ie_window_proc (iexplore.c:665) ==17071== by 0x54D8509: ??? (winproc.c:173) ==17071== by 0x54D867E: call_window_proc (winproc.c:244) ==17071== by 0x54DA817: WINPROC_call_window (winproc.c:900) ==17071== -- 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 1

[Bug 36196] New: valgrind shows some possible leaks in mmdevapi/tests/propstore.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36196 Bug ID: 36196 Summary: valgrind shows some possible leaks in mmdevapi/tests/propstore.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: mmdevapi Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==12387== 28 bytes in 1 blocks are possibly lost in loss record 92 of 461 ==12387== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==12387== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==12387== by 0x4FC483E: COMPOBJ_DllList_Add (compobj.c:526) ==12387== by 0x4FC6B7A: apartment_getclassobject (compobj.c:1335) ==12387== by 0x4FCA2C4: get_inproc_class_object (compobj.c:2894) ==12387== by 0x4FCA783: CoGetClassObject (compobj.c:3032) ==12387== by 0x4FCAD45: CoCreateInstance (compobj.c:3197) ==12387== by 0x4E6D893: func_propstore (propstore.c:120) ==12387== by 0x4E80EAF: run_test (test.h:584) ==12387== by 0x4E8129E: main (test.h:654) ==12387== { -- 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 1

[Bug 36586] New: valgrind shows uninitialized memory use in user32/tests/msg.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36586 Bug ID: 36586 Summary: valgrind shows uninitialized memory use in user32/tests/msg.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 ==27824== Conditional jump or move depends on uninitialised value(s) ==27824== at 0x427931D: vfprintf (vfprintf.c:1634) ==27824== by 0x429C4E1: vsprintf (iovsprintf.c:42) ==27824== by 0x428229E: sprintf (sprintf.c:32) ==27824== by 0x4D13DF4: add_message_ (msg.c:1994) ==27824== by 0x4D4338F: test_hotkey (msg.c:13929) ==27824== by 0x4D47490: func_msg (msg.c:14598) ==27824== by 0x4DA6978: run_test (test.h:584) ==27824== by 0x4DA6D67: main (test.h:654) ==27824== Uninitialised value was created by a stack allocation ==27824== at 0x4D41D56: test_hotkey (msg.c:13707) ==27824== Use of uninitialised value of size 4 ==27824== at 0x42780CD: _itoa_word (_itoa.c:180) ==27824== by 0x427B856: vfprintf (vfprintf.c:1634) ==27824== by 0x429C4E1: vsprintf (iovsprintf.c:42) ==27824== by 0x428229E: sprintf (sprintf.c:32) ==27824== by 0x4D13DF4: add_message_ (msg.c:1994) ==27824== by 0x4D4338F: test_hotkey (msg.c:13929) ==27824== by 0x4D47490: func_msg (msg.c:14598) ==27824== by 0x4DA6978: run_test (test.h:584) ==27824== by 0x4DA6D67: main (test.h:654) ==27824== Uninitialised value was created by a stack allocation ==27824== at 0x4D41D56: test_hotkey (msg.c:13707) ==27824== -- 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 1