21:46 < jibel> stgraber, the problem is still there with cgmanager 0.32-4ubuntu1
21:47 < stgraber> jibel: now that's something I wasn't hoping to hear :)
21:47 < stgraber> jibel: so I'm guessing the same dbus-send test hangs against 
cgmanager/sock and not against cgmanager.lower/sock, right?
21:47 < jibel> and the logs are not more interesting to read
21:48 < jibel> stgraber, yes, same result.
21:49 < stgraber> jibel: ok, what happens if you "pkill -9 cgproxy", does that 
fix it?
21:51 < jibel> stgraber, it does
21:51 < ogra> wow, i didnt know you could tear it out uderneath without losing 
anything 
21:52 < stgraber> ok, so that seems to confirm that it's the proxy getting 
confused somehow
21:52 < stgraber> ogra: yeah, you can shoot them in the head, they'll respawn 
and nobody should notice, we had to implement that so you can dist-upgrade the 
host and not kill all your containers in the process
21:52 < ogra> neat
21:53 < ogra> so worst case we could just introduce a watchdog as workaround 
21:53 < stgraber> so one thing I notice in the log and that's not supposed to 
really be a problem but may be making things worse at the moment is that we're 
dealing with a long running connection to cgproxy there which isn't very usual
21:53 < stgraber> upstart and systemd-logind both establish a new connection 
every time they need to talk to it rather than keeping a long running one around
21:54 < ogra> who is that keeping the constant connection atm ? 
upstart-app-launch ? 
21:54 < stgraber> it may be worth patching whatever's talking to cgmanager to 
do that too and see if that helps. Don't get me wrong, there's still a 
cgmanager/cgproxy bug somewhere, but short of having hallyn around, this may 
take a while to track down so if connect/disconnect does the trick, that may be 
an easy way out.
21:55 < ogra> ted, ^^^ ?
21:55 < stgraber> don't know, I don't think I've seen a log with the app name, 
only its pid :) but yeah, whatever calls gettasks all the time :)
21:55 < ogra> well either qtmir or UAL 
21:55 < ogra> i guess
21:58 < pmcgowan> stgraber, ogra good stuff, can we get all this in the bug 
report?
21:58 < stgraber> probably, what's the bug # for that again? I was given at 
least two different ones for this this morning

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

Title:
  [TOPBLOCKER] UI randomly freezes

Status in “cgmanager” package in Ubuntu:
  Incomplete
Status in “ubuntu-app-launch” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Opinion
Status in “ubuntu-app-launch” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Opinion

Bug description:
  Summary
  UI randomly freezes

  steps:
  1. unlock greeter
  2. open app
  3. pull down random indicator
  4. close indicator
  5. open app
  6. swipe to view all open apps
  7. open launcher
  8. close some open apps
  9. repeat until ui freezes

  device info:
  [service]
  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  device: krillin
  build_number: 79
  version_detail: 
ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1377332/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to