[Bug 47701] New: PUBG Lite does not start from launcher
https://bugs.winehq.org/show_bug.cgi?id=47701 Bug ID: 47701 Summary: PUBG Lite does not start from launcher Product: Wine Version: unspecified Hardware: x86-64 URL: https://lite.pubg.com/en/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: esdrastarsis(a)gmail.com Distribution: --- With the current implementation of httpapi, the launcher works perfectly, but when the game runs it breaks. -- 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=47701 --- Comment #1 from Esdras Tarsis <esdrastarsis(a)gmail.com> --- Log file (warn+all,+seh,+pid,+loaddll,+debugstr): https://drive.google.com/open?id=1G4_vGbbBtLNs1zmSW9n9NYInIJBGlvDH -- 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=47701 Esdras Tarsis <esdrastarsis(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |4.15 -- 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=47701 Esdras Tarsis <esdrastarsis(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download -- 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=47701 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|PUBG Lite does not start |PUBG Lite (.NET 4.5.2 |from launcher |application) does not start | |from launcher CC| |z.figura12(a)gmail.com -- 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=47701 --- Comment #2 from Zebediah Figura <z.figura12(a)gmail.com> --- In the future, you can generally compress the log and attach it. Text files compress well. Unfortunately, it's not really clear what's going wrong. I see a crash, but nothing is obviously causing it. Can you try adding +relay? -- 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=47701 --- Comment #3 from Esdras Tarsis <esdrastarsis(a)gmail.com> --- (In reply to Zebediah Figura from comment #2)
In the future, you can generally compress the log and attach it. Text files compress well.
Unfortunately, it's not really clear what's going wrong. I see a crash, but nothing is obviously causing it. Can you try adding +relay?
The relay log was 2GB in size, I compressed it with 7zip and it was 30MB, but I can't attach it -- 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=47701 --- Comment #4 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Esdras Tarsis from comment #3)
(In reply to Zebediah Figura from comment #2)
In the future, you can generally compress the log and attach it. Text files compress well.
Unfortunately, it's not really clear what's going wrong. I see a crash, but nothing is obviously causing it. Can you try adding +relay?
The relay log was 2GB in size, I compressed it with 7zip and it was 30MB, but I can't attach it
Sure, in that case it's best to upload it elsewhere, hence "generally" above :-) -- 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=47701 --- Comment #5 from Esdras Tarsis <esdrastarsis(a)gmail.com> --- Log file (warn+all,+relay,+seh,+pid,+loaddll,+debugstr): https://drive.google.com/open?id=1b_0YATyF5FYJ8RIGeHy0uMC0ziHeyxEg -- 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=47701 Guilherme S. <oguilherme(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oguilherme(a)protonmail.com -- 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=47701 --- Comment #6 from Zebediah Figura <z.figura12(a)gmail.com> --- Here's an interesting bit: 00d5:00d6:Call advapi32.RegOpenKeyA(80000002,140772d98 "SYSTEM\\ControlSet001\\Control\\Class\\{4D36E968-E325-11CE-BFC1-08002BE10318}\\0000",140772e31) ret=14077614e 00d5:00d6:Ret advapi32.RegOpenKeyA() retval=00000002 ret=14077614e 00d5:00d6:Call advapi32.RegOpenKeyA(80000002,140772df2 "Hardware\\description\\System",140772e31) ret=140776500 00d5:00d6:Ret advapi32.RegOpenKeyA() retval=00000000 ret=140776500 00d5:00d6:Call advapi32.RegQueryValueExA(000000d4,140772e0e "SystemBiosVersion",00000000,00000000,140772e39,140773039) ret=14077663e 00d5:00d6:Ret advapi32.RegQueryValueExA() retval=00000002 ret=14077663e 00d5:00d6:Call advapi32.RegQueryValueExA(000000d4,140772e20 "VideoBiosVersion",00000000,00000000,140772e39,140773039) ret=1407767a5 00d5:00d6:Ret advapi32.RegQueryValueExA() retval=00000002 ret=1407767a5 00d5:00d6:Call advapi32.RegCloseKey(000000d4) ret=1407768e9 00d5:00d6:Ret advapi32.RegCloseKey() retval=00000000 ret=1407768e9 00d5:00d6:trace:seh:NtRaiseException code=c0000005 flags=0 addr=(nil) ip=0 tid=00d6 What happens if you create the values SystemBiosVersion and VideoBiosVersion in HKLM\Hardware\Description\System? I'm not particularly sure what values they should have, but on my virtual machine they're both REG_MULTI_SZ values that describe the virtual machine software vendor. If that doesn't work, I'd try creating the HKLM\System\ControlSet001\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000 key. If neither work, can you please upload a new log? Assuming that it's still going to be registry problems, let's say +seh,+pid,+debugstr,+reg,+server, and if that doesn't offer any further clues we'll go back to analyzing relay logs. -- 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=47701 --- Comment #7 from Guilherme S. <oguilherme(a)protonmail.com> --- Created attachment 65215 --> https://bugs.winehq.org/attachment.cgi?id=65215 wine Launcher.exe (+seh,+pid,+debugstr,+reg,+server)
What happens if you create the values SystemBiosVersion and VideoBiosVersion in HKLM\Hardware\Description\System?
I'm not the OP, but in my Windows 10 installation (which is installed alongside Arch Linux, in the same computer), only the SystemBiosVersion key is present. Anyway, I've created them, ran the PUBG Lite Launcher and it still crashed, but after the wineserver process is finished, the keys I added are automatically removed by wine.
If that doesn't work, I'd try creating the HKLM\System\ControlSet001\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000 key
I've also exported this key from my Win10 installation, but the game still couldn't run. I'm attaching a log file (+seh,+pid,+debugstr,+reg,+server). It's worth mentioning that once you click on the "Run" button in the PUBG launcher, nothing happens (visually), and if you try to terminate this new LauncherAgent.exe" process that is created, the PUBG launcher will keep spawning new ones indefinitely. So the log file probably interrupts at some random instruction, because I had to Ctrl+C at some point. -- 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=47701 --- Comment #8 from Guilherme S. <oguilherme(a)protonmail.com> --- Forgot to mention that I'm running Wine Staging 4.15, on Arch Linux, on a fresh 64-bit prefix (I've only installed .NET, by running "winetricks dotnet472") -- 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=47701 --- Comment #9 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Guilherme S. from comment #7)
I'm not the OP, but in my Windows 10 installation (which is installed alongside Arch Linux, in the same computer), only the SystemBiosVersion key is present. Anyway, I've created them, ran the PUBG Lite Launcher and it still crashed, but after the wineserver process is finished, the keys I added are automatically removed by wine.
Ugh, right, that key is volatile. Presumably you should still be able to add the values and then run PUBG Lite so long as you keep the prefix alive between these (e.g. by just keeping regedit open); is this what you did?
00c6:00c7:trace:reg:open_key (0x44,L"SYSTEM\\ControlSet001\\Control\\Class\\{4D36E968-E325-11CE-BFC1-08002BE10318}\\0000",2000000,0x140772e31) 00c6:00c7:trace:reg:open_key <- 0xc0 00c6:00c7:trace:reg:RegQueryValueExA (00000000000000C0,"DriverDesc",0000000000000000,0000000000000000,0000000140772E39,0000000140773039=512) 00c6:00c7:trace:reg:NtQueryValueKey (0xc0,L"DriverDesc",2,0x22fab0,256)
Did the ControlSet001 key you added contain a DriverDesc value? If the answers to both questions are "yes", I guess the registry queries are probably a red herring... -- 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=47701 --- Comment #10 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Zebediah Figura from comment #9)
Did the ControlSet001 key you added contain a DriverDesc value?
Eh, to clarify, I mean the 0000 key, not literally the ControlSet0001 key. -- 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=47701 --- Comment #11 from Guilherme S. <oguilherme(a)protonmail.com> --- Created attachment 65217 --> https://bugs.winehq.org/attachment.cgi?id=65217 wine Launcher.exe (no extra flags)
Presumably you should still be able to add the values and then run PUBG Lite so long as you keep the prefix alive between these (e.g. by just keeping regedit open); is this what you did?
Yup, I did exactly that.
Did the ControlSet001 key you added contain a DriverDesc value? Eh, to clarify, I mean the 0000 key, not literally the ControlSet0001 key.
Also yes, the value being "NVIDIA GeForce GTX 660". As I exported the whole ControlSet0001 key from my Win10 installation, it added a bunch of other keys too. I would share the .reg file, but I'm not sure if contains any sensitive information. Anyway, if you have some other debugging flags I could try, I'd be glad to help. I haven't seen the log files from Esdras, but in my case, when I click the run button in the PUBG launcher, the following message pops up in the terminal:
013f:err:seh:setup_exception stack overflow 1824 bytes in thread 013f eip 000000007bcdd615 esp 0000000000130ef0 stack 0x130000-0x131000-0x230000
I'm attaching a smaller log file, that was generated when I ran "wine Launcher.exe". -- 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=47701 --- Comment #12 from Esdras Tarsis <esdrastarsis(a)gmail.com> --- Maybe it's the game's anticheat, according to the game's support at this link: https://litesupport.pubg.com/hc/en-us/articles/360019055093-Error-message-in... the anticheat is quite invasive and may even ban your hardware, this is just a speculation. -- 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=47701 --- Comment #13 from Esdras Tarsis <esdrastarsis(a)gmail.com> --- (In reply to Zebediah Figura from comment #9)
(In reply to Guilherme S. from comment #7)
I'm not the OP, but in my Windows 10 installation (which is installed alongside Arch Linux, in the same computer), only the SystemBiosVersion key is present. Anyway, I've created them, ran the PUBG Lite Launcher and it still crashed, but after the wineserver process is finished, the keys I added are automatically removed by wine.
Ugh, right, that key is volatile. Presumably you should still be able to add the values and then run PUBG Lite so long as you keep the prefix alive between these (e.g. by just keeping regedit open); is this what you did?
00c6:00c7:trace:reg:open_key (0x44,L"SYSTEM\\ControlSet001\\Control\\Class\\{4D36E968-E325-11CE-BFC1-08002BE10318}\\0000",2000000,0x140772e31) 00c6:00c7:trace:reg:open_key <- 0xc0 00c6:00c7:trace:reg:RegQueryValueExA (00000000000000C0,"DriverDesc",0000000000000000,0000000000000000,0000000140772E39,0000000140773039=512) 00c6:00c7:trace:reg:NtQueryValueKey (0xc0,L"DriverDesc",2,0x22fab0,256)
Did the ControlSet001 key you added contain a DriverDesc value?
If the answers to both questions are "yes", I guess the registry queries are probably a red herring...
I discovered a probable workaround to save volatile registry keys, run wineserver -w before closing regedit. -- 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=47701 --- Comment #14 from Guilherme S. <oguilherme(a)protonmail.com> --- FWI: https://lite.pubg.com/2021/03/30/notice-april-29-service-termination-notice/ -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla