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

[surasit]

top left icon missed

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ubuntu-sso-client 2.99.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Wed Mar 14 01:22:34 2012
ExecutablePath: /usr/lib/ubuntu-sso-client/ubuntu-sso-login
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/lib/ubuntu-sso-client/ubuntu-sso-login
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ffa5716e955 <_ZN15QSocketNotifier10setEnabledEb+21>: mov 0x40(%rdx),%rdx
 PC (0x7ffa5716e955) 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:
 QSocketNotifier::setEnabled(bool) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/python2.7/dist-packages/dbus/mainloop/qt.so
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 QSocketNotifier::activated(int) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 QSocketNotifier::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
Title: ubuntu-sso-login crashed with SIGSEGV in QSocketNotifier::setEnabled()
UpgradeStatus: Upgraded to precise on 2012-03-12 (1 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 pyqtDBusHelper::readSocket (this=0x20317c0, fd=9) 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.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad