December 2007 - Wine-bugs - list.winehq.org

[Bug 10349] New: Yukon Trail installer crashes at the end
by wine-bugs＠winehq.org 31 Oct '25

31 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=10349 Summary: Yukon Trail installer crashes at the end Product: Wine Version: 0.9.48. Platform: Other OS/Version: other Status: UNCONFIRMED Severity: minor Priority: P2 Component: wine-misc AssignedTo: wine-bugs(a)winehq.org ReportedBy: echidnaman(a)gmail.com Created an attachment (id=9017) --> (http://bugs.winehq.org/attachment.cgi?id=9017) Crash Log After the Yukon Trail's installer is done installing, it crashes, taking the file browser it spawns with it. To reproduce: -Run installer -Complete installation -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 36

[Bug 9314] New: Borland C++ Builder 5 expects registry values to be read in the same order they were written
by wine-bugs＠winehq.org 28 Oct '25

28 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=9314 Summary: Borland C++ Builder 5 expects registry values to be read in the same order they were written Product: Wine Version: 0.9.43. Platform: PC-x86-64 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: wine-advapi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: mikolaj.zalewski(a)gmail.com Created an attachment (id=7584) --> (http://bugs.winehq.org/attachment.cgi?id=7584) test It arranges the component palettes in the same order in which it read the values from the registry (even if MSDN exlicitly says not to rely on the order in which the values are read). We store the values in the alphabetical order to binsearch them so the palettes under Wine are in alphabetical order instead of the configured order. I attach a small test showing that under Windows the values are read in the same order as they were written. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 20

[Bug 9378] New: CM: Shock Force 'Could not initialize graphics display'
by wine-bugs＠winehq.org 17 Oct '25

17 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=9378 Summary: CM: Shock Force 'Could not initialize graphics display' Product: Wine Version: 0.9.43. Platform: PC URL: http://www.battlefront.com/products/cmsf/downloads.html OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-directx AssignedTo: wine-bugs(a)winehq.org ReportedBy: mailing_list(a)orange.nl After starting Combat Mission: Shock Force Demo it stops with the message: 'Could not initialize graphics display. REQUIRED 1024x768, 32-bit color'. The terminal output doesn't provide any clues: wine 'CM Shock Force DEMO.exe' ALSA lib conf.c:3939:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:910:(snd_ctl_open_noupdate) Invalid CTL default:0 err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element fixme:wave:ALSA_AddCaptureDevice Add support for DSCapture ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 38

[Bug 10941] New: Wine does not print in a newly allocated console window
by wine-bugs＠winehq.org 01 Jun '25

01 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=10941 Summary: Wine does not print in a newly allocated console window Product: Wine Version: 0.9.52. Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-console AssignedTo: wine-bugs(a)winehq.org ReportedBy: mail2benny(a)gmail.com Created an attachment (id=9867) --> (http://bugs.winehq.org/attachment.cgi?id=9867) The binary which recreates the bug Wine does not print in a newly allocated console window using the function FreeConsole(); and AllocConsole(); I've written a program which recreates the bug. I'll post the binary and the source. (compiled on Dev-C++ 4.9.9.2, in Wine) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 28

[Bug 10853] New: Codeblocks - misplaced windows
by wine-bugs＠winehq.org 01 Jun '25

01 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=10853 Summary: Codeblocks - misplaced windows Product: Wine Version: CVS/GIT Platform: PC-x86-64 URL: http://www.codeblocks.org OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-misc AssignedTo: wine-bugs(a)winehq.org ReportedBy: kgbricola(a)web.de Created an attachment (id=9747) --> (http://bugs.winehq.org/attachment.cgi?id=9747) the misplaced drop-down-list Wine misplaced the "Build target" drop-down-list. (I've tested codeblocks svn build 4630). -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 22

[Bug 9333] New: WM_LBUTTONDOWN message is not generated reliably
by wine-bugs＠winehq.org 01 Jun '25

01 Jun '25

http://bugs.winehq.org/show_bug.cgi?id=9333 Summary: WM_LBUTTONDOWN message is not generated reliably Product: Wine Version: 0.9.42. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-winelib AssignedTo: wine-bugs(a)winehq.org ReportedBy: ecentanni(a)lsijax.com using wine-devel rpm package for Red Hat Enterprise Client Ver 5. Version 0.9.42. Release 1.el5. Source rpm is wine-0.9.42-1.el5.src.rpm When clicking on the main window of the application the WM_LBUTTONDOWN message is not generated reliably. If I change focus to another application and then back to the subject program I may get one or two WM_LBUTTONDOWN message and then no more. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 19

[Bug 10051] New: Parallax SX Key IDE cannot detect serial port under WINE
by wine-bugs＠winehq.org 18 May '25

18 May '25

http://bugs.winehq.org/show_bug.cgi?id=10051 Summary: Parallax SX Key IDE cannot detect serial port under WINE Product: Wine Version: 0.9.46. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-setupapi AssignedTo: wine-bugs(a)winehq.org ReportedBy: ultimatedevr(a)yahoo.com Created an attachment (id=8599) --> (http://bugs.winehq.org/attachment.cgi?id=8599) Result of running SXKey.exe in wine with the +setupapi debug flag. I am trying to run the Parallax SX Key IDE through WINE, however the IDE does not detect any of my serial ports. I have symlinked them to ~/.wine/dosdevices/ and added them to my registry, however the IDE still cannot detect my serial ports. I am currently running WINE v.0.9.46 (the same problem exists in the CVS version as well). (BTW, I have heard of others getting this to work, yet others who couldn't: http://forums.parallax.com/forums/default.aspx?f=15&m=217429&g=221692) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 25

[Bug 10341] New: Pro evolution soccer 2008
by wine-bugs＠winehq.org 18 Apr '25

18 Apr '25

http://bugs.winehq.org/show_bug.cgi?id=10341 Summary: Pro evolution soccer 2008 Product: Wine Version: 0.9.48. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: test AssignedTo: wine-bugs(a)winehq.org ReportedBy: marco.r24(a)libero.it Game crash when exit the game -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 32

[Bug 10522] New: endless WM_PAINT loop bug (update regions, queue paint count)
by wine-bugs＠winehq.org 17 Feb '25

17 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=10522 Summary: endless WM_PAINT loop bug (update regions, queue paint count) Product: Wine Version: CVS/GIT Platform: PC URL: http://www.microsoft.com/whdc/devtools/debugging/install x86.mspx OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-user AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=9265) --> (http://bugs.winehq.org/attachment.cgi?id=9265) trace with WINEDEBUG=+tid,+message,+win,+server Hello, I've seen this bug a while ago in other apps but ignored it because it was not easily to reproduce. Well until recently when I tested some stuff with windbg from "Debugging Tools for Windows" (Microsoft). I used debugging tools version 6.8.4.0 and recent GIT (wine-0.9.49-302-g58b85bb). Immediately when a child window was opened using toolbar (register, locals, .. whatever), windbg would become unresponsive, eating most CPU. Happens in both GUI modes - "floating/docking toolwindow" and "MDI emulation. Though "MDI emulation" is more obvious, it actually shows the endless refreshing (window caption). Attached is WINEDEBUG=+tid,+message,+win,+server log. Additionally I added a trace message which prints the current queue paint count (when incremented or fetched) which makes some things easier to spot. Printed as "inc_queue_paint_count: %d" and "get_message_paint_count: %d". The window hierarchy is as follows: --- snip --- *root*=0x10020 Shell_TrayWnd=0x10022 WinDbgFrameClass=0x10024 DockClass=0x10026 ToolbarWindow32=0x10028 msctls_statusbar32=0x1002a tooltips_class32=0x1002e WinBaseClass=0x10030 ToolbarWindow32=0x10032 SysListView32=0x10034 SysHeader32=0x10036 RichEdit20W=0x10038 --- snip --- After the child windows are created the queue paint count never drops to zero, resulting in endless WM_PAINT processing. Maybe some update (region) code path missed or flags problem? I played a bit with ignoring null region updates and it seemed to help a bit (preventing endless WM_PAINT loop) though other stuff wasn't drawn properly then. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 41

[Bug 9418] New: Colasoft Mac Scanner 1.1 doesn't work
by wine-bugs＠winehq.org 26 Jan '25

26 Jan '25

http://bugs.winehq.org/show_bug.cgi?id=9418 Summary: Colasoft Mac Scanner 1.1 doesn't work Product: Wine Version: CVS/GIT Platform: Other URL: http://www.colasoft.com/mac_scanner/ OS/Version: other Status: NEW Keywords: download Severity: enhancement Priority: P2 Component: wine-net AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com A user complained in http://www.linuxforums.org/forum/wine/101536-problem-tcp-ip.html "[Running colasoft mac scan in wine complains Cannot find any valid ip address...]" So I downloaded it and tried it. It found my IP address right away, so that's fine. But it wasn't able to actually scan for MAC addresses; it had lots of fixme:iphlpapi:SendARP (DestIP 0xda01a8c0, SrcIP 0x00000000, pMacAddr 0x7abcc808, PhyAddrLen 0x7abcc7fc): stub messages. On Linux, at least, the way to do this is probably to send the packet, wait a millisec, then do ioctl SIOCGARP. (Or the command arp -n W.X.Y.Z. Or look in /proc/net/arp.) It'd be cheesy beans to implement, if anybody cares to. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 14