RSIBreak / KIdleTime on Wayland

Dominik Waurenschk dominik.waurenschk at protonmail.com
Mon Nov 16 15:35:58 GMT 2020


> > 2.  It works with XWayland, but only detects user activity if the user makes an input to an XWayland window.
> Yeah, that's expected. We only send things to X when an X app has focus.
> Changing this behaviour is not an option. I don't think this is a viable setup option to support.
> > RSIBreak is started as an XWayland application by default.
> That shouldn't be the case. Are you on OpenSuse by any chance?

Alright, just checking if that is intended behaviour.
Yes, I am indeed on OpenSuse, so I guess that's some kind of config error on my end. 

No need to worry about this case then.

> > 3.  It works okay if RSIBreak is started as a native Wayland application (QT_QPA_PLATFORM=wayland).
> >     All input is detected, on native and XWayland windows.
> >     But: It takes about 5-10 seconds of me not doing any inputs for the idle timeout to be called, instead of the 1 second timeout I requested.
> >     (the resume event is emitted immediately though, it is just the idle timout that is slow)
> Indeed:
>     // less than 5 sec is not idle by definition
>     timer->setInterval(qMax(timeout, 5000u));
>
> In kwayland-server/src/server/idle_interface.cpp
> I have no objections to changing this.
> 

> David

Thanks for the information, and the merge request :)

Dominik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 509 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20201116/45121207/attachment.sig>


More information about the kde-devel mailing list