I get a blank sign-in screen.
1 Like
Both RV and ShotGrid Create Autodesk sign-ins work perfectly. If ShotGrid Desktop did what they do I would not have any issues.
I realize how frustrating this can be, and this is unfortunate.
But I feel the need to mention that from my limited-and-not-necessarily-statistically-significant-sampling, I have not heard reports of others in this situation (recent SG Desktop + recent Mac + recent OS).
One workaround we are trying to offer : allow the SG Desktop to use the legacy login and passphrase to authenticate with an Autodesk Identity-using site. Not the perfect solution, but a solution.
-Patrick
I could not log in to shot grid desktop after migration was complete too. Here is what worked for me on Mac OS 11.5.1 .
Drag current install of Shotgun Desktop to the trash and empty trash.
Download the latest Shotgrid Desktop installer.
Install ShotGrid Desktop.
Upon loading Shotgrid desktop it prompted me for my Autodesk Identity and continued loading up.
Hi @achrystie
Depending on the version of your SG Desktop, an update would be necessary.
I am happy that you got things working after the update.
Do you, by any chance recall which version you had installed prior to your update ? Or if you could expand on your I could not log in to shot grid desktop experience ? (error message, behaviour)
Thanks,
-Patrick
Same problem here - I’m dead in the water.
Tried the steps mentioned by @achrystie above. Still nothing.
This problem resurfaced in my Windows 10 VM which I need in order to use Autodesk Motionbuilder since that is not available for MacOS. I once again was presented with a blank white login screen after entering my site in ShotGrid Desktop. I reinstalled ShotGrid Desktop but that did not help. I logged into RV without issue but that did not give me a session key. I then started clicking around in the blank white login screen for ShotGrid Desktop noticed the curser change to a text input so I typed in my Autodesk ID email and pressed enter. Then I located again the text input curser and typed in my Autodesk ID password and pressed enter. It worked! I am now logged in and am able to work. Hope this helps others. REALLY Hope Autodesk fixes this problem we are having.
PS. This same method allows me to login to ShotGrid Create in my Windows 10 VM which was also giving me a blank login screen.
Oh, so the blank page HAD some elements in it, but were not being rendered properly…
For some reason, I assumed that the process was just blocked on the rendering side. Meaning that no interaction with the app was possible at that point.
That seems like a Qt bug then.
Is the situation the same on your Windows and Mac machines ?
-Patrick
Hi @mgoetsch
Not sure if you had seen my post of a workaround script to authenticate: Blank white screen when trying to "Sign in using the Web." in Shotgun desktop - #3 by patrick-hubert-adsk
-Patrick
1 Like
Thank you very much for the script. I will use it next time ShotGrid Desktop breaks due to expired session key.
My session key expired, I once more get the blank login screen. I ran your script but it did not appear to do anything and had no improvement on the issue. I still have a blank white login screen. And now the method I had with the Autodesk login on the blank screen no longer works. So I am unable to work at all.
We had to recreate new sg-session tokens for every tool relying on. I assume SG & Autodesk made some changes somewhere. But who cares about the paying customers. Ahahahahahahahahahahahahahahaha! SG is permanently braking somewhat somewhere. But no one cares. There are bugs in production API, which no-one cares about! For example this one:
https://community.shotgridsoftware.com/t/eventlog-error-no-display-name/13191/7
Nobody cares. We are just forced to pay the doubled price…
Shotgun / Grid - what-so-ever and it’s “Support” is the biggest frustration in my entire life.
Once in a while, a new release of ShotGrid forces us to invalidate existing user sessions. This is required due to changes to DB schemas.
We try to avoid doing this, but it is not always possible. Last time this happened was a bit over a year ago if I recall correctly.
-Patrick
Yes, but there is a Qt bug in the ShotGrid Desktop for MacOS app so I cannot login again.
GVA encoder info: AMD performance mode : 2
GVA encoder info: deleteSCDMetalContext : texture cache hits: 0, misses: 0
[26485:44803:0818/133227.524665:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133227.524721:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133227.525702:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133227.525721:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133227.526194:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133227.526216:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133227.526562:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133227.526578:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133227.527087:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133227.527102:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133227.527417:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133227.527430:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133227.527795:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133227.527807:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133227.528187:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133227.528203:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133227.530469:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133227.530485:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133227.530856:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133227.530870:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133228.330957:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133228.330982:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133228.347963:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133228.347991:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133228.351390:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133228.351417:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133228.381566:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133228.381592:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133228.383906:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133228.383917:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133228.384498:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133228.384507:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133228.385001:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133228.385009:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133228.390767:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133228.390783:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133228.410470:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133228.410491:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[26485:44803:0818/133228.411866:ERROR:gl_context_cgl.cc(136)] Error creating context.
[26485:44803:0818/133228.411884:ERROR:gles2_command_buffer_stub.cc(262)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
Ok, i’m sorry for my raging here.
Am I missing some newsletter or live-ticker to be aware of things SG needs to reset, invalidate or rollback? This forum tends to be the best source for hearing about things happening.
I’m not a big fan of social media, so I probably miss some twitter announcements?
With best regards,
Dietmar
Speaking only for myself (I am not part of the DevOps team), I usually look here: https://status.shotgridsoftware.com/
I am subscribing to the updates via email.
But the session invalidation was not mentioned for this morning’s maintenance. I feel that this is an oversight.
-Patrick
I know the site, but:
- It’s not always up-to-date. Do I need to provide proofs for this thesis? If so, no problem, I’ll find my tickets with timestamps vs information posted on the site. It would just waste my time.
- I don’t see any announcements about session resets on this page either. Only a “Minimal downtime” is expected. I do not see anything about broken sessions etc.
- I believe that you are referring to some other page. The one I cited does not mention tickets, only system statuses and planned work. When we plan maintenances, this is where we notify clients. The release notes are elsewhere, and done by different people.
- I did mention this to our DevOps team, they have modified their process so that it will be mentioned next time.
-Patrick
No no, I mean, there was a down time back in may/july, where I had to create a ticket, because it was not obvious, that not only our site was down. It was the time I discovered the status page. Back then it was telling everything would be ok. But it was not. But forget it. Talking about past makes no sense. Let’s get better now and in the future 
Nice! Thank you very much!
1 Like
To be fair, you are a client… Calling us out our past mistakes is totally legitimate and desirable (if only to push us to be better in the future)
So… thank you 
-Patrick
1 Like