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

Bug #978208 reported by Jos
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-sso-client (Ubuntu)
New
Undecided
Unassigned

Bug Description

Occures after login
Upgrading from 11.10, using gnome-classic

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ubuntu-sso-client 2.99.92-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0-0ubuntu5
Architecture: amd64
Date: Tue Apr 10 19:31:13 2012
ExecutablePath: /usr/lib/ubuntu-sso-client/ubuntu-sso-login
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
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=fr_FR.UTF-8
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ubuntu-sso-client
Title: ubuntu-sso-login crashed with SIGSEGV in QSocketNotifier::setEnabled()
UpgradeStatus: Upgraded to precise on 2012-04-10 (0 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare vboxusers

Revision history for this message
Jos (namjos) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Brian Murray (brian-murray) wrote :

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. Please continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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