compiz crashed with SIGSEGV in calloc()

Bug #935817 reported by naamlose
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I was trying to active "Paint fire on the Screen" and then I got this problem.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
Uname: Linux 3.2.0-16-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sat Feb 18 17:16:03 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120201.1)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=es_CO:es
 PATH=(custom, no user)
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb740cef6: mov %esi,0x8(%ebp)
 PC (0xb740cef6) ok
 source "%esi" ok
 destination "0x8(%ebp)" (0x0220000e) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 calloc () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_malloc0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: compiz crashed with SIGSEGV in calloc()
UpgradeStatus: Upgraded to precise on 2012-02-17 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
naamlose (naamlose) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #923049, 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.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nux (Ubuntu):
status: New → Confirmed
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.