unity-2d-launcher crashed with SIGSEGV in __run_exit_handlers()

Bug #867512 reported by Serdar Yildiz on 2011-10-04
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-2d (Ubuntu)
Undecided
Unassigned

Bug Description

start up crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-launcher 4.12.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Tue Oct 4 09:44:42 2011
ExecutablePath: /usr/bin/unity-2d-launcher
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: unity-2d-launcher
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ffb5ce397d3 <__run_exit_handlers+67>: mov (%rdx),%rcx
 PC (0x7ffb5ce397d3) ok
 source "(%rdx)" (0xfff6ba4824cd0) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 __run_exit_handlers (status=1, listp=0x7ffb5d1965a8, run_list_atexit=true) at exit.c:50
 __GI_exit (status=<optimized out>) at exit.c:100
 ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: unity-2d-launcher crashed with SIGSEGV in __run_exit_handlers()
UpgradeStatus: Upgraded to oneiric on 2011-09-27 (6 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:1613): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (nautilus:1613): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #859596, 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  Edit
Everyone can see this information.

Other bug subscribers