diff options
| author | Roland Pallai <dap78@magex.hu> | 2023-01-27 14:29:56 +0100 |
|---|---|---|
| committer | Roland Pallai <dap78@magex.hu> | 2023-02-03 19:03:56 +0100 |
| commit | 03ac8c7397b9f070a8ef5f33b4675411293b0723 (patch) | |
| tree | 5064ab9f9ff97954d4b5b3013a3aa9ee3aa68213 /tests/auto/corelib/global/qnumeric | |
| parent | b464119dd497771d5c1fb0e4a35faae45641bf79 (diff) | |
QXcbConnection::getTimestamp: do not return stale timestamp
The problem is `PropertyNotify` event generated by
`xcb_delete_property()` at return could be reported as an actual
timestamp at next call due to a missing `state` filter.
Because `PropertyNotify` is generated even if an unchanged property
value is set we can get rid of this delete event easily.
This issue causes observable problems in kwin_x11 (KDE project)
too.
Fixes: QTBUG-56595
Pick-to: 5.15 6.2 6.4 6.5
Change-Id: Ice6cfa934e3769d86e9f7264e369dc5918c8542a
Reviewed-by: Giuseppe D'Angelo <giuseppe.dangelo@kdab.com>
Reviewed-by: Liang Qi <liang.qi@qt.io>
Reviewed-by: JiDe Zhang <zhangjide@uniontech.com>
Diffstat (limited to 'tests/auto/corelib/global/qnumeric')
0 files changed, 0 insertions, 0 deletions