Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.3.0a4
6000.4.0a1
6000.5.0a1
Issue ID
UUM-113474
Regression
No
[Linux] Dragging Editor items/objects is very laggy on Wayland
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Create a UI Document asset (Assets > Create > UI Toolkit > UI Document)
- Double click the new UI Document asset to open it in the UI Builder window
- Maximise the UI Builder window
- Click and drag any component to the Viewport
- Observe the UI Builder window
Actual results: Clicking and dragging the component is extremely slow/choppy and lagging
Expected results: Clicking and dragging the component is smooth and quick
Reproducible with versions: 6000.3.0a1, 6000.3.0a4
Not reproducible with versions: 6000.0.54f1, 6000.1.14f1, 6000.2.0b13
Tested on (OS): Ubuntu 24.04
Notes:
- Does not reproduce on macOS Silicon Sequoia 15.5
- Does not reproduce if the UI Builder is not maximised
- Also reproduces with other windows, like the Build Profiles window
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
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.
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.