touch-packages team mailing list archive

[Hannu N <_garbage_collector_@xxxxxxxxx>]

> the smae and more:
http://askubuntu.com/questions/477553/ubuntu-14-04-cant-get-nvidia-prime-working/496873#496873

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1341140

Title:
  nvidia-setting not persistent.

Status in “coreutils” package in Ubuntu:
  New

Bug description:
  The following has a direct relation to not being able to save changed
  settings:

  nvidia-settings and the package files have an inconsistency that makes
  it hard if not impossible to get any changes to keep more than for the
  moment (at most).

   The settings file: /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile
  has a note, e.g. 
  $ head -n 10 /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile
  # Application profiles for the NVIDIA Linux graphics driver, version 340.24
  # Last modified: Wed Jul  2 15:07:50 PDT 2014
  # These profiles were provided by NVIDIA and should not be modified.  If you
  # wish to change the defaults provided here, you can override them by creating
  # custom rules in /etc/nvidia/nvidia-application-profiles-rc (which will apply
  # system-wide) or, for a given user, $HOME/.nv/nvidia-application-profiles-rc
  # (which will apply to that particular user). See the "APPLICATION PROFILE
  # SEARCH PATH" section of the NVIDIA Linux Graphics Driver README for more
  # information.

  ... that refers to the folder /etc/nvidia/ - which does not exist immediately after install.
  The file that refers to it is in /etc/alternatives/ ... where you find a lot of *nvidia* items.

  Clearly it is so though, that at least TWO of the files still need to
  be in /etc/nvidia to allow nvidia-settings to be at least somewhat
  functional.


  -- FIX --

  <pre>
  $ gksudo nvidia-settings 

  ERROR: nvidia-settings could not find the registry key file. This file should have been installed along with this driver at either /usr/share/nvidia/nvidia-application-profiles-337.25-key-documentation or
         /usr/share/nvidia/nvidia-application-profiles-key-documentation. The application profiles will continue to work, but values cannot be preopulated or validated, and will not be listed in the help text. Please see the README for possible
         values and descriptions.
  </pre>
  ... is that familiar? Then do
  <pre>
  sudo bash
  ...
  mkdir -p /etc/nvidia
  cd /etc/nvidia
  ln -s /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile_keys  nvidia-application-profiles-340.24-key-documentation 
  ln -s /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile  nvidia-application-profiles-340.24-rc
  </pre>

  Then check that you can see something similar to:
  <pre>
  $ ls -l
  total 0
  lrwxrwxrwx 1 root 58 jul 12 14:23 nvidia-application-profiles-340.24-key-documentation -> /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile_keys
  lrwxrwxrwx 1 root 53 jul 12 14:23 nvidia-application-profiles-340.24-rc -> /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile
  </pre>

  Note that "-340.24..." and maybe other parts may differ for you
  (depending on version of the driver), what is shown is after
  installing the very latest from the xorg-edgers ppa at this writing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1341140/+subscriptions