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

[Bug 44109] New: Simple free HAM program Opera crash on start.
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=44109 Bug ID: 44109 Summary: Simple free HAM program Opera crash on start. Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maxtaylor(a)mail.ru Distribution: --- Created attachment 59830 --> https://bugs.winehq.org/attachment.cgi?id=59830 Program from : https://rosmodem.wordpress.com/2011/01/10/ros-2/ Hi. This free ham program not run on WINE 1.6.2 I attach crash report and setup same program. Unhandled exception: unimplemented function pdh.dll.PdhVbAddCounter called in 32-bit code (0x7b83aace). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:7b83aace ESP:0033fa64 EBP:0033fad8 EFLAGS:00200246( - -- I Z- -P- ) EAX:7b82695d EBX:7b8b5000 ECX:00000000 EDX:80000100 ESI:80000100 EDI:660cc25a Stack dump: 0x0033fa64: 0033fb04 00000008 7b8583e6 80000100 0x0033fa74: 00000001 00000000 7b83aace 00000002 0x0033fa84: 7ce6d960 7ce6e1c2 0033fa94 00000000 0x0033fa94: 7ce69560 0010000f 00427540 004274d4 0x0033faa4: 00000000 00000000 0033facc 00427550 0x0033fab4: 0057d658 0033faec 6600a0d8 01ad493c Backtrace: =>0 0x7b83aace in kernel32 (+0x2aace) (0x0033fad8) 1 0x7ce6d928 in pdh (+0xd927) (0x0033fb14) 2 0x7ce69589 in pdh (+0x9588) (0x0033fbc0) 3 0x004bfc03 in opera v1.6.5 (+0xbfc02) (0x0033fbc0) 4 0x004bdedc in opera v1.6.5 (+0xbdedb) (0x0033fc34) 5 0x66009f64 in msvbvm60 (+0x9f63) (0x0033fd74) 6 0x66007a5a in msvbvm60 (+0x7a59) (0x0033fd98) 7 0x66003959 in msvbvm60 (+0x3958) (0x0033fdb8) 8 0x660036d2 in msvbvm60 (+0x36d1) (0x0033fdd8) 9 0x660035d8 in msvbvm60 (+0x35d7) (0x0033fe58) 10 0x00405102 in opera v1.6.5 (+0x5101) (0x0033fe78) 11 0x7b85f653 in kernel32 (+0x4f652) (0x0033feb8) 12 0x7bc799b0 call_thread_func_wrapper+0xb() in ntdll (0x0033fed8) 13 0x7bc7c93d call_thread_func+0x7c() in ntdll (0x0033ffa8) 14 0x7bc7998e RtlRaiseException+0x21() in ntdll (0x0033ffc8) 15 0x7bc4e8fe call_dll_entry_point+0x7ed() in ntdll (0x0033ffe8) 16 0xb758650d wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) 17 0xb75865cb wine_switch_to_stack+0x2a() in libwine.so.1 (0xbf9f2c78) 18 0x7bc541e2 LdrInitializeThunk+0x3a1() in ntdll (0xbf9f2cd8) 19 0x7b865bdd __wine_kernel_init+0xa0c() in kernel32 (0xbf9f3df8) 20 0x7bc547a3 __wine_process_init+0x192() in ntdll (0xbf9f3e88) 21 0xb7583c70 wine_init+0x30f() in libwine.so.1 (0xbf9f3ee8) 22 0x7bf00fdc main+0xfb() in <wine-loader> (0xbf9f4338) 23 0xb73abaf3 __libc_start_main+0xf2() in libc.so.6 (0x00000000) 0x7b83aace: subl $4,%esp Modules: Module Address Debug info Name (141 modules) PE 400000- 58a000 Export opera v1.6.5 PE 10000000-10030000 Deferred pskreporter_v1_6 PE 20000000-20032000 Deferred richtx32 PE 21580000-215b2000 Deferred mci32 PE 21c10000-21c2a000 Deferred mscomm32 PE 22170000-2218c000 Deferred mswinsck PE 234c0000-234dd000 Deferred msinet PE 24dd0000-24ded000 Deferred msstdfmt PE 27580000-27685000 Deferred mscomctl PE 66000000-66152000 Export msvbvm60 ELF 7ac00000-7ac5f000 Deferred riched20<elf> \-PE 7ac10000-7ac5f000 \ riched20 ELF 7b800000-7ba5b000 Dwarf kernel32<elf> \-PE 7b810000-7ba5b000 \ kernel32 ELF 7bc00000-7bcdb000 Dwarf ntdll<elf> \-PE 7bc10000-7bcdb000 \ ntdll ELF 7bf00000-7bf04000 Dwarf <wine-loader> ELF 7ce39000-7ce56000 Deferred libgcc_s.so.1 ELF 7ce56000-7ce75000 Dwarf pdh<elf> \-PE 7ce60000-7ce75000 \ pdh ELF 7ce75000-7ce7c000 Deferred libnss_dns.so.2 ELF 7ce94000-7ce9d000 Deferred libogg.so.0 ELF 7ce9d000-7cec9000 Deferred libvorbis.so.0 ELF 7cec9000-7d041000 Deferred libvorbisenc.so.2 ELF 7d041000-7d075000 Deferred libflac.so.8 ELF 7d075000-7d07c000 Deferred libasyncns.so.0 ELF 7d07c000-7d0ef000 Deferred libsndfile.so.1 ELF 7d0ef000-7d15e000 Deferred libpulsecommon-4.0.so ELF 7d15e000-7d169000 Deferred libjson-c.so.2 ELF 7d169000-7d1b8000 Deferred libpulse.so.0 ELF 7d1b8000-7d1e0000 Deferred winepulse<elf> \-PE 7d1c0000-7d1e0000 \ winepulse ELF 7d1e0000-7d202000 Deferred mmdevapi<elf> \-PE 7d1f0000-7d202000 \ mmdevapi ELF 7d202000-7d22d000 Deferred msacm32<elf> \-PE 7d210000-7d22d000 \ msacm32 ELF 7d22d000-7d2e7000 Deferred winmm<elf> \-PE 7d230000-7d2e7000 \ winmm ELF 7d2e7000-7d30d000 Deferred iphlpapi<elf> \-PE 7d2f0000-7d30d000 \ iphlpapi ELF 7d30d000-7d343000 Deferred ws2_32<elf> \-PE 7d310000-7d343000 \ ws2_32 ELF 7d343000-7d400000 Deferred windowscodecs<elf> \-PE 7d350000-7d400000 \ windowscodecs ELF 7d500000-7d50a000 Deferred libwrap.so.0 ELF 7d50a000-7d526000 Deferred wsock32<elf> \-PE 7d510000-7d526000 \ wsock32 ELF 7d526000-7d581000 Deferred libjpeg.so.8 ELF 7d599000-7d5c9000 Deferred p11-kit-trust.so ELF 7d5c9000-7d5d2000 Deferred librt.so.1 ELF 7d5d2000-7d5d9000 Deferred libffi.so.6 ELF 7d5d9000-7d5de000 Deferred libgpg-error.so.0 ELF 7d5de000-7d5f6000 Deferred libresolv.so.2 ELF 7d5f6000-7d5fa000 Deferred libkeyutils.so.1 ELF 7d5fa000-7d645000 Deferred libdbus-1.so.3 ELF 7d645000-7d681000 Deferred libp11-kit.so.0 ELF 7d681000-7d695000 Deferred libtasn1.so.6 ELF 7d695000-7d71c000 Deferred libgcrypt.so.11 ELF 7d71c000-7d728000 Deferred libkrb5support.so.0 ELF 7d728000-7d72d000 Deferred libcom_err.so.2 ELF 7d72d000-7d75d000 Deferred libk5crypto.so.3 ELF 7d75d000-7d81c000 Deferred libkrb5.so.3 ELF 7d81c000-7d82e000 Deferred libavahi-client.so.3 ELF 7d82e000-7d8f5000 Deferred libgnutls.so.26 ELF 7d8f5000-7d93b000 Deferred libgssapi_krb5.so.2 ELF 7d93b000-7d9a8000 Deferred libcups.so.2 ELF 7d9a8000-7d9ac000 Deferred libnss_mdns4_minimal.so.2 ELF 7d9ac000-7d9c0000 Deferred riched32<elf> \-PE 7d9b0000-7d9c0000 \ riched32 ELF 7d9c0000-7da00000 Deferred winspool<elf> \-PE 7d9d0000-7da00000 \ winspool ELF 7da00000-7daeb000 Deferred comdlg32<elf> \-PE 7da10000-7daeb000 \ comdlg32 ELF 7daeb000-7db25000 Deferred oledlg<elf> \-PE 7daf0000-7db25000 \ oledlg ELF 7db25000-7db5c000 Deferred uxtheme<elf> \-PE 7db30000-7db5c000 \ uxtheme ELF 7db5c000-7dbd8000 Deferred wininet<elf> \-PE 7db70000-7dbd8000 \ wininet ELF 7dbd8000-7dcdf000 Deferred comctl32<elf> \-PE 7dbe0000-7dcdf000 \ comctl32 ELF 7dcdf000-7df12000 Deferred shell32<elf> \-PE 7dcf0000-7df12000 \ shell32 ELF 7df12000-7dfb4000 Deferred urlmon<elf> \-PE 7df20000-7dfb4000 \ urlmon ELF 7dfb4000-7e027000 Deferred ieframe<elf> \-PE 7dfc0000-7e027000 \ ieframe ELF 7e027000-7e068000 Deferred usp10<elf> \-PE 7e030000-7e068000 \ usp10 ELF 7e068000-7e0e2000 Deferred shlwapi<elf> \-PE 7e080000-7e0e2000 \ shlwapi ELF 7e13b000-7e163000 Deferred mpr<elf> \-PE 7e140000-7e163000 \ mpr ELF 7e1a8000-7e1cd000 Deferred imm32<elf> \-PE 7e1b0000-7e1cd000 \ imm32 ELF 7e213000-7e219000 Deferred libxfixes.so.3 ELF 7e219000-7e224000 Deferred libxcursor.so.1 ELF 7e224000-7e234000 Deferred libxi.so.6 ELF 7e234000-7e238000 Deferred libxcomposite.so.1 ELF 7e238000-7e243000 Deferred libxrandr.so.2 ELF 7e243000-7e24e000 Deferred libxrender.so.1 ELF 7e24e000-7e254000 Deferred libxxf86vm.so.1 ELF 7e254000-7e258000 Deferred libxinerama.so.1 ELF 7e258000-7e25f000 Deferred libxdmcp.so.6 ELF 7e25f000-7e263000 Deferred libxau.so.6 ELF 7e263000-7e285000 Deferred libxcb.so.1 ELF 7e285000-7e3b9000 Deferred libx11.so.6 ELF 7e3b9000-7e3cc000 Deferred libxext.so.6 ELF 7e3cc000-7e3da000 Deferred libavahi-common.so.3 ELF 7e3e4000-7e476000 Deferred winex11<elf> \-PE 7e3f0000-7e476000 \ winex11 ELF 7e4cb000-7e4f4000 Deferred libexpat.so.1 ELF 7e4f4000-7e52f000 Deferred libfontconfig.so.1 ELF 7e52f000-7e557000 Deferred libpng12.so.0 ELF 7e557000-7e571000 Deferred libz.so.1 ELF 7e571000-7e611000 Deferred libfreetype.so.6 ELF 7e629000-7e75f000 Deferred oleaut32<elf> \-PE 7e640000-7e75f000 \ oleaut32 ELF 7e75f000-7e7e0000 Deferred rpcrt4<elf> \-PE 7e770000-7e7e0000 \ rpcrt4 ELF 7e7e0000-7e91c000 Deferred ole32<elf> \-PE 7e800000-7e91c000 \ ole32 ELF 7e91c000-7e936000 Deferred version<elf> \-PE 7e920000-7e936000 \ version ELF 7e936000-7e9a8000 Deferred advapi32<elf> \-PE 7e940000-7e9a8000 \ advapi32 ELF 7e9a8000-7eac5000 Deferred gdi32<elf> \-PE 7e9b0000-7eac5000 \ gdi32 ELF 7eac5000-7ec1f000 Deferred user32<elf> \-PE 7eae0000-7ec1f000 \ user32 ELF 7ec4e000-7ec5a000 Deferred libnss_files.so.2 ELF 7ec5a000-7ec66000 Deferred libnss_nis.so.2 ELF 7ec66000-7ec7f000 Deferred libnsl.so.1 ELF 7ec7f000-7ec88000 Deferred libnss_compat.so.2 ELF 7efba000-7f000000 Deferred libm.so.6 ELF b7392000-b7543000 Dwarf libc.so.6 ELF b7543000-b7548000 Deferred libdl.so.2 ELF b7549000-b7565000 Deferred libpthread.so.0 ELF b757d000-b7732000 Dwarf libwine.so.1 ELF b7734000-b7756000 Deferred ld-linux.so.2 ELF b7756000-b7757000 Deferred [vdso].so Threads: process tid prio (all id:s are in hex) 0000000e services.exe 0000001e 0 0000001d 0 00000014 0 00000010 0 0000000f 0 00000012 winedevice.exe 0000001c 0 00000018 0 00000017 0 00000013 0 0000001a plugplay.exe 00000020 0 0000001f 0 0000001b 0 00000021 explorer.exe 00000025 0 00000022 0 00000030 (D) C:\Program Files\Opera\Opera v1.6.5.exe 00000037 0 00000036 0 00000035 0 00000034 15 00000033 0 00000032 0 00000031 0 <== System information: Wine build: wine-1.6.2 Platform: i386 Host system: Linux Host version: 3.13.0-24-generic -- 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 44177] New: Guitar Pro 5: Long freezes during draw process of dashed lines ( P.M. or let ring markers)
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=44177 Bug ID: 44177 Summary: Guitar Pro 5: Long freezes during draw process of dashed lines (P.M. or let ring markers) Product: Wine Version: 3.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kitsunyan(a)inbox.ru Distribution: ArchLinux Created attachment 59941 --> https://bugs.winehq.org/attachment.cgi?id=59941 log Guitar Pro 5 always hangs when tries to draw dashed lines (like these https://imgur.com/GgvrEuq.png) The longer the line, the longer the freeze. CPU core is loaded to 100% during this freeze. Sometimes it even draws odd lines (https://imgur.com/1efGsF2.png) This bug is regression. About 6 months ago everything was fine. It begins ~4 months ago. I don't know what causes this problem so I started wine with WINEDEBUG=+all and tried to find where it hangs. I noticed a lot of gdi calls which can cause this hangs. I restarted wine with WINEDEBUG=+gdi and grabbed the log which I've attached to the bug. I'm using Arch Linux. WINEARCH=win32. -- 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 14

[Bug 40303] New: Control Data passed in DIALOGEX Resource passes pointer with offset sizeof(WORD)
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=40303 Bug ID: 40303 Summary: Control Data passed in DIALOGEX Resource passes pointer with offset sizeof(WORD) Product: Wine Version: 1.9.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: vendor2013(a)herdsoft.com Distribution: --- Created attachment 53942 --> https://bugs.winehq.org/attachment.cgi?id=53942 Sourcecode for a test program When DIALOGEX Resources contain Custom data like in: DEFPUSHBUTTON "OK", IDOK, 148, 6, 50, 14 { 1, 2, 3, 4, 5 } The pointer passed in WM_CREATE is two bytes higher than in windows. In Windows (Tested with Vista an Windows 7 64-Bit) it Points to the Number of Words, in Wine it points to the first data byte. Microsoft Specs for this stuff are here: https://msdn.microsoft.com/de-de/library/windows/desktop/ms645389%28v=vs.85… Attached file dialogtest.zip is sourcecode for a test program with a simple custom control that displays the passed control data. Bug is in Version 1.6.2 (Debian Jessie) and 1.9.5 (Last Download). My suggestion for a patch: --- wine-1.6.2.orig/dlls/user32/dialog.c +++ wine-1.6.2/dlls/user32/dialog.c @@ -234,7 +234,8 @@ static const WORD *DIALOG_GetControl32( TRACE("\n"); TRACE(" END\n" ); } - info->data = p + 1; + info->data = p; p += GET_WORD(p) / sizeof(WORD); } else info->data = NULL; -- 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 41356] New: The Crew(Uplay) won't launch[STAGING]
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=41356 Bug ID: 41356 Summary: The Crew(Uplay) won't launch[STAGING] Product: Wine Version: 1.9.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spleefer90(a)gmail.com Distribution: --- Created attachment 55708 --> https://bugs.winehq.org/attachment.cgi?id=55708 launching the game Using wine STAGING Absolutely no idea what's the problem. Running the game just stays at the uplay game loading screen 64 bit prefix -- 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 36

[Bug 40264] New: Iris Online cannot connect to login server
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=40264 Bug ID: 40264 Summary: Iris Online cannot connect to login server Product: Wine Version: 1.9.4 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: noscrubs.net(a)gmail.com Created attachment 53881 --> https://bugs.winehq.org/attachment.cgi?id=53881 Winsock trace from Linux and Mac OS X versions of wine. The game client cannot connect to the login server to authenticate the account. This works perfectly when running under the same version of Wine under Linux, and of course Windows. I have attached a short winsock trace that shows the differences when running under Linux and Mac OS X versions of Wine. I am also including a snippet of the client source relating to this log. The game client can be downloaded from http://noscrubs.net/downloads/NoScrubs_Iris_Online_Nov_2015.zip The launcher/patcher works fine apart from some HTML display issues. AppDB page: https://appdb.winehq.org/objectManager.php?sClass=version&iId=33421&iTestin… -- 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 17

[Bug 44485] New: makes Delphi 7 debugger generate new exceptions by itself (regression)
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=44485 Bug ID: 44485 Summary: makes Delphi 7 debugger generate new exceptions by itself (regression) Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: development(a)winomega.com Distribution: --- Created attachment 60433 --> https://bugs.winehq.org/attachment.cgi?id=60433 WINEDEBUG=+seh Starting with commit a75e3f734d32bd98df9017f1a94819d2b6dca85d, the Delphi 7 debugger behaves erratically after catching an exception generated by the debugged program. It generates new floating point arithmetic exceptions, making debugging impossible and forces the debugger application to abort. The test program is a trivial application which raises an exception when clicking on a button. I'm attaching a WINEDEBUG=+seh log. Also, here's an annotated excerpt describing what I'm doing when each of the traces show up: I start the program and click on the button. Then get this: trace:seh:raise_exception code=eedfade flags=1 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=00450767 trace:seh:raise_exception info[1]=00473dbc trace:seh:raise_exception info[2]=004736c0 trace:seh:raise_exception info[3]=00426c58 trace:seh:raise_exception info[4]=0033ef44 trace:seh:raise_exception info[5]=0033ef08 trace:seh:raise_exception info[6]=0033edc4 trace:seh:raise_exception eax=7b428e39 ebx=00000018 ecx=0033ed30 edx=0033eda8 esi=0033ef08 edi=0033ef44 trace:seh:raise_exception ebp=0033ed88 esp=0033ed04 cs=0023 ds=13002b es=4d43002b fs=0063 gs=006b flags=00000212 I press F9 (run) to resume execution. Then get these: trace:seh:call_stack_handlers calling handler at 0x433637 code=eedfade flags=1 trace:seh:call_stack_handlers handler at 0x433637 returned 1 trace:seh:call_stack_handlers calling handler at 0x433648 code=eedfade flags=1 trace:seh:__regs_RtlUnwind code=eedfade flags=3 trace:seh:__regs_RtlUnwind calling handler at 0x7bc81710 code=eedfade flags=3 trace:seh:__regs_RtlUnwind handler at 0x7bc81710 returned 1 trace:seh:__regs_RtlUnwind calling handler at 0x433637 code=eedfade flags=3 trace:seh:raise_exception code=eedfae1 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0043362c trace:seh:raise_exception eax=7b428e39 ebx=0043362c ecx=0033e3d0 edx=0033e448 esi=00000000 edi=0033ed1c trace:seh:raise_exception ebp=0033e428 esp=0033e3a4 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000212 trace:seh:__regs_RtlUnwind handler at 0x403844 returned 1 trace:seh:raise_exception code=eedfae0 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0043364d trace:seh:raise_exception eax=7b428e39 ebx=0043364d ecx=0033e890 edx=0033e90c esi=00000000 edi=0033f104 trace:seh:raise_exception ebp=0033e8e8 esp=0033e864 cs=330023 ds=002b es=002b fs=0063 gs=006b flags=00000212 trace:seh:raise_exception code=c0000092 flags=0 addr=0x7ecdb6be ip=7ecdb6c1 tid=0031 trace:seh:raise_exception eax=00117f68 ebx=7ed32000 ecx=0013e398 edx=0013e398 esi=0033dc40 edi=00117f68 trace:seh:raise_exception ebp=0033db98 esp=0033db70 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010202 trace:seh:call_stack_handlers calling handler at 0x44f399 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x44f399 returned 1 trace:seh:call_stack_handlers calling handler at 0x44f467 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x44f467 returned 1 trace:seh:call_stack_handlers calling handler at 0x403664 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x403664 returned 1 trace:seh:call_stack_handlers calling handler at 0x433637 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x433637 returned 1 trace:seh:call_stack_handlers calling handler at 0x433648 code=c0000092 flags=0 trace:seh:raise_exception code=eedfae4 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0033d84c trace:seh:raise_exception info[1]=00473dfc trace:seh:raise_exception eax=7b428e39 ebx=00000004 ecx=0033d690 edx=0033d70c esi=0033d84c edi=0033db18 trace:seh:raise_exception ebp=0033d6e8 esp=0033d664 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000212 A MessageBox is shown: "Debugger Exception Notification: Project xxx.exe raised exception class EInvalidOp with message 'Invalid floating point operation'. Process stopped. Use Step or Run to continue." I click OK. Debugger stops at vcl/Controls.pas class, at CallWindowProc; it appears as if the exception is triggered in CallWindowProc itself, but I can't tell for sure as the debugger environment is unreliable (if I were to single-step, it keeps triggering new exceptions). I press F9 again.... trace:seh:__regs_RtlUnwind code=c0000092 flags=2 trace:seh:__regs_RtlUnwind calling handler at 0x7bc81710 code=c0000092 flags=2 trace:seh:__regs_RtlUnwind handler at 0x7bc81710 returned 1 trace:seh:__regs_RtlUnwind calling handler at 0x44f399 code=c0000092 flags=2 trace:seh:raise_exception code=eedfae1 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0044f33f trace:seh:raise_exception eax=7b428e39 ebx=0044f33f ecx=0033d1b0 edx=0033d228 esi=00000000 edi=0033db18 trace:seh:raise_exception ebp=0033d208 esp=0033d184 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000216 trace:seh:__regs_RtlUnwind handler at 0x403844 returned 1 trace:seh:__regs_RtlUnwind calling handler at 0x44f467 code=c0000092 flags=2 trace:seh:raise_exception code=eedfae1 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0044f453 trace:seh:raise_exception eax=7b428e39 ebx=0044f453 ecx=0033d1b0 edx=0033d228 esi=00000000 edi=0033db18 trace:seh:raise_exception ebp=0033d208 esp=0033d184 cs=110023 ds=002b es=33002b fs=0063 gs=7bc8006b flags=00000216 trace:seh:__regs_RtlUnwind handler at 0x403844 returned 1 trace:seh:__regs_RtlUnwind calling handler at 0x403664 code=c0000092 flags=2 trace:seh:raise_exception code=eedfae1 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=00403669 trace:seh:raise_exception eax=7b428e39 ebx=00403669 ecx=0033d1b0 edx=0033d228 esi=00000000 edi=0033db18 trace:seh:raise_exception ebp=0033d208 esp=0033d184 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000216 trace:seh:__regs_RtlUnwind handler at 0x403844 returned 1 trace:seh:__regs_RtlUnwind calling handler at 0x433637 code=c0000092 flags=2 trace:seh:raise_exception code=eedfae1 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0043362c trace:seh:raise_exception eax=7b428e39 ebx=0043362c ecx=0033d1b0 edx=0033d228 esi=00000000 edi=0033db18 trace:seh:raise_exception ebp=0033d208 esp=0033d184 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000216 trace:seh:__regs_RtlUnwind handler at 0x403844 returned 1 trace:seh:raise_exception code=eedfae0 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0043364d trace:seh:raise_exception eax=7b428e39 ebx=0043364d ecx=0033d670 edx=0033d6ec esi=00000000 edi=0033fb94 trace:seh:raise_exception ebp=0033d6c8 esp=0033d644 cs=330023 ds=002b es=002b fs=0063 gs=006b flags=00000216 trace:seh:raise_exception code=c0000092 flags=0 addr=0x7ece39b7 ip=7ece39d6 tid=0031 trace:seh:raise_exception eax=00000003 ebx=7ed32000 ecx=7b43c5ac edx=00000000 esi=00141214 edi=00000001 trace:seh:raise_exception ebp=0033ca18 esp=0033c8a0 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010297 trace:seh:call_stack_handlers calling handler at 0x44f399 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x44f399 returned 1 trace:seh:call_stack_handlers calling handler at 0x44f467 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x44f467 returned 1 trace:seh:call_stack_handlers calling handler at 0x403664 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x403664 returned 1 trace:seh:call_stack_handlers calling handler at 0x44f159 code=c0000092 flags=0 trace:seh:raise_exception code=eedfae4 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0033c57c trace:seh:raise_exception info[1]=00473e40 trace:seh:raise_exception eax=7b428e39 ebx=00000004 ecx=0033c3c0 edx=0033c43c esi=0033c57c edi=0033c848 trace:seh:raise_exception ebp=0033c418 esp=0033c394 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000212 Again: "Debugger Exception Notification: Project xxx.exe raised exception class EInvalidOp with message 'Invalid floating point operation'. Process stopped. Use Step or Run to continue." I press OK. Debugged test app is terminated this time. Before exitting a seh error shows up: err:seh:setup_exception_record stack overflow 952 bytes in thread 0031 eip f73fb162 esp 00240f78 stack 0x240000-0x241000-0x340000 -- 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 20104] New: Fujiprint/Fotokasten albums cannot be created due to missing richtext query interface
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

http://bugs.winehq.org/show_bug.cgi?id=20104 Summary: Fujiprint/Fotokasten albums cannot be created due to missing richtext query interface Product: Wine Version: 1.1.29 Platform: PC URL: http://www.fotokasten.de/index.php?ftkPage=static&ftkV iew=ftksoftware OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: cweiske(a)cweiske.de Running the "fotokasten" photo album creation software fails to create certain photo books with the following error: > fixme:richedit:fnTextSrv_QueryInterface Unknown interface: > {01c25500-4268-11d1-883a-3c8b00c10000} > fixme:richedit:fnTextSrv_OnTxInplaceDeactivate 0x3a1e8e0: STUB How to reproduce: 1. Run software 2. Click on tab "Fotobücher" 3. Click on "Fotobücher" icon 4. Click on "Fun" 5. Click on "Fun A4" 6. A loading window appears but is hidden soon after. When using Fotobücher->Fotobücher->Soft->A4, the richtext window has not to be shown, and I get to the next window (meaning it works without richtext). -- 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 10913] New: start.exe doesn't support optional process title argument
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

http://bugs.winehq.org/show_bug.cgi?id=10913 Summary: start.exe doesn't support optional process title argument Product: Wine Version: CVS/GIT Platform: Other URL: http://jedit.org OS/Version: other Status: NEW Keywords: download Severity: normal Priority: P2 Component: wine-programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Running real Java apps under the latest Sun win32 JRE on Wine seems like a fine stress test, even though in many cases users should run with the Linux JRE instead. The Sun JRE and jEdit install ok, but jedit has many startup problems. Here's the first one. Invoking it with the batch file provided by jEdit fails. Here's what's in the batch file: start "jEdit startup" "c:\windows\system32\javaw.exe" -Xms64M -Xmx192M -jar "C:\Program Files\jEdit\jedit.jar" -reuseview %* And here's what happens when you run it: $ cd ~/.wine/drive_c/Program Files/jEdit $ ~/wine-git/wine cmd /c jedit.bat fixme:exec:SHELL_execute flags ignored: 0x00000500 trace:process:CreateProcessW app (null) cmdline L"jEdit startup c:\\windows\\system32\\javaw.exe -Xms64M -Xmx192M -jar \"C:\\Program Files\\jEdit\\jedit.jar\" -reuseview" trace:process:find_exe_file looking for L"jEdit" trace:process:find_exe_file Trying native exe L"c:\\windows\\system32\\jEdit.exe" ... trace:process:find_exe_file Trying built-in exe L"c:\\windows\\system32\\jEdit startup.exe" ... trace:process:find_exe_file looking for L"jEdit startup c:\\windows\\system32\\javaw.exe -Xms64M -Xmx192M -jar \"C:\\Program Files\\jEdit\\jedit.jar\" -reuseview" Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found So it seems that start takes an optional process title argument. Sure enough, http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en… documents it. Who knew? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 20

[Bug 42508] New: start.exe does not detect its title argument when it should ( breaking .e.g URL opening in League of Legends)
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=42508 Bug ID: 42508 Summary: start.exe does not detect its title argument when it should (breaking .e.g URL opening in League of Legends) Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: hydratech(a)gmail.com Distribution: --- Created attachment 57397 --> https://bugs.winehq.org/attachment.cgi?id=57397 Trace showing League of Legends Client attempting to open a URL. When start.exe is invoked, its first argument in quotes that is not an argument of the application to be executed should be interpreted as the console title. Wine's start.exe fails to do so. -- How to reproduce -- Running the following line in Wine's cmd should open a URL in your browser: Z:\>start "" https://winehq.org/ the actual result is an application not found error. On Windows the same line opens the website as expected. -- Why this is a bug -- I know this was marked as fixed in bug 10913 but the reasoning was incorrect. The argument for stating the bug was fixed was, that when \"escaping your quotes\" in cmd to the title was parsed. This is however not consistent with with Windows behaviour. As explained at the end of that bug report, if you escape your quotes in Wine's cmd start.exe parses the argument as the console title, i.e.: Z:\>start \"hello\" cmd I will now clarify why this is incorrect by showing Windows' behaviour. The following command lines are not equivalent on Windows: C:\>start hello.exe vs. C:\>start "hello.exe" The latter will open a new cmd window titled hello.exe whereas the former attempts to execute an application named hello.exe. In other words cmd's start built-in parses its own command-line checking wether quotes where used. In fact escaping the quotes using back-slashes is invalid as it tries start a process named \hello.exe\. I have tested this on both Windows 7 and Windows XP. In other words, this is invalid: C:>start \"hello.exe\" To illustrate how unintuitive this Windows behaviour is: C:>start "C:\Program Files\Application\hello.exe" Few would guess this actually opens a console titled as such, instead of running an application. That's why I can understand the maintainers would think the bug was fixed. Wine will however correctly emulate unescaped quote-senstive behaviour with the echo built-in: Z:\>echo hoi hoi Z:\>echo "hoi" "hoi" We can see echo being "aware" of the quotes and correctly displaying them; behaviour identical to Windows' echo built-in. Looking at the wine source, start.exe relies on its "argv" parameter instead of using GetCommandLine() and thereby accessing the unmodified command-line. As a consequence the difference between a quoted argument and a non-quoted argument is lost as CreateProcess strips the quotes off the parameters when passing them to execve(). To quote the source of Wine's cmd.exe (wcmdmain.c): /* Can't use argc/argv as it will have stripped quotes from parameters * meaning cmd.exe /C echo "quoted string" is impossible */ It should now be evident that start.exe should either become a wrapper around cmd.exe's built-in start function, invoking cmd and let cmd itself implement start.exe's actual behaviour, or implement GetCommandLine() based argument parsing similar to cmd.exe's within start.exe, leading to duplicated command-line parsing code. Both are not ideal solutions. -- Why does this bug matter? -- There are actually Windows applications relying on this behaviour to open URLs in the user's browser. As an example, League of Legends executes the following shell command to open a URL: cmd.exe /c start "" "<url here>" In other words, League instructs start to launch an untitled shell window with a URL as application, effectively causing the shell to pass it to the browser. However, wine's start.exe interprets this as League trying to execute an empty string as executable name, with a URL as argument. I have attached the relevant output running League with WINEDEBUG=cmd,start,process,exec set. I will speculate that more applications will run into this exact same issue. League's client is based on CEF and it might very well be CEF which implements this style of external URL opening, furthermore there is documentation recommending the use of empty quotes as console title argument when invoking start to prevent it from accidentally parsing follow up arguments in quotes as the console title, think "C:\Program Files\etc...", establishing this as a pattern that might well have been adopted by other applications. See: https://ss64.com/nt/start.html I will also say that, given some instruction, I will be glad to help fixing this bug and write any necessary code. There is actually another issue with current start.exe's console title parsing which I will submit as a separate issue. That issue is however, significantly easier to fix. Finally this also means wine's current handling of command-line arguments might need fixing as: $ wine start '""' "http://winehq.og" will break in a fixed version of 'start.exe', while it should work. For this I will file yet another issue, although the necessity of this fix is debatable. -- 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 13

[Bug 31644] New: glMapBufferRange is extremely slow while playing Resident Evil 5 ( happens only on nvidia binary driver )
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

http://bugs.winehq.org/show_bug.cgi?id=31644 Bug #: 31644 Summary: glMapBufferRange is extremely slow while playing Resident Evil 5 ( happens only on nvidia binary driver ) Product: Wine Version: 1.5.12 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: tizbac2(a)gmail.com Classification: Unclassified Calls to glMapBufferRange are extremely slow on nvidia drivers with resident evil 5, if this should be reported to nvidia instead just close it over 90% of frame time is taken by glMapBufferRange -- 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 20