Can't not recive any command

Same problem for me. I found this problem yesterday.

lgy@lgy-laptop:~$ gnome-do

(Do:7556): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.

(Do:7556): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

(Do:7556): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

(Do:7556): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

(Do:7556): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

(Do:7556): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

(Do:7556): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

......

Environment: Lucid

I'm guessing if a recent upgrade caused this issue, because Do had run smoothly before yesterday.

I'm using Fedora 13 (i686) with Do 0.8.3.1-1. It was working fine until today, but after I reboot post some package updates, it's having the same problem. Running in a terminal will reveal the message:
GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

Additional info: I have Compiz enabled.

Just FYI, here are the package update yum transaction happened prior to the first observation of the problem:

    Updated cifs-utils-4.4-3.fc13.i686
    Update 4.5-2.fc13.i686
    Updated dosbox-0.73-2.fc12.i686
    Update 0.74-1.fc13.i686
    Updated fontpackages-filesystem-1.42-1.fc13.noarch
    Update 1.44-1.fc13.noarch
    Updated gnome-color-manager-2.30.1-1.fc13.i686
    Update 2.30.2-1.fc13.i686
    Updated gvfs-1.6.1-3.fc13.i686
    Update 1.6.2-1.fc13.i686
    Updated gvfs-afc-1.6.1-3.fc13.i686
    Update 1.6.2-1.fc13.i686
    Updated gvfs-archive-1.6.1-3.fc13.i686
    Update 1.6.2-1.fc13.i686
    Updated gvfs-fuse-1.6.1-3.fc13.i686
    Update 1.6.2-1.fc13.i686
    Updated gvfs-gphoto2-1.6.1-3.fc13.i686
    Update 1.6.2-1.fc13.i686
    Updated gvfs-obexftp-1.6.1-3.fc13.i686
    Update 1.6.2-1.fc13.i686
    Updated gvfs-smb-1.6.1-3.fc13.i686
    Update 1.6.2-1.fc13.i686
    Updated ibus-1.3.4-2.fc13.i686
    Update 1.3.5-2.fc13.i686
    Updated ibus-gtk-1.3.4-2.fc13.i686
    Update 1.3.5-2.fc13.i686
    Updated ibus-libs-1.3.4-2.fc13.i686
    Update 1.3.5-2.fc13.i686
    Updated libgnomekbd-2.30.1-1.fc13.i686
    Update 2.30.1-2.fc13.i686
    Updated policycoreutils-2.0.82-18.fc13.i686
    Update 2.0.82-29.fc13.i686
    Updated policycoreutils-gui-2.0.82-18.fc13.i686
    Update 2.0.82-29.fc13.i686
    Updated policycoreutils-python-2.0.82-18.fc13.i686
    Update 2.0.82-29.fc13.i686
    Updated python-2.6.4-25.fc13.i686
    Update 2.6.4-27.fc13.i686
    Updated python-devel-2.6.4-25.fc13.i686
    Update 2.6.4-27.fc13.i686
    Updated python-libs-2.6.4-25.fc13.i686
    Update 2.6.4-27.fc13.i686
    Updated rhythmbox-0.12.8-3.fc13.i686
    Update 0.12.8-4.fc13.i686
    Updated sane-backends-1.0.21-1.fc13.i686
    Update 1.0.21-2.fc13.i686
    Updated sane-backends-libs-1.0.21-1.fc13.i686
    Update 1.0.21-2.fc13.i686
    Updated sudo-1.7.2p6-1.fc13.i686
    Update 1.7.2p6-2.fc13.i686
    Updated telepathy-glib-0.10.5-1.fc13.i686
    Update 0.10.6-1.fc13.i686
    Updated tkinter-2.6.4-25.fc13.i686
    Update 2.6.4-27.fc13.i686

I'm on Fedora 13 as well and have the same problem... I'm pretty sure it started after an update as well, unfortunately I don't remember when it started happening so I can't look up the log.

Just to clarify a little, I get the same "(Do:4778): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed" message with each letter I press while the Do window is open. Running with --debug doesn't show any other errors.

I was using Openbox when it started to happen, then I tried logging through GNOME but still encountered the same problem.

I am on Fedora 13 and have the same symptoms as the others have reported. Definitely triggered by an update, but not sure which.

comparing with my yum log, this are the packages that apear in both, Gaveen Prabhasara's (comment 3) and mine. I'm using the x86_64 version by the way.

fontpackages-filesystem-1.42-1.fc13.noarch
gvfs-1.6.1-3.fc13.i686
gvfs-afc-1.6.1-3.fc13.i686
gvfs-archive-1.6.1-3.fc13.i686
gvfs-fuse-1.6.1-3.fc13.i686
gvfs-gphoto2-1.6.1-3.fc13.i686
gvfs-obexftp-1.6.1-3.fc13.i686
gvfs-smb-1.6.1-3.fc13.i686
ibus-1.3.4-2.fc13.i686
ibus-gtk-1.3.4-2.fc13.i686
ibus-libs-1.3.4-2.fc13.i686
libgnomekbd-2.30.1-1.fc13.i686
policycoreutils-2.0.82-18.fc13.i686
policycoreutils-python-2.0.82-18.fc13.i686
python-2.6.4-25.fc13.i686
python-devel-2.6.4-25.fc13.i686
python-libs-2.6.4-25.fc13.i686
rhythmbox-0.12.8-3.fc13.i686
sane-backends-1.0.21-1.fc13.i686
sane-backends-libs-1.0.21-1.fc13.i686
sudo-1.7.2p6-1.fc13.i686
telepathy-glib-0.10.5-1.fc13.i686
tkinter-2.6.4-25.fc13.i686

I created a new user who was able use Do without any problem, so i think the issue may be on the configuration files.

I got the solution by analyzing the log in Comment 3, Comment 6 and mine :

This is most likely to be caused by latest PPA version of IBUS !

You guys may try kill ibus-daemon, or anything similar,

then Do can receive command again!

So, roll back ibus may be an effective solution......

See:
http://code.google.com/p/ibus/issues/detail?id=960
http://code.google.com/p/ibus/issues/detail?id=968

I am the developer of ibus. In ibus im context, gtk_im_context_filter_keypress works in async mode. It means gtk_im_context_filter_keypress will always return TRUE. And if the ibus imcontext does not handle the key event, it will use gdk_event_put to send the event back to client windows.

I guess the problem is because of gnome-do does not use gtk_im_context_set_client_window to set client window correctly. Please check it.

From lgy0417#8, I rolled back my ibus packages, and gnome-do now seems to work properly. On Fedora 13, I achieved this by:

yum downgrade ibus ibus-libs ibus-gtk

Each package got downgraded to version 1.3.3-1.fc3. I then used yum's versionlock plugin to prevent updates. Works for me.

I realize that the problem might be in gnome-do's input handling, but gnome-do is written in Mono, and I have zero experience in C# or GTK. When I have spare time to learn C# and GTK, I may try checking and debugging the problem, but until then, I'm happy that things seem to work again.

@Daniel Wang: Now it is no longer necessary to lock your ibus version. It seems that the latest PPA ibus-1.3.5.20100622 has fixed this issue~~ It's now running correctly in Ubuntu Lucid. No rolling back is required.

@lgy0417 This seems to work for me too. I added the Ibus 1.3 Dev PPA, did an upgrade and after a reboot Gnome-Do was working once again:

sudo add-apt-repository ppa:ibus-dev/ibus-1.3-lucid
sudo apt-get update && sudo apt-get upgrade

You should see that the latest version of Ibus is now installed on your system. You may find that you also need to install some additional packages if the input methods you usually use are not available. For example ibus-pinyin, ibus-table-wubi etc.

Hopefully this should fix the problem for most people.

@Jonathan Lumb
Glad to know your Do works again. If you wanna try latest version of Ibus, you may add the following PPA:
ppa:shawn-p-huang/ppa

Is there any way Fedora users can get access to an rpm of ibus-1.3.5.20100622? Please correct if I'm wrong, but I don't think we have the option to add PPA's.

Does anyone know where the sources to the fixed package are? Or do you know which patch fixed the bug in ibus?