** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
OSK becomes unusable as taps are delayed by 1-
** Changed in: usensord (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
And the race detector correctly showed the data race in test.go, just
not in usensord
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
OSK becomes unusable as taps are delayed by 1-2 sec
Landing:https://requests.ci-train.ubuntu.com/#/ticket/1930
I verified vivid debian package on below images by creating 6 simultaneous
alarms that will ring one minute later.
current build number: 827
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed
last update: 2016-09
Additional info:
I built usensord on my laptop using
"go run -race usensord.go"
and that did not show any race condition after usensord stalled.
I also tried "go run -race test.go" using the code from
https://golang.org/doc/articles/race_detector.html#Introduction
so I think the race detector s
** Branch linked: lp:~zhangew401/usensord/bug-1620553
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
OSK becomes unusable as taps are delayed by 1-2 seconds and vibration
doesn't occ
another stacktrace, this time dispatchMessage does not appear in the
list of the calls, just fyi.
It could be that it had already completed or had not started yet, not
sure. Just thought I'd share this trace as well
** Attachment added: "go_stacktrace2"
https://bugs.launchpad.net/ubuntu/+sour
Here is the stracktrace of all the goroutines running at
http://bazaar.launchpad.net/~go-dbus/go-dbus/v1/view/136/dbus.go#L302
i.e. I printed the stacktrace of all the goroutines right before the
"reply := <- replyChan"
(disclaimer: I have 0 Go knowledge so take my words here with a pinch of
salt
Hi Zhang, more precisely, it seems at least one of the routines gets
stuck at waiting for a reply on replyChan
i.e. line 303 (see above)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
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 --s
Started from Pat's script and found an easier way to reproduce it (note
the final ampersand, which is the trick):
cat ./bombard.sh
#!/bin/bash
i=$1
while [ $i -gt 0 ]; do
dbus-send --session --print-reply --type=method_call
--dest='com.canonical.usensord' /com/canonical/usensord/haptic
com.
Thanks Pat telling me how to reproduce it.
I have reproduced it. I am trying to figuring out the reason and at the same
time I wrote to James for help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
** Changed in: usensord (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
OSK becomes unusable as taps are delayed by 1-2 seconds and vibr
** Tags added: lt-blocker
** Description changed:
Krillin, rc-proposed/bq_aquaris.en r422
- UPDATE: see comment #5, it turns out it's the haptics plugin doing SYNC
- dbus calls and blocking the UI thread when the dbus service does not
- reply or the replies come with a big delay
+ TEST CASE:
I had a quick look at this (I have ZERO Go knowledge though), the code seems to
hang at http://bazaar.launchpad.net/~go-dbus/go-dbus/v1/view/136/dbus.go#L303
i.e. waiting for a reply on replyChan
gdb showed that all threads had an infinite chain of futexsleep() except
one, that was waiting on epo
It seems to be deadlocked after calling messagebus.Call
@enwei can you take a look, set two alarms in the clock app for the same minute
to reproduce it
** Changed in: usensord (Ubuntu)
Assignee: (unassigned) => Zhang Enwei (zhangew401)
--
You received this bug notification because you are
One of the threads deadlocks inside the haptic handler (which is 100
lines of go, called every time the user e.g. presses the OSK), on a call
to dbus (messageBus.Call()). However, dbus seems to function fine, this
looks like an internal failure in usensord.
--
You received this bug notification b
Verified it does not trigger a deadlock on stable using the approach of
two simultaneous alarms
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
OSK becomes unusable as taps are delayed
fwiw I bombarded usensord with direct dbus requests simultaneously and
could not reproduce the issue
#!/bin/bash
i=$1
while [ $i -gt 0 ]; do
dbus-send --session --print-reply --type=method_call
--dest='com.canonical.usensord' /com/canonical/usensord/haptic
com.canonical.usensord.haptic.Vibra
My turbo was affected by this yesterday and reboots didn't seem to fix
it. I'm guessing usensord was wedged very quickly after startup, I was
receiving lots of SMS messages around the time it happened.
Debugging this morning showed the last process that called usensord was
telephony-service-indic
Reproduced a few times, need to root cause it
** Changed in: canonical-devices-system-image
Importance: Medium => Critical
** Changed in: canonical-devices-system-image
Milestone: None => 13
** Tags added: regression-proposed
--
You received this bug notification because you are a membe
I'd think it'd be useful to also add the actual problem, so we can look
it up later when needed. But I don't mind
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
OSK becomes unusable as
22 matches
Mail list logo