compiz crashed with SIGSEGV in free()

Bug #747692 reported by digitalcrow
198
This bug affects 46 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: compiz

Compiz crashed every while !
This time it crashed when i pressed Alt+ F2

Come on guys its nice desktop but i hate bugs!!!

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4git20110322-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 1 22:32:11 2011
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=el_GR:en
 LANG=el_GR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature_: Ubuntu 2.6.38-7.39-generic 2.6.38
SegvAnalysis:
 Segfault happened at: 0x7fdb6a91b88d <free+29>: mov -0x8(%rdi),%rsi
 PC (0x7fdb6a91b88d) ok
 source "-0x8(%rdi)" (0x44234000c27ffff8) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 free () from /lib/x86_64-linux-gnu/libc.so.6
 g_closure_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: compiz crashed with SIGSEGV in free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu1

Revision history for this message
digitalcrow (digitalcrow) wrote :
tags: added: compiz-0.9
Revision history for this message
Fernando del Valle (fernandodelvalle) wrote :

I was switching the active panel of midnight commander with mouse

Revision history for this message
Erik B. Andersen (azendale) wrote :

I logged in and had no window decorator. Opened terminal and ran gtk-window-decorator. Tried to move the terminal window with and and left mouse button drag -> crash.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

compiz 1:0.9.4git20110322

Changed in compiz (Ubuntu):
status: New → Confirmed
Revision history for this message
GaaL (gaal33) wrote :

It always append when I 'm switching between windows with alt-tab

Revision history for this message
Hidde van Gelder (hjvgelder) wrote :

It also crashes every now and then when I try to move a window to another workspace with CTRL+ALT+SHIFT+up/down/left/right

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in compiz (Ubuntu):
importance: Undecided → Low
status: Confirmed → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug should be fixed in the current version but feel free to open a new one if it still crashes for you

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.