Add hook scripts to be run by nvidia-installer

Bug #317703 reported by Aaron Plattner
2
Affects Status Importance Assigned to Milestone
nvidia-common (Ubuntu)
Fix Released
Wishlist
Alberto Milone

Bug Description

Sorry this didn't make it into 180.22, Alberto. I finally got around to implementing the hook script code we talked about, and the next round of releases will include it. Here's the relevant new section in the manpage:

DISTRIBUTION HOOK SCRIPTS
       Because the NVIDIA installer may interact badly with distribution packages that contain the NVIDIA driver,
       nvidia-installer provides a mechanism for the distribution to handle manual installation of the driver. If they
       exist, nvidia-installer will run the following scripts:
              · /usr/lib/nvidia/pre-install
              · /usr/lib/nvidia/pre-uninstall
              · /usr/lib/nvidia/post-uninstall
              · /usr/lib/nvidia/post-install
              · /usr/lib/nvidia/failed-install
       Note that if installation of a new driver requires uninstallation of a previously installed driver, the pre- and
       post-uninstall scripts will be called after the pre-install script. If the install fails, the installer will exe‐
       cute /usr/lib/nvidia/failed-install instead of /usr/lib/nvidia/post-install. These scripts should not require user
       interaction.

       Use the --no-distro-scripts option to disable execution of these scripts.

I don't know if nvidia-graphics-drivers-* is really the right place for these scripts. It might be necessary to add a new package, depending on what you want them to do.

Changed in nvidia-graphics-drivers-180:
assignee: nobody → albertomilone
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi aplattner,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

Please attach the output of `lspci -vvnn` too.

[This is an automated message. If this script has reached you erroneously, please accept our apologies; any reply to this message will be sufficient to prevent it from doing further automated processing.]

Changed in nvidia-graphics-drivers-180:
status: New → Incomplete
Revision history for this message
Aaron Plattner (aplattner) wrote :

Dear Bryce Harrington's automated script: This is a wishlist bug, but I can't change the importance because I'm not a project maintainer or a bug supervisor. Changing status back to New.

Changed in nvidia-graphics-drivers-180:
status: Incomplete → New
Revision history for this message
Alberto Milone (albertomilone) wrote :

Thanks for your work Aaron. Maybe I could add these scripts to my "nvidia-common" package so as to keep things in one place.

I look forward to seeing this implemented in the next release of the installer.

Changed in nvidia-graphics-drivers-180:
importance: Undecided → Wishlist
status: New → In Progress
Revision history for this message
Aaron Plattner (aplattner) wrote :

Attached is a patch against the 180.22 tag from git://people.freedesktop.org/~aplattner/nvidia-installer/ (http://cgit.freedesktop.org/~aplattner/nvidia-installer/)

You can test it by extracting the .run file with the -x option, changing to the unpacked directory, replacing the nvidia-installer with the one you built, and then running it as ./nvidia-installer

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

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

Revision history for this message
Aaron Plattner (aplattner) wrote : Re: [Bug 317703] Re: Add hook scripts to be run by nvidia-installer

On Thu, Apr 02, 2009 at 12:51:53PM -0700, Bryce Harrington wrote:
> c. If your bug still remains, please simply reply to this email
> indicating so.

This is an enhancement request for Ubuntu to use these hooks to allow
.run packages and dpkgs to interact correctly.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: In Progress → Triaged
Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Triaged → In Progress
affects: nvidia-graphics-drivers-180 (Ubuntu) → nvidia-common (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nvidia-common - 0.2.17

---------------
nvidia-common (0.2.17) lucid; urgency=low

  * setup.py:
    - Add pre-inst hook for the NVIDIA installer as
      the latter may interact badly with the Ubuntu
      packages(LP: #317703).
  * NvidiaDetector/nvidiadetector.py:
    - Handle driver flavours which have strings (instead
      of integers in their name).
  * NvidiaDetector/alternatives.py:
    - Alternatives class to get the list of alternatives
      and to get and set the alternative in use.
  * nvidia-common:
    - ${LATEST} should have quotation marks (LP: #505855).
 -- Alberto Milone <email address hidden> Mon, 11 Jan 2010 18:13:11 +0100

Changed in nvidia-common (Ubuntu):
status: In Progress → Fix Released
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.