xkillxkillcompiz crashed with SIGSEGV in xcb_take_socket()

[Jonathan Mounier]

unity is gone trying to get it back

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
Date: Sat Feb 21 21:35:21 2015
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2015-02-21 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: compiz --replace
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd8f0d23963 <xcb_take_socket+19>: mov (%rdi),%edi
 PC (0x7fd8f0d23963) ok
 source "(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 xcb_take_socket () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XFlush () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetSelectionOwner () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: compiz crashed with SIGSEGV in xcb_take_socket()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 xcb_take_socket (c=0x1, return_socket=return_socket@entry=0x7fd8f2a6b210 <return_socket>, closure=closure@entry=0x2cc4950, flags=1, sent=sent@entry=0x7fff752ac8f8) at ../../src/xcb_out.c:284
 require_socket (dpy=0x2cc4950) at ../../src/xcb_io.c:68
 _XFlush (dpy=0x2cc4950) at ../../src/xcb_io.c:511
 _XGetRequest (dpy=dpy@entry=0x2cc4950, type=type@entry=23 '\027', len=len@entry=8) at ../../src/XlibInt.c:1735
 XGetSelectionOwner (dpy=0x2cc4950, selection=0) at ../../src/GetSOwner.c:39

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.