Search Issue Tracker
Fixed in 2020.3.46f1
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0b9, 2023.2.X
Votes
0
Found in
2020.3.44f1
2021.3.17f1
2022.2.4f1
2023.1.0b1
Issue ID
UUM-24705
Regression
No
[Linux] Editor ignores SIGTERM signal when using command 'kill <PID>'
Reproduction steps:
1. Create a new 3D project
2. Open the Terminal
3. Enter this command: ps aux | grep 2021.3.14f1 | grep -v grep | awk '{print $2}'
4. Enter this command: kill <first PID from the results of the previous command>
Expected result: Unity Editor is killed
Actual result: Unity Editor is still open
Reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.2.4f1, 2023.1.0b1
Reproducible on: Ubuntu 20.04
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [LinuxEditor] Crash on "XAddExtension" when opening the Unity Editor on Linux with -batchmode and -nographics on a project with a custom default cursor
- Folder attachment size is displayed as 0 bytes when a folder is added to the Hub bug reporter's attachments
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
Add comment