Mouse cursor gets lost in game (wine 1.9.21)

[Cookie]

I am very happy that the FFB works now with my USB wheel, but after the upgrade to the last version of wine, the mouse cursor gets lost when leaving the game to the game menu.
It worked fine with the previous wine version.
Moving the mouse, I can see the buttons get lighted but I can not click a button, I can only leave the game with keyboard esc...

Any idea?

Thanks for helping

Axel

PS
The mouse cursor is only visible in the game menues, in game there is no mouse cursor, so leaving the menu to the game the mouse cursor is switched off, but it does not reappear leaving the game to the menu.

[Bob Wya]

@Cookie

That sounds like a pure regression (possibly). I'd recommend filing a bug on the WineHQ Bugzilla. Attach a console log to the report.
Performing a full regression test would provide a much faster response to your bug report.

Bob

[Cookie]

This is the log.txt

But the main problem is the Mouse cursor lost, Wheel (joystick) related errors are no problem.

Code: Select all

err:service:load_reg_dword Error 1804 while reading value L"Type"
err:service:scmdatabase_load_services Error 1804 reading registry key for service L"papycpu2" - skipping
fixme:win:LockWindowUpdate (0x10054), partial stub!
fixme:win:LockWindowUpdate ((nil)), partial stub!
fixme:dinput:JoystickWImpl_SetProperty DIPROP_CALIBRATIONMODE(1)
fixme:tapi:lineInitialize (0x7dee70, 0x400000, 0x4b8720, "Grand Prix Legends", 0x7dee74): stub.
fixme:ras:RasEnumConnectionsA (0x29fce6c,0x29fce18,0x29fce1c),stub!
fixme:ras:RasEnumConnectionsA RAS support is not implemented! Configure program to use LAN connection/winsock instead!
err:dinput:JoystickWImpl_Acquire Failed to open device /dev/input/event5: 4 Unterbrechung während des Betriebssystemaufrufs
err:dinput:JoystickWImpl_Acquire Failed to open device /dev/input/event5: 4 Unterbrechung während des Betriebssystemaufrufs
fixme:win:LockWindowUpdate (0x10054), partial stub!
fixme:win:LockWindowUpdate ((nil)), partial stub!
fixme:dinput:joy_polldev joystick cannot handle type 21 event (code 96)
fixme:dinput:joy_polldev joystick cannot handle type 21 event (code 97)
fixme:dinput:joy_polldev joystick cannot handle type 21 event (code 96)
fixme:dinput:joy_polldev joystick cannot handle type 21 event (code 97)
fixme:dinput:joy_polldev joystick cannot handle type 21 event (code 0)
fixme:dinput:joy_polldev joystick cannot handle type 21 event (code 0)
fixme:dinput:joy_polldev joystick cannot handle type 21 event (code 0)
fixme:win:LockWindowUpdate (0x10054), partial stub!
fixme:win:LockWindowUpdate ((nil)), partial stub!
err:dinput:JoystickWImpl_Unacquire Failed to set autocenter to ffff: 9 Ungültiger Dateideskriptor

[Bob Wya]

This is the log.txt

But the main problem is the Mouse cursor lost, Wheel (joystick) related errors are no problem.
...

OK... So what I'd suggest in this case is to run:

Code: Select all

wineserver -d -f -p &>~/wineserver_debug_log.txt

to launch a persistent, foreground wineserver process for your Wineprefix.

Then launch your game/application as normal, in a seperate terminal tab.

You'd need to stop the wineserver process as soon as you re-enter the application menu. Hopefully the resulting wineserver log will be more useful for a bug report.

Bob

[Cookie]

I made another test with wine 1.9.21 on a 2nd PC:

The problem occurs only with the NVidia GTX960 GPU prop driver at mint18 PC!

2nd PC has AMD HD6870 GPU with last fglrx driver mint17.3 and no problem loosing the cursor.

So maybe it is a NV driver problem?

[Bob Wya]

I made another test with wine 1.9.21 on a 2nd PC:

The problem occurs only with the NVidia GTX960 GPU prop driver at mint18 PC!

2nd PC has AMD HD6870 GPU with last fglrx driver mint17.3 and no problem loosing the cursor.

So maybe it is a NV driver problem?

Can you try a different Nvidia driver version? What obsolete driver version is Clem shipping by default these days??

I had a look on Nvidia / devtalk / Linux ... The channel is so noisy (probably with totally mis-configured systems )...
There was one older thread about cursor issues I found: Possible 346.35 regression: Hardware cursor not drawn on top screen edge

Also Wine can suffer from focus issues - since X draws windows in a different order from MS Windows. So the cursor could be focus on some random junk behind your main window (like a launcher window, etc.).
Or it could be Desktop Environment bug with Cinnamon.

Bob

[Cookie]

Now wine is updated to 1.9.22 on both systems.

AMD still runs fine, the NVidia driver is also updated to the last 367 and the problem remains.

I found a workaround to not have to leave the sim, I switch to the next desktop and back, voila the cursor is back

[Bob Wya]

Now wine is updated to 1.9.22 on both systems.

AMD still runs fine, the NVidia driver is also updated to the last 367 and the problem remains.

I found a workaround to not have to leave the sim, I switch to the next desktop and back, voila the cursor is back

No there's definitely more issues with the Nvidia proprietary driver and 2D desktop acceleration... It's just not as well integrated with mesa. The AMD driver tends to give a much less rough experience... Then you fire up a game and Nvidia wins hands-down in the 3D space still...

I usually clear missing mouse cursor issues, e.g. after running a Wine game w/ Steam say, by simply ALT-TAB'ing between my open windows. Anything like that will cause your Window manager to re-establish Window focus - away from your Wine applications.

I'm running Nvidia drivers version 375.10 on my laptop - so I'm not sure what you mean by "last 367"...

Bob

[Cookie]

NVIDIA Driver Version: 367.57
is the latest one from
deb-src http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial main

I am pretty new to linux...

edit

Thx to your answer I updated the NV driver to 370.28,

but the problem is still the same...

[Bob Wya]

NVIDIA Driver Version: 367.57
is the latest one from
deb-src http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial main

I am pretty new to linux...

edit

Thx to your answer I updated the NV driver to 370.28,

but the problem is still the same...

Are you running Unity?
Because Window Managers will interact in different ways with the proprietary Nvidia Drivers. They tend to handle focus stealing in a subtly different ways. I know that Plasma 5 (my preferred Desktop - is quite configurable in this regard). Perhaps a retest with a different Desktop Environment (e.g. Mate)?

Bob