[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Looking for maintainer of Wayland KDE Idle protocol
From:       David Edmundson <david () davidedmundson ! co ! uk>
Date:       2020-07-07 11:47:25
Message-ID: CAGeFrHAgfsFdsgTspoeqvAJjet+u6q3=vHen_eyg4tiLDR=w4g () mail ! gmail ! com
[Download RAW message or body]

On Tue, Jul 7, 2020 at 12:18 PM David Edmundson <david@davidedmundson.co.uk>
wrote:

> >It seems that the most popular Wayland protocol for detecting when a
> user is "idle" is this protocol that is a part of KDE.
>
> Yes-ish.
>
> Note it is now being upstreamed:
>
> https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/29
>
> So now is a good time for any changes.
>
> Any discussion should happen there. I have a feeling you're effectively
> responding to the question Simon had about interaction with idle-inhibit
> and whether we really want to inhibit idle events or actions on idle events.
>
> >One limitation that I have with this protocol is that if the user stops
> typing/mousing, but is watching a video or something, the video player
> can send fake activity with the `simulate_user_activity` request.
>
> That's not really right.
> One should use an idle inhibition protocol. Annoyingly this is fragmented,
> there's one in x and wayland but also some DBus ones.
> `simulate_user_activity`will get deprecated at some point, it just exists
> from a time to fake things in X and us mapping it.
>
> >My application is trying to track actual keyboard/mouse activity, and
> this fake activity makes things difficult (even though it is an
> effective way to prevent a lockscreen from triggering).
>
> I suspect it's idle inhibitions that's breaking it, not this simulate user
> activity. Let's follow this up on the relevant wayland-protocols thread
> above
>
> David
>
> Relevant comment:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/29#note_560996

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Tue, Jul 7, 2020 at 12:18 PM David Edmundson &lt;<a \
href="mailto:david@davidedmundson.co.uk">david@davidedmundson.co.uk</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">&gt;It \
seems that the most popular Wayland protocol for detecting when a<br><div> user is \
&quot;idle&quot; is this protocol that is a part of \
KDE.</div><div><br></div><div>Yes-ish.</div><div><br></div><div>Note it is now being \
upstreamed:</div><div><a \
href="https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/29" \
target="_blank">https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/29</a></div><div><br></div><div>So \
now is a good time for any changes.<br></div><div><br></div><div>Any discussion \
should happen there. I have a feeling you&#39;re effectively responding to the \
question Simon had about interaction with idle-inhibit and whether we really want to \
inhibit idle events or actions on idle events.<br></div><div><br></div><div>&gt;One \
limitation that I have with this protocol is that if the user stops<br> \
typing/mousing, but is watching a video or something, the video player<br> can send \
fake activity with the `simulate_user_activity` \
request.</div><div><br></div><div>That&#39;s not really right.</div><div>One should \
use an idle inhibition protocol. Annoyingly this is fragmented, there&#39;s one in x \
and wayland but also some DBus ones.</div><div>`simulate_user_activity`will get \
deprecated at some point, it just exists from a time to fake things in X and us \
mapping it.</div><div><br></div><div></div><div> &gt;My application is trying to \
track actual keyboard/mouse activity, and<br> this fake activity makes things \
difficult (even though it is an<br> effective way to prevent a lockscreen from \
triggering).</div><div><br></div><div>I suspect it&#39;s idle inhibitions that&#39;s \
breaking it, not this simulate user activity. Let&#39;s follow this up on the \
relevant wayland-protocols thread \
above<br></div><div><br></div><div>David<br></div><div><div><div><br></div></div></div></div></blockquote><div>Relevant \
comment: <a href="https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_req \
uests/29#note_560996">https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/29#note_560996</a></div><div> \
</div><div><br></div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]