Search Issue Tracker
Not Reproducible
Votes
0
Found in
2022.3.41f1
Issue ID
UUM-77433
Regression
No
[Linux] Player hangs when splash screen disappears
Reproduction steps:
1. Open the attached “BugRepro” project
2. Build the project
3. Install necessary packages by running these commands in Linux terminal:
* sudo apt install wmctrl scrot
* pip install numpy pillow
4. Open the “fuzztester.py” file
5. Edit the path to Build executable on line 7
6. Launch the script with command “python fuzztester.py”
7. Observe the Player and the Terminal output
Expected result: The player always initializes after the splash screen
Actual result: The player hangs after the splash screen and it’s indicated in terminal output
Reproducible with: 2022.3.41f1
Couldn’t test with: 2021.3.42f1, 6000.0.13f1 - Compilation errors
Reproducible on: Ubuntu 24.04
Not reproducible on: No other environment tested
Notes:
- Reproducible with 545 and 535 Nvidia drivers
- The reproduction chance is around 5%
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. We unfortunately were unable to reproduce this issue.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue. If this issue were to reproduce more effectively through different environments or repro steps, please feel free to re-open the issue with more context for future review.