Markus Elfring changed bug 1215872
What Removed Added
Summary Cannot communicate with BOINC client (possibly related to XSS idle detection) Checking run time characteristics of the function call “XOpenDisplay(":0")” (by service implementations)

Comment # 10 on bug 1215872 from Markus Elfring
(In reply to Aaron Puchert from comment #9)
> …, or have to discuss with the owner of that repository.

I obviously tried to clarify involved technical details for a while
accordingly.


> So the actual issue is not necessarily related to idle detection. That this
> doesn't work, as indicated by the log messages, might be unrelated to the
> failure to communicate.

Please take another look at published information.


> Did you actually observe such a call being stuck?

Yes. - I got such an impression from added debug output.


> > XSS idle detection can eventually be relevant for development software variations.
> 
> But not for the package that we're going to ship. If we're going to ship
> idle detection again, it will have a service running under the logged-in
> user that communicates the idle state to the BOINC client, and that ideally
> works with Wayland as well.

I am curious which software design options will be taken better into account
here.
Would you like to influence any progress on the topic “redesign Linux idle
detection”?
https://github.com/BOINC/boinc/issues/5226


You are receiving this mail because: