start on dbus != start on started dbus =)
Bug #1302516 reported by
Dimitri John Ledkov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Push Notifications |
Fix Released
|
Undecided
|
Unassigned | ||
| usensord (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
start on dbus -> is start on any event on system or session dbus
start on started dbus -> is start after session/system dbus have started
Related branches
lp:~xnox/ubuntu-push/fix-upstart
- John Lenton (community): Approve
-
Diff: 13 lines (+3/-3)1 file modifieddebian/ubuntu-push-client.conf (+3/-3)
lp:~xnox/usensord/fix-upstart-job
- PS Jenkins bot: Approve (continuous-integration)
- Sergio Schvezov: Approve
-
Diff: 13 lines (+3/-3)1 file modifieddebian/usensord.conf (+3/-3)
lp:~chipaca/ubuntu-push/fix-from-xnox
- Samuele Pedroni: Approve
-
Diff: 3651 lines (+1729/-310)38 files modified.bzrignore (+2/-0)
Makefile (+21/-6)
README (+11/-3)
bus/bus.go (+6/-1)
bus/connectivity/connectivity.go (+31/-8)
bus/connectivity/connectivity_test.go (+79/-19)
bus/endpoint.go (+18/-10)
bus/networkmanager/networkmanager.go (+71/-2)
bus/networkmanager/networkmanager_test.go (+124/-9)
bus/notifications/raw.go (+4/-8)
bus/systemimage/systemimage.go (+68/-0)
bus/systemimage/systemimage_test.go (+62/-0)
bus/testing/testing_endpoint.go (+40/-13)
bus/testing/testing_endpoint_test.go (+12/-10)
bus/urldispatcher/urldispatcher.go (+1/-1)
client/client.go (+99/-8)
client/client_test.go (+224/-49)
client/gethosts/gethost_test.go (+5/-7)
client/session/session.go (+179/-33)
client/session/session_test.go (+333/-45)
debian/config.json (+4/-1)
debian/ubuntu-push-client.conf (+3/-3)
sampleconfigs/dev.json (+3/-3)
server/acceptance/acceptanceclient.go (+6/-0)
server/acceptance/cmd/acceptanceclient.go (+7/-2)
server/acceptance/suites/broadcast.go (+48/-25)
server/acceptance/suites/helpers.go (+2/-2)
server/acceptance/suites/pingpong.go (+2/-2)
server/acceptance/suites/suite.go (+6/-4)
server/broker/broker.go (+20/-0)
server/broker/broker_test.go (+18/-0)
server/broker/exchanges.go (+31/-0)
server/broker/exchanges_test.go (+85/-25)
server/broker/exchg_impl_test.go (+30/-0)
server/broker/simple/simple.go (+32/-10)
server/broker/simple/simple_test.go (+2/-0)
server/broker/testing/impls.go (+10/-0)
server/broker/testsuite/suite.go (+30/-1)
Revision history for this message
| Dimitri John Ledkov (xnox) wrote | #1 |
Revision history for this message
| Dimitri John Ledkov (xnox) wrote | #2 |
| summary: |
- initctl stop restarts daemon + upstart-dbus-session-bridge conflicts in stopping certain jobs |
Revision history for this message
| Dimitri John Ledkov (xnox) wrote Re: upstart-dbus-session-bridge conflicts in stopping certain jobs | #3 |
Revision history for this message
| Dimitri John Ledkov (xnox) wrote | #4 |
| summary: |
- upstart-dbus-session-bridge conflicts in stopping certain jobs + start on dbus != start on started dbus =) |
| affects: | upstart (Ubuntu) → usensord (Ubuntu) |
| description: | updated |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in usensord (Ubuntu): | |
| status: | New → Fix Released |
| Changed in ubuntu-push: | |
| status: | New → Fix Committed |
| Changed in ubuntu-push: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
2014-04-04 11:40:15.074429 stopped JOB='usensord' INSTANCE='' RESULT='ok'
2014-04-04 11:40:15.087736 starting JOB='usensord' INSTANCE=''
2014-04-04 11:40:15.092009 started JOB='usensord' INSTANCE=''
So something does start it up again....