https://bugs.winehq.org/show_bug.cgi?id=41670
Bug ID: 41670
Summary: Planetside 2: BattlEye service not starting
Product: Wine
Version: 1.9.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: arsh79(a)gmail.com
Distribution: ---
Created attachment 56062
--> https://bugs.winehq.org/attachment.cgi?id=56062
error in cosole for the 'failed to initialize battleye service' window
Trying to run the latest version of the game, Installer runs fine, but game
doesn't start.
On the first run the launcher tries to install battleye service, which it fails
with the error in the attachment.
On subsequent runs it just hangs forever trying to start the same service
without outputting any error.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=31890
Bug #: 31890
Summary: Cicso communicator throws a segmentation fault when
call is initiated
Product: Wine
Version: 1.5.13
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fastalan(a)gmail.com
Classification: Unclassified
Description of problem:
While emulator the Cisco IP Communicator 8-6-1, sometimes the application seg
faults after the call is initiated. STDOUT
shows:
fixme:mmdevapi:AEV_GetMasterVolumeLevelScalar stub
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. wine ./communicatork9.exe
2. Make a call on the soft phone
Actual results:
When call initiates, the app crashes. The cisco CUCM continues the call, but
the UA Endpoint client is dead.
Expected results:
Caller should hear a ringing sound and call should complete.
Additional info:
3.5.4-2.fc17.x86_64
wine-1.5.13
--
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.
https://bugs.winehq.org/show_bug.cgi?id=48611
Bug ID: 48611
Summary: Cairo Shell v0.3.x (.NET 4.7 app) crashes due to
missing 'HKCU\\Software\\Microsoft\\Windows
NT\\CurrentVersion\\WinLogon\\Shell' registry sub-key
Product: Wine
Version: 5.1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: registry
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
as it says. Some user tried to install it:
https://old.reddit.com/r/winehq/comments/e7f3rz/cairo_requires_microsoft_ne…
So I tried as well. He likely suffers from broken .NET install/WINEPREFIX (not
subject to this report).
Project site: https://cairoshell.com/https://github.com/cairoshell/cairoshell/releases/tag/v0.3.6842
--- snip ---
$ pwd
/home/focht/.wine/drive_c/Program Files (x86)/Cairo Shell
$ WINEDEBUG=+seh,+relay wine ./CairoDesktop.exe >>log.txt 2>&1
...
002c:Call advapi32.RegOpenKeyExW(80000001,016839bc
L"SOFTWARE\\Microsoft\\Windows
NT\\CurrentVersion\\WinLogon",00000000,00020019,0032f428) ret=79b98089
002c:Call ntdll.RtlInitUnicodeString(0032f35c,016839bc
L"SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\WinLogon") ret=7b031b59
002c:Ret ntdll.RtlInitUnicodeString() retval=0000006c ret=7b031b59
002c:Call ntdll.NtOpenKeyEx(0032f428,00020019,0032f364,00000000) ret=7b031b7b
002c:Ret ntdll.NtOpenKeyEx() retval=c0000034 ret=7b031b7b
002c:Call ntdll.RtlNtStatusToDosError(c0000034) ret=7b031b82
002c:Ret ntdll.RtlNtStatusToDosError() retval=00000002 ret=7b031b82
002c:Ret advapi32.RegOpenKeyExW() retval=00000002 ret=79b98089
002c:trace:seh:raise_exception code=c0000005 flags=0 addr=0x3d86e29 ip=03d86e29
tid=002c
002c:trace:seh:raise_exception info[0]=00000000
002c:trace:seh:raise_exception info[1]=00000000
002c:trace:seh:raise_exception eax=00000000 ebx=0032f544 ecx=00000000
edx=016838e0 esi=00000000 edi=0032f4c0
002c:trace:seh:raise_exception ebp=0032f490 esp=0032f48c cs=0023 ds=002b
es=002b fs=0063 gs=006b flags=00210246
002c:trace:seh:call_vectored_handlers calling handler at 0xbb4ec0 code=c0000005
flags=0
002c:Call KERNEL32.GetLastError() ret=00bb4eee
002c:Ret KERNEL32.GetLastError() retval=00000000 ret=00bb4eee
002c:trace:seh:call_vectored_handlers handler at 0xbb4ec0 returned 0
002c:trace:seh:call_stack_handlers calling handler at 0xbb7020 code=c0000005
flags=0
...
--- snip ---
Managed backtrace:
--- snip ---
0009:err:eventlog:ReportEventW L"Application: CairoDesktop.exe\nFramework
Version: v4.0.30319\nDescription: The process was terminated due to an
unhandled exception.\nException Info: System.NullReferenceException\n at
CairoDesktop.Interop.Shell.get_IsCairoUserShell()\n at
CairoDesktop.Startup.Main(System.String[])\n\n"
0009:fixme:advapi:DeregisterEventSource (0xcafe4242) stub
Unhandled Exception: 0009:fixme:ver:GetCurrentPackageId (0x32cad0 (nil)): stub
System.NullReferenceException: Object reference not set to an instance of an
object.
at CairoDesktop.Interop.Shell.get_IsCairoUserShell()
at CairoDesktop.Startup.Main(String[] args)
wine: Unhandled page fault on read access to 00000000 at address 03D86E29
(thread 0009), starting debugger...
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x03d86e29).
--- snip ---
It can be worked around by adding the sub-key/data:
--- snip ---
$ wine reg.exe add "HKCU\\Software\\Microsoft\\Windows
NT\\CurrentVersion\\WinLogon" /v Shell /t REG_SZ /d "explorer.exe" /f
--- snip ---
The app searches 'WinLogon' key first under HKCU. If not present, it will crash
right away. If 'WinLogon' is present but no 'Shell' sub-key it will search
HKLM.
$ sha1sum CairoSetup_32bit.exe
ba4098fce86a2d63a9107c0c18b2f68eb9417039 CairoSetup_32bit.exe
$Â du -sh CairoSetup_32bit.exe
2.2M CairoSetup_32bit.exe
$Â wine --version
wine-5.1-391-g7332de64a5
Regards
--
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.
https://bugs.winehq.org/show_bug.cgi?id=37062
Bug ID: 37062
Summary: Wireshark 1.10 'dumpcap.exe' tool crashes on
unimplemented function wpcap.dll.pcap_findalldevs
Product: Wine
Version: 1.7.23
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Hello folks,
as the summary says ...
--- snip ---
$ pwd
/home/focht/.wine/drive_c/Program Files/Wireshark
$ wine ./dumpcap.exe
...
wine: Call from 0x7b83ae8f to unimplemented function
wpcap.dll.pcap_findalldevs, aborting
wine: Unimplemented function wpcap.dll.pcap_findalldevs called at address
0x7b83ae8f (thread 0026), starting debugger...
--- snip ---
$ sha1sum Wireshark-win32-1.10.10rc0-7-gce4abdf.exe
94b6c2d2029dd00aa05b25bfc4fc6bbdc4ec405d
Wireshark-win32-1.10.10rc0-7-gce4abdf.exe
$ du -sh Wireshark-win32-1.10.10rc0-7-gce4abdf.exe
22M Wireshark-win32-1.10.10rc0-7-gce4abdf.exe
$ wine --version
wine-1.7.23-90-gbdeb761
Regards
--
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.
https://bugs.winehq.org/show_bug.cgi?id=37094
Bug ID: 37094
Summary: Wireshark 1.10 'dumpcap.exe' tool crashes on
unimplemented function wpcap.dll.pcap_open_live
Product: Wine
Version: 1.7.24
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Hello folks,
continuation of bug 37062
--- snip ---
$ pwd
/home/focht/.wine/drive_c/Program Files/Wireshark
$ wine ./dumpcap.exe
...
Capturing on 'virbr0'
wine: Call from 0x7b83ae8f to unimplemented function wpcap.dll.pcap_open_live,
aborting
wine: Unimplemented function wpcap.dll.pcap_open_live called at address
0x7b83ae8f (thread 0009), starting debugger...
--- snip ---
$ sha1sum Wireshark-win32-1.10.10rc0-7-gce4abdf.exe
94b6c2d2029dd00aa05b25bfc4fc6bbdc4ec405d
Wireshark-win32-1.10.10rc0-7-gce4abdf.exe
$ du -sh Wireshark-win32-1.10.10rc0-7-gce4abdf.exe
22M Wireshark-win32-1.10.10rc0-7-gce4abdf.exe
$ wine --version
wine-1.7.24-14-gd1749b5
Regards
--
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.
http://bugs.winehq.org/show_bug.cgi?id=12099
Summary: .NET Framework 1.1 installer requires loadperf.dll in
case of AeDebug -> Auto=0 (unhandled exception dialog)
Product: Wine
Version: CVS/GIT
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Created an attachment (id=11486)
--> (http://bugs.winehq.org/attachment.cgi?id=11486)
example patch to add loadperf.dll and simple UnloadPerfCounterTextStringsW stub
preventing .NET 1.1 installer exception
Hello,
VS.NET 7.x installers modify AeDebug which results in error message box from
.NET Framework 1.1 installer due to an unhandled exception.
With default AeDebug Auto=1 and standalone .NET 1.1 installation you won't
notice it because this exception doesn't affect overall "success" result of
installer.
You can capture output from console to see winedbg actually spawned.
VS.NET 7.x installers add/modify the following JIT debugging keys:
--- snip ---
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\AeDebug\Debugger
Auto: 1 -> 0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
Default: cordbg.exe !a 0x%x8
--- snip ---
Extract from .msi file:
--- snip ---
_FldbVs7eve_RegFile_887_00017.3643236F_FC70_11D3_A536_0090278A1BB8 2
SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug Auto 0
_VS_Debugging___VS7JIT_____X86.3643236F_FC70_11D3_A536_0090278A1BB8)
..
--- snip ---
You can simulate the behaviour on clean ~/.wine if you manually set
AeDebug/Auto=0 (default is 1) and then execute the standalone .NET 1.1
installer.
--- snip ---
002d:Call KERNEL32.lstrlenA(0034f55c "2008-03-17
21:20:25\t\tStarting\tUninstalling performance counters\r\n") ret=79e88b92
..
002d:Call KERNEL32.LoadLibraryA(79e61310 "loadperf.dll") ret=79e907ed
002d:Ret KERNEL32.LoadLibraryA() retval=00000000 ret=79e907ed
002d:Call KERNEL32.GetLastError() ret=79e907f9
002d:Ret KERNEL32.GetLastError() retval=0000007e ret=79e907f9
002d:Call KERNEL32.RaiseException(c06d007e,00000000,00000001,0034f960)
ret=79e9082c
002d:trace:seh:raise_exception code=c06d007e flags=0 addr=0x7b8419a0
002d:trace:seh:raise_exception info[0]=0034f910
002d:trace:seh:raise_exception eax=7b82c3e9 ebx=7b8af3e4 ecx=00000000
edx=0034f904 esi=0034f904 edi=0034f880
002d:trace:seh:raise_exception ebp=0034f868 esp=0034f804 cs=0073 ds=007b
es=007b fs=0033 gs=003b flags=00200212
002d:trace:seh:call_stack_handlers calling handler at 0x402518 code=c06d007e
flags=0
..
002d:Call KERNEL32.UnhandledExceptionFilter(0034f350) ret=7c34c456
wine: Unhandled exception 0xc06d007e at address 0x7b8419a0 (thread 002d),
starting debugger...
002d:Call user32.MessageBoxA(00000000,0034efd8 "Unhandled exception 0xc06d007e
at address 0x7b8419a0.\nDo you wish to debug it?",7b8a3e47 "Exception
raised",00000014) ret=7b841deb
--- snip ---
The message box is shown with the option to dismiss the exception or to debug
it.
This can be pretty confusing to users who have no knowledge how to deal with
this.
Well, actually this exception should never occur.
Wine can prevent this problem by providing a simple loadperf.dll and
UnloadPerfCounterTextStringsW stub.
Output after patch:
--- snip ---
0041:Ret KERNEL32.LoadLibraryA() retval=607d0000 ret=79e907ed
0041:Call KERNEL32.InterlockedExchange(79e96fa8,607d0000) ret=79e9083e
0041:Ret KERNEL32.InterlockedExchange() retval=00000000 ret=79e9083e
0041:Call KERNEL32.GetProcAddress(607d0000,79e919b4
"UnloadPerfCounterTextStringsW") ret=79e908c4
0041:Ret KERNEL32.GetProcAddress() retval=607d8808 ret=79e908c4
0041:Call loadperf.UnloadPerfCounterTextStringsW(0034f9d0 L"u
\"ASP.NET_1.1.4322\"",00000001) ret=79e86e64
0041:fixme:loadperf:UnloadPerfCounterTextStringsW (L"u \"ASP.NET_1.1.4322\"",
1): stub!
0041:Ret loadperf.UnloadPerfCounterTextStringsW() retval=00000000 ret=79e86e64
--- snip ---
Please add this dll and the UnloadPerfCounterTextStringsW stub.
The attached patch is provided as example to quickly validate the problem
solution.
Regards
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44704
Bug ID: 44704
Summary: Screenhero installer runs into crash window (Access
Violation)
Product: Wine
Version: 3.3
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: ---
The Screenhero installer runs into a crash window (Access Violation) while
calling FormatMessageW with id 0x800b0109 which apparently is
CERT_E_UNTRUSTEDROOT
I don`t know where this error comes from but with the patch it gets further to
install all files***, though there`s still a crash in the end.
Patch is at:
https://bugs.winehq.org/attachment.cgi?id=60704&action=diff
***: It also suffers from bug 34989, so you need workaround from here to avoid
a hang: https://bugs.winehq.org/attachment.cgi?id=60702&action=diff
--
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.
https://bugs.winehq.org/show_bug.cgi?id=45841
Bug ID: 45841
Summary: Battleye's BEDaisy.sys requires that PsThreadType and
PsProcessType are defined
Product: Wine
Version: 3.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: dereklesho52(a)Gmail.com
Distribution: ---
Without these two structures, battleye's BEDaisy.sys will crash on an
EXCEPTION_ACCESS_VIOLATION.
Alongside the fixes for #45664 and #44912, Battleye will launch the game.
I will commit my fix to my github shortly after posting this bug:
https://github.com/Guy1524/wine/commits/battleye-work-stable
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44911
Bug ID: 44911
Summary: BattlEye 'BEDaisy' kernel service crashes on
unimplemented function ntoskrnl.exe.PsGetProcessId
Product: Wine
Version: 3.5
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
continuation of bug 44910
--- snip ---
$ WINEDEBUG=+seh,+relay,+ntoskrnl wine net start BEDaisy >>log.txt 2>&1
...
0034:Call driver init 0x78d000
(obj=0x11cc28,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy")
...
0034:Ret ntdll.NtQuerySystemInformation() retval=00000000 ret=7bc803ab
0034:Ret ntoskrnl.exe.ZwQuerySystemInformation() retval=00000000 ret=0082d9b5
...
0034:Call KERNEL32.RaiseException(80000100,00000001,00000002,0065eb78)
ret=7ec1ace2
...
0034:trace:seh:raise_exception code=80000100 flags=1 addr=0x7b446c33
ip=7b446c33 tid=0034
0034:trace:seh:raise_exception info[0]=7ec1ad00
0034:trace:seh:raise_exception info[1]=7ec1e697
wine: Call from 0x7b446c33 to unimplemented function
ntoskrnl.exe.PsGetProcessId, aborting
wine: Unimplemented function ntoskrnl.exe.PsGetProcessId called at address
0xf7c30023:0x7b446c33 (thread 0034), starting debugger...
--- snip ---
$ sha1sum Tibia_Setup.exe
50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe
$ du -sh Tibia_Setup.exe
5.2M Tibia_Setup.exe
$ wine --version
wine-3.5-107-gf4573adb0f
Regards
--
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.