compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x006f1ff4 ***
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Was trying to resize LibreOffice Calc window, but somehow ended up dragging the zoom slider back and forth, at the same time as resizing the window... When I let go of the mouse button, I could tell something wasn't right, so I minimized Calc. The transparent orange rectangle stayed, and LibreOffice Calc would not come back from being minimized. Eventually I got the crash /w error attached.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.18.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu1
Architecture: i386
AssertionMessage: *** glibc detected *** compiz: free(): invalid pointer: 0x006f1ff4 ***
CrashCounter: 1
Date: Tue Sep 27 13:26:23 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: unity
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/i386-
abort () from /lib/i386-
?? () from /lib/i386-
?? () from /lib/i386-
Title: compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x006f1ff4 ***
UpgradeStatus: Upgraded to oneiric on 2011-09-27 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Lucas Welper (lucaswelper) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
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 #750386, 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.