Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.3.0b1
2018.4
2019.3.6f1
2020.2
Issue ID
1231531
Regression
Yes
[Linux] Shader selection dropdown's context menu's "Select Shader" option doen't work
How to reproduce:
1. Open the attached project (1231531.zip)
2. Select the "Test" material in the Project window
3. In the Inspector right-click on the shader selection dropdown
4. In the context menu click on the "Select shader" option
5. Observe the Project window
Expected result: A shader file is selected in the Project window
Actual result: Nothing happens
Reproducible with: 2018.3.0b1, 2018.4.20f1, 2019.3.8f1, 2020.1.0b4, 2020.2.0a5
Not reproducible with: 2017.4.39f1, 2018.3.0a11
Notes:
1. Does not reproduce on Windows 7
2. Tested on Windows 7 and Linux (Ubuntu 18.04, KDE Neon 5.18)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2020.2):
Select Shader option in inspector shader context menu now works in the Linux editor
Fixed in 2020.2.0a15