I was in ubuntu tweak looking through the login, and I lost metacitty, and I can not get alt &f2 to pop up. I can only tab tp get to diferent parts of the web page. I have to restart now
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.14.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sun Sep 11 05:30:22 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x76fe2e <_ZNK4sigc11signal_base4implEv+30>: mov 0x4(%edi),%esi
PC (0x0076fe2e) ok
source "0x4(%edi)" (0x00000084) not located in a known VMA region (needed readable region)!
destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
sigc::signal_base::impl() const () from /usr/lib/libsigc-2.0.so.0
sigc::signal_base::connect(sigc::slot_base const&) () from /usr/lib/libsigc-2.0.so.0
UnityScreen::UnityScreen(CompScreen*) () from /usr/lib/compiz/libunityshell.so
PluginClassHandler<UnityScreen, CompScreen, 0>::get(CompScreen*) () from /usr/lib/compiz/libunityshell.so
CompPlugin::VTableForScreenAndWindow<UnityScreen, UnityWindow>::initScreen(CompScreen*) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in sigc::signal_base::impl()
UpgradeStatus: Upgraded to oneiric on 2011-09-10 (1 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
XsessionErrors:
(ubuntu-tweak:4209): GConf-WARNING **: : You can't use a GConfEngine that has an active GConfClient wrapper object. Use GConfClient API instead.
(ubuntu-tweak:4209): GConf-WARNING **: : You can't use a GConfEngine that has an active GConfClient wrapper object. Use GConfClient API instead.
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 #831769, 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.