wine-bugs May 2016

wine-bugs@winehq.org

1 participants
7576 discussions

[Bug 40384] New: dinput8:dinput regression caused by new compiler
by wine-bugs＠winehq.org 19 Aug '16

19 Aug '16

https://bugs.winehq.org/show_bug.cgi?id=40384 Bug ID: 40384 Summary: dinput8:dinput regression caused by new compiler Product: Wine Version: 1.9.6 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The WineHQ upgrade changed the cross-compiler used to generate the reference WineTest executables. Since the upgrade the dinput8:dinput test has these failures on all 32 bit Windows platforms: dinput.c:519: Test failed: EnumDevicesBySemantics did not call the callback hr=80070057 dinput.c:520: Test failed: EnumDevicesBySemantics should enumerate the keyboard dinput.c:521: Test failed: EnumDevicesBySemantics should enumerate the mouse dinput.c:527: Test failed: EnumDevicesBySemantics failed hr=80070057 dinput.c:535: Test failed: EnumDevicesBySemantics failed hr=80070057 dinput.c:536: Test failed: There should be devices available before action mapping available=0 dinput.c:543: Test failed: EnumDevicesBySemantics failed: hr=80070057 dinput.c:548: Test failed: EnumDevicesBySemantics failed hr=80070057 dinput.c:554: Test failed: EnumDevicesBySemantics failed: hr=80070057 dinput.c:559: Test failed: EnumDevicesBySemantics failed hr=80070057 dinput.c:565: Test failed: EnumDevicesBySemantics failed hr=80070057 dinput.c:571: Test failed: EnumDevicesBySemantics failed hr=80070057 dinput.c:577: Test failed: EnumDevicesBySemantics failed hr=80070057 See: https://test.winehq.org/data/tests/dinput8:dinput.html https://www.winehq.org/pipermail/wine-devel/2016-March/112371.html I can reproduce the problem with this compiler: $ i686-w64-mingw32-gcc --version i686-w64-mingw32-gcc (GCC) 5.3.1 20160205 But if I recompile the tests with -O0 the failures go away which points to a compiler bug. We need to either: * Switch to a non buggy compiler to build the reference WineTest executables. (which might involve reporting the bug in the first place) * Add 'CFLAGS = -g -O0' to the test's Makefile.in as a workaround. (preferably once we can point to a relevant compiler bug) * Find some other nicer workaround in the C file. -- 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 37433] New: Game dont run and show dont have winsock2 correct
by wine-bugs＠winehq.org 18 Aug '16

18 Aug '16

https://bugs.winehq.org/show_bug.cgi?id=37433 Bug ID: 37433 Summary: Game dont run and show dont have winsock2 correct Product: Wine Version: 1.7.29 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: Mint Once game launched, show loading screen and after this show winsock 2 error, non proper winsock 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 11

[Bug 39662] New: Printing problem when CUPS printer description contains spaces
by wine-bugs＠winehq.org 18 Aug '16

18 Aug '16

https://bugs.winehq.org/show_bug.cgi?id=39662 Bug ID: 39662 Summary: Printing problem when CUPS printer description contains spaces Product: Wine Version: 1.7.55 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ragaconi(a)hotmail.com Distribution: --- It seems that "win.ini" is auto generated every time I run wine program. In win.ini CUPS printer seems to be named by its description in CUPS. When this description contains spaces a problem printing does not work. -- 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 7

[Bug 24147] New: Worms Reloaded: Screen position issues at non-native resolution
by wine-bugs＠winehq.org 17 Aug '16

17 Aug '16

http://bugs.winehq.org/show_bug.cgi?id=24147 Summary: Worms Reloaded: Screen position issues at non-native resolution Product: Wine Version: 1.3.1 Platform: x86 URL: http://steampowered.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: adys.wh(a)gmail.com Created an attachment (id=30389) --> (http://bugs.winehq.org/attachment.cgi?id=30389) Screenshot of behaviour See attached screenshot. At resolutions other than native, the game screen "slides" towards the bottomleft and hides part of the screen outside the display. err:ole:RevokeDragDrop invalid hwnd (nil) err:ole:RevokeDragDrop invalid hwnd 0x50130 err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed? err:ole:CoGetClassObject class {074b110f-7f58-4743-aea5-12f15b5074ed} not registered err:ole:CoGetClassObject no class object {074b110f-7f58-4743-aea5-12f15b5074ed} could be created for context 0x1 err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x2953530,0x2953490): stub -- 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 32265] New: Polycom People+Content IP crashes when attempting to stream desktop to remote display
by wine-bugs＠winehq.org 17 Aug '16

17 Aug '16

http://bugs.winehq.org/show_bug.cgi?id=32265 Bug #: 32265 Summary: Polycom People+Content IP crashes when attempting to stream desktop to remote display 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: aboyd(a)fusionio.com Classification: Unclassified Created attachment 42578 --> http://bugs.winehq.org/attachment.cgi?id=42578 Backtrace of PPCIP crash When I try to stream my desktop to a remote display (a Polycom HDX 7000 HD) using People+Content IP, I can connect to the display fine, but when I press the play button, PPCIP freezes for about 20 seconds, then crashes. I've attached the backtrace. -- 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 4

[Bug 27798] New: GTA3 & GTAVC rendering is messed up
by wine-bugs＠winehq.org 17 Aug '16

17 Aug '16

http://bugs.winehq.org/show_bug.cgi?id=27798 Summary: GTA3 & GTAVC rendering is messed up Product: Wine Version: 1.3.23 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: b7.10110111(a)gmail.com See http://i.imgur.com/EigrV.png Works correctly in 1.3.22, appears in 1.3.23, remains in 1.3.24. Reproducible on my intel (EEE PC 901) video: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03) , but NOT on nvidia gtx460. Will try to do regression testing, but... well, intel Atom... -- 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 35

[Bug 32935] New: Detailed view int "file->open" window MSoffice 2003, not showing details
by wine-bugs＠winehq.org 17 Aug '16

17 Aug '16

http://bugs.winehq.org/show_bug.cgi?id=32935 Bug #: 32935 Summary: Detailed view int "file->open" window MSoffice 2003, not showing details Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: chpnp(a)free.fr Classification: Unclassified I happily run office 2003, i still have a minor issue which is annoying on a day to day basis when i open a file, and from the open window select the "detailed view", only the names will show (no modification date) Is there anything i am missing here ? can it be solved somehow ? This is wine 1.4 or 1.5 (i think i have the problem with both) and this happens on Ubuntu 12.04 (64 bits) and Slitaz 4.0 (32 bits) Thanks -- 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 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 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

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 May 2016