Some applications are not able to inhibit the idle behavior because
each of them creates an inhibitor object before the corresponding
ShellClient object becomes ready for painting.
BUG: 401499
FIXED-IN: 5.15.0
Details
Details
- Reviewers
graesslin - Group Reviewers
KWin - Commits
- R108:437d35eee242: [wayland] Check presence of the inhibitor object when a client is registered in…
idle-inhibit client (from wlroots/examples) works.
Diff Detail
Diff Detail
- Repository
- R108 KWin
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
| idle_inhibition.cpp | ||
|---|---|---|
| 47 | You're right on where the problem is, good work analysing. But this TODO is still valid. From the spec we should only apply the inhibition when the surface is visible. This is an OK short term fix (if you leave this one line), but when we do it properly we'll have to move it all around. | |
| idle_inhibition.cpp | ||
|---|---|---|
| 47 | I probably misunderstood this TODO comment. | |