compiz crashed with SIGSEGV in pthread_mutex_lock()

Bug #684445 reported by henning melgaard

This bug report was converted into a question: question #168786: compiz crashed with SIGSEGV in pthread_mutex_lock().

60
This bug affects 12 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: compiz

In Ubuntu 11.04 alpha1
I was trying to start compiz (double clicked the icon in the applications menu and opened a terminal and typed compiz)

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.2.1+glibmainloop2-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.37-7.19-generic 2.6.37-rc3
Uname: Linux 2.6.37-7-generic i686
Architecture: i386
CompizPlugins: No value set for `/apps/compiz/general/allscreens/options/active_plugins'
Date: Thu Dec 2 21:34:54 2010
ExecutablePath: /usr/bin/compiz
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101202)
MachineType: Hewlett-Packard Compaq Mini CQ10-100
PciDisplay: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller])
ProcCmdline: compiz
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: initrd=/ubninit file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/ubnkern
RelatedPackageVersions:
 xserver-xorg 1:7.5+6ubuntu3b1
 libgl1-mesa-glx 7.9+repack-1ubuntu2
 libdrm2 2.4.22-2ubuntu1
 xserver-xorg-video-intel 2:2.13.901-2ubuntu1
 xserver-xorg-video-ati 1:6.13.2-1ubuntu2
SegvAnalysis:
 Segfault happened at: 0x1a13bd <pthread_mutex_lock+29>: mov 0xc(%esi),%edi
 PC (0x001a13bd) ok
 source "0xc(%esi)" (0x00000011) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 pthread_mutex_lock () from /lib/libpthread.so.0
 ?? () from /lib/libglib-2.0.so.0
 Glib::Source::unreference() const () from /usr/lib/libglibmm-2.4.so.1
 PrivateScreen::~PrivateScreen() ()
 PrivateScreen::~PrivateScreen() ()
Title: compiz crashed with SIGSEGV in pthread_mutex_lock()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 11/05/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 14680 Ver. F.01
dmi.board.name: 1468
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 02.10
dmi.chassis.asset.tag: CNU0131NVS
dmi.chassis.type: 10
dmi.chassis.vendor: Inventec
dmi.modalias: dmi:bvnHewlett-Packard:bvr14680Ver.F.01:bd11/05/2009:svnHewlett-Packard:pnCompaqMiniCQ10-100:pvr0493200000001C00000300000:rvnHewlett-Packard:rn1468:rvrKBCVersion02.10:cvnInventec:ct10:cvr:
dmi.product.name: Compaq Mini CQ10-100
dmi.product.version: 0493200000001C00000300000
dmi.sys.vendor: Hewlett-Packard
glxinfo: Error: [Errno 2] No such file or directory
system: distro = Ubuntu, architecture = i686, kernel = 2.6.37-7-generic

Revision history for this message
henning melgaard (nymark1) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __pthread_mutex_lock (mutex=0x5) at pthread_mutex_lock.c:50
 g_source_unref_internal (source=0x95b3aa8, context=0x1,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Bouke Bunnik (bosyber) wrote :

Similar thing, but on amd64 machine - happened on startup+login

tags: added: compiz-0.9
Revision history for this message
Michael Terry (mterry) wrote :

Bug 711231 has better traces. Marking as dup.

Revision history for this message
jose ponce (japonce-4) wrote :

espero estar a la altura.

necesito el bios f.01 para una compaq mini cq10-100

Changed in compiz (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.