I've figured out the immediate root cause, though I'm still puzzled why
the new "clickanywhere" code causes the problem. The initialization path
for the widget takes it through the function calls
cc_timezone_map_init() and either 1 or 2 calls to
cc_timezone_map_size_allocate(). Using the packages from the repo, there
is no problem. When using the "clickanywhere" binary, there are some
instances when cc_timezon_map_init() is not called _at all_! So when
this happens, we SIGSEV. I'm not exactly sure why this is happening. The
functions referenced above are automatically called somewhere out of gtk
or glib, and there isn't anything in the code that I've written to
indicate that the glue code shouldn't have to call
cc_timezone_map_init()

Note that this is only a problem when using gnome_control_center. If you
use "Time & Date Settings..." directly from the time dropdown in the
indicator, there's no problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892370

Title:
  The time zone for China should default to Beijing not Shanghai (when
  offline)

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to