Dear Walters: Thanks your reply. Session bus crash but System bus doesn't crash. And my service register into session bus. My service API have return value to GUI. And it workable, before 8h.rs So, I think this is not reply issue. cat /proc/3246/wchan : futex_wait_queue_me /proc/3246/task/3257/wchan : hrtimer_nanosleep /proc/3246/task/3387/wchan : n_tty_read /proc/3246/task/3388/wchan : n_tty_write /proc/3246/task/3393/wchan : futex_wait_queue_me /proc/3246/task/3394/wchan : futex_wait_queue_me BTW, i save dbus-monitor message in normal case: method call sender=:1.25 -> dest=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello method call sender=:1.25 -> dest=org.Hellow.Network serial=2 path=/org/Hellow/Network; interface=org.Hellow.Network; member=GetNetworkONOFF method return sender=:1.5 -> dest=:1.3 reply_serial=1951 int32 0 method return sender=:1.5 -> dest=:1.25 reply_serial=2 int32 0 in fail case: method call sender=:1.409 -> dest=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello method call sender=:1.409 -> dest=org.Hellow.Network serial=2 path=/org/Hellow/Network; interface=org.Hellow.Network; member=GetNetworkONOFF but fail case dbus-signal is OK : Edward 在，Colin Walters <walters@verbum.org>寫道： > On Fri, Mar 25, 2011 at 2:44 AM, rain blue b123114@gmail.com> wrote: > > > Dear All, > > > I have some issues that when i use DBUS. > > > I write a system daemon by Dbus session. > > > It will provide 4 interface & 8x API for all GUI. > > > But when system run 8 h.r. or 10 h.r > > > My Dbus will disappear. > > > > The system or session bus crashes? > > > > > ex: dbus-send --session --print-reply --dest=org.xxxx.xxxx /org/xxxx/xxxx > > > org.xxxx.xxxx.xxx > > > It will hands on this command & no return. > > > > Hang? Can you get a stack trace via e.g. "gstack"? Or find out what > > system call it's stuck on ("strace" works for this, or since you're > > using Linux, just cat /proc/pid/wchan). > > > > What seems very likely to me is your service simply isn't sending a > > reply, and since you've specified --print-reply, the command will hang > > until the timeout. > >