at-spi-registryd crashed with SIGSEGV in _SmcProcessMessage()

Bug #420053 reported by Juan Sebastián Marulanda
354
This bug affects 58 people
Affects Status Importance Assigned to Milestone
at-spi
Invalid
Critical
at-spi (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: at-spi

Got this error along others after a hard restart.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Aug 27 11:39:36 2009
Disassembly:
 0x0: $5 = -99
 $6 = 0x0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/at-spi/at-spi-registryd
Package: at-spi 1.27.91-0ubuntu1
ProcCmdline: /usr/lib/at-spi/at-spi-registryd
ProcCwd: /home/richardwolfvi
ProcEnviron:
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-7.27-generic-pae
SegvAnalysis: Failure: Unknown offset literal: -99
Signal: 11
SourcePackage: at-spi
StacktraceTop:
 ?? ()
 _SmcProcessMessage () from /usr/lib/libSM.so.6
 IceProcessMessages () from /usr/lib/libICE.so.6
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
Title: at-spi-registryd crashed with SIGSEGV in _SmcProcessMessage()
Uname: Linux 2.6.31-7-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Juan Sebastián Marulanda (juanchito2006) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
IceProcessMessages (iceConn=0x0, replyWait=0x0,
process_ice_messages (channel=0x8f62f70, condition=G_IO_IN,
g_io_unix_dispatch (source=0x8f62fb8,
IA__g_main_context_dispatch (context=0x8f3b738)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in at-spi (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Steve Beattie (sbeattie)
visibility: private → public
Revision history for this message
josa (johnny-sander) wrote :

This happened twice tonight when loging out. After restarting my computer it seems I can not reproduce it. At least not on the two new tries I did.
Bug #423947

Revision history for this message
josa (johnny-sander) wrote :

Updated bug #423947 with description and backtrace after todays crash as there are new versions involved.
Dare I set this one as duplicate of that?

Revision history for this message
Martin Olsson (mnemo) wrote :

josa created a nice gdb log in his bug report (which is now a dupe of this one):
http://launchpadlibrarian.net/31983751/gdb_at-spi-registryd%20sep%2017%202009.log

Revision history for this message
Martin Olsson (mnemo) wrote :

I was able to repro this two times using these steps (can anyone else confirm?):

1. check the checkbox "System::Preferences::Assistive technologies::Enable Assistive Technologies".
2. wait 10-20 second and then logout using the top-right ubuntu shutdown menu
3. SEGV happens _during_ log out

Revision history for this message
Martin Olsson (mnemo) wrote :

Here is a better gdb trace (with symbols) so we can see the exact line where the crash happens;
it's src/sm_process.c:324.

The offending code is:

    case SM_SaveComplete:

        if (!smcConn->save_yourself_in_progress)
        {
            _IceErrorBadState (iceConn, _SmcOpcode,
                SM_SaveComplete, IceCanContinue);
        }
        else
        {
            CHECK_SIZE_MATCH (iceConn, _SmcOpcode, opcode,
                length, SIZEOF (smSaveCompleteMsg),
                IceFatalToProtocol);

            smcConn->save_yourself_in_progress = False;

            (*smcConn->callbacks.save_complete.callback) (smcConn,
                smcConn->callbacks.save_complete.client_data);
        }
        break;

And the crash happens when the function pointer is called (last statement).

Revision history for this message
Martin Olsson (mnemo) wrote :

I reported upstream as well now:
https://bugzilla.gnome.org/show_bug.cgi?id=596115

Changed in at-spi:
status: Unknown → New
Revision history for this message
Fatih Bostancı (fbostanci) wrote :

i can confirm this bug .. 9.10 beta i386

Revision history for this message
Darcy Casselman (dscassel) wrote :

Got a crash report on startup after doing a safe-upgrade last night.

Revision history for this message
Brian Murray (brian-murray) wrote : Marking as a duplicate

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 437315, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

Changed in at-spi (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

I apologize for the noise here. Bug 437315 should be a duplicate of this one since this bug has an upstream bug task.

Changed in at-spi:
importance: Unknown → Critical
status: New → Unknown
Changed in at-spi (Ubuntu):
status: Confirmed → Triaged
tags: added: a11y
Changed in at-spi:
status: Unknown → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.