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 331610 - Crash when starting dasher
Crash when starting dasher
Status: RESOLVED DUPLICATE of bug 331484
Product: at-spi
Classification: Platform
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: bill.haneman
bill.haneman
Depends on:
Blocks:
 
 
Reported: 2006-02-17 21:49 UTC by Vincent Untz
Modified: 2006-02-20 14:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vincent Untz 2006-02-17 21:49:10 UTC 
This crash happened when testing GNOME 2.13.91.

This error was printed on the terminal: ** ERROR **: AT-SPI error: during registry activation: Impossible de cloner un nouveau processus:L'exécution du processus fils « /usr/libexec/at-spi-registryd » a échoué (Aucun fichier ou répertoire de ce type)

Backtrace was generated from '/gnome/releases/usr/libexec/Dasher'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225795904 (LWP 24491)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 66284

Thread 1 (Thread -1225795904 (LWP 24491))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 792
  • #3 <signal handler called>
  • #4 IA__g_logv
    at gmessages.c line 503
  • #5 IA__g_log
    at gmessages.c line 517
  • #6 cspi_init
    at cspi-bonobo.c line 141
  • #7 SPI_init
    at spi_main.c line 382
  • #8 main
    at main.cc line 211
  • #0 __kernel_vsyscall 






Comment 1


bill.haneman





          2006-02-20 14:33:12 UTC
        



Caused because the Accessibility_Registry.server file has a hard-coded path, due to not being properly regenerated during the build process.

*** This bug has been marked as a duplicate of 331484 ***