February 2017 - Wine-Bugs - list.winehq.org

[Bug 5402] Multiple MFC-based apps crash during non-modal child dialog control creation with active window being zero (Canon PhotoStitch 3.1.13, Flexible Renamer v8.4)
by wine-bugs＠winehq.org Feb. 9, 2017

Feb. 9, 2017

https://bugs.winehq.org/show_bug.cgi?id=5402 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #43 from winetest(a)luukku.com --- The attached program at url field works just fine with wine-staging 2.1 now. Ty for fixing this long standing bug. Who knows how many other bugs it might fix now. -- 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 0

[Bug 37425] New: After installing Ulead Gif Animator with wine I got the message that programm has to be closed immediately because of a unspecified bug. Please get information by attachment file.
by wine-bugs＠winehq.org Feb. 9, 2017

Feb. 9, 2017

https://bugs.winehq.org/show_bug.cgi?id=37425 Bug ID: 37425 Summary: After installing Ulead Gif Animator with wine I got the message that programm has to be closed immediately because of a unspecified bug. Please get information by attachment file. Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ua-holland(a)t-online.de Distribution: --- Ulead Gif Animator complete Installation with win does not run. See attached message. -- 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 22

[Bug 42399] New: Implement Windows Script Host
by wine-bugs＠winehq.org Feb. 8, 2017

Feb. 8, 2017

https://bugs.winehq.org/show_bug.cgi?id=42399 Bug ID: 42399 Summary: Implement Windows Script Host Product: Wine-gecko Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gecko-unknown Assignee: jacek(a)codeweavers.com Reporter: kolan_n(a)mail.ru Distribution: --- Wine has wscript.exe, cscript.exe and JScript.dll, but they seem to do nothing. This prevents some software embedding WSH from working properly. The solution can be some open-source JS engine like SpiderMonkey or v8 wrapped into a a library providing WSH API. Probably you can reuse node.js which looks similar to WSH in the sense it has API for network requests and FS manipulation. Of course it is possible to install Microsoft's WSH, but it surely contain vulnerabilities since it have not been updated for years and lacks modern JS features. -- 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 38598] New: Crash when UpdateLayeredWindow with large window & complicated transparency
by wine-bugs＠winehq.org Feb. 8, 2017

Feb. 8, 2017

https://bugs.winehq.org/show_bug.cgi?id=38598 Bug ID: 38598 Summary: Crash when UpdateLayeredWindow with large window & complicated transparency Product: Wine Version: 1.7.42 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: m13253(a)hotmail.com Distribution: --- The program that causes the bug is here: https://gist.github.com/m13253/092b94c7bd526a9a4e57 A .exe executable is also included in the Git repo. The program is tested to be fine under Windows 10. Upon successful execution, the program creates a transparent panel with spotted background on the right half of the screen. Wine failed with the following messages: X Error of failed request: BadLength (poly request too large or internal Xlib length error) Major opcode of failed request: 33 (X_GrabKey) Serial number of failed request: 219 Current serial number in output stream: 227 Depending on the window size, the "major opcode" may vary. This issue only occurs when: Source line 72-76: The window size is large enough and Source line 115-131: The RGBA bitmap is complicated, especially the alpha channel Additional info: Distribution: ArchLinux It is a WINEARCH=win32 prefix. libx11: 1.6.3-1 xorg-server: 1.17.1-5 mesa: 10.5.4-1 gnome-shell: 3.16.1-2 -- 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 4

[Bug 21397] New: LookupAccountName cannot retrieve a 'groups' SID
by wine-bugs＠winehq.org Feb. 8, 2017

Feb. 8, 2017

http://bugs.winehq.org/show_bug.cgi?id=21397 Summary: LookupAccountName cannot retrieve a 'groups' SID Product: Wine Version: 1.1.36 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: advapi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: us(a)edmeades.me.uk Debugging an application I found the cause of the first failure is that the software installs a 'group' (which fails with a fixme). Post install, I created a group (addgroup) but the application calls LookupAccountName to retrieve the SID of that created group. You can hack around this (if LookupAccountName fails, query the current user and re-call the function to get it's sid) but looking at the function there is complete support missing for anything other than the current user. Ideally it should call (something like getgrent?) and if it finds a group, map it to a SID somehow (perhaps end the SID with the gid?). It could handle querying other users as well in a similar way (getpwnam?) JEWMQ -- 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 9221] Force Feedback doesn' t work but does after little source modification
by wine-bugs＠winehq.org Feb. 8, 2017

Feb. 8, 2017

https://bugs.winehq.org/show_bug.cgi?id=9221 Adam Williamson <adamw(a)happyassassin.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|adamw(a)happyassassin.net | -- 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 0

[Bug 9221] Force Feedback doesn' t work but does after little source modification
by wine-bugs＠winehq.org Feb. 8, 2017

Feb. 8, 2017

https://bugs.winehq.org/show_bug.cgi?id=9221 --- Comment #46 from madbad82(a)gmail.com --- (In reply to Bruno Jesus from comment #44) > (In reply to madbad82 from comment #43) > > Created attachment 57205 [details] > > backtrace > > > > Backtrace of "wine control" with the experimental KLGDFF Logitec driver > > There are some well-known crashes in joy.cpl but since my controllers don't > support the other effects I can't reproduce myself so it is good that you > can test this. If you are able to compile Wine I can attach some patches. > > Anyway, please attach a +dinput patch when playing with all effects > sequentially. Attached the new log with +dinput. Never compiled wine but should not be too hard, I will be glad to test your patches! -- 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 0

[Bug 9221] Force Feedback doesn' t work but does after little source modification
by wine-bugs＠winehq.org Feb. 8, 2017

Feb. 8, 2017

https://bugs.winehq.org/show_bug.cgi?id=9221 --- Comment #45 from madbad82(a)gmail.com --- Created attachment 57214 --> https://bugs.winehq.org/attachment.cgi?id=57214 console log with +dinput (and the experimental logitec driver) -- 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 0

[Bug 39988] New: winepath -w wrong output with path longer 260
by wine-bugs＠winehq.org Feb. 8, 2017

Feb. 8, 2017

https://bugs.winehq.org/show_bug.cgi?id=39988 Bug ID: 39988 Summary: winepath -w wrong output with path longer 260 Product: Wine Version: 1.9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: s3141p(a)gmail.com Distribution: --- When the input $pathname is longer than 260 characters wine -w $pathname 1. truncates the converted output path at 260 characters 2. appends some garbage characters to it 3. reports no error and exits with status 0 I think fixing #3 as a minimum is important; at least exit 1, possibly print an error message. Fixing #2? Why is it printing garbage characters? Buffer overrun? And please consider changing #1 by extending support to paths > 260 characters. After all, if I convert the same path by hand and feed it to a Windows application it has no problems dealing with it. So the 260-character limit of winepath -w seems rather artificial to me. I create long linux paths with mkdir -p /tmp/aaa/bbb/ccc/ddd/eee/ touch /tmp/aaa/bbb/ccc/ddd/eee/$(dd if=/dev/zero count=1 bs=260 | tr '\000' a) # which creates /tmp/aaa/bbb/ccc/ddd/eee/aaaaaaaa... Thanks. -- 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 36199] New: valgrind shows several warnings under crypt32/tests/chain.c
by wine-bugs＠winehq.org Feb. 8, 2017

Feb. 8, 2017

https://bugs.winehq.org/show_bug.cgi?id=36199 Bug ID: 36199 Summary: valgrind shows several warnings under crypt32/tests/chain.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 48320 --> https://bugs.winehq.org/attachment.cgi?id=48320 valgrind log A few in glibc: ==17802== Thread 2: ==17802== Invalid read of size 1 ==17802== at 0x40187FA: strcmp (strcmp.S:34) ==17802== by 0x4008925: _dl_map_object (dl-load.c:2113) ==17802== by 0x4013383: dl_open_worker (dl-open.c:224) ==17802== by 0x400F1F5: _dl_catch_error (dl-error.c:187) ==17802== by 0x4012D93: _dl_open (dl-open.c:650) ==17802== by 0x435093A: do_dlopen (dl-libc.c:87) ==17802== by 0x400F1F5: _dl_catch_error (dl-error.c:187) ==17802== by 0x4350A2A: dlerror_run (dl-libc.c:46) ==17802== by 0x4350AB0: __libc_dlopen_mode (dl-libc.c:163) ==17802== by 0x4221819: pthread_cancel_init (unwind-forcedunwind.c:52) ==17802== by 0x42219FB: _Unwind_ForcedUnwind (unwind-forcedunwind.c:129) ==17802== by 0x421F732: __pthread_unwind (unwind.c:129) ==17802== by 0x421A080: pthread_exit (pthreadP.h:280) ==17802== by 0x7BC8E1A9: terminate_thread (thread.c:349) ==17802== by 0x7BC87009: ??? (signal_i386.c:2571) ==17802== by 0x6A5F357: ??? ==17802== by 0x4218F92: start_thread (pthread_create.c:309) ==17802== by 0x431D7ED: clone (clone.S:129) ==17802== Address 0x693d913 is on thread 1's stack ==17802== ==17802== Invalid read of size 4 ==17802== at 0x4352239: _Unwind_IteratePhdrCallback (unwind-dw2-fde-glibc.c:112) ==17802== by 0x43503E2: dl_iterate_phdr (dl-iteratephdr.c:76) ==17802== by 0x4352AF9: _Unwind_Find_FDE (unwind-dw2-fde-glibc.c:267) ==17802== by 0x6B9E336: ??? (in /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/32/libgcc_s.so.1) ==17802== by 0x6B9EB21: ??? (in /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/32/libgcc_s.so.1) ==17802== by 0x6B9F10F: _Unwind_ForcedUnwind (in /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/32/libgcc_s.so.1) ==17802== by 0x42219F1: _Unwind_ForcedUnwind (unwind-forcedunwind.c:137) ==17802== by 0x421F732: __pthread_unwind (unwind.c:129) ==17802== by 0x421A080: pthread_exit (pthreadP.h:280) ==17802== by 0x7BC8E1A9: terminate_thread (thread.c:349) ==17802== by 0x7BC87009: ??? (signal_i386.c:2571) ==17802== by 0x6A5F357: ??? ==17802== by 0x4218F92: start_thread (pthread_create.c:309) ==17802== by 0x431D7ED: clone (clone.S:129) ==17802== Address 0x693c034 is on thread 1's stack ==17802== ==17802== Thread 1 crypt32_test.exe.so: ==17802== Jump to the invalid address stated on the next line ==17802== at 0x693E820: ??? (in /lib32/libresolv-2.19.so) ==17802== by 0x425F4E8: __run_exit_handlers (exit.c:82) ==17802== by 0x425F54C: exit (exit.c:104) ==17802== by 0x7BC68772: NtTerminateProcess (process.c:63) ==17802== by 0x7BC5941B: RtlExitUserProcess (loader.c:2538) ==17802== by 0x7B868D09: ??? (process.c:2668) ==17802== Address 0x693e820 is on thread 1's stack ==17802== and several possible leaks: ==17802== 20 bytes in 1 blocks are possibly lost in loss record 50 of 427 ==17802== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==17802== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==17802== by 0x514398B: CryptMemAlloc (main.c:124) ==17802== by 0x511E0A9: CertAddStoreToCollection (collectionstore.c:519) ==17802== by 0x5164B4B: CRYPT_SysOpenStoreW (store.c:592) ==17802== by 0x5165ADF: CertOpenStore (store.c:907) ==17802== by 0x51136FD: CRYPT_CreateChainEngine (chain.c:130) ==17802== by 0x511394F: get_chain_engine (chain.c:175) ==17802== by 0x511ADC0: CertGetCertificateChain (chain.c:2894) ==17802== by 0x4E618AA: testVerifyCertChainPolicy (chain.c:4790) ==17802== by 0x4E61C4C: func_chain (chain.c:4844) ==17802== by 0x4EB7F67: run_test (test.h:584) ==17802== by 0x4EB8356: main (test.h:654) ==17802== ==17802== 60 bytes in 3 blocks are possibly lost in loss record 197 of 427 ==17802== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==17802== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==17802== by 0x514398B: CryptMemAlloc (main.c:124) ==17802== by 0x5157661: ContextPropertyList_SetProperty (proplist.c:132) ==17802== by 0x515788F: ContextPropertyList_Copy (proplist.c:215) ==17802== by 0x511E9AF: Context_CopyProperties (context.c:130) ==17802== by 0x510AB6C: Cert_clone (cert.c:139) ==17802== by 0x5163664: MemStore_addContext (store.c:151) ==17802== by 0x5163A35: MemStore_addCert (store.c:243) ==17802== by 0x510B119: add_cert_to_store (cert.c:263) ==17802== by 0x510B27F: CertAddCertificateContextToStore (cert.c:287) ==17802== by 0x510A852: CertAddEncodedCertificateToStore (cert.c:65) ==17802== by 0x515E94A: add_ms_root_certs (rootstore.c:732) ==17802== by 0x515EB12: create_root_store (rootstore.c:808) ==17802== by 0x515EC6C: CRYPT_RootOpenStore (rootstore.c:829) ==17802== by 0x516435C: CRYPT_SysRegOpenStoreW (store.c:435) ==17802== by 0x5165ADF: CertOpenStore (store.c:907) ==17802== by 0x5164BAF: CRYPT_SysOpenStoreW (store.c:604) ==17802== by 0x5165ADF: CertOpenStore (store.c:907) ==17802== by 0x51136FD: CRYPT_CreateChainEngine (chain.c:130) ==17802== ==17802== 96 bytes in 1 blocks are possibly lost in loss record 294 of 427 ==17802== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==17802== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==17802== by 0x61ACD34: heap_alloc_zero (internet.h:121) ==17802== by 0x61ADCA1: create_netconn (netconnection.c:369) ==17802== by 0x619CFF2: open_http_connection (http.c:4826) ==17802== by 0x619D68C: HTTP_HttpSendRequestW (http.c:4972) ==17802== by 0x619EE2C: HttpSendRequestExW (http.c:5511) ==17802== by 0x61643F8: HTTP_RetrieveEncodedObjectW (cryptnet_main.c:933) ==17802== by 0x6165930: CryptRetrieveObjectByUrlW (cryptnet_main.c:1479) ==17802== by 0x5118CA0: CRYPT_FindIssuer (chain.c:2039) ==17802== by 0x51193A2: CRYPT_GetIssuer (chain.c:2168) ==17802== by 0x511952F: CRYPT_BuildSimpleChain (chain.c:2200) ==17802== by 0x511976F: CRYPT_GetSimpleChainForCert (chain.c:2247) ==17802== by 0x5119885: CRYPT_BuildCandidateChainFromCert (chain.c:2277) ==17802== by 0x511AE8B: CertGetCertificateChain (chain.c:2914) ==17802== by 0x4E5F02E: testGetCertChain (chain.c:3996) ==17802== by 0x4E61C51: func_chain (chain.c:4845) ==17802== by 0x4EB7F67: run_test (test.h:584) ==17802== by 0x4EB8356: main (test.h:654) ==17802== etc. (full log attached) -- 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