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 581308 - crash in Help: yelp crashes on startup
crash in Help: yelp crashes on startup
Status: RESOLVED NOTGNOME
Product: yelp
Classification: Applications
Component: General
2.24.x
Other All
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-04 13:06 UTC by Johannes Rohr
Modified: 2009-05-06 10:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Johannes Rohr 2009-05-04 13:06:34 UTC
Version: 2.24.0

What were you doing when the application crashed?
yelp crashes on startup


Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.24.2

System: Linux 2.6.29-1-686 #1 SMP Fri Apr 17 14:35:16 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10601000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 109780992 vsize: 109780992 resident: 27021312 share: 18194432 rss: 27021312 rss_rlim: 18446744073709551615
CPU usage: start_time: 1241442106 rtime: 45 utime: 40 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6c1c760 (LWP 11126)]
[New Thread 0xb2770b90 (LWP 11130)]
[New Thread 0xb2f71b90 (LWP 11129)]
[New Thread 0xb4928b90 (LWP 11128)]
0xb8029424 in __kernel_vsyscall ()

Thread 2 (Thread 0xb2770b90 (LWP 11130))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/glib/gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/glib/gspawn.c line 694
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 ??
    from /usr/lib/librarian.so.0
  • #8 ??
    from /usr/lib/librarian.so.0
  • #9 ??
    from /usr/lib/librarian.so.0
  • #10 rrn_for_each_in_category
    at rarian-main.c line 93
  • #11 toc_process
    at yelp-toc.c line 474
  • #12 g_thread_create_proxy
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/glib/gthread.c line 635
  • #13 start_thread
    at pthread_create.c line 297
  • #14 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130


----------- .xsession-errors (46 sec old) ---------------------
Unhandled exception in thread started by <bound method MyCache.get_changelog of <UpdateManager.UpdateManager.MyCache object at 0xb620f62c>>
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.5/UpdateManager/UpdateManager.py", line 162, in get_changelog
    section = pkg._depcache.GetCandidateVer(pkg._pkg).Section
AttributeError: 'Package' object has no attribute '_depcache'
Got Event! 100, -1
Got Event! 100, -1
Got Event! 100, -1
Multiple segmentation faults occurred; can't display error dialog
Got Event! 100, -1
Got Event! 100, -1
Got Event! 100, -1
Got Event! 100, -1
Got Event! 100, -1
Got Event! 100, -1
--------------------------------------------------
Comment 1 Gianluca Borello 2009-05-05 11:05:40 UTC
Thanks for taking the time to report this bug.
However, this application does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome.

If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other.
Thanks in advance!
Comment 2 Johannes Rohr 2009-05-05 11:32:51 UTC
(In reply to comment #1)
> Thanks for taking the time to report this bug.
> However, this application does not track its bugs in the GNOME Bugzilla. We
> kindly ask you to report the bug to the application authors.

Hi, please provide a hint, which third party I should turn to.
Comment 3 Gianluca Borello 2009-05-05 11:49:52 UTC
You are right, I apologize.
The bug is in rarian (http://rarian.freedesktop.org/)
You can report this crash on https://bugs.freedesktop.org/