Ubuntu
yelp package

yelp crashes after clicking on a search result

Bug #468742 reported by Corey B. on 2009-11-01

This bug report is a duplicate of: Bug #220142: Yelp:ERROR:(yelp-document.c:275):yelp_document_cancel_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document)). Edit Remove

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	yelp (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: yelp

When yelp is opened in terminal it shows this:

** (yelp:1976): CRITICAL **: atk_object_set_name: assertion 'name != NULL' failed

** (yelp:1976): CRITICAL **: atk_object_set_name: assertion 'name != NULL' failed
OMF category 'Applications|Other' not recognised, ignoring.
OMF category 'Applications|Other' not recognised, ignoring.
OMF category 'Applications|Other' not recognised, ignoring.

Then when I search for "symbolic links" this shows up:

I/O error : Is a directory
I/O error : Is a directory

Then when I click the first result, it says 'Loading...' in the title bar, but it never loads, then when I click it again, yelp crashes and this shows up in the termainal:

**
Yelp:ERROR:yelp-document.c:275:yelp_document_cancel_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document))
Aborted

I am on a fresh install of Karmic, amd64.

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2009-11-02:

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in yelp (Ubuntu):
importance:	Undecided → Medium
status:	New → Invalid

Revision history for this message

Corey B. (cbodendein) wrote on 2009-11-02:

I did the above-mentioned steps, but I got a message that said:

The problem cannot be reported:

The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes.?field.comment=I did the above-mentioned steps, but I got a message that said:

The problem cannot be reported:

The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes.

I attached the crash.

Corey B. (cbodendein) on 2009-11-02

Changed in yelp (Ubuntu):
status:	Invalid → New

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2009-11-03:

Please do not attach such files to the report, that's no use for us, instead try obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in yelp (Ubuntu):
status:	New → Incomplete

Revision history for this message

Corey B. (cbodendein) wrote on 2009-11-04:

Backtrace Edit (15.7 KiB, text/plain)

Revision history for this message

Craig H (crherrin) wrote on 2009-11-06:

I searched on remote access and clicked on a link. Application was busy for a few minutes and I clicked on link again and application crashed.

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2009-11-12:

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.