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 376976 - crash in Help:
crash in Help:
Status: RESOLVED DUPLICATE of bug 377079
Product: yelp
Classification: Applications
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-19 12:22 UTC by japes
Modified: 2006-11-21 18:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description japes 2006-11-19 12:22:45 UTC 
Version: 2.16.1

What were you doing when the application crashed?



Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.17.2 2006-11-14 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 100950016 vsize: 0 resident: 100950016 share: 0 rss: 42168320 rss_rlim: 0
CPU usage: start_time: 1163938948 rtime: 0 utime: 148 stime: 0 cutime:98 cstime: 0 timeout: 50 it_real_value: 0 frequency: 2

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 -1228011824 (LWP 4506)]
[New Thread -1279042672 (LWP 4512)]
[New Thread -1270522992 (LWP 4511)]
[New Thread -1247876208 (LWP 4510)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 87686

Thread 1 (Thread -1228011824 (LWP 4506))

  • #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 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #10 ??
  • #0 __kernel_vsyscall 






Comment 1


Christian Kirbach





          2006-11-19 12:24:12 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


Don Scorgie





          2006-11-21 18:43:12 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 377079 ***