February 2018 - Wine-bugs - list.winehq.org

[Bug 12553] New: Toolbars misplaced, hidden
by wine-bugs＠winehq.org 17 Aug '18

17 Aug '18

http://bugs.winehq.org/show_bug.cgi?id=12553 Summary: Toolbars misplaced, hidden Product: Wine Version: 0.9.59. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: tarasov.igor(a)gmail.com Created an attachment (id=12122) --> (http://bugs.winehq.org/attachment.cgi?id=12122) WINEDEBUG=+toolbar,+listview,+themingcombo wine 0.9.59 log Here are two screenshots: Wine being run with MS comctl32.dll, the same thing you see in Windows: http://polosatus.ru/wine/toolbar_reference.png And wine running with it's own version of comctl32: http://polosatus.ru/wine/toolbar_bug.png First of all, disappeared toolbar at the middle of screenshot. Also, notice misplaced right toolbar. It is misplaced to left a bit. I suppose both bugs are related. Seems that developers have used some undocumented features, as log has this: warn:toolbar:TOOLBAR_SetBitmapSize 5 buttons, undoc increase to bitmap size : 16-15 -> 20-20 and this: warn:toolbar:TOOLBAR_SetBitmapSize 6 buttons, undoc increase to bitmap size : 20-20 -> 16-16 several times. I've supposed that WINEDEBUG=+toolbar,+listview,+themingcombo should be enough for initial log :) -- 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 42

[Bug 40412] New: When opening the game Stardew Valley, I get an error message and it never opens
by wine-bugs＠winehq.org 12 Aug '18

12 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=40412 Bug ID: 40412 Summary: When opening the game Stardew Valley, I get an error message and it never opens Product: Wine Version: 1.9.4 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: goodman.jaime(a)gmail.com Created attachment 54149 --> https://bugs.winehq.org/attachment.cgi?id=54149 backtrace file I get the message "This program has encountered a serious problem and needs to close" Logs 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 12

[Bug 44597] New: Window rendering com pletely breaks after interacting with the “Desktop Integration” section of winecfg with enabled GTK3 themeing
by wine-bugs＠winehq.org 10 Aug '18

10 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=44597 Bug ID: 44597 Summary: Window rendering completely breaks after interacting with the “Desktop Integration” section of winecfg with enabled GTK3 themeing Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexander-winehq(a)xmine128.tk CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 60584 --> https://bugs.winehq.org/attachment.cgi?id=60584 Changes in HKCU registry # Background & Steps to reproduce Window rendering will show bizare artifacts, up to becoming totally useless (tiny transparent window frames that cannot be interacted with), after following the below steps: 1. In WINE staging enable GTK3 themeing 2. Open `winecfg` again (things should be themed now) 3. Select the “desktop integration” tab 4. Change the “theme” from “GTK-3” to “(No Theme)” and click “Apply” 5. Do the above two times for noticable rendering issues and crashes 6. Do the above three (or more) times to break *any window rendering in WINE* (see attachment 2) # Underlying issue I'm not exactly sure what `winecfg` happens to do here, but it somehow manages to calculate and store some completely wrong values for several entries inside the HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics registry key (see attachment 1) that then result in this behaviour. # Workaround Open `${WINEPREFIX}/user.reg` in a text editor and delete the entire HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics registry key section before launching WINE 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 31741] New: python-2.7.3.amd64.msi fails to install
by wine-bugs＠winehq.org 09 Aug '18

09 Aug '18

http://bugs.winehq.org/show_bug.cgi?id=31741 Bug #: 31741 Summary: python-2.7.3.amd64.msi fails to install Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: tahoar(a)gmail.com Classification: Unclassified I tried installing Python 64-bit 2.7.3 on wine1.5-amd64. The installer loads but will not progress after the introduction page. When clicking "continue", the installer does nothing. Clicking "cancel" exits the installer. -- 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 21

[Bug 44373] New: cmd's %0 path variables (e.g. %~dp0) don' t match those of Windows (w.r.t. case and quoting)
by wine-bugs＠winehq.org 05 Aug '18

05 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=44373 Bug ID: 44373 Summary: cmd's %0 path variables (e.g. %~dp0) don't match those of Windows (w.r.t. case and quoting) Product: Wine Version: 3.0-rc6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: ryan.prichard(a)gmail.com Distribution: --- I'm filing this issue at Fabian Maurer's suggestion, after filing https://bugs.winehq.org/show_bug.cgi?id=44369. When %0 starts with a quote character, Windows tends to evaluate the %0 path variables (%~d0, %~p0, ...) strangely. I think the Wine behavior makes more sense, but it could also make sense to match Windows bug-for-bug. Test program (you might have to fix up the C:\bin for your machine): C:\>mkdir Bin C:\Bin\ShowArg0.Cmd: @echo [%0] -------------------- [%~d0] [%~p0] [%~n0] [%~x0] C:\Bin\RunScript.Cmd @echo off setlocal set PATH=C:\bin;%PATH% cd \ echo --- Wine and Windows roughly do the same thing. call showarg0 call SHOWARG0 call showarg0.cmd call SHOWARG0.CMD call C:\bin\showarg0 call C:\bin\showarg0.cmd call c:\bin\showarg0.CMD call showarg0".cmd" call showarg0."cmd" call showarg0.c"md" call s"ho"warg0.cmd call s"ho"warg0 call "C:\bin\showarg0.cmd" call "c:\bin\showarg0.CMD" echo --- Wine and Windows diverge here. call "showarg0" call "SHOWARG0" call "showarg0.cmd" call "SHOWARG0.CMD" call "showarg0".cmd call "sho"warg0.cmd call "sho"warg0 call "C":\bin\showarg0.cmd call "C:"\bin\showarg0.cmd call "C:\"bin\showarg0.cmd call "c:\"bin\showarg0.CMD call "C:\bin\showarg0" (I edited the script output to align the columns.) Windows behavior (tested on XP and Win10.0.16299.125): C:\Bin>RunScript --- Aside from case, Wine and Windows roughly do the same thing. --- ... Using c:\bin in PATH [showarg0] ----------------- [c:] [\Bin\] [ShowArg0] [.Cmd] [SHOWARG0] ----------------- [c:] [\Bin\] [ShowArg0] [.Cmd] --- ... Using C:\bin in PATH [showarg0] ----------------- [C:] [\Bin\] [ShowArg0] [.Cmd] [SHOWARG0] ----------------- [C:] [\Bin\] [ShowArg0] [.Cmd] [showarg0.cmd] ------------- [C:] [\Bin\] [ShowArg0] [.Cmd] [SHOWARG0.CMD] ------------- [C:] [\Bin\] [ShowArg0] [.Cmd] [C:\bin\showarg0] ---------- [C:] [\Bin\] [ShowArg0] [.Cmd] [C:\bin\showarg0.cmd] ------ [C:] [\Bin\] [ShowArg0] [.Cmd] [c:\bin\showarg0.CMD] ------ [c:] [\Bin\] [ShowArg0] [.Cmd] [showarg0".cmd"] ----------- [C:] [\Bin\] [ShowArg0] [.Cmd] [showarg0."cmd"] ----------- [C:] [\Bin\] [ShowArg0] [.Cmd] [showarg0.c"md"] ----------- [C:] [\Bin\] [ShowArg0] [.Cmd] [s"ho"warg0.cmd] ----------- [C:] [\Bin\] [ShowArg0] [.Cmd] [s"ho"warg0] --------------- [C:] [\Bin\] [ShowArg0] [.Cmd] ["C:\bin\showarg0.cmd"] ---- [C:] [\Bin\] [ShowArg0] [.Cmd] ["c:\bin\showarg0.CMD"] ---- [c:] [\Bin\] [ShowArg0] [.Cmd] --- Wine and Windows diverge here. ["showarg0"] --------------- [C:] [\] [showarg0] [] ["SHOWARG0"] --------------- [C:] [\] [SHOWARG0] [] ["showarg0.cmd"] ----------- [C:] [\] [showarg0] [.cmd] ["SHOWARG0.CMD"] ----------- [C:] [\] [SHOWARG0] [.CMD] ["showarg0".cmd] ----------- [C:] [\] [showarg0"] [.cmd] ["sho"warg0.cmd] ----------- [C:] [\] [sho"warg0] [.cmd] ["sho"warg0] --------------- [C:] [\] [sho"warg0] [] ["C":\bin\showarg0.cmd] ---- [C:] [\C":\bin\] [showarg0] [.cmd] ["C:"\bin\showarg0.cmd] ---- [C:] [\"\bin\] [showarg0] [.cmd] ["C:\"bin\showarg0.cmd] ---- [C:] [\"bin\] [showarg0] [.cmd] ["c:\"bin\showarg0.CMD] ---- [c:] [\"bin\] [showarg0] [.CMD] ["C:\bin\showarg0"] -------- [C:] [\Bin\] [showarg0] [] Behavior on wine-3.0-rc6: C:\Bin>RunScript --- Aside from case, Wine and Windows roughly do the same thing. --- ... Using c:\bin in PATH [showarg0] ----------------- [c:] [\bin\] [showarg0] [.CMD] [SHOWARG0] ----------------- [c:] [\bin\] [SHOWARG0] [.CMD] --- ... Using C:\bin in PATH [showarg0] ----------------- [C:] [\bin\] [showarg0] [.CMD] [SHOWARG0] ----------------- [C:] [\bin\] [SHOWARG0] [.CMD] [showarg0.cmd] ------------- [C:] [\bin\] [showarg0] [.cmd] [SHOWARG0.CMD] ------------- [C:] [\bin\] [SHOWARG0] [.CMD] [C:\bin\showarg0] ---------- [C:] [\bin\] [showarg0] [.CMD] [C:\bin\showarg0.cmd] ------ [C:] [\bin\] [showarg0] [.cmd] [c:\bin\showarg0.CMD] ------ [c:] [\bin\] [showarg0] [.CMD] [showarg0".cmd"] ----------- [C:] [\bin\] [showarg0] [.cmd] [showarg0."cmd"] ----------- [C:] [\bin\] [showarg0] [.cmd] [showarg0.c"md"] ----------- [C:] [\bin\] [showarg0] [.cmd] [s"ho"warg0.cmd] ----------- [C:] [\bin\] [showarg0] [.cmd] [s"ho"warg0] --------------- [C:] [\bin\] [showarg0] [.CMD] ["C:\bin\showarg0.cmd"] ---- [C:] [\bin\] [showarg0] [.cmd] ["c:\bin\showarg0.CMD"] ---- [c:] [\bin\] [showarg0] [.CMD] --- Wine and Windows diverge here. ["showarg0"] --------------- [C:] [\bin\] [showarg0] [.CMD] ["SHOWARG0"] --------------- [C:] [\bin\] [SHOWARG0] [.CMD] ["showarg0.cmd"] ----------- [C:] [\bin\] [showarg0] [.cmd] ["SHOWARG0.CMD"] ----------- [C:] [\bin\] [SHOWARG0] [.CMD] ["showarg0".cmd] ----------- [C:] [\bin\] [showarg0] [.cmd] ["sho"warg0.cmd] ----------- [C:] [\bin\] [showarg0] [.cmd] ["sho"warg0] --------------- [C:] [\bin\] [showarg0] [.CMD] ["C":\bin\showarg0.cmd] ---- [C:] [\bin\] [showarg0] [.cmd] ["C:"\bin\showarg0.cmd] ---- [C:] [\bin\] [showarg0] [.cmd] ["C:\"bin\showarg0.cmd] ---- [C:] [\bin\] [showarg0] [.cmd] ["c:\"bin\showarg0.CMD] ---- [c:] [\bin\] [showarg0] [.CMD] ["C:\bin\showarg0"] -------- [C:] [\bin\] [showarg0] [.CMD] I see two differences: - In most cases, when a path starts with a quote, Windows somehow doesn't parse the path correctly and/or doesn't find the batch file in the PATH. - As long as Windows *does* find the batch file, it uses the canonical case for the path, filename, and extension. It doesn't canonicalize the drive; instead it uses the drive from the PATH or %0. I also tested a SMB share on XP and Win10 (\\nAs\nAs and \\NaS\NaS), and Windows didn't canonicalize the server name or share name. (Maybe it never does.) -- 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 34893] New: LaTale Launcher gives WSASocketW Failed to create a socket of type SOCK_RAW, this requires special permissions
by wine-bugs＠winehq.org 04 Aug '18

04 Aug '18

http://bugs.winehq.org/show_bug.cgi?id=34893 Bug #: 34893 Summary: LaTale Launcher gives WSASocketW Failed to create a socket of type SOCK_RAW, this requires special permissions Product: Wine Version: 1.7.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: iyeru42(a)gmail.com Classification: Unclassified tried using the regnum fix: sudo setcap CAP_NET_RAW=ep /usr/bin/wine sudo setcap CAP_NET_RAW=ep /usr/bin/wineserver sudo setcap CAP_NET_RAW=ep LaTaleLauncher.exe Also applied it to the ogplauncher, Still gave the error. LaTale also requires GC_DONT_GC=1 before the wine command on the downloader for the client, since it's pandomediabooster. Get the client here: http://latale.ogplanet.com/en/download/client.og Pastebin: http://pastebin.com/FTT71zb1 -- 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 43436] New: Would it be possible to add Mageia 6 back to the Install page?
by wine-bugs＠winehq.org 03 Aug '18

03 Aug '18

https://bugs.winehq.org/show_bug.cgi?id=43436 Bug ID: 43436 Summary: Would it be possible to add Mageia 6 back to the Install page? Product: Wine-staging Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arichter(a)lobo.net CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- I would sure like to see Mageia added back to the wine-staging Install page, Mageia has been very good about keeping up with the stable releases but staging is where all the fun is. I have been successfully building RPMS for both i586 and x86_64 under Mageia 6 and would be glad to submit RPMS or SRPMS for both architectures. Mageia 6 also now supports mock, which is what I have been using to build the i586 RPMs under x86_64. I apologize for submitting this as a bug since it's not a bug but I would either like to see Mageia back under the Install page or contribute built RPMS and SRPMS to help make it happen. I'm a bit new to this RPM building thing but the stuff I've made has worked out for me, and I've tried to be more active in the winedb. Thank you for your time and efforts, I only want to help on the Mageia side of things. -- 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 15

[Bug 15864] New: window size has reversed width and height
by wine-bugs＠winehq.org 29 Jul '18

29 Jul '18

http://bugs.winehq.org/show_bug.cgi?id=15864 Summary: window size has reversed width and height Product: Wine Version: 1.1.7 Platform: Other URL: http://jeffz.name/dvt-fc2.exe OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jeffz(a)jeffz.name Created an attachment (id=17001) --> (http://bugs.winehq.org/attachment.cgi?id=17001) Windows-vs-Wine This small program seems to have its width and height mixed up under Wine. The attached screenshot shows the program running under windows (top) and under Wine (below) -- 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 22

[Bug 41635] New: The Banner Saga 2 (adobe air) - poor performance on plain Wine, flickering on Wine-staging
by wine-bugs＠winehq.org 28 Jul '18

28 Jul '18

https://bugs.winehq.org/show_bug.cgi?id=41635 Bug ID: 41635 Summary: The Banner Saga 2 (adobe air) - poor performance on plain Wine, flickering on Wine-staging Product: Wine Version: 1.9.22 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: donanykey(a)gmail.com Distribution: --- Although from the first glance the Banner Saga 2 (based on the Adobe Air) is fully functional with plain Wine, the performance is very poor and the framerate is bad (literally `slide show`). I wouldn't have fired this bug, if not the following reasons: 1. The performance on wine-staging is much better, almost close to native, but there is another problem - picture flickering 2. The first game in series has native linux support, but with known problems (during battles after some time of playing the framerate drops dramatically and hardly recovers). Due to the small fraction of linux gamers and, I believe, due to the porting efforts and problems the developer announced that they have no plans to support linux in the 2 & 3 games in the foreseeable future. I think it would be a good opportunity for CodeWeavers to reach those guys and propose porting services (they are quite opened guys, their CTO shares details over porting vendor selection, problems and etc - easily googled). One of the major problems - Adobe stopped support of Air on Linux Nevertheless, I would be happy to provide any additional info, full log is not useful I suppose, as soon as game runs without errors and can't say what patch(s) in wine-staging makes it run faster -- 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 40541] New: 4d embroidery crashes
by wine-bugs＠winehq.org 28 Jul '18

28 Jul '18

https://bugs.winehq.org/show_bug.cgi?id=40541 Bug ID: 40541 Summary: 4d embroidery crashes Product: Wine Version: 1.9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hal Assignee: wine-bugs(a)winehq.org Reporter: mcseport(a)gmail.com Distribution: --- Created attachment 54372 --> https://bugs.winehq.org/attachment.cgi?id=54372 response from windows ws. System: theport(a)theport-To-be-filled-by-O-E-M ~ $ uname -a Linux theport-To-be-filled-by-O-E-M 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux theport(a)theport-To-be-filled-by-O-E-M ~ $ installed 4d embroidery software, requires dongle from safe-net. keeps crashing. dongle flashes, but sw doesn't boot up: theport(a)theport-To-be-filled-by-O-E-M ~ $ lsusb Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0781:55a5 SanDisk Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 006: ID 0846:6a00 NetGear, Inc. WG111v2 54 Mbps Wireless [RealTek RTL8187L] Bus 006 Device 005: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle Bus 006 Device 004: ID 05e3:0605 Genesys Logic, Inc. USB 2.0 Hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 009 Device 003: ID 04ca:004f Lite-On Technology Corp. SK-9020 keyboard Bus 009 Device 002: ID 045e:0039 Microsoft Corp. IntelliMouse Optical Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub theport(a)theport-To-be-filled-by-O-E-M ~ $ windows dump: Unhandled exception: page fault in 64-bit code (0x000000000045e8c6). Register dump: rip:000000000045e8c6 rsp:000000000043f910 rbp:0000000000440000 eflags:00010216 ( R- -- I -A-P- ) rax:0000000000000400 rbx:000000000045f77f rcx:000000000045e9de rdx:000000000045f135 rsi:000000000045f135 rdi:000000000045e9de r8:000000000000064a r9:000000000045e9de r10:000000000001f900 r11:0033006d00650074 r12:0000000000011de0 r13:0000000000000000 r14:000000000000000b r15:00007fa8fa113700 Stack dump: 0x000000000043f910: 0000000000440000 00007fa8f8884650 0x000000000043f920: 00007fa8f8680000 00000000004400d8 0x000000000043f930: 000000000045e9de 0000000000440380 0x000000000043f940: 000000000045eb65 000000000045e83c 0x000000000043f950: 00007fa8f8682472 00007fa8fa113700 0x000000000043f960: 000000000000000b 0000000000000000 0x000000000043f970: 0000000000011de0 0033006d00650074 0x000000000043f980: 000000000001f900 000000007bd19e20 0x000000000043f990: 000000000045f900 000000000043fa10 0x000000000043f9a0: 00007fa8f88846a0 00000000004400d8 0x000000000043f9b0: 000000000045d954 00007fa8f8682472 0x000000000043f9c0: 0000000000440000 0000000000000000 Backtrace: =>0 0x000000000045e8c6 in aksfridge.sys (+0x1e8c6) (0x0000000000440000) 0x000000000045e8c6: movl %eax,%dr7 Modules: Module Address Debug info Name (28 modules) PE 440000- 45f900 Export aksfridge.sys ELF 7b400000- 7b809000 Deferred kernel32<elf> \-PE 7b420000- 7b809000 \ kernel32 ELF 7bc00000- 7bd1b000 Deferred ntdll<elf> \-PE 7bc20000- 7bd1b000 \ ntdll ELF 7c000000- 7c004000 Deferred <wine-loader> ELF 7fa8f7cd8000- 7fa8f7ef0000 Deferred hal<elf> \-PE 7fa8f7ce0000- 7fa8f7ef0000 \ hal ELF 7fa8f7ef0000- 7fa8f8187000 Deferred rpcrt4<elf> \-PE 7fa8f7f00000- 7fa8f8187000 \ rpcrt4 ELF 7fa8f8188000- 7fa8f83db000 Deferred ntoskrnl<elf> \-PE 7fa8f81a0000- 7fa8f83db000 \ ntoskrnl ELF 7fa8f83e0000- 7fa8f8670000 Deferred advapi32<elf> \-PE 7fa8f83f0000- 7fa8f8670000 \ advapi32 ELF 7fa8f8670000- 7fa8f8885000 Deferred winedevice<elf> \-PE 7fa8f8680000- 7fa8f8885000 \ winedevice ELF 7fa8f8b58000- 7fa8f8d64000 Deferred libnss_files.so.2 ELF 7fa8f8d68000- 7fa8f8f74000 Deferred libnss_nis.so.2 ELF 7fa8f8f78000- 7fa8f9192000 Deferred libnsl.so.1 ELF 7fa8f9198000- 7fa8f93a2000 Deferred libnss_compat.so.2 ELF 7fa8f93c8000- 7fa8f95de000 Deferred libgcc_s.so.1 ELF 7fa8f95e0000- 7fa8f98e6000 Deferred libm.so.6 ELF 7fa8f9908000- 7fa8f9b0c000 Deferred libdl.so.2 ELF 7fa8f9b10000- 7fa8f9ed5000 Deferred libc.so.6 ELF 7fa8f9ed8000- 7fa8fa0f6000 Deferred libpthread.so.0 ELF 7fa8fa118000- 7fa8fa4d8000 Dwarf libwine.so.1 ELF 7fa8fa4d8000- 7fa8fa6fd000 Deferred ld-linux-x86-64.so.2 ELF 7ffcb79f2000- 7ffcb79f3000 Deferred [vdso].so Threads: process tid prio (all id:s are in hex) 0000000e services.exe 00000032 0 00000031 0 0000002a 0 00000016 0 00000012 0 0000000f 0 00000010 explorer.exe 00000037 0 00000036 0 00000035 0 00000011 0 00000014 (D) C:\windows\system32\winedevice.exe 0000001b 0 <== 0000001a 0 00000015 0 00000028 winedevice.exe 00000030 0 0000002d 0 0000002c 0 00000029 0 0000002e plugplay.exe 00000034 0 00000033 0 0000002f 0 System information: Wine build: wine-1.9.8 (Staging) Platform: x86_64 Version: Windows 7 Host system: Linux Host version: 3.19.0-32-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 2