diff options
| author | Ivan Molodetskikh <yalterz@gmail.com> | 2025-09-06 11:10:23 +0300 |
|---|---|---|
| committer | Ivan Molodetskikh <yalterz@gmail.com> | 2025-09-17 22:04:23 +0300 |
| commit | 82276771a5e5590d5aac5847be84d99076815501 (patch) | |
| tree | 5bd017630c261a449cb07bcb8e63ff05256da829 /docs | |
| parent | cd7108ef5dc30afd7d5aefb51d5e73fbd004afc1 (diff) | |
| download | niri-82276771a5e5590d5aac5847be84d99076815501.tar.gz niri-82276771a5e5590d5aac5847be84d99076815501.tar.bz2 niri-82276771a5e5590d5aac5847be84d99076815501.zip | |
Downgrade lack of our initial configure from error! to debug!
This can happen if a surface unmaps by committing a null buffer and then
immediately does the initial commit without a sync roundtrip, while there are
pending configures from the compositor in-flight. In this case, the surface
cannot tell that the pending configures were meant for "before unmapping" and
considers them to be the new initial configure.
From our point of view, we don't get to do a proper initial configuration
sequence in this case, and receive a mapping commit without our initial
configure state. We cannot really do much about it, but it is not an error when
this specific situation happens.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions