compiz.real crashed with SIGSEGV in groupGroupWindows()

Bug #430902 reported by Linus Hoppe
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Compiz
Invalid
Undecided
Unassigned
compiz (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: compiz

Crash while trying to edit some preferences (grouping windows)

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/compiz.real
MachineType: Dell Inc. Studio 1535
NonfreeKernelModules: fglrx wl
Package: compiz-core 1:0.8.2-0ubuntu8.1
ProcCmdLine: root=UUID=3f9a6446-eac6-4000-a7e6-90f93268f43e ro quiet splash
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --indirect-rendering --sm-client-id 108970bbc797d0a85125311608066952300000044250027 core ccp
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-15.49-generic
Signal: 11
SourcePackage: compiz
StacktraceTop:
 groupGroupWindows () from /usr/lib/compiz/libgroup.so
 handleEvent ()
 ?? () from /usr/lib/compiz/libvideo.so
 ?? () from /usr/lib/compiz/libresize.so
 ?? () from /usr/lib/compiz/libextrawm.so
Title: compiz.real crashed with SIGSEGV in groupGroupWindows()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0xb70437ec <groupGroupWindows+220>: mov (%eax,%edx,1),%eax
 PC (0xb70437ec) ok
 source "(%eax,%edx,1)" (0x000003a5) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA

Revision history for this message
Linus Hoppe (linus-hoppe-deactivatedaccount) wrote :
visibility: private → public
Kees Cook (kees)
description: updated
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:groupGroupWindows (d=0x8310cd8, action=0x8f2bf0c,
handleEvent (d=0x8310cd8, event=0xbfa10d78)
videoHandleEvent (d=0x8310cd8, event=0xbfa10d78)
resizeHandleEvent (d=0x8310cd8, event=0xbfa10d78)
extraWMHandleEvent (d=0x8310cd8, event=0xbfa10d78)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Travis Watkins (amaranth) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in compiz (Ubuntu):
status: New → Incomplete
Revision history for this message
Linus Hoppe (linus-hoppe-deactivatedaccount) wrote :

I couldn't reproduce the error yet

Changed in compiz:
status: New → Invalid
Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you encounter that this issue is still occurring or even better if you can check in latest Ubuntu Karmic version. To reopen the bug report you can click under the Status column, and change the Status back to "New". Thanks again!

Changed in compiz (Ubuntu):
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.