compiz crashed with SIGSEGV

Bug #980542 reported by casparvanster
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

after update unity crashed with above message, ubuntu 2d is still working but with unity I get black screen and no control over pc other than right click settings menu.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
Date: Fri Apr 13 03:38:10 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f64769e97e5: mov (%rsi),%rax
 PC (0x7f64769e97e5) ok
 source "(%rsi)" (0x7f6424236000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.295.40
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.295.40
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.295.40
Title: compiz crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-03-27 (16 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
casparvanster (casparvan) wrote :
tags: removed: need-amd64-retrace
Revision history for this message
casparvanster (casparvan) wrote :

when trying to fix broken packages, got this message in terminal window:

GConf Error: Configuration server couldn't be contacted: D-BUS error: Can't overwrite existing read-only value: Value for `/apps/metacity/global_keybindings/panel_main_menu' set in a read-only source at the front of your configuration path

has this to do with unity crash??

I also re-enabled unity plugins in ccsm, but I keep getting black screen and unresponsive windows(terminal comes up but I cannot type commands)
when I reboot, 2D version works but seems rather slow.

visibility: private → public
Revision history for this message
casparvanster (casparvan) wrote :
Download full text (14.9 KiB)

cas@cas-imedia-S1300:~$ unity --reset
unity-panel-service: geen proces gevonden
Checking if settings need to be migrated ...no
Checking if internal files need to be migrated ...no
Backend : gconf
Integration : true
Profile : unity
Adding plugins
Initializing core options...done
compiz (core) - Warn: failed to receive ConfigureNotify event on 0x1600004

compiz (core) - Warn: failed to receive ConfigureNotify event on 0x1200002

compiz (core) - Warn: failed to receive ConfigureNotify event on 0x1400002

compiz (core) - Warn: failed to receive ConfigureNotify event on 0x3c00035

Initializing composite options...done
Initializing opengl options...done
Initializing decor options...done
Initializing vpswitch options...done
Initializing snap options...done
Initializing mousepoll options...done
Initializing resize options...done
Initializing place options...done
Initializing move options...done
Initializing wall options...done
Initializing grid options...done
Initializing session options...done
Initializing gnomecompat options...done
Initializing animation options...done
Initializing fade options...done
Initializing unitymtgrabhandles options...done
Initializing workarounds options...done
Initializing scale options...done
compiz (expo) - Warn: failed to bind image to texture
Initializing expo options...done
Initializing ezoom options...done

Screen geometry changed:
   0x0x1440x900

(compiz:3302): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed
Initializing unityshell options...done
compiz (core) - Warn: unhandled ConfigureNotify on 0x4800090!
compiz (core) - Warn: this should never happen. you should probably file a bug about this.
compiz (core) - Warn: unhandled ConfigureNotify on 0x4800093!
compiz (core) - Warn: this should never happen. you should probably file a bug about this.
compiz (core) - Warn: unhandled ConfigureNotify on 0x4800096!
compiz (core) - Warn: this should never happen. you should probably file a bug about this.
compiz (core) - Warn: unhandled ConfigureNotify on 0x4800099!
compiz (core) - Warn: this should never happen. you should probably file a bug about this.
compiz (core) - Warn: unhandled ConfigureNotify on 0x4800099!
compiz (core) - Warn: this should never happen. you should probably file a bug about this.
WARN 2012-04-13 10:46:24 unity.screeneffectframebufferobject ScreenEffectFramebufferObject.cpp:167 unsupported internal format
Starting gtk-window-decorator
WARN 2012-04-13 10:46:32 unity.glib-gobject <unknown>:0 invalid cast from `BamfWindow' to `BamfApplication'
ERROR 2012-04-13 10:46:32 unity <unknown>:0 bamf_application_get_desktop_file: assertion `BAMF_IS_APPLICATION (application)' failed
WARN 2012-04-13 10:46:32 unity.glib-gobject <unknown>:0 invalid cast from `BamfWindow' to `BamfApplication'
ERROR 2012-04-13 10:46:32 unity <unknown>:0 bamf_application_get_desktop_file: assertion `BAMF_IS_APPLICATION (application)' failed
WARN 2012-04-13 10:46:32 unity.glib-gobject <unknown>:0 invalid cast from `BamfWindow' to `BamfApplication'
ERROR 2012-04-13 10:46:32 unity <unknown>:0 bamf_application_get_desktop_file: assertion `BAMF_IS_APPLICATION (application)' failed
W...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 980298, so it 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. Feel free to continue to report any other bugs you may find.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

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

Other bug subscribers

Remote bug watches

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