compiz.real crashed with SIGSEGV in drawWindow()

Bug #293619 reported by Koko
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: compiz

while running rhythmbox and update manager, the compiz suddenly crashed.

ProblemType: Crash
Architecture: i386
Disassembly: 0x0:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/compiz.real
Package: compiz-core 1:0.7.8-0ubuntu4
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --indirect-rendering core ccp
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=id_ID.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/compiz/libvideo.so
 ?? () from /usr/lib/compiz/libanimation.so
 ?? () from /usr/lib/compiz/libexpo.so
 drawWindow ()
Title: compiz.real crashed with SIGSEGV in drawWindow()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Revision history for this message
Koko (k02ah89) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
videoDrawWindowTexture (w=0x88a25f8, texture=0x889ed48, attrib=0xbfd9b5b8, mask=1)
animDrawWindowTexture (w=0x88a25f8, texture=0x889ed48, attrib=0xbfd9b5b8, mask=1)
expoDrawWindowTexture (w=0x88a25f8, texture=0x889ed48, attrib=0xbfd9b5b8, mask=1) at expo.c:1431
drawWindow (w=0x88a25f8, transform=0xbfd9bcfc, fragment=0xbfd9b5b8, region=0x889fcb0, mask=1)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in compiz:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in compiz:
status: Incomplete → Invalid
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.