April 2003 - Wine-Bugs - list.winehq.org

[Bug 1359] - Wine doesn't work with XFree86-4.3 on RH9

by wine-bugs＠winehq.com

http://bugs.winehq.com/show_bug.cgi?id=1359 mike(a)theoretic.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From mike(a)theoretic.com 2003-04-03 02:59 ------- This is caused by the new glibc, and is a known problem *** This bug has been marked as a duplicate of 1343 *** DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1359>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

April 3, 2003

[Bug 1358] - "GraphicsDriver" = "none" wanted

by wine-bugs＠winehq.com

http://bugs.winehq.com/show_bug.cgi?id=1358 ------- Additional Comments From mike(a)theoretic.com 2003-04-03 02:56 ------- What is wrong with wineconsole? It was patched lately to use the standard stdin/stdout, so you can run winedbg in the xterm from which it was started for instance. Is that what you're thinking of? DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1358>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

April 3, 2003

[Bug 1359] New: - Wine doesn't work with XFree86-4.3 on RH9

by wine-bugs＠winehq.com

http://bugs.winehq.com/show_bug.cgi?id=1359 Summary: Wine doesn't work with XFree86-4.3 on RH9 Product: Wine Version: 20030318 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: wine-binary AssignedTo: wine-bugs(a)winehq.com ReportedBy: apunga(a)mymail.ro It stops giving: XIO: fatal IO error 0 (Success) on X server ":0.0" after 177 requests (176 known processed) with 0 events remaining. DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1359>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

April 2, 2003

[Bug 1010] - Unhandled exception in VFP6R.DLL (Visual FoxPro 6)

by wine-bugs＠winehq.com

http://bugs.winehq.com/show_bug.cgi?id=1010 ------- Additional Comments From aztecconsultants(a)java.fsbusiness.co.uk 2003-04-02 12:03 ------- I have to say that this bug is also to be found in Visual FoxPro 6.0 SP5 running under native Win2K SP3. It only occurs if you use an OCX control on a form. I believe that it is related to an OCX control firing internal events. When considering GPF faults with Visual FoxPro it is better to make sure that they do not occur on the native platform. FoxPro is single threaded (or stolen zero threaded during big SQL extracts!) so how it responds to underlying windows messages is very precarious. To date I have about 20 different variations of various unacknoledge Visual FoxPro GPFs. I have to work around then all during my Visual FoxPro development. I did report them via MS WWW site but noticed months later that they had no outstanding bugs with this horrid product so I stopped reporting them! I am now a Sun Java Certified programmer and hope never to have to deal with this FoxPro product again. Anton DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1010>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

April 2, 2003

[Bug 1358] New: - "GraphicsDriver" = "none" wanted

by wine-bugs＠winehq.com

http://bugs.winehq.com/show_bug.cgi?id=1358 Summary: "GraphicsDriver" = "none" wanted Product: Wine Version: CVS Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-binary AssignedTo: wine-bugs(a)winehq.com ReportedBy: wine(a)how.dk I suggest making a dummy graphicsdriver such "GraphicsDriver" = "none" which just makes stdout and stdin transparent. The two existing drivers x11drv and ttydrv won't do when running console programs many times in a row (e.g. a win32 console compiler from a gnumakefile): x11drv: initialization due to communication with xfs is painful over a slow network (e.g. a modem line) ttydrv: uses ncurses which means restoring the contents of the window each time wine finishes. This erases the output of the console program. Here is the code: // original code beginning in line 73 of user_main.c (rev 1.50): if (!(graphics_driver = LoadLibraryA( buffer ))) { MESSAGE( "Could not load graphics driver '%s'\n", buffer ); return FALSE; } ---- // could be changed to something along these lines: if (strncmp( "none", buffer, MAX_PATH) == 0 ) ; // do nothing else if (!(graphics_driver = LoadLibraryA( buffer ))) { MESSAGE( "Could not load graphics driver '%s'\n", buffer ); return FALSE; } DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1358>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

April 2, 2003

[Bug 1161] - CryptoAPI crashes in MS Money 2001 (illegal CPDeriveKey() call?)

by wine-bugs＠winehq.com

http://bugs.winehq.com/show_bug.cgi?id=1161 ------- Additional Comments From mike(a)theoretic.com 2003-04-02 08:38 ------- trace:crypt:CryptAcquireContextA (0x40541eb4, (null), (null), 1, 00000000) trace:crypt:CryptCreateHash (0x4029ef40, 0x8003, 0x0, 00000000, 0x40541e84) trace:crypt:CryptHashData (0x4029f4c8, 0x27108998, 2, 00000000) trace:crypt:CryptDeriveKey (0x4029ef40, 26114, 0x1076491464, 00000000, 0x40541e80) wine: Unhandled exception, starting debugger... Looks like a stub isn't good enough DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1161>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

April 2, 2003

[Bug 1091] - ScrollWindowEx does not update invalidated are

by wine-bugs＠winehq.com

http://bugs.winehq.com/show_bug.cgi?id=1091 ------- Additional Comments From jason_doig(a)scee.net 2003-04-02 01:58 ------- I am not convinced that this bug is infact related to the invalidated area. I think it's a case of the appropriate controls within the area not being scrolled. Commenting out the line in the X11 driver which checks if a control is inside the scrolling rectangle or not results in all the controls being scrolled and the window appears to function correctly again - albeit with some (possibly unrelated) graphical update issues. I don't understand the internals enough to think about a fix - but it seems to me that the window is scrolled before the childrens positions are checked, so perhaps that might be one issue? DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1091>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

April 2, 2003

[Bug 1357] New: - Vobsub text writing problems

by wine-bugs＠winehq.com

http://bugs.winehq.com/show_bug.cgi?id=1357 Summary: Vobsub text writing problems Product: Wine Version: 20030318 Platform: PC URL: http://vobsub.edensrising.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-binary AssignedTo: wine-bugs(a)winehq.com ReportedBy: webmaster(a)stratastuff.com I have this video editing program for windows I often use to subtitle foreign videos. It uses a plugin called textsub which "writes" the text to the movie. Now, that further uses vobsub.dll (the final reference ;p). So, I tried it out but got these erros: fixme:text:ExtTextOutW called on an open path fixme:text:ExtTextOutW called on an open path fixme:text:ExtTextOutW called on an open path fixme:text:ExtTextOutW called on an open path etc.. etc... etc... So, if anyone has any ideas on that. The link provided also has the source for the dll in case you want to look at that at all. Thanks ahead of time for everyone's help. Sincerely, Chris White DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1357>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

April 2, 2003

[Bug 1161] - CryptoAPI crashes in MS Money 2001 (illegal CPDeriveKey() call?)

by wine-bugs＠winehq.com

http://bugs.winehq.com/show_bug.cgi?id=1161 ------- Additional Comments From pollockd(a)magma.ca 2003-04-01 09:43 ------- Created an attachment (id=445) wine --debugmsg +relay,+crypt msmoney.exe &>~/output.txt DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1161>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

April 1, 2003

[Bug 1161] - CryptoAPI crashes in MS Money 2001 (illegal CPDeriveKey() call?)

by wine-bugs＠winehq.com

http://bugs.winehq.com/show_bug.cgi?id=1161 ------- Additional Comments From pollockd(a)magma.ca 2003-04-01 09:42 ------- Now, when the application starts, two windows open. One for "PSTORES.EXE" and another for MSMoney. The application still bombs, but I don't get the same "no implementation message". I'll attach the +crypt,+relay trace you asked for. The patch given didn't apply on the version I have. The spec file has an additional value after the parameter list, which appears to just be the function name itself. I've patched as follows: @ stdcall CryptGetHashParam(long long ptr ptr long) CryptGetHashParam @ stdcall CryptGetKeyParam(long long ptr ptr long) CryptGetKeyParam @ stdcall CryptGetLocalKeyLimits(long long long long long long long) CryptGetLocalKeyLimits @ stdcall CryptGetProvParam(long long ptr ptr long) CryptGetProvParam @ stdcall CryptGetUserKey(long long ptr) CryptGetUserKey DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1161>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

April 1, 2003