fails when there is no existing system bus?
Bug #456008 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DBus Test Runner |
Invalid
|
Low
|
Unassigned | ||
Bug Description
libindicate-ERROR **: Unable to get system bus: Failed to connect to socket /var/run/
aborting...
Client: ** (process:23919): DEBUG: 0 of 100 indicators displayed
FAIL: test_indicator_
DBus address: unix:abstract=
libindicate-ERROR **: Unable to get system bus: Failed to connect to socket /var/run/
This is what we see running in a chroot: in the chroot no services are started; and I suspect that this means that the test runner isn't providing the fully isolated bus its meant to (or perhaps libindicate isn't honouring the dbus test runners isolated bus)
| Changed in dbus-test-runner: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| milestone: | none → 09.11 |
| Changed in dbus-test-runner: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
