Search Issue Tracker

Won't Fix

Won't Fix in 6000.6.X

Votes

0

Found in

6000.3.11f1

6000.4.0f1

6000.5.0a9

6000.6.0a1

Issue ID

UUM-137248

Regression

Yes

[Linux] “FocusController has unprocessed focus events” warnings thrown in the Console after reimporting package via Package Manager

Steps to reproduce:
1. Create new Unity project
2. Open Package Manager window
3. Select “All Samples” tab
4. Install any package (for example On-Screen Controls or Input System Sample “Custom Binding Composite”)
5. Once installed, press “Reimport” button
6. Observe Console window

Actual results: “FocusController has unprocessed focus events. Clearing” warnings are thrown in the Console window after reimporting the package

Expected results: No warnings are thrown in the Console after reimporting the package

Reproducible with versions: 6000.3.0b6 (211490bb75a6), 6000.3.11f1, 6000.4.0f1, 6000.5.0a9, 6000.6.0a1
Not reproducible with versions:  6000.0.71f1, 6000.2.15f1, 6000.3.0b5 (d8efd0de5abc)

Tested on (OS): Ubuntu 24.04 (reproducible), macOS Silicon Tahoe 26.3.1 (not reproducible)

Notes:

  • in lower versions (6000.3), keep “In Project” tab and select Input System package > Samples > Import Sample > once imported - press “Reimport” button
  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.