unity-greeter crashed with SIGSEGV in start_thread()

Bug #959178 reported by James Tait
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-greeter (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm not sure at exactly which stage of proceedings this crash occurred. I got the notification upon login after rebooting to complete the day's updates.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-greeter 0.2.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 19 10:36:03 2012
ExecutablePath: /usr/sbin/unity-greeter
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x40aff0: mov %eax,0x3c(%rdx)
 PC (0x0040aff0) ok
 source "%eax" ok
 destination "0x3c(%rdx)" (0x0000003c) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity-greeter
StacktraceTop:
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
 clone () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: unity-greeter crashed with SIGSEGV in start_thread()
UpgradeStatus: Upgraded to precise on 2012-01-13 (65 days ago)
UserGroups:

Revision history for this message
James Tait (jamestait) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #942227, so 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.