aurora still running unless end in task manager

[mechcentric]

task tray quit does not work; context menu stuck on screen until end in task manager. this is part of how i get logitech sdk to start working after sleep.

[Aytackydln]

related to #55 Can you try with v77? I've added new library to control Logitech devices

[mechcentric]

logitech mouse momentarily lights properly after sleep, then stops. It takes a while, but aurora is now able to quit from the tray, and the context menu stops hanging after a minute. close, but not quite. i appreciate your efforts.

[mechcentric]

It does give me a crash error message when I exit it... but it's not in task manager afterward anymore...

[Aytackydln]

Can you give me the error message or logs? Is cooler master device enabled?

[mechcentric]

Cooler Master device is not enabled.

[kjstew]

I was also having this issue because of my Logitech keyboard. Disabling the persistent profile feature in GHUB fixed it for me (see https://github.com/Aurora-RGB/Aurora/issues/55#issuecomment-1214266955).

This did not fix the SDK failing to start after sleep however.

[Aytackydln]

@kjstew did you try RGB.NET controller from the latest version?

[kjstew]

The RGB.NET controller does not start for me. Here's the error thrown in logs:

[ERROR] 10:45:32: Device provider "LogitechDeviceProvider" threw critical exception RGB.NET.Core.RGBDeviceException: Can't find the Logitech-SDK at one of the expected locations:
 'C:\Program Files\Aurora\x64\LogitechLedEnginesWrapper.dll'
   at RGB.NET.Devices.Logitech.Native._LogitechGSDK.LoadLogitechGSDK()
   at RGB.NET.Devices.Logitech.Native._LogitechGSDK.Reload()
   at RGB.NET.Devices.Logitech.LogitechDeviceProvider.InitializeSDK()
   at RGB.NET.Core.AbstractRGBDeviceProvider.Initialize(RGBDeviceType loadFilter, Boolean throwExceptions)

[Aytackydln]

@kjstew can you do a clean installation and try rgb.net again?

[Aytackydln]

@kjstew sorry for late reply but can you try (rgb.net) again with clean installation? If it doesn't work again I will add the dll to aurora itself.

[kjstew]

@Aytackydln Sure, I will try when I can. I'm currently away from my desktop and will return in a week. Apologies for the delay

[Aytackydln]

Sadly this can happen from many reasons; devices not releasing, some legacy/bad coded system integrations etc. Unless the cause is specific like when certain device, layer, configuration is enabled I can't solve it properly.

I will be adding a workaround for this though. I will set a timer for shutdown process.

Feel free to open new issue though.