compiz crashed with SIGSEGV in nux::Rect::Rect()

Bug #975939 reported by JohnWashington
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Freshly installed system, using daily build 2012-04-07. System just started, nothing else done.

User left clicked on Ubuntu One icon, nothing immediately happened, so she right clicked on it. Unclear whether the crash had already happened.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
Uname: Linux 3.2.0-22-generic-pae i686
ApportVersion: 2.0-0ubuntu4
Architecture: i386
Date: Sat Apr 7 14:13:09 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120407)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nux
Title: compiz crashed with SIGSEGV in nux::Rect::Rect()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
JohnWashington (ubuntu-johnwash) wrote :
visibility: private → public
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 #954736, 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.

affects: ubuntu → nux (Ubuntu)
tags: removed: need-i386-retrace
Revision history for this message
JohnWashington (ubuntu-johnwash) wrote :

"duplicate of bug #954736"? But the link to that bug says "cannot be found", so how do I verify if it really is a duplicate?

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.