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 405869 - crash in Help: je faisais une recherche...
crash in Help: je faisais une recherche...
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-02-08 19:33 UTC by renaudcm
Modified: 2007-02-09 17:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description renaudcm 2007-02-08 19:33:59 UTC 
Version: 2.16.1

What were you doing when the application crashed?
je faisais une recherche dans le manuel du terminal
bash:


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

Memory status: size: 129159168 vsize: 0 resident: 129159168 share: 0 rss: 46247936 rss_rlim: 0
CPU usage: start_time: 1170963070 rtime: 0 utime: 486 stime: 0 cutime:460 cstime: 0 timeout: 26 it_real_value: 0 frequency: 112

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 -1227397456 (LWP 14020)]
[New Thread -1303549024 (LWP 14028)]
[New Thread -1294750816 (LWP 14027)]
[New Thread -1247495264 (LWP 14022)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 109119

Thread 1 (Thread -1227397456 (LWP 14020))

  • #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


Susana





          2007-02-09 17:06:43 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 issue has already been fixed. Thanks.

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