June 2012 - Wine-Bugs - list.winehq.org

[Bug 17807] New: Electronics Workbench 5.12: measurement units aren't shown
by wine-bugs＠winehq.org May 18, 2021

May 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=17807 Summary: Electronics Workbench 5.12: measurement units aren't shown Product: Wine Version: 1.1.17 Platform: PC URL: http://appdb.winehq.org/objectManager.php?sClass=version &iId=402 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nick(a)vyalceva.net Created an attachment (id=20039) --> (http://bugs.winehq.org/attachment.cgi?id=20039) the oscilloscope window When trying to set measurement unit for a parameter in the "Component Properties" window, or in the oscilloscope, measurement units are not shown in the selection box. But I can view it by copying from the box and pasting in a text editor, e.g. "0.50 s/div ". Old wine version 0.9.52 shows units in the oscilloscope window, but doesn't do it in the component properties (http://appdb.winehq.org/screenshots.php?iAppId=267&iVersionId=402) Also I get the following error message on exit: "access violation on (FFF4EFFF), reading C4". Running from terminal shows me the only line "fixme:font:WineEngRemoveFontResourceEx :stub". -- 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.

2 25

[Bug 15462] New: Wine blocking on exit when stdout and stderr are piped
by wine-bugs＠winehq.org May 18, 2021

May 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=15462 Summary: Wine blocking on exit when stdout and stderr are piped Product: Wine Version: 1.0.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: chris(a)neko.net.nz Created an attachment (id=16357) --> (http://bugs.winehq.org/attachment.cgi?id=16357) Output of two simultaneous runs of described script The issue occurs when concurrently running shell scripts which call Wine processes whose standard out and standard error are both piped to another program. When two instances of a script such as the following are run concurrently, the first child wine processes started by each of then run together, but in one of the scripts that child doesn't fully exit until the _other_ script has completely run and exited. (The Wine process terminates, but the pipeline doesn't complete and so the script doesn't continue.) A bash test-case to show this behaviour is as follows: for iter in first second ; do echo "[$$] running $iter child wine" `date`; wine sleep-long.exe 2>&1 | tee /dev/null; done; echo "[$$] done " `date` The problem doesn't occur if either the redirection or pipe is removed, if I run the scripts in separate Wine environments using $WINEPREFIX, or if I have another long-lived Wine process which stays running throughout the entire operation. An example run with timing is attached. The test Wine program used above, 'sleep-long', is the following tiny C program (tested with Microsoft cl and Cygwin GCC with mingw): #include <stdio.h> #include <windows.h> int main(){ printf("Started fake compiler, sleeping 8000ms\n"); Sleep(8000); printf("Exiting fake compiler\n"); exit(0); } I've been able to reproduce this problem on several systems and Wine versions (Debian Lenny with distro-packaged Wine 1.0.0-1, Debian Etch with Wine 1.0-rc1-1~bpo40+1 from Debian backports, Ubuntu Dapper with distro-packaged Wine 0.9.9-0ubuntu2) but not on one other (Debian Etch with distro-packaged Wine 0.9.25-2.1) -- 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.

2 15

[Bug 15906] New: EnumFonts returns each font multiple times
by wine-bugs＠winehq.org May 18, 2021

May 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=15906 Summary: EnumFonts returns each font multiple times Product: Wine Version: 1.1.5 Platform: PC-x86-64 URL: http://msdn.microsoft.com/en- us/library/ms533964(VS.85).aspx OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: goeran(a)uddeborg.se Created an attachment (id=17078) --> (http://bugs.winehq.org/attachment.cgi?id=17078) Test program executing EnumFonts() According to the documentation (see URL) the EnumFonts function returns one (random) font of each available typeface. The Wine implementation returns each typeface many times. As a test case I installed the typeface "Signet Roundhand" and ran the attached test program. Under indows it returns "Signet Roundhand" once. Under wine it returns it three times, with different values for lfCharSet and tmCharSet. I also copied the Arial font files from Windows (arial.ttf, ariali.ttf, arialbd.ttf, and arialbi.ttf) to my $HOME/.fonts directory. Under Windows, Arial is returned once with the test program. Under Wine it is returned ten(!) times. -- 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.

2 17

[Bug 14350] New: SetClassLongW() to subclass window EDIT control Problem
by wine-bugs＠winehq.org May 18, 2021

May 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=14350 Summary: SetClassLongW() to subclass window EDIT control Problem Product: Wine Version: 1.0.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: hongbo(a)njstar.com CC: hongbo(a)njstar.com Created an attachment (id=14649) --> (http://bugs.winehq.org/attachment.cgi?id=14649) MSVC6 MFC test project with exe in debug dir Summary: SetClassLongW(hEditWnd, GCL_WNDPROC, (DWORD)EditWndProc) behave different on WINE 1.0 from Windows. Any EDIT window created after will be ANSI window on Windows, but Unicode Windows on Wine. How To Repeat: In the attached VC6 MFC ANSI App project, SetClassLongW is called in ------------------------------------------------------------------- static WNDPROC lpfnOldEditWndProc=NULL; LONG FAR PASCAL EditWndProc(HWND hWnd, WORD Message, WORD wParam, LONG lParam) { return CallWindowProcW((WNDPROC)lpfnOldEditWndProc, hWnd, Message, wParam,lParam); } int CDialogTestView::OnCreate(LPCREATESTRUCT lpCreateStruct) { if (CView::OnCreate(lpCreateStruct) == -1) return -1; HWND hEditWnd1 = CreateWindowEx(0,"EDIT", "E1",WS_POPUP,0, 0, 1, 1,NULL,NULL,NULL,NULL); lpfnOldEditWndProc =(WNDPROC)SetClassLongW(hEditWnd1, GCL_WNDPROC, (DWORD)EditWndProc); // TODO: Add your specialized creation code here return 0; } ------------------------------------------------------------------- There is a EDIT control on the About dialogbox, when click 'OK' on window the program report the Edit Box is NOT unicode Window. But Under Wine 1.0, It says 'the Edit Box IS unicode Window'. To Test: run the EXE in debug folder, Help - About DialogTest - click 'OK'. -- 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.

2 18

[Bug 12891] New: ntdll: exception.ok test fails in PC-BSD but not Linux
by wine-bugs＠winehq.org May 18, 2021

May 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=12891 Summary: ntdll: exception.ok test fails in PC-BSD but not Linux Product: Wine Version: 0.9.60 Platform: PC OS/Version: FreeBSD Status: NEW Keywords: testcase Severity: minor Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=12597) --> (http://bugs.winehq.org/attachment.cgi?id=12597) +relay,+seh,+ntdll in git exception.c:602: Test failed: expected 4 exceptions, got 0 fixme:seh:fpe_handler untested SIMD exception: 0. Might not work correctly *** Error code 1 +relay,+seh,+ntdll log attached -- 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.

2 10

[Bug 28831] New: secur32/tests/schannel.ok: occasional uninitialised memory read in _gnutls_recv_int() in test_communication()?
by wine-bugs＠winehq.org May 16, 2021

May 16, 2021

http://bugs.winehq.org/show_bug.cgi?id=28831 Bug #: 28831 Summary: secur32/tests/schannel.ok: occasional uninitialised memory read in _gnutls_recv_int() in test_communication()? Product: Wine Version: 1.3.30 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: secur32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified I don't see this on every run, but sometimes Valgrind complains: Conditional jump or move depends on uninitialised value(s) at _gnutls_recv_int (in /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14) by ??? (in /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14) by ??? (in /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14) by ??? (in /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14) by schan_InitializeSecurityContextW (schannel.c:728) by schan_InitializeSecurityContextA (schannel.c:775) by InitializeSecurityContextA (wrapper.c:282) by test_communication (schannel.c:644) by func_schannel (schannel.c:773) by run_test (test.h:556) by main (test.h:624) Uninitialised value was created by a client request by mark_block_uninitialized (heap.c:208) by initialize_block (heap.c:239) by RtlAllocateHeap (heap.c:1703) by init_buffers (schannel.c:496) by test_communication (schannel.c:633) by func_schannel (schannel.c:773) by run_test (test.h:556) by main (test.h:624) -- 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.

2 4

[Bug 15956] New: "make test" doesn't always leave screen in same video mode as it started in
by wine-bugs＠winehq.org May 12, 2021

May 12, 2021

http://bugs.winehq.org/show_bug.cgi?id=15956 Summary: "make test" doesn't always leave screen in same video mode as it started in Product: Wine Version: 1.1.7 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: testcases AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Some tests don't properly reset the video mode, even if they don't crash. I'm gathering a list of culprits and will post it here. -- 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.

2 4

[Bug 28816] New: kernel32/tests/loader.ok fails under valgrind
by wine-bugs＠winehq.org May 12, 2021

May 12, 2021

http://bugs.winehq.org/show_bug.cgi?id=28816 Bug #: 28816 Summary: kernel32/tests/loader.ok fails under valgrind Product: Wine Version: 1.3.30 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified Under Valgrind, "make loader.ok" fails with log loader.c:375: Test failed: 2: 0x10002000 != 0 loader.c:376: Test failed: 2: 1 != 0 loader.c:378: Test failed: 2: 2000 != MEM_FREE loader.c:379: Test failed: 2: 20000 != 0 -- 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.

2 9

[Bug 28738] New: user32/tests: invalid read in server_end_to_end_callback in dde.ok?
by wine-bugs＠winehq.org May 12, 2021

May 12, 2021

http://bugs.winehq.org/show_bug.cgi?id=28738 Bug #: 28738 Summary: user32/tests: invalid read in server_end_to_end_callback in dde.ok? Product: Wine Version: 1.3.30 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified Not sure how bad an invalid read in a dbgstr is, but here's the log: Invalid read of size 2 at wine_dbgstr_wn (test.h:471) by server_end_to_end_callback (test.h:66) by WDML_InvokeCallback (dde_misc.c:734) by WDML_ServerHandle (dde_server.c:834) by WDML_ServerConvProc (dde_server.c:1112) by ??? (in user32/user32.dll.so) by call_window_proc (winproc.c:242) by WINPROC_call_window (winproc.c:908) by DispatchMessageA (message.c:3738) by test_end_to_end_server (dde.c:2680) by func_dde (dde.c:2746) by run_test (test.h:556) by main (test.h:624) Address 0x7f00dae8 is 16 bytes inside a block of size 20 free'd at notify_free (heap.c:262) by RtlFreeHeap (heap.c:1748) by RtlFreeUnicodeString (rtlstr.c:319) by RegQueryValueExA (registry.c:1489) by load_face (freetype.c:1207) by WineEngInit (freetype.c:1345) by DllMain (gdiobj.c:582) -- 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.

2 7

[Bug 20925] New: d3d[89]/tests/visual crash under valgrind
by wine-bugs＠winehq.org May 12, 2021

May 12, 2021

http://bugs.winehq.org/show_bug.cgi?id=20925 Summary: d3d[89]/tests/visual crash under valgrind Product: Wine Version: 1.1.34 Platform: PC OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com http://kegel.com/wine/valgrind/logs/2009-12-05-01.15/vg-d3d8_visual.txt and http://kegel.com/wine/valgrind/logs/2009-12-05-01.15/vg-d3d9_visual.txt both show the crash Unhandled exception: page fault on read access to 0x58469450 in 32-bit code (0x0d9bc92b). Backtrace: =>0 0x0d9bc92b (0x11ad7000) 1 0x0fa16d50 in libgl.so.1 (+0x3dd50) (0x0ffbc038) which might be a problem in the driver, but could also be a disagreement between valgrind and the driver. I'm going to stop running d3d[89]/tests/visual under valgrind for now, since they always crash. Perhaps the good folks at Nvidia could have a look at how to get valgrind and their drivers to play nice together. (One of those logs also seems to have found a real use-after-free bug in their driver: Invalid read of size 4 at ??? (in /usr/lib32/libGLcore.so.180.44) Address 0xe6905f4 is 156 bytes inside a block of size 632 free'd at free (vg_replace_malloc.c:325) by ??? (in /usr/lib32/libGLcore.so.180.44) so perhaps they would actually get something out of this.) -- 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.

2 10