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 380147 - crash in Help: I was just opening the U...
crash in Help: I was just opening the U...
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-28 14:18 UTC by snaporaz
Modified: 2006-12-14 12:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description snaporaz 2006-11-28 14:18:17 UTC
Version: 2.16.1

What were you doing when the application crashed?
I was just opening the Ubuntu Help Centre.
The crash occurs always


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

Memory status: size: 397881344 vsize: 397881344 resident: 51060736 share: 24076288 rss: 51060736 rss_rlim: -1
CPU usage: start_time: 1164723325 rtime: 84 utime: 78 stime: 6 cutime:1 cstime: 1 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)
0x00002b9c5698dd4f in ?? ()
  • #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-29 00:12:23 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 snaporaz 2006-12-06 10:06:58 UTC
Here is the stack trace after installing yelp-dbgsym:

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

Memory status: size: 401981440 vsize: 401981440 resident: 49876992 share: 24563712 rss: 49876992 rss_rlim: -1
CPU usage: start_time: 1165399347 rtime: 81 utime: 74 stime: 7 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
0x00002b7ed3591d4f in ?? ()
  • #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 3 André Klapper 2006-12-10 20:43:19 UTC
hi snaporaz,
thanks for reproducing this again; unfortunately the stacktrace still is not useful. :-(
can you also install debug packages for glib, gtk+, libgnome and libgnomeui? thanks in advance.
Comment 4 snaporaz 2006-12-12 14:58:32 UTC
Hi 

I'm sorry, but bug buddy is now broken, too.
Well, anyway, when I launch yelp from the CLI, I get:
m*****@k******:~$ yelp

** (yelp:12877): CRITICAL **: AT_SPI_REGISTRY was not started at session startup.

** (yelp:12877): WARNING **: IOR not set.

** ERROR **: Could not locate registry
aborting...
Aborted (core dumped)

I guess this is a duplicate of Ubuntu bug # 73517:
https://launchpad.net/distros/ubuntu/+source/yelp/+bug/73517

Also, should I install -dbg or -dbgsym packages? They conflict with each other.

Thanks.
Comment 5 André Klapper 2006-12-12 15:08:59 UTC
looks related to bug 377079
Comment 6 Don Scorgie 2006-12-12 16:23:57 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.

Andre: For now, yelp is seriously broken in Ubuntu Feisty (bug 377079).  If you come across any yelp bugs with "Distribution: Ubuntu 7.04 (feisty)", they can be marked as dups of bug 377079 (at least until it that bug is fixed).  3 stacktraces have been added to the "Known bug" list, but occasional other ones still sneak through.

snaporaz: (For future reference) -dbg and -dbgsym are equivalent.  It shouldn't matter which package you install.

*** This bug has been marked as a duplicate of 377079 ***
Comment 7 snaporaz 2006-12-14 12:15:44 UTC
After updating the system today, the bug is gone and I cannot reproduce it (fixed?)