On Thu, 2013-10-24 at 13:37 -0400, Matthew Barnes wrote: > ** (evolution:685): WARNING **: Couldn't register with accessibility > bus: Did not receive a reply. Possible causes include: the remote > application did not send a reply, the message bus security policy > blocked the reply, the reply timeout expired, or the network connection > was broken. > > (evolution:685): Gtk-WARNING **: Failed to register client: > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name > org.gnome.SessionManager was not provided by any .service files > > ** (evolution-alarm-notify:716): WARNING **: Couldn't register with > accessibility bus: Did not receive a reply. Possible causes include: the > remote application did not send a reply, the message bus security policy > blocked the reply, the reply timeout expired, or the network connection > was broken. > > Unfortunately GTK3 increasingly assumes a GNOME environment, and > complains when used elsewhere. The warnings themselves I believe are > harmless -- it's just indicating certain desktop integration features > won't work.
Hi Matthew, yes, all warnings are harmless, I missed to snip the above warnings after pasting. Annoying is only that ~/.xsession-errors increases that much by the set_id WebKit warnings. I don't care about the disc space, but it's not pleasant to check .xsession-errors with KiBs of irrelevant warnings, assumed there should be an issue. And from time to time I take a look at .xsession-errors only to see if there's something going wrong, I didn't notice. Regards, Ralf _______________________________________________ evolution-list mailing list [email protected] To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
