compiz crashed with SIGSEGV in g_datalist_id_set_data_full()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crashes when changing screen layout between two monitors and a single monitor.
Screen 0: minimum 320 x 200, current 3200 x 1200, maximum 8192 x 8192
DisplayPort-0 connected 1920x1200+1280+0 (normal left inverted right x axis y axis) 519mm x 324mm
1920x1200 60.0*+
1600x1200 60.0
1680x1050 60.0
1280x1024 75.0 60.0
1152x864 75.0
1024x768 75.1 60.0
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
DVI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 359mm x 287mm
1280x1024 60.0*+
1024x768 75.1 60.0
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.0.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-8-generic x86_64
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Jan 13 12:20:14 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fcb8021eb05 <g_datalist_
PC (0x7fcb8021eb05) ok
source "0x0(%r13)" (0xaaaaaaaaaaaa
destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
g_datalist_
?? () from /usr/lib/
g_object_unref () from /usr/lib/
unity:
unity:
Title: compiz crashed with SIGSEGV in g_datalist_
UpgradeStatus: Upgraded to precise on 2012-01-12 (1 days ago)
UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare video
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 #916228, 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.