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 376623 - crash in Help: I just opened the help f...
crash in Help: I just opened the help f...
Status: RESOLVED DUPLICATE of bug 377568
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-18 11:48 UTC by Mark Junker
Modified: 2006-11-20 23:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
stack trace as produced by bug buddy (810 bytes, text/plain)
2006-11-20 23:25 UTC, Mark Junker
Details
console messages created by yelp and/or bug buddy (6.58 KB, text/plain)
2006-11-20 23:26 UTC, Mark Junker
Details

Description Mark Junker 2006-11-18 11:48:17 UTC
Version: 2.16.1

What were you doing when the application crashed?
I just opened the help file for AisleRiot Solitaire, "Labyrinth" game by clicking on the menu "Help", "Labyrinth". The help shows up but then it immediately crashes.


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

Memory status: size: 442302464 vsize: 442302464 resident: 60743680 share: 22630400 rss: 60743680 rss_rlim: -1
CPU usage: start_time: 1163850319 rtime: 169 utime: 159 stime: 10 cutime:2 cstime: 0 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)
0x00002b52864dcd4f 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 Damien Durand 2006-11-18 12:18:16 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 Mark Junker 2006-11-18 13:54:57 UTC
This is the new stack trace. Sorry that I cannot provide any further information.

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

Memory status: size: 372047872 vsize: 372047872 resident: 56815616 share: 22654976 rss: 56815616 rss_rlim: -1
CPU usage: start_time: 1163857592 rtime: 87 utime: 79 stime: 8 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".
0x00002ab45c21dd4f in ?? ()
  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ??

Comment 3 Don Scorgie 2006-11-20 19:12:22 UTC
Hi,

Unfortunately, the new stacktrace is no better.  Could you please try installing the firefox-dbg package as well as yelp-dgb?

Thanks
Comment 4 Don Scorgie 2006-11-20 19:13:33 UTC
Sorry for the spam.

Could you also try running yelp from the command line, reproducing the error and adding any output from the terminal here?  Thanks.
Comment 5 Mark Junker 2006-11-20 23:25:50 UTC
Created attachment 76950 [details]
stack trace as produced by bug buddy
Comment 6 Mark Junker 2006-11-20 23:26:29 UTC
Created attachment 76951 [details]
console messages created by yelp and/or bug buddy
Comment 7 Mark Junker 2006-11-20 23:27:24 UTC
I installed libgnomeui-0-dbg, firefox-dbg, and yelp-dbg but the stack trace is still the same. I saved the stack trace and the console output as attachment.
Comment 8 Don Scorgie 2006-11-20 23:37:03 UTC
Thanks for the quick response :)

From the console messages:
** (yelp:29502): CRITICAL **: AT_SPI_REGISTRY was not started at session startup.

This is the problem.  Bug #377568 also displays this behaviour, but has a good stacktrace as well.  Marking this as a duplicate.

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 377568 ***