If you open the accounts page in the settings app and close it you can't reopen it

Bug #1273781 reported by Dave Morley
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
ubuntu-system-settings-online-accounts (Ubuntu)
Invalid
Undecided
Unassigned
unity-mir (Ubuntu)
Fix Released
Undecided
Michael Zanetti

Bug Description

Steps:
1. Open the settings app
2. Click on accounts
3. Long swipe from the left once accounts is open
4. Long press on one of the thumbnails
5. Close both accounts and settings
6. Open settings
7. Try to open accounts

The second time you can not open accounts.

Related branches

Dave Morley (davmor2)
tags: added: maguro mako r150
affects: accountsservice (Ubuntu) → ubuntu-system-settings-online-accounts (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu-system-settings-online-accounts (Ubuntu):
status: New → Confirmed
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

I assume Dave meant close in the running apps in the dash. I can reproduce it that way by just closing the online accounts "app" that is shown and returning to settings.

This is not a new regression. The basic problem seems to be that online accounts is a separate app and not a plugin to system settings. Therefore we can get into some weird behavior.

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

The solution for this issue will come from bug #1230091

Revision history for this message
Selene ToyKeeper (toykeeper) wrote :

I tried this on image 237, and it seems to be working.

I get a black screen for a few seconds after hitting 'back' on the accounts page, but after closing settings, I can re-open accounts with no difficulty.

Revision history for this message
Selene ToyKeeper (toykeeper) wrote :

Nevermind. I just found the correct way to trigger this bug: Open settings, open accounts, swipe from left to get running apps list, close both settings and accounts with a hold-then-X. After that, accounts won't open again.

Dave Morley (davmor2)
description: updated
tags: added: flo r261
tags: added: r263
rosa maria (ceryscloe)
Changed in ubuntu-system-settings-online-accounts (Ubuntu):
assignee: nobody → rosa maria (ceryscloe)
Revision history for this message
Dave Morley (davmor2) wrote :

Rosa Stop assigning yourself to bugs you are not working on

Changed in ubuntu-system-settings-online-accounts (Ubuntu):
assignee: rosa maria (ceryscloe) → nobody
Revision history for this message
Michał Sawicz (saviq) wrote :

Just understood this issue - when you X an app not launched via upstart, the shell won't kill it, so the service won't launch it again.

Changed in ubuntu-system-settings-online-accounts (Ubuntu):
status: Confirmed → Invalid
Changed in unity-mir (Ubuntu):
assignee: nobody → Michael Zanetti (mzanetti)
Revision history for this message
Alberto Mardegan (mardy) wrote :

Please don't kill unconfined processes (or anyway those not started by upstart); just make sure that the window gets closed: the application will receive the "window closed" events and will take the appropriate action, which most of the times is quitting.
In the Online Accounts case, the service won't quit immediately, but after a short timeout (unless other requests are active).

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

Right, yeah, we should do that to upstart-started apps, too, probably - just let them shut down cleanly, only then ask upstart to shut it down forcfully. Could use support for that (term timeout) in upstart...

Changed in unity-mir (Ubuntu):
status: New → In Progress
tags: added: r276
tags: added: r281
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity-mir - 0.3+14.04.20140414-0ubuntu1

---------------
unity-mir (0.3+14.04.20140414-0ubuntu1) trusty; urgency=low

  [ Michael Zanetti ]
  * send a SIGTERM to the process if upstart fails to stop an
    application (LP: #1273781)

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Alan Griffiths ]
  * Compatibility with Mir 0.1.8

  [ Gerry Boland ]
  * Mir 0.1.8 refactoring allows removal of custom SurfaceFactory and
    instead use InitialSurfacePlacementStrategy to set surface depth and
    other properties. The shell surface notification now comes via
    SessionListener
 -- Ubuntu daily release <email address hidden> Mon, 14 Apr 2014 12:56:40 +0000

Changed in unity-mir (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Selene ToyKeeper (toykeeper) wrote :

I did *not* see this in utopic image 2.

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.