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 124813 - yelp crashes on startup
yelp crashes on startup
Status: RESOLVED DUPLICATE of bug 104609
Product: yelp
Classification: Applications
Component: General
unspecified
Other other
: Normal critical
: ---
Assigned To: Shaun McCance
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2003-10-17 06:35 UTC by Laurence Gonsalves
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Laurence Gonsalves 2003-10-17 06:35:49 UTC
Package: Yelp
Severity: critical
Version: 2.2.0
Synopsis: yelp crashes on startup
Bugzilla-Product: Yelp
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:

yelp crashes on startup


Steps to reproduce the problem:
1. Type "yelp" at command line
2. Hit ENTER
3. Observe


Actual Results:

(yelp:9632): Bonobo-CRITICAL **: file bonobo-running-context.c: line 406
(bonobo_running_context_auto_exit_unref): assertion `object != NULL'
failed

Yelp-ERROR **: Could not activate Yelp: 'Failed to execute yelp-base: 2
(No such file or directory)'
aborting...


Expected Results:

A window with help.


How often does this happen?

Every time I've tried.


Additional Information:

Going to "Help" in Gnome applications (eg: gthumb or Galeon) results in
a dialog that says 'Application "gnome-help"... has crashed due to a
fatal error. (Aborted)'. I assume this is related.



Debugging Information:

Backtrace was generated from '/usr/bin/yelp'

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 1086876416 (LWP 9632)]
0xffffe002 in ?? ()

Thread 1 (Thread 1086876416 (LWP 9632))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 abort
    from /lib/tls/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 yelp_info_init
  • #8 yelp_info_init
  • #9 g_timeout_add
    from /usr/lib/libglib-2.0.so.0
  • #10 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #16 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-17 02:35 -------

Reassigning to the default owner of the component, shaunm@gnome.org.

Comment 1 John Fleck 2003-10-18 01:52:39 UTC
Thanks for the report. This bug has been fixed in the latest release.

*** This bug has been marked as a duplicate of 104609 ***
Comment 2 Laurence Gonsalves 2003-10-18 04:06:39 UTC
Whet version is this fixed in? Are RPMs for it available somewhere?
Comment 3 John Fleck 2003-10-18 16:42:53 UTC
According to the Red Hat bugzilla bug referred to in b.g.o #104609
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=82993), the bug
was actually in gtkhtml2, and was fixed in gtkhtml2-2.2.0-5 round
about last March. The GNOME project doesn't provide RPM's directly
(they tend to be too distro specific for generic RPM's to work very
well) but rpmfind shows several available (http://www.rpmfind.net/).
Comment 4 Laurence Gonsalves 2003-10-21 06:20:41 UTC
Hmmm... that's exactly the version of gtkhtml2 I had installed, so I
suspect that this is actually a separate problem.

I ended up upgrading gtkhtml2 and yelp (as well as a bunch of other
packages) from the NyQuist apt-rpm repository located at
http://people.ecsc.co.uk/~matt/repository.html

That gave me yelp-2.4.1-1 and gtkhtml2-2.4.1-1. Now the problem seems
to be fixed, but I'm not sure which of those upgrades was responsible.