As per nvidia-settings-1.0/src/nvidia-settings.c /* * initialize the ui * * XXX it would be nice if we didn't do this up front, since we * may not even use the gui, but we want the toolkit to have a * chance to parse the commandline before we do... we should * investigate gtk_init_check(). Rewrote a few lines of code to enable that. This would allow nvidia-settings to run without getting this error: (nvidia-settings:17616): Gtk-WARNING **: cannot open display: Will attach patch, which is verified (by me) to work on 6629 and 7167. I wanted to submit this to Nvidia, but I don't know how. Reproducible: Always Steps to Reproduce:
Created attachment 59988 [details, diff] The patch to allow nvidia-settings to run without $DISPLAY
I meant to say: This would allow nvidia-settings to run without getting this error: (nvidia-settings:17616): Gtk-WARNING **: cannot open display: _when run from a normal ssh connection without X._
You could write to linux-bugs@nvidia.com
So is this still a issue or is it time to mak this as upstream?
Well, hopefully it would be fixed upstream. Does anyone know if this is fixed in the latest version of nvidia-settings?
esp. in nvidia-settings-1.0.20070302
I just have a question. Is this enough to keep it from being marked as stable x86? I have emerged this package succesfully on several different machines all of which it runs fine (as long as I'm not trying to run a GTK+ tool through an non-x ssh session). What do you think? Let me know if you want to see my output of my make.conf and emerge nvidia-settings.
Took care of following up on this submission to NVIDIA. They are considering this for inclusion and it is tracked internally as bug #368579. peper: You could probably be safe in committing this.
I am marking this as fixed, as upstream has applied the patch. Aaron Plattner at Nvidia has sent myself, Doug Klima and Piotr Jaroszyński this message: Hi guys, I just wanted to let you know that your patch has been applied and will be included in a future nvidia-settings release. I don't have an account at bugs.gentoo.org so I'm emailing you instead. -- Aaron
Thanks all, I have added 169.04 with the patch.