ubuntu-sso-login crashed with SIGSEGV in setEnabled()

[Hanine HAMZIOUI]

This is a duplicate of 947715 but in Unity not Unity 2D.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ubuntu-sso-client 2.99.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Mar 8 18:48:46 2012
ExecutablePath: /usr/lib/ubuntu-sso-client/ubuntu-sso-login
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/lib/ubuntu-sso-client/ubuntu-sso-login
SegvAnalysis:
 Segfault happened at: 0x7f5255cf2955 <QSocketNotifier::setEnabled(bool)+21>: mov 0x40(%rdx),%rdx
 PC (0x7f5255cf2955) ok
 source "0x40(%rdx)" (0x00000040) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ubuntu-sso-client
StacktraceTop:
 setEnabled (enable=true, this=0x1e719c0) at kernel/qsocketnotifier.cpp:293
 QSocketNotifier::setEnabled (this=0x1e719c0, enable=true) at kernel/qsocketnotifier.cpp:284
 ?? () from /usr/lib/python2.7/dist-packages/dbus/mainloop/qt.so
 QMetaObject::activate (sender=0x1e719c0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7ffff1c6db40) at kernel/qobject.cpp:3547
 QSocketNotifier::activated (this=<optimized out>, _t1=10) at .moc/release-shared/moc_qsocketnotifier.cpp:103
Title: ubuntu-sso-login crashed with SIGSEGV in setEnabled()
UpgradeStatus: Upgraded to precise on 2012-03-02 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 pyqtDBusHelper::readSocket (this=0x1c8e2e0, fd=10) at /build/buildd/python-qt4-4.9.1/dbus/dbus.cpp:274
 ?? ()
 ?? ()
 ?? ()

[Robert Roth (evfool)]

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 #943046, 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. Feel free to continue to report any other bugs you may find.