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

Bug #873431 reported by Dmitry Shachnev
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
unity-2d (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Unity 2D launcher crashed on exit.

Duplicate: Unity 2D launcher crashes when "Ubuntu" (3D) session is requested, leaving no unity launcher at all. (Perhaps Unity 3D refuses to run on my machine and tries to fallback to 2D?) But it doesn't crash when a "Ubuntu 2D" session is specifically requested at the login screen.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-launcher 4.12.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Thu Oct 13 19:39:24 2011
ExecutablePath: /usr/bin/unity-2d-launcher
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: unity-2d-launcher
ProcEnviron:
 LANGUAGE=ru:en
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 LC_MESSAGES=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x313934 <__run_exit_handlers+68>: mov 0x8(%edx),%edx
 PC (0x00313934) ok
 source "0x8(%edx)" (0x9185ad08) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 __run_exit_handlers (status=1, listp=0x459324, run_list_atexit=true) at exit.c:50
 __GI_exit (status=1) at exit.c:100
 _IceDefaultIOErrorHandler () from /usr/lib/i386-linux-gnu/libICE.so.6
 _IceRead () from /usr/lib/i386-linux-gnu/libICE.so.6
 IceProcessMessages () from /usr/lib/i386-linux-gnu/libICE.so.6
Title: unity-2d-launcher crashed with SIGSEGV in __run_exit_handlers()
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (41 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev nopasswdlogin plugdev sambashare tape video

Revision history for this message
Dmitry Shachnev (mitya57) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __run_exit_handlers (status=1, listp=0x459324, run_list_atexit=true) at exit.c:50
 __GI_exit (status=1) at exit.c:100
 _IceDefaultIOErrorHandler (iceConn=0x87db6a8) at ../../src/error.c:602
 _IceRead (iceConn=0x87db6a8, nbytes=8, ptr=<optimized out>) at ../../src/misc.c:292
 IceProcessMessages (iceConn=0x87db6a8, replyWait=0x0, replyReadyRet=0x0) at ../../src/process.c:151

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity-2d (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity-2d (Ubuntu):
status: New → Confirmed
Revision history for this message
Alan Jenkins (aj504) wrote :

This is happening every time I try to log *in* as "Ubuntu" (i.e. I'm actually requesting Unity 3D). It doesn't happen if I request "Ubuntu 2D" directly.

I don't think it happened originally (earlier today). But I'm not sure why.

I did enable the Orca Screen Reader & switch to gdm, but switching back to lightdm and disabling Orca doesn't seem to help

After Unity has crashed, I'm left with only a window manager + nautilus (on the background); there's actually no way to log out! This should probably be considered a separate bug, although I'm not sure what the best solution would be.

description: updated
Revision history for this message
Gerry Boland (gerboland) wrote :

Hi Alan,
can you tell what window manager you are running when you're logged in as Ubuntu?

FYI, if it helps, you should be able to hit Ctrl+Alt+T to bring up a terminal, and type "gnome-session-quit" to log out.

Revision history for this message
Alan Jenkins (aj504) wrote :

I can't reproduce this now :(.

When I successfully log in as "Ubuntu", I can see compiz is running. (When I run "Ubuntu 2D", I can see that metacity is running). But I didn't notice which was running when the problem was happening.

(And I use a more general & easier to remember recovery method: Alt+SysRq+K).

Revision history for this message
dino99 (9d9) wrote :

This version has expired long time ago, and is no more supported

Changed in unity-2d (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.