Comment 36 for bug 213494

Revision history for this message
Radu Cristescu (radu.c) wrote : Re: [Hardy] Glipper dies when desktop starting

Hmm... looks like the message trail for this bug entry treats two bugs:
- one about glipper having trouble reading stuff from a .glipper directory after upgrading (which has nothing to do with gnome panel, as you have to delete the .glipper directory for things to work out) -- looks like what is being said in the description; and
- another about glipper starting up (which I tied to gnome panel rather than being glipper's fault, because it works if you log out and then log back in without deleting the .glipper directory, yet adding a small(!) delay at the top of the script) -- which is mentioned when the time.sleep(8) workaround is suggested;

At first I had the first issue, deleted the .glipper directory, and the problem was solved forever. Then the second mentioned issue crawled in.

I renamed /usr/lib/glipper/glipper to glipper.real and put a bash script named glipper in its place, which looks like this:

#!/bin/bash
exec 1> >(tee /tmp/glipper.out) 2> >(tee /tmp/glipper.err)
exec /usr/lib/glipper/glipper.real "$@"

So now I have this text in both glipper.out and glipper.err:

 Bonobo-Activation-ERROR **: This process has not registered the required OAFIID your source code should register 'OAFIID:Glipper_Factory'. If your code is performing delayed registration and this message is trapped in error, see bonobo_activation_idle_reg_check_set.
 aborting...

With glipper.out also having a line saying "SHARED_DATA_DIR: /usr/share/glipper" before this message.

And there's no stack trace in any of those files. Unless glipper is killed because of its failure to start (on grounds that failure cannot be tolerated perhaps), a stack trace should show up if one was printed by python.

So I logged out, logged back in, glipper started this time, and I have the "normal" messages in glipper.out and glipper.err:

** (glipper.real:6500): WARNING **: Binding '<Ctrl><Alt>v' failed!

which is normal, because I have that combination bound to something else.

Sorry for turning the bug comments into a forum if I'm not supposed to do so, but it seems to me that something's not right with this entry, and debate about what should happen to it (possibly split it? send part of it to gnome-panel?).

Wish I knew that that Bonobo error meant, so I could dig deeper before posting something to gnome-panel.