unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint()

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

Bug Description

Looks like bug #1048131 but I'm running 13.10

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-greeter 13.10.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
Uname: Linux 3.11.0-1-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 13 15:21:40 2013
ExecutablePath: /usr/sbin/unity-greeter
InstallationDate: Installed on 2013-07-05 (38 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=sv_SE.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7fecaf2ad450 <gdk_window_get_type_hint>: mov 0x18(%rdi),%rax
 PC (0x7fecaf2ad450) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-greeter
StacktraceTop:
 gdk_window_get_type_hint () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint()
UpgradeStatus: Upgraded to saucy on 2013-07-06 (38 days ago)
UserGroups:

Revision history for this message
Anders Pamdal (anders-pamdal) 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 #1048131, 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.

information type: 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.