Icons in launcher sometimes refuse to launch application

Bug #1541388 reported by SB
52
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
Critical
Michał Sawicz
qtmir (Ubuntu)
Fix Released
Critical
Nick Dedekind

Bug Description

After OTA-9 on BQ Aquaris E4.5 I am sometimes experiencing strange behavior of icons on the launcher, sometimes they refuse to launch the application and nothing helps except reboot, launching the application from the Apps scope works however, removing the icon from the launcher, launching from scope and then pinning the icon to the launcher does nothing, when you tap the newly added icon application does not launch, only reboot helps.

This happened with File Manager, Browser and Gallery, generally after they froze/crashed. Other applications launch normally. I checked /var/crash after Gallery froze today (then I closed it and tried to relaunch it with the icon in the launcher), but nothing inside from today, last log there is from 31.1 it seems.

http://paste.ubuntu.com/14865896/

http://paste.ubuntu.com/14865887/

Unity logs.

Any other logs I can check? Upload older crash files?

Related branches

Revision history for this message
SB (emehntehtt) wrote :

I have just discovered that Gallery now launches from the launcher, like it recovered somehow after some time.

Revision history for this message
Michael Zanetti (mzanetti) wrote :

I've seen this too since OTA-9.

Changed in unity8 (Ubuntu):
status: New → Confirmed
assignee: nobody → Michael Zanetti (mzanetti)
importance: Undecided → Critical
Revision history for this message
Michael Zanetti (mzanetti) wrote :

Just happened again. Managed to catch a log:

When I press the address-book-app in the launcher, I get this output from unity8.log but the app does *NOT* launch:

qtmir.applications: ApplicationManager::startApplication - this= qtmir::ApplicationManager(0xf66570, name = "qtmir::ApplicationManager") appId address-book-app
ApplicationManager::startApplication - application appId= "address-book-app" is queued to start

This indicates that the call ends up in QtMir properly and it seems to get lost in there.

reassigning the issue to QtMir

affects: unity8 (Ubuntu) → qtmir (Ubuntu)
Changed in qtmir (Ubuntu):
assignee: Michael Zanetti (mzanetti) → nobody
Revision history for this message
Michael Zanetti (mzanetti) wrote :

For the record, here's the full unity8.log when this issue happens.

http://paste.ubuntu.com/14867269/

Changed in qtmir (Ubuntu):
assignee: nobody → Nick Dedekind (nick-dedekind)
Revision history for this message
Nick Dedekind (nick-dedekind) wrote :

I can reproduce this now:

1) open dialer-app from dash (wait for full load).
2) switch back to dash and wait a few seconds
3) simulate app failure using ssh "kill -9 `pidof dialer-app`".
4) open switcher and swipe app placeholder away.

You should now be in the state where you cannot re-load the app.

Michał Sawicz (saviq)
Changed in canonical-devices-system-image:
status: New → Triaged
status: Triaged → In Progress
importance: Undecided → Critical
assignee: nobody → Michał Sawicz (saviq)
Changed in qtmir (Ubuntu):
status: Confirmed → In Progress
Changed in canonical-devices-system-image:
milestone: none → ww04-2016
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package qtmir - 0.4.7+16.04.20160208-0ubuntu1

---------------
qtmir (0.4.7+16.04.20160208-0ubuntu1) xenial; urgency=medium

  [ Nick Dedekind ]
  * Added fix and test for closing app during the StoppedResumable
    state. (LP: #1541388)

 -- Michał Sawicz <email address hidden> Mon, 08 Feb 2016 09:36:17 +0000

Changed in qtmir (Ubuntu):
status: In Progress → Fix Released
Changed in canonical-devices-system-image:
status: In Progress → Fix Committed
Changed in canonical-devices-system-image:
milestone: ww04-2016 → 9.1
Revision history for this message
Michael S. (i-mich9el-s) wrote :

This issue is NOT fixed. It still occurs with OTA 9.1 on BQ Aquaris E4.5.

Revision history for this message
Michael S. (i-mich9el-s) wrote :

The behavior is exactly as before: Unity launcher doesn't work. Starting the app via the application scope works.

Revision history for this message
Michał Sawicz (saviq) wrote :

Can you please show your output from the below on the phone:

$ system-image-cli -i

I just tried the steps from comment no. 5 above and can confirm that situation is fixed. Any chance you're seeing bug #1527737? Can you please describe the steps you're taking that lead to this behaviour for you?

Revision history for this message
Michael S. (i-mich9el-s) wrote :

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 30
device name: krillin
channel: ubuntu-touch/stable/bq-aquaris.en
last update: 2016-02-24 21:46:53
version version: 30
version ubuntu: 20160217.1
version tag: OTA-9.1
version device: 20160108-efc96d8
version custom: 20160111-926-36--vivid

How to reproduce:
1) Wipe from the left, to get the unity launcher
2) Scroll to the top of the launcher bar
3) Tap on the "dekko" icon
4) Dekko doesn't start

Revision history for this message
Michael S. (i-mich9el-s) wrote :

See video attached to https://bugs.launchpad.net/dekko/+bug/1543744
The is exact the same behavior now with OTA 9.1

Revision history for this message
Michael S. (i-mich9el-s) wrote :

Attached a video I've just taken, which clearly shows, that in OTA 9.1 the bug is NOT fixed.

Revision history for this message
Michał Sawicz (saviq) wrote :

OK that's the symptom, not the cause, I assume when you reboot it works fine, so any steps you can think of that lead to this situation?

I mean, restart the phone, start dekko from launcher - I suppose it works then? What did you do to get to the state where it doesn't launch from the launcher any more?

Also, there's no need to use capitals. As you can see we're trying to resolve this issue for you, not trying to dismiss it.

Revision history for this message
Michael S. (i-mich9el-s) wrote :

After reboot the phone will work fine again. I dont now how to reproduce, but my suspicion is, that multiple restarts of dekko (after moving from one network to another dekko does not to receive emails - see #1520693) causes the problem. At the moment dekko is the only app involved by this issue.

Changed in canonical-devices-system-image:
status: Fix Committed → Fix Released
Revision history for this message
Michael S. (i-mich9el-s) wrote :

This issue exists furthermore. It still occurs with OTA 10.1 on BQ Aquaris E4.5.
Dekko refuses startup frequently when using the unity launcher.

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Opened bug #1577793 as this seems specific to dekko

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.