ubuntu-sso-login crashed with SIGSEGV in QSocketNotifier::setEnabled()
Bug #977977 reported by
Cristian Aravena Romero
This bug report is a duplicate of:
Bug #943046: ubuntu-sso-login crashed with SIGSEGV in QSocketNotifier::setEnabled().
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-sso-client (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Start Ubuntu and crash.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ubuntu-sso-client 2.99.92-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu5
Architecture: amd64
Date: Tue Apr 10 08:53:00 2012
ExecutablePath: /usr/lib/
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: python /usr/lib/
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ubuntu-sso-client
Title: ubuntu-sso-login crashed with SIGSEGV in QSocketNotifier
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Revision history for this message
| Cristian Aravena Romero (caravena) wrote | #1 |
Revision history for this message
| Apport retracing service (apport) wrote Stacktrace.txt | #3 |
Revision history for this message
| Apport retracing service (apport) wrote StacktraceTop.txt | #4 |
Revision history for this message
| Apport retracing service (apport) wrote ThreadStacktrace.txt | #5 |
| tags: | added: apport-failed-retrace |
| tags: | removed: need-amd64-retrace |
| visibility: | private → public |
Revision history for this message
| Brian Murray (brian-murray) wrote | #6 |
To post a comment you must log in.
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.