Ubuntu
at-spi2-core package

Requires SessionManager now?

Bug #1128942 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
at-spi2-core (Ubuntu)
New
Low
Unassigned

Bug Description

** (at-spi2-registryd:7039): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

I see above messages in the logs when SessionManager is not running (e.g. during installation in ubiquity-only mode).

Does at-spi2-core now requires SessionManager running?
Should we provide SessionManager in the installer?
Or are these messages mostly harmless?

Dimitri John Ledkov (xnox)
Changed in at-spi2-core (Ubuntu):
importance: Undecided → Low
Revision history for this message
Luke Yelavich (themuso) wrote : Re: [Bug 1128942] [NEW] Requires SessionManager now?

Testing the latest daily of raring and attempting to use Orca for installation shows that everything still works properly, so at-spi2-core doesn't require a session manager, I think its just trying to find one.

Given the new world order with GTK3 and at-spi, we no longer need to explicitly launch at-spi2 in ubiquity-dm, since GTK now launches at-spi2 via the use of libatk-bridge. I wonder if these messages go away if the at-spi2 loading code from ubiquity-dm is removed.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.