Delay in opening system-settings from indicators

Bug #1502223 reported by Víctor R. Ruiz
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Confirmed
High
Michał Sawicz
unity8 (Ubuntu)
Triaged
High
Nick Dedekind

Bug Description

Reproduce:
- Go to indicator bluetooth.
- Tap in settings (system settings must open in bluetooth settings).
- Go to indicator sound.
- Tap in settings (system settings must open in sound settings).
- Go back to settings main screen and go to Privacy > Report.
- Tap on "App crashes and errors" switch to enable.
- Go back.
- Tap on "App crashes and errors" switch to disable.
- Go back.
- Tap on "App crashes and errors" switch to enable again.

Expected result.
- Opening System Settings from any indicator is quick.

Actual result.
- Opening System Settings from any indicator takes 30 seconds

current build number: 129
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en

Tags: qa-silo
Revision history for this message
Víctor R. Ruiz (vrruiz) wrote :

While testing silo 41, there was no delay, there were some crashes and system settings couldn't be opened at all through indicators.

Revision history for this message
Víctor R. Ruiz (vrruiz) wrote :

Delay is ~30 seconds.

Revision history for this message
Víctor R. Ruiz (vrruiz) wrote :

Correct sequences is:

- Tap on "App crashes and errors" switch to enable.
- Go back.
- Tap on "App crashes and errors" switch to disable.
- Go back.
- Tap on "App crashes and errors" switch to enable again.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-system-settings (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the report but the description is not clear, is there a delay when opening from indicator or is there a delay after going to the error reporting page?

Changed in ubuntu-system-settings (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

You can trigger the delay state by toggling the error reporting check box. After you've entered the delay state, you can trigger this from any indicator.

I'll update the description.

Changed in ubuntu-system-settings (Ubuntu):
status: Incomplete → Confirmed
description: updated
Changed in canonical-devices-system-image:
assignee: nobody → Bill Filler (bfiller)
importance: Undecided → High
milestone: none → backlog
status: New → Confirmed
Bill Filler (bfiller)
Changed in ubuntu-system-settings (Ubuntu):
assignee: nobody → Jonas G. Drange (jonas-drange)
Bill Filler (bfiller)
Changed in canonical-devices-system-image:
milestone: backlog → ww02-2016
Bill Filler (bfiller)
Changed in ubuntu-system-settings (Ubuntu):
assignee: Jonas G. Drange (jonas-drange) → Ken VanDine (ken-vandine)
Revision history for this message
Ken VanDine (ken-vandine) wrote :

I've reproduced this issue with slow to launch from the indicators, but when I get it into the "slow" state, it's only slow to launch from the indicators not with url-dispatcher.

For example, once in the slow state I can run these commands and get instant results:

url-dispatcher settings:///system/security-privacy
url-dispatcher settings:///system/sound

The problem is noticeable when launched from any of the indicators, so I think it must be some delay in unity8. I'm a bit puzzled why the toggling of crash reporting triggers it though.

Changed in ubuntu-system-settings (Ubuntu):
status: Confirmed → Invalid
Michał Sawicz (saviq)
Changed in unity8 (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → Nick Dedekind (nick-dedekind)
Bill Filler (bfiller)
Changed in canonical-devices-system-image:
assignee: Bill Filler (bfiller) → kevin gunn (kgunn72)
Changed in canonical-devices-system-image:
milestone: ww02-2016 → ww08-2016
kevin gunn (kgunn72)
no longer affects: ubuntu-system-settings (Ubuntu)
Changed in canonical-devices-system-image:
milestone: ww08-2016 → 11
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

any chance to revisit this? do we still see it?

Changed in canonical-devices-system-image:
milestone: 11 → backlog
kevin gunn (kgunn72)
Changed in canonical-devices-system-image:
assignee: kevin gunn (kgunn72) → Michał Sawicz (saviq)
Revision history for this message
kevin gunn (kgunn72) wrote :

@vrruiz - can you confirm this is still happening

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.