"exiting: service couldn't acquire or lost ownership of busname" errors on the greeter logs

Bug #1257251 reported by Sebastien Bacher on 2013-12-03
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
indicator-power (Ubuntu)
Medium
Charles Kerr

Bug Description

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?

Changed in indicator-power (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
assignee: nobody → Charles Kerr (charlesk)
Chris H (harsesus) wrote :

I get this message in saucy. My indicator stopped logging out and shutting down so I tried...

harsesus@talyn:~$ /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service --logout

** (process:23381): WARNING **: exiting: service couldn't acquire, or lost ownership of, busname

I added a bunch of software/ppa's after a fresh install and can't pin down the cause... I definately did not add Cairo-Dock, which some googling reveals creates a similar *surface* issue. Is there a way to get the indicator behaving properly? /noob

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers