touch-packages team mailing list archive

[Alexandros Frantzis <alexandros.frantzis@xxxxxxxxxxxxx>]

> i succeeded in getting my device stuck in a frozen state. it seems
alive, i can interact with the shell

How can you interact with the shell? Does it respond to input? Can you
turn the screen on/off with the power button?

> so i grabbed a dump from lsof as well.
> here's the list of open files dump

Good call! unity8 has clearly reached its fd limit. It seems to be
leaking fds (can't tell if it's unity8 itself leaking or another
component inside unity8, e.g., mir):

...
unity8     2421           phablet 1017r      CHR      13,70      0t0    1122358 /dev/input/event6 (deleted)
unity8     2421           phablet 1018r      CHR      13,70      0t0    1117702 /dev/input/event6 (deleted)
unity8     2421           phablet 1019r      CHR      13,70      0t0    1120899 /dev/input/event6 (deleted)
unity8     2421           phablet 1020r     0000        0,9        0       5513 anon_inode
unity8     2421           phablet 1021r     0000        0,9        0       5513 anon_inode
unity8     2421           phablet 1022r      CHR      13,70      0t0    1120534 /dev/input/event6 (deleted)
unity8     2421           phablet 1023r      CHR      13,70      0t0    1117848 /dev/input/event6 (deleted)

Unfortunately we didn't get a list of files for USC since it's running
as root. If you still have the phone in that state could you rerun lsof
with sudo?

> ok, i was able to attach gdb to usc, here's the bt

The backtrace seems normal. USC is just waiting for work to do, nothing
suspicious in this case.

So, the question is if this is indeed an instance of the same bug we
have been investigating or a different bug you have uncovered.

I will follow the fd leak lead and see if I can get more information.

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

Title:
  Shell not responsive after an incoming SMS or call notification

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  In Progress

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

  Adding incoming calls as also suspected to be triggering the issue

  Note this has been impossible to reproduce, and in use only happens
  very rarely

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