compiz crashed adding external display via nvidia-settings

Bug #743692 reported by Chad A. Davis on 2011-03-27
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Nux
Invalid
Critical
Unassigned
Unity
Invalid
Critical
Unassigned
nux (Ubuntu)
Critical
Unassigned
unity (Ubuntu)
Critical
Unassigned

Bug Description

Using nvidia-settings, which detected the external monitor and showed it as 'disabled', I enabled twin view. While the video mode was changing, some artifacts appeared. I did some Alt-Tab'ing and some mouse wiggling to force a redraw when compiz crashed. Compiz restarted itself and both displays were working correctly.

This external monitor generally works fine on this system. This was a one-time crash and I cannot reproduce it every time.

Natty dev branch (2011-03-26) on MacBookPro6.2

nvidia-current:
  Installed: 270.30-0ubuntu3
  Candidate: 270.30-0ubuntu3
  Version table:
 *** 270.30-0ubuntu3 0
        500 http://de.archive.ubuntu.com/ubuntu/ natty/restricted amd64 Packages
        100 /var/lib/dpkg/status

compiz:
  Installed: 1:0.9.4git20110322-0ubuntu5
  Candidate: 1:0.9.4git20110322-0ubuntu5
  Version table:
 *** 1:0.9.4git20110322-0ubuntu5 0
        500 http://de.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.36-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: wl nvidia
Architecture: amd64
CrashCounter: 1
Date: Sun Mar 27 17:47:45 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64+mac (20110323)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f0982f41da0: movslq 0x314,%rax
 PC (0x7f0982f41da0) ok
 source "0x314" (0x00000314) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.30
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.30
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.30
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.30
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.30
Title: compiz crashed with SIGSEGV
UpgradeStatus: Upgraded to natty on 2011-03-26 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Chad A. Davis (chadadavis) wrote :
summary: - compiz crashed adding external model via nvidia-settings
+ compiz crashed adding external display via nvidia-settings

StacktraceTop:
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.30
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.30
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.30
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.30
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.270.30

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Alex Launi (alexlauni) wrote :

Is this something you can reproduce if you try a couple of times? If so could you please follow the instructions on https://wiki.ubuntu.com/Unity/FilingBugs#Getting%20a%20stack%20trace and attach unity.log to this bug report? Otherwise the trace provided isn't enough to really debug/fix the issue.

Changed in unity:
status: New → Incomplete
Changed in nux:
status: New → Incomplete
Changed in nux (Ubuntu):
status: New → Incomplete
visibility: private → public
Chad A. Davis (chadadavis) wrote :

I'm able to recreate the artifacts (on the primary display) by increasing and decreasing the resolution, but I'm not able to recreate the crash, neither via Alt-Tab nor via dragging windows over the parts of the display to force them to be redrawn.

Sebastien Bacher (seb128) wrote :

the issue seems rather an nvidia driver one than an unity bug

Dave Johnson (dave-scomple) wrote :

I have a similar problem while using radeon. My desktop is set up with two displays and the default behavior of mirroring the desktop on both displays works fine, but when I untick the "mirror desktop" option and span across both screens all I get is a bunch of artifacts on the second monitor. This is reproducible to an extent, I'll try the stack trace link posted above.

Dave Johnson (dave-scomple) wrote :

I looked at the stack trace page and have no idea what it's trying to get me to do, so no promises on that data.

Omer Akram (om26er) on 2011-04-19
Changed in unity (Ubuntu):
status: New → Incomplete
Didier Roche (didrocks) on 2011-05-31
Changed in nux:
importance: Undecided → Critical
Changed in unity:
importance: Undecided → Critical
Changed in nux (Ubuntu):
importance: Undecided → Critical
Changed in unity (Ubuntu):
importance: Undecided → Critical
Launchpad Janitor (janitor) wrote :

[Expired for nux (Ubuntu) because there has been no activity for 60 days.]

Changed in nux (Ubuntu):
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

[Expired for unity (Ubuntu) because there has been no activity for 60 days.]

Changed in unity (Ubuntu):
status: Incomplete → Expired
Omer Akram (om26er) on 2011-09-19
Changed in nux:
status: Incomplete → Invalid
Changed in unity:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers