compiz.real crashed with SIGSEGV in malloc()

Bug #459915 reported by Majestyx
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: compiz

i start the Paketmanager, no PM but compiz crashes

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/compiz.real
MachineType: Foxconn OEM
NonfreeKernelModules: nvidia
Package: compiz-core 1:0.8.2-0ubuntu8.1
ProcCmdLine: root=UUID=73ebc1e8-63ed-4079-b356-6a2955f2e5b0 ro splash
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --sm-client-id 1032c99521c868b06f125619413490662200000037190033 --loose-binding core ccp
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-16.55-generic
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libxcb.so.1
 ?? () from /usr/lib/libxcb.so.1
 xcb_wait_for_reply () from /usr/lib/libxcb.so.1
Title: compiz.real crashed with SIGSEGV in malloc()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Majestyx (majestyx) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:_int_malloc (av=0xb7e33140, bytes=40) at malloc.c:4295
*__GI___libc_malloc (bytes=40) at malloc.c:3551
_xcb_in_read (c=0x96abf88)
_xcb_conn_wait (c=0x96abf88, cond=0xbf988b78, vector=0x0,
xcb_wait_for_reply (c=0x96abf88, request=17064664,

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
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) 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
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 (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.