https://bugs.meego.com/show_bug.cgi?id=20885
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
Flags| |MeeGo_Update_Release_Blocke
| |r?
Severity|normal |critical
--- Comment #1 from pohly <patrick.ohly(a)intel.com> 2011-07-11 20:45:08 UTC ---
The MeeGo UX usage model is that the user never has to enter settings to run
syncs. This is a critical feature.
I have a fix ready, committed to the "master" branch of SyncEvolution":
commit 11b322b5ee2c7dc0cb98963f60db51a16307583c
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Mon Jul 11 22:22:50 2011 +0200
D-Bus server: avoid shutting down while auto-sync is active (BMC #20885)
When a config was set to "auto-sync on", the AutoSyncManager added it
to a list, but did not prevent the server from shutting down. Not sure
how this was meant to work or when it broke.
Fixing it is easy: as long as AutoSyncManager has at least one config
lined up for auto-syncing, it holds a reference on the AutoTerm
instance and thus prevents shutting down.
This commit also adds test cases for various situations:
- prevent shutdown while auto-sync on
- re-enable shutdown while timer is running
- re-enable shutdown while timer is off
--------
Product: OS Middleware
Component: SyncEvolution
MeeGo Release: 1.2
Severity: critical
Priority: Undecided
Keywords:
Status: RESOLVED
Who: patrick.ohly(a)intel.com
Assigned To: patrick.ohly(a)intel.com
Target Build: ---
Flags:
Changed: Status Resolution Flags Severity
--------
https://bugs.meego.com/show_bug.cgi?id=20885
--
Configure bugmail:
https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.