Yelp crashes when trying to open o help topic

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 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.

Chris, please note that apport is known for not catching all crashes, and this is one of those cases.

The gdb log I attached earlier has been obtained according to the recommended Ubuntu way, as described here: https://wiki.ubuntu.com/Backtrace

PS: Please reopen this bug report.

there is no reason apport should not catch crashes, open a bug on apport if it doesn't work, the stacktrace you got has no debug symbol and is of no use

Sebastien - I've just come back to this bug report because I've had a similar experience with another user who isn't getting a crash report with Apport (even though it is enabled). It turns out that Apport doesn't catch SIGABRT, which is what Yelp is terminating with here. I don't know if Apport is meant to catch this or not, so I asked question 33050 to try and clarify it. If it is a bug in Apport, I'll open a bug report as I can reproduce it without fail here. If this is the intended behaviour of Apport, then can we get Victor to submit a stacktrace with debug symbols in to this report if he can still reproduce the crash (using the guide at https://wiki.ubuntu.com/DebuggingProgramCrash - the example is with yelp funnily enough)

could you try to obtain a backtrace following the instructions at [WWW] http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Hello all,

I am having the same trouble with the Gnome Help center yelp (version 2.22.1) as Victor Osadci. Here is what I did:

1. Open the help application via System -> Help and Support

2. Enter the search word 'splash' and hit "Enter".
The search results are (among others) the topic 'Update Manager Manual'
(which is linking to -> file:///usr/share/omf/update-manager/update-manager-C.omf#performance-6)

4. Left-Click on the topic 'Update Manager Manual' and wait a few seconds. The titlebar of yelp displays 'loading ...'

5. Again left-clicking on the topic 'Update Manager Manual'. Yelp crashes. :(

After the crash I checked my /var/crash/ directory in the command line with "ls -al".
It only brings up the entries . and .. (so the directory is empty).

I tried to report a bug from within yelp with Help -> Report a bug which brought me here to launchpad. I then subscribed to this bug report (since it fits my issue with yelp). It was displayed that there would be files attached to the bug report automatically bit there were none.

I am setting the status of this bug report to "New" (hopefully doing the right thing).
If you need more information from my computer (running Ubuntu 8.04), please let me know.

Kind regards, Tobias

did you enable apport as explained before?

>>> did you enable apport as explained before?

As I understood from the posts above Apport collects the crash-files in /var/crash and uploads them to launchpad. Yet after yelp crashes on my computer there are not any files in /var/crash. I have apport installed on my system so it should do something.

Should I do a Backtrace of the crash as described in

-> https://wiki.ubuntu.com/Backtrace

or follow the procedures in

-> https://wiki.ubuntu.com/DebuggingProgramCrash ?

TobiasK - Apport may be installed on your system, but it is not enabled by default. You have to do this manually. To enable it you should hand edit the file "/etc/default/apport" and change "enabled=0" to "enabled=1". You then need to restart Apport by typing the following in to a terminal:

sudo /etc/init.d/apport restart

Follow the procedures in DebuggingProgramCrash (enable the repositories, install the dbgsym packages, etc) then get a Backtrace as described in the other document, thanks.

Chris Coulson - thanks for those hints to get Apport to work.

Right now I am stuck with -> https://wiki.ubuntu.com/DebuggingProgramCrash

I have got everything up to the third topic done (enabling the repositories). I am stuck in Synaptic with installing the debugging symbols package of yelp.
Currently I am running yelp 2.22.1-0ubuntu2.8.04.2
The current debugging symbols package is at version 2.22.1-0ubuntu2.8.04.1 (meaning it is actual 'older' than yelp).
Synaptic doesn't get the dependencies right and won't install the debug symbols (see screenshot of a German Synaptic version). In the command line it's not working, too.

Do you have any further hints?

TobiasK - You're right - there isn't a new enough -dbgsym package in the repository at the moment. I've spoken to Martin Pitt about this and I'll let you know when this is fixed.

Thanks

I'm marking this a duplicate of bug 206162, which has a slightly more complete backtrace of this crash. Thanks