Unable to fetch children: No such interface `org.ayatana.bamf.view'

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

I'm getting this whenever I close the pidgin main window (the so called buddy-list):

WARN 2012-04-04 10:16:11 unity <unknown>:0 Unable to fetch children: No such interface `org.ayatana.bamf.view' on object at path /org/ayatana/bamf/application2083276344

WARN 2012-04-04 10:16:11 unity <unknown>:0 Unable to fetch children: No such interface `org.ayatana.bamf.view' on object at path /org/ayatana/bamf/application2083276344

WARN 2012-04-04 10:16:11 unity <unknown>:0 Unable to fetch children: No such interface `org.ayatana.bamf.view' on object at path /org/ayatana/bamf/application2083276344

Re-opening the pidgin main window doesn't give any error or warning messages at all.

I noticed that it also happens when closing the last chromium-browser window:

WARN 2012-04-04 10:18:01 unity <unknown>:0 Unable to fetch children: No such interface `org.ayatana.bamf.view' on object at path /org/ayatana/bamf/application843378290

But in that case I'm getting only one line of warning (instead of three with pidgin).

Status changed to 'Confirmed' because the bug affects multiple users.

saw this when doing a unity --reset

I also saw this after doing a unity --reset

Seeing this all the time. could it be linked to bug #803943 ?

This is not exactly a bug... There's only a warning caused by dbus objects that have been destroyed, it should cause no side effect tough.

unity <unknown>:0 Unable to fetch children: No such interface `org.ayatana.bamf.view affects me as well...

I also get this when opening or closing random windows recently - and mostly notice that because for me, it's immedately followed by a unity-killing segfault.

Some info:
- Ubuntu 12.10
- nvidia blob driver
- multiple screens in use

The way I see this is that there's only two possibilities

a) the warning concerns a valid error
or
b) it doesn't

Either way, there's something that needs fixing, either the underlying problem itself or the log-spam in .xsession-errors.

Just my 2¢

I believe bug 937680 and bug 943083 are likely dupes. The former is how it manifests itself in precise, the latter in oneiric.

I have a general problem whenever re-booting Ubuntu 12.10; Compiz seems to always crash, and I'm losing the launcher, dash, window decorations, ability to switch desktops or even window focus. If I'm able to type into a terminal under unity (still default tty7), I'm usually able to (temporarily) fix the problem by typing
 $ compiz --replace &

However, if I have to switch to tty1, it's not working with the same
 $ DISPLAY=:0.0 compiz --replace & (not even if I do a killall -9 compiz first)

In this case, I have to do the following from tty1:
 $ sudo service lightdm restart

Sorry for the long intro, but here's the link to this very issue;

Whenever I'm able to get into a terminal window under unity and fix the issue by 'compiz --replace &', the terminal window is printing out lots of these ayatana/bamf warnings afterwords. Also, a few ERRORs are printed:

ERROR 2013-02-19 11:07:36 nux.gestures_subscription GesturesSubscription.cpp:364 Failed to set Geis subscription configuration com.canonical.oif.drag.threshold
ERROR 2013-02-19 11:07:36 nux.gestures_subscription GesturesSubscription.cpp:364 Failed to set Geis subscription configuration com.canonical.oif.drag.timeout
ERROR 2013-02-19 11:07:36 nux.gestures_subscription GesturesSubscription.cpp:364 Failed to set Geis subscription configuration com.canonical.oif.pinch.threshold
ERROR 2013-02-19 11:07:36 nux.gestures_subscription GesturesSubscription.cpp:364 Failed to set Geis subscription configuration com.canonical.oif.pinch.timeout
ERROR 2013-02-19 11:07:36 nux.gestures_subscription GesturesSubscription.cpp:364 Failed to set Geis subscription configuration com.canonical.oif.tap.threshold
ERROR 2013-02-19 11:07:36 nux.gestures_subscription GesturesSubscription.cpp:364 Failed to set Geis subscription configuration com.canonical.oif.tap.timeout
ERROR 2013-02-19 11:07:36 nux.gestures_subscription GesturesSubscription.cpp:364 Failed to set Geis subscription configuration com.canonical.oif.rotate.threshold
ERROR 2013-02-19 11:07:36 nux.gestures_subscription GesturesSubscription.cpp:364 Failed to set Geis subscription configuration com.canonical.oif.rotate.timeout

Please NOTE that if I leave my computer (Lenovo Thinkpad T500 using the onboard Intel graphics adaptor without any proprietary driver) on for a week or more, just closing the lid when moving, I usually don't have any problems -- even if plugging/unplugging external monitor/projector.
   When I'm rebooting, however, the problems almost certainly will occur. What I've found out is that deleting all compiz logs (which I can do from tty1 before restarting lightdm) seems to fix the problems crashing compiz. I.e. what I do is basically
  1. switch to tty1 and log in as myself
  2. rm -rf ~/.compiz (in order to recursively delete session logs....there might also be ~/compiz-1 and so on --> delete all!)
  3. sudo service lightdm restart
  4. log in using the standard greeter again

Note that this procedure (restarting lightdm) has the negative effect of killing any open applications, including my virtual machines running on top of Ubuntu. Hence, it's a procedure I try to perform just after restarting the computer, since the system seems ...

Fix committed into lp:bamf at revision 551, scheduled for release in bamf, milestone 0.5.0

Thank you for your work.

How can this be invalid for Ubuntu if it was fixed only recently upstream I wonder? Resetting the status. I'd love to see a fix backported to the precise LTS.

Just ignore my last comment (except for the LTS part) ;-) Sorry for the noise.

Rolf, porting this to the LTS is possible, but not that easily since it needs a little of refactoring of libbamf's bamf-view. However, since this seems a quite minor warning, I'd just avoid this for now.

This bug was fixed in the package bamf - 0.5.0daily13.06.19-0ubuntu1

---------------
bamf (0.5.0daily13.06.19-0ubuntu1) saucy; urgency=low

  [ Marco Trevisan (Treviño) ]
  * New upstream release, bumping debian version to 0.5.0
  * LibBamfPrivate: add new private library to share code between client
    and daemon.
  * libbamf, BamfView: Use dbus-properties (both values and signals) It
    allows to have correct values and signals when they get updated.
    Deprecating related dbus methods/signals.
  * debian/control:
    - don't build-depend anymore on libdbus-glib-1-dev

  [ Jeremy Bicha ]
  * debian/control:
    - Have libbamf3-dev depend on gir1.2-bamf-3
    - Drop explicit build-depends on gir1.2-glib-2.0

  [ Ted Gould ]
  * Have bamfdaemon depend on the library instead of vice versa.

  [ Marco Trevisan (Treviño) ]
  * Makefile.am.gtests: kill the launched dbus-daemon after running the
    tests. (LP: #1088696, #1186915)
  * BamfDaemon, LibBamf: Fix compilation errors out from ubuntu. (LP:
    #1186915, #1176524)
  * BamfView: use statically allocated pspec to notify property changes
    BamfFactory: some initial cleanup, remove views that have changed
    their path and use cached children.
  * BamfView: use incremental children caching, delete them only when
    daemon stops Each view used to cleanup the cached children every
    time a new one was added or removed. This was needed at the dbus-
    glib times to handle the case of bamfdaemon restart, but now we can
    handle this nicely, clening the children up only when this happens.
  * BamfView: disconnect proper callback if a bamf-tab is closed I guess
    it was a typo, we need to disconnect to the callback we've been
    connected to before.
  * BamfView: don't try to reload the children if they're empty but we
    already tried once This finally mutes the "Unable to fetch children"
    warning... \o/. (LP: #943083)
  * Bamf: use generic marshallers when creating signals, remove legacy
    bamf-marshal Improvements to the build system, fixed "make
    distcheck" (it was still referencing the old bamf.h file) and
    generation of files when using parallel builds (make -jX).
  * BamfMatcher: If a Window has changed its class, then we try to
    rematch it This is mostly the case of LibreOffice, but if a window
    has changed its class, then we should try to re-match, checking if
    now it can be matched by a new application. If this is the case,
    then we remove the window from the previous application (that may
    eventually be closed) and we add it to the new one. Thanks to this
    we can finally remove a lot of libreoffice-only related code.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 554
 -- Ubuntu daily release <email address hidden> Wed, 19 Jun 2013 02:01:25 +0000

Fix Released in Bamf BAMF 0.5.0.

Is this issue really gone?
I am using Elementary OS which seems to have 0.5.1 BAMF installed.

I have basically the same issues mentioned above:
-> my session freezes.
The only workaround I so far have is to brutally kill gnome-session or restart lightdm.
But both of these workarounds mean I lose all current open applications and have to hope they close cleanly.
As you can imagine this is pretty high priority on my list of "high priority issues".
I have had it since installing Elementary but cannot tell when precisely it occurs - it doesn't happen immediately after login. Possibly connected to hibernation/suspend but also not totally sure about this. It seems though to happen when I haven't been doing anything on my netbook for a while. i.e. this never occurred to me in the middle of me doing something ...
Not sure if this is sufficient information to be going on.
This are the error messages I am getting in .xsession-errors:
Window manager warning: Log level 16: Failed to fetch xid: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.ayatana.bamf.window' on object at path /org/ayatana/bamf/window/48234530
Window manager warning: Log level 16: Unable to fetch children: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.ayatana.bamf.view' on object at path /org/ayatana/bamf/application/1339296950
Window manager warning: Log level 16: Failed to fetch path: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.ayatana.bamf.application' on object at path /org/ayatana/bamf/application/1339296950

I don't see this since a lot of time, it's really nothing to worry
about BTW (just a warning).

It seems like I experienced a similiar error with Ubuntu 17.04 (with i5 3400 and RX 480). I wanted to re-login after the screen was locked. For more than a minute, I could not move the mouse nor switch from x environment to terminal or something like this. After some time, everything just worked fine again.

First, the following appears some times:
Aug 25 14:33:31 reichelt-desktop kernel: [14558.796706] failed to send message 146 ret is 0
Aug 25 14:33:31 reichelt-desktop kernel: [14559.219339]
Aug 25 14:33:31 reichelt-desktop kernel: [14559.219339] failed to send pre message 5d ret is 0
Aug 25 14:33:31 reichelt-desktop kernel: [14559.642303]
Aug 25 14:33:31 reichelt-desktop kernel: [14559.642303] failed to send message 5d ret is 0
Aug 25 14:33:32 reichelt-desktop kernel: [14560.066004]
Aug 25 14:33:32 reichelt-desktop kernel: [14560.066004] failed to send pre message 148 ret is 0

and than a similiar error occured:

Aug 25 14:33:35 reichelt-desktop compiz[2749]: ERROR 2017-08-25 14:33:35 unitynding->source != null <unknown>:0 g_value_set_object: assertion 'g_value_type_compatible (G_OBJECT_TYPE (v_object), G_VALUE_TYPE (value))' failed
Aug 25 14:33:35 reichelt-desktop unity-panel-ser[2771]: Failed to fetch xid: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Keine derartige Schnittstelle »org.ayatana.bamf.window« des Objekts im Pfad /org/ayatana/bamf/window/35651636
Aug 25 14:33:35 reichelt-desktop compiz[2749]: WARN 2017-08-25 14:33:35 unity <unknown>:0 Failed to fetch xid: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Keine derartige Schnittstelle »org.ayatana.bamf.window« des Objekts im Pfad /org/ayatana/bamf/window/35651636
Aug 25 14:33:35 reichelt-desktop unity-panel-ser[2771]: Failed to fetch type: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Keine derartige Schnittstelle »org.ayatana.bamf.window« des Objekts im Pfad /org/ayatana/bamf/window/35651636
Aug 25 14:33:35 reichelt-desktop acpid: input device has been disconnected, fd 16
Aug 25 14:33:35 reichelt-desktop unity-panel-ser[2771]: Failed to fetch monitor: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Keine derartige Schnittstelle »org.ayatana.bamf.window« des Objekts im Pfad /org/ayatana/bamf/window/35651636
Aug 25 14:33:35 reichelt-desktop compiz[2749]: WARN 2017-08-25 14:33:35 unity <unknown>:0 Failed to fetch type: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Keine derartige Schnittstelle »org.ayatana.bamf.window« des Objekts im Pfad /org/ayatana/bamf/window/35651636
Aug 25 14:33:35 reichelt-desktop unity-panel-ser[2771]: Failed to fetch maximized state: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Keine derartige Schnittstelle »org.ayatana.bamf.window« des Objekts im Pfad /org/ayatana/bamf/window/35651636
Aug 25 14:33:35 reichelt-desktop unity-panel-ser[2771]: Failed to fetch xid: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Keine derartige Schnittstelle »org.ayatana.bamf.window« des Objekts im Pfad /org/ayatana/bamf/window/35651636
Aug 25 14:33:35 reichelt-desktop compiz[2749]: WARN 2017-08-25 14:33:35 unity <unknown>:0 Failed to fetch monitor: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Keine derar...