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 343888 - Can't stay up more than 10s without segfault.
Can't stay up more than 10s without segfault.
Status: RESOLVED DUPLICATE of bug 334408
Product: yelp
Classification: Applications
Component: General
2.14.x
Other other
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2006-06-05 09:42 UTC by Lionel Elie Mamane
Modified: 2006-06-05 12:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Lionel Elie Mamane 2006-06-05 09:43:32 UTC 
Distribution: Debian testing/unstable
Package: Yelp
Severity: major
Version: GNOME2.14.2 2.14.x
Gnome-Distributor: Debian
Synopsis: Can't stay up more than 10s without segfault.
Bugzilla-Product: Yelp
Bugzilla-Component: general
Bugzilla-Version: 2.14.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:

segfault

Steps to reproduce the crash:
1. Start yelp, whether directly or through a Gnome app's help menu.
2. If it hasn't crashed yet, click on a link / an entry in the left-hand
outline
3. If it still hasn't crashed, scroll, switch focus to another
application, ...

Expected Results:

Permit me to read the documentation.

How often does this happen?

every time
Additional Information:



Debugging Information:

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 47992768847088 (LWP 9591)]
[New Thread 1098918240 (LWP 9594)]
[New Thread 1090525536 (LWP 9593)]
[New Thread 1082132832 (LWP 9592)]
0x00002ba62b19e3a9 in waitpid () from /lib/libpthread.so.0

+ Trace 68651

Thread 1 (Thread 47992768847088 (LWP 9591))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 CORBA_free
    from /usr/lib/libORBit-2.so.0
  • #4 ORBit_free_T
    from /usr/lib/libORBit-2.so.0
  • #5 ORBit_free
    from /usr/lib/libORBit-2.so.0
  • #6 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #7 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #8 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 atk_object_notify
    at atkobject.c line 1341
  • #12 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_object_interface_list_properties
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_object_notify
    from /usr/lib/libgobject-2.0.so.0
  • #18 GetSecurityContext
    from /usr/lib/libxul.so.0d
  • #19 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #20 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #23 yelp_html_printf
  • #24 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #28 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #29 main
  • #0 waitpid
    from /lib/libpthread.so.0 




------- Bug created by bug-buddy at 2006-06-05 09:42 -------
Comment 1 Sergej Kotliar 2006-06-05 12:15:01 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 334408 ***