Bug 166647 - [patch] x11/nvidia-settings should ignore disconnected display devices
[patch] x11/nvidia-settings should ignore disconnected display devices
Status: Closed FIXED
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s)
Any Any
: Normal Affects Only Me
Assigned To: Alexander Nedotsukov
Depends on:
  Show dependency treegraph
Reported: 2012-04-04 17:30 UTC by david
Modified: 2012-04-07 16:50 UTC (History)
0 users

See Also:

file.diff (888 bytes, patch)
2012-04-04 17:30 UTC, david
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description david 2012-04-04 17:30:05 UTC
	As discussed (e.g.) in
	<http://ubuntuforums.org/showthread.php?t=1047029>, if one uses
	nvidia-settings to make use of a second display, then disables
	the second display and disconnects it, a subsequent invocation
	of nvidia-settings (e.g., to connect a different display) may
	(will?) cause nvidia-settings to display a message such as:

	Unable to load X Server Display Configuration page:

	Failed to find display device 0x00000001 on screen 0 (on GPU-0)
	while parsing metamode:

	'CRT-0: nvidia-auto-select @1280x1024 +1440+0'

	if one tries to select "X Server Display Configuration".

	And at that point, it is no longer possible (in my experience,
	despite trying the circumventions mentioned in the above-cited
	ubuntuforums.org post) to perform any X Server Display
	Configuration using nvidia-settings --even if the display
	is re-attached ... unless one applies the attached patch
	and rebuilds nvidia-settings.

	A comment about the patch: it seemed to me that the existing
	behavior of nvidia-setting (whining and refusing to do anything
	because a display that used to be there wasn't there any more)
	was ... well, "unfortunate" (to say it politely).  So I changed
	the code to bypass displays that it can't find -- which seems to
	me to be ... well, almost sensible.

	I note that ideally, this change would be made upstream.  That,
	or some other change would be made upstream to fix the problem.
	In the mean time, the attached patch does resolve it for me,
	and we thus have a way to make the FreeBSD port usable despite
	the bug.

Fix: Drop the attached patch into the port's files directory as
	patch-ctkdisplayconfig-utils.c, then rebuild the port.
How-To-Repeat: 	I think I covered it fairly well in Description.
Comment 1 scheidell freebsd_committer 2012-04-04 20:13:17 UTC
Responsible Changed
From-To: freebsd-ports-bugs->bland

Maintainer has GNATS access. 
Fix Synopsis.
Comment 2 dfilter freebsd_committer 2012-04-07 16:39:13 UTC
bland       2012-04-07 15:39:05 UTC

  FreeBSD ports repository

  Modified files:
    x11/nvidia-settings  Makefile 
  Added files:
  Let users to recover from the situation when the display was used is
  PR:             166647
  Feature safe:   yes
  Revision  Changes    Path
  1.53      +1 -0      ports/x11/nvidia-settings/Makefile
  1.1       +11 -0     ports/x11/nvidia-settings/files/patch-src__gtk+-2.x__ctkdisplayconfig-utils.c (new)
cvs-all@freebsd.org mailing list
To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
Comment 3 Alexander Nedotsukov freebsd_committer 2012-04-07 16:39:37 UTC
State Changed
From-To: open->closed

Modified version of patch commtted, thanks! 

I'd prefere nvidia-settings to make some noise on the console in a such 

And please, do bug upstream about the issue.