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 380698 - crash in Help: Just started yelp and. h...
crash in Help: Just started yelp and. h...
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-29 23:37 UTC by Christian Hamar
Modified: 2006-11-30 14:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Christian Hamar 2006-11-29 23:37:41 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Just started yelp and. hm. It crashed :)

btw in console i see that:

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

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

** ERROR **: Could not locate registry
aborting...

I'm not sure that it is a 'local' distro problem or a yelp one :) (yep yelp compiled against right firefox, nspr,nss version)

Regards

Christian Hamar alias krix
Hungary
Frugalware Development Team



Distribution: Unknown
Gnome Release: 2.17.2 2006-11-07 (Frugalware)
BugBuddy Version: 2.16.0

Memory status: size: 329281536 vsize: 329281536 resident: 46211072 share: 22106112 rss: 46211072 rss_rlim: -1
CPU usage: start_time: 1164843414 rtime: 94 utime: 78 stime: 16 cutime:3 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)
[Thread debugging using libthread_db enabled]
[New Thread 47435533059440 (LWP 5510)]
[New Thread 1124096320 (LWP 5519)]
[New Thread 1115703616 (LWP 5518)]
[New Thread 1107310912 (LWP 5517)]
[New Thread 1098918208 (LWP 5516)]
[New Thread 1090525504 (LWP 5512)]
[New Thread 1082132800 (LWP 5511)]
(no debugging symbols found)
0x00002b246f915a1f in waitpid () from /lib/libpthread.so.0

+ Trace 90416

Thread 1 (Thread 47435533059440 (LWP 5510))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_segv_handle
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib64/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib64/libglib-2.0.so.0
  • #7 spi_atk_bridge_do_registration
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #8 atk_bridge_init
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #9 gnome_accessibility_module_init
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #10 NSGetModule
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #11 NSGetModule
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #12 NSGetModule
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #13 NSGetModule
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #14 NSGetModule
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #15 NSGetModule
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #16 NSGetModule
    from /usr/lib/firefox-2.0/components/libaccessibility.so
  • #17 EmbedPrivate::GetAtkObjectForCurrentDocument
    from /usr/lib/firefox-2.0/libgtkembedmoz.so
  • #18 nsIDOMMouseEvent::GetIID
  • #19 g_timeout_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #21 g_main_context_iterate
    from /usr/lib64/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #24 nsIDOMMouseEvent::GetIID
  • #25 __libc_start_main
    from /lib/libc.so.6
  • #26 ??
  • #27 ??
  • #28 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Daniel Holbach





          2006-11-30 14:55: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 ***