Search Issue Tracker
Fixed
Fixed in 3.4.X, 3.5-beta.1
Votes
4
Found in [Package]
3.4
Issue ID
HUBX-754
Regression
No
Unity Hub is black when being used by multiple computer users
Reproduction steps:
1. Open the Unity Hub
2. Change computer's user
3. Open the Unity Hub
Expected result: Unity Hub runs as usual
Actual result: Unity Hub is black
Reproducible with: 2.4.5, 3.0.0, 3.0.1, 3.1.2
Note: reproducible on macOS and Windows 10
More issues being reported here with 3.3-beta.1 when using multiple computer users: [https://unity.slack.com/archives/C7MKBJ34G/p1662560532839199]
From a second user account on Windows:
- Installing an editor fails from the second user account, failed message doesn't elaborate why. (Logs in thread for this.)
- The license shown and used on the second account is my Unity Pro license from my main user account - the account signed in to the Hub is new and should have no purchased licenses. I can remove the splash screen as this user.
- Switching user on Windows and opening the Hub on the second user account results in an endless loading screen for that Hub.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment