unity-greeter crashed with SIGSEGV in start_thread()

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

Bug Description

When I have another monitor connected (or my laptop docked) the greeter crashes at startup and keeps crashing in a loop.
I break the loop by disconnecting the monitor, the greeter starts normally, I plug it back in and the monitor is normally recognized and I can finally login.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-greeter 0.2.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Fri Mar 16 15:34:29 2012
ExecutablePath: /usr/sbin/unity-greeter
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x8050762: mov %eax,0x24(%edx)
 PC (0x08050762) ok
 source "%eax" ok
 destination "0x24(%edx)" (0xaaaaaace) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity-greeter
StacktraceTop:
 ?? ()
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 start_thread () from /lib/i386-linux-gnu/libpthread.so.0
 clone () from /lib/i386-linux-gnu/libc.so.6
Title: unity-greeter crashed with SIGSEGV in start_thread()
UpgradeStatus: Upgraded to precise on 2012-02-13 (31 days ago)
UserGroups:

Revision history for this message
Enver ALTIN (ealtin) 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-i386-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.