On 2019-08-15 at 07:34:00, Simon McVittie wrote:
> Control: tags -1 + moreinfo
> On Wed, 14 Aug 2019 at 23:48:09 +0000, brian m. carlson wrote:
> > GTK+ produces the following warning when attempting to register a client
> > with the session manager and the client is already registered:
> > 
> >   (caja:3729): Gtk-WARNING **: 02:59:57.229: Failed to register client: 
> > GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
> > client
> Under what circumstances does this occur? I see the program in question
> is caja. What desktop environment is this in, and how can this bug be
> reproduced?

This is in MATE with a typical mate-session startup. This message gets
logged to ~/.xsession-errors, and it's trivially reproducible by running
"killall caja". I believe I've seen it before when running from the
command line, but I can't seem to reproduce that now.

I unfortunately don't have a fresh session to test against, and MATE
isn't likely to run nicely in a Docker container, which is my usual test
environment for bugs.

> (I assume it's either GNOME, one of the various GNOME forks, or XFCE,
> based on the D-Bus APIs used in the function that contains that warning.)
> I don't know the session manager API well enough to know immediately
> whether this message indicates a bug in the session manager, the
> application, GTK, or something else.

I see this much like reporting an ENOENT with unlink(2): what you wanted
has already been done, so barring some specific circumstance where you
know it will be a problem, there's no reason to report an error.
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

Attachment: signature.asc
Description: PGP signature

Reply via email to