|
Sorry, it posted prematurely, now editing.... OS & Version:
BugRunning latest gupax as non-root (normal user), launches GUI, started node synching (at 30%) now try xmrig , enter key hash, and click START all with default values, causes GUI to feeze with logs of errors.. StepsSteps to reproduce the behavior: errors start with: This appears like it tries to authenticate to root?? couldn't find any docs that say gupax needs root ? how to automate that? it depends on additional agent setup? later more errors flood: eventually the GUI locks up and stalls machine, only way out is kill -9.. Crash reportno crash found in ~/.local/share/gupax |
Replies: 4 comments
|
Here are the launch flags from log: it might start working once node is fully synced, not sure if related. |
|
OH WOW, checking on very old machine running v1.3 when running xmrig it prompts:
|
|
The way gupax handles the authentication for launching xmrig with admin privileges has changed between v1.3 and v2.01. Now it uses pkexec to handle authentication. You don't need to run gupax as root. pkexec will open a window (by calling your authentification agent, which is policykit) asking for a password by default on a fresh Ubuntu 24.04 If that's not the case, it is falling back on terminal input like we can see in your logs. If your pkexec on your system is falling back on terminal input (You can test by simply testing the command |
|
Wow, thanks for insight! These servers run without any display, connection is via VNC, x11 works fine, however, pkexec does not open a terminal window, it prompts text, same lines that appear in the log file!!
That did not work either.. full output for the record:
This incident has been reported. reading further suggests that the auth agent is not part of icewm, so need to add it to xstartup in .vnc, and now it's running:
Thanks, maybe some validation could run before hand and alert user in a more "streamlined" fashion :) |
The way gupax handles the authentication for launching xmrig with admin privileges has changed between v1.3 and v2.01.
Now it uses pkexec to handle authentication. You don't need to run gupax as root. pkexec will open a window (by calling your authentification agent, which is policykit) asking for a password by default on a fresh Ubuntu 24.04
If that's not the case, it is falling back on terminal input like we can see in your logs.
If your pkexec on your system is falling back on terminal input (You can test by simply testing the command
pkexec),, it means your system has been modified. Please first resolve this issue first. On Ubuntu 24.04, you should have policykit installed and running.…