Bug 376701 – crash in Help: search

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 376701 - crash in Help: search


Summary:	crash in Help: search


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:	2006-11-18 16:42 UTC by edgar_yu
Modified:	2006-11-18 16:59 UTC

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

Description edgar_yu 2006-11-18 16:42:08 UTC

Version: 2.16.1

What were you doing when the application crashed?
search				


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 195530752 vsize: 0 resident: 195530752 share: 0 rss: 59731968 rss_rlim: 0
CPU usage: start_time: 1163867940 rtime: 0 utime: 1666 stime: 0 cutime:1584 cstime: 0 timeout: 82 it_real_value: 0 frequency: 91

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227819344 (LWP 4903)]
[New Thread -1328182368 (LWP 5038)]
[New Thread -1302287456 (LWP 4908)]
[New Thread -1232086112 (LWP 4905)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 87482

Thread 1 (Thread -1227819344 (LWP 4903))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strcmp
from /lib/tls/i686/cmov/libc.so.6
#5 g_str_equal
from /usr/lib/libglib-2.0.so.0
#6 ??
#7 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-11-18 16:59:39 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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