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

[Bug 39959] New: Growtopia v2.11 fails to run with unhandled exception (2.09 did run ok)
by wine-bugs＠winehq.org Jan. 4, 2019

Jan. 4, 2019

https://bugs.winehq.org/show_bug.cgi?id=39959 Bug ID: 39959 Summary: Growtopia v2.11 fails to run with unhandled exception (2.09 did run ok) 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: wine.hq(a)jyge.net Distribution: --- Created attachment 53389 --> https://bugs.winehq.org/attachment.cgi?id=53389 backtrace.txt See subject and attachment. Application runs fine with Win8 but fails with Wine 1.9.0 Standard MythUbuntu 14.04 so tried wine 1.6.x (that comes with standard), and now also the development version (1.9.0) using instructions from winehq.site for Ubuntu to install. Same endresult (Unhandled exception) on both. Backtrace is done with 1.9.0 -version. Application download link: http://growtopiagame.com/GrowtopiaInstaller.exe -- 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 23

[Bug 32221] New: LTspice: component drawing issues when moving
by wine-bugs＠winehq.org Jan. 4, 2019

Jan. 4, 2019

http://bugs.winehq.org/show_bug.cgi?id=32221 Bug #: 32221 Summary: LTspice: component drawing issues when moving Product: Wine Version: 1.5.13 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: testelor(a)yahoo.com Classification: Unclassified Created attachment 42497 --> http://bugs.winehq.org/attachment.cgi?id=42497 Traces left behind when moving Steps to reproduce: 1) Download and install LTspice - http://ltspice.linear.com/software/LTspiceIV.exe 2) Run LTspice using: $ wine scad3.exe -nowine 3) Create a new schematic, press 'R' (resistor), for example, and don't place it by clicking, simply move it around. The same happens for any component that is grabbed and moved. See the attached screenshot. -- 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 11

[Bug 45984] New: Skyrim Special Edition does not get past loading screen on high core count or high memory systems
by wine-bugs＠winehq.org Jan. 4, 2019

Jan. 4, 2019

https://bugs.winehq.org/show_bug.cgi?id=45984 Bug ID: 45984 Summary: Skyrim Special Edition does not get past loading screen on high core count or high memory systems Product: Wine Version: 3.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tom(a)r.je Distribution: --- Skyrim SE gets stuck at the loading screen on certain hardware configurations. It doesn't freeze as keeps displaying different loading screen tips but does so forever. I posted on the Steam forums about this: https://steamcommunity.com/app/221410/discussions/8/1734336452599497070/ With a blank wineprefix (no savegames, no mods, just a fresh install from steam) click "New game". It sits at the loading screen forever. Almost everyone affected has: AMD Threadripper 1950x >= 32gb RAM ### Software information Skyrim Special Edition (Steam) (With or without DXVK) ### System information - GPU: nvidia 980ti - Driver: 410 (396.54 also affected) - Wine version: 3.18 There are several systems listed in the steam thread: ///// Arch Linux AMD Threadripper 1950x 32gb RAM nvidia 980ti with 396.54 driver ///// Ubuntu 18.04 AMD Threadripper 1950x 64gb RAM Nvidia Titan XP /// Arch Linux AMD Threadripper 1950x 32gb RAM AMD Vega 64 //// Both AMD and nVidia GPUs are affected so it's unlikely to be a driver issue. The common elements are: 32gb or more of RAM AMD Threadripper 1950x ### What I've tried Knowing that it only affects high CPU core systems or high RAM systems I have tried the following: - taskset -c 0-7 wine steam.exe I wasn't sure whether this would limit just steam.exe, when steam.exe spawns SkyrimSE.exe does this have all 32 cores enabled? - Disabling SMT in the bios. This effectively disables half the cores so there are only 16 available. This would be similar to someone playing on a Ryzen 7 (8 cores + smt) and I haven't seen any reports with 16 thread CPUs - It seems like it might be a memory issue. I've tried enabling/disabling NUMA in the bios to no effect - With NUMA enabled I've tried using `numactl -m 0 -t wine Steam.exe` to force WINE to only use one bank of memory (effectively limiting it to 16gb in the process) - Running off a SSD rather than NVME driver (It could be a scheduler issue??) None of this made any difference. How else can I debug this? Looking around, posts regarding similar issues on windows suggests it's a memory problem. Perhaps it's something to do with having 32gb RAM in the system? Please let me know if you need any kind of trace/log. WINEDEBUG=all makes steam take so long to start it eventually crashes, so I couldn't provide that, I can try with requested debug options though. -- 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 33719] New: comctl32:propsheet custom window proc test failure
by wine-bugs＠winehq.org Jan. 4, 2019

Jan. 4, 2019

http://bugs.winehq.org/show_bug.cgi?id=33719 Bug #: 33719 Summary: comctl32:propsheet custom window proc test failure Product: Wine Version: 1.5.19 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified A number of VMs report one of these two related test failures: Elevated privileges (or pre-Vista): propsheet.c:746: Test failed: property sheet with custom window proc: the msg 0x001c was expected, but got msg 0x0047 instead or not elevated privileges: propsheet.c:746: Test failed: property sheet with custom window proc: the msg 0x0046 was expected, but got msg 0x0210 instead They have been seen on the following systems: comctl32 5.81.4968.2500 Windows 2000 Professional SP4 + IE55 (rare ~1/50) comctl32 5.82.3790.3959 Windows 2003 Enterprise Server SP2 + IE8 (rare ~1/50) comctl32 5.82.6002.18305 Windows Vista Home Premium SP2+IE9 comctl32 5.82.7601.17514 Windows 7 Ultimate SP1 64-bit (+IE8) (32-bit tests) comctl32 5.82.7601.17514 Windows 7 Ultimate SP1 64-bit + IE9 (32-bit tests) comctl32 5.82.7601.17514 Windows 7 SP1 (not one of mine) comctl32 5.82.9200.16384 Windows 8 -- 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 45190] New: Test report
by wine-bugs＠winehq.org Jan. 3, 2019

Jan. 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=45190 Bug ID: 45190 Summary: Test report Product: Wine Version: 3.8 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bunglehead(a)gmail.com Distribution: --- This is a test report. -- 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 2

[Bug 42613] New: PowerPoint 2016 crashes at start screen
by wine-bugs＠winehq.org Jan. 3, 2019

Jan. 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=42613 Bug ID: 42613 Summary: PowerPoint 2016 crashes at start screen Product: Wine Version: 2.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isiraseneviratne(a)yahoo.com Distribution: Ubuntu Created attachment 57558 --> https://bugs.winehq.org/attachment.cgi?id=57558 Backtrace from PowerPoint 2016 PowerPoint tends to crash at the start screen with the attached error message. However, sometimes it will load normally after running it again. -- 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 2

[Bug 26262] New: No video output in game
by wine-bugs＠winehq.org Jan. 1, 2019

Jan. 1, 2019

http://bugs.winehq.org/show_bug.cgi?id=26262 Summary: No video output in game Product: Wine Version: 1.3.14 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: torgeriedel(a)gmx.de When trying to play Commandos - Behind Enemy lines, there is no video output. Sound is working. -- 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 25

[Bug 33368] New: WM_DEADCHAR events not sent
by wine-bugs＠winehq.org Dec. 31, 2018

Dec. 31, 2018

http://bugs.winehq.org/show_bug.cgi?id=33368 Bug #: 33368 Summary: WM_DEADCHAR events not sent Product: Wine Version: 1.5.27 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: sloonz(a)gmail.com Classification: Unclassified Created attachment 44152 --> http://bugs.winehq.org/attachment.cgi?id=44152 Keyboard traces in three different scenarios (Windows, Wine, Wine+patch) XFilterEvent() returns true for events of dead keys, so they are not processed by wine. However, that prevents sending a WM_DEADCHAR event to the application, as it works on Windows. For example, in order to emit a "ê" character in a french keyboard layout, I first have to press ^ (which is a dead key) and then e. Under Windows, this leads to the following sequence of events : KEYDOWN: dead_circumflex DEADCHAR: dead_circumflex KEYDOWN: e CHAR: ê KEYUP: e KEYUP: dead_circumflex Under wine I have only those events : KEYUP: dead_circumflex KEYDOWN: e CHAR: ê Attached patch fixes most of that, with it I get : KEYDOWN: dead_circumflex DEADCHAR: dead_circumflex UP: dead_circumflex KEYDOWN: e CHAR: ê KEYUP: e Note that it’s still slighty different from Windows (KEYUP for dead key is third message on Wine, whereas it is before the last one on Windows), but I don’t see a clean fix for this issue. As for the traces in attachment, contains three traces. The first one is from Spy++ on Windows ; the second is the relevant output of WINEDEBUG=+msg notepad for unpatched wine ; the third one for patched wine. -- 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 6

[Bug 36095] New: valgrind errors in loader when loading a dll
by wine-bugs＠winehq.org Dec. 31, 2018

Dec. 31, 2018

https://bugs.winehq.org/show_bug.cgi?id=36095 Bug ID: 36095 Summary: valgrind errors in loader when loading a dll Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: major Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Noticed this in most tests, there are at least 3 places. 1: ==11164== 26 bytes in 1 blocks are definitely lost in loss record 57 of 244 ==11164== at 0x7BC4C735: notify_alloc (heap.c:255) ==11164== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11164== by 0x7BC758B6: RtlCreateUnicodeString (rtlstr.c:281) ==11164== by 0x7BC54CF3: alloc_module (loader.c:919) ==11164== by 0x7BC566CB: load_builtin_callback (loader.c:1519) ==11164== by 0x40192DE: __wine_dll_register (loader.c:517) ==11164== by 0x7B88A18B: __wine_spec_init (init.c:35) ==11164== by 0x4E850459: call_init.part.0 (in /usr/lib/ld-2.18.so) ==11164== by 0x4E850593: _dl_init (in /usr/lib/ld-2.18.so) ==11164== by 0x4E854953: dl_open_worker (in /usr/lib/ld-2.18.so) ==11164== by 0x4E850329: _dl_catch_error (in /usr/lib/ld-2.18.so) ==11164== by 0x4E854013: _dl_open (in /usr/lib/ld-2.18.so) ==11164== by 0x4EA25CBB: dlopen_doit (in /usr/lib/libdl-2.18.so) ==11164== by 0x4E850329: _dl_catch_error (in /usr/lib/ld-2.18.so) ==11164== by 0x4EA263CB: _dlerror_run (in /usr/lib/libdl-2.18.so) ==11164== by 0x4EA25D70: dlopen@@GLIBC_2.1 (in /usr/lib/libdl-2.18.so) ==11164== by 0x4019898: wine_dlopen (loader.c:1029) ==11164== by 0x4018C06: dlopen_dll (loader.c:295) ==11164== by 0x4019532: wine_dll_load (loader.c:581) ==11164== by 0x7BC57199: load_builtin_dll (loader.c:1732) ==11164== 2: ==11164== 32 bytes in 1 blocks are possibly lost in loss record 65 of 244 ==11164== at 0x7BC4C735: notify_alloc (heap.c:255) ==11164== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11164== by 0x7BC76348: RtlAnsiStringToUnicodeString (rtlstr.c:689) ==11164== by 0x7BC7595F: RtlCreateUnicodeStringFromAsciiz (rtlstr.c:302) ==11164== by 0x7BC5B407: init_load_order (loadorder.c:252) ==11164== by 0x7BC5B9FB: get_load_order (loadorder.c:440) ==11164== by 0x7BC58099: load_dll (loader.c:2045) ==11164== by 0x7BC585B7: LdrLoadDll (loader.c:2125) ==11164== by 0x7B85A79A: load_library (module.c:933) ==11164== by 0x7B85A908: LoadLibraryExW (module.c:990) ==11164== by 0x7B8649B8: __wine_kernel_init (process.c:1230) ==11164== by 0x7BC5ACA9: __wine_process_init (loader.c:3103) ==11164== by 0x4019864: wine_init (loader.c:952) ==11164== by 0x7BF011AD: main (main.c:237) ==11164== 3: ==11165== 20 bytes in 1 blocks are definitely lost in loss record 14 of 58 ==11165== at 0x7BC4C735: notify_alloc (heap.c:255) ==11165== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11165== by 0x7BC758B6: RtlCreateUnicodeString (rtlstr.c:281) ==11165== by 0x7BC54CF3: alloc_module (loader.c:919) ==11165== by 0x7BC566CB: load_builtin_callback (loader.c:1519) ==11165== by 0x40193D9: wine_dll_set_callback (loader.c:548) ==11165== by 0x7BC5ABA2: __wine_process_init (loader.c:3086) ==11165== by 0x4019864: wine_init (loader.c:952) ==11165== by 0x7BF011AD: main (main.c:237) ==11165== 4: ==11194== 32 bytes in 1 blocks are possibly lost in loss record 66 of 248 ==11194== at 0x7BC4C735: notify_alloc (heap.c:255) ==11194== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==11194== by 0x7BC76348: RtlAnsiStringToUnicodeString (rtlstr.c:689) ==11194== by 0x7BC7595F: RtlCreateUnicodeStringFromAsciiz (rtlstr.c:302) ==11194== by 0x7BC5B407: init_load_order (loadorder.c:252) ==11194== by 0x7BC5B9FB: get_load_order (loadorder.c:440) ==11194== by 0x7BC58099: load_dll (loader.c:2045) ==11194== by 0x7BC585B7: LdrLoadDll (loader.c:2125) ==11194== by 0x7B85A79A: load_library (module.c:933) ==11194== by 0x7B85A908: LoadLibraryExW (module.c:990) ==11194== by 0x7B8649B8: __wine_kernel_init (process.c:1230) ==11194== by 0x7BC5ACA9: __wine_process_init (loader.c:3103) ==11194== by 0x4019864: wine_init (loader.c:952) ==11194== by 0x7BF011AD: main (main.c:237) ==11194== (tested running advapi32/security.c) wine-1.7.17-92-ge2bf516 -- 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 17488] New: Animation issues in 4Story
by wine-bugs＠winehq.org Dec. 30, 2018

Dec. 30, 2018

http://bugs.winehq.org/show_bug.cgi?id=17488 Summary: Animation issues in 4Story Product: Wine Version: 1.1.15 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: killzenator(a)gmail.com Created an attachment (id=19581) --> (http://bugs.winehq.org/attachment.cgi?id=19581) Output of "wine 4Story.exe >> log.txt 2>&1" In 4Story none of the character/npcs have animations, weapons move up and down like their supposed to when you walk, characters stay the same. -- 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 27