I saw this issue in firefox bugzilla:
Is this a bug on kwin side?
I saw this issue in firefox bugzilla:
Is this a bug on kwin side?
@Zamundaaa ping
KWin just uses the system time for frame callbacks, which may go backwards in some cases. As the protocol doesn’t define the base for the timestamp, clients just have to deal with this.