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

Bug #943046 reported by Rainer Rohde on 2012-02-29
This bug affects 178 people
Affects Status Importance Assigned to Milestone
ubuntu-sso-client (Ubuntu)
High
Ubuntu One Client Engineering team
Precise
High
Ubuntu One Client Engineering team

Bug Description

Crashed shortly after logging in...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ubuntu-sso-client 2.99.5-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 28 20:45:12 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
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7feb08a3f955 <_ZN15QSocketNotifier10setEnabledEb+21>: mov 0x40(%rdx),%rdx
 PC (0x7feb08a3f955) 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-01-31 (28 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Rainer Rohde (rainer-rohde) wrote :
visibility: private → public

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

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-sso-client (Ubuntu):
status: New → Confirmed
Changed in ubuntu-sso-client (Ubuntu):
importance: Undecided → High
tags: added: rls-mgr-p-tracking
Changed in ubuntu-sso-client (Ubuntu Precise):
assignee: nobody → Ubuntu One Desktop+ team (ubuntuone-desktop+)
David Duffey (dduffey) wrote :

Besides getting the crash dialog, this bug did not appear to affect my normal workflow.

I have not seen the issue arise again (since March 14th)

David

On 24/03/12 06:10, David Duffey wrote:
> I have not seen the issue arise again (since March 14th)
likewise

cliff tinker (cliff5555) wrote :

I have encountered this only once so far when i reported it
--
John Clifford Tinker

On Mon, 2012-03-26 at 00:45 +0000, Chris Petrov wrote:

> On 24/03/12 06:10, David Duffey wrote:
> > I have not seen the issue arise again (since March 14th)
> likewise
>

tags: added: bugpattern-written
Alejandro J. Cura (alecu) wrote :

This is a duplicate of bug #334757. The pyqt bindings as used in the new version of ubuntu-sso-client are crashing in the same way as they crash in said pyqt bug when the dbus connection is interrupted.

To post a comment you must log in.