touch-packages team mailing list archive

[Bill Filler <1471338@xxxxxxxxxxxxxxxxxx>]

When I attach to telepathy-approver with gdb I see this in the trace:

Thread 6 (Thread 0xb38683a0 (LWP 4339)):
#0  0xb64a14e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 5 (Thread 0xb2eff3a0 (LWP 4340)):
#0  0xb64a14e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 4 (Thread 0xb18d33a0 (LWP 4341)):
#0  0xb64a8132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0xb268b28a in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#2  0xb268d262 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#3  0xb268d7c2 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#4  0xb2676678 in core::dbus::Bus::run() () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#5  0xb65b32a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#6  0xb6405490 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
#7  0xb64a7c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0xb10563a0 (LWP 4345)):
#0  0xb64a14e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xb06d53a0 (LWP 4346)):
#0  0xb640dd44 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
#1  0xb640b980 in __lll_lock_wait () from /lib/arm-linux-gnueabihf/libpthread.so.0
#2  0xb6407202 in pthread_mutex_lock () from /lib/arm-linux-gnueabihf/libpthread.so.0
#3  0xb609c024 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb3dff230 (LWP 4338)):
#0  0xb64a5620 in syscall () from /lib/arm-linux-gnueabihf/libc.so.6
#1  0xb6c4de3a in QBasicMutex::lockInternal() () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) 


** Changed in: canonical-devices-system-image
     Assignee: John McAleely (john.mcaleely) => Bill Filler (bfiller)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1471338

Title:
  sometimes phone never wakes up or rings on incoming call

Status in Canonical System Image:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  testing on krilin build 56 vivid+overlay latest
  dual sims installed

  The problem is sometimes during an incoming call the phone never wakes
  up or rings at all (and no snap decision). From the remote end the
  call just continues to ring and eventually goes to voicemail. When
  this occurs the signal strength appears to have at least 3 bars.

  It seems ofono is not notifying the upper layers that a call is incoming. This can be verifed by running the following command:
  dbus-monitor --system | grep CallAdded

  This never gets fired during error condition when the incoming call is
  ringing from remote end.

  Attached is the ofono log when I got it to happen once (not sure where
  in the log corresponds to the failure)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338/+subscriptions