[Bug 45095] New: BattlEye Issues with fixme:system: SystemParametersInfoW and ntdll stub (Planetside 2)

wine-bugs at winehq.org wine-bugs at winehq.org
Sun Apr 29 20:45:45 CDT 2018


https://bugs.winehq.org/show_bug.cgi?id=45095

            Bug ID: 45095
           Summary: BattlEye Issues with
                    fixme:system:SystemParametersInfoW and ntdll stub
                    (Planetside 2)
           Product: Wine
           Version: 3.7
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: ntdll
          Assignee: wine-bugs at winehq.org
          Reporter: games at mail.timekill.org
      Distribution: ---

Created attachment 61261
  --> https://bugs.winehq.org/attachment.cgi?id=61261
backtrace info

Planetside 2  (and probably other games) still does not make it through
starting BattlEye.  The work on wine 3.6 and 3.7 have helped, however it's not
quite working yet.

After starting the game from DayBreak Games / Planetside 2's Launcher: 
-The "BattlEye Launcher" window pops up with "Starting BattlEye Service"
inside. 
-There is a pause 
-The console spits out 8 lines:

0042:fixme:system:SystemParametersInfoW Unknown action: 116
003a:fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
003a:fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
003a:fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x8794094): stub
002e:fixme:ntdll:EtwEventUnregister (deadbeef) stub.
002e:fixme:ntdll:EtwEventUnregister (deadbeef) stub.
002e:fixme:ntdll:EtwEventUnregister (0) stub.
002e:fixme:ntdll:EtwEventUnregister (deadbeef) stub.
002e:fixme:ntdll:EtwEventUnregister (0) stub.

-The process dies and the "BattlEye Launcher"  window remains on the screen
until closed by the window manager.

The hex number in fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x********)
differs each time

I attempted to take a backtrace of 'PlanetSide2_x64_BE.exe' and
'BEService.exe'.  The former is attached, the latter caused winedbg to hang
when I ran "attach 0x********" in winedbg.

This may be related to Bug 43582
(https://bugs.winehq.org/show_bug.cgi?id=43582)
This may be related to Bug 44910
(https://bugs.winehq.org/show_bug.cgi?id=44910)

-- 
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.



More information about the wine-bugs mailing list