Search Issue Tracker

Won't Fix

Won't Fix in 6000.6.X

Votes

0

Found in

6000.4.1f1

6000.5.0b1

6000.6.0a1

Issue ID

UUM-138177

Regression

No

[Linux] Multiple "Add a graph node" windows can be opened in Graph Toolkit when the graph is freshly imported

Graph Toolkit

-

Steps to reproduce:

  1. Create a new project using Universal 3D template
  2. Import the attached "MySimpleGraph.cs" into the Project
  3. Go to Assets > Create > Graph Toolkit Samples > Simple Graph
  4. Open the created graph
  5. Right-click on empty space and select "Add Node"
  6. Repeat 5th step
  7. Observe additional "Add a graph node" window opens
  8. Press "Space" on the keyboard
  9. Observe another additional  "Add a graph node" window opens

Actual results: There is an unlimited amount of "Add a graph node" windows that can be opened

Expected results: Only one "Add a graph node" window should be open at a time

Reproducible with versions: 6000.4.1f1, 6000.5.0b1, 6000.6.0a1

Can’t test with versions: 6000.3.12f1 (Graph Toolkit errors)

Tested on (OS): Ubuntu 24.04 (reproducible), macOS 26.3 (not reproducible)

Notes:

  • After some time in the Editor, the issue may stop reproducing
  • For best reproduction results, import the graph script and create the graph asset fresh in a new project/session
  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.