What | Removed | Added |
---|---|---|
Summary | Checking run time characteristics of the function call “XOpenDisplay(":0")” (by service implementations) | Cannot communicate with BOINC client (possibly related to XSS idle detection) |
Sorry for the late reply. (In reply to Markus Elfring from comment #8) > I would occasionally like to use an other development repository directly. Understood, but then you're on your own, or have to discuss with the owner of that repository. > Repetition: > I saw the German message “Kommuniziere mit dem BOINC Client. Bitte warten > ...” within a modal dialogue which was similar to the English message that > was shown also in a screenshot from Austin Conlon on 2020-10-05. 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. > > But I'm not sure if this will help you. > > How do you think about to inspect the control flow between the called > functions “XOpenDisplay” and “CheckAuthorization” any further? > https://gitlab.freedesktop.org/xorg/lib/libx11/-/blob/ > c745719e23af44a4b40ab4508447637b35d91a1e/src/OpenDis.c#L60 > https://gitlab.freedesktop.org/xorg/xserver/-/blob/ > 722e464bffdcfc7c4beb00e0995c105bc431d0d4/os/auth.c#L164 > > Would you find a loop which would hinder the return of a null pointer? You could certainly try in a debugger, or index the code base and go through the call graph manually. But for now I don't think we have enough information to be sure that is your problem. > > XSS idle detection should not block, > > This is a reasonable expectation. > I came along other observations. Did you actually observe such a call being stuck? I didn't see any indication of that. And if it gets stuck, where? If there is no progress with ~100% CPU, a profile might be interesting, with ~0% CPU something offcputime from bcc-tools should help. Just guessing based on the log won't get us there. > [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.