dx-packages team mailing list archive

[Launchpad Bug Tracker <1204532@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package indicator-datetime -
13.10.0+13.10.20130913-0ubuntu1

---------------
indicator-datetime (13.10.0+13.10.20130913-0ubuntu1) saucy; urgency=low

  [ Charles Kerr ]
  * Make the EDS planner nonblocking. (LP: #1204532)
  * Minor changes that eliminate unnecessary temporary strings.
  * This change adds a GSettings* arg to the utils functions so that
    they don't have to churn through temporary GSettings objects. These
    functions are usually called in a loop, causing a lot of GSettings
    temporaries, even though the calling code already has an instance
    for that GSettings schema.
  * name says it all; this branch is for improving indicator-datetime
    test coverage.
  * Remove code duplication between timezone-file and timezone-geoclue.
  * Adds a title in the header's action state. (LP: #1223635)

  [ Ted Gould ]
  * Fix GeoClue signal handler to have proper prototype. (LP: #1195874)
  * Protect against invalid begin or end dates. (LP: #1216263)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 256
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Fri, 13 Sep 2013 15:16:38 +0000

** Changed in: indicator-datetime (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1204532

Title:
  indicator-service-datetime hangs on startup when loading a problematic
  calendar

Status in The Date and Time Indicator:
  Fix Committed
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  It seems I've some Evolution configuration issues, so that also manually calling 
  gdbus call --session --dest :1.58 --object-path /org/gnome/evolution/dataserver/Calendar/24658/50 --method org.gnome.evolution.dataserver.Calendar.Open

  Makes my evolution to hang... However, this shouldn't really be a
  problem for indicator-service-datetime that should instead use async
  calls and proper timeouts.

  This is the backtrace showing where the hanging happens:
  http://paste.ubuntu.com/5907745/

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1204532/+subscriptions