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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054458 Title: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/1054458/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
