dx-packages team mailing list archive

[Charles Kerr <charles.kerr@xxxxxxxxxxxxx>]

Looks like this is the culprit:

#0  close () at ../sysdeps/unix/syscall-template.S:81
#1  0xb7bd3545 in g_mapped_file_new (filename=filename@entry=0x809dca0 "/etc/localtime", 
    writable=writable@entry=0, error=error@entry=0x0)
    at /build/buildd/glib2.0-2.38.0/./glib/gmappedfile.c:271
#2  0xb7bfa972 in zone_info_unix (identifier=<optimised out>)
    at /build/buildd/glib2.0-2.38.0/./glib/gtimezone.c:432
#3  g_time_zone_new (identifier=0x0) at /build/buildd/glib2.0-2.38.0/./glib/gtimezone.c:1411
#4  0xb7bfb595 in g_time_zone_new_local () at /build/buildd/glib2.0-2.38.0/./glib/gtimezone.c:1508
#5  0xb7bb9de6 in g_date_time_new_now_local () at /build/buildd/glib2.0-2.38.0/./glib/gdatetime.c:731

-- 
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/1238043

Title:
  indicator-datetime-service is opening /etc/localtime every 5 seconds
  even on a totally "idle" system

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  In an attempt to reduce unnecessary frequent periodic file access to
  save power, I noticed that indicator-datetime-service is opening and
  closing /etc/localtime every 5 seconds on my desktop and not
  apparently reading this file.   On the ubuntu phone it is doing the
  same thing with /etc/writable/localtime.

  This seems a little excessive, especially because the TZ data doesn't
  change quite that frequently.  It would be useful if this excessive
  polling on the file could be reduced if possible.

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