wine-bugs November 2015

wine-bugs@winehq.org

1 participants
7945 discussions

[Bug 38598] New: Crash when UpdateLayeredWindow with large window & complicated transparency
by wine-bugs＠winehq.org 08 Feb '17

08 Feb '17

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 08 Feb '17

08 Feb '17

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 36199] New: valgrind shows several warnings under crypt32/tests/chain.c
by wine-bugs＠winehq.org 08 Feb '17

08 Feb '17

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

[Bug 35490] New: After SimCity 2013 updates: d3d_shader:shader_sm4_read_src_param Unhandled swizzle type 0.
by wine-bugs＠winehq.org 06 Feb '17

06 Feb '17

http://bugs.winehq.org/show_bug.cgi?id=35490 Bug ID: 35490 Summary: After SimCity 2013 updates: d3d_shader:shader_sm4_read_src_param Unhandled swizzle type 0. Product: Wine Version: 1.7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: eric.ladner(a)gmail.com Classification: Unclassified Created attachment 47376 --> http://bugs.winehq.org/attachment.cgi?id=47376 basic output on the command line It used to run ok (although both Origin and SimCity were a nightmare to install). After a recent update, though when starting SimCity it never shows the splash screen and spews this until you kill the process: fixme:d3d_shader:shader_sm4_read_src_param Unhandled swizzle type 0. I let it run for about 10 seconds and it spit out 11 million errors (log attached). If you want a more detailed log, let me know what options you'd like. -- 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 37398] New: Urban Assault black screen when using software renderer and DDSCAPS_SYSTEMMEMORY
by wine-bugs＠winehq.org 06 Feb '17

06 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=37398 Bug ID: 37398 Summary: Urban Assault black screen when using software renderer and DDSCAPS_SYSTEMMEMORY Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: erich.e.hoover(a)gmail.com Depends on: 37307 Regression SHA1: b464067313bff1fd9a25b284b48a252025c4504f Distribution: --- Created attachment 49735 --> https://bugs.winehq.org/attachment.cgi?id=49735 Workaround Once Bug #37307 is resolved then Urban Assault runs into another issue (at least, when using the software renderer). The game has a black screen and just hangs there, apparently due to an unexpected DDSCAPS_SYSTEMMEMORY capability being set. Workaround attached. Note: This commit is later moved (commit 9443c95a895a530fdbbb607758f674467e2010c7), but the issue persists. -- 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 32988] New: StudioTax 2012 Installer stops with Error 67108864
by wine-bugs＠winehq.org 05 Feb '17

05 Feb '17

http://bugs.winehq.org/show_bug.cgi?id=32988 Bug #: 32988 Summary: StudioTax 2012 Installer stops with Error 67108864 Product: Wine Version: 1.5.24 Platform: x86-64 URL: http://www.studiotax.com/en/?page=2 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: jchevrier(a)gmail.com Classification: Unclassified Created attachment 43586 --> http://bugs.winehq.org/attachment.cgi?id=43586 Log of StudioTax2012 installer StudioTax 2012 installer stops with error 67108864 (presented in a dialog, see screenshot). Clicking 'OK' brings up another similar error dialog with a different error number, clicking on that dialog brings up another and so on. Prerequisite: 'winetricks dotnet40' and the installer must be run from the C: drive (or at least it doesn't like being run from Z:) or the installer fails earlier with an 'Invalid command line' error dialog. Website suggests that .NET 2.0 SP2 is required but installing dotnet20sp2 via winetricks causes the installer to fail much earlier complaining about lack of space. Attached +msi,+msidb as it appears to be MSI related. -- 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 34864] New: K32EnumProcessModulesEx not implemented in 64-bit
by wine-bugs＠winehq.org 05 Feb '17

05 Feb '17

http://bugs.winehq.org/show_bug.cgi?id=34864 Bug #: 34864 Summary: K32EnumProcessModulesEx not implemented in 64-bit Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: audvare(a)gmail.com Classification: Unclassified Created attachment 46472 --> http://bugs.winehq.org/attachment.cgi?id=46472 crash log Call of Duty Ghosts uses 'PE32+' EXE to start up in 32-bit, but ultimately requires a 64-bit set up to run. It would seem like it probably does this so it can at least tell the user of a 32-bit system that they need to have a 64-bit set up to run. It calls this function at start. I replaced psapi.dll with one from my Windows 7 installation (because PSAPI.EnumProcessModulesEx is not implemented in 64-bit), but after that the call is forwarded to kernel32 K32EnumProcessModulesEx. -- 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 38527] New: Tab controls do not honor parent changes
by wine-bugs＠winehq.org 04 Feb '17

04 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=38527 Bug ID: 38527 Summary: Tab controls do not honor parent changes Product: Wine Version: 1.7.34 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: pietro10(a)mac.com Distribution: --- Created attachment 51397 --> https://bugs.winehq.org/attachment.cgi?id=51397 Test program source code Currently the wine implementation of the comctl32 tab control gets its parent window once and caches it. While it's true that on real Windows some controls do this, the tab control is not one of them in my tests. The attached program is an example test. It creates two windows, an empty window and a full window. It then creates a tab control on the empty window, changes its parent to the full window, adds a few pages, and shows both windows. If you click on a tab to change pages, you should see a message on stdout telling you which parent window received the TCN_SELCHANGE notification. On real Windows, both with Common Controls v5 and v6, I see notification received on full window On wine, I see notification received on empty winddow (The test program does no error checking. By default it runs with Common Controls 5; with the first argument set to comctl6 it will run with Common Controls 6.) This is wine-1.7.34 built from source, Windows XP 32-bit, and Windows 7 64-bit. 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 5

[Bug 23775] New: Text box is too small in 16-bit program. Only one line high, should be two.
by wine-bugs＠winehq.org 04 Feb '17

04 Feb '17

http://bugs.winehq.org/show_bug.cgi?id=23775 Summary: Text box is too small in 16-bit program. Only one line high, should be two. Product: Wine Version: 1.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: markk(a)clara.co.uk Created an attachment (id=29800) --> (http://bugs.winehq.org/attachment.cgi?id=29800) Stellar Explorer 2.0b demo The 16-bit game Stellar Explorer 2.0b (attached) shows a problem with the size of a text box. The text box at the upper left of the window should show two lines of text. Running under Wine, it's only one line high and the scroll buttons at the right side consequently appear squashed. Run stellar2.exe. Click through the initial dialog boxes then select File->New from the menu and click OK. -- 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 39704] New: UC Browser 5.5.7608.1012 crashes immediately
by wine-bugs＠winehq.org 04 Feb '17

04 Feb '17

https://bugs.winehq.org/show_bug.cgi?id=39704 Bug ID: 39704 Summary: UC Browser 5.5.7608.1012 crashes immediately Product: Wine Version: 1.8-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dmn2004404(a)gmail.com Distribution: --- Created attachment 52946 --> https://bugs.winehq.org/attachment.cgi?id=52946 Crash dump for UC Browser 5.5.7608.1012 on Sun Nov 29, 2015. UC Browser 5.5.7608.1012 crashes immediately on launch. Crash dump is 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 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs November 2015