Ubuntu
platform-api package

  1. Bug #1620553
  2. Comment #20

Comment 20 for bug 1620553

Revision history for this message
Zhang Enwei (zhangew401) wrote :

Thanks Andrea. I am using a similar way with that of yours, only four commands executed simultaneously.

#!/bin/bash
dbus-send --session --print-reply --type=method_call --dest='com.canonical.usensord' /com/canonical/usensord/haptic com.canonical.usensord.haptic.Vibrate uint32:100 &
dbus-send --session --print-reply --type=method_call --dest='com.canonical.usensord' /com/canonical/usensord/haptic com.canonical.usensord.haptic.Vibrate uint32:100 &
dbus-send --session --print-reply --type=method_call --dest='com.canonical.usensord' /com/canonical/usensord/haptic com.canonical.usensord.haptic.Vibrate uint32:100 &
dbus-send --session --print-reply --type=method_call --dest='com.canonical.usensord' /com/canonical/usensord/haptic com.canonical.usensord.haptic.Vibrate uint32:100 &

I think this could simulate the operation in clock/alarm
I found the rule is that two or more senders(thread or process) calls the dbus function at the same time.
It freezes at below code,
http://bazaar.launchpad.net/~phablet-team/usensord/trunk/view/head:/haptic/haptic.go#L146