Value box lag with wayland #99465

New Issue

Roni · 2022-07-05T17:48:08+02:00

Roni commented

2022-07-05 17:48:08 +02:00

Operating system: Fedora 36
Graphics card: NVIDIA GeForce GTX 1660

Blender Version: 3.2.0

This issue is only happening when using the wayland display protocol instead of xorg.

When modifying values in value boxes with the keyboard, there is this weird lag thing happening. For example, if I'm inserting "123", when I press 1, nothing happens yet, when pressing 2 the 1 comes visible, when pressing 3 its 12, so it's always one digit behind. If I exit the input mode (deselecting the box with enter or mouse click), the value shows up correct.
When modifying the values with mouse drag, or arrows, everything works normally.

Operating system: Fedora 36 Graphics card: NVIDIA GeForce GTX 1660 Blender Version: 3.2.0 This issue is only happening when using the wayland display protocol instead of xorg. When modifying values in value boxes with the keyboard, there is this weird lag thing happening. For example, if I'm inserting "123", when I press 1, nothing happens yet, when pressing 2 the 1 comes visible, when pressing 3 its 12, so it's always one digit behind. If I exit the input mode (deselecting the box with enter or mouse click), the value shows up correct. When modifying the values with mouse drag, or arrows, everything works normally.

Roni commented

2022-07-05 17:48:08 +02:00

Added subscriber: @Roni-4

Roni commented

2022-07-05 19:14:58 +02:00

I got informed that I should try 3.3.0 alpha if the problem still exists in there, and it does.

Pratik Borhade commented

2022-07-06 05:58:52 +02:00

Added subscribers: @ideasman42, @PratikPB2123

Pratik Borhade commented

2022-07-06 05:58:52 +02:00

@ideasman42 , can you look at this report?

Campbell Barton commented

2022-07-06 12:23:46 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Campbell Barton commented

2022-07-06 12:23:46 +02:00

@Roni-4 I can't redo this bug, could you try some extra checks?

Does this happen for all text input (Python / Blender's Text Editor / 3D Text).
Could you try a different compositor? (Weston/Sway/KDE Plasma... for e.g.)
Could you try with software OpenGL:

`LIBGL_ALWAYS_SOFTWARE=1 GALLIUM_DRIVER=llvmpipe blender`

@Roni-4 I can't redo this bug, could you try some extra checks? - Does this happen for all text input (Python / Blender's Text Editor / 3D Text). - Could you try a different compositor? (Weston/Sway/KDE Plasma... for e.g.) - Could you try with software OpenGL: ``` `LIBGL_ALWAYS_SOFTWARE=1 GALLIUM_DRIVER=llvmpipe blender`

Pratik Borhade commented

2022-07-15 09:19:21 +02:00

Changed status from 'Needs User Info' to: 'Archived'

Pratik Borhade closed this issue

2022-07-15 09:19:21 +02:00

Pratik Borhade commented

2022-07-15 09:19:21 +02:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists please open a new report with the required information (or reopen this report).

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information (or reopen this report).

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Value box lag with wayland #99465