make link : /usr/lib/systemd/user/dbus.socket ==> /usr/lib/systemd/user/sockets.targe... 03/115903/1 accepted/tizen/3.0/common/20170223.122144 accepted/tizen/3.0/ivi/20170223.001216 accepted/tizen/3.0/mobile/20170223.001158 accepted/tizen/3.0/tv/20170223.001206 accepted/tizen/3.0/wearable/20170223.001212 submit/tizen_3.0/20170222.044139
authorINSUN PYO <insun.pyo@ubuntu1604.playinsun.pe.kr>
Wed, 22 Feb 2017 02:38:43 +0000 (11:38 +0900)
committerINSUN PYO <insun.pyo@ubuntu1604.playinsun.pe.kr>
Wed, 22 Feb 2017 03:09:54 +0000 (12:09 +0900)
commit1beb067e73478b3948980eb19e379a8986dc365a
tree1c440f59038a15b307855eb8624363a00cb233a6
parent4f11f164f44d78ec6a54892e5d4095ca52e7117d
make link : /usr/lib/systemd/user/dbus.socket ==> /usr/lib/systemd/user/sockets.target.wants/dbus.socket

Until now, dbus.socket of user session  was not running in the sockets.target.
dbus.socket has been triggered by dbus.service's dependencies.
The dbus.service is included in basic.target.

Therefore, there are some dependency issues.
If a service runs before dbus.service, the service can not accesses dbus system.
(Since dbus.socket is not yet activated, so you can not make a dbus connection.)

I have modified dbus.service to be explicitly run in sockets.target.
On the session bus, sockets.target is guaranteed to run before all services.

Signed-off-by: INSUN PYO <insun.pyo@ubuntu1604.playinsun.pe.kr>
Change-Id: Ic46f1a46b458e2017b0025c6e564ac1204eb8cc8
packaging/dbus.spec