compiz crashed with SIGSEGV in sigc::signal_base::impl()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: unity
This time I set "Window Animations" to true in compizconfig-
Symptoms:
compiz restarted several times. When the mouse cursor was usable again, I was able to operate all windows and clickspots, but redraws would not always happen, resulting in visual artifacts of windows, buttons, icons etc.
Tried:
Switching desktops did also not redraw, but still showed the existing graphics output (clickspots not usable then, of course).
Switching to console (CTRL+ALT+F1) and back did just restore the same state.
Logging out of the session did not bring up gdm, but a blank screen.
Supposed cause:
I guess the cause could be in display-driver xorg-server-intel, provoked by compiz or not I am uncertain.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.6.8-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Mar 30 14:09:57 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=de:en
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x111e3d <_ZNK4sigc11sig
PC (0x00111e3d) ok
source "0x4(%edi)" (0x0000007c) not located in a known VMA region (needed readable region)!
destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
sigc::
sigc::
UnityScreen:
CompPlugin:
CompManager:
Title: compiz crashed with SIGSEGV in sigc::signal_
UpgradeStatus: Upgraded to natty on 2011-03-23 (7 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #745315, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.