nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304'

[Removed by request]

If other people report this at the current level with xorg/nvidia it might be a bug. It is also possible the error stems from a bad combination of free and proprietary material. Further details will be provided as necessary/available.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: ubuntu-drivers-common 1:0.2.69
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Fri Sep 21 22:48:18 2012
ExecutablePath: /usr/bin/nvidia-detector
InterpreterPath: /usr/bin/python3.2mu
ProcCmdline: /usr/bin/python3.2 /usr/bin/nvidia-detector
ProcEnviron:
 SHELL=/bin/bash
 TERM=linux
 PATH=(custom, no user)
 LANG=de_CH.UTF-8
 LANGUAGE=de_CH:de
PythonArgs: ['/usr/bin/nvidia-detector']
SourcePackage: ubuntu-drivers-common
Title: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304'
UpgradeStatus: Upgraded to quantal on 2012-07-31 (52 days ago)
UserGroups: audio pulse pulse-access video

[Launchpad Janitor (janitor)]

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

[Martin Pitt (pitti)]

Alberto, this happens on current Quantal by merely calling nvidia-detector. It stumbles over the "nvidia-experimental-XXX" package name which it doesn't parse properly. Could you please have a look at this? Thanks!

[Norbert (nrbrtx)]

Same here. GT310M, Asus U30Jc.

[Norbert (nrbrtx)]

PC, Nvidia GeForce 9600 GT.

[Norbert (nrbrtx)]

It does not depend on installed driver package (nvidia-current, nvidia-current-updates or nvidia-experimental-304).

[Martin Pitt (pitti)]

Proposed fix in https://code.launchpad.net/~ted/ubuntu/raring/ubuntu-drivers-common/nvidia-experimental-number/+merge/137754

[Sebastien Bacher (seb128)]

the issue should be resolved in raring/quantal from the merge request comments, jockey in precise might need a similar fix though?

[Martin Pitt (pitti)]

No, it is not resolved in raring yet.

[Alberto Milone (albertomilone)]

This should be fixed in ubuntu-drivers-common 1:0.2.71.1 and in nvidia-common 1:0.2.44.2

[Timo Jyrinki (timo-jyrinki)]

According to errors.ubuntu.com, a duplicate of this bug - bug #1074892 - is being encountered also on the 12.04, and is currently the #1 crasher there.

[Alberto Milone (albertomilone)]

SRU request:

Please accept nvidia-common 1:0.2.44.3 in precise-proposed. The only change is a the addition of a test which tries to reproduce this bug when building the package.

Basically the test fakes the availability of an nvidia card and checks that the problem discussed in this bug report can no longer be reproduced.

[Iain Lane (laney)]

I just checked a lot of reports of this on errors.u.c; while they unfortunately don't show the nvidia-common version it's possible to correlate the updates the user had installed by checking against the version of jockey-gtk.

All users (who reported the problem 'recently'; after mid-November 2012 or so) I could see had jockey-gtk 0.9.7-0ubuntu7.1 or less. This was an update pushed out on 2012-08-17 and superseded on 2012-10-03. nvidia-common's fixed version was released to precise-updates also on 2012-10-03. Thus I think it is pretty safe to assume that users would have jockey -7.3 if they were to have the fixed nvidia-common.

So, as surprising as this is to me, I conclude (unless new evidence emerges) that there is a significant class of users who don't regularly install updates and are thus living with this bug despite it really being fixed in Precise.

[Timo Jyrinki (timo-jyrinki)]

Another reason may be that the Jockey pops up right after installation, and not everyone chooses to download updates during the installation. In this case 12.04.2 installers should be better off, assuming all the LTS-Q related stack proprietary driver fixes go in and work.

[Nafallo Bjälevik (nafallo)]

This bug have popped up again in Bionic.

nafallo@wendigo:~$ nvidia-detector
Traceback (most recent call last):
  File "/usr/bin/nvidia-detector", line 8, in <module>
    a = NvidiaDetection(printonly=True, verbose=False)
  File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 68, in __init__
    self.getData()
  File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 151, in getData
    driver_version = self.__get_value_from_name(stripped_package_name)
  File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 87, in __get_value_from_name
    v = int(name)
ValueError: invalid literal for int() with base 10: 'driver-390'

[Launchpad Janitor (janitor)]

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

---------------
ubuntu-drivers-common (1:0.5.1) bionic; urgency=medium

  * debian/control:
    - Build depend on dh-python.
    - Drop dh-systemd, and use debhelper (>= 9.20160709).
  * tests/ubuntu_drivers.py:
    - Raise time to 40.0 for i386 in
      test_system_driver_packages_performance().
  * NvidiaDetector/nvidiadetector.py:
    - Fix crash with new name scheme of the NVIDIA
      packages (LP: #1054458).
  * gpu-manager.(c|py):
    - Create a xorg.conf.d file for systems with PRIME.
      This way we can drop the PrimaryGpu option from
      the main NVIDIA configuration xorg.conf.d snippet,
      and generate an additional custom snippet on demand
      with that option, to avoid causing problems on systems
      with multiple NVIDIA GPUs (LP: #1756226).

 -- Alberto Milone <email address hidden> Thu, 12 Apr 2018 16:35:07 +0200

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1054458

[Bill (franksmcb) (franksmcb)]

This is occurring on Ubuntu MATE 20.10 daily with nvidia 390.138

[Colby Combs (clcombs)]

Ubuntu MATE 20.04, same issue with an nVidia GeForce MX150 on an ASUS Zenbook 14

[Colby Combs (clcombs)]

Driver version 440.100

[Perry Lanford (99125q)]

Same problem on new Dell G5 and MSI GE75 after initial install of Ubuntu 20.04 Mate
Nvidia GTX 1650 & RTX 2080 Super were using 440.100 driver and now using 450.66 but still getting the error.