[regression] Qt.application.active not working correctly

[Tiago Salem Herrmann]

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).

[Michał Sawicz (saviq)]

Most likely culprit: http://bazaar.launchpad.net/~phablet-team/qtubuntu/trunk/revision/298

[Michał Sawicz (saviq)]

As per http://doc.qt.io/qt-5/qml-qtqml-qt.html#application-prop

application.active Deprecated, use Qt.application.state == Qt.ApplicationActive instead.

We should not have changed the behaviour of the .active property though.

[Michał Sawicz (saviq)]

Adding this code:

  Text {
    text: "state: " + Qt.application.state + "\nactive: " + Qt.application.active
    onTextChanged: console.debug(text)
  }

At the end of /usr/share/dialer-app/dialer-app.qml indeed does show trouble, the application remains in "Inactive" state when in foreground (and active remains false).

I'll be reverting that change for now.

[Andrew Hayzen (ahayzen)]

I found an issue where it now takes the launcher two taps to dismiss, and wanted to check that this is the same issue?

What happened:
1) Swipe from left to right to show the launcher
2) Tap in the dimmed/shadow portion (right side) of the screen
3) Notice nothing happens, tap again and notice the launcher is dismissed.

What was expected:
At step 2 for the launcher to be dismissed

[Launchpad Janitor (janitor)]

This bug was fixed in the package qtubuntu - 0.62+16.04.20160104-0ubuntu1

---------------
qtubuntu (0.62+16.04.20160104-0ubuntu1) xenial; urgency=medium

  [ Daniel d'Andrada ]
  * Fix QGuiApplication::applicationState() updates (LP: #1528668)

  [ Gerry Boland ]
  * On geometry change, save new geometry before creating change event
    (LP: #1526328)

 -- Michał Sawicz <email address hidden> Mon, 04 Jan 2016 09:38:35 +0000

[Cris Dywan (kalikiana)]

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?

[Michał Sawicz (saviq)]

> 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).

[Tobias Stollenwerk (tobias-stollenwerk)]

For me, it seems the problem is still there in OTA-9.

I reported this bug:

https://bugs.launchpad.net/ubuntu-ux/+bug/1512327

which was marked as a duplicate for this one.

Since the status is "Fix Released" I was wondering if the fix was released in OTA-9.

My System is the following: (I will translate some descriptions from german):
- Hardware: BQ Aquaris 4.5 Ubuntu Version

From Settings->Device Information-> Operating System :
- OS-Build Number: OTA-9
- Ubuntu-Image-Part: 20160123.1
- Ubuntu-Build-Description: Ubuntu 15.04 -armhf (20160123-115651)
- Device-Image-Part: 20160108-efc96d8
- Device-Builde-Description: KRILIN01A-S15A_BQ_L100EN_2029_160123
- Adaption-Image-Part: 20160111-926-36-vivid

[Michał Sawicz (saviq)]

@Tobias please comment on the other bug, then, and remove the duplicate link, must be a separate issue after all.