compiz crashed with SIGSEGV in _tnl_run_pipeline()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: unity
i logged in and updated ubuntu, the system asked me to restar my laptop, thing i did, i logged on again, i opened the displays (monitors) panel and i plugged and extra monitor with the "show the same on each monitor" unchecked, i clicked on "detect monitors", i indicated "on" for the extra monitor and click on apply. After that the wall appears on both monitors and then the wallpaper changed to stripes, like slashes, and a few seconds later i came back to the monitors panel with the extra monitor off and the bug window on my desktop
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.8.8-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
CrashCounter: 1
Date: Fri Apr 15 11:26:49 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=es_ES:en
LANG=es_MX.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xc4896c: mov (%eax),%eax
PC (0x00c4896c) ok
source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
_tnl_run_pipeline () from /usr/lib/
?? () from /usr/lib/
Title: compiz crashed with SIGSEGV in _tnl_run_pipeline()
UpgradeStatus: Upgraded to natty on 2011-04-06 (8 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #733346, 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.