After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 348266 - yelp crashes at startup
yelp crashes at startup
Status: RESOLVED OBSOLETE
Product: yelp
Classification: Applications
Component: General
2.15.x
Other Linux
: Normal normal
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-21 16:36 UTC by Matthias Clasen
Modified: 2006-08-05 13:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthias Clasen 2006-07-21 16:36:24 UTC 
It happened a number of times for me; clicking the help button in
the window capplet, and yelp keeps respawning. It also happened
to me when using the Help menuitem.

This is with 2.15.2
Comment 1 Don Scorgie 2006-07-21 18:30:45 UTC 
Hi,

In 2.15.3, we moved to dbus activation (as opposed to bonobo).  Any chance of testing later versions, see if the same is still happening?

What do you mean respawning?  Does the current window close and a new one open, or do new windows keep appearing?

Also, does it happen when run from the command line?  If so, any other output produced?

Thanks
Comment 2 Matthias Clasen 2006-07-21 19:01:05 UTC 
We won't be able to go to 2.15.3 for a while, since we don't have gecko 1.8
in Fedora Core currently. That dependency bump was a bit, ahem, rushed, imo.

Anyway, here is what it said when respawning:

Yelp-ERROR **: Could not activate yelp: 'Race condition activating server 'OAFIID:GNOME_Yelp_Factory''
Comment 3 Don Scorgie 2006-07-22 15:06:47 UTC 
(In reply to comment #2)
> Anyway, here is what it said when respawning:
> 
> Yelp-ERROR **: Could not activate yelp: 'Race condition activating server
> 'OAFIID:GNOME_Yelp_Factory''
> 

Looks like a problem with bonobo.  Possibly the same as bug #343153.  I can't tell entirely though (as #343153 doesn't have the reason for the failure to reach bonobo).
Comment 4 Matthias Clasen 2006-08-05 13:22:38 UTC 
2.15.5 doesn't have this problem anymore (since it switched to dbus).
so this bug can probably be closed now.