compiz crashed with SIGSEGV

Bug #1163039 reported by userDepth
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
New
Undecided
Unassigned

Bug Description

I inserted a 32 gb Kingston 101 G2 and Compiz crashed. It is formated in NTFS.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: compiz-core 1:0.9.9~daily13.03.29-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Apr 1 18:33:12 2013
Disassembly: => 0x71: Cannot access memory at address 0x71
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
DpkgLog:

ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:035c]
InstallationDate: Installed on 2013-03-29 (3 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
MachineType: Acer Aspire 5820T
MarkForUpload: True
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-15-generic root=UUID=8095aa5e-f4e8-4551-97f0-58f173075b54 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x71: Cannot access memory at address 0x71
 PC (0x00000071) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: compiz
Stacktrace:
 #0 0x0000000000000071 in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()
Title: compiz crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 09/08/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: V1.19
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: ZR7B
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrV1.19:bd09/08/2010:svnAcer:pnAspire5820T:pvrV1.19:rvnAcer:rnZR7B:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire 5820T
dmi.product.version: V1.19
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.9~daily13.03.29-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.43-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1
xserver.bootTime: Mon Apr 1 18:29:45 2013
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.3-0ubuntu4
xserver.video_driver: intel

Revision history for this message
userDepth (binarydepth) wrote :
information type: Private → Public
Revision history for this message
Sami Jaktholm (sjakthol) wrote :

I believe this is a duplicate of bug 1161916 which has been fixed since. Please log a new bug if the problem persists. Thanks for reporting this one!

Revision history for this message
userDepth (binarydepth) wrote :

This was fixed. Is not happening in version daily13.04.18.1~13.04-0ubuntu1

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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