compiz crashed with SIGSEGV in PrivateWindow::configureFrame() when enabling second monitor ousing NVidia X Server Settings app
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Release:
Using 11.10 from a fresh install of beta2
Package version:
Unity: 4.20.0-0ubuntu1
NVidia Driver: 280.13
NVidia Control App: 1.27
What happened:
Laptop was already up, I plugged in vga cable connected to secondary monitor
opened up NVidia X Server Settings app (driver 280.13)
went to X Server Display Configuration
Clicked on 'Detect Displays' (secondary monitor showed up)
Clicked on the box representing the secondary monitor in the Layout pane
Clicked on 'Enable' drop down and selected 'Twin View'
Clicked apply
Screen flashed off then back on with laptop display showing desktop and secondary monitor showing a black screen
Received error
Expected:
Secondary monitor to display extended desktop, using my laptop display as the primary
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.20.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 30 11:51:48 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
SegvAnalysis:
Segfault happened at: 0x443ea8 <_ZN13PrivateWi
PC (0x00443ea8) ok
source "0x68(%rax)" (0x00000068) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
PrivateWindow:
CompScreen:
PrivateComposi
CompScreen:
PrivateGLScree
Title: compiz crashed with SIGSEGV in PrivateWindow:
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 #861909, 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.