GNOME Bugzilla – Bug 163238
Crashed on startup
Last modified: 2005-02-07 07:01:39 UTC
Distribution: Debian 3.1 Package: gnopernicus Severity: normal Version: GNOME2.9.3 unspecified Gnome-Distributor: Ubuntu Synopsis: Crashed on startup Bugzilla-Product: gnopernicus Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: dialog just says gnopernicus exited unexpectedly Steps to reproduce the crash: 1. Start screen reader 2. 3. Expected Results: How often does this happen? Every time Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnopernicus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1223179296 (LWP 5804)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 54233
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-07 10:07 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnopernicus". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was jaypee@hotpop.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces.
Hi, can you reinstall at-spi making shure that your CFLAGS variable is set to CFLAGS='-g' and test gnopernicus again from a terminal? If attach the output from that terminal that appears with the crash, or get a stacktrace with gdb , or both :). This could be a dublicate of bug #162676 but we need to be sure.
Yep looks like a duplicate. here is the last few lines output of #strace gnopernicus gettimeofday({1106663226, 316296}, NULL) = 0 brk(0) = 0x80be000 brk(0x80df000) = 0x80df000 write(2, "\n** ERROR **: file accessible.c:"..., 104 ** ERROR **: file accessible.c: line 495 (spi_accessible_construct): assertion f ailed: (o) aborting... I take it ubuntu needs new libgail, at-spi etc.
Okay, I'll reopen and mark as a duplicate then.
*** This bug has been marked as a duplicate of 162676 ***