https://bugzilla.suse.com/show_bug.cgi?id=1215872 https://bugzilla.suse.com/show_bug.cgi?id=1215872#c8 --- Comment #8 from Markus Elfring <Markus.Elfring@web.de> --- (In reply to Aaron Puchert from comment #7)
What kind of constraints?
It seems that you would like to concentrate on provided software packages which were generated from commands of a known RPM file format. https://build.opensuse.org/package/view_file/openSUSE:Factory/boinc-client/b...
And why should I think about them?
I would occasionally like to use an other development repository directly.
You're describing your thought process, but we need a description of the program behavior on the screen.
Reminder: I added my application concern within the context of an existing issue.
What do you see?
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. See also: https://github.com/BOINC/boinc/blob/44295c1a50d84e44992d97b9e949700d3b9af2d1...
Do you mean "Authorization …"?
Obviously, yes.
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/c745719e23af44a4b40ab4... https://gitlab.freedesktop.org/xorg/xserver/-/blob/722e464bffdcfc7c4beb00e09... Would you find a loop which would hinder the return of a null pointer?
XSS idle detection should not block,
This is a reasonable expectation. I came along other observations.
and it's not active in the package.
It can eventually be relevant for development software variations. The understanding is still incomplete for the presented function call trace. -- You are receiving this mail because: You are on the CC list for the bug.