touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

** Also affects: mir
   Importance: Undecided
       Status: New

** Changed in: mir
   Importance: Undecided => High

-- 
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/1532979

Title:
  N7 freeze/ui lockup on hdmi hotplug when puritine apps open

Status in canonical-pocket-desktop:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  OK, so after quite a a bit of testing in series on the N7 and N4 consisting of many plug/unplug events to determine stability
  ~10x plug/unplug with just dash open on both - both devices survived fine.
  ~10x plug/unplug with several ubuntu apps open (dash, browser, scancode, message app, clock, pathwind, music, system settings) - both devices survived fine

  on N7 while connected, i would open up all the ubuntu apps above, then
  launching a puritine app (ff or lo), ui remained usable, then on
  unplug it would freeze - either with the "you are connected to a
  display" or the ui would refresh on the device screen, but always the
  ui was completely frozen, the power button didn't work either, i did
  connect to shell and run top...i would see services runnning ok, for
  instance ff & proot consuming like 45% cpu each. There were no crash
  files..but the ui would not respond in any way to touch/mouse input. I
  was able to replicate this 3x in a row.

  on N4, I followed roughly the same steps - open ubuntu apps, then
  puritine, i even opened all the puritine apps at once. I was able to
  hotplug 20x just fine, no reboots required, no freeze etc.

  subsequently i tried N7 once more, just having the Dash open and then
  launching FF, it survived one plug+unplug+plug...i let sit for some
  moments, i then mouse to move the ff window (i think it began to
  resize as i missed the target) and in an instant froze, hdmi remote
  screen went black and the device screen maintained the "you are
  connected to a monitor" billboard - unplugging, the billboard just
  remained. Feels like a potential memory issues....could it be that the
  n4 kernel is tuned better, n7 is more sensitive ?

  hard to tell if this may effect other devices similar to N7

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1532979/+subscriptions