Public bug reported:
Using trusting indicator-power has a bunch of those errors in its logs
(/var/lib/lightdm/.cache/upstart/indicator-power.log)
"Indicator-Power-Message: exiting: service couldn't acquire or lost ownership
of busname"
Other indicators seem to have similar issues, e.g indicator-session has those
and
"WARNING **:
/build/buildd/indicator-session-12.10.5+14.04.20131125/src/backend-dbus/actions.c:196
on_screensaver_proxy_ready: can't connect : Connection refused"
(string might not be exact, I'm translating it there)
Should those be open on individual indicators or is there an
infrastructur problem with the upstart jobs?
** Affects: indicator-power (Ubuntu)
Importance: Medium
Assignee: Charles Kerr (charlesk)
Status: Confirmed
** Changed in: indicator-power (Ubuntu)
Importance: Undecided => Medium
** Changed in: indicator-power (Ubuntu)
Status: New => Confirmed
** Changed in: indicator-power (Ubuntu)
Assignee: (unassigned) => Charles Kerr (charlesk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1257251
Title:
"exiting: service couldn't acquire or lost ownership of busname"
errors on the greeter logs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1257251/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
