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

[Bug 42727] New: obsolete 128MB bitmap size limit
by wine-bugs＠winehq.org July 11, 2017

July 11, 2017

https://bugs.winehq.org/show_bug.cgi?id=42727 Bug ID: 42727 Summary: obsolete 128MB bitmap size limit Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: claude(a)mathr.co.uk Distribution: --- Created attachment 57708 --> https://bugs.winehq.org/attachment.cgi?id=57708 source code to probe supported bitmap size The current WINE bitmap implementation has a size limit of 128MiB dating back to 2008 with a comment about Windows XP: https://source.winehq.org/git/wine.git/blob/39935fe5ad889d537d828cc82771bdb… 197 /* XP doesn't allow creating bitmaps larger than 128 MB */ 198 if (bm.bmHeight > 128 * 1024 * 1024 / bm.bmWidthBytes) 199 { 200 SetLastError( ERROR_NOT_ENOUGH_MEMORY ); 201 return 0; 202 } However, recent versions of Windows seem to have a higher limit, of 2GiB. Attached source code tries to create bitmaps with increasing sizes (each just under 2^N bytes) and prints successes and eventual failure. The bitmap test code seems to have a test for individual maximum dimension (width), but not for maximum total bitmap size: https://source.winehq.org/git/wine.git/blob/39935fe5ad889d537d828cc82771bdb… Thanks for testing to users at http://www.fractalforums.com/windows-fractal-software/windows-bitmap-size-t… - I'll attach their results after submitting. -- 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 8

[Bug 43181] New: NetBSD ptrace.c:678:46: error: 'struct dbreg' has no member named 'dr0' (and more)
by wine-bugs＠winehq.org July 11, 2017

July 11, 2017

https://bugs.winehq.org/show_bug.cgi?id=43181 Bug ID: 43181 Summary: NetBSD ptrace.c:678:46: error: 'struct dbreg' has no member named 'dr0' (and more) Product: Wine Version: 2.9 Hardware: x86-64 OS: NetBSD Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adrien_fernandes2(a)hotmail.com Created attachment 58452 --> https://bugs.winehq.org/attachment.cgi?id=58452 Entire output I'm using NetBSD 8.99.1 (GENERIC) amd64 I built successfully Wine for 64 bits ONLY (no 32 and 16 bits compatibility) with the exact same wip/wine-staging package I made by myself. To be able to build it to have 32 bits compatibility, I had to use a chroot with a full set of NetBSD i386 inside. It was working in the past, a few months earlier on an earlier version of Wine and NetBSD but not anymore now with 2.9 and NetBSD 8.99.1 (if it can be the problem) I attached the entire output when I "make -C /usr/pkgsrc/wip/wine-staging" -- 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

[Bug 43313] New: valgrind shows several uninitialized writes in dlls/ dinput/tests/device.c
by wine-bugs＠winehq.org July 10, 2017

July 10, 2017

https://bugs.winehq.org/show_bug.cgi?id=43313 Bug ID: 43313 Summary: valgrind shows several uninitialized writes in dlls/dinput/tests/device.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com CC: 00cpxxx(a)gmail.com Distribution: Gentoo ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A6DAE: JoystickWImpl_Acquire (joystick_linuxinput.c:718) ==21119== by 0x52A6F15: JoystickAImpl_Acquire (joystick_linuxinput.c:736) ==21119== by 0x48783BA: test_object_info (device.c:118) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6B64: JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A700D: JoystickWImpl_Unacquire (joystick_linuxinput.c:762) ==21119== by 0x52A70F0: JoystickAImpl_Unacquire (joystick_linuxinput.c:774) ==21119== by 0x4878441: test_object_info (device.c:121) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6F36: JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A6DAE: JoystickWImpl_Acquire (joystick_linuxinput.c:718) ==21119== by 0x52A6F15: JoystickAImpl_Acquire (joystick_linuxinput.c:736) ==21119== by 0x48785AF: test_object_info (device.c:131) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6B64: JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A700D: JoystickWImpl_Unacquire (joystick_linuxinput.c:762) ==21119== by 0x52A70F0: JoystickAImpl_Unacquire (joystick_linuxinput.c:774) ==21119== by 0x4878683: test_object_info (device.c:136) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6F36: JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A6DAE: JoystickWImpl_Acquire (joystick_linuxinput.c:718) ==21119== by 0x52A6F15: JoystickAImpl_Acquire (joystick_linuxinput.c:736) ==21119== by 0x48788F9: test_object_info (device.c:161) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6B64: JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A700D: JoystickWImpl_Unacquire (joystick_linuxinput.c:762) ==21119== by 0x52A70F0: JoystickAImpl_Unacquire (joystick_linuxinput.c:774) ==21119== by 0x48789BD: test_object_info (device.c:166) ==21119== by 0x4878BBB: enum_devices (device.c:194) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f68c is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6F36: JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A6DAE: JoystickWImpl_Acquire (joystick_linuxinput.c:718) ==21119== by 0x48783BA: test_object_info (device.c:118) ==21119== by 0x4878C4C: enum_devices (device.c:200) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f6cc is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6B64: JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A700D: JoystickWImpl_Unacquire (joystick_linuxinput.c:762) ==21119== by 0x4878441: test_object_info (device.c:121) ==21119== by 0x4878C4C: enum_devices (device.c:200) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f6cc is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6F36: JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A6DAE: JoystickWImpl_Acquire (joystick_linuxinput.c:718) ==21119== by 0x48785AF: test_object_info (device.c:131) ==21119== by 0x4878C4C: enum_devices (device.c:200) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f6cc is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6B64: JoystickWImpl_Acquire (joystick_linuxinput.c:684) ==21119== ==21119== Syscall param write(buf) points to uninitialised byte(s) ==21119== at 0x424DE7F: ??? (syscall-template.S:84) ==21119== by 0x52A700D: JoystickWImpl_Unacquire (joystick_linuxinput.c:762) ==21119== by 0x4878683: test_object_info (device.c:136) ==21119== by 0x4878C4C: enum_devices (device.c:200) ==21119== by 0x5295DD3: ??? (dinput_main.c:351) ==21119== by 0x5296011: IDirectInputAImpl_EnumDevices (dinput_main.c:419) ==21119== by 0x4878EF8: device_tests (device.c:241) ==21119== by 0x4879050: func_device (device.c:266) ==21119== by 0x48822E7: run_test (test.h:603) ==21119== by 0x4882739: main (test.h:687) ==21119== Address 0x4b0f6cc is on thread 1's stack ==21119== in frame #1, created by JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== Uninitialised value was created by a stack allocation ==21119== at 0x52A6F36: JoystickWImpl_Unacquire (joystick_linuxinput.c:743) ==21119== wine-2.12. Note: I had a Sony DS4 plugged in via USB when the tests were run, which may be related -- 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

[Bug 36183] New: valgrind shows a potential leaks in atl100/tests/atl.c
by wine-bugs＠winehq.org July 10, 2017

July 10, 2017

https://bugs.winehq.org/show_bug.cgi?id=36183 Bug ID: 36183 Summary: valgrind shows a potential leaks in atl100/tests/atl.c Product: Wine Version: 1.3.13 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: atl Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==13578== 8 bytes in 1 blocks are possibly lost in loss record 37 of 602 ==13578== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==13578== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==13578== by 0x7B8457FF: HeapAlloc (heap.c:271) ==13578== by 0x7B845AD4: GlobalAlloc (heap.c:376) ==13578== by 0x4E29357: OLEClipbrd_Initialize (clipboard.c:1732) ==13578== by 0x4E626C6: OleInitialize (ole2.c:215) ==13578== by 0x4DE5CA0: AtlAxWinInit (atl_ax.c:108) ==13578== by 0x4C9708E: test_ax_win (atl.c:600) ==13578== by 0x4C97273: func_atl (atl.c:627) ==13578== by 0x4C98072: run_test (test.h:584) ==13578== by 0x4C98460: main (test.h:654) ==13578== ==13578== 32 bytes in 1 blocks are possibly lost in loss record 208 of 602 ==13578== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==13578== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==13578== by 0x7BC39A6B: RtlInitializeCriticalSectionEx (critsection.c:326) ==13578== by 0x7B876AE5: InitializeCriticalSectionEx (sync.c:356) ==13578== by 0x7B876A64: InitializeCriticalSection (sync.c:313) ==13578== by 0x4DE4213: AtlWinModuleInit (atl.c:436) ==13578== by 0x4C950D9: test_winmodule (atl.c:89) ==13578== by 0x4C9725A: func_atl (atl.c:622) ==13578== by 0x4C98072: run_test (test.h:584) ==13578== by 0x4C98460: main (test.h:654) ==13578== ==1611== 32 bytes in 1 blocks are possibly lost in loss record 217 of 629 ==1611== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==1611== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==1611== by 0x7BC39A6B: RtlInitializeCriticalSectionEx (critsection.c:326) ==1611== by 0x7B876AE5: InitializeCriticalSectionEx (sync.c:356) ==1611== by 0x7B876A64: InitializeCriticalSection (sync.c:313) ==1611== by 0x4E62252: test_winmodule (atl.c:101) ==1611== by 0x4E6425A: func_atl (atl.c:622) ==1611== by 0x4E65072: run_test (test.h:584) ==1611== by 0x4E65460: main (test.h:654) ==1611== ==1611== 32 bytes in 1 blocks are possibly lost in loss record 218 of 629 ==1611== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==1611== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==1611== by 0x5B300B4: alloc_bstr (oleaut.c:162) ==1611== by 0x5B3044A: SysAllocStringLen (oleaut.c:324) ==1611== by 0x5B535E8: TLB_MultiByteToBSTR (typelib.c:1753) ==1611== by 0x5B580A8: ITypeLib2_Constructor_MSFT (typelib.c:3706) ==1611== by 0x5B57398: TLB_ReadTypeLib (typelib.c:3460) ==1611== by 0x5B4F6BC: LoadTypeLibEx (typelib.c:478) ==1611== by 0x5B4F5F8: LoadTypeLib (typelib.c:454) ==1611== by 0x4E639C1: Dispatch_GetTypeInfo (atl.c:520) ==1611== by 0x4F853FA: AtlGetObjectSourceInterface (oaidl.h:811) ==1611== by 0x4E63D58: test_source_iface (atl.c:576) ==1611== by 0x4E6426E: func_atl (atl.c:626) ==1611== by 0x4E65072: run_test (test.h:584) ==1611== by 0x4E65460: main (test.h:654) ==1611== ==1659== 32 bytes in 1 blocks are possibly lost in loss record 218 of 630 ==1659== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==1659== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==1659== by 0x7BC39A6B: RtlInitializeCriticalSectionEx (critsection.c:326) ==1659== by 0x7B876AE5: InitializeCriticalSectionEx (sync.c:356) ==1659== by 0x7B876A64: InitializeCriticalSection (sync.c:313) ==1659== by 0x4E62252: test_winmodule (atl.c:101) ==1659== by 0x4E6425A: func_atl (atl.c:622) ==1659== by 0x4E65072: run_test (test.h:584) ==1659== by 0x4E65460: main (test.h:654) ==1659== ==1986== 80 bytes in 1 blocks are possibly lost in loss record 348 of 630 ==1986== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==1986== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==1986== by 0x5B040B4: alloc_bstr (oleaut.c:162) ==1986== by 0x5B045F5: SysAllocStringByteLen (oleaut.c:413) ==1986== by 0x5B29DA8: MSFT_ReadAllStrings (typelib.c:2879) ==1986== by 0x5B2B9F0: ITypeLib2_Constructor_MSFT (typelib.c:3581) ==1986== by 0x5B2B398: TLB_ReadTypeLib (typelib.c:3460) ==1986== by 0x5B236BC: LoadTypeLibEx (typelib.c:478) ==1986== by 0x5B235F8: LoadTypeLib (typelib.c:454) ==1986== by 0x4A349C1: Dispatch_GetTypeInfo (atl.c:520) ==1986== by 0x4F553FA: AtlGetObjectSourceInterface (oaidl.h:811) ==1986== by 0x4A34D58: test_source_iface (atl.c:576) ==1986== by 0x4A3526E: func_atl (atl.c:626) ==1986== by 0x4A36072: run_test (test.h:584) ==1986== by 0x4A36460: main (test.h:654) ==1986== -- 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 43299] New: Browse App fails to find application.
by wine-bugs＠winehq.org July 10, 2017

July 10, 2017

https://bugs.winehq.org/show_bug.cgi?id=43299 Bug ID: 43299 Summary: Browse App fails to find application. Product: WineHQ Apps Database Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- When filtering on "Cloud Pirates" to see if it was in the database, it failed to find the entry. However when "submitting" an application, it found the entry straight away on the duplicate check. -- 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 43298] New: World of Warcraft and Windows XP out of date.
by wine-bugs＠winehq.org July 10, 2017

July 10, 2017

https://bugs.winehq.org/show_bug.cgi?id=43298 Bug ID: 43298 Summary: World of Warcraft and Windows XP out of date. Product: Wine Version: 2.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arnaud.his(a)free.fr Distribution: --- Created attachment 58641 --> https://bugs.winehq.org/attachment.cgi?id=58641 Screenshot For some weeks, every time I start the software, I get this message: "Your operating system will no longer be supported". "Windows XP support will stop soon. We recommend that you upgrade to Windows 7 at a minimum." -- 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 41363] New: Starcraft Editor crash when accessing Triggers.
by wine-bugs＠winehq.org July 8, 2017

July 8, 2017

https://bugs.winehq.org/show_bug.cgi?id=41363 Bug ID: 41363 Summary: Starcraft Editor crash when accessing Triggers. Product: Wine Version: 1.9.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zombie_ryushu(a)yahoo.com Distribution: --- In all versions of Starcraft (Brood War) under Wine 1.9.12 to current, Starcraft Map editor Crashes whenever the "Triggers" Dialogue is accessed. Wine will report that the program had a serious problem, and dump a backtrace. -- 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 43297] New: Hello Neighbor crashes on startup
by wine-bugs＠winehq.org July 8, 2017

July 8, 2017

https://bugs.winehq.org/show_bug.cgi?id=43297 Bug ID: 43297 Summary: Hello Neighbor crashes on startup Product: Wine Version: 2.10 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- Prompts with message The global shader cache file 'C:/Program Files (x86)/Steam/steamapps/common/Hello Neighbor Demo/Engine/GlobalShaderCache-GLSL_150.bin' is missing. You're running a version of the application built to load COOKED content only, however no COOKED content was found. Consider cooking content for this b... -- 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 41585] New: Rogue Operatives won't launch
by wine-bugs＠winehq.org July 8, 2017

July 8, 2017

https://bugs.winehq.org/show_bug.cgi?id=41585 Bug ID: 41585 Summary: Rogue Operatives won't launch Product: Wine Version: 1.9.21 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 55923 --> https://bugs.winehq.org/attachment.cgi?id=55923 crash log - steam Only a window opens saying Your application is built to load COOKED content. No COOKED content was found; This usually means you did not cook content for this build. It also may indicate missing cooked data for a shader platform(e.g., OpenGL under Windows): Make sure your platform's packaging settings include this Targeted RHI. -- 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 35278] New: KindleforPC crashes with big books
by wine-bugs＠winehq.org July 8, 2017

July 8, 2017

http://bugs.winehq.org/show_bug.cgi?id=35278 Bug ID: 35278 Summary: KindleforPC crashes with big books Product: Wine Version: 1.7.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine(a)staerk.de Classification: Unclassified Created attachment 47052 --> http://bugs.winehq.org/attachment.cgi?id=47052 backtrace when clicking onto a large book in Amazon Kindle reader for PC When starting Kindle.exe to read my e-books, wine crashes with the attached backtrace. I tried with SUSE 13.1 and SUSE 12.2, in both cases it crashes. -- 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