June 2016 - Wine-bugs - list.winehq.org

[Bug 30837] New: Star Trek Online doesn't detect joystick/gamepad
by wine-bugs＠winehq.org 15 Aug '16

15 Aug '16

http://bugs.winehq.org/show_bug.cgi?id=30837 Bug #: 30837 Summary: Star Trek Online doesn't detect joystick/gamepad Product: Wine Version: 1.5.5 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: vitor.dominor(a)gmail.com Classification: Unclassified Recently I decided to try playing Star Trek Online with one of my old but still working xbox 1 gamepads. For that purpose, I installed the xboxdrv (the userspace driver for xbox 360 and 1 gamepads) and after running xboxdrv with the command xboxdrv --silent --trigger-as-button, I started the game. The game has support for joysticks (I made sure I enabled joystick support in the in-game options). However, the game does not detect it, since it does not respond to any button presses or axis movements from the gamepad. When running the game from the terminal, the output I get with the gamepad attached to the PC is attached to this bug report. I have tried running the game natively on Windows 7 and XP SP3 with the gamepad attached and it is detected and runs as expected. Furthermore, by running STO with apimonitor from http://www.rohitab.com/apimonitor in Windows, I was able to determine that the game uses direct input 8, specifically the IDirectInputDevice8 and IDirectInput8 interfaces, to detect and control the system mouse and any attached joystick. It uses in particular the IDirectInput8::EnumDevices to find any available joysticks. In order to determine if this is an issue specific to this game running on Wine, I tried using the gamepad with another game well supported by wine and which also supports joysticks: Trackmania Nations Forever. This one detects the gamepad as a joystick automatically and by adding +dinput to WINEDEBUG, I noticed the following line on the output: Code: trace:dinput:IDirectInputWImpl_EnumDevices (this=0x12f718,0x0004 'DIDEVTYPE_JOYSTICK',0x8fc5a0,0x12238a0,0001). After that, wine outputs successfull detection of the joystick: Code: trace:dinput:find_joydevs Found a joystick on /dev/input/event16: Xbox Gamepad (userspace driver) ({9e573eda-7734-11d2-8d4a-23903fb6bdf7}) Next, while running STO on wine with WINEDEBUG="+dinput": and while the game detects and initializes the system mouse through dinput, it seems to initialize the IDirectInput8 Interface, but it does not enumerate any joystick unlike Trackmania. -- 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 8

[Bug 40765] New: Python 3.5.1 interpreter crashes, needs __fpe_flt_rounds
by wine-bugs＠winehq.org 15 Aug '16

15 Aug '16

https://bugs.winehq.org/show_bug.cgi?id=40765 Bug ID: 40765 Summary: Python 3.5.1 interpreter crashes, needs __fpe_flt_rounds Product: Wine Version: 1.9.11 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: api-ms-win-* Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 54666 --> https://bugs.winehq.org/attachment.cgi?id=54666 Backtrace To reproduce: 1. Download https://www.python.org/ftp/python/3.5.1/python-3.5.1-embed-win32.zip 2. Unzip python-3.5.1-embed-win32.zip 3. Run `wine python.exe` $ sha1sum python-3.5.1-embed-win32.zip 240dd2da695fea58847b9fbc5420d31f75f275ce python-3.5.1-embed-win32.zip -- 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 37503] New: Bad reflow in joystick control panel
by wine-bugs＠winehq.org 15 Aug '16

15 Aug '16

https://bugs.winehq.org/show_bug.cgi?id=37503 Bug ID: 37503 Summary: Bad reflow in joystick control panel Product: Wine Version: 1.7.30 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: adys.wh(a)gmail.com Distribution: --- Created attachment 49892 --> https://bugs.winehq.org/attachment.cgi?id=49892 Screenshot See attachment. The word "applet" is cut. If I change tab and go back, the word applet is on a newline as it should be. -- 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 26160] New: Broken control path in mcicda
by wine-bugs＠winehq.org 15 Aug '16

15 Aug '16

http://bugs.winehq.org/show_bug.cgi?id=26160 Summary: Broken control path in mcicda Product: Wine Version: 1.3.13 Platform: x86 OS/Version: Mac OS X 10.5 Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net I'm thankful to C. Robinson for making mcicda work on my Linux machines since wine-1.1.5. Since then the code supports 2 modes of operation, either via - IOCTL_CDROM_*_AUDIO (PLAY/STOP/PAUSE/RESUME/SEEK) - or via a separate thread using DirectSound with IOCTL_CDROM_RAW_READ. READ_TOC is needed in both modes. However, commit 8afa626faa3c5aa2d32d17dca77edaf9efb3a5da uses as selector if (wmcda->hThread != 0) { which causes inconsistent results as the thread may be long dead. I believe that is not the correct way to select whether to invoke either thread/DS+RAW_READ commands or IOCTL_CDROM_*_AUDIO ones. Consider this sequence of MCI commands: cmd hThread comment play -- start hThread stop # !0 => SetEvent stopEvent, hThread becomes 0 stop # =0 => DeviceIoControl resume # =0 => DeviceioControl play resume # !0 => DSB+Play, unlike previously status mode !0 GetStatus yields PLAY, later STOP it will never detect that a disk was long ejected! stop status mode =0 GetStatus performs IoControl instead and hence reports current and correct state. It's fine that the code supports 2 modes of operation, the bug is that the current code confuses itself as to which branch should be taken and produces results depending on the history of commands rather than the current state (and HW capabilities), wrongly mixing both code paths, leading to incorrect results. IMHO a binary decision via hThread is wrong, there are more states to consider: - DSB + RAW_READ is useable / being used; - IOCTL_CDROM_PLAY_AUDIO is useable / being used - don't know yet. This issue becomes more important now as MacOS support is getting close (see bug #20323). This issue becomes more important now as MacOS support is getting close (see bug #20323). It does not implement the IOCTL_CDROM_*_AUDIO and spits out unneeded err: and fixme: to the console. I mentioned that I'd about this issue in bug #20323 comment #4 last year. -- 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 14

[Bug 20323] New: MacOS mcicda does not play audio CD
by wine-bugs＠winehq.org 15 Aug '16

15 Aug '16

http://bugs.winehq.org/show_bug.cgi?id=20323 Summary: MacOS mcicda does not play audio CD Product: Wine Version: 1.1.30 Platform: PC OS/Version: Mac OS X 10.5 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net mcicda invokes GetDriveTypeW which returns 3, the same as for C: and other HD drives. It expects DRIVE_CDROM(5). E: is not recognized as CD-ROM by Wine, although it is created by the mountmgr. It points to /Volumes/Audio-CD. Indeed /Volumes/Audio-CD/ is a directory full of files named "N Titel NN.aiff", e.g. "2 Titel 02.aiff". e:: points to /dev/rdisk2 GetDriveTypeW in turn calls: trace:file:CreateFileW returning 0x68 trace:vxd:DeviceIoControl (0x68,6d4084,0x32f2ac,16,0x32f2ac,16,0x0,0x0) trace:ntdll:NtDeviceIoControlFile (0x68,0x0,0x0,0x0,0x32f018,0x006d4084,0x3 2f2ac,0x00000010,0x32f2ac,0x00000010) code=006d4084 (device=6d) is weird, as winioctl.h only lists FILE_DEVICE_* 01 .. 39 I have not looked further into the origin of this code. Bypassing this test allows mcicda to open cdaudio. mciSendString: open e: type cdaudio alias y + status cdaudio length + status cdaudio length 2 + status cdaudio number of tracks work -- so there's hope -- whereas - status cdaudio position - status cdaudio current track - status cdaudio media present - seek and - play fail. fixme:ntdll:server_ioctl_file Unsupported ioctl 2402c (device=2 access=1 func=b method=0) fixme:mcicda:MCICDA_GetError Unknown mode 50 status length etc. show that DeviceIoControl(wmcda->handle, IOCTL_CDROM_READ_TOC works. -- 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 35165] New: Quake Live standalone login window shows difficult to read text in the username field
by wine-bugs＠winehq.org 15 Aug '16

15 Aug '16

http://bugs.winehq.org/show_bug.cgi?id=35165 Bug ID: 35165 Summary: Quake Live standalone login window shows difficult to read text in the username field Product: Wine Version: 1.7.8 Hardware: x86-64 URL: http://quakelive.com OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexandru.balut(a)gmail.com Classification: Unclassified Created attachment 46910 --> http://bugs.winehq.org/attachment.cgi?id=46910 Entered "mmmmmmmm" in the two fields Install the app (installer might crash, but ignore that), start it, notice the text entered in the username/password fields appears in a weird way. When pressing backspace to delete the last character, the text suddenly seems to appear fine but there is an unexpected margin between the right-side of the text and the cursor. Then if more letters are entered they continue to be displayed broken. Does not happen with digits for some reason. -- 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 13

[Bug 40816] New: Webrotate (FREE) application hangs during installation
by wine-bugs＠winehq.org 15 Aug '16

15 Aug '16

https://bugs.winehq.org/show_bug.cgi?id=40816 Bug ID: 40816 Summary: Webrotate (FREE) application hangs during installation Product: Wine Version: 1.9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bob.mt.wya(a)gmail.com Distribution: --- Created attachment 54761 --> https://bugs.winehq.org/attachment.cgi?id=54761 WINEDEBUG=+relay,+seh,+tid console output (truncated) Installation of this application hangs after pressing the INSTALL button. I've not dug through the trace to see what's going wrong - but it's not immediately obvious what (Wine) component is at fault. The last few lines of the console trace repeat ad infinitum (so I've truncated the attached version): 000d:Call ntdll.RtlAllocateHeap(00110000,00000000,00000014) ret=7efeb721 000d:Ret ntdll.RtlAllocateHeap() retval=00179098 ret=7efeb721 000d:Call ntdll.RtlAllocateHeap(00110000,00000000,00000016) ret=7efeb44b 000d:Ret ntdll.RtlAllocateHeap() retval=001790b8 ret=7efeb44b 000d:Call ntdll.RtlAllocateHeap(00110000,00000000,00000006) ret=7efeb44b 000d:Ret ntdll.RtlAllocateHeap() retval=001790d8 ret=7efeb44b 000d:Call ntdll.RtlAllocateHeap(00110000,00000000,00000006) ret=7efeb44b 000d:Ret ntdll.RtlAllocateHeap() retval=001790f0 ret=7efeb44b -- 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 40787] New: POILoader quits right after start
by wine-bugs＠winehq.org 15 Aug '16

15 Aug '16

https://bugs.winehq.org/show_bug.cgi?id=40787 Bug ID: 40787 Summary: POILoader quits right after start Product: Wine Version: 1.9.12 Hardware: x86 URL: http://www.garmin.com/us/maps/poiloader OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ladislav.laska(a)gmail.com Distribution: ArchLinux The Garmin POI Loader quits after start, without an error message. This might be related to bug #22544, but it's an old bug, and I'm not really sure if it's regression. I've tried testing this with the 1.7.11 as suggested, but the result is the same. Installer works (and required mono). Whenever I start the application, I get a few messages on terminal, the POI Loader initial screen shows up for a few seconds, but is non-responsive, and crashes promptly, without further error: krakonos(a)wallaby ~/[...]/POI Loader $ wine POILoader fixme:dbghelp:elf_search_auxv can't find symbol in module fixme:dbghelp:elf_search_auxv can't find symbol in module fixme:dbghelp:elf_search_auxv can't find symbol in module krakonos(a)wallaby ~/[...]/POI Loader $ wine --version wine-1.9.12 The wine I'm using is a version from Arch repository. I'd be glad to provide more information, but I have no idea where to look for problems. Download is available here: http://www.garmin.com/us/maps/poiloader Tested with POI Loader 2.7.3 (the latest available) -- 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 34928] New: X Rebirth only (re)draws HUD Elements
by wine-bugs＠winehq.org 13 Aug '16

13 Aug '16

http://bugs.winehq.org/show_bug.cgi?id=34928 Bug #: 34928 Summary: X Rebirth only (re)draws HUD Elements Product: Wine Version: 1.7.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: skython(a)web.de Classification: Unclassified Created attachment 46545 --> http://bugs.winehq.org/attachment.cgi?id=46545 Screenshot 1: Rendering bugs after starting a new free game. The game doesn't renders everything except the HUD. When you start a new free game the screen becomes black and only the HUD elements are visible. If any of the HUD elements is moving, you see them being 'copied' over the black background. The attached screenshots are showing this behaviour. If you alter some graphics settings (for example antialiasing) while ingame, you can see the game rendering everything just fine for a single frame. But then again the rendered scene doesn't redraw and HUD is being copied again. You can see this behaviour on the second screenshot. The terminal repeatedly says: err:d3d:wined3d_debug_callback 0x193ef0: "GL_INVALID_OPERATION error generated. Buffer is mapped.". err:d3d_draw:drawStridedFast >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawElementsBaseVertex @ ../../../wine/dlls/wined3d/drawprim.c / 64 I'm using Archlinux and the current Wine version 1.7.6 I already tried altering several rendering settings using winetricks. No luck so far. Any help is appreciated -- 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 40725] New: 8-bit Armies crashes on start (32-bit prefix, Windows 7 mode)
by wine-bugs＠winehq.org 13 Aug '16

13 Aug '16

https://bugs.winehq.org/show_bug.cgi?id=40725 Bug ID: 40725 Summary: 8-bit Armies crashes on start (32-bit prefix, Windows 7 mode) Product: Wine Version: 1.9.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fjfrackiewicz(a)gmail.com Distribution: --- Created attachment 54631 --> https://bugs.winehq.org/attachment.cgi?id=54631 Terminal output for Wine 1.9.11 Staging no CSMT I am attempting to run this game in a clean 32-bit prefix and it crashes while loading. Running the command "wine ClientG.exe" gets me a splash screen and opens up a very tiny square which I assume is the game's window. After a few seconds the game then crashes. I have checked that ClientG.exe, the game's executable, is in fact a 32-bit file: file ClientG.exe ClientG.exe: PE32 executable (GUI) Intel 80386, for MS Windows I am attempting to run the game in Windows 7 mode as it does not support Windows XP. I have attached the terminal output as the game loads then crashes. I am using Wine 1.9.11 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 17