Search Issue Tracker

Won't Fix

Won't Fix in 6000.6.X

Votes

0

Found in

6000.0.71f1

6000.3.12f1

6000.4.1f1

6000.5.0b1

6000.6.0a1

Issue ID

UUM-138165

Regression

Yes

[LinuxEditor] Auto refresh is not triggered when switching back to the Editor using keyboard shortcuts across virtual desktops

Reproduction steps:
1. Open the attached “IN-137917” project
2. Open the “Scenes/SampleScene” Scene
3. Open the “Repro.cs” Script in an IDE
4. Make sure the opened IDE is on different desktop than the Editor (on Ubuntu: Ctrl + Alt + Shift and Arrow keys)
5. Edit the script by changing the “Debug.Log” output
6. Save the script
7. Go back to the desktop which has the Editor opened (on Ubuntu: Ctrl + Alt and Arrow keys)
8. Observe the Editor
OPTIONAL:
9. Enter the Play Mode
10. Observe the Console window

Actual result: Auto refresh is not triggered and the “Debug.Log” output does not change
Expected result: Auto refresh is triggered and the “Debug.Log” output is changed

Reproducible with: 6000.0.29f1, 6000.0.71f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0b1, 6000.6.0a1
Not reproducible with: 6000.0.28f1

Reproducible on: Ubuntu 24.04.4, Ubuntu 25.04
Not reproducible on: Windows 11, macOS 26.3.1

Notes:
- Issue only reproduces using X11, it does not when using Wayland windowing system
- Issue does not reproduce if you manually select the Editor from the Taskbar. You need to use keyboard shortcuts
- After step 7, if you focus another application, and then focus back to the Editor, auto refresh is triggered
- Tested only with VS Code IDE

  1. 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. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    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.

  2. Resolution Note (6000.6.X):

    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. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.