Disable Display Device dialog shown on the unplugged monitor

Bug #845857 reported by Steve Magoun
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-settings (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have a dual-monitor setup (laptop + external monitor). Unplugging the external monitor then running 'detect displays' in NVidia Settings results in the "Disable Display Device" dialog being displayed on the just-unplugged monitor. This is not helpful.

To reproduce:
1) Boot Ubuntu w/ an external monitor hooked up. The system comes up and drives both screens
2) Launch nvidia-settings; select "X Server Display Configuration". Note that the 2 screens are shown in in TwinView mode. The laptop's internal monitor (DFP-0 on GPU 0) is set as the primary display according to the "Make this the primary display for the X screen" checkbox in NVidia Settings
3) Unplug the external monitor
4) Press the "Detect Displays" button

At this point the nvidia-settings app appears to hang - the buttons (including 'Quit') don't respond. The Layout widget continues to show the external monitor as being connected. The device tree in the left pane of NVida Settings does show the external display as being removed from GPU 0.

5) Plug the external monitor back in. Note the "Disable Display Device" dialog is displayed on the external monitor.

The dialog should not be displayed on the monitor that was just unplugged. It should be displayed on the monitor that was not unplugged, so that it is actually usable.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: nvidia-settings 280.13-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Fri Sep 9 13:45:17 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-settings
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (7 days ago)

Revision history for this message
Steve Magoun (smagoun) wrote :
Revision history for this message
Bryce Harrington (bryce) wrote :

Hey smagoun,

Hi, thanks for reporting this issue during the development period of
Ubuntu.

I notice there's not been further comments to the bug report since the
release came out, would you mind updating us on the status of it in the
release?

Are you still able to reproduce the issue? If not, do you think the bug
report can be closed, or do you think we should continue tracking it?

Changed in nvidia-settings (Ubuntu):
status: New → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in nvidia-settings (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Steve Magoun (smagoun) wrote :

Still buggy in 11.10 with all updates applied as of today (dec 19). I've also reproduced with nvidia-current-updates 285.05.09-0ubuntu0.1 installed.

Changed in nvidia-settings (Ubuntu):
status: Expired → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.