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 594287 - segfault in at-spi-registryd
segfault in at-spi-registryd
Status: RESOLVED OBSOLETE
Product: at-spi
Classification: Platform
Component: at-spi2-core
unspecified
Other Linux
: Normal normal
: ---
Assigned To: At-spi maintainer(s)
At-spi maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-09-06 03:11 UTC by Matthias Clasen
Modified: 2021-07-05 10:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias Clasen 2009-09-06 03:11:19 UTC
Originally filed here: https://bugzilla.redhat.com/show_bug.cgi?id=521413

Core was generated by `/usr/libexec/at-spi-registryd'.
Program terminated with signal 6, Aborted.

Thread 1 (Thread 2072)

  • #0 raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #1 abort
    at abort.c line 92
  • #2 IA__g_assertion_message
  • #3 IA__g_assertion_message_expr
    at gtestutils.c line 1312
  • #4 do_unref
    at orbit-object.c line 159
  • #5 ORBit_RootObject_release
    at orbit-object.c line 200
  • #6 bonobo_object_release_unref
    at bonobo-object.c line 587
  • #7 registry_start_queue
    at registry.c line 815
  • #8 registry_defer_on_event
    at registry.c line 855
  • #9 registry_filter_event
    at registry.c line 905
  • #10 impl_registry_notify_event
    at registry.c line 954
  • #11 ORBit_small_invoke_adaptor
    at orbit-small.c line 846
  • #12 ORBit_POAObject_handle_request
    at poa.c line 1357
  • #13 ORBit_POAObject_invoke_incoming_request
    at poa.c line 1427
  • #14 ORBit_POA_handle_request
    at poa.c line 1649
  • #15 ORBit_handle_request
    at orbit-adaptor.c line 300
  • #16 giop_connection_handle_input
    at giop-recv-buffer.c line 1312
  • #17 link_connection_io_handler
    at linc-connection.c line 1475
  • #18 g_main_dispatch
    at gmain.c line 1960
  • #19 IA__g_main_context_dispatch
    at gmain.c line 2513
  • #20 g_main_context_iterate
    at gmain.c line 2591
  • #21 IA__g_main_loop_run
    at gmain.c line 2799
  • #22 bonobo_main
    at bonobo-main.c line 311
  • #23 main
    at registry-main.c line 113

Comment 1 Li Yuan 2009-11-09 06:20:44 UTC

*** This bug has been marked as a duplicate of bug 578334 ***
Comment 2 André Klapper 2012-02-26 10:40:27 UTC
[Resetting QA Contact to newly introduced "at-spi-maint@gnome.bugs". 
Reason: So far it was impossible to watch changes in at-spi bug reports without following all the specific persons (Li Yuan, Bill Haneman, Jeff Wai, ...) and also their activity outside of at-spi reports.

IMPORTANT: Anyone interested in following all bug activity (including all maintainers) must watch the "at-spi-maint@gnome.bugs" dummy user by adding it to the 'Users to watch' list under Preferences->Email preferences. This is also the default procedure nowadays in GNOME when setting up new products.]
Comment 3 André Klapper 2013-08-14 10:03:07 UTC
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
Comment 4 André Klapper 2018-08-31 09:50:59 UTC
Moving open tickets in at-spi2' "registry" Bugzilla component to "at-spi2-core" as it has a subdir called "registryd".
Comment 5 GNOME Infrastructure Team 2021-07-05 10:44:49 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/

Thank you for your understanding and your help.