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 377086 - crash in Help: started sytem->help
crash in Help: started sytem->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 18:26 UTC by endrejat
Modified: 2006-11-20 19:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description endrejat 2006-11-19 18:26:13 UTC
Version: 2.16.1

What were you doing when the application crashed?
started sytem->help


Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:36:14 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled
----------- .xsession-errors ---------------------
** (yelp:3973): WARNING **: IOR not set.
** ERROR **: Could not locate registry
aborting...
** (bug-buddy:3981): WARNING **: Couldn't load icon for Open Folder
** (yelp:4001): CRITICAL **: AT_SPI_REGISTRY was not started at session startup.
** (yelp:4001): WARNING **: IOR not set.
** ERROR **: Could not locate registry
aborting...
** (bug-buddy:4009): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 120070144 vsize: 0 resident: 120070144 share: 0 rss: 45686784 rss_rlim: 0
CPU usage: start_time: 1163960642 rtime: 0 utime: 146 stime: 0 cutime:136 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0

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)
[Thread debugging using libthread_db enabled]
[New Thread -1208138016 (LWP 4001)]
[New Thread -1242219632 (LWP 4007)]
[New Thread -1231729776 (LWP 4003)]
[New Thread -1210238064 (LWP 4002)]
(no debugging symbols found)
0x00981402 in __kernel_vsyscall ()

Thread 1 (Thread -1208138016 (LWP 4001))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #10 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #11 gnome_accessibility_module_init
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #12 ??
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #13 ??
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #14 ??
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #15 ??
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #16 ??
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #17 ??
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #18 ??
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #19 gtk_moz_embed_get_title
    from /usr/lib/firefox-2.0/libgtkembedmoz.so
  • #20 gtk_moz_embed_new
    from /usr/lib/firefox-2.0/libgtkembedmoz.so
  • #21 gtk_widget_get_accessible
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 g_cclosure_marshal_VOID__VOID
  • #23 g_source_get_current_time
    from /lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #25 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 g_cclosure_marshal_VOID__VOID
  • #29 __libc_start_main
    from /lib/libc.so.6
  • #30 g_cclosure_marshal_VOID__VOID
  • #0 __kernel_vsyscall

Comment 1 Don Scorgie 2006-11-20 19:07:49 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 ***