@WetGeek @riffer @synth-ruiner Like you, I think that the authentication is required to run a bash script. My guess is that we all suspect that the script is related to a specific app/program that was user-installed after Solus was installed, and that the app/program is set up to run at on startup and requires the script to obtain the necessary permissions to run.
So far, so good. That brings us back to the original question:
mbevks Is there a good way to figure out which program is triggering that?
We've all asked, in different ways, what apps/programs where installed after Solus was installed, focusing on non-repos apps and apps installed immediately before the authentication notification. No response so far, but I assume that we will get an answer in time, and that answer will point in a direction.
I'm wondering if coming at the problem from another direction might be helpful. The script, if typical, is likely to be stored in /etc/init.d. Once displayed, the script, should identify the app/program that is attempting to run at start up. Is there a way to identify the script in /etc/init.d, or at least make a good guess as to which script it might be?