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 417958 - crash in Help: Did a search
crash in Help: Did a search
Status: RESOLVED DUPLICATE of bug 364768
Product: yelp
Classification: Applications
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-13 18:50 UTC by kja002
Modified: 2007-03-14 21:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description kja002 2007-03-13 18:50:41 UTC
Version: 2.16.1

What were you doing when the application crashed?
Did a search


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

Memory status: size: 128937984 vsize: 0 resident: 128937984 share: 0 rss: 31035392 rss_rlim: 0
CPU usage: start_time: 1173811795 rtime: 0 utime: 220 stime: 0 cutime:200 cstime: 0 timeout: 20 it_real_value: 0 frequency: 8

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 -1227979088 (LWP 5957)]
[New Thread -1316242528 (LWP 5970)]
[New Thread -1307849824 (LWP 5969)]
[New Thread -1299457120 (LWP 5968)]
[New Thread -1291064416 (LWP 5967)]
[New Thread -1281967200 (LWP 5960)]
[New Thread -1232057440 (LWP 5959)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227979088 (LWP 5957))

  • #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 Christian Kirbach 2007-03-14 21:59:19 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 ***