Search Issue Tracker
Fixed
Fixed in 2022.3.X, 2023.1.X, 2023.2.X
Votes
0
Found in
2021.3.26f1
2022.3.1f1
2023.1.0b20
2023.2.0a18
Issue ID
UUM-37536
Regression
Yes
[Linux] Default File Manager is not opened when opening containing folder with Nautilus removed
Reproduction steps:
1. Install Nemo file manager with these steps:
- sudo apt update
- sudo apt install nemo
- xdg-mime default nemo.desktop inode/directory application/x-gnome-saved-search
- gsettings set org.gnome.shell.extensions.ding use-nemo true
- gsettings set org.gnome.shell.extensions.ding show-home true
- reboot
- test if xdg-open is working properly with Nemo file manager, by using ‘xdg-open $HOME’
2. Remove the Nautilus file manager with these steps:
- sudo apt-get update
- sudo apt-get remove nautilus
- sudo apt autoremove
3. Create a new 3D Unity Project
4. In the Project view, right-click anywhere
5. Click “Open Containing Folder”
Expected result: Nemo file manager opens the containing folder
Actual result: Nothing happens
Reproducible with: 2021.3.26f1, 2022.3.1f1, 2023.1.0b20, 2023.2.0a15, 2023.2.0a18
Not reproducible with: 2023.2.0a1, 2023.2.0a14
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment