I just got a freeze from Navigator, so it still happens in current stable (OTA-11).
Can't give the details because I have no idea of the application name (Ubuntu Touch doesn't give much information about the underlying system, sounds like a bad idea seeing as it's still beta, for what I've seen). Should I go on reporting or is this bug fixed in the future, and should be marked as such ? Le mercredi 8 juin 2016 00:08:28 CEST, Michael Zanetti <michael.zane...@canonical.com> a écrit : > This has been fixed as part of ~mzanetti/unity8/alerting-pips > > Should land in rc-proposed soonish > > ** Branch linked: lp:~mzanetti/unity8/alerting-pips > > ** Changed in: unity8 (Ubuntu) > Status: Triaged => In Progress > > ** Changed in: canonical-devices-system-image > Status: Triaged => In Progress > -- 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/1584348 Title: Launcher thinking app is running still when it's dead Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: When you let an app opened after a while (about hours) and after that you try to work with it the app sometimes does not respond. I saw it with a lot of apps (camera, dialer, facebook, telegram, webbrowser... Atached you'll find a video where you can see me trying to use camera app without any result. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584348/+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
