How to get dbus-monitor to listen to more dbus messages?
How to get dbus-monitor to listen to more dbus messages?
Re: How to get dbus-monitor to listen to more dbus messages?
Neal H. Walfield
At Sun, 03 Jul 2011 22:00:13 +0800,
Jonathan Wilson wrote:
>
> I am trying to get dbus-monitor to listen to some dbus messages,
> (specifically the tklock_open and tklock_close messages sent from mce to
> systemui for the device lock state) and no combination of arguments to
> dbus-monitor seems to get dbus-monitor to output them.
I put the following in /etc/dbus-1/system-local.conf (this file is
automatically loaded via system.conf if it exists). I've been using
it for about a year.
<busconfig>
<policy context="default">
<!-- Allow everything to be sent -->
<allow send_destination="*" eavesdrop="true"/>
<!-- Allow everything to be received -->
<allow eavesdrop="true"/>
<!-- Allow anyone to own anything -->
<allow own="*"/>
<!-- XXX: Allow all users to connect -->
<allow user="*"/>
</policy>
</busconfig>
Jonathan Wilson wrote:
>
> I am trying to get dbus-monitor to listen to some dbus messages,
> (specifically the tklock_open and tklock_close messages sent from mce to
> systemui for the device lock state) and no combination of arguments to
> dbus-monitor seems to get dbus-monitor to output them.
I put the following in /etc/dbus-1/system-local.conf (this file is
automatically loaded via system.conf if it exists). I've been using
it for about a year.
<busconfig>
<policy context="default">
<!-- Allow everything to be sent -->
<allow send_destination="*" eavesdrop="true"/>
<!-- Allow everything to be received -->
<allow eavesdrop="true"/>
<!-- Allow anyone to own anything -->
<allow own="*"/>
<!-- XXX: Allow all users to connect -->
<allow user="*"/>
</policy>
</busconfig>
(specifically the tklock_open and tklock_close messages sent from mce to
systemui for the device lock state) and no combination of arguments to
dbus-monitor seems to get dbus-monitor to output them.
After trying this
http://mvidner.blogspot.com/2008/05/d-bus-spying.html
to try and get dbus-monitor to show me what I wanted to see and nearly
bricking my phone in the process, I am out of ideas.
Any ideas on how to get logs of these messages would be appreciated (and if
editing the dbus config file is the right solution, I need exact steps to
do it that are known to be safe and easily reversible)