yelp crashed with SIGSEGV in rrn_info_get_categories()

Bug #433504 reported by Edgar Cherkasov
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
yelp (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: yelp

Yelp crashed on starting

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/yelp
NonfreeKernelModules: nvidia
Package: yelp 2.25.1-0ubuntu5
ProcCmdline: yelp
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: yelp
StacktraceTop:
 ?? () from /usr/lib/librarian.so.0
 ?? () from /usr/lib/librarian.so.0
 rrn_info_get_categories () from /usr/lib/librarian.so.0
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
Title: yelp crashed with SIGSEGV in rrn_info_get_categories()
Uname: Linux 2.6.28-15-generic i686
UserGroups: adm admin cdrom dialout kqemu lpadmin plugdev sambashare

Revision history for this message
Edgar Cherkasov (edgar2705) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? () from /usr/lib/librarian.so.0
?? () from /usr/lib/librarian.so.0
rrn_info_get_categories () at rarian-info.c:612
toc_process_info (toc=0x8bb60b0) at yelp-toc.c:756
g_thread_create_proxy (data=0x900d8c8)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in yelp (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file 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
Pedro Villavicencio (pedro) wrote :

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

Changed in yelp (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
K. Deniz Ogut (kdenizogut) wrote :

Today I experienced a similar (maybe same) problem with my new Maverick installation which is a Web upgrade install from Lucid. I was not using the Lucid installation on that drive much, so I have no idea if the problem was there during Lucid era, but then I logged in my Karmic installation and experienced the bug. I have no clue when it started for my Karmic installation. So first I am sending this additional info. At the moment I can't create apport reports for some reason on that Maverick installation. I'll make a fresh install of Maverick over my Karmic installation and check for the behaviour of yelp again. For there will be no chance to check for my Karmic installation again, I'm now attaching the file created by Apport.

Note: Both Karmic and Maverick installations are Turkish locale

Changed in yelp (Ubuntu):
status: Invalid → New
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

I am experiencing this bug as well (yelp package version 2.30.1-0ubuntu1), on an Lubuntu Maverick amd64 system. This system was created by installing the lubuntu-desktop package on an existing Xubuntu Maverick amd64 system (so xubuntu-desktop is installed too), which was itself upgraded from Xubuntu Lucid amd64. So my system is much like K. Deniz Ogut's system--both systems are running Maverick, upgraded from Lucid.

(In case it's relevant: I also have the ubuntu-desktop package installed, so that I can use the standard GNOME interface from time to time.)

My locale is US English (UTF-8). It does not seem that this bug is locale-dependent.

If requested, I will attach crash data produced by Apport.

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

This bug appears similar to Bug 644025, except that in that bug, yelp loads (but displays "invalid" characters), and then crashes when the home button is clicked. (Inspection of the stack traces reveals the possible similarity.)

This bug (and that one) also appear similar to the old bug 375986. That bug is filed against the package rarian, which provides /usr/lib/librarian.so.0 (see this bug's stack trace). Since that old bag appears to be fixed, my guess is that this is not (quite) the same as that.

(I'll go ahead and comment on those other two bugs to indicate the similarity.)

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

I have found that I only experience this bug when I run yelp with no arguments. If I run yelp with arguments (e.g. "yelp ghelp:user-guide"), this crash does not occur. Perhaps this bug is related to yelp's attempt to render the yelp main page (which might explain the similar crash documented in Bug 644025, where yelp displays "invalid" characters before crashing).

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

@K. Deniz Ogut: Do you also experience this problem only when running yelp with no arguments? (One way of running it with no arguments is System > Help and Support in a standard Ubuntu desktop session.)

Or do you also experience it when you run help with arguments? (One way of running it with arguments is System > About Ubuntu in a standard Ubuntu desktop session -- that passes the command-line argument "ghelp:about-ubuntu".)

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

To add to comment #9: As In Bug 644025, if I run yelp with no arguments and then I click the home button, I get the crash also. So my experience is the same as Phillip Susi's experience in Bug 644025, except that I don't see any "invalid" characters first -- yelp works fine, except when I view the main page, and then it crashes.

Is this your experience as well, K. Deniz Ogut?

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

I have just found that, in addition to the above, I experience this bug when trying to open info pages with yelp. On my system, the following succeeds:

yelp ghelp:user-guide
yelp man:gcc

But the following fails, producing this crash:

yelp
yelp info:gcc

(This is with gcc-doc installed...though when I installed it via apt-get, it did say "The package gcc-doc should be rebuilt with new debhelper to get trigger support". I'm not saying that's relevant. I'm just not sure.)

Revision history for this message
K. Deniz Ogut (kdenizogut) wrote :

@Eliah Kagan for comment #10
Sorry for the very late answer:
Yes, I also experience this problem only when running yelp with no arguments. With arguments -as you have told- I can view it without crash.

Revision history for this message
K. Deniz Ogut (kdenizogut) wrote :

@Eliah Kagan for comment #11
Same here: If I start Yelp with arguments, its OK but then if I click on the home button, it crashes.

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

It seems to be the same bug then.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Oneiric Ocelot. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Changed in yelp (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for yelp (Ubuntu) because there has been no activity for 60 days.]

Changed in yelp (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.