Service quits even if ref count is not zero

Bug #709200 reported by Natalia Bidart
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Fix Released
Medium
Natalia Bidart
Ubuntu Single Sign On Client
Fix Released
High
Natalia Bidart
ubuntu-sso-client (Ubuntu)
Fix Released
High
Natalia Bidart
Natty
Fix Released
High
Natalia Bidart

Bug Description

When the ref count reaches 0, the service setups a timer that makes the service quits, even if a new client was requesting the service after the timer was set and the service was actually quited.

Related branches

Changed in ubuntu-sso-client:
status: New → In Progress
assignee: nobody → Naty Bidart (nataliabidart)
importance: Undecided → High
Changed in ubuntu-sso-client (Ubuntu):
status: New → In Progress
importance: Undecided → High
milestone: none → natty-alpha-2
assignee: nobody → Naty Bidart (nataliabidart)
Changed in ubuntuone-client:
status: New → Triaged
assignee: nobody → Naty Bidart (nataliabidart)
importance: Undecided → Medium
Changed in ubuntu-sso-client:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-sso-client - 1.1.10-0ubuntu1

---------------
ubuntu-sso-client (1.1.10-0ubuntu1) natty; urgency=low

  * New upstream release:

    [ Natalia B. Bidart <email address hidden> ]
      - The service is not shutdown if ref count is not zero, even if the
        shutdown_func was queued (LP: #709200).
      - Test failures (caused by a buggy test) fixed (LP: #704941).
 -- Natalia Bidart (nessita) <email address hidden> Fri, 28 Jan 2011 13:38:28 -0300

Changed in ubuntu-sso-client (Ubuntu Natty):
status: In Progress → Fix Released
dobey (dobey)
Changed in ubuntu-sso-client:
status: Fix Committed → Fix Released
Changed in ubuntuone-client:
status: Triaged → In Progress
Changed in ubuntuone-client:
status: In Progress → Fix Committed
dobey (dobey)
Changed in ubuntuone-client:
status: Fix Committed → Fix Released
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.