March 2009 - Wine-bugs - list.winehq.org

[Bug 16273] New: nVidia melody installer fails in ole
by wine-bugs＠winehq.org 06 Jan '16

06 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=16273 Summary: nVidia melody installer fails in ole Product: Wine Version: 1.1.9 Platform: PC URL: http://download.nvidia.com/developer/Tools/Melody/1.2/Me lody_1.2.0630.1500.exe OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: ole AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Blocks: 6912 Created an attachment (id=17548) --> (http://bugs.winehq.org/attachment.cgi?id=17548) +ole in git err:ole:TLB_ReadTypeLib Loading of typelib L"C:\\Program Files\\Common Files\\InstallShield\\Professional\\RunTime\\IsProBE.tlb" failed with error 2 +ole 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.

1 5

[Bug 13027] New: Add a description field to winetest
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=13027 Summary: Add a description field to winetest Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: testcases AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Depends on: 13026 It should be possible to specify a description for a winetest run. That description field would be sent with the report and would describe the system the tests are run on, providing details that cannot be retrieve programmatically. For instance: "US Windows XP system provided by Compaq and then cleaned up. Last updated on 2007/10/16 but no IE7." or "Clean install of a stock French Windows 95, running in a VMware 5.5 guest." The user should be able to either enter this description in the main dialog (see also bug 13026), or on the command line. -- 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 8

[Bug 13028] New: winetest's Stop button does not work
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=13028 Summary: winetest's Stop button does not work Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: testcases AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com It says it's not implemented but closing the winetest window works just fine. So it seems like implementing the Stop button should not be too hard. -- 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 11

[Bug 11016] New: odbc32.dll should look for libodbc.so.1 instead of libodbc .so
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=11016 Summary: odbc32.dll should look for libodbc.so.1 instead of libodbc.so Product: Wine Version: 20040615 Platform: PC URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=259710 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-misc AssignedTo: wine-bugs(a)winehq.org ReportedBy: ovek(a)arcticnet.no An easy one for a newbie wine hacker, maybe... Currently, in dlls/odbc32/proxyodbc.c, there's a hardcoded libodbc.so (unless an environment variable overrides it). Perhaps it would be preferable if the WINE_GET_SONAME configure macro was used to grab a name like libodbc.so.1 instead, so that if some user have installed unixodbc, things would Just Work without forcing him/her to also either install unixodbc-dev, or manually make a symlink, or figure out weird environment variables. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 3

[Bug 13030] New: winetest and result logging / submission
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=13030 Summary: winetest and result logging / submission Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: testcases AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com The winetest GUI does not make it possible to choose between saving the results to a local file and submitting the results. -- 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 11177] New: winealsa doesn't assign unique MIDI port names
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=11177 Summary: winealsa doesn't assign unique MIDI port names Product: Wine Version: 20050628 Platform: PC URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=333361 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: _obsolete_multimedia AssignedTo: wine-bugs(a)winehq.org ReportedBy: ovek(a)arcticnet.no Currently, when mapping ALSA MIDI ports to Windows MIDI port names, winealsa uses the port's client name, which is not unique and may cause some programs to get confused. A user is suggesting using the ALSA port name, which I suspect can be acquired by e.g. replacing snd_seq_client_info_get_name(cinfo) in midi.c with snd_seq_port_info_get_name(pinfo). You could also append a number to the client name, or whatever else it takes to make the name unique. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 7

[Bug 14607] New: Serious Sam TFE and TSE - window minimizes and becomes unusable
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=14607 Summary: Serious Sam TFE and TSE - window minimizes and becomes unusable Product: Wine Version: CVS/GIT Platform: PC URL: http://files.seriouszone.com/download.php?fileid=338 OS/Version: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: alexd4(a)inbox.lv CC: julliard(a)winehq.org In current git both "encounters" of Serious Sam 1 are regressed compared to wine-0.9.59. When attempting to change video resolution in full screen mode (in current git) the game's window becomes minimized and can't be restored after that. It actually appears to change resolution successfully, but then there is a "keep this settings yes/no" box and after pressing yes it breaks. This worked in wine-0.9.59. The problem is in fullscreen mode only, in virtual desktop emulation everything works. I did some regression testing, and I think problems began with this commit: commit fd97acbadffdc8af6d2682cb761a92ff2ab2f355 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Apr 7 11:43:46 2008 +0200 winex11: Set the _NET_WM_STATE atom directly for unmapped windows. It is a bit difficult, because the nature of the problem changed slightly between the above commit and current git. I.e. in a commit just before fd97acbadffdc8af6d2682cb761a92ff2ab2f355 it works, in fd97acbadffdc8af6d2682cb761a92ff2ab2f355 a similar broken "minimization" happens, only not after changing the resolution, but instead during game initialization (you can't even get to the main menu). A bit later, a different commit (1bf824e0b00d2b179d5f34dd0c7ace83e83bd28a) partially fixed the problem, getting it to the state as it is now (can get to menu, but can't change resolution). I tried backporting fix from 1bf824e0b00d2b179d5f34dd0c7ace83e83bd28a to commit fd97acbadffdc8af6d2682cb761a92ff2ab2f355 and it works as expected, recreating the problem in current form in that commit. In all of these cases only fullscreen mode is affected. I see this in Serious Sam - The First Encounter 1.05 (retail) and in Serious Sam - The Second Encounter demo. Demo is available for download. If it will be necessary I can generate some logs for 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.

1 6

[Bug 13029] New: winetest should make it possible to just extract the individual tests
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=13029 Summary: winetest should make it possible to just extract the individual tests Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: testcases AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com The first task that winetest does is extract the individual test binaries. However it does not say where and if one wants to get at them (to then run them by hand for testing/debugging purposes), then one has to kill winetest, and track down its temporary directory (which is something like in c:\Documents and Settings\account\Local Settings\Temp\wctXXX btw). It would be nice to have an 'Extract tests' button in the main dialog that would open a dialog letting the user choose where to save the individual tests (or some other reasonably simple way of achieving the same purpose). -- 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 10417] New: OLEAUT32: crash if >128 methods in an interface
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=10417 Summary: OLEAUT32: crash if >128 methods in an interface Product: Wine Version: 0.9.49. Platform: Macintosh OS/Version: Mac OS X 10.5 Status: UNCONFIRMED Severity: normal Priority: P1 Component: wine-ole AssignedTo: wine-bugs(a)winehq.org ReportedBy: mjk(a)cardbox.com This bug was encountered in build cxoffice-6.2.0rc1-2-g024be42 of Wine (part of CrossOver Mac). The bug has been identified in the current source code at http://source.winehq.org/source/dlls/oleaut32/tmarshal.c. Using any marshaled interface with more than 128 methods causes a crash within OLEAUT32 if any method at position >=128 is called. This was detected when using Cardbox (http://www.cardbox.com) and is a SHOW-STOPPER because it makes the use of VBScript macros impossible. However, the bug is completely general and applies to any application at all that has interfaces with large number of methods. It is quite possible that many random OLE / COM - related bugs that have already been reported have this bug as their underlying cause. The version of Cardbox on which the bug was found is more recent than the one currently available on the web site. If anyone wants to have a copy for testing, together with instructions for reproducing the crash, please contact me. LOCATION OF THE BUG The bug is in dlls/oleaut32/tmarshal.c. When constructing a proxy interface, PSFacBuf_CreateProxy at line #1712 constructs the following proxy code for each method: popl %eax pushl <nr> pushl %eax call xCall lret <n> (+4) where <nr> is the position of the method in the list of methods: 0, 1, 2, and so on. The pushl <nr> instruction is defined by following code: 374 BYTE pushlval; // set to 0x6a by line #1712 375 BYTE nr; The fact that the method position is a byte already limits the maximum size of an interface to 256 methods, which is less than the 512-method limit of Windows NT4.0 SP3, and the 1024-method limit of Windows 2000: see "MIDL2362" in http://msdn2.microsoft.com/en-us/library/aa366756.aspx for details. Thus this needs to be corrected in any case. The proxy code as it stands will call method 0 instead of method 256, method 1 instead of method 257, and so on, leading to random behaviour and possible stack corruption. The crash when method 128 is called has a different cause. The proxy for method 128 contains the instruction 6A 80, because the programmer thought that this would push 00000080 onto the stack. In fact the PUSH instruction with opcode 6A SIGN-EXTENDS its operand and does not zero-extend it. Thus the proxy for the 128th method pushes FFFFFF80 onto the stack before calling xCall. xCall interprets this as a negative number (-128) and thus attempts to synthesize a call not to method 128 but to a non-existent method -128. In the same way it will call method -127 instead of method 129,... and so on. SUGGESTED CORRECTION The very simple correction to this bug, which is guaranteed to work, is to alter line 375 to 375 DWORD nr; and line 1712 to 1712 xasm->pushlval = 0x68; which expects a 32-bit operand rather than an 8-bit one. This will result in every proxy using 15 bytes per method instead of 12 bytes. This does not seem an excessive price to pay for complete reliability in the future: there will then be no limit to the number of methods that can be supported. ALTERNATIVE CORRECTIONS If the 25% expansion in proxy size is considered unacceptable (it should not really be: proxies are small) then there are several ways round the problem. An increase to 256 methods could be achieved simply by adding a line at the very beginning of xCall: method &= 0xff; but this would HAVE to be accompanied by an explicit test for the method count limit (now 256) in PSFacBuf_CreateProxy so that the attempt to create a proxy with too methods would simply fail rather than (as now) generate a proxy that will randomly crash the application. Another approach would be to create dummy functions (in assembler) that would add 128, 256, 384, 512, etc to the 'method' argument before forwarding it on to xCall. In that case, method numbers after 127 would generate proxies that called one of the variant xCalls instead of the original one. The programming in PSFacBuf_CreateProxy would be relatively straightforward, and the dummy functions would not need to do any stack manipulation: they would simply add an offset to the DWORD at [ESP+8] and then JMP straight to the start of xCall. This would *still* give a finite limit to the number of methods, but the limit would be much larger. Again, good engineering practice dictates that PSFacBuf_CreateProxy should report an error if it encounters a number of methods beyond the number that it was designed to cope with. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 11

[Bug 10536] New: ITypeInfo_fnInvoke failed to convert param 0 to VT_BOOL from VT_BSTR
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=10536 Summary: ITypeInfo_fnInvoke failed to convert param 0 to VT_BOOL from VT_BSTR Product: Wine Version: 0.9.49. Platform: PC URL: http://uniqlo.jp/uniqlock OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-ole AssignedTo: wine-bugs(a)winehq.org ReportedBy: fnjordy(a)gmail.com Uniqlock screensaver doesn't display anything, presumably it might be related to the Wine output: in CSoundUtils constructor: fixme:win:WIN_CreateWindowEx Parent is HWND_MESSAGE err:ole:ITypeInfo_fnInvoke failed to convert param 0 to VT_BOOL from VT_BSTR -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 4