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 377325 - 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-20 08:01 UTC by bugs
Modified: 2006-11-21 18:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bugs 2006-11-20 08:01:39 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: 374104064 vsize: 374104064 resident: 59699200 share: 23392256 rss: 59699200 rss_rlim: -1
CPU usage: start_time: 1164009659 rtime: 164 utime: 142 stime: 22 cutime:2 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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)
0x00002b5b5ec05d4f in ?? ()

+ Trace 87929

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ?? 






Comment 1


André Klapper





          2006-11-20 09:48:48 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:35:15 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 ***