Flame 2025, ADSK Identity Manager and HPAnyware

Same here on 2025.2.

Flame support had me open a different case with the Autodesk InL team (installation and licensing) and says the issue is in their world. Feel free to reference that Case ID: 23157159 in addition to the other cases mentioned in this thread. The case status is currently “Open - Waiting for Internal Action.”

I’ll never understand why people run old software…

:joy:

6 Likes

@cnoellert - and I’ll never understand why old people run software…

4 Likes

Here’s something that occurred to me today after updating my Mac OS from 15 to 15.1 Sequoia with Flame 2025.2

Flame 2025.2 was already installed and after I updated the OS from 15 to 15.1 I started seeing the issue where whenever Flame is launched, the web browser loads first wanting you to log into your ADSK account even if you have been logged in.

I uninstalled/reinstalled Flame 2025.2 then I went into Privacy settings / Full disk, and toggled every Flame-related item.

This fixed it for me. Not sure if the uninstall/reinstall was necessary so if it’s happening for you, try toggling the items first.

Hi Friends,

If you are still experiencing this issue, you may want to try the latest Identity Manager update that was just released.

manage.autodesk.com > Products and Services > Product Updates > Updates

1 Like

This appears to have fixed the issue so far. Will be keeping an eye on it as we continue testing next week. :+1:

1 Like

Thanks for testing Aaron. Have a great weekend!

This updated Identity Manager package will also be rolled out in the upcoming 2025.2.2 Update. But feel free to download the package for previous versions.

Looking forward your feedback here on the fix.

2 Likes

Is this expected to fix my “black screen of death” too? @Slabrie

Hello Alan!

I doubt the new version fixes this issue but since you are the only one who can reproduce this problem, could you replicate it and provide HP Anyware the support logs they asked you to provide. Ideally, if you could build a config without your Gnome customization and validate the fix that would be great. Then add your customization and see what happens. if you reproduce, generate logs so HP Anyware can investigate the problem.