gtk-window-decorator crashed with SIGSEGV in g_object_unref()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
when i'm login with unity, i only get an empty blank screen: no dash, no icons.
So i run "setsid unity" into a terminal to get the icons & dash. Compiz is loaded, but fails with " no default decoration found".
Running "gtk-window-
I also get these errors logged:
- gnome-session[
- gnome-session[
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: compiz-gnome 1:0.9.9~
ProcVersionSign
Uname: Linux 3.8.0-15-generic i686
NonfreeKernelMo
.proc.driver.
.proc.driver.
.proc.driver.
NVRM version: NVIDIA UNIX x86 Kernel Module 313.26 Wed Feb 27 12:36:26 PST 2013
GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-22ubuntu4)
.tmp.unity.
ApportVersion: 2.9.2-0ubuntu5
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
CompositorUnred
CompositorUnred
CrashCounter: 1
Date: Thu Mar 28 10:44:26 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
DkmsStatus:
nvidia-
nvidia-
vboxhost, 4.2.10, 3.8.0-14-generic, i686: installed
vboxhost, 4.2.10, 3.8.0-15-generic, i686: installed
ExecutablePath: /usr/bin/
GraphicsCard:
NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:824f]
Lsusb:
Bus 002 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
MarkForUpload: True
ProcCmdline: /usr/bin/
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0xb756c241: mov (%eax),%eax
PC (0xb756c241) ok
source "(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
g_object_unref () from /usr/lib/
?? ()
g_object_unref () from /usr/lib/
Title: gtk-window-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: Debian-exim adm admin audio avahi avahi-autoipd backup bin cdrom clamav colord couchdb crontab daemon debian-tor dialout dip disk fax floppy fuse games gnats haldaemon i2c irc klog kmem libuuid lightdm list lp lpadmin mail man messagebus mlocate mysql mythtv netdev news ntp operator pcscd plugdev polkituser powerdev proxy pulse pulse-access root rtkit sambashare saned sasl scanner shadow src ssh ssl-cert staff sudo sys syslog tape tty users utempter utmp uucp vboxusers video voice whoopsie winbindd_priv www-data
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P5W DH Deluxe
dmi.product.
dmi.sys.vendor: ASUSTEK COMPUTER INC
version.compiz: compiz 1:0.9.9~
version.libdrm2: libdrm2 2.4.43-0ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Thu Mar 28 10:42:49 2013
xserver.configfile: default
xserver.devices:
input Power Button KEYBOARD, id 6
input Power Button KEYBOARD, id 7
input Logitech USB RECEIVER MOUSE, id 8
input AT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
open /dev/dri/card0: No such file or directory
open /dev/dri/card0: No such file or directory
open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.13.3-0ubuntu4
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1061282, 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.