emacs23-x crashed with SIGABRT in kill()

Bug #952141 reported by Janne Kronbäck on 2012-03-11
This bug affects 7 people
Affects Status Importance Assigned to Milestone
emacs23 (Ubuntu)

Bug Description

Sorry, not much to report. Came back to my computer and had a crash-popup.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: emacs23 23.3+1-1ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sun Mar 11 11:42:23 2012
ExecutablePath: /usr/bin/emacs23-x
ProcCmdline: emacs article_form.py
Signal: 6
SourcePackage: emacs23
 kill () at ../sysdeps/unix/syscall-template.S:82
 abort ()
 ?? ()
 ?? ()
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: emacs23-x crashed with SIGABRT in kill()
UpgradeStatus: Upgraded to precise on 2012-03-10 (1 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare vboxusers

 kill () at ../sysdeps/unix/syscall-template.S:82
 abort () at emacs.c:431
 x_connection_closed (dpy=<optimized out>, error_message=0x7fffdea04ab0 "Connection lost to X server `localhost:11.0'") at xterm.c:7921
 x_io_error_quitter (display=0x1027020) at xterm.c:8038
 _XIOError (dpy=0x1027020) at ../../src/XlibInt.c:1618

Changed in emacs23 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

The stacktrace seems to suggest that I've had a ssh -X session that terminated, which is accurate.

Launchpad Janitor (janitor) wrote :

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

Changed in emacs23 (Ubuntu):
status: New → Confirmed
tags: added: quantal running-unity
tags: added: saucy
information type: Private → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers