compiz crashed with SIGSEGV in g_object_unref()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
11.10 beta is too buggy.... whether it is nautilus, software-center or any app i try to run, i always get a pop up to send bug report... i also wish unity and gnome-shell to co-exist peacefully without interfering with each other.. this will be the hallmark of oneiric ocelot... where user has the choice between unity and gnome-shell. both are unique in their own right and it will be bad if one is working and the other gets buggy...
skype is not working... and i dont know how many more apps will be buggy... i feel a complete check / revamp will be necessary before the stable release is out and time seems to be running out !!! its the first time i ve installed the beta version and hope i wont be disappointed by the developers ! thank you for reading this report...
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.10.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 17 13:31:39 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=en_IN:en
PATH=(custom, no user)
LANG=en_IN
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f32280f0ca2 <g_object_
PC (0x7f32280f0ca2) ok
source "(%rdi)" (0x0000001a) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
g_object_unref () from /usr/lib/
BamfLauncherIc
BamfLauncherIc
nux::Object:
nux::Object:
Title: compiz crashed with SIGSEGV in g_object_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #849792, 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.