This bug was fixed in the package indicator-datetime -
13.10.0+15.10.20150909-0ubuntu1
---------------
indicator-datetime (13.10.0+15.10.20150909-0ubuntu1) wily; urgency=medium
[ CI Train Bot ]
* New rebuild forced.
[ Iain Lane ]
* Remove warnings from test logs. Swallow the ones that are expected
and fail the test if they don't show up. In addition, fail tests if
unexpected warnings show up again.
[ Lars Uebernickel ]
* Remove warnings from test logs. Swallow the ones that are expected
and fail the test if they don't show up. In addition, fail tests if
unexpected warnings show up again.
[ Sebastien Bacher ]
* under unity8 start system-settings instead unity-control-center,
don't special case u-c-c by looking for the binary, Unity
installations come with it installed (LP: #1489481)
-- Iain Lane <i...@orangesquash.org.uk> Wed, 09 Sep 2015 16:40:52
+0000
** Changed in: indicator-datetime (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1489481
Title:
Try to start unity-control-center on unity8 sessions
Status in indicator-datetime package in Ubuntu:
Fix Released
Bug description:
Using the current wily version it tries to start u-c-c, that doesn't
work. The suggested change checks if MIR_SOCKET is defined and calls
the unity8 version in this case
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1489481/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
