compiz crashed with SIGSEGV; when changing monitor resolution, VMware Installation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Using 12.04 current update on a VMWare installation, with VMware player 4.0.1 build-528992, 768 Mbyte RAM, 1 Processor on a Ubuntu 10.04 Quad Core Host.
The System is extremly slow. Unity uses effects which seems not be supported yet by VMware grafics drives. It claims that there is no resolution adjustment possibly for many resolutions. At trying out which monitor resolution is supported Unity chrashed and claimed at the first time that there is not sufficient memory to collect data for bug reporting. Then, after a few minutes, it cames up with with a workinge bug report window.
I tryed to find an adjustment where I can disable grafics effects, like transparency, but I failed.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-17-
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Mon Feb 20 11:10:41 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120203)
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb7584760: movdqu (%eax),%xmm0
PC (0xb7584760) ok
source "(%eax)" (0x5a719e20) not located in a known VMA region (needed readable region)!
destination "%xmm0" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
?? () from /lib/i386-
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: compiz crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-02-19 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #927168, 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.