compiz crashed with SIGSEGV in nux::CairoGraphics::GetBitmap()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Maybe this is a duplicate to bug 727636 , but I thought it may be better to report it separately to include the backtrace informations from apport.
The first time I tried to login to Unity after Nvidia drivers installed resulted in Compiz failing to start. Only the wallpaper of the desktop with mounted filesystem was visible. This seem to be the same problem as on a bug I reported some weeks early (728523, closed as invalid due to not being able to attach a backtrace that time).
Also note that I could only send a "reduced report", because Apport showed me that the uploaded data size would be 1,1 GB(!!!) (see also attached screenshot). My internet connection can't handle this in a reasonable time and I'm not sure if Launchpad will accept such large backtraces ;-)
Kind regards,
Jan
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.34-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sat Mar 19 18:45:28 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110319)
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=de_DE:en
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f652c06712c: movdqu -0x70(%rsi),%xmm6
PC (0x7f652c06712c) ok
source "-0x70(%rsi)" (0x0077aff0) not located in a known VMA region (needed readable region)!
destination "%xmm6" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
?? () from /lib/x86_
nux::CairoGrap
PanelMenuView:
PanelMenuView:
g_closure_invoke () from /usr/lib/
Title: compiz crashed with SIGSEGV in nux::CairoGraph
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (nautilus:1386): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
Thanks for the report, we've got all the informations now to debug that issue.
Marking it as a duplicate of lp:727636.