unity_support_test crashed with SIGSEGV

[Thomas Ankcorn]

not too sure... compiz just crashed while using ubuntu 11.10 running additional drivers, gwibber and the software center

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nux-tools 1.2.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic i686
Architecture: i386
BootLog:
 fsck from util-linux 2.19.1
 /dev/sda7: clean, 164195/2555904 files, 1021946/10210560 blocks
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
CompositorRunning: None
Date: Fri Aug 19 22:57:31 2011
DistUpgraded: Log time: 2011-08-19 21:56:02.812343
DistroCodename: oneiric
DistroVariant: ubuntu
DkmsStatus: nvidia-current-updates, 280.13, 3.0.0-8-generic, i686: installed
ExecutablePath: /usr/lib/nux/unity_support_test
GraphicsCard: nVidia Corporation GT218 [GeForce 8400 GS] [10de:10c3] (rev a2) (prog-if 00 [VGA controller])
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
MachineType: eveshamvale MS-7133
ProcCmdline: /usr/lib/nux/unity_support_test
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(cususername, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-8-generic root=UUID=d213d6ff-4e3f-46dd-ad23-33a1824853ec ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x8048eaa: movzbl (%esi,%eax,1),%ebx
 PC (0x08048eaa) ok
 source "(%esi,%eax,1)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
Stacktrace:
 #0 0x08048eaa in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfdfd8ec
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 769):
 #0 0x08048eaa in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfdfd8ec
Title: unity_support_test crashed with SIGSEGV
UnitySupportTest:
 Error: command ['/usr/lib/nux/unity_support_test', '-p'] failed with exit code -11: Xlib: extension "GLX" missing on display ":0".
 Xlib: extension "GLX" missing on display ":0".
 Xlib: extension "GLX" missing on display ":0".
UpgradeStatus: Upgraded to oneiric on 2011-08-19 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/28/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.0B6
dmi.board.name: MS-7133
dmi.board.vendor: eveshamvale
dmi.board.version: 100
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: eveshamvale
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.0B6:bd03/28/2005:svneveshamvale:pnMS-7133:pvr100:rvneveshamvale:rnMS-7133:rvr100:cvneveshamvale:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7133
dmi.product.version: 100
dmi.sys.vendor: eveshamvale
version.compiz: compiz 1:0.9.5.0-0ubuntu5
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 7.11-0ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

[Apport retracing service (apport)]

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 #810182, 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.