Ubuntu
compiz package

compiz.real crashed with signal 7 in eventLoop()

Bug #209882 reported by fluffybacon on 2008-03-31

This bug report is a duplicate of: Bug #131679: Crash inside doPoll(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	compiz (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: compiz

I was attempting to log in the system hung at the Nvidia logo screen.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Mar 31 20:18:50 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/compiz.real
NonfreeKernelModules: nvidia
Package: compiz-core 1:0.7.2-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --loose-binding --only-current-screen ccp
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_GB.UTF-8
SHELL=/bin/bash
Signal: 7
SourcePackage: compiz
Stacktrace:
#0 0x000000000040feb0 in ?? ()
#1 0x0000000000412444 in eventLoop ()
#2 0x000000000040d019 in main ()
StacktraceTop:
?? ()
eventLoop ()
main ()
ThreadStacktrace:
.
Thread 1 (process 8033):
#0 0x000000000040feb0 in ?? ()
#1 0x0000000000412444 in eventLoop ()
#2 0x000000000040d019 in main ()
Title: compiz.real crashed with signal 7 in eventLoop()
Uname: Linux 2.6.24-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

Tags:

Revision history for this message

fluffybacon (fluffybacon) wrote on 2008-03-31:

Dependencies.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (487 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (33.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (686 bytes, text/plain; charset="utf-8")
Registers.txt Edit (985 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2008-03-31: Possible regression detected

This crash has the same stack trace characteristics as bug #191365. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.