protonscr

NCSOFT Purple launcher: The Lobby crashes right away after logged in on Proton

protonclosed
ValveSoftware/Proton#8515 · opened 2025-03-12 by robstarmcdonald · updated 2025-03-12 · 5 comments · github
Rrobstarmcdonald 2025-03-12 github

Compatibility Report

  • Name of the game with compatibility issues: Purple
  • Steam AppID of the game: Unknown, because this app is not available on Steam and will be running as a non-steam

System Information

I confirm:

  • [ ] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

Symptoms

Hello everyone (Including @kisak-valve),
Steam Snap is ready for me to play games on Steam whatever I want unlike a flatpak version or a deb version, also the login for Purple is now able to work, but its lobby still has issues, it crashes on launching the lobby.

So, I hope Proton 10.0 has that fixed in a future.

Reproduction

Files in my Github Gist page should includes System info, Steam Runtime info and Proton Log.

Rrobstarmcdonald 2025-03-12 github

Welcome to part 2 about NCSOFT's Purple launcher issues.
This thread is a successor to this old one because, previously the login won't work period, and this current thread talks about the Lobby crashes on the boot.

FWIW, feel free to make a comments below, about your ideas or bug fixes that is corrected by an updates. 🤠

Rrobstarmcdonald 2025-03-12 github

On a terminal debug, it displayed the reason why the lobby crashes at the boot.

[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'Microsoft.Win32.TaskScheduler.TaskService' threw an exception. ---> System.NotImplementedException: The method or operation is not implemented.
  at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR (System.Int32 errorCode) [0x0000a] in <94942505ad4c4982af4db0763017d52e>:0 
  at (wrapper cominterop) Microsoft.Win32.TaskScheduler.V2Interop.ITaskService.get_ConnectedUser()
  at (wrapper cominterop-invoke) Microsoft.Win32.TaskScheduler.V2Interop.ITaskService.get_ConnectedUser()
  at Microsoft.Win32.TaskScheduler.TaskService.Connect () [0x00138] in <4f8b5d18b80e4c1fbc5f90ef9d5358bd>:0 
  at Microsoft.Win32.TaskScheduler.TaskService..ctor () [0x0000c] in <4f8b5d18b80e4c1fbc5f90ef9d5358bd>:0 
  at (wrapper remoting-invoke-with-check) Microsoft.Win32.TaskScheduler.TaskService..ctor()
  at Microsoft.Win32.TaskScheduler.TaskService.get_Instance () [0x00007] in <4f8b5d18b80e4c1fbc5f90ef9d5358bd>:0 
  at Microsoft.Win32.TaskScheduler.TaskService..cctor () [0x00051] in <4f8b5d18b80e4c1fbc5f90ef9d5358bd>:0 
   --- End of inner exception stack trace ---Some threads failed to suspend before timeout reached. Continuing with shutdown.

Yes, it's in the log as well.

Kkisak-valve maintainer 2025-03-12 github

Closing as a duplicate of #7878.

Rrobstarmcdonald 2025-03-12 github

Hello @robstarmcdonald, this is not a valid reason to fragment the discussion across multiple issue reports. In general, we're using one issue report per game title and this issue report should cover all issues with this non-Steam launcher.

Hello @kisak-valve

This is not acceptable, I'm going to re-create the main description in a first thread that has been re-opened by you and renaming it to the same title to prevent confusion. Plus, I see no reason for it be marked as duplicate of #7878, because the first one talks about the whole app won't work, not just lobby.

Rrobstarmcdonald 2025-03-12 github

For those of you folks are about to make thread, please do it in #7878 because it was closed by @kisak-valve for a silly reason.

Proton versions

Upstream links