How to identify which dbus rights an application needs? #6613
Unanswered
saltiniroberto
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is the suggested method to identify which dbus rights an application needs?
The best I have found is the following:
dbus-monitor
logging the output to a filedbug-monitor
d-feet
to find out all the dbus IDs (not sure this is the right terminology) associated with the applicationID
, grep through thedbus-monitor
output forsender=<ID>
Is there any quicker way?
Also, this method does not allow the discovery of the names that the application needs to own.
Beta Was this translation helpful? Give feedback.
All reactions