Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.0.68f1

6000.3.10f1

6000.4.0b9

6000.5.0a7

Issue ID

UUM-135101

Regression

No

[Linux] TMP Font Asset pop-up Window opens on the secondary monitor when the Editor is placed in primary monitor

Steps to reproduce:

  1. Make sure you have two monitors available for testing
  2. Set up secondary monitor to be position to the right of the primary monitor
  3. Create a new project using Universal 3D template
  4. Right-click in Hierarchy and select 'UI (Canvas) > Text (TextMeshPro)'
  5. Import TMP Essentials
  6. Select the created "Text (TMP)" GO in the Hierarchy
  7. In the Inspector, in the "Font Asset" property click on the GameObject picker button
  8. Observe the opened "Select TMP_Font Asset" window 

Actual results: The Window opens on the secondary monitor

Expected results: The Window opens on the same monitor as the Editor

Reproducible with versions: 6000.0.68f1, 6000.3.10f1, 6000.4.0b9, 6000.5.0a7

Tested on (OS): Ubuntu 24.04

Notes:

  • Does not reproduce on Windows and macOS
  • The Window opens up in the same place even if its position is changed and then the Window is closed and reopened
  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.5.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.