View Single Post
Posts: 32 | Thanked: 30 times | Joined on Jul 2012 @ Deb & Ian's dooryard
#4
I have no experience handling dbus, but this may help to debug it.

No leak in my case:
Code:
date >> dbus.log; ps avx | grep dbus-daemon >> dbus.log
Code:
Thu Aug  9 05:11:07 CEST 2012
 1198 messageb  3380 S <  /usr/bin/dbus-daemon --system --nofork 
 1559 user      3008 S <  /usr/bin/dbus-daemon --fork --print-pid 5 --print-add
 2205 user      2092 S    grep dbus-daemon 
Thu Aug  9 05:15:17 CEST 2012
 1198 messageb  3380 S <  /usr/bin/dbus-daemon --system --nofork 
 1559 user      3008 S <  /usr/bin/dbus-daemon --fork --print-pid 5 --print-add
 2209 user      2092 S    grep dbus-daemon 
Thu Aug  9 11:56:09 CEST 2012
 1198 messageb  3380 S <  /usr/bin/dbus-daemon --system --nofork 
 1559 user      3008 S <  /usr/bin/dbus-daemon --fork --print-pid 5 --print-add
 2213 user      2092 S    grep dbus-daemon 
Thu Aug  9 13:21:36 CEST 2012
 1198 messageb  3380 S <  /usr/bin/dbus-daemon --system --nofork 
 1559 user      3008 S <  /usr/bin/dbus-daemon --fork --print-pid 5 --print-add
 2217 user      2092 S    grep dbus-daemon 
Thu Aug  9 13:53:17 CEST 2012
 1198 messageb  3380 S <  /usr/bin/dbus-daemon --system --nofork 
 1559 user      3008 S <  /usr/bin/dbus-daemon --fork --print-pid 5 --print-add
 2220 user      2092 S    grep dbus-daemon
 

The Following User Says Thank You to conred For This Useful Post: