Bug 433336 – crash in Help: Distribution: Fedora Cor...

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 433336 - crash in Help: Distribution: Fedora Cor...


Summary:	crash in Help: Distribution: Fedora Cor...


Status:	RESOLVED DUPLICATE of bug 364768

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-04-25 15:35 UTC by ded_mazay
Modified:	2007-05-29 02:22 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description ded_mazay 2007-04-25 15:35:20 UTC

Version: 2.16.0

What were you doing when the application crashed?
Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 145629184 vsize: 0 resident: 145629184 share: 0 rss: 65527808 rss_rlim: 0
CPU usage: start_time: 1177601620 rtime: 0 utime: 550 stime: 0 cutime:522 cstime: 0 timeout: 28 it_real_value: 0 frequency: 5

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208666400 (LWP 4013)]
[New Thread -1256043632 (LWP 4017)]
[New Thread -1245271152 (LWP 4016)]
[New Thread -1211081840 (LWP 4015)]
(no debugging symbols found)
0x00b43402 in __kernel_vsyscall ()

+ Trace 130514

Thread 1 (Thread -1208666400 (LWP 4013))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strcmp
from /lib/libc.so.6
#5 g_str_equal
from /lib/libglib-2.0.so.0
#6 g_cclosure_marshal_VOID__VOID
#7 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#8 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#9 g_main_context_check
from /lib/libglib-2.0.so.0
#10 g_main_loop_run
from /lib/libglib-2.0.so.0
#11 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_cclosure_marshal_VOID__VOID
#13 __libc_start_main
from /lib/libc.so.6
#14 g_cclosure_marshal_VOID__VOID
#0 __kernel_vsyscall
#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strcmp
from /lib/libc.so.6
#5 g_str_equal
from /lib/libglib-2.0.so.0
#6 g_cclosure_marshal_VOID__VOID
#7 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#8 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#9 g_main_context_check
from /lib/libglib-2.0.so.0
#10 g_main_loop_run
from /lib/libglib-2.0.so.0
#11 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_cclosure_marshal_VOID__VOID
#13 __libc_start_main
from /lib/libc.so.6
#14 g_cclosure_marshal_VOID__VOID

Comment 1 palfrey 2007-04-26 10:29:21 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.
Thanks in advance!

Comment 2 Pedro Villavicencio 2007-05-29 02:22:57 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 364768 ***