Bug 568832 – crash in Help: starting yelp

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 568832 - crash in Help: starting yelp


Summary:	crash in Help: starting yelp


Status:	RESOLVED INCOMPLETE

Product:	yelp
Classification:	Applications
Component:	General
Version:	2.24.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Yelp maintainers
QA Contact:	Yelp maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-01-23 12:45 UTC by ganto82
Modified:	2009-01-23 13:01 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description ganto82 2009-01-23 12:45:18 UTC

Version: 2.24.0

What were you doing when the application crashed?
starting yelp


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.24.3 2009-01-17 (Gentoo)
BugBuddy Version: 2.24.2

System: Linux 2.6.28-gentoo #1 SMP Fri Jan 16 21:10:52 CET 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 445739008 vsize: 445739008 resident: 45002752 share: 27045888 rss: 45002752 rss_rlim: 18446744073709551615
CPU usage: start_time: 1232714543 rtime: 113 utime: 73 stime: 40 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f835b4017b0 (LWP 19217)]
[New Thread 0x4394a950 (LWP 19223)]
[New Thread 0x43149950 (LWP 19221)]
[New Thread 0x42948950 (LWP 19220)]
[New Thread 0x41073950 (LWP 19219)]
[New Thread 0x42147950 (LWP 19218)]
(no debugging symbols found)
0x00007f8350f85146 in poll () from /lib/libc.so.6

+ Trace 211792

Thread 2 (Thread 0x4394a950 (LWP 19223))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 ??
from /usr/lib/librarian.so.0
#6 ??
from /usr/lib/librarian.so.0
#7 rrn_info_get_categories
from /usr/lib/librarian.so.0
#8 toc_process_info
#9 ??
from /usr/lib/libglib-2.0.so.0
#10 start_thread
from /lib/libpthread.so.0
#11 clone
from /lib/libc.so.6
#12 ??



----------- .xsession-errors (1832 sec old) ---------------------

SWFDEC: ERROR: swfdec_stream.c(373): swfdec_stream_errorv: error in stream for unknown url: Network error
SWFDEC: ERROR: swfdec_stream.c(373): swfdec_stream_errorv: error in stream for unknown url: Network error
snd_pcm_writei failed: Broken pipe
snd_pcm_writei failed: Broken pipe
SWFDEC: ERROR: swfdec_stream.c(373): swfdec_stream_errorv: error in stream for unknown url: Network error
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4600004 (System Mon); these messages lack timestamps and therefore suck.
--------------------------------------------------

Comment 1 Christoph Wurm 2009-01-23 13:01:57 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!