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

[Bug 30912] New: [Prince Of Persia : The Forgotten Sand]Does not work in 64Bits Prefix
by wine-bugs＠winehq.org Jan. 25, 2014

Jan. 25, 2014

http://bugs.winehq.org/show_bug.cgi?id=30912 Bug #: 30912 Summary: [Prince Of Persia : The Forgotten Sand]Does not work in 64Bits Prefix Product: Wine Version: 1.5.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: berillions(a)gmail.com Classification: Unclassified Created attachment 40546 --> http://bugs.winehq.org/attachment.cgi?id=40546 Output console without UGL Message I tried to play at this game in my 32Bits prefix and my 64Bits prefix. In my 32Bits prefix, there aren't problems, the game works correctly. No need to install applications with winetricks. In my 64Bits prefix, it's impossible to play. The Ubisoft Game Launcher works great but wine crash when the UGL launch the game. PoP TFS uses the same Ubisoft DRM than Assassin's Creed II/Brotherhood/Revelations and these games work without problems in the 64Bits prefix. -- 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 27271] New: ActiveX control of cebchina go out of iexplore
by wine-bugs＠winehq.org Jan. 24, 2014

Jan. 24, 2014

http://bugs.winehq.org/show_bug.cgi?id=27271 Summary: ActiveX control of cebchina go out of iexplore Product: Wine Version: 1.3.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mshtml AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Created an attachment (id=34879) --> (http://bugs.winehq.org/attachment.cgi?id=34879) HTML: powerpassword.html submit a testcase html file -- 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 17297] New: widl must accept arguments to functions (midl doesn't have to)
by wine-bugs＠winehq.org Jan. 23, 2014

Jan. 23, 2014

http://bugs.winehq.org/show_bug.cgi?id=17297 Summary: widl must accept arguments to functions (midl doesn't have to) Product: Wine Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: rpc AssignedTo: wine-bugs(a)winehq.org ReportedBy: lkcl(a)lkcl.net example: void get_data([out] char*); is valid syntax. widl barfs with the obtuse "syntax error" (gotta love flex/bison...) and must have this: void get_data([out] char* foo); i found the examples "com in plain c" and the IDL file in example 2 didn't have the variable names. -- 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 7

[Bug 16011] New: widl: Complex structs should have their pointer layout section after the structure's description
by wine-bugs＠winehq.org Jan. 23, 2014

Jan. 23, 2014

http://bugs.winehq.org/show_bug.cgi?id=16011 Summary: widl: Complex structs should have their pointer layout section after the structure's description Product: Wine Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: rpc AssignedTo: wine-bugs(a)winehq.org ReportedBy: huw(a)codeweavers.com CC: robertshearman(a)gmail.com, dsh(a)linux.ucla.edu See IDataObject_QueryGetData_Proxy. The pointer layout section's offset in FORMATETC (currently at 3330) is -ve. These are treated as WORD offsets in, for example, NdrComplexStructBufferSize(). -- 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 14787] New: widl fails to honour typedef ptr attributes
by wine-bugs＠winehq.org Jan. 23, 2014

Jan. 23, 2014

http://bugs.winehq.org/show_bug.cgi?id=14787 Summary: widl fails to honour typedef ptr attributes Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: rpc AssignedTo: wine-bugs(a)winehq.org ReportedBy: huw(a)codeweavers.com CC: robertshearman(a)gmail.com, dsh(a)linux.ucla.edu See dlls/rpcrt4/epm_c.c . For example the 'object' parameter of ept_map(). We have (in include/wine/dcetypes.idl) typedef [ptr] GUID *uuid_p_t; and (in include/wine/epm.idl) ept_map(..., uuid_p_t object, ...) So 'object' should be a full ptr, which is what midl generates. On the other hand widl generates a reference ptr. It looks like this should be fixed up in parser.y:set_type() somewhere. -- 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 14746] New: Natural Selection crashes with err:ntdll:RtlpWaitForCriticalSection section
by wine-bugs＠winehq.org Jan. 20, 2014

Jan. 20, 2014

http://bugs.winehq.org/show_bug.cgi?id=14746 Summary: Natural Selection crashes with err:ntdll:RtlpWaitForCriticalSection section Product: Wine Version: 1.1.2 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: clancc(a)shadowkitsune.net CC: clancc(a)shadowkitsune.net Created an attachment (id=15244) --> (http://bugs.winehq.org/attachment.cgi?id=15244) Crash Log (partial log, only copied the part that I think is related to the crash) from console. Natural Selection freezes for abit before crashing to desktop with a "err:ntdll:RtlpWaitForCriticalSection section" error. See attachment. -- 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 33

[Bug 29857] New: GetAsyncKeyState says Escape key is permanently down once it has been pressed
by wine-bugs＠winehq.org Jan. 20, 2014

Jan. 20, 2014

http://bugs.winehq.org/show_bug.cgi?id=29857 Bug #: 29857 Summary: GetAsyncKeyState says Escape key is permanently down once it has been pressed Product: Wine Version: 1.3.28 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: silas-wine(a)flatline.org.uk Classification: Unclassified I am debugging a Windows application that has a long-running processing thread which periodically checks for interrupts using GetAsyncKeyState(VK_ESCAPE) < 0 This worked fine on WINE 1.2.2, but on 1.3.28 the app kept behaving as if it were interrupted immediately when it had not been. Further investigation showed that, after Escape has been pressed just once, any future calls to GetAsyncKeyState (no matter how many events have been processed in the meantime) always return ffff8001. In other words, if you press Escape just once while running your app, any future calls that app makes to GetAsyncKeyState(VK_ESCAPE) will behave as though the Escape key is still down. Again this does not happen with WINE 1.2.2, only with 1.3.28. I was able to work around this bug by adding a call to GetKeyState(VK_ESCAPE) just before the test for GetAsyncKeyState(VK_ESCAPE) < 0. I ignored the return value of GetKeyState (http://msdn.microsoft.com/en-us/library/windows/desktop/ms646301%28v=vs.85%… says it should be called in response to a message; it doesn't say what happens if it's called when there has been no message, so I assume we can't rely on it to return meaningful values if called at just any time) however somehow the presence of the GetKeyState call caused WINE 1.3.28's GetAsyncKeyState to behave correctly. -- 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 29150] New: Windows FirstClass Client 11.0 (Buid 017) no login screen, settings problems and freeze
by wine-bugs＠winehq.org Jan. 20, 2014

Jan. 20, 2014

http://bugs.winehq.org/show_bug.cgi?id=29150 Bug #: 29150 Summary: Windows FirstClass Client 11.0 (Buid 017) no login screen, settings problems and freeze Product: Wine Version: 1.3.33 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jorgenqv(a)yahoo.com Classification: Unclassified Created attachment 37598 --> http://bugs.winehq.org/attachment.cgi?id=37598 Log running FCC 11.017 This is my fist WineHQ Bugzilla report so I hope I got everything right :-) Trying to get latest FirstClass client (FCC) to work in Wine 1.3.33 (ubuntu-wine-ppa-oneiric) with the following problems in Ubuntu 11.10 with Unity. The same behavior in Ubuntu 10.04 LTS with Wine 1.3.31 (ubuntu-wine-ppa-lucid). 1) Installation works fine but after it's done the FCC spash screen freezes when FCC starts. Normaly the login screen should pop up. You then have to right-click on the upper panel FCC icon (splash then disapear) and choose Connect. If you only click on the spash screen it disapears. 2) FirstClass can't find the settings file "home.fc" - this works fine in older versions of FCC. A file popup appears called "Open Settings File" to choose the settings file, but there isn't one. If you right click on the panel icon and look at your FCC Preferences under "General" the "Download folder" is set to "C:\users\yourlogin\My Documents\FirstClass\Download". Even if you set this right the settings file cannot be found next time you run FCC and you have to choose your settings file every time you want to login. You cannot connect if you don't have a old settings file - I think normaly the file is created by FCC if there isn't one. So you can't login on a fresh installed comuputer without a settings file. Even if you put the file home.fc it doesn't show so you have to write "home.fc" and hit Open in the "Open Settings File" window. 3) If you got your settings file and the login screen finaly shows - and you write your correct login and password and hit the enter key - FCC freezes. The workaround is to click on the green login arrow button next to the password field instead of hitting enter - not obvious for most users. For testing/reproduceing purposes: FirstClass Client 11.017 Download: http://www3.firstclass.com/ClientDownloads/FC11ClientDownloadFiles/FC11017U… Missing file home.fc to be save i home directory FirstClass/Settings/ Download: http://www.mediafire.com/?82x95kcqp3celd4 Also see attachment () Guest testing login/pass: gast/gast server fc.folkbildning.net Any kind of hints and workarounds are greatly appreciated. Thanks! /Jorgen -- 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 25357] New: CodeWright crashes
by wine-bugs＠winehq.org Jan. 20, 2014

Jan. 20, 2014

http://bugs.winehq.org/show_bug.cgi?id=25357 Summary: CodeWright crashes Product: Wine Version: 1.2.1 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kurtbutfrank(a)gmail.com CC: aric(a)codeweavers.com, xerox_xerox2000(a)yahoo.co.uk, scott(a)open-vote.org, unreal(a)home.nl, skunktrader(a)gmail.com, istvan.bisz(a)t-online.hu +++ This bug was initially created as a clone of Bug #14012 +++ I have CodeWright 7.5.04.7519 and have successfully installed in on a 32-bit version of Ubuntu 10.10 on a a stand-alone machine. I also have a 64-bit version of Ubuntu 10.10 running as a virtual machine using VirtualBox under a Win7-64 host. On that machine CodeWright halts immediately after displaying the splash screen. It appears to me that the symptoms are the same as that of bug 14012. On both machines Wine was installed using the Synaptic Package Manager under GNOME. My understanding is that this would have installed a 32-bit version of Wine in both cases. I can gather trace/debug info but will need specific directions. -- 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 27410] New: Starcraft II Patcher exits immediately without a crash
by wine-bugs＠winehq.org Jan. 19, 2014

Jan. 19, 2014

http://bugs.winehq.org/show_bug.cgi?id=27410 Summary: Starcraft II Patcher exits immediately without a crash Product: Wine Version: 1.3.21 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: m.strashun(a)gmail.com Created an attachment (id=35053) --> (http://bugs.winehq.org/attachment.cgi?id=35053) console output After launching Starcraft II.exe , patcher inetrface shows for 1-2 seconds and then program closes. No crash in log though. All console output 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 15