I posted this up on Discord and was asked to put it here for those who may run into the same trouble.
I installed 2025.1 on Linux 8.5 on 2 of my Lenovo P620 machines. I reproduced the same behavior on both machines. I start the app and get the link to a browser, with Firefox being the default, then have to sign in to Autodesk.com and then it bounced back to the app with this error.
It allows you to open Flame and work, but when the auth times out, it crashes Flame and then logs you out.
Bob Maple sent some help my way with
*. With flame not running (not a problem for you ) try deleting ~/.gnome2/keyrings and ~/.local/share/keyrings (you may not have one or the other)
*. reboot, then login, launch Flame, login to your AD account when it yells at you, and see if it stays behaving
That did not help me, unfortunately. To get thing working, I installed Chrome and then forced Linux to have Chrome as a default. Once I did that, Flame opened Chrome to authenticate. In doing so, it allowed a pop-up that was some type of Autodesk Application Manager. I approved that to run, and now it works as expected. No crashes.
Still have not been able to get Firefox to allow the authentication to work properly.
Thanks for this info @marcwellington. I hoped it was a new solution not covered in this related thread, but unfortunately your steps didn’t solve it for me. I still get the “Unable to access information in your keyring” message and have to go through the prompts every time I launch Flame. I get the same results with either Chrome or Firefox set as the default browser.
Before this, how often did your auth timeout and crash Flame? What indicators were there that it was the cause of the crash?
Not auth related, but in my experience Firefox on Linux seems to have holes. Can’t use Frame IO in Firefox on my Linux Flame. Begrudgingly have to use Chrome regularly. So this problem may not be ADSK only problem.
I did. I always install the DKU required for the update before I update. Just good practice. Thanks for the suggestion. This behavior happened 2 different machines here.
Let me clarify, the Firefox app works for everything EXCEPT authorizing the Flame license via the app interchange. ONLY CHROME as the default works. I did install the DKU first on both machines and then the app. We get the same behavior on both. Also, we did the fix via Mr. Maple and the notes in the link that pop up that tell you there is an issue and the delete the folders with the keyring or whatever it is called, but that was not successful. We only had success as a work around in installing Chrome and forcing Chrome to the default browser. Then the app interchange works and authorizes Flame to run properly.
We are still getting crashes occasionally, especially when rendering multiple segments in a timeline with just unexpected something or whatnot error.
