UnboundLocalError: local variable 'version' referenced before assignment

I saw the same issue. I performed fresh Ubuntu 22.04.1 install on Dell Precision 7540. First attempt I immediately installed proprietary drivers by enabling this third party option in install dialog. After this Software & Updates do not allow update. All options are greyed out and cannot be enabled. There is a message "This device is using a manually-installed driver"

Second attempt I installed without proprietary drivers / with third party disabled. After installation and reboot Software & Updates does allow me to select a proprietary driver. There is no longer a message "This device is using a manually-installed driver"

See screenshot for message

I also ran into this issue. In my case the package names were `nvidia-driver-515-open` and `nvidia-dkms-515-open` so I changed `version = int(package_name.split('-')[-1])` to `version = int(package_name.split('-')[2])` and that worked for me (`sudo ubuntu-drivers install` ran to completion). Not sure if that is a robust solution as I don't know how consistent the package names are. Also I'm new here.

Status changed to 'Confirmed' because the bug affects multiple users.

I confirmed @westonkelliher 's method and I have changed the python script with the file name '{usr-directory}/detect.py and it worked.

Thanks @westonkelliher !

# detect.py
def nvidia_desktop_pre_installation_hook(to_install):
    '''Applies changes that need to happen before installing the NVIDIA drivers'''
    with_nvidia_kms = False

    # Enable KMS if nvidia >= 470
    for package_name in to_install:
        if package_name.startswith('nvidia-driver-'):
            try:
                version = int(package_name.split('-')[-2]) #Line 839
            except ValueError:
                pass
            finally:
                with_nvidia_kms = version >= 470

    if with_nvidia_kms:
        set_nvidia_kms(1)

Have the same problem using a Ideapad 3i. The solution provided by Weston Kelliher works, with a few start up problems, but all right now.

What happened that it broken so many ppl things? wtf ubuntu
My gpu stopped detecting other two displays and one display has limited resolution. It was working!!! Stopped working few days ago
3080TI if that helps.. I think it's for nvidia only, but someone messed something pretty badly..

Also have this. Decided to update drivers after failure to run steam app. autoinstall fails

I have the same issue but I can't edit 'detect.py' as other people have suggested. It is a read-only file and I can't edit it. Any ideas how to do so? My issue is also that my second and third monitors are mostly black. Sometimes they work out of nowhere but then it goes out again.

I've just experienced the same issue, but with the ubuntu driver tool GUI (on Ubuntu 22.04).

I tried to change the NVIDIA drivers from 515 to 520-open. After asking for my password I got a pop-up with a big grey "X" and an "OK" button, but no text. Not helpful at all. Then I took a look at the installed "*nvidia*" packages with dpkg and noticed that all 515 packages had been removed but no 520 packages had been installed. When executing "ubuntu-drivers autoinstall" I got the same Python exception as above.

After that, I installed the 520 drivers with

"apt install nvidia-driver-520-open"

However, that didn't really work. After the reboot, I got a Kernel Oops:

[ 7.678638] NVRM: Open nvidia.ko is only ready for use on Data Center GPUs.
[ 7.678640] NVRM: To force use of Open nvidia.ko on other GPUs, see the
[ 7.678641] NVRM: 'OpenRmEnableUnsupportedGpus' kernel module parameter described
[ 7.678642] NVRM: in the README.
[ 7.680890] RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
[ 8.243707] NVRM s_executeBooterUcode_TU102: Booter failed with non-zero error code: 0xa
[ 8.243709] NVRM kgspExecuteBooterUnloadIfNeeded_TU102: failed to execute Booter Unload: 0xffff
[ 8.243713] NVRM nvAssertFailedNoLog: Assertion failed: rmStatus == NV_OK @ osinit.c:1982
[ 8.244983] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x63:0x0:1900)
[ 8.245515] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
[ 8.245564] [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate NvKmsKapiDevice
[ 8.245660] [drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to register device
[ 8.245666] BUG: kernel NULL pointer dereference, address: 0000000000000040
[ 8.245709] #PF: supervisor read access in kernel mode
[ 8.245722] #PF: error_code(0x0000) - not-present page
[ 8.245733] PGD 0 P4D 0
[ 8.245739] Oops: 0000 [#1] SMP NOPTI

Now I'm not sure if this is a driver issue or due to the way it has been installed ("520-open" is the recommended driver, so I assume that it should work). Anyway, that bug in ubuntu-drivers is a serious issue and should be fixed as soon as possible...

Update: Fixed by "apt install nvidia-driver-520". It seems like the "520-open" driver does not really work with consumer GPUs (at least not with my RTX 3060 TI). But then why is it marked as "recommended" and "tested" in the ubuntu-drivers tool? That should probably also be fixed...

I have also encountered this issue

I have nvidia-520 installed for a while. After noticing that the packages have been kept back (don't know why), I tried to upgrade the driver from the "Software and Updates" GUI. Not possible, all options grayed out and a message reads "This device is using a manually-installed driver".

Then I tried to "sudo ubuntu-drivers autoinstall", and got the error "UnboundLocalError: local variable 'version' referenced before assignment" and to this bug report.

The proposed change breaks extraction for drivers without -open.

A more appropriate fix is to regex extract the version number:
```
version = int(re.findall("[0-9]+", package_name)[0]
```

Hello Seth, or anyone else affected,

Accepted ubuntu-drivers-common into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.6.3.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Seth, or anyone else affected,

Accepted ubuntu-drivers-common into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.6.2~0.22.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Seth, or anyone else affected,

Accepted ubuntu-drivers-common into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.6.3.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Seth, or anyone else affected,

Accepted ubuntu-drivers-common into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.6.2~0.22.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

The installation proceeded as expected in Kinetic.

:~$ apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
  Installed: 1:0.9.6.3.2
  Candidate: 1:0.9.6.3.2
  Version table:
 *** 1:0.9.6.3.2 400
        400 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1:0.9.6.3 500
        500 http://it.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages

You can see the attached output of "ubuntu-drivers debug"

The installation proceeded as expected in Jammy.

:~$ apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
  Installed: 1:0.9.6.2~0.22.04.3
  Candidate: 1:0.9.6.2~0.22.04.3
  Version table:
 *** 1:0.9.6.2~0.22.04.3 500
        500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1:0.9.6.1 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

You can see the attached output of "ubuntu-drivers debug"

Note: neither in Jammy nor in Kinetic was the -open driver preferred over its non-open counterpart, which is one of the things that we want for this SRU.

This bug was fixed in the package ubuntu-drivers-common - 1:0.9.6.3.2

---------------
ubuntu-drivers-common (1:0.9.6.3.2) kinetic; urgency=medium

  * UbuntuDrivers/detect.py:
    - Fix "882:5 local variable 'with_nvidia_kms' is assigned to
      but never used" FTBFS (triggered by tests/test_static.py).

ubuntu-drivers-common (1:0.9.6.3.1) kinetic; urgency=medium

  [ Alberto Milone ]
  * debian/rules:
    - Limit the tests to the selected architectures (amd64, arm64).
      This prevents armhf builds from failing.
  * UbuntuDrivers/detect.py:
    - Make sure all -open drivers have a lower priority, regardless
      of whether the --server parameter is passed in or not.
    - Update regex and unify package name parsing in the following
      functions by using the new NvidiaPkgNameInfo class:
      nvidia_desktop_pre_installation_hook,
      _get_headless_no_dkms_metapackage,
      nvidia_desktop_pre_installation_hook,
      get_linux_modules_metapackage.
      This prevents ubuntu-drivers from crashing when dealing with
      the -open NVIDIA drivers (LP: #1993019).
  * tests/test_ubuntu_drivers.py:
    - Add tests so we make sure to keep preferring non-open NVIDIA
      modules over the -open ones, at least until the open modules catch up
      feature wise and performance wise.

  [ gongzhengyang ]
  * UbuntuDrivers/detect.py:
    - Fix local variable 'version' being referenced before assignment
      when catching ValueError (LP: #1993019).

  [ Jeff Lane ]
  * detect-plugins/sl-modem.py:
    - Add some error trapping when aplay is not installed (on servers)
      (LP: #1935070).

 -- Alberto Milone <email address hidden> Wed, 08 Mar 2023 15:57:25 +0000

The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Can someone tell me how to know when this fix hits the normal updates? Or how long this normally takes? I don't want to mess with editing files if I can help it, or attempting to not mess up my system by trying to include proposed.

Edit: was able to fix by:

sudo ubuntu-drivers install --gpgpu nvidia:xxx

where xxx is the number of the driver you want for me it was 530 but yours might be different options were 530-open, 470, 525, and so on. The I rebooted and installed the utilities with:

sudo apt install nvidia-utils-530

did nvidia-smi and it reported everything the way I wanted

Any reason for not releasing 0.9.6.2~0.22.04.3 to jammy-updates?

Alberto, it looks like nobody verified https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1988836

You can find the bugs that need verification or that failed verification on https://ubuntu-archive-team.ubuntu.com/pending-sru.html

Thanks

All related bugs https://bugs.launchpad.net/bugs/1988836 and https://bugs.launchpad.net/bugs/1935070 had been verified in Jammy. Can 0.9.6.2~0.22.04.3 be released to jammy-updates?

This bug was fixed in the package ubuntu-drivers-common - 1:0.9.6.2~0.22.04.3

---------------
ubuntu-drivers-common (1:0.9.6.2~0.22.04.3) jammy; urgency=medium

  * UbuntuDrivers/detect.py:
    - Fix "882:5 local variable 'with_nvidia_kms' is assigned to
      but never used" FTBFS (triggered by tests/test_static.py).

ubuntu-drivers-common (1:0.9.6.2~0.22.04.2) jammy; urgency=medium

  [ Alberto Milone ]
  * debian/rules:
    - Limit the tests to the selected architectures (amd64, arm64).
      This prevents armhf builds from failing.
  * UbuntuDrivers/detect.py:
    - Make sure all -open drivers have a lower priority, regardless
      of whether the --server parameter is passed in or not.
    - Update regex and unify package name parsing in the following
      functions by using the new NvidiaPkgNameInfo class:
      nvidia_desktop_pre_installation_hook,
      _get_headless_no_dkms_metapackage,
      nvidia_desktop_pre_installation_hook,
      get_linux_modules_metapackage,
      This prevents ubuntu-drivers from crashing when dealing with
      the -open NVIDIA drivers (LP: #1993019).
  * tests/test_ubuntu_drivers.py:
    - Add tests so we make sure to keep preferring non-open NVIDIA
      modules over the -open ones, at least until the open modules catch up
      feature wise and performance wise.

  [ gongzhengyang ]
  * UbuntuDrivers/detect.py:
    - Fix local variable 'version' being referenced before assignment
      when catching ValueError (LP: #1993019).

  [ Jeff Lane ]
  * detect-plugins/sl-modem.py:
    - Add some error trapping when aplay is not installed (on servers)
      (LP: #1935070).

 -- Alberto Milone <email address hidden> Wed, 08 Mar 2023 16:03:28 +0000