As the policy defined in the polkit actions for KernelShark Record define both the environment ($DISPLAY and $XAUTHORITY) as well as the path to the executible, no need to add hacks to the kshark-su-record that is used. Just revert the code that did so. Steven Rostedt (VMware) (2): kernel-shark: Revert adding environment variables to kshark-su-record kernel-shark: Revert adding relative path to policy installation ---- kernel-shark/bin/kshark-su-record | 3 +-- kernel-shark/src/CMakeLists.txt | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-)