> What about test cases? The dialer tests passed despite the bug when I > was checking this. Does any existing test catch it - which would mean > either the bug was introduced manually or the test plan is complete?
We will add a manual test case for this and will think with high prio on how to test it automagically (might need to be autopilot, not sure yet). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1528668 Title: [regression] Qt.application.active not working correctly Status in Canonical System Image: Fix Committed Status in qtubuntu package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1) open dialer-app 2) lock the screen 3) unlock the screen Expected behavior: Qt.application.active == true Current behavior Qt.application.active == false until we manually switch the app to background/foreground again. Additional info: This is causing a bigger issue in the dialer-app functionality. It currently only refreshes the live call view when in foreground, so when dialer is in this state, calls are placed but the call controls don't work (like hangup or speaker mode). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528668/+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
